From owner-freebsd-stable Sun Jan 21 1:36: 5 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 6AC9737B401 for ; Sun, 21 Jan 2001 01:35:46 -0800 (PST) Received: from localhost (darren@localhost) by tzeench.dhs.org (8.11.1/8.11.1) with ESMTP id f0L9Zog00542 for ; Sun, 21 Jan 2001 02:35:51 -0700 (MST) (envelope-from darren@tzeench.dhs.org) Date: Sun, 21 Jan 2001 02:35:50 -0700 (MST) From: Darren 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 alright, I'm not sure if this is a hardware problem that can be helped. but I wonder if anyone out there is having a similar problem. I have a maxtor 60 gig drive, whenever it approaches the 30 gig mark... we've never had a need to store more than that. it starts crashing. my system has frozen up two times in the last week. with the current incident I was in telnet over my lan from windows, decompressing a file and using cuteftp to download a different file. I heard a beep come from the computer(FreeBSD), and that was it... crashed... had to force a reboot by manually pressing the button. -Darren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 21 1:42: 6 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mailout06.sul.t-online.com (mailout06.sul.t-online.com [194.25.134.19]) by hub.freebsd.org (Postfix) with ESMTP id A94E437B400; Sun, 21 Jan 2001 01:41:46 -0800 (PST) Received: from fwd02.sul.t-online.com by mailout06.sul.t-online.com with smtp id 14KH0I-0005K5-01; Sun, 21 Jan 2001 10:41:42 +0100 Received: from frolic.no-support.loc (520094253176-0001@[217.80.111.50]) by fmrl02.sul.t-online.com with esmtp id 14KH08-05zm7cC; Sun, 21 Jan 2001 10:41:32 +0100 Received: (from bjoern@localhost) by frolic.no-support.loc (8.11.1/8.9.3) id f0L9XPG01498; Sun, 21 Jan 2001 10:33:25 +0100 (CET) (envelope-from bjoern) From: Bjoern Fischer Date: Sun, 21 Jan 2001 10:33:24 +0100 To: Roelof Osinga Cc: freebsd-stable@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: MAIL set by whom? Message-ID: <20010121103324.A297@frolic.no-support.loc> 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 X-Sender: 520094253176-0001@t-dialin.net Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > 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! :) You can set MAIL via /etc/login.conf, all applications that use either login(1) or setusercontext(3) should work. Beware of ssh! The OpenSSH client, that is part of FreeBSD is completey buggy here: It sets MAIL to /var/mail/$USER, this is hardcoded. I have a dirty fix, maybe I'll clean it up and send it as a PR or to Kris (Kris, are you still ssh maintainer?) This whole stuff of initial user environment and friends has to be cleaned up to be consistent for all login methods: login(1), xdm, rsh, rlogin, ssh, telnet. I would volunteer(sic!) for a in detail analysis of this issue if I get feedback on this. (i.e. looking for inconsistencies, where to put on solutions (e.g. a pam module that evals /etc/login.conf via setusercontext(3)). To fiddle with user's .bash{rc,_profile}, .tcshrc, .whateverrc is the wrong way. Some rc files are not evaluated for non login shells, so you put it into .bashrc or whatever get executed for non login shells; if you do this you parameters will be overwritten each time you start a new shell (e.g. xterm). The user should have a minimal reasonable environment (even without shell rc files, if you want to go that far), that he/she may optionally extend or adapt. /etc/login.conf, maybe in combination with pam, is the right thing for doing this. Bjoern -- -----BEGIN GEEK CODE BLOCK----- GCS d--(+) s++: a- C+++(-) UB++++OSI++++$ P+++(-) L---(++) !E W- N+ o>+ K- !w !O !M !V PS++ PE- PGP++ t+++ !5 X++ tv- b+++ D++ G e+ h-- y+ ------END GEEK CODE BLOCK------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 21 6:18:23 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 2332A37B401 for ; Sun, 21 Jan 2001 06:18:05 -0800 (PST) Received: (qmail 15935 invoked by uid 0); 21 Jan 2001 14:18:03 -0000 Received: from p3ee21650.dip.t-dialin.net (HELO speedy.gsinet) (62.226.22.80) by mail.gmx.net (mp010-rz3) with SMTP; 21 Jan 2001 14:18:03 -0000 Received: (from sittig@localhost) by speedy.gsinet (8.8.8/8.8.8) id LAA22582 for freebsd-stable@freebsd.org; Sun, 21 Jan 2001 11:33:35 +0100 Date: Sun, 21 Jan 2001 11:33:35 +0100 From: Gerhard Sittig To: freebsd-stable@freebsd.org Subject: Re: MAIL set by whom? Message-ID: <20010121113334.P253@speedy.gsinet> Mail-Followup-To: freebsd-stable@freebsd.org References: <3A6A50F3.307C9E06@nisser.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <3A6A50F3.307C9E06@nisser.com>; from roelof@nisser.com on Sun, Jan 21, 2001 at 04:01:07AM +0100 Organization: System Defenestrators Inc. Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jan 21, 2001 at 04:01 +0100, Roelof Osinga wrote: > > The following is what i've got: > > nl:~$ grep MAIL /etc/* You better may do something like find /etc -type f -print | xargs grep -wn MAIL /dev/null which walks the complete /etc tree and only greps in regular files. You might find /etc/defaults and friends of interest, too, sometimes. The /dev/null thingy is a "trick" to make grep display a file name even if it has only one "real" file to grep through. [ cutting down your list to 'grep -w' output :) ] [ your lines were wrapped, too, without being marked as such; PLONK your mail frontend for this stupidity (why don't you use mutt?) ] > > /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/services:ni-mail 61/tcp #NI MAIL > /etc/services:ni-mail 61/udp #NI MAIL [ inserting your complaint from below ] > The above /etc/login.conf parts don't do the trick and other > occurrences of MAIL I can't find. Have you looked at what sections these MAIL settings are in? That "these don't do the trick" may have a reason. Issue some grep -n '^[a-z][a-z]*:' /etc/login.conf which (together with the above -wn) should give you the idea. Or alternatively open /etc/login.conf with your favourite $PAGER to eyeball it, grep output is not always meant for human reception. > nl:~$ grep MAIL * You're absolutely missing _all_ your _config_ files! :) Use grep -w MAIL ~/.??* > PS I've read about: > > nl:~$ cat .mutttrc Check your spelling, please. This might have been in your message only, but when it's in your $HOME, it "won't do the trick". :> And I would better move to the ~/.mutt/muttrc scheme which in presence of all the address books, included configs and stuff leaves your $HOME sane und mostly uncluttered. 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 Sun Jan 21 7:10:18 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 694E037B6A0 for ; Sun, 21 Jan 2001 07:10:01 -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 JAA18941 for ; Sun, 21 Jan 2001 09:19:36 -0600 From: "Paul A. Howes" To: Subject: Error in installworld Date: Sun, 21 Jan 2001 10:09:56 -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 wanted to change the partitioning on my laptop computer, so I wiped it clean, performed an FTP-install of 4.2-RELEASE, and then did an installworld over NFS from my server, which had been updated through cvsup yesterday, January 20th. When installworld tried to install the man pages for /usr/src/secure/usr.bin/openssl, the process complained that it couldn't find "pod2man". I did a quick search, and it was definately in /usr/bin, and /usr/bin was in my path. I tried re-running the installworld, but it died at the same place. Finally, I did a simple "rehash" to refresh the shell's built-in command hashtable, and re-ran the installworld for the third time. Then, it worked flawlessly. This has not happened on any of my systems that regularly track 4-STABLE. I usually run cvsup and buildworld/buildkernel on my server every Saturday or Sunday morning. This is the first time in a while that I have put a "virgin" system on the network, and had to make this large of a jump from RELEASE to STABLE. Does anyone have any thoughts on this? 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 Sun Jan 21 7:12:53 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 3330637B6A0 for ; Sun, 21 Jan 2001 07:12:35 -0800 (PST) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id QAA65674; Sun, 21 Jan 2001 16:12:29 +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: Gerhard Sittig Cc: freebsd-stable@FreeBSD.ORG Subject: Re: MAIL set by whom? References: <3A6A50F3.307C9E06@nisser.com> <20010121113334.P253@speedy.gsinet> From: Dag-Erling Smorgrav Date: 21 Jan 2001 16:12:29 +0100 In-Reply-To: Gerhard Sittig's message of "Sun, 21 Jan 2001 11:33:35 +0100" Message-ID: Lines: 9 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 Gerhard Sittig writes: > You better may do something like > find /etc -type f -print | xargs grep -wn MAIL /dev/null grep -rwn MAIL /etc 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 21 7:46:26 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 DC4C137B402; Sun, 21 Jan 2001 07:45:53 -0800 (PST) Received: from nisser.com (roelof [10.0.0.2]) by nisser.com (8.9.3/8.9.2) with ESMTP id QAA93365; Sun, 21 Jan 2001 16:45:50 +0100 (CET) (envelope-from roelof@nisser.com) Message-ID: <3A6B042E.659C716D@nisser.com> Date: Sun, 21 Jan 2001 16:45:50 +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: Bjoern Fischer Cc: freebsd-stable@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: MAIL set by whom? References: <3A6A50F3.307C9E06@nisser.com> <20010121103324.A297@frolic.no-support.loc> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bjoern Fischer wrote: > > > ... > > So what gives? (IOW please help! :) > > You can set MAIL via /etc/login.conf, all applications that use > either login(1) or setusercontext(3) should work. > > Beware of ssh! The OpenSSH client, that is part of FreeBSD is > completey buggy here: It sets MAIL to /var/mail/$USER, this is > hardcoded. I have a dirty fix, maybe I'll clean it up and > send it as a PR or to Kris (Kris, are you still ssh maintainer?) And guess what I'm using ;). But that explains it. Thanks for reminding me. > This whole stuff of initial user environment and friends has > to be cleaned up to be consistent for all login methods: login(1), > xdm, rsh, rlogin, ssh, telnet. I would volunteer(sic!) for a in detail > analysis of this issue if I get feedback on this. (i.e. looking for > inconsistencies, where to put on solutions (e.g. a pam module > that evals /etc/login.conf via setusercontext(3)). Grand gesture. Laudable even. Yeah, that PAM sure seems to've become popular. The Courier IMAP port also insisted upon its installation. Insisted in that fiddling with the makefile only resulted in failure to configure. But that's a whole different story. > To fiddle with user's .bash{rc,_profile}, .tcshrc, .whateverrc > is the wrong way. Some rc files are not evaluated for non login shells, > so you put it into .bashrc or whatever get executed for non login > shells; if you do this you parameters will be overwritten each time > you start a new shell (e.g. xterm). Sure, but it does the trick for now. > The user should have a minimal reasonable environment (even without > shell rc files, if you want to go that far), that he/she may optionally > extend or adapt. /etc/login.conf, maybe in combination with pam, is > the right thing for doing this. Mebbe. But just like there's PAM, there's also LDAP and let us not forget Kerberos. Played with them, once upon a time, but not enough to have a feel for their possible impacts. Just be careful with what you volunteer for! ;). 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 Sun Jan 21 8: 8:58 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 DA73237B400 for ; Sun, 21 Jan 2001 08:08:32 -0800 (PST) Received: from nisser.com (roelof [10.0.0.2]) by nisser.com (8.9.3/8.9.2) with ESMTP id RAA93443; Sun, 21 Jan 2001 17:08:25 +0100 (CET) (envelope-from roelof@nisser.com) Message-ID: <3A6B0979.59CCED72@nisser.com> Date: Sun, 21 Jan 2001 17:08:25 +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> <3A6A63A5.94C2BC86@nisser.com> <20010120234048.A32228@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: > > 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. Tx. Turns out a ssh bug tripped me up. I'll put it in /etc/profile, neater then mucking with the skeletons and individual profiles. It's a system thing anyway :). > That's just for MH-style mailboxes. Maybe, but it still makes me nervous . > >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. Tx. I'll skip that var for 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 Sun Jan 21 8:11:23 2001 Delivered-To: freebsd-stable@freebsd.org Received: from anchor-post-33.mail.demon.net (anchor-post-33.mail.demon.net [194.217.242.91]) by hub.freebsd.org (Postfix) with ESMTP id 976D737B401 for ; Sun, 21 Jan 2001 08:11:04 -0800 (PST) Received: from shootthemlater.demon.co.uk ([194.222.93.84] helo=cerebus.parse.net) by anchor-post-33.mail.demon.net with esmtp (Exim 2.12 #1) id 14KN54-000OAz-0X for stable@freebsd.org; Sun, 21 Jan 2001 16:11:02 +0000 Received: from wbra0013.cognos.com ([10.0.0.3] helo=acm.org) by cerebus.parse.net with esmtp (Exim 3.16 #1) id 14KN4f-000Oea-00 for stable@freebsd.org; Sun, 21 Jan 2001 16:10:37 +0000 Message-ID: <3A6B09E2.EA269488@acm.org> Date: Sun, 21 Jan 2001 16:10:10 +0000 From: David Goddard X-Mailer: Mozilla 4.75 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: stable@freebsd.org Subject: dmesg/security check output wierdness Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I've recently noticed some odd entries in my security check output mail from a couple of 4.2-STABLE machines, so I did some digging. The following is one example: [Date: Sun, 21 Jan 2001 03:18:15 +0000] cassium.mydomain.com kernel log messages: > 06 cleared. On one machine (buildworld on 2001-01-18, not rebooted since then) I see: dmg@cassium% ls -la /var/log/dmesg.* -rw-r----- 1 root wheel 12 Jan 21 03:18 /var/log/dmesg.today -rw-r----- 1 root wheel 42 Jan 20 03:13 /var/log/dmesg.yesterday dmg@cassium% dmg@cassium% cat /var/log/dmesg.today 06 cleared. dmg@cassium% dmg@cassium% dmesg dmg@cassium% dmg@cassium% cat /var/log/dmesg.yesterday <118> setup xl0: promiscuous mode enabled dmg@cassium% The 06 cleared bit looks like it is a corruption of an entry that I usually see in /var/log/messages and /var/log/security: Jan 21 13:59:08 cassium /kernel: ipfw: Entry 306 cleared. (I use ipfw for traffic counting) The <118> setup line does not seem to be in /var/log/messages or anywhere else I looked. On another machine (buildworld on 2001-01-14, also not rebooted since then), I get similarly odd content: root@cerebus% ls -la /var/log/dmesg.* -rw-r----- 1 root wheel 1454 Jan 21 03:10 /var/log/dmesg.today -rw-r----- 1 root wheel 3470 Jan 14 03:09 /var/log/dmesg.yesterday root@cerebus% root@cerebus% dmesg scuous mode enabled root@cerebus% root@cerebus% head /var/log/dmesg.today 4 on atapci0 [normal entries snipped] root@cerebus% root@cerebus% grep scuous /var/log/dmesg.today tun0: promiscuous mode enabled ed0: promiscuous mode enabled root@cerebus% root@cerebus% grep scuous /var/log/dmesg.yesterday tun0: promiscuous mode enabled ed0: promiscuous mode enabled root@cerebus% root@cerebus% grep src /etc/security # $FreeBSD: src/etc/security,v 1.36.2.7 2000/10/30 10:40:11 obrien Exp $ Neither system has any old _secure* files hanging around in /var/run/. My assumption is that it is connected to the diff that goes on in /etc/security but I can't see anything obvious to me (although that isn't saying much). I'm hoping that it's not a hardware thing otherwise I have two machines to fix :-) Any ideas? Thanks, Dave To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 21 10: 6:30 2001 Delivered-To: freebsd-stable@freebsd.org Received: from nothing-going-on.demon.co.uk (nothing-going-on.demon.co.uk [193.237.89.66]) by hub.freebsd.org (Postfix) with ESMTP id 759A437B699 for ; Sun, 21 Jan 2001 10:06:08 -0800 (PST) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.11.1/8.11.1) id f0LFJbM10440; Sun, 21 Jan 2001 15:19:37 GMT (envelope-from nik) Date: Sun, 21 Jan 2001 15:19:36 +0000 From: Nik Clayton To: stable@freebsd.org Cc: uwe@ptc.spbu.ru Subject: Re: preventing cvsup from replacing /usr/ports symlink? Message-ID: <20010121151936.A10410@canyon.nothing-going-on.org> References: <200101202028.f0KKSUr80758@saturn.home.ben.com> <20010121021117.A2300@snark.ptc.spbu.ru> <200101210047.f0L0lBq15592@vashon.polstra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200101210047.f0L0lBq15592@vashon.polstra.com>; from jdp@polstra.com on Sat, Jan 20, 2001 at 04:47:11PM -0800 Organization: FreeBSD Project Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Jan 20, 2001 at 04:47:11PM -0800, John Polstra wrote: > 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. It still happens periodically for me, and has done on 3.x, 4.x, and now -current. John, I'd be more than happy to rebuild cvsup with any extra debugging options you'd like to help track this down. N -- Internet connection, $19.95 a month. Computer, $799.95. Modem, $149.95. Telephone line, $24.95 a month. Software, free. USENET transmission, hundreds if not thousands of dollars. Thinking before posting, priceless. Somethings in life you can't buy. For everything else, there's MasterCard. -- Graham Reed, in the Scary Devil Monastery To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 21 11: 0: 5 2001 Delivered-To: freebsd-stable@freebsd.org Received: from albatross-ext.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [194.237.142.116]) by hub.freebsd.org (Postfix) with ESMTP id 9BAE237B400 for ; Sun, 21 Jan 2001 10:59:42 -0800 (PST) Received: from super.du.uab.ericsson.se (super.du.uab.ericsson.se [134.138.176.16]) by albatross.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with ESMTP id f0LIxfC00241 for ; Sun, 21 Jan 2001 19:59:41 +0100 (MET) Received: from news.du.uab.ericsson.se (news [134.138.176.24]) by super.du.uab.ericsson.se (8.10.1/8.10.1/erix-1.8) with ESMTP id f0LIxer05164 for ; Sun, 21 Jan 2001 19:59:40 +0100 (MET) Received: (from news@localhost) by news.du.uab.ericsson.se (8.9.1b+Sun/8.9.1/news-1.1) id TAA27533 for freebsd-stable@freebsd.org; Sun, 21 Jan 2001 19:59:40 +0100 (MET) Received: from GATEWAY by news with netnews for freebsd-stable@freebsd.org (freebsd-stable@freebsd.org) To: freebsd-stable@freebsd.org Date: 21 Jan 2001 19:59:39 +0100 From: Kent Boortz Message-ID: Organization: Ericsson Utvecklings AB, Stockholm, Sweden Content-Type: text/plain; charset=us-ascii Subject: PCI128 and RELENG_4 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have updated my source and built a kernel Jan 17. Tried to record audio with my SoundBlaster 128 PCI (ES1370) but only record noice. It is not a cable problem, I can hear the sound in the speakers (is this normal that the incoming sound is passed to the speaker?). I can play sound files. I didn't try recordning much when running FreeBSD 3.4 but I think it was working. % dmesg | egrep 'STABLE|pcm' FreeBSD 4.2-STABLE #0: Wed Jan 17 22:36:46 CET 2001 pcm0: port 0xd800-0xd83f irq 9 at device 10.0 on pci0 (the IRQ is not shared according to dmesg) % cat /dev/sndstat FreeBSD Audio Driver (newpcm) Jan 17 2001 22:35:59 Installed devices: pcm0: at io 0xd800 irq 9 (1p/1r channels duplex) % grep pcm /sys/i386/conf/MYKERNEL device pcm # PnP/PCI sound cards % mixer Mixer vol is currently set to 75:75 Mixer synth is currently set to 75:75 Mixer pcm is currently set to 75:75 Mixer line is currently set to 75:75 Mixer mic is currently set to 0:0 Mixer cd is currently set to 75:75 Mixer ogain is currently set to 50:50 Mixer line1 is currently set to 75:75 Mixer line2 is currently set to 0:0 Mixer line3 is currently set to 0:0 No error messages in "/var/log/messages" after I try to record. No error message from sox "rec", just recording noise. % rec foo.wav Send break (control-c) to end recording ^C % play foo.wav Do you know if the "AudioPCI ES1370" support is currently broken? If so, is there another cheap or medium cost card I can buy that has good recordning and is supported by 4.2-STABLE? Maybe a better one for recording than SoundBlaster 128 PCI? kent To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 21 11:29:35 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 3118A37B400; Sun, 21 Jan 2001 11:29:12 -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 f0LJT8901098; Sun, 21 Jan 2001 12:29:09 -0700 (MST) (envelope-from imp@harmony.village.org) Message-Id: <200101211929.f0LJT8901098@harmony.village.org> To: "Cameron Grant" Subject: Re: newpcm/kobj MFC Cc: arch@FreeBSD.ORG, stable@FreeBSD.ORG In-reply-to: Your message of "Sat, 20 Jan 2001 23:53:45 GMT." <003401c0833c$39ac3f40$1004020a@darkstar> References: <003401c0833c$39ac3f40$1004020a@darkstar> Date: Sun, 21 Jan 2001 12:29:08 -0700 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <003401c0833c$39ac3f40$1004020a@darkstar> "Cameron Grant" writes: : unless vetoed for good reason, i intend to MFC kobj support into 4.x and Wouldn't the kobj merge break binary compatibility that we're trying to maintain? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 21 11:36:59 2001 Delivered-To: freebsd-stable@freebsd.org Received: from hyperreal.org (taz.hyperreal.org [209.133.83.16]) by hub.freebsd.org (Postfix) with SMTP id F32A637B402 for ; Sun, 21 Jan 2001 11:36:33 -0800 (PST) Received: (qmail 16439 invoked by uid 12); 21 Jan 2001 19:36:33 -0000 Message-ID: <20010121193633.16438.qmail@hyperreal.org> From: mike@hyperreal.org Subject: Re: MAIL set by whom? To: bfischer@Techfak.Uni-Bielefeld.DE Date: Sun, 21 Jan 2001 11:36:33 -0800 (PST) Cc: freebsd-stable@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL60 (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 Someone forwarded me Bjorn's post. > You can set MAIL via /etc/login.conf, all applications that use > either login(1) or setusercontext(3) should work. > > Beware of ssh! The OpenSSH client, that is part of FreeBSD is > completey buggy here: It sets MAIL to /var/mail/$USER, this is > hardcoded. I have a dirty fix, maybe I'll clean it up and > send it as a PR or to Kris (Kris, are you still ssh maintainer?) (FYI) On Jan 11 I posted to the freebsd-questions and openssh-unix-dev lists the following. I received no replies. This is just a workaround, not a solution, really. ----- Forwarded message (env-from mike) ----- From mike Thu Jan 11 20:17:02 2001 Subject: login.conf MAIL environment weirdness solved To: freebsd-questions@freebsd.org Date: Thu, 11 Jan 2001 20:17:02 -0800 (PST) CC: openssh-unix-dev@mindrot.org X-Mailer: ELM [version 2.4ME+ PL60 (25)] Content-Length: 1797 A while back, I posted to the freebsd-questions list about a problem I was having getting custom MAIL environment variable settings in /etc/login.conf to take. Something had happened between FreeBSD 3.3 and 4.2 that caused MAIL to always be set to /var/mail/$USER. It turns out this was a problem with the sshd configuration. The problem was apparently related to the fact OpenSSH's sshd is now configured by default with "UseLogin no", meaning it will not invoke the system's login(1) after authentication. I changed this to "UseLogin yes" and sent a HUP signal to sshd, and all is well; MAIL is now whatever I set it to in /etc/login.conf (and /etc/login.conf.db). The version of OpenSSH that comes with FreeBSD 4.2, if "UseLogin no" is set or is undefined, will seem to process *other* environment variables defined in /etc/login.conf, but always leaves MAIL as the default value which is compiled into sshd. This was very a confusing situation and made the problem difficult to diagnose. More recent snapshots of OpenSSH do not seem to acknowledge environment changes in /etc/login.conf at all, when UseLogin was no. So like I said, the solution was "UseLogin yes" in sshd_config. Now I have some questions: 1. What risks are there in having "UseLogin yes"? 2. Is the current sshd behaving as intended (not doing anything to cause /etc/login.conf.db to be processed at all)? 3. Why was the older version picking up the login.conf environment settings, aside from MAIL, even if "UseLogin no" was set? - Mike ________________________________________________________________________ Mike Brown / Hyperreal | Hyperreal http://music.hyperreal.org/ PO Box 61334 | XML & XSL http://skew.org/xml/ Denver CO 80206-8334 USA | personal http://www.hyperreal.org/~mike/ ----- End of forwarded message (env-from 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 21 12:30: 3 2001 Delivered-To: freebsd-stable@freebsd.org Received: from marius.org (marius.org [216.88.115.170]) by hub.freebsd.org (Postfix) with ESMTP id 4901B37B400 for ; Sun, 21 Jan 2001 12:29:43 -0800 (PST) Received: (from marius@localhost) by marius.org (8.11.0/8.11.0) id f0LKTeU08533 for freebsd-stable@FreeBSD.ORG; Sun, 21 Jan 2001 14:29:40 -0600 (CST) Date: Sun, 21 Jan 2001 14:29:39 -0600 From: Marius Strom To: freebsd-stable@FreeBSD.ORG Subject: Re: your mail Message-ID: <20010121142939.C534@marius.org> Mail-Followup-To: freebsd-stable@FreeBSD.ORG 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 darren@tzeench.dhs.org on Sun, Jan 21, 2001 at 02:35:50AM -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Any console information would probably be most helpful here. On Sun, Jan 21, 2001 at 02:35:50AM -0700, Darren wrote: > alright, I'm not sure if this is a hardware problem that can be helped. > but I wonder if anyone out there is having a similar problem. I have a > maxtor 60 gig drive, whenever it approaches the 30 gig mark... we've never > had a need to store more than that. it starts crashing. my system has > frozen up two times in the last week. with the current incident I was in > telnet over my lan from windows, decompressing a file and using cuteftp to > download a different file. I heard a beep come from the > computer(FreeBSD), and that was it... crashed... had to force a reboot > by manually pressing the button. > > -Darren > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > -- Marius Strom Professional Geek/Unix System Administrator URL: http://www.marius.org/ http://www.marius.org/marius.pgp 0x55DE53E4 "Never underestimate the bandwidth of a mini-van full of DLT tapes traveling down the highway at 65 miles per hour..." -Andrew Tanenbaum, "Computer Networks" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 21 12:49:49 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 86C8137B401 for ; Sun, 21 Jan 2001 12:49:31 -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 f0LKo0X66174 for ; Sun, 21 Jan 2001 21:50:01 +0100 (CET) (envelope-from ohartman@ipamzlx.physik.uni-mainz.de) Date: Sun, 21 Jan 2001 21:50:00 +0100 (CET) From: "O. Hartmann" To: freebsd-stable@freebsd.org Subject: ssh problem 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 Mmmh, well, I do not know whether this is a subject of this forum. Since a couple of days I lost contact to one of our machines, means: I can not login via ssh. I think it has something to do with the last cvsupdate I made (and buildworld afterwards), because I did not chance the configuration and it worked before. I thinks I saw three or five days before some openssh-changes in the source code, so maybe this problem is related to a simple "misconfiguration due a source update. Does anyone have some hints or can report the same problem? 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 Sun Jan 21 12:54:56 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 352F737B400 for ; Sun, 21 Jan 2001 12:54:36 -0800 (PST) Received: by peitho.fxp.org (Postfix, from userid 1501) id 41FDC13614; Sun, 21 Jan 2001 15:54:35 -0500 (EST) Date: Sun, 21 Jan 2001 15:54:35 -0500 From: Chris Faulhaber To: "O. Hartmann" Cc: freebsd-stable@freebsd.org Subject: Re: ssh problem Message-ID: <20010121155435.B66974@peitho.fxp.org> Mail-Followup-To: Chris Faulhaber , "O. Hartmann" , freebsd-stable@freebsd.org 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 ohartman@ipamzlx.physik.uni-mainz.de on Sun, Jan 21, 2001 at 09:50:00PM +0100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jan 21, 2001 at 09:50:00PM +0100, O. Hartmann wrote: > Mmmh, well, I do not know whether this is a subject of this forum. > > Since a couple of days I lost contact to one of our machines, means: > I can not login via ssh. I think it has something to do with the last > cvsupdate I made (and buildworld afterwards), because I did not chance the > configuration and it worked before. > > I thinks I saw three or five days before some openssh-changes in the > source code, so maybe this problem is related to a simple > "misconfiguration due a source update. Does anyone have some hints > or can report the same problem? > /etc/ssh/sshd_config changed due to the OpenSSH MFC. If you did not merge the changes, sshd will not start. -- 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 21 13: 3: 5 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 E1B6A37B400 for ; Sun, 21 Jan 2001 13:02:46 -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 f0LL3EX18459; Sun, 21 Jan 2001 22:03:14 +0100 (CET) (envelope-from ohartman@ipamzlx.physik.uni-mainz.de) Date: Sun, 21 Jan 2001 22:03:14 +0100 (CET) From: "O. Hartmann" To: Chris Faulhaber Cc: freebsd-stable@freebsd.org Subject: Re: ssh problem In-Reply-To: <20010121155435.B66974@peitho.fxp.org> 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, 21 Jan 2001, Chris Faulhaber wrote: Thanks a lot ... These infos passed myself unread. I changed one line and all things worked fine. Thanks ... :>On Sun, Jan 21, 2001 at 09:50:00PM +0100, O. Hartmann wrote: :>> Mmmh, well, I do not know whether this is a subject of this forum. :>> :>> Since a couple of days I lost contact to one of our machines, means: :>> I can not login via ssh. I think it has something to do with the last :>> cvsupdate I made (and buildworld afterwards), because I did not chance the :>> configuration and it worked before. :>> :>> I thinks I saw three or five days before some openssh-changes in the :>> source code, so maybe this problem is related to a simple :>> "misconfiguration due a source update. Does anyone have some hints :>> or can report the same problem? :>> :> :>/etc/ssh/sshd_config changed due to the OpenSSH MFC. If you did not :>merge the changes, sshd will not start. :> :>-- :>Chris D. Faulhaber - jedgar@fxp.org - jedgar@FreeBSD.org :>-------------------------------------------------------- :>FreeBSD: The Power To Serve - http://www.FreeBSD.org :> - 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 Sun Jan 21 13:39:57 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 18BDC37B400 for ; Sun, 21 Jan 2001 13:39:40 -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 f0LLda901980; Sun, 21 Jan 2001 14:39:36 -0700 (MST) (envelope-from imp@harmony.village.org) Message-Id: <200101212139.f0LLda901980@harmony.village.org> To: Forrest Aldrich Subject: Re: Required files for Linux emulation Cc: freebsd-stable@FreeBSD.ORG In-reply-to: Your message of "Sat, 20 Jan 2001 14:09:31 EST." <5.0.0.25.2.20010120140820.02188bd0@216.67.14.69> References: <5.0.0.25.2.20010120140820.02188bd0@216.67.14.69> Date: Sun, 21 Jan 2001 14:39:36 -0700 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <5.0.0.25.2.20010120140820.02188bd0@216.67.14.69> Forrest Aldrich writes: : 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? echo "6.0" > /compat/linux/etc/redhat-release Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 21 13:40:48 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 804EC37B400 for ; Sun, 21 Jan 2001 13:40:31 -0800 (PST) Received: (from bjj@localhost) by saturn.home.ben.com (8.11.1/8.9.3) id f0LLeSF86424; Sun, 21 Jan 2001 13:40:28 -0800 (PST) From: Ben Jackson Message-Id: <200101212140.f0LLeSF86424@saturn.home.ben.com> Subject: Re: PCI128 and RELENG_4 In-Reply-To: from Kent Boortz at "Jan 21, 2001 07:59:39 pm" To: Kent Boortz Date: Sun, 21 Jan 2001 13:40:22 -0800 (PST) Cc: freebsd-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 Hm, I have: pcm0: port 0xd000-0xd03f irq 9 at device 10.0 on pci0 FreeBSD Audio Driver (newpcm) Dec 26 2000 20:17:05 Installed devices: pcm0: at io 0xd000 irq 9 (1p/1r channels duplex) I just tried recording and I can't get anything out of line0 or mic. Also, the sox port is broken... rec doesn't do anything. I also tried record from an OSS dist. I'm assuming: > % mixer > Mixer mic is currently set to 0:0 You are adjusting that if you're using the mic input. I'm also curious to know if you get a hiss from the speakers all the time that goes away if you set the synth volume to 0. That's what happens with my SB PCI128. --Ben To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 21 13:41:51 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 DAC5F37B400 for ; Sun, 21 Jan 2001 13:41:31 -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 f0LLfS902012; Sun, 21 Jan 2001 14:41:29 -0700 (MST) (envelope-from imp@harmony.village.org) Message-Id: <200101212141.f0LLfS902012@harmony.village.org> To: "Shawn Barnhart" Subject: Re: Limit on the number of disklabel entries? Cc: freebsd-stable@FreeBSD.ORG In-reply-to: Your message of "Sat, 20 Jan 2001 11:57:04 CST." <006301c0830a$65959f70$b8209fc0@marlowe> References: <006301c0830a$65959f70$b8209fc0@marlowe> Date: Sun, 21 Jan 2001 14:41:28 -0700 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <006301c0830a$65959f70$b8209fc0@marlowe> "Shawn Barnhart" writes: : Is there a hard limit on the number of disk label entries? Yes. a-h is all you get. On boot disks, a is /, b is swap. On all disks 'c' is the whole disk (too many things break when you ignore this rule). : 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: Nope. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 21 13:49: 6 2001 Delivered-To: freebsd-stable@freebsd.org Received: from epsilon.lucida.ca (epsilon.lucida.ca [216.95.146.6]) by hub.freebsd.org (Postfix) with SMTP id B44C737B401 for ; Sun, 21 Jan 2001 13:48:48 -0800 (PST) Received: (qmail 53501 invoked by uid 1000); 21 Jan 2001 21:48:47 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 21 Jan 2001 21:48:47 -0000 Date: Sun, 21 Jan 2001 16:48:45 -0500 (EST) From: Matt Heckaman To: Warner Losh Cc: Shawn Barnhart , Subject: Re: Limit on the number of disklabel entries? In-Reply-To: <200101212141.f0LLfS902012@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: localhost 1.6.2 0/1000/N Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sun, 21 Jan 2001, Warner Losh wrote: ... : Yes. a-h is all you get. On boot disks, a is /, b is swap. On all : disks 'c' is the whole disk (too many things break when you ignore : this rule). ... Then what, might I ask, is slice "d" for? :) I've always wondered this. Also, "e" is "the whole disk within slice 'c'" on a secondary disk? At least that's what mine defaulted to when i installed a second drive... * Matt Heckaman - mailto:matt@lucida.ca http://www.lucida.ca/pgp * * GPG fingerprint - 53CA 8320 C8F6 32ED 9DDF 036E 3171 C093 4AD3 1364 * -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: http://www.lucida.ca/pgp iD8DBQE6a1k/MXHAk0rTE2QRArynAKCJnKNDO23mYPAav/TL4h5+MONTAwCgyAUP RoRp/ts5eBErI8swOqgnR8o= =oydT -----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 Sun Jan 21 14:12:51 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 DD56237B404 for ; Sun, 21 Jan 2001 14:12:33 -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 f0LMCR902132; Sun, 21 Jan 2001 15:12:28 -0700 (MST) (envelope-from imp@harmony.village.org) Message-Id: <200101212212.f0LMCR902132@harmony.village.org> To: Matt Heckaman Subject: Re: Limit on the number of disklabel entries? Cc: Shawn Barnhart , freebsd-stable@FreeBSD.ORG In-reply-to: Your message of "Sun, 21 Jan 2001 16:48:45 EST." References: Date: Sun, 21 Jan 2001 15:12:27 -0700 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Matt Heckaman writes: : Then what, might I ask, is slice "d" for? :) I've always wondered this. It used to be for the whole whole disk. : Also, "e" is "the whole disk within slice 'c'" on a secondary disk? At : least that's what mine defaulted to when i installed a second drive... No. THat's not right. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 21 14:15: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 883DF37B400 for ; Sun, 21 Jan 2001 14:15: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 OAA00608; Sun, 21 Jan 2001 14:15:24 -0800 (PST) (envelope-from jessem@spammie.svbug.com) Message-Id: <200101212215.OAA00608@spammie.svbug.com> Date: Sun, 21 Jan 2001 14:15:23 -0800 (PST) From: opentrax@email.com Reply-To: opentrax@email.com Subject: Re: OOPS.. (Re: MFC? src/sys/i386/conf/GENERIC and sound support) To: keichii@peorth.iteration.net Cc: freebsd-stable@FreeBSD.ORG In-Reply-To: <20010115160930.A59752@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 I like mine red. On 15 Jan, Michael C . Wu wrote: > Can we please stop this bikeshed? > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 21 14:16:10 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 99E8037B402 for ; Sun, 21 Jan 2001 14:15:52 -0800 (PST) Received: from localhost (darren@localhost) by tzeench.dhs.org (8.11.1/8.11.1) with ESMTP id f0LMFws00906 for ; Sun, 21 Jan 2001 15:15:58 -0700 (MST) (envelope-from darren@tzeench.dhs.org) Date: Sun, 21 Jan 2001 15:15:57 -0700 (MST) From: Darren To: Subject: Re: your mail 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 alright, to satisfy the question earlier, there wasn't any console information, the moniter was in sleep mode and wouldn't wake from it. second I went out and purchased a controller card(Hot Rod 66) which does support my harddrive(or drives up to 128 gigs). I am using the ata66 cables. the chipset is "HPT366 Ultra DMA66 IDE Controller". It's a pci bus card. this controller seems to work fine with my maxtor 13gig drive. Just occasionally panics on my maxtor 60 gig drive. I have an asus p5a motherboard I suppose this about solves my problem, I don't get the use of the ata66 mode, I just felt I would make these additional comments for anyone who was following the conversation -Darren On Sun, 21 Jan 2001, Adam wrote: > You didnt mention anything about what motherboard, ide controller, and > cables you are using.. If you are using one of the new 80 pin ide cables > I would suggest trying it on a normal 40 pin cable as that forces it to > ata33 mode which seems to be stable for me. I have a HPT366 ide > controller and it doesnt seem to like the various drives I've tried on it > with an ata66 cable. I own a maxtor 80g and it blew chunks until I > changed the cable. > > On Sun, 21 Jan 2001, Darren wrote: > > >alright, I'm not sure if this is a hardware problem that can be helped. > >but I wonder if anyone out there is having a similar problem. I have a > >maxtor 60 gig drive, whenever it approaches the 30 gig mark... we've never > >had a need to store more than that. it starts crashing. my system has > >frozen up two times in the last week. with the current incident I was in > >telnet over my lan from windows, decompressing a file and using cuteftp to > >download a different file. I heard a beep come from the > >computer(FreeBSD), and that was it... crashed... had to force a reboot > >by manually pressing the button. > > > >-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 Sun Jan 21 14:18:12 2001 Delivered-To: freebsd-stable@freebsd.org Received: from penguin-ext.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [194.237.142.110]) by hub.freebsd.org (Postfix) with ESMTP id D9A3437B698 for ; Sun, 21 Jan 2001 14:17:50 -0800 (PST) Received: from super.du.uab.ericsson.se (super.du.uab.ericsson.se [134.138.176.16]) by penguin.wise.edt.ericsson.se (8.11.0/8.10.1/WIREfire-1.3) with ESMTP id f0LMHnd04436 for ; Sun, 21 Jan 2001 23:17:49 +0100 (MET) Received: from news.du.uab.ericsson.se (news [134.138.176.24]) by super.du.uab.ericsson.se (8.10.1/8.10.1/erix-1.8) with ESMTP id f0LMHmr12110 for ; Sun, 21 Jan 2001 23:17:48 +0100 (MET) Received: (from news@localhost) by news.du.uab.ericsson.se (8.9.1b+Sun/8.9.1/news-1.1) id XAA01665 for freebsd-stable@freebsd.org; Sun, 21 Jan 2001 23:17:48 +0100 (MET) Received: from GATEWAY by news with netnews for freebsd-stable@freebsd.org (freebsd-stable@freebsd.org) To: freebsd-stable@freebsd.org Date: 21 Jan 2001 23:17:45 +0100 From: Kent Boortz Message-ID: Organization: Ericsson Utvecklings AB, Stockholm, Sweden Content-Type: text/plain; charset=us-ascii References: , <200101212140.f0LLeSF86424@saturn.home.ben.com> Subject: Re: PCI128 and RELENG_4 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ben@ben.com (Ben Jackson) writes: > I just tried recording and I can't get anything out of line0 or mic. > Also, the sox port is broken... rec doesn't do anything. I also tried > record from an OSS dist. Do you mean you could record with another program, which one? > > % mixer > > Mixer mic is currently set to 0:0 > > You are adjusting that if you're using the mic input. I tried with "mixer mic 50:50", it made no difference. > I'm also curious to know if you get a hiss from the speakers all the time > that goes away if you set the synth volume to 0. That's what happens > with my SB PCI128. Yes, when I increase the volume I can hear it. Very different from the smooth noise I hear when recording, a high frequency noise that vary. kent To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 21 14:24:52 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 769B837B402; Sun, 21 Jan 2001 14:24: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 OAA00615; Sun, 21 Jan 2001 14:24:13 -0800 (PST) (envelope-from jessem@spammie.svbug.com) Message-Id: <200101212224.OAA00615@spammie.svbug.com> Date: Sun, 21 Jan 2001 14:24:12 -0800 (PST) From: opentrax@email.com Reply-To: opentrax@email.com Subject: Re: OOPS.. (Re: MFC? src/sys/i386/conf/GENERIC and sound support To: jhb@FreeBSD.ORG Cc: freebsd-stable@FreeBSD.ORG, roman@harmonic.co.il, keichii@peorth.iteration.net In-Reply-To: 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, John Baldwin wrote: > > On 15-Jan-01 opentrax@email.com wrote: >> 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. > Hardly, we use the sound drivers that come with FreeBSD As a matter of fact, we contributed back when we needed a fix to the sound driver. BTW, your good luck does not translate to good luck by others. We have been able to get sound cards to work the first time out, but we'd had enough that have not to know better. >>> >> 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. > Yes, thank you for that corrections. If memory servers me well, LKM is Novell (ala Kernel Loadable Module). Thanks again for that correction. Jessem. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 21 14:29:29 2001 Delivered-To: freebsd-stable@freebsd.org Received: from epsilon.lucida.ca (epsilon.lucida.ca [216.95.146.6]) by hub.freebsd.org (Postfix) with SMTP id 7264637B699 for ; Sun, 21 Jan 2001 14:29:11 -0800 (PST) Received: (qmail 53659 invoked by uid 1000); 21 Jan 2001 22:29:10 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 21 Jan 2001 22:29:10 -0000 Date: Sun, 21 Jan 2001 17:29:09 -0500 (EST) From: Matt Heckaman To: Warner Losh Cc: Shawn Barnhart , Subject: Re: Limit on the number of disklabel entries? In-Reply-To: <200101212212.f0LMCR902132@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: localhost 1.6.2 0/1000/N Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sun, 21 Jan 2001, Warner Losh wrote: ... : It used to be for the whole whole disk. Ahh.. : : Also, "e" is "the whole disk within slice 'c'" on a secondary disk? At : : least that's what mine defaulted to when i installed a second drive... : : No. THat's not right. According to sysinstall it is: Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/da0s1a 254063 29232 219750 12% / /dev/da0s1e 254063 3001 245981 1% /var /dev/da0s1f 7085237 2788656 4154877 40% /usr /dev/da1s1e 17376099 8328598 8699980 49% /misc procfs 4 4 0 100% /proc Brand new system, installed 3 days ago, 4.2-RELEASE. Creating the partition on the newly sliced da1 via sysinstall put it on "e". * Matt Heckaman - mailto:matt@lucida.ca http://www.lucida.ca/pgp * * GPG fingerprint - 53CA 8320 C8F6 32ED 9DDF 036E 3171 C093 4AD3 1364 * -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: http://www.lucida.ca/pgp iD8DBQE6a2K2MXHAk0rTE2QRAnBAAJ4smf934Benz4igCymq4ClnR/iKbQCgk0Gc 5JBRxVyF65OTLKLvgXKng+M= =UcZR -----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 Sun Jan 21 14:33:46 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 17E7137B401 for ; Sun, 21 Jan 2001 14:33:27 -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); Sun, 21 Jan 2001 14:31:35 -0800 Received: (from cjc@localhost) by rfx-216-196-73-168.users.reflexcom.com (8.11.1/8.11.0) id f0LMXOR31232; Sun, 21 Jan 2001 14:33:24 -0800 (PST) (envelope-from cjc) Date: Sun, 21 Jan 2001 14:33:24 -0800 From: "Crist J. Clark" To: David Goddard Cc: stable@FreeBSD.ORG Subject: Re: dmesg/security check output wierdness Message-ID: <20010121143324.U10761@rfx-216-196-73-168.users.reflex> Reply-To: cjclark@alum.mit.edu References: <3A6B09E2.EA269488@acm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <3A6B09E2.EA269488@acm.org>; from goddard@acm.org on Sun, Jan 21, 2001 at 04:10:10PM +0000 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jan 21, 2001 at 04:10:10PM +0000, David Goddard wrote: > I've recently noticed some odd entries in my security check output mail > from a couple of 4.2-STABLE machines, so I did some digging. The > following is one example: > > [Date: Sun, 21 Jan 2001 03:18:15 +0000] > cassium.mydomain.com kernel log messages: > > 06 cleared. [snip] > Any ideas? The dmesg(8) is stored in a finite buffer. Once full, as more stuff gets shoved in, other stuff falls out (really it gets overwritten, it's a circular buffer, but same thing). The stuff that falls out, does not do so all that gracefully. That is, it does not get dropped whole lines at a time. For example, $ dmesg | head -5 0.1.35:427 in via de0 ipfw: 11500 Deny UDP AAA.BBB.153.173:137 AAA.BBB.153.255:137 in via de0 ipfw: 11500 Deny UDP AAA.BBB.153.173:137 AAA.BBB.153.255:137 in via de0 ipfw: 11500 Deny UDP AAA.BBB.153.173:137 AAA.BBB.153.255:137 in via de0 ipfw: 11500 Deny UDP AAA.BBB.153.173:427 224.0.1.35:427 in via de0 Notice the first line. Now, I do something to make a little noise in the dmesg buffer and check again, $ dmesg | head -5 .255:137 in via de0 ipfw: 11500 Deny UDP AAA.BBB.153.173:137 AAA.BBB.153.255:137 in via de0 ipfw: 11500 Deny UDP AAA.BBB.153.173:137 AAA.BBB.153.255:137 in via de0 ipfw: 11500 Deny UDP AAA.BBB.153.173:427 224.0.1.35:427 in via de0 ipfw: 11500 Deny ICMP:10.0 AAA.BBB.153.173 224.0.0.2 in via de0 Now, as for the '10>' or similar constructions you sometimes see popping up on the first line. Have a look at, $ sysctl machdep.msgbuf dmesg(8) strips the leading off of the lines when printing it for you. But if one of these is cut in the middle... You get the picture. -- 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 21 14:35:44 2001 Delivered-To: freebsd-stable@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 7901B37B401 for ; Sun, 21 Jan 2001 14:35:23 -0800 (PST) Received: from billy-club.village.org (billy-club.village.org [10.0.0.3]) by rover.village.org (8.11.1/8.11.0) with ESMTP id f0LMZMs01070; Sun, 21 Jan 2001 15:35:22 -0700 (MST) (envelope-from imp@billy-club.village.org) Received: from billy-club.village.org (localhost [127.0.0.1]) by billy-club.village.org (8.11.1/8.8.3) with ESMTP id f0LMXVs03655; Sun, 21 Jan 2001 15:33:31 -0700 (MST) Message-Id: <200101212233.f0LMXVs03655@billy-club.village.org> To: Matt Heckaman Subject: Re: Limit on the number of disklabel entries? Cc: Shawn Barnhart , freebsd-stable@FreeBSD.ORG In-reply-to: Your message of "Sun, 21 Jan 2001 17:29:09 EST." References: Date: Sun, 21 Jan 2001 15:33:31 -0700 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Matt Heckaman writes: : Brand new system, installed 3 days ago, 4.2-RELEASE. Creating the : partition on the newly sliced da1 via sysinstall put it on "e". 'e' is the first slice that sysinstall uses. Since you wanted the whole disk, it gave you the whole disk as 'e'. Nothing magical about it. 'c' being the whole disk *IS* magical. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 21 14:37:17 2001 Delivered-To: freebsd-stable@freebsd.org Received: from green.dyndns.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id B9BA437B404; Sun, 21 Jan 2001 14:36:50 -0800 (PST) Received: from localhost (3ysk8l@localhost [127.0.0.1]) by green.dyndns.org (8.11.1/8.11.1) with ESMTP id f0LMajc09302; Sun, 21 Jan 2001 17:36:47 -0500 (EST) (envelope-from green@FreeBSD.org) Message-Id: <200101212236.f0LMajc09302@green.dyndns.org> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Warner Losh Cc: "Cameron Grant" , arch@FreeBSD.org, stable@FreeBSD.org Subject: Re: newpcm/kobj MFC In-Reply-To: Message from Warner Losh of "Sun, 21 Jan 2001 12:29:08 MST." <200101211929.f0LJT8901098@harmony.village.org> From: "Brian F. Feldman" Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 21 Jan 2001 17:36:44 -0500 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Warner Losh wrote: > In message <003401c0833c$39ac3f40$1004020a@darkstar> "Cameron Grant" writes: > : unless vetoed for good reason, i intend to MFC kobj support into 4.x and > > Wouldn't the kobj merge break binary compatibility that we're trying > to maintain? And then make it so that binary compatibility will be preserved between 5.0 and 4.X for newpcm modules? (at least until the driver is properly locked ...) -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / green@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 21 14:39:40 2001 Delivered-To: freebsd-stable@freebsd.org Received: from epsilon.lucida.ca (epsilon.lucida.ca [216.95.146.6]) by hub.freebsd.org (Postfix) with SMTP id 7A2F637B402 for ; Sun, 21 Jan 2001 14:39:23 -0800 (PST) Received: (qmail 53718 invoked by uid 1000); 21 Jan 2001 22:39:22 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 21 Jan 2001 22:39:22 -0000 Date: Sun, 21 Jan 2001 17:39:21 -0500 (EST) From: Matt Heckaman To: Warner Losh Cc: Shawn Barnhart , Subject: Re: Limit on the number of disklabel entries? In-Reply-To: <200101212233.f0LMXVs03655@billy-club.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: localhost 1.6.2 0/1000/N Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sun, 21 Jan 2001, Warner Losh wrote: ... : 'e' is the first slice that sysinstall uses. Since you wanted the : whole disk, it gave you the whole disk as 'e'. Nothing magical about : it. 'c' being the whole disk *IS* magical. In other words, I misunderstood the whole thing. :) Thanks for the clarification Warner, bare with me. Almost scary to think it's now a bit over 2 years I've been using FreeBSD and I'm still discovering these little things. I love it, never gets boring. * Matt Heckaman - mailto:matt@lucida.ca http://www.lucida.ca/pgp * * GPG fingerprint - 53CA 8320 C8F6 32ED 9DDF 036E 3171 C093 4AD3 1364 * -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: http://www.lucida.ca/pgp iD8DBQE6a2UaMXHAk0rTE2QRAlXNAJ98BQS6EVGF1tUJiuvUA9h+hpHsNgCfTX4O yYSGaQ5a8uRcp6l2cltE3a4= =mUHL -----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 Sun Jan 21 14:47:40 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 0827E37B401 for ; Sun, 21 Jan 2001 14:47:22 -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); Sun, 21 Jan 2001 14:45:32 -0800 Received: (from cjc@localhost) by rfx-216-196-73-168.users.reflexcom.com (8.11.1/8.11.0) id f0LMlMK31344; Sun, 21 Jan 2001 14:47:22 -0800 (PST) (envelope-from cjc) Date: Sun, 21 Jan 2001 14:47:22 -0800 From: "Crist J. Clark" To: Matt Heckaman Cc: Warner Losh , Shawn Barnhart , freebsd-stable@FreeBSD.ORG Subject: Re: Limit on the number of disklabel entries? Message-ID: <20010121144722.V10761@rfx-216-196-73-168.users.reflex> Reply-To: cjclark@alum.mit.edu References: <200101212212.f0LMCR902132@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from matt@LUCIDA.CA on Sun, Jan 21, 2001 at 05:29:09PM -0500 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jan 21, 2001 at 05:29:09PM -0500, Matt Heckaman wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Sun, 21 Jan 2001, Warner Losh wrote: > ... > : It used to be for the whole whole disk. > > Ahh.. > > : : Also, "e" is "the whole disk within slice 'c'" on a secondary disk? At > : : least that's what mine defaulted to when i installed a second drive... > : > : No. THat's not right. > > According to sysinstall it is: > > Filesystem 1K-blocks Used Avail Capacity Mounted on > /dev/da0s1a 254063 29232 219750 12% / > /dev/da0s1e 254063 3001 245981 1% /var > /dev/da0s1f 7085237 2788656 4154877 40% /usr > /dev/da1s1e 17376099 8328598 8699980 49% /misc > procfs 4 4 0 100% /proc > > Brand new system, installed 3 days ago, 4.2-RELEASE. Creating the > partition on the newly sliced da1 via sysinstall put it on "e". $ disklabel da1s1 I believe sysinstall(8) starts lettering any non-root partions you add to a disk at 'e.' If you had made two partitions to cut up da1s1, they would have been e and f. I started to look at the code to double-check... but then I came to my senses. -- 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 21 15: 5:47 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 32BFB37B402 for ; Sun, 21 Jan 2001 15:05:30 -0800 (PST) Received: (from kris@localhost) by citusc17.usc.edu (8.11.1/8.11.1) id f0LN60I74300; Sun, 21 Jan 2001 15:06:00 -0800 (PST) (envelope-from kris) Date: Sun, 21 Jan 2001 15:06:00 -0800 From: Kris Kennaway To: "O. Hartmann" Cc: freebsd-stable@FreeBSD.ORG Subject: Re: ssh problem Message-ID: <20010121150600.D73989@citusc17.usc.edu> References: <20010121155435.B66974@peitho.fxp.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="HWvPVVuAAfuRc6SZ" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from ohartman@ipamzlx.physik.uni-mainz.de on Sun, Jan 21, 2001 at 10:03:14PM +0100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --HWvPVVuAAfuRc6SZ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Jan 21, 2001 at 10:03:14PM +0100, O. Hartmann wrote: > On Sun, 21 Jan 2001, Chris Faulhaber wrote: > Thanks a lot ... > These infos passed myself unread. I changed one line and all > things worked fine. That's why you need to get into the habit of doing a mergemaster with every world you build :-) Kris --=20 NOTE: To fetch an updated copy of my GPG key which has not expired, finger kris@FreeBSD.org --HWvPVVuAAfuRc6SZ 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 iD8DBQE6a2tYWry0BWjoQKURAkFsAKCPObuNvAJwZ6GcJ5fylxqECqBRTACgkIlh VQBrqf/xi0JsYDj3ha6wCBw= =b8ZP -----END PGP SIGNATURE----- --HWvPVVuAAfuRc6SZ-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 21 15:10:19 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 3EA0137B400; Sun, 21 Jan 2001 15:10:01 -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 f0LNAfN00702; Mon, 22 Jan 2001 00:10:41 +0100 (CET) (envelope-from ohartman@ipamzlx.physik.uni-mainz.de) Date: Mon, 22 Jan 2001 00:10:41 +0100 (CET) From: "O. Hartmann" To: Kris Kennaway Cc: freebsd-stable@FreeBSD.ORG Subject: Re: ssh problem In-Reply-To: <20010121150600.D73989@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 Sun, 21 Jan 2001, Kris Kennaway wrote: But changes mergemaster not all the opther stuff we figured out and set up? :>On Sun, Jan 21, 2001 at 10:03:14PM +0100, O. Hartmann wrote: :>> On Sun, 21 Jan 2001, Chris Faulhaber wrote: :>> Thanks a lot ... :>> These infos passed myself unread. I changed one line and all :>> things worked fine. :> :>That's why you need to get into the habit of doing a mergemaster with :>every world you build :-) :> :>Kris :> :>-- :>NOTE: To fetch an updated copy of my GPG key which has not expired, :>finger kris@FreeBSD.org :> - 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 Sun Jan 21 15:22:34 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 0836337B400; Sun, 21 Jan 2001 15:22:17 -0800 (PST) Received: (from kris@localhost) by citusc17.usc.edu (8.11.1/8.11.1) id f0LNMlY74561; Sun, 21 Jan 2001 15:22:47 -0800 (PST) (envelope-from kris) Date: Sun, 21 Jan 2001 15:22:47 -0800 From: Kris Kennaway To: "O. Hartmann" Cc: Kris Kennaway , freebsd-stable@FreeBSD.ORG Subject: Re: ssh problem Message-ID: <20010121152247.A74407@citusc17.usc.edu> References: <20010121150600.D73989@citusc17.usc.edu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="xHFwDpU9dbj6ez1V" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from ohartman@ipamzlx.physik.uni-mainz.de on Mon, Jan 22, 2001 at 12:10:41AM +0100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --xHFwDpU9dbj6ez1V Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Jan 22, 2001 at 12:10:41AM +0100, O. Hartmann wrote: > On Sun, 21 Jan 2001, Kris Kennaway wrote: > But changes mergemaster not all the opther stuff we figured out and > set up? Only if you use it wrong :-) Kris --=20 NOTE: To fetch an updated copy of my GPG key which has not expired, finger kris@FreeBSD.org --xHFwDpU9dbj6ez1V 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 iD8DBQE6a29HWry0BWjoQKURAnUBAJ9rSvR4MNzrrs63hVg1bZfoHL7b0QCgiUtv mSzOQQ3lU7+zsGu9qoBBK44= =hb/+ -----END PGP SIGNATURE----- --xHFwDpU9dbj6ez1V-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 21 15:28:30 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 57DE437B698 for ; Sun, 21 Jan 2001 15:28:12 -0800 (PST) From: "Robert Banniza" To: Subject: RE: ssh problem Date: Sun, 21 Jan 2001 17:28:36 -0800 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit In-Reply-To: <20010121152247.A74407@citusc17.usc.edu> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This brings me to a stupid question. It is better to install the new file when cvsup'ing or merge the old and new file together? This is assuming the user hasn't entered anything special into the file. I did an install on the last cvsup rather than merging. I was somewhat confused when it asked me whether I wanted to install the file on the right or the file on the left. Shouldn't they be one in the same if merged? Any info. appreciated... Robert -----Original Message----- From: owner-freebsd-stable@FreeBSD.ORG [mailto:owner-freebsd-stable@FreeBSD.ORG]On Behalf Of Kris Kennaway Sent: Sunday, January 21, 2001 3:23 PM To: O. Hartmann Cc: Kris Kennaway; freebsd-stable@FreeBSD.ORG Subject: Re: ssh problem On Mon, Jan 22, 2001 at 12:10:41AM +0100, O. Hartmann wrote: > On Sun, 21 Jan 2001, Kris Kennaway wrote: > But changes mergemaster not all the opther stuff we figured out and > set up? Only if you use it wrong :-) Kris -- NOTE: To fetch an updated copy of my GPG key which has not expired, finger kris@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 21 15:36:25 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 7773837B401; Sun, 21 Jan 2001 15:36:03 -0800 (PST) Received: (from kris@localhost) by citusc17.usc.edu (8.11.1/8.11.1) id f0LNd4374894; Sun, 21 Jan 2001 15:39:04 -0800 (PST) (envelope-from kris) Date: Sun, 21 Jan 2001 15:39:04 -0800 From: Kris Kennaway To: Cameron Grant Cc: arch@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: newpcm/kobj MFC Message-ID: <20010121153904.B74751@citusc17.usc.edu> References: <003401c0833c$39ac3f40$1004020a@darkstar> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="4SFOXa2GPu3tIq4H" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <003401c0833c$39ac3f40$1004020a@darkstar>; from gandalf@vilnya.demon.co.uk on Sat, Jan 20, 2001 at 11:53:45PM -0000 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --4SFOXa2GPu3tIq4H Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Jan 20, 2001 at 11:53:45PM -0000, Cameron Grant wrote: > this is a followup to my proposal some weeks ago which recieved no releva= nt > commentary. I'm also concerned about breaking binary compatibility. I understand your reasons for wanting this, but we really shouldn't be breaking binary compatibility in -stable. If we keep doing this then no third party vendor is going to want to support drivers that they have to update every few months. Kris --=20 NOTE: To fetch an updated copy of my GPG key which has not expired, finger kris@FreeBSD.org --4SFOXa2GPu3tIq4H 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 iD8DBQE6a3MYWry0BWjoQKURAs94AJ9mI543CvOBhCKTNx/CTUwufLqq+wCeLrki bxG3aijkA0rY3WLTtZ8040o= =8Ays -----END PGP SIGNATURE----- --4SFOXa2GPu3tIq4H-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 21 15:57: 4 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 6F34037B400 for ; Sun, 21 Jan 2001 15:56:46 -0800 (PST) Received: by tao.org.uk (Postfix, from userid 100) id 857253256; Sun, 21 Jan 2001 23:56:44 +0000 (GMT) Date: Sun, 21 Jan 2001 23:56:44 +0000 From: Josef Karthauser To: Warner Losh Cc: Matt Heckaman , Shawn Barnhart , freebsd-stable@FreeBSD.ORG Subject: Re: Limit on the number of disklabel entries? Message-ID: <20010121235644.A29517@tao.org.uk> Mail-Followup-To: Josef Karthauser , Warner Losh , Matt Heckaman , Shawn Barnhart , freebsd-stable@FreeBSD.ORG References: <200101212233.f0LMXVs03655@billy-club.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200101212233.f0LMXVs03655@billy-club.village.org>; from imp@village.org on Sun, Jan 21, 2001 at 03:33:31PM -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jan 21, 2001 at 03:33:31PM -0700, Warner Losh wrote: > In message Matt Heckaman writes: > : Brand new system, installed 3 days ago, 4.2-RELEASE. Creating the > : partition on the newly sliced da1 via sysinstall put it on "e". > > 'e' is the first slice that sysinstall uses. Since you wanted the > whole disk, it gave you the whole disk as 'e'. Nothing magical about > it. 'c' being the whole disk *IS* magical. Does 'c' include the disklabel itself, and the boot blocks? Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 21 16: 4: 9 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mailhost.kal.ameritech.net (mpdr0.kalamazoo.mi.ameritech.net [206.141.239.30]) by hub.freebsd.org (Postfix) with ESMTP id 3D52437B404 for ; Sun, 21 Jan 2001 16:03:51 -0800 (PST) Received: from pfinkler ([209.18.15.152]) by mailhost.kal.ameritech.net (InterMail v4.01.01.07 201-229-111-110) with SMTP id <20010122000350.MCVE19678.mailhost.kal.ameritech.net@pfinkler> for ; Sun, 21 Jan 2001 19:03:50 -0500 Message-ID: <002801c08407$290058e0$980f12d1@pfinkler> From: "Phil Finkler" To: Subject: subscribe Date: Sun, 21 Jan 2001 19:06:25 -0500 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0025_01C083DD.3FEECE80" 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_0025_01C083DD.3FEECE80 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable ------=_NextPart_000_0025_01C083DD.3FEECE80 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
 
------=_NextPart_000_0025_01C083DD.3FEECE80-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 21 17: 1:12 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 5EDD837B400 for ; Sun, 21 Jan 2001 17:00:55 -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 f0M10h903000; Sun, 21 Jan 2001 18:00:48 -0700 (MST) (envelope-from imp@harmony.village.org) Message-Id: <200101220100.f0M10h903000@harmony.village.org> To: Josef Karthauser Subject: Re: Limit on the number of disklabel entries? Cc: Matt Heckaman , Shawn Barnhart , freebsd-stable@FreeBSD.ORG In-reply-to: Your message of "Sun, 21 Jan 2001 23:56:44 GMT." <20010121235644.A29517@tao.org.uk> References: <20010121235644.A29517@tao.org.uk> <200101212233.f0LMXVs03655@billy-club.village.org> Date: Sun, 21 Jan 2001 18:00:43 -0700 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20010121235644.A29517@tao.org.uk> Josef Karthauser writes: : Does 'c' include the disklabel itself, and the boot blocks? 'c' is the entire slice. So yes it includes the disklabel and boot[12]. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 21 17: 4:24 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 8C56B37B400; Sun, 21 Jan 2001 17:04:03 -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 f0M142O04580; Sun, 21 Jan 2001 20:04:02 -0500 (EST) (envelope-from louie@whizzo.transsys.com) Message-Id: <200101220104.f0M142O04580@whizzo.transsys.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Kris Kennaway Cc: Cameron Grant , arch@FreeBSD.ORG, stable@FreeBSD.ORG X-Image-URL: http://www.transsys.com/louie/images/louie-mail.jpg From: "Louis A. Mamakos" Subject: Re: newpcm/kobj MFC References: <003401c0833c$39ac3f40$1004020a@darkstar> <20010121153904.B74751@citusc17.usc.edu> In-reply-to: Your message of "Sun, 21 Jan 2001 15:39:04 PST." <20010121153904.B74751@citusc17.usc.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 21 Jan 2001 20:04:02 -0500 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Sat, Jan 20, 2001 at 11:53:45PM -0000, Cameron Grant wrote: > > this is a followup to my proposal some weeks ago which recieved no relevant > > commentary. > > I'm also concerned about breaking binary compatibility. I understand > your reasons for wanting this, but we really shouldn't be breaking > binary compatibility in -stable. If we keep doing this then no third > party vendor is going to want to support drivers that they have to > update every few months. My concern as a "user" is that we continue to have maintained sound drivers in RELENG_4. My impression is that it will be a while before CURRENT is working well enough for the great unwashed masses to use, perhaps longer than usual for a new major version release. It would be useful perhaps to gauge the actual impact of this incompatability (how many people are using 3rd party sound driver?) before making a decision. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 21 17:11:36 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 DA77237B401; Sun, 21 Jan 2001 17:11:14 -0800 (PST) Received: from darkstar (darkstar.rings [10.2.4.16]) by vilnya.demon.co.uk (Postfix) with SMTP id B603CD9B8; Mon, 22 Jan 2001 01:11:12 +0000 (GMT) Message-ID: <001b01c0840f$b30ea070$1004020a@darkstar> From: "Cameron Grant" To: "Kris Kennaway" , "Louis A. Mamakos" Cc: , References: <003401c0833c$39ac3f40$1004020a@darkstar> <20010121153904.B74751@citusc17.usc.edu> <200101220104.f0M142O04580@whizzo.transsys.com> Subject: Re: newpcm/kobj MFC Date: Mon, 22 Jan 2001 01:07:32 -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 > > On Sat, Jan 20, 2001 at 11:53:45PM -0000, Cameron Grant wrote: > > > this is a followup to my proposal some weeks ago which recieved no relevant > > > commentary. > > I'm also concerned about breaking binary compatibility. I understand > > your reasons for wanting this, but we really shouldn't be breaking > > binary compatibility in -stable. If we keep doing this then no third > > party vendor is going to want to support drivers that they have to > > update every few months. > It would be useful perhaps to gauge the actual impact of this > incompatability (how many people are using 3rd party sound driver?) > before making a decision. to the best of my knowledge, there exist 5 drivers not in the tree now, all of which have kobjified versions available and 4 of which will be entering the tree soon. i know of no commercial newpcm drivers. -cg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 21 17:39:24 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 2786437B400; Sun, 21 Jan 2001 17:39:04 -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 f0M1d1O05133; Sun, 21 Jan 2001 20:39:01 -0500 (EST) (envelope-from louie@whizzo.transsys.com) Message-Id: <200101220139.f0M1d1O05133@whizzo.transsys.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: "Cameron Grant" Cc: "Kris Kennaway" , arch@FreeBSD.ORG, stable@FreeBSD.ORG X-Image-URL: http://www.transsys.com/louie/images/louie-mail.jpg From: "Louis A. Mamakos" Subject: Re: newpcm/kobj MFC References: <003401c0833c$39ac3f40$1004020a@darkstar> <20010121153904.B74751@citusc17.usc.edu> <200101220104.f0M142O04580@whizzo.transsys.com> <001b01c0840f$b30ea070$1004020a@darkstar> In-reply-to: Your message of "Mon, 22 Jan 2001 01:07:32 GMT." <001b01c0840f$b30ea070$1004020a@darkstar> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 21 Jan 2001 20:39:01 -0500 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > On Sat, Jan 20, 2001 at 11:53:45PM -0000, Cameron Grant wrote: > > > > this is a followup to my proposal some weeks ago which recieved no > relevant > > > > commentary. > > > I'm also concerned about breaking binary compatibility. I understand > > > your reasons for wanting this, but we really shouldn't be breaking > > > binary compatibility in -stable. If we keep doing this then no third > > > party vendor is going to want to support drivers that they have to > > > update every few months. > > It would be useful perhaps to gauge the actual impact of this > > incompatability (how many people are using 3rd party sound driver?) > > before making a decision. > > to the best of my knowledge, there exist 5 drivers not in the tree now, all > of which have kobjified versions available and 4 of which will be entering > the tree soon. i know of no commercial newpcm drivers. Well, there you go. Is changing an unused API an incompatability? 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 21 17:52:30 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 9C5CA37B400 for ; Sun, 21 Jan 2001 17:52:12 -0800 (PST) Received: by wantadilla.lemis.com (Postfix, from userid 1004) id AEAC46AC18; Mon, 22 Jan 2001 12:22:09 +1030 (CST) Date: Mon, 22 Jan 2001 12:22:09 +1030 From: Greg Lehey To: FreeBSD Stable Users Subject: Reproducible panic out of fr_makefrip Message-ID: <20010122122209.J3066@wantadilla.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i 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 I've been getting a reproducible panic at startup time with a -STABLE kernel built about 22 December: #15 0xc031eaa3 in trap (frame={tf_fs = 16, tf_es = 16, tf_ds = 16, tf_edi = -1060565020, tf_esi = 0, tf_ebp = -1070002640, tf_isp = -1070002716, tf_ebx = 0, tf_edx = -1070002592, tf_ecx = -1070002596, tf_eax = 961034024, tf_trapno = 12, tf_err = 0, tf_eip = -1071589251, tf_cs = 8, tf_eflags = 66118, tf_esp = 10240, tf_ss = 2928}) at ../../i386/i386/trap.c:443 #16 0xc020d87d in fr_makefrip (hlen=20, ip=0xc0c90fe4, fin=0xc0390e5c) at ../../netinet/fil.c:258 #17 0xc02138cc in fr_checkicmpmatchingstate (ip=0xc0c90fc8, fin=0xc0390f6c) at ../../netinet/ip_state.c:1081 #18 0xc0213b0d in fr_checkstate (ip=0xc0c90fc8, fin=0xc0390f6c) at ../../netinet/ip_state.c:1194 #19 0xc020e46c in fr_check (ip=0xc0c90fc8, hlen=20, ifp=0xc126d600, out=1, mp=0xc0391028) at ../../netinet/fil.c:887 #20 0xc02023cc in ip_output (m0=0xc0c90f00, opt=0x0, ro=0xc0391068, flags=0, imo=0x0) at ../../netinet/ip_output.c:437 #21 0xc020062e in icmp_send (m=0xc0c90f00, opts=0x0) at ../../netinet/ip_icmp.c:753 #22 0xc02005af in icmp_reflect (m=0xc0c90f00) at ../../netinet/ip_icmp.c:715 #23 0xc01ffeb9 in icmp_error (n=0xc0c8f000, type=3, code=1, dest=0, destifp=0x0) at ../../netinet/ip_icmp.c:225 #24 0xc0201bf9 in ip_forward (m=0xc0c8f000, srcrt=0) at ../../netinet/ip_input.c:1498 #25 0xc0200d4e in ip_input (m=0xc0c8f000) at ../../netinet/ip_input.c:563 #26 0xc02010bb in ipintr () at ../../netinet/ip_input.c:759 #27 0xc0311ab5 in swi_net_next () The code being executed in frame 16 is IPV6-related: 257 fi->fi_src.in6 = ip6->ip6_src; 258 fi->fi_dst.in6 = ip6->ip6_dst; 259 fin->fin_id = (u_short)(ip6->ip6_flow & 0xffff); I'm not using IPV6. I can work around the problem by not running /etc/rc.firewall until after the system is up and running, and I'm currently upgrading to a more recent -STABLE kernel, but I was wondering if anybody else had seen this. Dumps are available on request. 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 Sun Jan 21 17:54:38 2001 Delivered-To: freebsd-stable@freebsd.org Received: from femail10.sdc1.sfba.home.com (femail10.sdc1.sfba.home.com [24.0.95.106]) by hub.freebsd.org (Postfix) with ESMTP id 3310137B400 for ; Sun, 21 Jan 2001 17:54:22 -0800 (PST) Received: from home.com ([24.2.168.159]) by femail10.sdc1.sfba.home.com (InterMail vM.4.01.03.00 201-229-121) with ESMTP id <20010122015422.RYZK6975.femail10.sdc1.sfba.home.com@home.com> for ; Sun, 21 Jan 2001 17:54:22 -0800 Message-ID: <3A6B9008.88CCCE91@home.com> Date: Sun, 21 Jan 2001 20:42:32 -0500 From: Ted Sikora Reply-To: tsikora@powerusersbbs.com Organization: Jtl Development Group X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.19pre2 i686) X-Accept-Language: en-US, en MIME-Version: 1.0 To: "freebsd-stable@FreeBSD.ORG" Subject: ssh login Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I was using the ssh from ports previously. After upgrading and using the one integrated I no longer can access my other nix machines. I can log onto FreeBSD fine though. Any ideas? -- Ted Sikora Jtl Development Group http://powerusersbbs.com Linux the choice of a GNU generation............ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 21 18:13:30 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 2FF7D37B404; Sun, 21 Jan 2001 18:13:07 -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 f0M2D6903850; Sun, 21 Jan 2001 19:13:06 -0700 (MST) (envelope-from imp@harmony.village.org) Message-Id: <200101220213.f0M2D6903850@harmony.village.org> To: "Brian F. Feldman" Subject: Re: newpcm/kobj MFC Cc: "Cameron Grant" , arch@FreeBSD.ORG, stable@FreeBSD.ORG In-reply-to: Your message of "Sun, 21 Jan 2001 17:36:44 EST." <200101212236.f0LMajc09302@green.dyndns.org> References: <200101212236.f0LMajc09302@green.dyndns.org> Date: Sun, 21 Jan 2001 19:13:06 -0700 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200101212236.f0LMajc09302@green.dyndns.org> "Brian F. Feldman" writes: : Warner Losh wrote: : > In message <003401c0833c$39ac3f40$1004020a@darkstar> "Cameron Grant" writes: : > : unless vetoed for good reason, i intend to MFC kobj support into 4.x and : > : > Wouldn't the kobj merge break binary compatibility that we're trying : > to maintain? : : And then make it so that binary compatibility will be preserved between 5.0 : and 4.X for newpcm modules? (at least until the driver is properly locked : ...) There is no way in heck that a 4.x driver will run on 5.x right now. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 21 18:14:51 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 D27E637B400; Sun, 21 Jan 2001 18:14:27 -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 f0M2EP903890; Sun, 21 Jan 2001 19:14:25 -0700 (MST) (envelope-from imp@harmony.village.org) Message-Id: <200101220214.f0M2EP903890@harmony.village.org> To: "Louis A. Mamakos" Subject: Re: newpcm/kobj MFC Cc: Kris Kennaway , Cameron Grant , arch@FreeBSD.ORG, stable@FreeBSD.ORG In-reply-to: Your message of "Sun, 21 Jan 2001 20:04:02 EST." <200101220104.f0M142O04580@whizzo.transsys.com> References: <200101220104.f0M142O04580@whizzo.transsys.com> <003401c0833c$39ac3f40$1004020a@darkstar> <20010121153904.B74751@citusc17.usc.edu> Date: Sun, 21 Jan 2001 19:14:25 -0700 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200101220104.f0M142O04580@whizzo.transsys.com> "Louis A. Mamakos" writes: : It would be useful perhaps to gauge the actual impact of this : incompatability (how many people are using 3rd party sound driver?) : before making a decision. The right question is "How many people are using 3rd party drivers?" since this break binary compatibility for all drivers. That's if I understand the kobj stuff correctly. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 21 18:33:13 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mjolnir.home.m2.qc.ca (modemcable122.45-200-24.mtl.mc.videotron.ca [24.200.45.122]) by hub.freebsd.org (Postfix) with ESMTP id 720D337B400 for ; Sun, 21 Jan 2001 18:32:55 -0800 (PST) Received: (from mailer@localhost) by mjolnir.home.m2.qc.ca (8.10.1/8.10.1) id f0M2UsY01564 for ; Sun, 21 Jan 2001 21:30:54 -0500 (EST) X-Authentication-Warning: mjolnir.home.m2.qc.ca: mailer set sender to using -f Received: from loki.home.m2.qc.ca(192.168.6.7), claiming to be "m2.qc.ca" via SMTP by brother.big, id smtpdfo7255; Sun Jan 21 21:30:46 2001 Message-ID: <3A6B9C7A.38887928@m2.qc.ca> Date: Sun, 21 Jan 2001 21:35:38 -0500 From: Mathieu Mourez X-Mailer: Mozilla 4.73 [en] (X11; U; Linux 2.2.17 i686) X-Accept-Language: en MIME-Version: 1.0 To: stable@freebsd.org Subject: Weird NFS behaviour Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I'm having a problem exporting an ext2fs partition with 4.2-STABLE. (/dev/ad2s2 is my ext2fs partition) [root@minotaur]# more /etc/exports /mnt/drawer/2 -ro -alldirs [root@minotaur]# df -k Filesystem 1K-blocks Used Avail Capacity Mounted on [...] /dev/ad2s2 16516084 9343016 6334076 60% /mnt/drawer/2 [root@minotaur]# kill -1 73669 [root@minotaur]# tail /var/log/messages [...] Jan 21 20:06:40 minotaur mountd[73669]: can't change attributes for /mnt/drawer/2 Jan 21 20:06:40 minotaur mountd[73669]: bad exports list line /mnt/drawer/2 -ro -alldirs So ok, that doesn't work. But now this: [root@minotaur]# umount /mnt/drawer/2/ [root@minotaur]# kill -1 73669 [root@minotaur]# mount /mnt/drawer/2/ # showmount -e Exports list on localhost: /mnt/drawer/2 Everyone And everything works fine. Then a few minutes later, I unmount the ext2, kill mountd and when I restart it (with mountd -dn) I get: [root@minotaur]# mountd -dn mountd: getting export list mountd: got line /mnt/drawer/2 -ro -alldirs mountd: making new ep fs=0x3a4a59f1,0x4b5db4bc mountd: doing opt -ro -alldirs mountd: doing opt -alldirs mountd: adding a default entry mountd: getting mount list mountd: here we go And in the logs: Jan 21 21:08:28 minotaur mountd[73899]: could not remount /mnt/drawer/2: Invalid argument Jan 21 21:08:28 minotaur mountd[73899]: bad exports list line /mnt/drawer/2 -ro -alldirs Can someone shed any light on this? Cheers, - Matt +----------------------------------------------------------+ | Mathieu Mourez matt@loki.home.m2.qc.ca | | BOFH 514.996.9626 | | "The light that burns twice as fast burns half as long" | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 21 19:19: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 5A36D37B404 for ; Sun, 21 Jan 2001 19:19:22 -0800 (PST) Received: from nisser.com (roelof [10.0.0.2]) by nisser.com (8.9.3/8.9.2) with ESMTP id EAA96408; Mon, 22 Jan 2001 04:19:16 +0100 (CET) (envelope-from roelof@nisser.com) Message-ID: <3A6BA6B4.C220CE31@nisser.com> Date: Mon, 22 Jan 2001 04:19:16 +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: Gerhard Sittig Cc: freebsd-stable@FreeBSD.ORG Subject: Re: MAIL set by whom? References: <3A6A50F3.307C9E06@nisser.com> <20010121113334.P253@speedy.gsinet> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Gerhard Sittig wrote: > > [ your lines were wrapped, too, without being marked as such; > PLONK your mail frontend for this stupidity (why don't you use > mutt?) ] 1st this whole thread is about getting mutt started 2nd been there, done that. Had this discussion with Greg. He did not convince me. Maybe you can. Who knows? Unfortunately now, like then, a query like http://www.FreeBSD.org/cgi/search.cgi?words=Re%3A+MAIL+set+by+whom%3F&max=25&sort=score&index=recent&source=freebsd-stable does not give me the 'evidence' I'm looking for. Maybe in due time, maybe not. Who knows? Who has the time? Who cares (then)? You don't need to tell me NS is - eufemism for crap - I'm the one using it! I'm the one who has just got his bookmark.htm file truncated! Alas MS IE does not run on BSD. But let me put it this way. Again. Using NS when reading my very own posts I see no wrapped lines. So if *you* do could it not be due to something *you're* using? Ok, granted, maybe, just *maybe* NS is performing some arcane higher form of magick. Buth me don't think so. End Of Rant and begging your pardon! ;). Roelof -- ---------------------------------------------------------------- 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 Sun Jan 21 19:31:12 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 52CDC37B401; Sun, 21 Jan 2001 19:30:51 -0800 (PST) Received: from darkstar (darkstar.rings [10.2.4.16]) by vilnya.demon.co.uk (Postfix) with SMTP id 2DA24D9B8; Mon, 22 Jan 2001 03:30:49 +0000 (GMT) Message-ID: <007101c08423$33d961a0$1004020a@darkstar> From: "Cameron Grant" To: "Brian F. Feldman" , "Warner Losh" Cc: , References: <200101212236.f0LMajc09302@green.dyndns.org> <200101220213.f0M2D6903850@harmony.village.org> Subject: Re: newpcm/kobj MFC Date: Mon, 22 Jan 2001 03:27:09 -0000 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 > In message <200101212236.f0LMajc09302@green.dyndns.org> "Brian F. Feldman" writes: > : Warner Losh wrote: > : > In message <003401c0833c$39ac3f40$1004020a@darkstar> "Cameron Grant" writes: > : > : unless vetoed for good reason, i intend to MFC kobj support into 4.x and > : > > : > Wouldn't the kobj merge break binary compatibility that we're trying > : > to maintain? > : > : And then make it so that binary compatibility will be preserved between 5.0 > : and 4.X for newpcm modules? (at least until the driver is properly locked > : ...) > > There is no way in heck that a 4.x driver will run on 5.x right now. once newpcm in 4.x is kobjified, drivers from 5.x will at least be source compatible, and appear to be binary compatible from the quick test i just did, though i'm not sure how dependancy data is handled. -cg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 21 19:41:55 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 BBF6037B400; Sun, 21 Jan 2001 19:41:34 -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 f0M3fV904592; Sun, 21 Jan 2001 20:41:31 -0700 (MST) (envelope-from imp@harmony.village.org) Message-Id: <200101220341.f0M3fV904592@harmony.village.org> To: "Cameron Grant" Subject: Re: newpcm/kobj MFC Cc: "Brian F. Feldman" , arch@FreeBSD.ORG, stable@FreeBSD.ORG In-reply-to: Your message of "Mon, 22 Jan 2001 03:27:09 GMT." <007101c08423$33d961a0$1004020a@darkstar> References: <007101c08423$33d961a0$1004020a@darkstar> <200101212236.f0LMajc09302@green.dyndns.org> <200101220213.f0M2D6903850@harmony.village.org> Date: Sun, 21 Jan 2001 20:41:31 -0700 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <007101c08423$33d961a0$1004020a@darkstar> "Cameron Grant" writes: : once newpcm in 4.x is kobjified, drivers from 5.x will at least be source : compatible, and appear to be binary compatible from the quick test i just : did, though i'm not sure how dependancy data is handled. OK. Are you going to just change the interface between the sound drivers and the pcm system, or are you going to back port the newer kobj system. If just the former, then forget I said anything. If there's no kernel interaction other than the bus_space* functions, chances are pretty good it might work. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 21 19:50: 6 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 7B2FB37B400; Sun, 21 Jan 2001 19:49:43 -0800 (PST) Received: from darkstar (darkstar.rings [10.2.4.16]) by vilnya.demon.co.uk (Postfix) with SMTP id 5D88ED9B8; Mon, 22 Jan 2001 03:49:41 +0000 (GMT) Message-ID: <007901c08425$d6b11600$1004020a@darkstar> From: "Cameron Grant" To: "Warner Losh" Cc: "Brian F. Feldman" , , References: <007101c08423$33d961a0$1004020a@darkstar> <200101212236.f0LMajc09302@green.dyndns.org> <200101220213.f0M2D6903850@harmony.village.org> <200101220341.f0M3fV904592@harmony.village.org> Subject: Re: newpcm/kobj MFC Date: Mon, 22 Jan 2001 03:46:01 -0000 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 > OK. Are you going to just change the interface between the sound > drivers and the pcm system, or are you going to back port the newer > kobj system. If just the former, then forget I said anything. If > there's no kernel interaction other than the bus_space* functions, > chances are pretty good it might work. the change involves backporting kobj, but it will only be used in the interface between newpcm and newpcm hardware drivers. there will be no change in binary compatibility for the rest of the kernel. -cg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 21 19:52:43 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 29C6537B402; Sun, 21 Jan 2001 19:52:22 -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 f0M3qF904691; Sun, 21 Jan 2001 20:52:15 -0700 (MST) (envelope-from imp@harmony.village.org) Message-Id: <200101220352.f0M3qF904691@harmony.village.org> To: "Cameron Grant" Subject: Re: newpcm/kobj MFC Cc: "Brian F. Feldman" , arch@FreeBSD.ORG, stable@FreeBSD.ORG In-reply-to: Your message of "Mon, 22 Jan 2001 03:46:01 GMT." <007901c08425$d6b11600$1004020a@darkstar> References: <007901c08425$d6b11600$1004020a@darkstar> <007101c08423$33d961a0$1004020a@darkstar> <200101212236.f0LMajc09302@green.dyndns.org> <200101220213.f0M2D6903850@harmony.village.org> <200101220341.f0M3fV904592@harmony.village.org> Date: Sun, 21 Jan 2001 20:52:15 -0700 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <007901c08425$d6b11600$1004020a@darkstar> "Cameron Grant" writes: : the change involves backporting kobj, but it will only be used in the : interface between newpcm and newpcm hardware drivers. there will be no : change in binary compatibility for the rest of the kernel. Ah. I misunderstood. Change me to a "go for it" kinda guy. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 21 20:35:42 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail.catseye.net (dsl-64-34-131-193.telocity.com [64.34.131.193]) by hub.freebsd.org (Postfix) with SMTP id 4B95737B400 for ; Sun, 21 Jan 2001 20:35:23 -0800 (PST) Received: (qmail 79235 invoked by uid 1001); 22 Jan 2001 04:35:14 -0000 Date: Sun, 21 Jan 2001 22:35:14 -0600 From: Timothy Legant To: freebsd-stable@freebsd.org Subject: Re: MAIL set by whom? Message-ID: <20010121223513.A76438@mail.catseye.net> Mail-Followup-To: freebsd-stable@freebsd.org 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 X-Editor: Vim (http://www.vim.org/) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jan 21, 2001 at 04:01:07AM +0100, Roelof Osinga wrote: [snip...] > 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! :) I've followed this whole thread and it appears there are two issues. 1. If you need to have MAIL set properly: a. do it through login.conf, and b. ensure "UseLogin no" is *NOT* set in sshd_config 2. You want to read Maildirs with Mutt With the proper configuration of your .muttrc, you don't need to worry about the MAIL variable. On my system... % printenv | grep MAIL % I use Mutt both at home (in an rxvt in X) and through an ssh connection from work. I use Maildirs for incoming mail and an mbox for saving outgoing messages and for Mutt's postponed feature. Mutt automatically detects which I'm using. > PS I've read about: > > nl:~$ cat .mutttrc > set mbox_type="Maildir" mbox_type specifies which type of mailbox to create (Maildir, mbox, MH folder, etc) when you create a new mailbox in mutt. Nothing more. It does NOT specify anything about existing mailboxes. > set mbox="$HOME/Maildir/" mbox specifies where to move messages from your spoolfile once you've read them. It doesn't apply to other mailboxes - only the one you've specified as your spoolfile. I have mine set to the same Maildir that is my spoolfile. In other words, messages don't get moved at all. They stay where they are. You can put them somewhere else, if you like. > set spoolfile="$HOME/Maildir/" This is your startup mailbox - what was traditionally /var/mail/$USER. The concept of a spoolfile isn't so important anymore, since most of us use procmail or the like to deliver into multiple local mailboxes. In any case, it's the mailbox mutt displays first if you don't specify a different one on the command line. > but am wondering if that really is all there is? Not quite. You should set the "folder" variable *before* you set any of the other mailbox related variables. Then you can use either '+' or '=' as a shortcut to mean the directory where you keep all your mailboxes. Also, "record" specifies which mailbox should store a copy of all your outgoing mail. Here is how I have mine set up. % ls -l ~/Mail drwx------ 5 thl thl 512 Sep 4 12:40 Bedtime drwx------ 5 thl thl 512 Sep 4 12:40 Dns drwx------ 5 thl thl 512 Sep 4 12:41 FreeBSD-STABLE drwx------ 5 thl thl 512 Sep 4 12:39 Inbox drwx------ 5 thl thl 512 Jan 21 00:28 Mix drwx------ 5 thl thl 512 Nov 9 21:51 Mutt-Dev drwx------ 5 thl thl 512 Sep 4 12:41 Mutt-Users drwx------ 5 thl thl 512 Sep 4 12:43 Qmail -rw------- 1 thl thl 2329652 Jan 21 03:31 outbox -rw------- 1 thl thl 0 Jan 21 02:23 postponed The directories are all qmail-style Maildirs. outbox and postponed are mboxes. Here are the relevant pieces from my .muttrc set folder=~/Mail # set this first, then use + as a shortcut set spoolfile=+Inbox set mbox=+Inbox set record=+outbox set postponed=+postponed set mbox_type=Maildir # new mailboxes will be Maildirs # this lets Mutt know about all the mailboxes I read, in order to cycle # through them with 'c'. mailboxes +Inbox +Qmail +Mutt-Dev +Mutt-Users + FreeBSD-STABLE +Dns +Mix Mutt handles all the rest. My MAIL setting is not relevant. Mutt's handling of Maildirs is excellent. People using mboxes sometimes have difficulties detecting new mail with Mutt, since using another tool (like grep or various biffs) can change the access time. Maildirs don't suffer from this problem at all. Good luck! Tim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 21 21:15: 4 2001 Delivered-To: freebsd-stable@freebsd.org Received: from femail12.sdc1.sfba.home.com (femail12.sdc1.sfba.home.com [24.0.95.108]) by hub.freebsd.org (Postfix) with ESMTP id 2C43437B400 for ; Sun, 21 Jan 2001 21:14:45 -0800 (PST) Received: from boots2 ([24.0.178.21]) by femail12.sdc1.sfba.home.com (InterMail vM.4.01.03.00 201-229-121) with SMTP id <20010122051439.TAVW9070.femail12.sdc1.sfba.home.com@boots2>; Sun, 21 Jan 2001 21:14:39 -0800 From: "Craig Burgess" To: Cc: Subject: RE: dmesg/security check output wierdness Date: Sun, 21 Jan 2001 21:20:09 -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: <20010121143324.U10761@rfx-216-196-73-168.users.reflex> X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a bit different but from what you have written, may I assume that the msg poses (below) no threat? It's the first I've seen it and it appeared on first boot after kernel build (following CVSUP for ports & source and make world) >>Jan 21 20:25:51 Felix /kernel: file: table is full or is this another matter entirely? If I need to do something about it, what? One strangeness was that the machine "spontaneously" denied permission to ping even localhost until i had rebuilt the kernel, even though it worked for about 8 hours after 'make installworld' but running on the "old" kernel (4.1.1) - no reboot following installworld. Here's what I'm running now: FreeBSD Felix 4.2-STABLE FreeBSD 4.2-STABLE #8: Sun Jan 21 17:57:41 PST 2001 craig@Felix:/usr/src/sys/compile/FELIX alpha mostly the machine is a very large and underworked natd/firewall which seems to be running okay. thanks, craig -----Original Message----- From: owner-freebsd-stable@FreeBSD.ORG [mailto:owner-freebsd-stable@FreeBSD.ORG]On Behalf Of Crist J. Clark Sent: Sunday, January 21, 2001 2:33 PM To: David Goddard Cc: stable@FreeBSD.ORG Subject: Re: dmesg/security check output wierdness On Sun, Jan 21, 2001 at 04:10:10PM +0000, David Goddard wrote: > I've recently noticed some odd entries in my security check output mail > from a couple of 4.2-STABLE machines, so I did some digging. The > following is one example: > > [Date: Sun, 21 Jan 2001 03:18:15 +0000] > cassium.mydomain.com kernel log messages: > > 06 cleared. [snip] > Any ideas? The dmesg(8) is stored in a finite buffer. Once full, as more stuff gets shoved in, other stuff falls out (really it gets overwritten, it's a circular buffer, but same thing). The stuff that falls out, does not do so all that gracefully. That is, it does not get dropped whole lines at a time. For example, $ dmesg | head -5 0.1.35:427 in via de0 ipfw: 11500 Deny UDP AAA.BBB.153.173:137 AAA.BBB.153.255:137 in via de0 ipfw: 11500 Deny UDP AAA.BBB.153.173:137 AAA.BBB.153.255:137 in via de0 ipfw: 11500 Deny UDP AAA.BBB.153.173:137 AAA.BBB.153.255:137 in via de0 ipfw: 11500 Deny UDP AAA.BBB.153.173:427 224.0.1.35:427 in via de0 Notice the first line. Now, I do something to make a little noise in the dmesg buffer and check again, $ dmesg | head -5 .255:137 in via de0 ipfw: 11500 Deny UDP AAA.BBB.153.173:137 AAA.BBB.153.255:137 in via de0 ipfw: 11500 Deny UDP AAA.BBB.153.173:137 AAA.BBB.153.255:137 in via de0 ipfw: 11500 Deny UDP AAA.BBB.153.173:427 224.0.1.35:427 in via de0 ipfw: 11500 Deny ICMP:10.0 AAA.BBB.153.173 224.0.0.2 in via de0 Now, as for the '10>' or similar constructions you sometimes see popping up on the first line. Have a look at, $ sysctl machdep.msgbuf dmesg(8) strips the leading off of the lines when printing it for you. But if one of these is cut in the middle... You get the picture. -- Crist J. Clark cjclark@alum.mit.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 21 21:18: 2 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mass.dis.org (ashto-0006.sjc.ca.bbnow.net [24.219.121.199]) by hub.freebsd.org (Postfix) with ESMTP id 748A937B400 for ; Sun, 21 Jan 2001 21:17:44 -0800 (PST) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.1/8.11.1) with ESMTP id f0M5VqD01716; Sun, 21 Jan 2001 21:32:08 -0800 (PST) (envelope-from msmith@mass.dis.org) Message-Id: <200101220532.f0M5VqD01716@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Jim C. Nasby" Cc: Mike Tancsa , Sys Admin , freebsd-stable@freebsd.org Subject: Re: RAID configuration for a mail server (1 or 5) In-reply-to: Your message of "Sat, 20 Jan 2001 01:26:00 CST." <3A693D88.9D1F4E3D@nasby.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 21 Jan 2001 21:31:52 -0800 From: Mike Smith 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. This depends on how smart the RAID controller is; AFAIR the 3ware controller is actually doing striped "TwinStor" groups, but I'm on the road and would have to check when I get home. > 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. I'd have a hard time accepting that 10+ years into the evolution of RAID technology, anything other than a dime-store controller would do this. 8) > 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. Um, I'd recommend a quick RAID-101 course. 8) You can read the original data block, the checksum block, and from the delta between the original block, the new data and using the checksum data you can regenerate the checksum. This typically involves two reads and two writes for a given write, although normally the reads are performed on a fairly large block to improve sequential performance (some will read a whole stripe, others like eg. Mylex use 8k (default) 'cache lines' as the basic unit for this operation). You only actually have to read the data that backs the data being written though. -- ... 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 Sun Jan 21 21:42: 4 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mailout00.sul.t-online.com (mailout00.sul.t-online.com [194.25.134.16]) by hub.freebsd.org (Postfix) with ESMTP id C094637B400; Sun, 21 Jan 2001 21:41:44 -0800 (PST) Received: from fwd02.sul.t-online.com by mailout00.sul.t-online.com with smtp id 14KZjb-0008Sv-00; Mon, 22 Jan 2001 06:41:43 +0100 Received: from frolic.no-support.loc (520094253176-0001@[217.80.111.105]) by fmrl02.sul.t-online.com with esmtp id 14KZjQ-1bi9XEC; Mon, 22 Jan 2001 06:41:32 +0100 Received: (from bjoern@localhost) by frolic.no-support.loc (8.11.1/8.9.3) id f0M5ai700537; Mon, 22 Jan 2001 06:36:44 +0100 (CET) (envelope-from bjoern) From: Bjoern Fischer Date: Mon, 22 Jan 2001 06:36:44 +0100 To: mike@hyperreal.org Cc: freebsd-stable@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: MAIL set by whom? Message-ID: <20010122063644.A273@frolic.no-support.loc> References: <20010121193633.16438.qmail@hyperreal.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010121193633.16438.qmail@hyperreal.org>; from mike@hyperreal.org on Sun, Jan 21, 2001 at 11:36:33AM -0800 X-Sender: 520094253176-0001@t-dialin.net Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > So like I said, the solution was "UseLogin yes" in sshd_config. This only works for shh shell logins. If you want to start an application on the remote site without invoking your shell, the use of /bin/login is not possible. E.g. you want to start an xterm or a mail (x-)client on a remote machine with: ssh -f . Bjoern -- -----BEGIN GEEK CODE BLOCK----- GCS d--(+) s++: a- C+++(-) UB++++OSI++++$ P+++(-) L---(++) !E W- N+ o>+ K- !w !O !M !V PS++ PE- PGP++ t+++ !5 X++ tv- b+++ D++ G e+ h-- y+ ------END GEEK CODE BLOCK------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 21 21:49:21 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 90C4937B404; Sun, 21 Jan 2001 21:48:56 -0800 (PST) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id QAA06650; Mon, 22 Jan 2001 16:48:47 +1100 Date: Mon, 22 Jan 2001 16:48:41 +1100 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Warner Losh Cc: "Brian F. Feldman" , Cameron Grant , arch@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: newpcm/kobj MFC In-Reply-To: <200101220213.f0M2D6903850@harmony.village.org> 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, 21 Jan 2001, Warner Losh wrote: > In message <200101212236.f0LMajc09302@green.dyndns.org> "Brian F. Feldman" writes: > : And then make it so that binary compatibility will be preserved between 5.0 > : and 4.X for newpcm modules? (at least until the driver is properly locked > : ...) > > There is no way in heck that a 4.x driver will run on 5.x right now. E.g., 4.x drivers probably use spl's, but spl's no longer exist as extern functions. The vmware modules broke about 5 minutes after I rebuilt them when extern spl's went away a couple of days ago :-). 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 21 21:52:24 2001 Delivered-To: freebsd-stable@freebsd.org Received: from lafontaine.cybercable.fr (lafontaine.cybercable.fr [212.198.0.202]) by hub.freebsd.org (Postfix) with SMTP id 9F48837B404 for ; Sun, 21 Jan 2001 21:52:03 -0800 (PST) Received: (qmail 29506191 invoked from network); 22 Jan 2001 05:52:02 -0000 Received: from s011.dhcp212-229.cybercable.fr (HELO gits.dyndns.org) ([212.198.229.11]) (envelope-sender ) by lafontaine.cybercable.fr (qmail-ldap-1.03) with SMTP for ; 22 Jan 2001 05:52:02 -0000 Received: (from root@localhost) by gits.dyndns.org (8.11.1/8.11.1) id f0M5q0A87431; Mon, 22 Jan 2001 06:52:00 +0100 (CET) (envelope-from clefevre@citeweb.net) To: Courvette Cc: FBSD-Q , FBSD-STABLE Subject: Re: Help with Tape Drive References: <20010117181924.A18085@poeza.iconnect.co.ke> X-Face: V|+c;4!|B?E%BE^{E6);aI.[<97Zd*>^#%Y5Cxv;%Y[PT-LW3;A:fRrJ8+^k"e7@+30g0YD0*^^3jgyShN7o?a]C la*Zv'5NA,=963bM%J^o]C In-Reply-To: Courvette's message of "Wed, 17 Jan 2001 18:19:24 +0300" From: Cyrille Lefevre Reply-To: clefevre@noos.fr Mail-Copies-To: never Date: 22 Jan 2001 06:51:58 +0100 Message-ID: <3decqgld.fsf@gits.dyndns.org> Lines: 11 User-Agent: Gnus/5.0807 (Gnus v5.8.7) XEmacs/21.1 (Channel Islands) 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: > 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.... please, give us the output of : camcontrol devlist Cyrille. -- home: mailto:clefevre@citeweb.net work: mailto:Cyrille.Lefevre@edf.fr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 21 22:33:17 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 0B4BA37B6A0 for ; Sun, 21 Jan 2001 22:32:57 -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); Sun, 21 Jan 2001 22:30:38 -0800 Received: (from cjc@localhost) by rfx-216-196-73-168.users.reflexcom.com (8.11.1/8.11.0) id f0M6WO169923; Sun, 21 Jan 2001 22:32:24 -0800 (PST) (envelope-from cjc) Date: Sun, 21 Jan 2001 22:32:19 -0800 From: "Crist J. Clark" To: Craig Burgess Cc: stable@FreeBSD.ORG Subject: Re: dmesg/security check output wierdness Message-ID: <20010121223219.I10761@rfx-216-196-73-168.users.reflex> Reply-To: cjclark@alum.mit.edu References: <20010121143324.U10761@rfx-216-196-73-168.users.reflex> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from craig-burgess@home.net on Sun, Jan 21, 2001 at 09:20:09PM -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jan 21, 2001 at 09:20:09PM -0800, Craig Burgess wrote: > This is a bit different but from what you have written, This really has nothing to do with this thread. > may I assume that > the msg poses (below) no threat? It's the first I've seen it and it appeared > on first boot after kernel build (following CVSUP for ports & source and > make world) > > >>Jan 21 20:25:51 Felix /kernel: file: table is full > > or is this another matter entirely? Not a good thing. > If I need to do something about it, > what? First figure out if something is broken. Check fstat(1) for a process opening more files than it should. If OTOH, this is part of the systems normal operations, try uping 'maxusers' in the kernel config. See the maillogs and other references on how high to go. > One strangeness was that the machine "spontaneously" denied permission > to ping even localhost until i had rebuilt the kernel, even though it worked > for about 8 hours after 'make installworld' but running on the "old" kernel > (4.1.1) - no reboot following installworld. Weird breakage with the kernel and userland out of sync? Not surprising. > Here's what I'm running now: > > FreeBSD Felix 4.2-STABLE FreeBSD 4.2-STABLE #8: Sun Jan 21 17:57:41 PST 2001 > craig@Felix:/usr/src/sys/compile/FELIX alpha > > mostly the machine is a very large and underworked natd/firewall which seems > to be running okay. -- 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 21 23:14:28 2001 Delivered-To: freebsd-stable@freebsd.org Received: from note.orchestra.cse.unsw.EDU.AU (note.orchestra.cse.unsw.EDU.AU [129.94.242.29]) by hub.freebsd.org (Postfix) with SMTP id ED27837B401 for ; Sun, 21 Jan 2001 23:14:06 -0800 (PST) Received: From notabene.cse.unsw.edu.au ([129.94.242.2] == beethoven.orchestra.cse.unsw.EDU.AU) (for ) (for ) (for ) (for ) By note With Smtp ; Mon, 22 Jan 2001 18:12:18 +1100 Received: from neilb by notabene.cse.unsw.edu.au with local (Exim 3.12 #1 (Debian)) id 14Kb9B-0002Wy-00; Mon, 22 Jan 2001 18:12:13 +1100 From: Neil Brown To: Matthias Andree Date: Mon, 22 Jan 2001 18:12:12 +1100 (EST) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14955.56652.919230.41950@notabene.cse.unsw.edu.au> Cc: Linux NFS mailing list , reiserfs-list@namesys.com, FreeBSD Stable Subject: Re: [NFS] Incompatible: FreeBSD 4.2 client, Linux 2.2.18 nfsv3 server, ReiserFS In-Reply-To: message from Matthias Andree on Saturday January 20 References: <20010120234024.A1771@emma1.emma.line.org> X-Mailer: VM 6.72 under Emacs 20.7.2 X-face: [Gw_3E*Gng}4rRrKRYotwlE?.2|**#s9D 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) > Beware of error messages reported by tcpdump... they are misleading. The error code in the tcp packet is an "NFS error code" which should not be confused with an "Unix-errno" error code, though there are sometimes similarities. tcpdump seems to assume that nfs error codes *are* unix error codes. So you can believe the "116" but not the "read-only file system". Interestingly, nfs does not have an error "116", so it looks like the NFS server is leaking unix errno codes into the protocol. The Linux error code "116" is "Stale NFS file handle" (expect for Sparc Linux, there it is "Interrupted syscall should be restarted"). So my guess is that the reiserfs code which tries to support nfsd (which may well involve some patches to knfsd) is having problems, and wants to return ESTALE, but returns it without converting to an NFS error code. However I'm having trouble guessing why it would affect FreeBSD clients, but not Solaris or Linux clients. Hope this is helpful to someone. NeilBrown To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 22 0:40:48 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 98DC137B401; Mon, 22 Jan 2001 00:40: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 14KcUt-000Hhn-00; Mon, 22 Jan 2001 11:38:44 +0300 Received: from wash by poeza.iconnect.co.ke with local (Exim 3.20 #1) id 14KcWb-00052S-00; Mon, 22 Jan 2001 11:40:29 +0300 Date: Mon, 22 Jan 2001 11:40:29 +0300 From: Corvette To: FBSD-Q , FBSD-STABLE Cc: Cyrille.Lefevre@edf.fr Subject: Re: Help with Tape Drive Message-ID: <20010122114029.D18801@poeza.iconnect.co.ke> Mail-Followup-To: Corvette , FBSD-Q , FBSD-STABLE , Cyrille.Lefevre@edf.fr References: <20010117181924.A18085@poeza.iconnect.co.ke> <3decqgld.fsf@gits.dyndns.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3decqgld.fsf@gits.dyndns.org>; from "Cyrille Lefevre" on Mon, Jan 22, 2001 at 06:51:58AM +0100 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 * Cyrille Lefevre [20010122 09:48]: writing on the subject 'Re: Help with Tape Drive' Cyrille> Courvette writes: Cyrille> Cyrille> > Someone can help me with this one. After an upgrade to 4.2-STABLE from Cyrille> > 3.5-STABLE I am unable to use my tape drive -and consequently can't do Cyrille> > backups - we all know how serious that is.... Cyrille> Cyrille> please, give us the output of : camcontrol devlist wash:/usr/home/wash# camcontrol devlist at scbus0 target 0 lun 0 (pass0,da0) at scbus0 target 2 lun 0 (pass1,da1) at scbus0 target 4 lun 0 (pass2,sa0) -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. The right to be let alone is indeed the beginning of all freedom. (contributed by Frank v Waveren) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 22 1:35:21 2001 Delivered-To: freebsd-stable@freebsd.org Received: from duckling.worldonline.nl (duckling.worldonline.nl [195.241.45.86]) by hub.freebsd.org (Postfix) with ESMTP id 42DA937B400 for ; Mon, 22 Jan 2001 01:35:01 -0800 (PST) Received: (from maikel@localhost) by duckling.worldonline.nl (8.11.1/8.11.1) id f0M9ZDH07172 for stable@freebsd.org; Mon, 22 Jan 2001 10:35:13 +0100 (CET) (envelope-from maikel) Date: Mon, 22 Jan 2001 10:35:03 +0100 From: Maikel Verheijen To: stable@freebsd.org Subject: Ipfilter version in stable... Message-ID: <20010122103503.B78003@duckling.worldonline.nl> Mail-Followup-To: Maikel Verheijen , 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 all! Does anyone know when there will be a new version of ipfilter be integrated in FreeBSD-stable? The one in FreeBSD (v3.4.8) still has a bug when natting active ftp connections. Of course I can install the newest ipfilter, but I don't want to recompile and install it after each buildworld + installworld :) TIA, Maikel Verheijen. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 22 1:47:33 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 7694137B400; Mon, 22 Jan 2001 01:47:11 -0800 (PST) Received: (from dom@localhost) by clove.rp.lan (8.9.3/8.8.7) id JAA08793; Mon, 22 Jan 2001 09:46:47 GMT X-Authentication-Warning: clove.rp.lan: dom set sender to dom@semantico.com using -f Date: Mon, 22 Jan 2001 09:46:47 +0000 From: Dominic Mitchell To: Roelof Osinga Cc: Bjoern Fischer , freebsd-stable@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: PAM (was: Re: MAIL set by whom?) Message-ID: <20010122094647.A7853@semantico.com> References: <3A6A50F3.307C9E06@nisser.com> <20010121103324.A297@frolic.no-support.loc> <3A6B042E.659C716D@nisser.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3us In-Reply-To: <3A6B042E.659C716D@nisser.com> X-Warning: Incoming message from The Big Giant Head! X-OS: Linux 2.2.13 i686 X-Uptime: 9:36am up 24 days, 20:56, 3 users, load average: 1.24, 0.72, 0.29 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jan 21, 2001 at 04:45:50PM +0100, Roelof Osinga wrote: > Grand gesture. Laudable even. Yeah, that PAM sure seems to've > become popular. The Courier IMAP port also insisted upon its > installation. Insisted in that fiddling with the makefile only > resulted in failure to configure. But that's a whole different > story. Would it be a good idea to start using /etc/pam.d ala RedHat, instead of the monolithic /etc/pam.conf? As far as I can see the support is already there, it's just not being used due to the presence of the /etc/pam.conf. This would make installing PAM entries far easier for the ports. -Dom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 22 1:57:32 2001 Delivered-To: freebsd-stable@freebsd.org Received: from emma1.emma.line.org (p3EE3C97F.dip.t-dialin.net [62.227.201.127]) by hub.freebsd.org (Postfix) with ESMTP id 7FCA237B400 for ; Mon, 22 Jan 2001 01:57:14 -0800 (PST) Received: by emma1.emma.line.org (Postfix, from userid 500) id 1A48BA2002; Mon, 22 Jan 2001 10:57:06 +0100 (CET) Date: Mon, 22 Jan 2001 10:57:05 +0100 From: Matthias Andree To: Linux NFS mailing list , reiserfs-list@namesys.com, FreeBSD Stable Subject: Re: [NFS] Incompatible: FreeBSD 4.2 client, Linux 2.2.18 nfsv3 server, ReiserFS Message-ID: <20010122105705.A2957@emma1.emma.line.org> Mail-Followup-To: Linux NFS mailing list , reiserfs-list@namesys.com, FreeBSD Stable References: <20010120234024.A1771@emma1.emma.line.org> <14955.56652.919230.41950@notabene.cse.unsw.edu.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <14955.56652.919230.41950@notabene.cse.unsw.edu.au>; from neilb@cse.unsw.edu.au on Mon, Jan 22, 2001 at 18:12:12 +1100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 22 Jan 2001, Neil Brown wrote: > On Saturday January 20, matthias.andree@stud.uni-dortmund.de wrote: > Beware of error messages reported by tcpdump... they are misleading. > The error code in the tcp packet is an "NFS error code" which should > not be confused with an "Unix-errno" error code, though there are > sometimes similarities. > tcpdump seems to assume that nfs error codes *are* unix error codes. > So you can believe the "116" but not the "read-only file system". Euhm, mount as well as ls return this error response as well. > Interestingly, nfs does not have an error "116", so it looks like the > NFS server is leaking unix errno codes into the protocol. > The Linux error code "116" is "Stale NFS file handle" (expect for > Sparc Linux, there it is "Interrupted syscall should be restarted"). May be, but a stale NFS file handle error on a freshly mounted file system (in response to mount possibly) is no better than a completely bogus error. > However I'm having trouble guessing why it would affect FreeBSD clients, > but not Solaris or Linux clients. And why v2 is fine with FreeBSD. -- Matthias Andree To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 22 2: 7:39 2001 Delivered-To: freebsd-stable@freebsd.org Received: from pcwin002.win.tue.nl (pcwin002.win.tue.nl [131.155.71.72]) by hub.freebsd.org (Postfix) with ESMTP id 4F7F137B404; Mon, 22 Jan 2001 02:07:12 -0800 (PST) Received: (from stijn@localhost) by pcwin002.win.tue.nl (8.11.1/8.11.1) id f0MA6x970885; Mon, 22 Jan 2001 11:06:59 +0100 (CET) (envelope-from stijn) Date: Mon, 22 Jan 2001 11:06:59 +0100 From: Stijn Hoop To: Dominic Mitchell Cc: freebsd-stable@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: PAM (was: Re: MAIL set by whom?) Message-ID: <20010122110659.F70055@pcwin002.win.tue.nl> References: <3A6A50F3.307C9E06@nisser.com> <20010121103324.A297@frolic.no-support.loc> <3A6B042E.659C716D@nisser.com> <20010122094647.A7853@semantico.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010122094647.A7853@semantico.com>; from dom@semantico.com on Mon, Jan 22, 2001 at 09:46:47AM +0000 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jan 22, 2001 at 09:46:47AM +0000, Dominic Mitchell wrote: > Would it be a good idea to start using /etc/pam.d ala RedHat, instead of > the monolithic /etc/pam.conf? > > As far as I can see the support is already there, it's just not being > used due to the presence of the /etc/pam.conf. > > This would make installing PAM entries far easier for the ports. Seconded. I don't see any reason *not* to do it this way. OTOH, ports are not supposed to install in /etc, so the best way would be to extend pam to support /usr/local/etc/pam.d *and* /etc/pam.d (if it doesn't already do this). No, I'm not sending patches, sorry :) --Stijn -- Nostalgia ain't what it used to be. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 22 2:21:37 2001 Delivered-To: freebsd-stable@freebsd.org Received: from emma1.emma.line.org (p3EE3C97F.dip.t-dialin.net [62.227.201.127]) by hub.freebsd.org (Postfix) with ESMTP id 72C6137B401 for ; Mon, 22 Jan 2001 02:21:19 -0800 (PST) Received: by emma1.emma.line.org (Postfix, from userid 500) id A38D4A2002; Mon, 22 Jan 2001 11:21:15 +0100 (CET) To: "Robert Banniza" Cc: Subject: Re: ssh problem References: In-Reply-To: From: Matthias Andree Date: 22 Jan 2001 11:21:15 +0100 Message-ID: Lines: 19 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 "Robert Banniza" writes: > This brings me to a stupid question. It is better to install the new file > when cvsup'ing or merge the old and new file together? This is assuming the > user hasn't entered anything special into the file. I did an install on the > last cvsup rather than merging. I was somewhat confused when it asked me > whether I wanted to install the file on the right or the file on the left. > Shouldn't they be one in the same if merged? Any info. appreciated... If you did not touch that file, install the new one, it's the safe side and also less hassle on next merge ;-) If you changed parameters in that file, merge your changes into the new one, if in doubt, consult the man pages to figure that the configuration does and if a new parameter is required. You may find either Ctrl-Z useful or the "leave for later" choice in mergemaster. -- Matthias Andree To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 22 2:31:26 2001 Delivered-To: freebsd-stable@freebsd.org Received: from shark.harmonic.co.il (jupiter.harmonic.co.il [192.116.140.62]) by hub.freebsd.org (Postfix) with ESMTP id 3813037B404 for ; Mon, 22 Jan 2001 02:31:08 -0800 (PST) Received: from localhost (roman@localhost) by shark.harmonic.co.il (8.9.3/8.9.3) with ESMTP id MAA16284; Mon, 22 Jan 2001 12:30:49 +0200 Date: Mon, 22 Jan 2001 12:30:48 +0200 (IST) From: Roman Shterenzon To: Forrest Aldrich Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Required files for Linux emulation In-Reply-To: <5.0.0.25.2.20010120140820.02188bd0@216.67.14.69> 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 If it's freely downloadable I can create a port which will deal with it. I don't think that this has to be handled at the linux-6.1 port level. Because, this app needs this file, other app need another file, I don't think it's a good idea to mirror the whole redhat distribution on /compat/linux. On Sat, 20 Jan 2001, Forrest Aldrich wrote: > 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 > --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 Mon Jan 22 2:39:48 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mailsweeper.qdc-ec.co.za (gauntlet.mccarthy.co.za [196.26.24.1]) by hub.freebsd.org (Postfix) with ESMTP id E5C0637B402; Mon, 22 Jan 2001 02:39:14 -0800 (PST) Received: from ntzn2.rainbow.co.za (unverified) by mailsweeper.qdc-ec.co.za (Content Technologies SMTPRS 4.1.5) with ESMTP id ; Mon, 22 Jan 2001 12:35:28 +0200 Received: by ntzn2-ip2.rainbow.co.za with Internet Mail Service (5.5.2650.21) id ; Mon, 22 Jan 2001 12:31:45 +0200 Message-ID: From: "Niekie Myburgh (QData)" To: 'Stijn Hoop' Cc: "'freebsd-stable@freebsd.org'" , "'freebsd-hackers@freebsd.org'" Subject: RE: PAM (was: Re: MAIL set by whom?) Date: Mon, 22 Jan 2001 12:35:55 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C0845F.1A079D00" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C0845F.1A079D00 Content-Type: text/plain I posted a question about PAM & Passwd on 4.2. It seems that passwd "ignores" any passwd lines in pam.conf. I tried the pam.d thing (Run Linux compatibility, copy rc.d/* from Redhat 6.1 to BSD. When you try to log in, the login terminates, and syslog shows: /kernel: pid 22202 (login), uid 0: exited on siglan 10 (core dumped) Rename pam.d, and all is happy (which means I'm back to pam.conf). I have 300Mb swap (all unused) and 26Mb RAM inactive. I don't think that memory / out of swap space is the problem in this case. (I gather from what I could see on the net, that the main culprit for signal 10 seems to be swap space / memory) Can anyone give me an example line for the passwd entry in pam.conf (seems to be happier, although it seems to ignore my changes) I'm using the following: passwd password required pam_xxxxxxx options_options...... I tried pam_cracklib.so with it's options, as well as pam_passwdqc and it's options. I am being ignored. Regards. Niekie > -----Original Message----- > From: Stijn Hoop [SMTP:stijn@win.tue.nl] > Sent: Monday, January 22, 2001 12:07 PM > To: Dominic Mitchell > Cc: freebsd-stable@freebsd.org; freebsd-hackers@freebsd.org > Subject: Re: PAM (was: Re: MAIL set by whom?) > > On Mon, Jan 22, 2001 at 09:46:47AM +0000, Dominic Mitchell wrote: > > Would it be a good idea to start using /etc/pam.d ala RedHat, instead of > > the monolithic /etc/pam.conf? > > > > As far as I can see the support is already there, it's just not being > > used due to the presence of the /etc/pam.conf. > > > > This would make installing PAM entries far easier for the ports. > > Seconded. I don't see any reason *not* to do it this way. > > OTOH, ports are not supposed to install in /etc, so the best way would > be to extend pam to support /usr/local/etc/pam.d *and* /etc/pam.d > (if it doesn't already do this). > > No, I'm not sending patches, sorry :) > > --Stijn > > -- > Nostalgia ain't what it used to be. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message ------_=_NextPart_001_01C0845F.1A079D00 Content-Type: text/html Content-Transfer-Encoding: quoted-printable RE: PAM (was: Re: MAIL set by whom?)

I posted a question = about PAM & Passwd on 4.2.  It seems that passwd = "ignores" any passwd lines in pam.conf.  I tried the = pam.d thing (Run Linux compatibility, copy rc.d/* from Redhat 6.1 to = BSD.  When you try to log in, the login terminates, and syslog = shows:

/kernel: pid 22202 = (login), uid 0: exited on siglan 10 (core dumped)

Rename pam.d, and = all is happy (which means I'm back to pam.conf).

I have 300Mb swap = (all unused) and 26Mb RAM inactive.  I don't think that memory / = out of swap space is the problem in this case. (I gather from what I = could see on the net, that the main culprit for signal 10 seems to be = swap space / memory)

Can anyone give me = an example line for the passwd entry in pam.conf (seems to be happier, = although it seems to ignore my changes)

I'm using the = following:

passwd  =         = password        = required        =         pam_xxxxxxx = options_options......

I tried = pam_cracklib.so with it's options, as well as pam_passwdqc and it's = options.  I am being ignored.

Regards.

Niekie





    -----Original Message-----
    From:   Stijn Hoop [SMTP:stijn@win.tue.nl]
    Sent:   Monday, January 22, 2001 12:07 PM
    To:     Dominic Mitchell
    Cc:     freebsd-stable@freebsd.org; = freebsd-hackers@freebsd.org
    Subject:       = Re: PAM (was: Re: MAIL set by = whom?)

    On Mon, Jan 22, 2001 at 09:46:47AM = +0000, Dominic Mitchell wrote:
    > Would it be a good idea to start = using /etc/pam.d ala RedHat, instead of
    > the monolithic = /etc/pam.conf?
    >
    > As far as I can see the support = is already there, it's just not being
    > used due to the presence of the = /etc/pam.conf.
    >
    > This would make installing PAM = entries far easier for the ports.

    Seconded. I don't see any reason *not* = to do it this way.

    OTOH, ports are not supposed to = install in /etc, so the best way would
    be to extend pam to support = /usr/local/etc/pam.d *and* /etc/pam.d
    (if it doesn't already do = this).

    No, I'm not sending patches, sorry = :)

    --Stijn

    --
    Nostalgia ain't what it used to = be.


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

------_=_NextPart_001_01C0845F.1A079D00-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 22 3:53:32 2001 Delivered-To: freebsd-stable@freebsd.org Received: from shark.harmonic.co.il (jupiter.harmonic.co.il [192.116.140.62]) by hub.freebsd.org (Postfix) with ESMTP id A433637B400 for ; Mon, 22 Jan 2001 03:53:13 -0800 (PST) Received: from localhost (roman@localhost) by shark.harmonic.co.il (8.9.3/8.9.3) with ESMTP id NAA18954; Mon, 22 Jan 2001 13:52:55 +0200 Date: Mon, 22 Jan 2001 13:52:55 +0200 (IST) From: Roman Shterenzon To: "Paul A. Howes" Cc: freebsd-stable@FreeBSD.ORG Subject: Re: New Intel NICs... 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 Sat, 20 Jan 2001, Paul A. Howes wrote: > 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? We were supposed to do a hardware project based on this chip. However, we didn't receive the docs in time, and it was dropped. The bottom line is that part of the specification is under NDA or something similar as far as I remember. If this is the case, then adding support for it can be tricky. ..ehmm... perhaps I'm wrong (hopefully). --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 Mon Jan 22 3:57:57 2001 Delivered-To: freebsd-stable@freebsd.org Received: from shark.harmonic.co.il (jupiter.harmonic.co.il [192.116.140.62]) by hub.freebsd.org (Postfix) with ESMTP id 17CA437B400 for ; Mon, 22 Jan 2001 03:57:38 -0800 (PST) Received: from localhost (roman@localhost) by shark.harmonic.co.il (8.9.3/8.9.3) with ESMTP id NAA19115; Mon, 22 Jan 2001 13:57:21 +0200 Date: Mon, 22 Jan 2001 13:57:21 +0200 (IST) From: Roman Shterenzon To: Warner Losh Cc: Forrest Aldrich , freebsd-stable@FreeBSD.ORG Subject: Re: Required files for Linux emulation In-Reply-To: <200101212139.f0LLda901980@harmony.village.org> 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, 21 Jan 2001, Warner Losh wrote: > In message <5.0.0.25.2.20010120140820.02188bd0@216.67.14.69> Forrest Aldrich writes: > : 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? > > echo "6.0" > /compat/linux/etc/redhat-release I guess it's using FreeBSD grep and looking at /etc. As I said, it should be done in the ports tree (or added to /etc/redhat-release) which I'd be very surprised to see on FreeBSD system :) --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 Mon Jan 22 6:12:24 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mailgate.abacus.co.uk (unknown [194.130.48.21]) by hub.freebsd.org (Postfix) with ESMTP id 61E0437B400 for ; Mon, 22 Jan 2001 06:12:04 -0800 (PST) Received: from abacus.co.uk (pcantony.bl.abacus.co.uk [194.130.48.111]) by mailgate.abacus.co.uk (8.9.3/8.9.3) with ESMTP id OAA01260; Mon, 22 Jan 2001 14:08:29 GMT Message-ID: <3A6C257A.140E27C2@abacus.co.uk> Date: Mon, 22 Jan 2001 12:20:10 +0000 From: Antony T Curtis Organization: Abacus Polar PLC (UK) X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.1.1-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: "Paul A. Howes" Cc: freebsd-stable@FreeBSD.ORG Subject: Re: New Intel NICs... References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Paul A. Howes" wrote: > > 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? ROTFL! Isn't the 82550A UART chips for serial comms? Nothing like a bit of chip numbering to confuse everyone. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 22 6:53:28 2001 Delivered-To: freebsd-stable@freebsd.org Received: from tele-post-20.mail.demon.net (tele-post-20.mail.demon.net [194.217.242.20]) by hub.freebsd.org (Postfix) with ESMTP id 0981137B401; Mon, 22 Jan 2001 06:53:05 -0800 (PST) Received: from calcaphon.demon.co.uk ([193.237.19.5]) by tele-post-20.mail.demon.net with esmtp (Exim 2.12 #2) id 14KiL6-000JsJ-0K; Mon, 22 Jan 2001 14:53:02 +0000 Received: from doug01 (dhcp112.qubesoft.com [192.168.1.112]) by calcaphon.demon.co.uk (8.11.1/8.9.1) with SMTP id f0MEqxT33505; Mon, 22 Jan 2001 14:52:59 GMT (envelope-from dfr@nlsystems.com) Message-ID: <02af01c08482$d2dc9420$7001a8c0@doug01> From: "Doug Rabson" To: "Cameron Grant" , "Warner Losh" Cc: , References: <003401c0833c$39ac3f40$1004020a@darkstar> <200101211929.f0LJT8901098@harmony.village.org> Subject: Re: newpcm/kobj MFC Date: Mon, 22 Jan 2001 14:50:58 -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 ----- Original Message ----- From: "Warner Losh" To: "Cameron Grant" Cc: ; Sent: Sunday, January 21, 2001 7:29 PM Subject: Re: newpcm/kobj MFC > In message <003401c0833c$39ac3f40$1004020a@darkstar> "Cameron Grant" writes: > : unless vetoed for good reason, i intend to MFC kobj support into 4.x and > > Wouldn't the kobj merge break binary compatibility that we're trying > to maintain? As far as I know, Cameron is only merging kobj, not the changes to subr_bus.c which use kobj. The ABI for newbus will not be affected. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 22 7:19:19 2001 Delivered-To: freebsd-stable@freebsd.org Received: from cc762335-a.ebnsk1.nj.home.com (cc762335-a.ebnsk1.nj.home.com [24.3.219.36]) by hub.freebsd.org (Postfix) with SMTP id 00BF837B402 for ; Mon, 22 Jan 2001 07:19:02 -0800 (PST) Received: (qmail 64782 invoked from network); 22 Jan 2001 15:17:51 -0000 Received: from athena.faerun.com (HELO athena) (192.168.0.2) by cc762335-a.ebnsk1.nj.home.com with SMTP; 22 Jan 2001 15:17:51 -0000 Message-Id: <4.2.2.20010122101435.00bdaf00@netmail.home.com> X-Sender: damascus@netmail.home.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Mon, 22 Jan 2001 10:18:21 -0500 To: Maikel Verheijen From: Carroll Kong Subject: Re: Ipfilter version in stable... Cc: stable@FreeBSD.ORG In-Reply-To: <20010122103503.B78003@duckling.worldonline.nl> 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 10:35 AM 1/22/01 +0100, Maikel Verheijen wrote: >Hi all! > >Does anyone know when there will be a new version of ipfilter be integrated >in FreeBSD-stable? The one in FreeBSD (v3.4.8) still has a bug when natting >active ftp connections. > >Of course I can install the newest ipfilter, but I don't want to recompile >and install it after each buildworld + installworld :) > > >TIA, >Maikel Verheijen. I had the same thoughts as you exactly, however, there is a better way. Seems like FreeBSD is more "modular" now, and IPfilter benefits from this as well. Unpack the src, make freebsd4, make minstall; Add ipf_load="YES" to /boot/loader.conf. Make sure IPFILTER is no longer in the kernel. (or else it will load up twice). This seems to expedite the upgrade procedure significantly. -Carroll Kong To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 22 7:25:41 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 3538F37B401 for ; Mon, 22 Jan 2001 07:25:24 -0800 (PST) Received: from onceler.kciLink.com (onceler.kciLink.com [208.184.13.196]) by yertle.kciLink.com (Postfix) with ESMTP id D7F5C2E443 for ; Mon, 22 Jan 2001 10:25:22 -0500 (EST) Received: (from khera@localhost) by onceler.kciLink.com (8.11.1/8.11.1) id f0MFPMI31278; Mon, 22 Jan 2001 10:25:22 -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: <14956.20706.794323.519259@onceler.kciLink.com> Date: Mon, 22 Jan 2001 10:25:22 -0500 To: freebsd-stable@freebsd.org Subject: Re: Required files for Linux emulation In-Reply-To: <5.0.0.25.2.20010120140820.02188bd0@216.67.14.69> References: <5.0.0.25.2.20010120140820.02188bd0@216.67.14.69> 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 >>>>> "FA" == Forrest Aldrich writes: FA> I have a third-party program (Interscan Viruswall, anyone using that on FA> FreeBSD?) that seems to require an additional amount of info to determine FA> the version of Linux supported: FA> grep: /etc/redhat-release: No such file or directory Is that from a shell script? Make sure the shell script runs in linux mode. ie, change /bin/sh to /compat/linux/bin/sh. This usually fixes things up for me. I have this: [onceler]% cat /compat/linux/etc/redhat-release Red Hat Linux release 6.1 (Cartman) [onceler]% uname -a FreeBSD onceler.kciLink.com 4.2-STABLE FreeBSD 4.2-STABLE #0: Mon Jan 15 13:44:07 EST 2001 khera@yertle.kciLink.com:/u/yertle2/usr.obj/amd/onceler/u/onceler1/usr/src/sys/ONCELER i386 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 22 7:55:49 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 9979B37B402 for ; Mon, 22 Jan 2001 07:55:29 -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 f0MFqdE61207 for ; Mon, 22 Jan 2001 09:52:39 -0600 (CST) (envelope-from swb@grasslake.net) Message-ID: <00a601c0848b$e9600ac0$b8209fc0@marlowe> From: "Shawn Barnhart" To: Subject: Non-sequential one-time passwords? Date: Mon, 22 Jan 2001 09:56: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.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'm looking for a way to do one time passwords. S/Key would work great, but when generating several passwords it turns out they have to be used sequentially rather than at random. The sequential nature of S/Key passwords is kind of a problem, because I don't think I can rely on the people giving out the one-time passwords to properly ensure they're given out in sequence and they can't guarantee they will be used in sequence. The basic idea is to have say five accounts, each with a block of 10 one-time passwords. These could be given out on an as-needed basis to freelancers for access to an FTP site. Is there some scheme for doing this or am I SOL? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 22 8: 1:46 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 70C8337B402 for ; Mon, 22 Jan 2001 08:01:29 -0800 (PST) Received: (from kris@localhost) by citusc17.usc.edu (8.11.1/8.11.1) id f0MG4NK88873; Mon, 22 Jan 2001 08:04:23 -0800 (PST) (envelope-from kris) Date: Mon, 22 Jan 2001 08:04:22 -0800 From: Kris Kennaway To: tsikora@powerusersbbs.com Cc: "freebsd-stable@FreeBSD.ORG" Subject: Re: ssh login Message-ID: <20010122080422.A88843@citusc17.usc.edu> References: <3A6B9008.88CCCE91@home.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="cNdxnHkX5QqsyA0e" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3A6B9008.88CCCE91@home.com>; from tsikora@home.com on Sun, Jan 21, 2001 at 08:42:32PM -0500 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --cNdxnHkX5QqsyA0e Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Jan 21, 2001 at 08:42:32PM -0500, Ted Sikora wrote: > I was using the ssh from ports previously. After upgrading and using the > one integrated I no longer can access my other nix machines. I can log > onto FreeBSD fine though. Any ideas? Post some more information, e.g. debugging logs (ssh -v) so we can help you. Kris --=20 NOTE: To fetch an updated copy of my GPG key which has not expired, finger kris@FreeBSD.org --cNdxnHkX5QqsyA0e 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 iD8DBQE6bFoGWry0BWjoQKURArtQAKCfaknwBGv3snWsAWW5TjIW17cFxACgpqX+ WUQiKSKjmvzisxiN3rj+jfc= =XYrS -----END PGP SIGNATURE----- --cNdxnHkX5QqsyA0e-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 22 8: 4:55 2001 Delivered-To: freebsd-stable@freebsd.org Received: from daemon.wilbury.sk (daemon.wilbury.sk [195.168.1.69]) by hub.freebsd.org (Postfix) with SMTP id CB76B37B402 for ; Mon, 22 Jan 2001 08:04:37 -0800 (PST) Received: (qmail 41318 invoked by uid 1000); 22 Jan 2001 16:06:18 -0000 Date: Mon, 22 Jan 2001 17:06:18 +0100 From: Juraj Lutter To: tsikora@powerusersbbs.com Cc: freebsd-stable@freebsd.org Subject: Re: ssh login Message-ID: <20010122170618.M16921@wilbury.sk> References: <3A6B9008.88CCCE91@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: <3A6B9008.88CCCE91@home.com>; from tsikora@home.com on Sun, Jan 21, 2001 at 08:42:32PM -0500 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jan 21, 2001 at 08:42:32PM -0500, Ted Sikora wrote: > I was using the ssh from ports previously. After upgrading and using the > one integrated I no longer can access my other nix machines. I can log > onto FreeBSD fine though. Any ideas? > Perhaps you're missing proper PAM config options. Try add this two lines into your /etc/pam.conf: sshd auth required pam_unix.so sshd session required pam_permit.so somewhere near beginning :-) otis ---------------------------------------------------------------- Juraj Lutter, e-mail: juraj@lutter.sk, URL: http://wilbury.sk/ All I want for Christmas is a Rock And Roll electric guitar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 22 8:13: 1 2001 Delivered-To: freebsd-stable@freebsd.org Received: from ocean.aldridge.com (ocean.aldridge.com [206.180.139.29]) by hub.freebsd.org (Postfix) with ESMTP id 086C337B404 for ; Mon, 22 Jan 2001 08:12:44 -0800 (PST) Received: from aldridge.com (green.gensys.com [206.180.139.1]) by ocean.aldridge.com (8.11.0/8.11.1) with ESMTP id f0MGCbl77554 for ; Mon, 22 Jan 2001 10:12:38 -0600 (CST) Message-ID: <3A6C5BFF.423D1E6A@aldridge.com> Date: Mon, 22 Jan 2001 10:12:47 -0600 From: "David L. Aldridge" Organization: The Aldridge Company X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: ftp.freebsd.org Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG What's up with ftp.freebsd.org being down? -- David L. Aldridge The Aldridge Company 713-403-9150 (fax: 713-621-1826) http://www.aldridge.com/ Powered by Pentium/FreeBSD/Apache - Because it works. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 22 8:24: 3 2001 Delivered-To: freebsd-stable@freebsd.org Received: from pop3.ids.net (pop3.ids.net [155.212.1.107]) by hub.freebsd.org (Postfix) with ESMTP id A855F37B402 for ; Mon, 22 Jan 2001 08:23:42 -0800 (PST) Received: from ids.net (dialup175f.egr-ri.ids.net [155.212.222.175]) by pop3.ids.net (8.10.1/8.10.1) with ESMTP id f0MGNZN22663; Mon, 22 Jan 2001 11:23:35 -0500 (EST) Message-ID: <3A6C5E6C.3E84EAC0@ids.net> Date: Mon, 22 Jan 2001 11:23:08 -0500 From: "Christopher M. Giordano" Reply-To: CGiordano@ids.net X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: stable@FreeBSD.ORG Cc: jdp@polstra.com Subject: Re: preventing cvsup from replacing /usr/ports symlink? References: <200101202028.f0KKSUr80758@saturn.home.ben.com> <20010121021117.A2300@snark.ptc.spbu.ru> <200101210047.f0L0lBq15592@vashon.polstra.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Polstra wrote: > > 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. This happened to me two days ago (jan 20, 1030 AM), and it always seems to occur when re-cvsup'ing following a failed cvsup. In this case, the first attempt failed with a message like: "Updater failed: unable to delete file archivers/arc/Makefile: no such file or directory", which in itself seemed odd, since I was starting with a full copy of the ports tree. Restarting cvsup then filled /usr/ports tree in my /usr filesystem rather than the linked filesystem. I assume the link is deleted upon the first failure, but I have no evidence of this. I know that's _very_ little to go on.... Chris Giordano CGiordano@ids.net -- A man cannot be too careful in the choice of his enemies. -- Oscar Wilde, "Picture of Dorian Gray" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 22 8:45:15 2001 Delivered-To: freebsd-stable@freebsd.org Received: from femail10.sdc1.sfba.home.com (femail10.sdc1.sfba.home.com [24.0.95.106]) by hub.freebsd.org (Postfix) with ESMTP id 835F537B402 for ; Mon, 22 Jan 2001 08:44:58 -0800 (PST) Received: from powerusersbbs.com ([24.2.169.205]) by femail10.sdc1.sfba.home.com (InterMail vM.4.01.03.00 201-229-121) with ESMTP id <20010122164458.GMWB6975.femail10.sdc1.sfba.home.com@powerusersbbs.com> for ; Mon, 22 Jan 2001 08:44:58 -0800 Message-ID: <3A6C6398.B62BE080@powerusersbbs.com> Date: Mon, 22 Jan 2001 11:45:12 -0500 From: Ted Sikora Organization: Jtl Development Group X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en-US, en MIME-Version: 1.0 To: "freebsd-stable@FreeBSD.ORG" Subject: Re: ssh login References: <3A6B9008.88CCCE91@home.com> <20010122170618.M16921@wilbury.sk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Juraj Lutter wrote: > > On Sun, Jan 21, 2001 at 08:42:32PM -0500, Ted Sikora wrote: > > I was using the ssh from ports previously. After upgrading and using the > > one integrated I no longer can access my other nix machines. I can log > > onto FreeBSD fine though. Any ideas? > > > > Perhaps you're missing proper PAM config options. Try add this two > lines into your /etc/pam.conf: > > sshd auth required pam_unix.so > sshd session required pam_permit.so > > somewhere near beginning :-) > > otis > I added the lines... same thing. -- Ted Sikora Jtl Development Group tsikora@powerusersbbs.com Linux the choice of a GNU generation............ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 22 8:49:48 2001 Delivered-To: freebsd-stable@freebsd.org Received: from femail10.sdc1.sfba.home.com (femail10.sdc1.sfba.home.com [24.0.95.106]) by hub.freebsd.org (Postfix) with ESMTP id 7657D37B699 for ; Mon, 22 Jan 2001 08:49:30 -0800 (PST) Received: from powerusersbbs.com ([24.2.169.205]) by femail10.sdc1.sfba.home.com (InterMail vM.4.01.03.00 201-229-121) with ESMTP id <20010122164930.GQJI6975.femail10.sdc1.sfba.home.com@powerusersbbs.com> for ; Mon, 22 Jan 2001 08:49:30 -0800 Message-ID: <3A6C64A7.4BFA4F9E@powerusersbbs.com> Date: Mon, 22 Jan 2001 11:49:43 -0500 From: Ted Sikora Organization: Jtl Development Group X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en-US, en MIME-Version: 1.0 To: "freebsd-stable@FreeBSD.ORG" Subject: Re: XFree86 4.0.2 References: <4.3.2.7.2.20010121013438.00ba9100@nsit-popmail.uchicago.edu> <20010121023208.A63679@citusc17.usc.edu> <3A6B3D84.58831A5@137.org> <20010122112245.A77620@wop21.wop.wtb.tue.nl> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Karel J. Bosschaart" wrote: > > On Sun, Jan 21, 2001 at 01:50:28PM -0600, Chris wrote: > > > > If you are currently running 4.0.1, I would seriously recommend skipping > > this > > minor revision. I have run into a multitude of problems with it, and am now > > back right where I started. > > > > One, is the lack of DRM support for the matrox cards anymore. The kernel > > module has a version number in it, which is less than that required by the > > DRM system. > > > At the moment I'm using XFree86-4.0.2_5 with Matrox G400 and DRM, on 4.2-STABLE. > I could get the correct DRM module version compiled thanks to a bunch of patches > that someone has sent me. Occasionally things lock up and I need to restart > remotely (killing -9 the offending process does not help). This happens only > when using drm. > > > It won't insert the module until you update this--so it appears > > that no one is actually using it. > > FYI, http://wop21.wop.wtb.tue.nl/freebsd/hwaccel.html describes how to install > drm/G400 with XFree86-4.0.1. I'm getting a few hits a day, so I suppose there > is some interest, although the patches are getting only 20 % of the number of > hits on the guidelines, which might be more indicative for the people actually > trying. > > > Another, is that there seem to be delays in the event stream, making > > interactive performance terrible. One example: When I go to move a window, > > I > > start dragging it, moving the outline as I go. Then I unclick, yet the > > frame > > is still visible. I actually have to move the mouse more to get the window > > move to take effect. There are other cases, where it appears to lose events > > all together--like clicking on windows to raise them, or with menus. > > > Hmm, I don't have such troubles. Only minor problem I have, besides above > mentioned drm related things, is that VMware doesn't correctly use Full Screen > mode. > > Karel. > 1 out of 1 hunks failed--saving rejects to programs/Xserver/hw/xfree86/input/joystick/Imakefile.rej >> Patch patch-1 failed to apply cleanly. >> Patch(es) patch-0 applied cleanly. *** Error code 1 I keep getting this error when trying to build XFree86-4.0.2 in FreeBSD-stable. It built fine the beginning of last week on another box. -- Ted Sikora Jtl Development Group tsikora@powerusersbbs.com Linux the choice of a GNU generation............ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 22 8:50:35 2001 Delivered-To: freebsd-stable@freebsd.org Received: from femail10.sdc1.sfba.home.com (femail10.sdc1.sfba.home.com [24.0.95.106]) by hub.freebsd.org (Postfix) with ESMTP id 45DA937B402 for ; Mon, 22 Jan 2001 08:50:09 -0800 (PST) Received: from powerusersbbs.com ([24.2.169.205]) by femail10.sdc1.sfba.home.com (InterMail vM.4.01.03.00 201-229-121) with ESMTP id <20010122165008.GRFW6975.femail10.sdc1.sfba.home.com@powerusersbbs.com> for ; Mon, 22 Jan 2001 08:50:08 -0800 Message-ID: <3A6C64CE.DDA1F400@powerusersbbs.com> Date: Mon, 22 Jan 2001 11:50:22 -0500 From: Ted Sikora Organization: Jtl Development Group X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en-US, en MIME-Version: 1.0 To: "freebsd-stable@FreeBSD.ORG" Subject: Re: ssh login References: <3A6B9008.88CCCE91@home.com> <20010122080422.A88843@citusc17.usc.edu> Content-Type: multipart/mixed; boundary="------------31E5A8BCF8A5BE1D1BE526EC" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------31E5A8BCF8A5BE1D1BE526EC Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Kris Kennaway wrote: > > On Sun, Jan 21, 2001 at 08:42:32PM -0500, Ted Sikora wrote: > > I was using the ssh from ports previously. After upgrading and using the > > one integrated I no longer can access my other nix machines. I can log > > onto FreeBSD fine though. Any ideas? > > Post some more information, e.g. debugging logs (ssh -v) so we can > help you. > > Kris I can connect to my Slackware box but Slack cannot connect to FreeBSD-stable(slack.txt). I cannot connect to any other FreeBSD-stable box with FreeBSD-stable(ssh.txt). -- Ted Sikora Jtl Development Group tsikora@powerusersbbs.com Linux the choice of a GNU generation............ --------------31E5A8BCF8A5BE1D1BE526EC Content-Type: text/plain; charset=us-ascii; name="ssh.txt" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="ssh.txt" bash-2.04# ssh -v 24.2.168.186 SSH Version OpenSSH_2.2.0, protocol versions 1.5/2.0. Compiled with SSL (0x0090581f). debug: Reading configuration data /etc/ssh/ssh_config debug: ssh_connect: getuid 0 geteuid 0 anon 0 debug: Connecting to 24.2.168.186 [24.2.168.186] port 22. debug: Allocated local port 1023. debug: Connection established. debug: Remote protocol version 1.99, remote software version OpenSSH_2.2.0 debug: Local version string SSH-1.5-OpenSSH_2.2.0 debug: Waiting for server public key. debug: Received server public key (768 bits) and host key (1024 bits). The authenticity of host '24.2.168.186' can't be established. RSA key fingerprint is 38:ce:4e:80:99:d0:62:e8:df:c7:89:92:a4:7e:4f:42. Are you sure you want to continue connecting (yes/no)? yes Warning: Permanently added '24.2.168.186' (RSA) to the list of known hosts. debug: Encryption type: 3des debug: Sent encrypted session key. debug: Installing crc compensation attack detector. debug: Received encrypted confirmation. debug: Trying Kerberos V5 authentication. Address 24.2.168.186 maps to c353425-a.htfds1.ct.home.com, but this does not p back to the address - POSSIBLE BREAKIN ATTEMPT! debug: Doing password authentication. root@24.2.168.186's password: Permission denied, please try again. root@24.2.168.186's password: --------------31E5A8BCF8A5BE1D1BE526EC Content-Type: text/plain; charset=us-ascii; name="slack.txt" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="slack.txt" warning: Development-time debugging not compiled in. warning: To enable, configure with --enable-debug and recompile. debug: hostname is '24.2.168.186'. debug: Unable to open /root/.ssh2/ssh2_config warning: Development-time debugging not compiled in. warning: To enable, configure with --enable-debug and recompile. debug: connecting to 24.2.168.186... debug: entering event loop debug: ssh_client_wrap: creating transport protocol debug: Ssh2Client/sshclient.c:1015/ssh_client_wrap: creating userauth protocol debug: Ssh2Client/sshclient.c:349/keycheck_key_match: Host key found from databa se. debug: Unable to open /root/.ssh2/identification debug: Ssh2AuthClient/sshauthc.c:304/ssh_authc_completion_proc: Method 'publicke y' disabled. debug: Ssh2AuthPasswdClient/authc-passwd.c:82/ssh_client_auth_passwd: Starting p assword query... root's password: debug: Ssh2AuthPasswdClient/authc-passwd.c:82/ssh_client_auth_passwd: Starting p assword query... root's password: --------------31E5A8BCF8A5BE1D1BE526EC-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 22 8:53:25 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.hcvlny.cv.net (mx1.hcvlny.cv.net [167.206.112.76]) by hub.freebsd.org (Postfix) with ESMTP id CDBB537B402 for ; Mon, 22 Jan 2001 08:53:07 -0800 (PST) Received: from s1.optonline.net (s1.optonline.net [167.206.112.6]) by mx1.hcvlny.cv.net (8.10.2/8.10.2) with ESMTP id f0MGr7i21715; Mon, 22 Jan 2001 11:53:07 -0500 (EST) Received: from optonline.net (ool-18be012f.dyn.optonline.net [24.190.1.47]) by s1.optonline.net (8.10.2/8.10.2) with ESMTP id f0MGr6u28444; Mon, 22 Jan 2001 11:53:07 -0500 (EST) Message-ID: <3A6C6572.DF137C54@optonline.net> Date: Mon, 22 Jan 2001 11:53:06 -0500 From: trini0 X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.2-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: Carroll Kong , FreeBSD Stable Subject: Re: Ipfilter version in stable... References: <4.2.2.20010122101435.00bdaf00@netmail.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 Very interesting. I came across that ftp problem, and was considering upping to 3.4.16, but I didn't want to go through the rebuilding of ipfilter everytime I upgrade FBSD. I quickly glanced at the man page for loader.conf and it seems that you can have modules & flags set in the file. So I just got to check on the rest of ipfilter, and see if ipnat, and ipmon can be modules. So is performance good using the module route instead of putting it in the kernel?? Carroll Kong wrote: > At 10:35 AM 1/22/01 +0100, Maikel Verheijen wrote: > >Hi all! > > > >Does anyone know when there will be a new version of ipfilter be integrated > >in FreeBSD-stable? The one in FreeBSD (v3.4.8) still has a bug when natting > >active ftp connections. > > > >Of course I can install the newest ipfilter, but I don't want to recompile > >and install it after each buildworld + installworld :) > > > > > >TIA, > >Maikel Verheijen. > > I had the same thoughts as you exactly, however, there is a better > way. Seems like FreeBSD is more "modular" now, and IPfilter benefits from > this as well. > > Unpack the src, make freebsd4, make minstall; Add > > ipf_load="YES" > > to /boot/loader.conf. Make sure IPFILTER is no longer in the kernel. (or > else it will load up twice). This seems to expedite the upgrade procedure > significantly. > > -Carroll Kong > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- _____________________________ | trini0 | | | / ) | Systems Administrator | / / | Network Engineer | ( ( | email ==> | (((\ \> |/ ) trini0@optonline.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 22 8:53:36 2001 Delivered-To: freebsd-stable@freebsd.org Received: from daemon.wilbury.sk (daemon.wilbury.sk [195.168.1.69]) by hub.freebsd.org (Postfix) with SMTP id C513F37B404 for ; Mon, 22 Jan 2001 08:53:18 -0800 (PST) Received: (qmail 45586 invoked by uid 1000); 22 Jan 2001 16:55:00 -0000 Date: Mon, 22 Jan 2001 17:55:00 +0100 From: Juraj Lutter To: Ted Sikora Cc: freebsd-stable@freebsd.org Subject: Re: ssh login Message-ID: <20010122175500.O16921@wilbury.sk> References: <3A6B9008.88CCCE91@home.com> <20010122080422.A88843@citusc17.usc.edu> <3A6C64CE.DDA1F400@powerusersbbs.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3A6C64CE.DDA1F400@powerusersbbs.com>; from tsikora@powerusersbbs.com on Mon, Jan 22, 2001 at 11:50:22AM -0500 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jan 22, 2001 at 11:50:22AM -0500, Ted Sikora wrote: > warning: Development-time debugging not compiled in. > warning: To enable, configure with --enable-debug and recompile. > debug: hostname is '24.2.168.186'. > debug: Unable to open /root/.ssh2/ssh2_config > warning: Development-time debugging not compiled in. > warning: To enable, configure with --enable-debug and recompile. > debug: connecting to 24.2.168.186... > debug: entering event loop > debug: ssh_client_wrap: creating transport protocol > debug: Ssh2Client/sshclient.c:1015/ssh_client_wrap: creating userauth protocol > debug: Ssh2Client/sshclient.c:349/keycheck_key_match: Host key found from databa > se. > debug: Unable to open /root/.ssh2/identification > debug: Ssh2AuthClient/sshauthc.c:304/ssh_authc_completion_proc: Method 'publicke > y' disabled. > debug: Ssh2AuthPasswdClient/authc-passwd.c:82/ssh_client_auth_passwd: Starting p > assword query... > root's password: > debug: Ssh2AuthPasswdClient/authc-passwd.c:82/ssh_client_auth_passwd: Starting p > assword query... > root's password: > Seems like you don't have root login enabled in your /etc/ssh/sshd_config. Try to enable or try to log in as normal user not as root. Root login can be possibly dangerous. otis ---------------------------------------------------------------- Juraj Lutter, e-mail: juraj@lutter.sk, URL: http://wilbury.sk/ All I want for Christmas is a Rock And Roll electric guitar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 22 8:54:13 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 5AEEA37B69C for ; Mon, 22 Jan 2001 08:53:51 -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 LAA31613; Mon, 22 Jan 2001 11:53:46 -0500 (EST) Received: (from sto@localhost) by feta.isds.duke.edu (8.11.1/8.11.1) id f0MGrkG57985; Mon, 22 Jan 2001 11:53:46 -0500 (EST) (envelope-from sto) Date: Mon, 22 Jan 2001 11:53:46 -0500 From: "Sean O'Connell" To: Ted Sikora Cc: FreeBSD stable Subject: Re: ssh login Message-ID: <20010122115346.E57772@stat.Duke.EDU> Reply-To: "Sean O'Connell" Mail-Followup-To: Sean O'Connell , Ted Sikora , FreeBSD stable References: <3A6B9008.88CCCE91@home.com> <20010122080422.A88843@citusc17.usc.edu> <3A6C64CE.DDA1F400@powerusersbbs.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3A6C64CE.DDA1F400@powerusersbbs.com>; from tsikora@powerusersbbs.com on Mon, Jan 22, 2001 at 11:50:22AM -0500 X-Organization: Institute of Statistics and Decision Sciences Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ted Sikora stated: : Kris Kennaway wrote: : > : > On Sun, Jan 21, 2001 at 08:42:32PM -0500, Ted Sikora wrote: : > > I was using the ssh from ports previously. After upgrading and using the : > > one integrated I no longer can access my other nix machines. I can log : > > onto FreeBSD fine though. Any ideas? : > : > Post some more information, e.g. debugging logs (ssh -v) so we can : > help you. : > : > Kris : : I can connect to my Slackware box but Slack cannot connect to : FreeBSD-stable(slack.txt). I cannot connect to any other FreeBSD-stable : box with FreeBSD-stable(ssh.txt). : : Permission denied, please try again. : root@24.2.168.186's password: I think the problem is that you are doing it as root. grep -i root /etc/ssh/sshd_config /etc/ssh/sshd_config:PermitRootLogin no 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 Mon Jan 22 9: 8:11 2001 Delivered-To: freebsd-stable@freebsd.org Received: from eve.framatome.fr (eve.framatome.fr [195.101.50.66]) by hub.freebsd.org (Postfix) with ESMTP id 271C137B69B for ; Mon, 22 Jan 2001 09:07:52 -0800 (PST) Received: from localhost (ubc@localhost) by eve.framatome.fr (8.9.3/8.9.3) with ESMTP id SAA70855; Mon, 22 Jan 2001 18:07:07 +0100 (CET) (envelope-from ubc@paris.framatome.fr) Date: Mon, 22 Jan 2001 18:07:07 +0100 (CET) From: Claude Buisson X-Sender: ubc@eve.framatome.fr To: Carroll Kong Cc: Maikel Verheijen , stable@FreeBSD.ORG Subject: Re: Ipfilter version in stable... In-Reply-To: <4.2.2.20010122101435.00bdaf00@netmail.home.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 Mon, 22 Jan 2001, Carroll Kong wrote: > At 10:35 AM 1/22/01 +0100, Maikel Verheijen wrote: > >Hi all! > > > >Does anyone know when there will be a new version of ipfilter be integrated > >in FreeBSD-stable? The one in FreeBSD (v3.4.8) still has a bug when natting > >active ftp connections. > > > >Of course I can install the newest ipfilter, but I don't want to recompile > >and install it after each buildworld + installworld :) > > > > > >TIA, > >Maikel Verheijen. > > I had the same thoughts as you exactly, however, there is a better > way. Seems like FreeBSD is more "modular" now, and IPfilter benefits from > this as well. > > Unpack the src, make freebsd4, make minstall; Add I have done it, but the patches to ip_input.c, ip_output.c, in_proto.c in /sys/netinet are rejected. Claude Buisson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 22 9:16:23 2001 Delivered-To: freebsd-stable@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 7979237B69B; Mon, 22 Jan 2001 09:16:01 -0800 (PST) Received: from newsguy.com (p33-dn02kiryunisiki.gunma.ocn.ne.jp [211.0.245.98]) by peach.ocn.ne.jp (8.9.1a/OCN/) with ESMTP id CAA23591; Tue, 23 Jan 2001 02:15:51 +0900 (JST) Message-ID: <3A6C6A34.59D392F@newsguy.com> Date: Tue, 23 Jan 2001 02:13:24 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR MIME-Version: 1.0 To: "Louis A. Mamakos" Cc: Cameron Grant , Kris Kennaway , arch@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: newpcm/kobj MFC References: <003401c0833c$39ac3f40$1004020a@darkstar> <20010121153904.B74751@citusc17.usc.edu> <200101220104.f0M142O04580@whizzo.transsys.com> <001b01c0840f$b30ea070$1004020a@darkstar> <200101220139.f0M1d1O05133@whizzo.transsys.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Louis A. Mamakos" wrote: > > > to the best of my knowledge, there exist 5 drivers not in the tree now, all > > of which have kobjified versions available and 4 of which will be entering > > the tree soon. i know of no commercial newpcm drivers. > > Well, there you go. Is changing an unused API an incompatability? Yes, it is... :-( It impacts reputation. OTOH, that has yet to prove a big problem for Linux, for instance. :-) -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org capo@a.crazy.bsdconspiracy.net "There is no spoon." -- Kiki To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 22 9:36:36 2001 Delivered-To: freebsd-stable@freebsd.org Received: from eve.framatome.fr (eve.framatome.fr [195.101.50.66]) by hub.freebsd.org (Postfix) with ESMTP id 05CFC37B404 for ; Mon, 22 Jan 2001 09:36:18 -0800 (PST) Received: from localhost (ubc@localhost) by eve.framatome.fr (8.9.3/8.9.3) with ESMTP id SAA71705; Mon, 22 Jan 2001 18:34:34 +0100 (CET) (envelope-from ubc@paris.framatome.fr) Date: Mon, 22 Jan 2001 18:34:33 +0100 (CET) From: Claude Buisson X-Sender: ubc@eve.framatome.fr To: Carroll Kong Cc: Maikel Verheijen , stable@FreeBSD.ORG Subject: Re: Ipfilter version in stable... 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 Mon, 22 Jan 2001, Claude Buisson wrote: > > > On Mon, 22 Jan 2001, Carroll Kong wrote: > > > At 10:35 AM 1/22/01 +0100, Maikel Verheijen wrote: > > >Hi all! > > > > > >Does anyone know when there will be a new version of ipfilter be integrated > > >in FreeBSD-stable? The one in FreeBSD (v3.4.8) still has a bug when natting > > >active ftp connections. > > > > > >Of course I can install the newest ipfilter, but I don't want to recompile > > >and install it after each buildworld + installworld :) > > > > > > > > >TIA, > > >Maikel Verheijen. > > > > I had the same thoughts as you exactly, however, there is a better > > way. Seems like FreeBSD is more "modular" now, and IPfilter benefits from > > this as well. > > > > Unpack the src, make freebsd4, make minstall; Add > > I have done it, but the patches to ip_input.c, ip_output.c, in_proto.c > in /sys/netinet are rejected. > > Claude Buisson > On 4.2-STABLE (2001/01/19) the make minstall may (must ?) be omitted: I just loaded the module and ran ipf without changing my kernel. Claude Buisson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 22 9:38:20 2001 Delivered-To: freebsd-stable@freebsd.org Received: from femail9.sdc1.sfba.home.com (femail9.sdc1.sfba.home.com [24.0.95.89]) by hub.freebsd.org (Postfix) with ESMTP id 792C137B404 for ; Mon, 22 Jan 2001 09:38:02 -0800 (PST) Received: from powerusersbbs.com ([24.2.169.205]) by femail9.sdc1.sfba.home.com (InterMail vM.4.01.03.00 201-229-121) with ESMTP id <20010122173802.KANJ7869.femail9.sdc1.sfba.home.com@powerusersbbs.com>; Mon, 22 Jan 2001 09:38:02 -0800 Message-ID: <3A6C7007.134CD18F@powerusersbbs.com> Date: Mon, 22 Jan 2001 12:38:15 -0500 From: Ted Sikora Organization: Jtl Development Group X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en-US, en MIME-Version: 1.0 To: Juraj Lutter , "freebsd-stable@FreeBSD.ORG" Subject: Re: ssh login References: <3A6B9008.88CCCE91@home.com> <20010122080422.A88843@citusc17.usc.edu> <3A6C64CE.DDA1F400@powerusersbbs.com> <20010122175500.O16921@wilbury.sk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Juraj Lutter wrote: > > On Mon, Jan 22, 2001 at 11:50:22AM -0500, Ted Sikora wrote: > > > warning: Development-time debugging not compiled in. > > warning: To enable, configure with --enable-debug and recompile. > > debug: hostname is '24.2.168.186'. > > debug: Unable to open /root/.ssh2/ssh2_config > > warning: Development-time debugging not compiled in. > > warning: To enable, configure with --enable-debug and recompile. > > debug: connecting to 24.2.168.186... > > debug: entering event loop > > debug: ssh_client_wrap: creating transport protocol > > debug: Ssh2Client/sshclient.c:1015/ssh_client_wrap: creating userauth protocol > > debug: Ssh2Client/sshclient.c:349/keycheck_key_match: Host key found from databa > > se. > > debug: Unable to open /root/.ssh2/identification > > debug: Ssh2AuthClient/sshauthc.c:304/ssh_authc_completion_proc: Method 'publicke > > y' disabled. > > debug: Ssh2AuthPasswdClient/authc-passwd.c:82/ssh_client_auth_passwd: Starting p > > assword query... > > root's password: > > debug: Ssh2AuthPasswdClient/authc-passwd.c:82/ssh_client_auth_passwd: Starting p > > assword query... > > root's password: > > > > Seems like you don't have root login enabled in your > /etc/ssh/sshd_config. Try to enable or try to log in as normal user > not as root. Root login can be possibly dangerous. > > otis That was it. How can root be dangerous in ssh.. isn't that why it exists? Or would using su be better? I usually use ssh to remotely administer the servers. -- Ted Sikora Jtl Development Group tsikora@powerusersbbs.com Linux the choice of a GNU generation............ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 22 9:42:39 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 DB49137B400 for ; Mon, 22 Jan 2001 09:42:18 -0800 (PST) Received: from pir by moek.pir.net with local (Exim) id 14Kkyv-00054n-00 for freebsd-stable@FreeBSD.ORG; Mon, 22 Jan 2001 12:42:17 -0500 Date: Mon, 22 Jan 2001 12:42:17 -0500 From: Peter Radcliffe To: "freebsd-stable@FreeBSD.ORG" Subject: Re: ssh login Message-ID: <20010122124217.H14001@pir.net> Reply-To: stable@freebsd.org Mail-Followup-To: "freebsd-stable@FreeBSD.ORG" References: <3A6B9008.88CCCE91@home.com> <20010122080422.A88843@citusc17.usc.edu> <3A6C64CE.DDA1F400@powerusersbbs.com> <20010122175500.O16921@wilbury.sk> <3A6C7007.134CD18F@powerusersbbs.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3A6C7007.134CD18F@powerusersbbs.com>; from tsikora@powerusersbbs.com on Mon, Jan 22, 2001 at 12:38:15PM -0500 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 Ted Sikora probably said: > That was it. How can root be dangerous in ssh.. isn't that why it > exists? Or would using su be better? I usually use ssh to remotely > administer the servers. Log in as a normal user and su to root. It's the same reason most UNIXes don't allow remote logins as root; if you allow passworded root logins you only have one password between a remote user and root access. If you make them su (the correct way, in most people's minds) then you have two passwords between them and root. Personally I restrict ssh access even further. P. -- pir pir@pir.net pir@net.tufts.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 22 9:43:22 2001 Delivered-To: freebsd-stable@freebsd.org Received: from daemon.wilbury.sk (daemon.wilbury.sk [195.168.1.69]) by hub.freebsd.org (Postfix) with SMTP id C5F4C37B402 for ; Mon, 22 Jan 2001 09:43:01 -0800 (PST) Received: (qmail 49602 invoked by uid 1000); 22 Jan 2001 17:44:42 -0000 Date: Mon, 22 Jan 2001 18:44:42 +0100 From: Juraj Lutter To: Ted Sikora Cc: freebsd-stable@freebsd.org Subject: Re: ssh login Message-ID: <20010122184442.C48980@wilbury.sk> References: <3A6B9008.88CCCE91@home.com> <20010122080422.A88843@citusc17.usc.edu> <3A6C64CE.DDA1F400@powerusersbbs.com> <20010122175500.O16921@wilbury.sk> <3A6C7007.134CD18F@powerusersbbs.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3A6C7007.134CD18F@powerusersbbs.com>; from tsikora@powerusersbbs.com on Mon, Jan 22, 2001 at 12:38:15PM -0500 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jan 22, 2001 at 12:38:15PM -0500, Ted Sikora wrote: > > That was it. How can root be dangerous in ssh.. isn't that why it > exists? Or would using su be better? I usually use ssh to remotely > administer the servers. Yes, using ``su'' or ``sudo'' is more elegant solution than remote root login. If I think about hcked boxes and patched ssh clients, it makes me scarry to login as root remote :-) otis ---------------------------------------------------------------- Juraj Lutter, e-mail: juraj@lutter.sk, URL: http://wilbury.sk/ All I want for Christmas is a Rock And Roll electric guitar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 22 9:45:50 2001 Delivered-To: freebsd-stable@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id A956A37B698; Mon, 22 Jan 2001 09:45:30 -0800 (PST) Received: from newsguy.com (p33-dn02kiryunisiki.gunma.ocn.ne.jp [211.0.245.98]) by peach.ocn.ne.jp (8.9.1a/OCN/) with ESMTP id CAA27607; Tue, 23 Jan 2001 02:45:08 +0900 (JST) Message-ID: <3A6C7111.80E5663F@newsguy.com> Date: Tue, 23 Jan 2001 02:42:41 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR MIME-Version: 1.0 To: Dominic Mitchell Cc: Roelof Osinga , Bjoern Fischer , freebsd-stable@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: PAM (was: Re: MAIL set by whom?) References: <3A6A50F3.307C9E06@nisser.com> <20010121103324.A297@frolic.no-support.loc> <3A6B042E.659C716D@nisser.com> <20010122094647.A7853@semantico.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dominic Mitchell wrote: > > On Sun, Jan 21, 2001 at 04:45:50PM +0100, Roelof Osinga wrote: > > Grand gesture. Laudable even. Yeah, that PAM sure seems to've > > become popular. The Courier IMAP port also insisted upon its > > installation. Insisted in that fiddling with the makefile only > > resulted in failure to configure. But that's a whole different > > story. > > Would it be a good idea to start using /etc/pam.d ala RedHat, instead of > the monolithic /etc/pam.conf? > > As far as I can see the support is already there, it's just not being > used due to the presence of the /etc/pam.conf. > > This would make installing PAM entries far easier for the ports. Ports shouldn't touch /etc. Does the existance of /etc/pam.conf precludes /usr/local/etc/pam.d from working? -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org capo@a.crazy.bsdconspiracy.net "There is no spoon." -- Kiki To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 22 9:52:22 2001 Delivered-To: freebsd-stable@freebsd.org Received: from cc762335-a.ebnsk1.nj.home.com (cc762335-a.ebnsk1.nj.home.com [24.3.219.36]) by hub.freebsd.org (Postfix) with SMTP id 264A937B404 for ; Mon, 22 Jan 2001 09:51:50 -0800 (PST) Received: (qmail 66727 invoked from network); 22 Jan 2001 17:50:39 -0000 Received: from athena.faerun.com (HELO athena) (192.168.0.2) by cc762335-a.ebnsk1.nj.home.com with SMTP; 22 Jan 2001 17:50:39 -0000 Message-Id: <4.2.2.20010122124113.00bdcf00@netmail.home.com> X-Sender: damascus@netmail.home.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Mon, 22 Jan 2001 12:51:50 -0500 To: trini0 From: Carroll Kong Subject: Re: Ipfilter version in stable... Cc: FreeBSD Stable In-Reply-To: <3A6C6572.DF137C54@optonline.net> References: <4.2.2.20010122101435.00bdaf00@netmail.home.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:53 AM 1/22/01 -0500, trini0 wrote: >Very interesting. I came across that ftp problem, and was considering upping >to 3.4.16, but I didn't want to go through the rebuilding of ipfilter >everytime >I upgrade FBSD. I quickly glanced at the man page for loader.conf and it >seems >that you can have modules & flags set in the file. So I just got to check on >the rest of ipfilter, and see if ipnat, and ipmon can be modules. So is >performance good using the module route instead of putting it in the kernel?? > >Carroll Kong wrote: > > > I had the same thoughts as you exactly, however, there is a better > > way. Seems like FreeBSD is more "modular" now, and IPfilter benefits from > > this as well. > > > > Unpack the src, make freebsd4, make minstall; Add > > > > ipf_load="YES" > > > > to /boot/loader.conf. Make sure IPFILTER is no longer in the kernel. (or > > else it will load up twice). This seems to expedite the upgrade procedure > > significantly. > > > > -Carroll Kong Fairly certain you only need to load the IPFilter module and calls like ipfilter_enable="YES" ipnat_enable="YES" ipmon_enable="YES" ipmon_program="/usr/sbin/ipmon" all work fine. Maybe I am getting lucky? I have not really stressed the particular system I am using it for. I would imagine modules would incur a slight run time penalty, but I doubt it is anything significant. Also, it seems easier for upgrades. I tended to get nasty kernel src mismatches and what not when I tried to compile ipfilter into the kernel. Maybe it was just me. And with the rate that IPFilter gets updated, seems nice to know that this method of upgrading works nearly 100% of the time with very simple compile commands. Oh no... I just overlooked my commands. It should be unpack the src, make freebsd4, make install-bsd. Terribly sorry for the misinformation! -Carroll Kong To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 22 10: 2:28 2001 Delivered-To: freebsd-stable@freebsd.org Received: from hugo10.ka.punkt.de (unknown [194.77.232.254]) by hub.freebsd.org (Postfix) with ESMTP id 3DC1C37B401 for ; Mon, 22 Jan 2001 10:02:06 -0800 (PST) Received: (from ry93@localhost) by hugo10.ka.punkt.de (8.9.3/8.9.3) id TAA51972; Mon, 22 Jan 2001 19:01:55 +0100 (CET) (envelope-from ry93) From: "Patrick M. Hausen" Message-Id: <200101221801.TAA51972@hugo10.ka.punkt.de> Subject: Re: ssh login In-Reply-To: <20010122184442.C48980@wilbury.sk> from Juraj Lutter at "Jan 22, 2001 06:44:42 pm" To: otis@wilbury.sk (Juraj Lutter) Date: Mon, 22 Jan 2001 19:01:55 +0100 (CET) Cc: tsikora@powerusersbbs.com (Ted Sikora), 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 Hi all! Juraj Lutter wrote: > On Mon, Jan 22, 2001 at 12:38:15PM -0500, Ted Sikora wrote: > > > > That was it. How can root be dangerous in ssh.. isn't that why it > > exists? Or would using su be better? I usually use ssh to remotely > > administer the servers. > > Yes, using ``su'' or ``sudo'' is more elegant solution than remote > root login. If I think about hcked boxes and patched ssh clients, it > makes me scarry to login as root remote :-) Well, using su would not save you from a patched client recording your keystrokes. But, to provide a different answer to the original question: ssh with root login enabled opens the system to remote dictionary attacks, i.e. guessing the root password. Of course, you'd never choose a root password that could easily be guessed, now, would you? ;-)) If you have to login with your regular account first, the attacker has to guess a valid login name first, then mount another attack to get root privileges. The only account that will be on _every_ (well, almost every) Unix system is "root", so there's no need to guess that one. It's common NT admin practice to rename the "Administrator" account. And this _does_ improve security against remote attacks, so it's not as moronic as it sounded to me when I first heard about it. Unfortunately MS made it rather easy to find out the name of that particular account, once you successfully authenticated to the NT domain in question, so beware of all "insiders" ;-) Just one more level of indirection for the script kiddies to cope with. Patrick -- --- WEB ISS GmbH - Scheffelstr. 17a - 76135 Karlsruhe - 0721/9109-0 --- ------ Patrick M. Hausen - Technical Director - hausen@punkt.de ------- "Contrary to popular belief, penguins are not the salvation of modern technology. Neither do they throw parties for the urban proletariat." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 22 10: 7:55 2001 Delivered-To: freebsd-stable@freebsd.org Received: from gw.nectar.com (gw.nectar.com [208.42.49.153]) by hub.freebsd.org (Postfix) with ESMTP id A7BB137B400; Mon, 22 Jan 2001 10:07:30 -0800 (PST) Received: from hamlet.nectar.com (hamlet.nectar.com [10.0.1.102]) by gw.nectar.com (Postfix) with ESMTP id 1C3C4193E4; Mon, 22 Jan 2001 12:07:30 -0600 (CST) Received: (from nectar@localhost) by hamlet.nectar.com (8.11.1/8.9.3) id f0MI7UL93735; Mon, 22 Jan 2001 12:07:30 -0600 (CST) (envelope-from nectar@spawn.nectar.com) Date: Mon, 22 Jan 2001 12:07:30 -0600 From: "Jacques A. Vidrine" To: "Daniel C. Sobral" Cc: Dominic Mitchell , Roelof Osinga , Bjoern Fischer , freebsd-stable@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: PAM (was: Re: MAIL set by whom?) Message-ID: <20010122120729.B93660@hamlet.nectar.com> Mail-Followup-To: "Jacques A. Vidrine" , "Daniel C. Sobral" , Dominic Mitchell , Roelof Osinga , Bjoern Fischer , freebsd-stable@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG References: <3A6A50F3.307C9E06@nisser.com> <20010121103324.A297@frolic.no-support.loc> <3A6B042E.659C716D@nisser.com> <20010122094647.A7853@semantico.com> <3A6C7111.80E5663F@newsguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3A6C7111.80E5663F@newsguy.com>; from dcs@newsguy.com on Tue, Jan 23, 2001 at 02:42:41AM +0900 X-Url: http://www.nectar.com/ Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jan 23, 2001 at 02:42:41AM +0900, Daniel C. Sobral wrote: > Ports shouldn't touch /etc. > > Does the existance of /etc/pam.conf precludes /usr/local/etc/pam.d from > working? Other way around. From the man page (the last sentence is even underlined :-) Alternatively, the configuration can be set by individual configuration files located in the /etc/pam.d/ directory. The presence of this directory will cause PAM to ignore /etc/pam.conf. -- Jacques Vidrine / n@nectar.com / jvidrine@verio.net / nectar@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 22 10:19: 2 2001 Delivered-To: freebsd-stable@freebsd.org Received: from daemon.wilbury.sk (daemon.wilbury.sk [195.168.1.69]) by hub.freebsd.org (Postfix) with SMTP id 5DA7037B400 for ; Mon, 22 Jan 2001 10:18:44 -0800 (PST) Received: (qmail 51586 invoked by uid 1000); 22 Jan 2001 18:20:25 -0000 Date: Mon, 22 Jan 2001 19:20:25 +0100 From: Juraj Lutter To: "Patrick M. Hausen" Cc: Ted Sikora , freebsd-stable@FreeBSD.ORG Subject: Re: ssh login Message-ID: <20010122192025.A51214@wilbury.sk> References: <20010122184442.C48980@wilbury.sk> <200101221801.TAA51972@hugo10.ka.punkt.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200101221801.TAA51972@hugo10.ka.punkt.de>; from hausen@punkt.de on Mon, Jan 22, 2001 at 07:01:55PM +0100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jan 22, 2001 at 07:01:55PM +0100, Patrick M. Hausen wrote: > > Well, using su would not save you from a patched client recording > your keystrokes. > I know that F-Secure SSH client (the old one 16 and 32bit supporting ssh1 only) is keylogger-proof and it does not start and crashes with a strange error at startup (tested on Win95). otis ---------------------------------------------------------------- Juraj Lutter, e-mail: juraj@lutter.sk, URL: http://wilbury.sk/ All I want for Christmas is a Rock And Roll electric guitar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 22 10:34:30 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 E864B37B402 for ; Mon, 22 Jan 2001 10:34:12 -0800 (PST) Received: (from daemon@localhost) by point.osg.gov.bc.ca (8.8.7/8.8.8) id KAA28552; Mon, 22 Jan 2001 10:33:38 -0800 Received: from passer.osg.gov.bc.ca(142.32.110.29) via SMTP by point.osg.gov.bc.ca, id smtpda28550; Mon Jan 22 10:33:30 2001 Received: (from uucp@localhost) by passer.osg.gov.bc.ca (8.11.2/8.9.1) id f0MIXPH29630; Mon, 22 Jan 2001 10:33:25 -0800 (PST) Received: from cwsys9.cwsent.com(10.2.2.1), claiming to be "cwsys.cwsent.com" via SMTP by passer9.cwsent.com, id smtpdJ29628; Mon Jan 22 10:32:30 2001 Received: (from uucp@localhost) by cwsys.cwsent.com (8.11.2/8.9.1) id f0MIWTm67585; Mon, 22 Jan 2001 10:32:29 -0800 (PST) Message-Id: <200101221832.f0MIWTm67585@cwsys.cwsent.com> Received: from localhost.cwsent.com(127.0.0.1), claiming to be "cwsys" via SMTP by localhost.cwsent.com, id smtpdi67581; Mon Jan 22 10:32:03 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-Sender: schubert To: Maikel Verheijen Cc: stable@FreeBSD.ORG Subject: Re: Ipfilter version in stable... In-reply-to: Your message of "Mon, 22 Jan 2001 10:35:03 +0100." <20010122103503.B78003@duckling.worldonline.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 22 Jan 2001 10:32:03 -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20010122103503.B78003@duckling.worldonline.nl>, Maikel Verheijen wr ites: > Hi all! > > Does anyone know when there will be a new version of ipfilter be integrated > in FreeBSD-stable? The one in FreeBSD (v3.4.8) still has a bug when natting > active ftp connections. You'll need to discuss that with Darren Reed, as he has FreeBSD commit privileges. > > Of course I can install the newest ipfilter, but I don't want to recompile > and install it after each buildworld + installworld :) I use the following procedure to install the latest IP Filter during buildworld/installworld. 1. Extract the latest IP Filter in /usr/src/contrib. 2. Rename /usr/src/contrib/ipfilter to ipfilter.orig 3. Symlink ipfilter to ip_fil3.4.16 (example). 4. Apply any local patches I may have to IP Filter (I currently have no local IP Filter patches). 5. cd ipfilter && ./FreeBSD-4.0/kinstall 6. Buildworld as usual. 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 22 10:58:20 2001 Delivered-To: freebsd-stable@freebsd.org Received: from cmpharm.ucsf.edu (cmpharm.ucsf.edu [128.218.67.18]) by hub.freebsd.org (Postfix) with ESMTP id 0DBCE37B401 for ; Mon, 22 Jan 2001 10:58:02 -0800 (PST) Received: from piglet.ucsf.edu (steve@piglet.ucsf.edu [128.218.67.20]) by cmpharm.ucsf.edu (8.10.1/8.10.1) with ESMTP id f0MIc6A25832 for ; Mon, 22 Jan 2001 10:38:06 -0800 (PST) Received: (from steve@localhost) by piglet.ucsf.edu (8.9.3/8.9.3) id KAA279379 for freebsd-stable@FreeBSD.ORG; Mon, 22 Jan 2001 10:58:01 -0800 (PST) Date: Mon, 22 Jan 2001 10:58:01 -0800 From: Steve Sizemore To: freebsd-stable@FreeBSD.ORG Subject: Are pipes broken in -STABLE? Message-ID: <20010122105801.A277561@cmpharm.ucsf.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG For the last week or so, all of the kernels that I've built have been having trouble with pipes. Port extractions fail, makewhatis fails, all sorts of things generate error messages. The simplest example is tar - e.g. # tar tzvf /usr/ports/distfiles/cfengine-1.6.1.tar.gz >/dev/null gzip: stdout: Broken pipe tar: child returned status 1 gunzip, followed by tar xf, works just fine, so I don't think it's a gzip or tar problem. Besides, other things fail which don't (apparently) use gzip or tar, but do use pipes. And, not all pipes, fail, but I haven't been able to determine what causes some to fail. This occurs on both intel and alpha. I have to believe that this is something local to my setup - I haven't seen anyone else discuss it on the list. Still I've tried almost everything I can think of, even dropping back to a GENERIC kernel, and still see the same behavior. Right now, I'm re-cvsupping the sources, and I'll try building GENERIC from virgin sources, but, in the meanwhile, does anyone have a clue what might be the problem? Thanks. Steve -- ----------------------------------------------#-----#--#####--------------- # # # # Steve Sizemore # # # Dept. of Cellular and Molecular Pharmacology # # # Box 0450, Room HSE-1285 # # # University of California Medical Center # # # # 513 Parnassus Avenue ##### ##### ##### ####### San Francisco CA 94143-0450 # # # # # steve@cmpharm.ucsf.edu ##### ##### (415) 476-6987 FAX: (415) 476-6515 # # # # # -------------------------------------------------------------#####--#------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 22 11: 2:39 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 63ABC37B401 for ; Mon, 22 Jan 2001 11:02:21 -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 OAA03821; Mon, 22 Jan 2001 14:02:20 -0500 (EST) Received: (from sto@localhost) by feta.isds.duke.edu (8.11.1/8.11.1) id f0MJ2KC58145; Mon, 22 Jan 2001 14:02:20 -0500 (EST) (envelope-from sto) Date: Mon, 22 Jan 2001 14:02:20 -0500 From: "Sean O'Connell" To: Steve Sizemore Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Are pipes broken in -STABLE? Message-ID: <20010122140220.G57772@stat.Duke.EDU> Reply-To: "Sean O'Connell" Mail-Followup-To: Sean O'Connell , Steve Sizemore , freebsd-stable@FreeBSD.ORG References: <20010122105801.A277561@cmpharm.ucsf.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010122105801.A277561@cmpharm.ucsf.edu>; from steve@cmpharm.ucsf.edu on Mon, Jan 22, 2001 at 10:58:01AM -0800 X-Organization: Institute of Statistics and Decision Sciences Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Steve Sizemore stated: : For the last week or so, all of the kernels that I've built have been : having trouble with pipes. Port extractions fail, makewhatis fails, : all sorts of things generate error messages. The simplest example is : tar - e.g. : # tar tzvf /usr/ports/distfiles/cfengine-1.6.1.tar.gz >/dev/null : : gzip: stdout: Broken pipe : tar: child returned status 1 : : gunzip, followed by tar xf, works just fine, so I don't think it's a : gzip or tar problem. Besides, other things fail which don't : (apparently) use gzip or tar, but do use pipes. And, not all pipes, : fail, but I haven't been able to determine what causes some to fail. : : This occurs on both intel and alpha. : : I have to believe that this is something local to my setup - I haven't : seen anyone else discuss it on the list. Still I've tried almost : everything I can think of, even dropping back to a GENERIC kernel, and : still see the same behavior. Right now, I'm re-cvsupping the sources, : and I'll try building GENERIC from virgin sources, but, in the : meanwhile, does anyone have a clue what might be the problem? Steve- Is this over ssh connection? I think something weird is happening with pipes and openssh 2.3.0p1 MFC. Not sure if it has been addressed or not. 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 Mon Jan 22 11: 3:48 2001 Delivered-To: freebsd-stable@freebsd.org Received: from implode.root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id 54AB937B402 for ; Mon, 22 Jan 2001 11:03:29 -0800 (PST) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id KAA14072; Mon, 22 Jan 2001 10:55:03 -0800 (PST) Message-Id: <200101221855.KAA14072@implode.root.com> To: "David L. Aldridge" Cc: freebsd-stable@FreeBSD.ORG Subject: Re: ftp.freebsd.org In-reply-to: Your message of "Mon, 22 Jan 2001 10:12:47 CST." <3A6C5BFF.423D1E6A@aldridge.com> From: David Greenman Reply-To: dg@root.com Date: Mon, 22 Jan 2001 10:55:02 -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >What's up with ftp.freebsd.org being down? There is a network or hardware problem of some kind; I'm working with our ISP to troubleshoot it. I don't have an ETR. -DG David Greenman Co-founder, The FreeBSD Project - http://www.freebsd.org President, TeraSolutions, Inc. - http://www.terasolutions.com Pave the road of life with opportunities. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 22 11:12:25 2001 Delivered-To: freebsd-stable@freebsd.org Received: from cmpharm.ucsf.edu (cmpharm.ucsf.edu [128.218.67.18]) by hub.freebsd.org (Postfix) with ESMTP id 7E6F437B401 for ; Mon, 22 Jan 2001 11:12:05 -0800 (PST) Received: from piglet.ucsf.edu (steve@piglet.ucsf.edu [128.218.67.20]) by cmpharm.ucsf.edu (8.10.1/8.10.1) with ESMTP id f0MIqAA05688; Mon, 22 Jan 2001 10:52:10 -0800 (PST) Received: (from steve@localhost) by piglet.ucsf.edu (8.9.3/8.9.3) id LAA275279; Mon, 22 Jan 2001 11:12:04 -0800 (PST) Date: Mon, 22 Jan 2001 11:12:04 -0800 From: Steve Sizemore To: "Sean O'Connell" , freebsd-stable@FreeBSD.ORG Subject: Re: Are pipes broken in -STABLE? Message-ID: <20010122111204.B277561@cmpharm.ucsf.edu> References: <20010122105801.A277561@cmpharm.ucsf.edu> <20010122140220.G57772@stat.Duke.EDU> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010122140220.G57772@stat.Duke.EDU>; from sean@stat.Duke.EDU on Mon, Jan 22, 2001 at 02:02:20PM -0500 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jan 22, 2001 at 02:02:20PM -0500, Sean O'Connell wrote: > Steve Sizemore stated: > : For the last week or so, all of the kernels that I've built have been > : having trouble with pipes. Port extractions fail, makewhatis fails, > : all sorts of things generate error messages. The simplest example is > : tar - e.g. > : # tar tzvf /usr/ports/distfiles/cfengine-1.6.1.tar.gz >/dev/null > : > : gzip: stdout: Broken pipe > : tar: child returned status 1 > : > : gunzip, followed by tar xf, works just fine, so I don't think it's a > : gzip or tar problem. Besides, other things fail which don't > : (apparently) use gzip or tar, but do use pipes. And, not all pipes, > : fail, but I haven't been able to determine what causes some to fail. > : > : This occurs on both intel and alpha. > : > : I have to believe that this is something local to my setup - I haven't > : seen anyone else discuss it on the list. Still I've tried almost > : everything I can think of, even dropping back to a GENERIC kernel, and > : still see the same behavior. Right now, I'm re-cvsupping the sources, > : and I'll try building GENERIC from virgin sources, but, in the > : meanwhile, does anyone have a clue what might be the problem? > > Steve- > > Is this over ssh connection? I think something weird is happening > with pipes and openssh 2.3.0p1 MFC. > > Not sure if it has been addressed or not. > > 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 Yes, in fact, it is. I hadn't even considered ssh as a possibility, since almost everything I do is over an ssh connection. I just tried some things while logged into the console, and everything seems to work just fine. Thanks for the clue. Now, who do we need to bother to get this addressed? Steve -- ----------------------------------------------#-----#--#####--------------- # # # # Steve Sizemore # # # Dept. of Cellular and Molecular Pharmacology # # # Box 0450, Room HSE-1285 # # # University of California Medical Center # # # # 513 Parnassus Avenue ##### ##### ##### ####### San Francisco CA 94143-0450 # # # # # steve@cmpharm.ucsf.edu ##### ##### (415) 476-6987 FAX: (415) 476-6515 # # # # # -------------------------------------------------------------#####--#------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 22 11:18:24 2001 Delivered-To: freebsd-stable@freebsd.org Received: from sttlpop5.sttl.uswest.net (sttlpop5.sttl.uswest.net [206.81.192.5]) by hub.freebsd.org (Postfix) with SMTP id 150AD37B400 for ; Mon, 22 Jan 2001 11:18:05 -0800 (PST) Received: (qmail 15473 invoked by alias); 22 Jan 2001 19:02:49 -0000 Delivered-To: fixup-freebsd-stable@freebsd.org@fixme Received: (qmail 9950 invoked by uid 0); 22 Jan 2001 18:51:26 -0000 Received: from www.a6l.net (HELO a6l.net) (63.229.13.49) by sttlpop5.sttl.uswest.net with SMTP; 22 Jan 2001 18:51:26 -0000 Received: (qmail 60465 invoked by uid 1002); 22 Jan 2001 18:51:42 -0000 To: freebsd-stable@freebsd.org Subject: building a debug world From: Kevin Mills Date: 22 Jan 2001 10:51:42 -0800 Message-ID: <85r91v7741.fsf@diablo.in.a6l.net> Lines: 10 X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just got through building my world and my kernel using "-g", hoping that I would be able to step into system calls and the like. This doesn't seem to be the case - attempting to step into "printf()", for example, produced the same behavior as in a non-debug world. How do I go about making this work? Thanks! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 22 11:20: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 21B6637B400 for ; Mon, 22 Jan 2001 11:19:55 -0800 (PST) Received: by peitho.fxp.org (Postfix, from userid 1501) id 55F6B1360C; Mon, 22 Jan 2001 14:19:49 -0500 (EST) Date: Mon, 22 Jan 2001 14:19:49 -0500 From: Chris Faulhaber To: Kevin Mills Cc: freebsd-stable@freebsd.org Subject: Re: building a debug world Message-ID: <20010122141949.B51247@peitho.fxp.org> Mail-Followup-To: Chris Faulhaber , Kevin Mills , freebsd-stable@freebsd.org References: <85r91v7741.fsf@diablo.in.a6l.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <85r91v7741.fsf@diablo.in.a6l.net>; from kmills@a6l.net on Mon, Jan 22, 2001 at 10:51:42AM -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jan 22, 2001 at 10:51:42AM -0800, Kevin Mills wrote: > > I just got through building my world and my kernel using "-g", hoping > that I would be able to step into system calls and the like. This doesn't > seem to be the case - attempting to step into "printf()", for example, > produced the same behavior as in a non-debug world. > > How do I go about making this work? > You also probably don't want to strip the binaries hint: STRIP= -- 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 22 11:47:13 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 066B837B402; Mon, 22 Jan 2001 11:46:55 -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 f0MJkn865092; Mon, 22 Jan 2001 14:46:49 -0500 (EST) (envelope-from mike@sentex.net) Message-Id: <5.0.1.4.0.20010122143930.01ecd780@marble.sentex.ca> X-Sender: mdtpop@marble.sentex.ca X-Mailer: QUALCOMM Windows Eudora Version 5.0.1 Date: Mon, 22 Jan 2001 14:40:54 -0500 To: Steve Sizemore , freebsd-stable@FreeBSD.ORG From: Mike Tancsa Subject: Re: Are pipes broken in -STABLE? (recent ssh commits) Cc: green@FreeBSD.ORG In-Reply-To: <20010122111204.B277561@cmpharm.ucsf.edu> References: <20010122140220.G57772@stat.Duke.EDU> <20010122105801.A277561@cmpharm.ucsf.edu> <20010122140220.G57772@stat.Duke.EDU> 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:12 AM 1/22/01 -0800, Steve Sizemore wrote: > > > > Not sure if it has been addressed or not. > > > > 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 > >Yes, in fact, it is. I hadn't even considered ssh as a possibility, >since almost everything I do is over an ssh connection. I just tried >some things while logged into the console, and everything seems to >work just fine. > >Thanks for the clue. Now, who do we need to bother to get this >addressed? makewhatis on make world has similar problems with ssh. If you telnet localhost, or login as root on the console, it gets around the issue. But it sure looks specific to the recent ssh commits. ---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 22 11:54: 6 2001 Delivered-To: freebsd-stable@freebsd.org Received: from vexpert.dbai.tuwien.ac.at (vexpert.dbai.tuwien.ac.at [128.130.111.12]) by hub.freebsd.org (Postfix) with ESMTP id AC47737B69B; Mon, 22 Jan 2001 11:53:42 -0800 (PST) Received: from taygeta.dbai.tuwien.ac.at (taygeta [128.130.111.77]) by vexpert.dbai.tuwien.ac.at (8.11.1/8.11.1) with ESMTP id f0MJree23896; Mon, 22 Jan 2001 20:53:40 +0100 (MET) Received: from localhost (pfeifer@localhost) by taygeta.dbai.tuwien.ac.at (8.11.1/8.11.1) with ESMTP id f0MJrft83106; Mon, 22 Jan 2001 20:53:41 +0100 (CET) (envelope-from pfeifer@dbai.tuwien.ac.at) X-Authentication-Warning: taygeta.dbai.tuwien.ac.at: pfeifer owned process doing -bs Date: Mon, 22 Jan 2001 20:53:41 +0100 (CET) From: Gerald Pfeifer To: , Subject: libgcc_pic is gone (affects Wine port) 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 Due to a serious bug in the port of GCC used in the base system (see ) I and probably others had to explicitly link against libgcc_pic. This bug has been fixed (around 4.2-RELEASE), but also libgcc_pic is gone now, though I'm not sure whether that is directly related. So, what is a "portable" way of compiling sources both on 4.1-RELEASE and 5.0-CURRENT? On the former I need libgcc_pic, on the latter there is no libgcc_pic at all. Or, as this mainly affects the Wine port, should I just ignore older versions of FreeBSD? Does 4.2-RELEASE already have the fix to PR 21983? Gerald -- Gerald "Jerry" pfeifer@dbai.tuwien.ac.at http://www.dbai.tuwien.ac.at/~pfeifer/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 22 12:38: 6 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 3595E37B404 for ; Mon, 22 Jan 2001 12:37:44 -0800 (PST) Received: (qmail 25673 invoked by uid 0); 22 Jan 2001 20:37:43 -0000 Received: from p3ee21646.dip.t-dialin.net (HELO speedy.gsinet) (62.226.22.70) by mail.gmx.net (mail08) with SMTP; 22 Jan 2001 20:37:43 -0000 Received: (from sittig@localhost) by speedy.gsinet (8.8.8/8.8.8) id TAA25319 for freebsd-stable@freebsd.org; Mon, 22 Jan 2001 19:32:20 +0100 Date: Mon, 22 Jan 2001 19:32:19 +0100 From: Gerhard Sittig To: freebsd-stable@freebsd.org Subject: Re: ssh problem Message-ID: <20010122193219.A253@speedy.gsinet> Mail-Followup-To: freebsd-stable@freebsd.org References: <20010121152247.A74407@citusc17.usc.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from robert@rootprompt.net on Sun, Jan 21, 2001 at 05:28:36PM -0800 Organization: System Defenestrators Inc. Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jan 21, 2001 at 17:28 -0800, Robert Banniza wrote: > > It is better to install the new file when cvsup'ing or merge > the old and new file together? This is assuming the user hasn't > entered anything special into the file. I did an install on the > last cvsup rather than merging. I was somewhat confused when it > asked me whether I wanted to install the file on the right or > the file on the left. Shouldn't they be one in the same if > merged? Any info. appreciated... Yes, _after_ merging all the stuff is in one file. But you seem to have a wrong idea of mergemaster merging the stuff for you. Administration is what you have to do yourself. The other scenario (a machine setting up itself) will result in an "I'm sorry, Dave ..." But the machine could sometimes _aid_ you in this task -- that's what mergemaster is meant for. You might want to read the sdiff(1) manpage and maybe the mergemaster(8) manpage. There are configuration changes your computer *cannot* merge reliably in the absence of AI. So the admin has to decide what to do should configuration have changed in the source tree. This brings us to your question "is it better to install or to merge?". The clear answer is "it depends". When you haven't touched the file yourself (like rc.* scripts or periodic jobs) you probably want to 'i'nstall the new version to get all the benefits of the development which took place. If you have touched the file and the source tree has an older (original) version - like /etc/ttys, /etc/motd, usually /etc/master.passwd, too - you probably don't want to erase your customization and decide to 'd'elete the /var/tmp/temproot file. In case the source tree has an update *and* you changed the file yourself in the system, you will have to merge these changes. Either by 'm'erging or by putting it back for later manual intervention (write down a note and really do come back!). This could apply to master.passwd (rarely, in case the source brings new users with it and you have created accounts on your own) or rc.* scripts or MAKEDEV you have fiddled with yourself or skeleton files and such. You always should be able to judge the consequences of your action in these steps. When in doubt, read the available online doc. One positive side effect is that you learn what was changed to get a certain effect. It makes the system more transparent to you after some cycles. 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 22 12:58: 2 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 7377537B698 for ; Mon, 22 Jan 2001 12:57:45 -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 f0MKvI912239; Mon, 22 Jan 2001 13:57:18 -0700 (MST) (envelope-from imp@harmony.village.org) Message-Id: <200101222057.f0MKvI912239@harmony.village.org> To: Antony T Curtis Subject: Re: New Intel NICs... Cc: "Paul A. Howes" , freebsd-stable@FreeBSD.ORG In-reply-to: Your message of "Mon, 22 Jan 2001 12:20:10 GMT." <3A6C257A.140E27C2@abacus.co.uk> References: <3A6C257A.140E27C2@abacus.co.uk> Date: Mon, 22 Jan 2001 13:57:18 -0700 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <3A6C257A.140E27C2@abacus.co.uk> Antony T Curtis writes: : "Paul A. Howes" wrote: : > : > 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? : : ROTFL! Isn't the 82550A UART chips for serial comms? : Nothing like a bit of chip numbering to confuse everyone. The 8250 is an ancient UART chip. It begat the 16450 (becayuse 82*2 is 164 and 50 means uart :-). Which begat the 16550, the 16650, the 16750 and I think the 16850. Plus clones, knock offs, macro cells, and the whole nine yards of imitation. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 22 12:59:33 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 59C3B37B402 for ; Mon, 22 Jan 2001 12:59:13 -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 f0MKxA912270; Mon, 22 Jan 2001 13:59:10 -0700 (MST) (envelope-from imp@harmony.village.org) Message-Id: <200101222059.f0MKxA912270@harmony.village.org> To: Ted Sikora Subject: Re: ssh login Cc: "freebsd-stable@FreeBSD.ORG" In-reply-to: Your message of "Mon, 22 Jan 2001 11:45:12 EST." <3A6C6398.B62BE080@powerusersbbs.com> References: <3A6C6398.B62BE080@powerusersbbs.com> <3A6B9008.88CCCE91@home.com> <20010122170618.M16921@wilbury.sk> Date: Mon, 22 Jan 2001 13:59:09 -0700 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <3A6C6398.B62BE080@powerusersbbs.com> Ted Sikora writes: : I added the lines... same thing. From UPDATING: 20010112: Important new FreeBSD-version stuff: PAM support has been worked in, partially from the "Unix" OpenSSH version. This requires adding the following in pam.conf: sshd auth sufficient pam_skey.so sshd auth required pam_unix.so try_first_pass sshd session required pam_permit.so Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 22 13: 3:49 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 7BC8637B6A1 for ; Mon, 22 Jan 2001 13:03:31 -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 f0ML1G912295; Mon, 22 Jan 2001 14:01:16 -0700 (MST) (envelope-from imp@harmony.village.org) Message-Id: <200101222101.f0ML1G912295@harmony.village.org> To: Ted Sikora Subject: Re: ssh login Cc: Juraj Lutter , "freebsd-stable@FreeBSD.ORG" In-reply-to: Your message of "Mon, 22 Jan 2001 12:38:15 EST." <3A6C7007.134CD18F@powerusersbbs.com> References: <3A6C7007.134CD18F@powerusersbbs.com> <3A6B9008.88CCCE91@home.com> <20010122080422.A88843@citusc17.usc.edu> <3A6C64CE.DDA1F400@powerusersbbs.com> <20010122175500.O16921@wilbury.sk> Date: Mon, 22 Jan 2001 14:01:16 -0700 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <3A6C7007.134CD18F@powerusersbbs.com> Ted Sikora writes: : That was it. How can root be dangerous in ssh.. isn't that why it : exists? Or would using su be better? I usually use ssh to remotely : administer the servers. Using su would be better. Root can be dangerous in ssh because it exposes your machines to outside agents that are able to login as root. It can be made to be allowed in the config file, but isn't by default due to this danger. Once you've set things up to allow only strong authentication methods for root, it is likely safe to remove it. However, it is even safer to use sudo or su to grant root access. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 22 13: 6:23 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 9964637B6A1 for ; Mon, 22 Jan 2001 13:06:02 -0800 (PST) Received: (from daemon@localhost) by point.osg.gov.bc.ca (8.8.7/8.8.8) id NAA28943; Mon, 22 Jan 2001 13:00:42 -0800 Received: from passer.osg.gov.bc.ca(142.32.110.29) via SMTP by point.osg.gov.bc.ca, id smtpda28941; Mon Jan 22 13:00:39 2001 Received: (from uucp@localhost) by passer.osg.gov.bc.ca (8.11.2/8.9.1) id f0ML0Y130862; Mon, 22 Jan 2001 13:00:34 -0800 (PST) Received: from cwsys9.cwsent.com(10.2.2.1), claiming to be "cwsys.cwsent.com" via SMTP by passer9.cwsent.com, id smtpdq30830; Mon Jan 22 12:59:34 2001 Received: (from uucp@localhost) by cwsys.cwsent.com (8.11.2/8.9.1) id f0MKxXx68194; Mon, 22 Jan 2001 12:59:33 -0800 (PST) Message-Id: <200101222059.f0MKxXx68194@cwsys.cwsent.com> Received: from localhost.cwsent.com(127.0.0.1), claiming to be "cwsys" via SMTP by localhost.cwsent.com, id smtpdZ68183; Mon Jan 22 12:58:39 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-Sender: schubert To: Juraj Lutter Cc: Ted Sikora , freebsd-stable@FreeBSD.ORG Subject: Re: ssh login In-reply-to: Your message of "Mon, 22 Jan 2001 18:44:42 +0100." <20010122184442.C48980@wilbury.sk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 22 Jan 2001 12:58:38 -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20010122184442.C48980@wilbury.sk>, Juraj Lutter writes: > On Mon, Jan 22, 2001 at 12:38:15PM -0500, Ted Sikora wrote: > > > > That was it. How can root be dangerous in ssh.. isn't that why it > > exists? Or would using su be better? I usually use ssh to remotely > > administer the servers. > > Yes, using ``su'' or ``sudo'' is more elegant solution than remote > root login. If I think about hcked boxes and patched ssh clients, it > makes me scarry to login as root remote :-) The problem with sudo is that you still have one password protecting root. Sudo does support OTP through S/Key and OPIE. With appropriate measures to ensure you don't paint yourself into a corner, this solution looks quite appealing. 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 22 13:33:12 2001 Delivered-To: freebsd-stable@freebsd.org Received: from tele-post-20.mail.demon.net (tele-post-20.mail.demon.net [194.217.242.20]) by hub.freebsd.org (Postfix) with ESMTP id CFDBA37B402 for ; Mon, 22 Jan 2001 13:32:54 -0800 (PST) Received: from shootthemlater.demon.co.uk ([194.222.93.84] helo=cerebus.parse.net) by tele-post-20.mail.demon.net with esmtp (Exim 2.12 #2) id 14Koa5-00048j-0K; Mon, 22 Jan 2001 21:32:53 +0000 Received: from wbra0013.cognos.com ([10.0.0.3] helo=acm.org) by cerebus.parse.net with esmtp (Exim 3.16 #1) id 14Kmm1-000AA5-00; Mon, 22 Jan 2001 19:37:05 +0000 Message-ID: <3A6C8BCC.FA4A8DB6@acm.org> Date: Mon, 22 Jan 2001 19:36:44 +0000 From: David Goddard X-Mailer: Mozilla 4.75 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: cjclark@alum.mit.edu Cc: stable@FreeBSD.ORG Subject: Re: dmesg/security check output wierdness References: <3A6B09E2.EA269488@acm.org> <20010121143324.U10761@rfx-216-196-73-168.users.reflex> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Crist J. Clark" wrote: ... > The dmesg(8) is stored in a finite buffer. Once full, as more stuff > gets shoved in, other stuff falls out (really it gets overwritten, > it's a circular buffer, but same thing). The stuff that falls out, > does not do so all that gracefully. That is, it does not get dropped > whole lines at a time. For example, ... That's a great answer - thanks for taking the time to elaborate on that point. Dave To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 22 13:45:23 2001 Delivered-To: freebsd-stable@freebsd.org Received: from sttlpop5.sttl.uswest.net (sttlpop5.sttl.uswest.net [206.81.192.5]) by hub.freebsd.org (Postfix) with SMTP id A7FE237B69F for ; Mon, 22 Jan 2001 13:45:03 -0800 (PST) Received: (qmail 26392 invoked by alias); 22 Jan 2001 21:45:02 -0000 Delivered-To: fixup-freebsd-stable@freebsd.org@fixme Received: (qmail 26339 invoked by uid 0); 22 Jan 2001 21:45:01 -0000 Received: from www.a6l.net (HELO a6l.net) (63.229.13.49) by sttlpop5.sttl.uswest.net with SMTP; 22 Jan 2001 21:45:01 -0000 Received: (qmail 62232 invoked by uid 1002); 22 Jan 2001 21:45:18 -0000 To: "Chris Faulhaber" Cc: freebsd-stable@freebsd.org Subject: Re: building a debug world References: <85r91v7741.fsf@diablo.in.a6l.net> <20010122141949.B51247@peitho.fxp.org> From: Kevin Mills Date: 22 Jan 2001 13:45:17 -0800 In-Reply-To: "Chris Faulhaber"'s message of "Mon, 22 Jan 2001 14:19:49 -0500" Message-ID: <85ofwzntw2.fsf@diablo.in.a6l.net> Lines: 23 X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Chris Faulhaber" writes: > On Mon, Jan 22, 2001 at 10:51:42AM -0800, Kevin Mills wrote: > > > > I just got through building my world and my kernel using "-g", hoping > > that I would be able to step into system calls and the like. This doesn't > > seem to be the case - attempting to step into "printf()", for example, > > produced the same behavior as in a non-debug world. > > > > How do I go about making this work? > > > > You also probably don't want to strip the binaries > hint: STRIP= OK... is there somewhere I can set this globally? I did a quick grep and didn't find many Makefiles with STRIP defined. Mostly contrib/bind and a few other places under gnu/usr.bin. Am I looking in the right place(s)? Thanks. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 22 13:54:43 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 1F30937B6A4 for ; Mon, 22 Jan 2001 13:54:22 -0800 (PST) Received: by peitho.fxp.org (Postfix, from userid 1000) id 0390413613; Mon, 22 Jan 2001 16:54:15 -0500 (EST) Date: Mon, 22 Jan 2001 16:54:15 -0500 From: Chris Faulhaber To: Kevin Mills Cc: freebsd-stable@freebsd.org Subject: Re: building a debug world Message-ID: <20010122165415.A28683@peitho.fxp.org> Mail-Followup-To: Chris Faulhaber , Kevin Mills , freebsd-stable@freebsd.org References: <85r91v7741.fsf@diablo.in.a6l.net> <20010122141949.B51247@peitho.fxp.org> <85ofwzntw2.fsf@diablo.in.a6l.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <85ofwzntw2.fsf@diablo.in.a6l.net>; from kmills@a6l.net on Mon, Jan 22, 2001 at 01:45:17PM -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jan 22, 2001 at 01:45:17PM -0800, Kevin Mills wrote: > "Chris Faulhaber" writes: > > > On Mon, Jan 22, 2001 at 10:51:42AM -0800, Kevin Mills wrote: > > > > > > I just got through building my world and my kernel using "-g", hoping > > > that I would be able to step into system calls and the like. This doesn't > > > seem to be the case - attempting to step into "printf()", for example, > > > produced the same behavior as in a non-debug world. > > > > > > How do I go about making this work? > > > > > > > You also probably don't want to strip the binaries > > hint: STRIP= > > OK... is there somewhere I can set this globally? I did a quick grep and > didn't find many Makefiles with STRIP defined. Mostly contrib/bind and a few > other places under gnu/usr.bin. Am I looking in the right place(s)? > /etc/make.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 Mon Jan 22 15:12:41 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 BFF9D37B6B8; Mon, 22 Jan 2001 15:12:20 -0800 (PST) Received: from jesup.eng.tvol.net ([10.32.2.26]) by mail.wgate.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21) id CX5HR0CC; Mon, 22 Jan 2001 18:12:20 -0500 Reply-To: Randell Jesup To: current@FreeBSD.ORG Cc: stable@FreeBSD.ORG Subject: Re: sysinstall.8 Breaking buildworld References: <20010111220021.C79365@strontium.scientia.demon.co.uk> <20010111174332.B74480@dragon.nuxi.com> From: Randell Jesup Date: 22 Jan 2001 18:15:24 -0500 In-Reply-To: "David O'Brien"'s message of "Thu, 11 Jan 2001 17:43:32 -0800" Message-ID: User-Agent: Gnus/5.0807 (Gnus v5.8.7) 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 "David O'Brien" writes: >On Thu, Jan 11, 2001 at 02:38:55PM -0800, John Baldwin wrote: >> Erm, sysinstall can be used as a replacement for fdisk and disklabel, >> both of which are in /sbin. In fact, in 4.2 the only tool you can >> realistically use to splat a virgin disklabel onto a slice w/o weird >> hoop jumping that isn't documented _is_ sysinstall. disklabel should >> have that fixed by 4.3, however. > >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. A full set of disklabel patches to support MB, GB, KB, %, and * (everything not spoken for elsewhere) for sizes (and * for offsets to allow disklabel to calculate them for you), etc are in Warner's hands. (I got annoyed at it one evening...) Now, if Warner would commit them.... :-) (Matt has looked at the patch also.) They also have improved error checking, etc. -- Randell Jesup, Worldgate Communications, ex-Scala, ex-Amiga OS team ('88-94) rjesup@wgate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 22 15:14: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 9D4D437B6C5 for ; Mon, 22 Jan 2001 15:13:47 -0800 (PST) Received: (qmail 31068 invoked by uid 0); 22 Jan 2001 23:13:41 -0000 Received: from unknown (HELO urx.com) (206.159.132.160) by mail.urx.com with SMTP; 22 Jan 2001 23:13:41 -0000 Message-ID: <3A6CBEA4.9A942CBC@urx.com> Date: Mon, 22 Jan 2001 15:13:40 -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: Steve Sizemore Cc: Sean O'Connell , freebsd-stable@FreeBSD.ORG Subject: Re: Are pipes broken in -STABLE? References: <20010122105801.A277561@cmpharm.ucsf.edu> <20010122140220.G57772@stat.Duke.EDU> <20010122111204.B277561@cmpharm.ucsf.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Steve Sizemore wrote: > > On Mon, Jan 22, 2001 at 02:02:20PM -0500, Sean O'Connell wrote: > > Steve Sizemore stated: > > : For the last week or so, all of the kernels that I've built have been > > : having trouble with pipes. Port extractions fail, makewhatis fails, > > : all sorts of things generate error messages. The simplest example is > > : tar - e.g. > > : # tar tzvf /usr/ports/distfiles/cfengine-1.6.1.tar.gz >/dev/null > > : > > : gzip: stdout: Broken pipe > > : tar: child returned status 1 > > : > > : gunzip, followed by tar xf, works just fine, so I don't think it's a > > : gzip or tar problem. Besides, other things fail which don't > > : (apparently) use gzip or tar, but do use pipes. And, not all pipes, > > : fail, but I haven't been able to determine what causes some to fail. > > : > > : This occurs on both intel and alpha. > > : > > : I have to believe that this is something local to my setup - I haven't > > : seen anyone else discuss it on the list. Still I've tried almost > > : everything I can think of, even dropping back to a GENERIC kernel, and > > : still see the same behavior. Right now, I'm re-cvsupping the sources, > > : and I'll try building GENERIC from virgin sources, but, in the > > : meanwhile, does anyone have a clue what might be the problem? > > > > Steve- > > > > Is this over ssh connection? I think something weird is happening > > with pipes and openssh 2.3.0p1 MFC. > > > > Not sure if it has been addressed or not. > > > > 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 > > Yes, in fact, it is. I hadn't even considered ssh as a possibility, > since almost everything I do is over an ssh connection. I just tried > some things while logged into the console, and everything seems to > work just fine. > > Thanks for the clue. Now, who do we need to bother to get this > addressed? Well, the commits were by green@freebsd.org. It was a complete replacement from what I can see. We first noticed the side effect on the 14th. Kent > > Steve > -- > ----------------------------------------------#-----#--#####--------------- > # # # # > Steve Sizemore # # # > Dept. of Cellular and Molecular Pharmacology # # # > Box 0450, Room HSE-1285 # # # > University of California Medical Center # # # # > 513 Parnassus Avenue ##### ##### ##### ####### > San Francisco CA 94143-0450 # # # > # # > steve@cmpharm.ucsf.edu ##### ##### > (415) 476-6987 FAX: (415) 476-6515 # # > # # # > -------------------------------------------------------------#####--#------ > > 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 Mon Jan 22 15:37:55 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 31FA037B404 for ; Mon, 22 Jan 2001 15:37:36 -0800 (PST) Received: from nisser.com (roelof [10.0.0.2]) by nisser.com (8.9.3/8.9.2) with ESMTP id AAA01614; Tue, 23 Jan 2001 00:37:14 +0100 (CET) (envelope-from roelof@nisser.com) Message-ID: <3A6CC42A.D228D56D@nisser.com> Date: Tue, 23 Jan 2001 00:37:14 +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: Timothy Legant Cc: freebsd-stable@FreeBSD.ORG Subject: Re: MAIL set by whom? References: <3A6A50F3.307C9E06@nisser.com> <20010121223513.A76438@mail.catseye.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Timothy Legant wrote: > > ... > Mutt handles all the rest. My MAIL setting is not relevant. Mutt's > handling of Maildirs is excellent. People using mboxes sometimes have > difficulties detecting new mail with Mutt, since using another tool > (like grep or various biffs) can change the access time. Maildirs don't > suffer from this problem at all. > > Good luck! Thx! That's a whole lot of information! Useful info to boot. I need to safe it for a rainy day, alas. It works for now, in that I can read my mail. So can the users. Now back to putting the remaining fires out :). 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 Mon Jan 22 15:45:41 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 0A57437B69F; Mon, 22 Jan 2001 15:45:20 -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 f0MNj6913586; Mon, 22 Jan 2001 16:45:07 -0700 (MST) (envelope-from imp@harmony.village.org) Message-Id: <200101222345.f0MNj6913586@harmony.village.org> To: Randell Jesup Subject: Re: sysinstall.8 Breaking buildworld Cc: current@FreeBSD.ORG, stable@FreeBSD.ORG In-reply-to: Your message of "22 Jan 2001 18:15:24 EST." References: <20010111220021.C79365@strontium.scientia.demon.co.uk> <20010111174332.B74480@dragon.nuxi.com> Date: Mon, 22 Jan 2001 16:45:06 -0700 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Randell Jesup writes: : A full set of disklabel patches to support MB, GB, KB, %, and * : (everything not spoken for elsewhere) for sizes (and * for offsets to allow : disklabel to calculate them for you), etc are in Warner's hands. (I got : annoyed at it one evening...) Now, if Warner would commit them.... :-) : (Matt has looked at the patch also.) I've looked at them, and I have found someone with more time than I have to review and commit them. They should be going in soon, unless there's problems that I've not encountered. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 22 16: 3:15 2001 Delivered-To: freebsd-stable@freebsd.org Received: from easystreet01.easystreet.com (easystreet.com [206.26.36.40]) by hub.freebsd.org (Postfix) with ESMTP id 9DA0E37B69E for ; Mon, 22 Jan 2001 16:02:55 -0800 (PST) Received: from jasonweb ([206.129.94.232]) by easystreet01.easystreet.com (8.9.3/8.9.3) with SMTP id QAA07918 for ; Mon, 22 Jan 2001 16:02:54 -0800 (PST) From: "Jason Watkins" To: "Freebsd-Stable" Subject: ftp logins Date: Mon, 22 Jan 2001 16:05:01 -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.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Disposition-Notification-To: "Jason Watkins" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Since rebuilding from 4.1 release to -stable, I've had a curious problem with ftp logins. Users which should be allowed to log into ftp will get a denial message immedately after entrying the login name, the password prompt is never given. I'm not all that familiar with freebsd, however the users (or groups) are not in /etc/ftpusers banlist. Most of the users are configured with tcsh as their shell, none are in /etc/ftpchroot. I've since built and installed wu-ftpd-2.6.0. Now users are prompted for a password, however, are still denied login. Newly created users work just fine. Existing users can login via ssh, etc just fine. I've asked some other more knowledgeable friends to look at this as well, and they can't figure out what the problem is either. It does appear that someone inadvertantly enabled anonymous ftp, and some warezer did a speed test, decided it was to slow to use as a dump, and moved on. It doesn't appear he did anything more nefarious, but I can't be absolutely sure. Any ideas? jason watkins jwatkins@firstplan.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 22 16: 7:56 2001 Delivered-To: freebsd-stable@freebsd.org Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (Postfix) with ESMTP id 5F56537B69E for ; Mon, 22 Jan 2001 16:07:39 -0800 (PST) Received: (from smap@localhost) by whistle.com (8.10.0/8.10.0) id f0N07co02167; Mon, 22 Jan 2001 16:07:38 -0800 (PST) Received: from pau-amma.whistle.com( 207.76.205.64) by whistle.com via smap (V2.0) id xma002164; Mon, 22 Jan 2001 16:07:28 -0800 Received: (from dhw@localhost) by pau-amma.whistle.com (8.11.1/8.11.1) id f0N07SF54213; Mon, 22 Jan 2001 16:07:28 -0800 (PST) Date: Mon, 22 Jan 2001 16:07:28 -0800 (PST) From: David Wolfskill Message-Id: <200101230007.f0N07SF54213@pau-amma.whistle.com> To: freebsd-stable@FreeBSD.ORG, jwatkins@firstplan.com Subject: Re: ftp logins In-Reply-To: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >From: "Jason Watkins" >Date: Mon, 22 Jan 2001 16:05:01 -0800 >Since rebuilding from 4.1 release to -stable, I've had a curious problem >with ftp logins. Users which should be allowed to log into ftp will get a >denial message immedately after entrying the login name, the password prompt >is never given. >.... If these folks use tcsh, you might want to do a reality check on the content of /etc/shells -- tcsh is now in /bin/tcsh. (I found it useful to have both /bin/tcsh and /usr/local/bin/tcsh in /etc/shells, at least for a while.) Cheers, david -- David Wolfskill dhw@whistle.com UNIX System Administrator Desk: 650/577-7158 TIE: 8/499-7158 Cell: 650/759-0823 I need help: http://www.whistle.com/employment/employ-engg.html#K030391 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 22 16: 9:36 2001 Delivered-To: freebsd-stable@freebsd.org Received: from easystreet01.easystreet.com (easystreet.com [206.26.36.40]) by hub.freebsd.org (Postfix) with ESMTP id 2170537B69E for ; Mon, 22 Jan 2001 16:09:18 -0800 (PST) Received: from jasonweb ([206.129.94.232]) by easystreet01.easystreet.com (8.9.3/8.9.3) with SMTP id QAA12469; Mon, 22 Jan 2001 16:09:17 -0800 (PST) From: "Jason Watkins" To: "Freebsd-Stable" Subject: RE: ftp logins Date: Mon, 22 Jan 2001 16:11:23 -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.2910.0) In-Reply-To: Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Disposition-Notification-To: "Jason Watkins" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Just a quick thought, but is tcsh in /etc/shells? (ie, if the passwd > entry says /usr/local/bin/tcsh, is /usr/local/bin/tcsh in there?) > > On Mon, 22 Jan 2001, Jason Watkins wrote: > > > Since rebuilding from 4.1 release to -stable, I've had a curious problem > > with ftp logins. Users which should be allowed to log into ftp > will get a > > denial message immedately after entrying the login name, the > password prompt > > is never given. > > > > I'm not all that familiar with freebsd, however the users (or > groups) are > > not in /etc/ftpusers banlist. Most of the users are configured > with tcsh as > > their shell, none are in /etc/ftpchroot. > > > > I've since built and installed wu-ftpd-2.6.0. Now users are > prompted for a > > password, however, are still denied login. > > > > Newly created users work just fine. Existing users can login > via ssh, etc > > just fine. > > > > I've asked some other more knowledgeable friends to look at > this as well, > > and they can't figure out what the problem is either. It does > appear that > > someone inadvertantly enabled anonymous ftp, and some warezer > did a speed > > test, decided it was to slow to use as a dump, and moved on. It doesn't > > appear he did anything more nefarious, but I can't be absolutely sure. > > > > Any ideas? > > > > jason watkins > > jwatkins@firstplan.com > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-stable" in the body of the message > > > > -- > Bob | iNFp > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 22 16:10:58 2001 Delivered-To: freebsd-stable@freebsd.org Received: from easystreet01.easystreet.com (easystreet.com [206.26.36.40]) by hub.freebsd.org (Postfix) with ESMTP id 8175937B69E for ; Mon, 22 Jan 2001 16:10:38 -0800 (PST) Received: from jasonweb ([206.129.94.232]) by easystreet01.easystreet.com (8.9.3/8.9.3) with SMTP id QAA13421; Mon, 22 Jan 2001 16:10:37 -0800 (PST) From: "Jason Watkins" To: "Freebsd-Stable" Subject: RE: ftp logins Date: Mon, 22 Jan 2001 16:12:43 -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.2910.0) In-Reply-To: Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Disposition-Notification-To: "Jason Watkins" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG (aplogies for empty reply, drunk mousing sucks) yes, tcsh is in /etc/shells > Just a quick thought, but is tcsh in /etc/shells? (ie, if the passwd > entry says /usr/local/bin/tcsh, is /usr/local/bin/tcsh in there?) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 22 16:13:19 2001 Delivered-To: freebsd-stable@freebsd.org Received: from easystreet01.easystreet.com (easystreet.com [206.26.36.40]) by hub.freebsd.org (Postfix) with ESMTP id BD36137B69F for ; Mon, 22 Jan 2001 16:12:59 -0800 (PST) Received: from jasonweb ([206.129.94.232]) by easystreet01.easystreet.com (8.9.3/8.9.3) with SMTP id QAA15091 for ; Mon, 22 Jan 2001 16:12:58 -0800 (PST) From: "Jason Watkins" To: "Freebsd-Stable" Subject: RE: ftp logins Date: Mon, 22 Jan 2001 16:15:05 -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.2910.0) In-Reply-To: <200101230007.f0N07SF54213@pau-amma.whistle.com> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Disposition-Notification-To: "Jason Watkins" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yea, both /bin/tcsh and /usr/local/bin/tcsh are in /etch/shells that was a good suggestion, I hadn't thought of that jason > If these folks use tcsh, you might want to do a reality check on the > content of /etc/shells -- tcsh is now in /bin/tcsh. (I found it useful > to have both /bin/tcsh and /usr/local/bin/tcsh in /etc/shells, at least > for a while.) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 22 16:24:53 2001 Delivered-To: freebsd-stable@freebsd.org Received: from yip.org (yip.org [199.45.111.121]) by hub.freebsd.org (Postfix) with ESMTP id AB8CF37B402 for ; Mon, 22 Jan 2001 16:24:35 -0800 (PST) Received: from localhost (melange@localhost) by yip.org (8.11.1/8.11.1) with ESMTP id f0N0OYN92640 for ; Mon, 22 Jan 2001 19:24:34 -0500 (EST) (envelope-from melange@yip.org) Date: Mon, 22 Jan 2001 19:24:34 -0500 (EST) From: Bob K To: Freebsd-Stable Subject: RE: ftp logins 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 Hmm. What's the exact denial message users get? Other things to check are if you have any groups in /etc/ftpusers (they begin with an @), and if there's anything related in /var/log/messages (or wherever you log ftpd info to)... On Mon, 22 Jan 2001, Jason Watkins wrote: > Yea, both /bin/tcsh and /usr/local/bin/tcsh are in /etch/shells > > that was a good suggestion, I hadn't thought of that > > jason > > > If these folks use tcsh, you might want to do a reality check on the > > content of /etc/shells -- tcsh is now in /bin/tcsh. (I found it useful > > to have both /bin/tcsh and /usr/local/bin/tcsh in /etc/shells, at least > > for a while.) > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > -- Bob | iNFp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 22 16:42:40 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mrynet.com (mrynet.com [63.228.57.57]) by hub.freebsd.org (Postfix) with ESMTP id 225D037B404 for ; Mon, 22 Jan 2001 16:42:24 -0800 (PST) Received: (from freebsd@localhost) by mrynet.com (8.11.1/8.11.1) id f0N0gNK00481 for freebsd-stable@freebsd.org; Mon, 22 Jan 2001 18:42:23 -0600 (CST) (envelope-from freebsd) Message-Id: <200101230042.f0N0gNK00481@mrynet.com> From: freebsd@mrynet.com (FreeBSD list) Date: Mon, 22 Jan 2001 18:42:23 -0600 X-Mailer: Mail User's Shell (7.2.6 beta(3) 11/17/96) To: freebsd-stable@freebsd.org Subject: NFS hangs root on today's CVSUP Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG After CVSUP'ing today and building world and installing a new kernel, ALL NFS mounts hang, and root (/) suddenly becomes unreadable with "/bin/ls -F"--it hangs as well. Also, df(1) and mount(8) hang forever. I've re-CVSUP'ed in case I caught something mid-stream, but the problem still prevails. Would others please check this? This NFS breakage renders a client of NFS unable to operate. -scott To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 22 16:46:34 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 6199237B698 for ; Mon, 22 Jan 2001 16:46:01 -0800 (PST) Received: from venus.n2.net (venus.n2.net [207.113.133.11]) by darkstar.bsdguru.com (Postfix) with ESMTP id 350C41DDF for ; Mon, 22 Jan 2001 16:45:53 -0800 (PST) Received: by venus.n2.net (Postfix, from userid 1002) id 8973A3CC9; Mon, 22 Jan 2001 16:45:58 -0800 (PST) Date: Mon, 22 Jan 2001 16:45:57 -0800 From: Ben Lovett To: stable@freebsd.org Subject: Re: Pagefaults occuring randomly Message-ID: <20010122164556.A1772@venus.homenet> References: <20010118142944.A580@bsdguru.com> <979918898.3a68603253893@webmail.harmonic.co.il> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="hHWLQfXTYDoKhP50" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <979918898.3a68603253893@webmail.harmonic.co.il>; from roman@harmonic.co.il on Fri, Jan 19, 2001 at 05:41:38PM +0200 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 (3% 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:58PM up 26 mins, 3 users, load averages: 0.56, 0.42, 0.18 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --hHWLQfXTYDoKhP50 Content-Type: multipart/mixed; boundary="MGYHOYXEY6WxJCY8" Content-Disposition: inline --MGYHOYXEY6WxJCY8 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Well.. Finally it has happened again, and I had a dumpdev setup. Attached is the output of the kernel debug session.. I hope I did this correctly, so if there is anythign that I missed, I would be more than happy to redo the debug. I have attached the output to this message, and will send a copy of the vmcore and kernel if neccessary upon request. Thanks once again for your time. -ben Roman Shterenzon (roman@harmonic.co.il) wrote: > Please read http://www.freebsd.org/handbook/kerneldebug.html > and create a PR with all the needed information. >=20 > Quoting Ben Lovett : >=20 > > Hello, > >=20 > > 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. > >=20 > > 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. > >=20 > > Thanks for your time! > > --=20 > > -=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-= =3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D- > > Ben Lovett printf("Hello world!); > > don4r return 0; > > don4r@bsdguru.com > > -=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-= =3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D- > > Speak softly and carry a cellular phone. > >=20 --MGYHOYXEY6WxJCY8 Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=kernel-debug Content-Transfer-Encoding: quoted-printable Script started on Mon Jan 22 14:50:39 2001 Erase is backspace.=0D TERM=3Dcons25 (25 80)=0D =0D People who develop the habit of thinking of themselves as world=0D citizens are fulfilling the first requirement of sanity in our time.=0D -- Norman Cousins=0D =0D root-venus> cd /usr/obj/usr/src/sys/VENUS/=0D root-venus> gdb -k=0D GNU gdb 4.18=0D Copyright 1998 Free Software Foundation, Inc.=0D GDB is free software, covered by the GNU General Public License, and you ar= e=0D welcome to change it and/or distribute copies of it under certain condition= s.=0D Type "show copying" to see the conditions.=0D There is absolutely no warranty for GDB. Type "show warranty" for details.= =0D This GDB was configured as "i386-unknown-freebsd".=0D (kgdb) symbol-file kernel.debug=0D Reading symbols from kernel.debug...done.=0D (kgdb) exec-file /var/crash/kernel.2=0D (kgdb) core-file /var/crash/vmcore.2=0D IdlePTD 4472832=0D initial pcb at 38f740=0D panicstr: from debugger=0D panic messages:=0D ---=0D Fatal trap 12: page fault while in kernel mode=0D fault virtual address =3D 0x2020206c=0D fault code =3D supervisor read, page not present=0D instruction pointer =3D 0x8:0xc01e72f8=0D stack pointer =3D 0x10:0xc4214f68=0D frame pointer =3D 0x10:0xc4214f88=0D code segment =3D base 0x0, limit 0xfffff, type 0x1b=0D =3D DPL 0, pres 1, def32 1, gran 1=0D processor eflags =3D interrupt enabled, resume, IOPL =3D 0=0D current process =3D 9775 (aterm)=0D interrupt mask =3D =0D trap number =3D 12=0D panic: page fault=0D =0D syncing disks... 18 18 13 5 =0D done=0D Uptime: 17h44m46s=0D =0D dumping to dev #ad/0x20001, offset 335744=0D dump ata0: resetting devices .. done=0D 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 = 6 5 4 3 failed, reason: aborted from console=0D Automatic reboot in 15 seconds - press a key on the console to abort=0D --> Press a key on the console to reboot <--=0D Rebooting...=0D Copyright (c) 1992-2001 The FreeBSD Project.=0D Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994=0D The Regents of the University of California. All rights reserved.=0D FreeBSD 4.2-STABLE #0: Mon Jan 15 18:43:35 PST 2001=0D root@luna:/usr/obj/usr/src/sys/VENUS=0D Timecounter "i8254" frequency 1193182 Hz=0D CPU: Pentium/P55C (quarter-micron) (233.29-MHz 586-class CPU)=0D Origin =3D "GenuineIntel" Id =3D 0x581 Stepping =3D 1=0D Features=3D0x8001bf=0D real memory =3D 33619968 (32832K bytes)=0D avail memory =3D 28626944 (27956K bytes)=0D Preloaded elf kernel "kernel" at 0xc0425000.=0D Intel Pentium detected, installing workaround for F00F bug=0D md0: Malloc disk=0D apm0: on motherboard=0D apm: found APM BIOS v1.2, connected at v1.2=0D npx0: on motherboard=0D npx0: INT 16 interface=0D pcib0: on motherboard=0D pci0: on pcib0=0D pci0: at 4.0=0D pci0: at 11.0 irq 11=0D chip1: port 0xffe0-0xffff irq 11 at dev= ice 17.0 on pci0=0D isa0: on motherboard=0D fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0=0D fd0: <1440-KB 3.5" drive> on fdc0 drive 0=0D ata0 at port 0x1f0-0x1f7,0x3f6 irq 14 on isa0=0D ata1 at port 0x170-0x177,0x376 irq 15 on isa0=0D atkbdc0: at port 0x60,0x64 on isa0=0D atkbd0: flags 0x1 irq 1 on atkbdc0=0D kbd0 at atkbd0=0D psm0: irq 12 on atkbdc0=0D psm0: model GlidePoint, device ID 0=0D vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0=0D sc0: at flags 0x100 on isa0=0D sc0: VGA <16 virtual consoles, flags=3D0x300>=0D pcic0: at port 0x3e0 iomem 0xd0000 irq 10 on isa0=0D pcic0: management irq 10=0D pccard0: on pcic0=0D pccard1: on pcic0=0D sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0=0D sio0: type 16550A=0D sio1: configured irq 3 not in bitmap of probed irqs 0=0D ppc0: parallel port not found.=0D pcm0: at port 0x530-0x537,0x370-0x371 irq 5 drq 1 flags= 0xc100 on isa0=0D IPsec: Initialized Security Association Processing.=0D IP Filter: v3.4.8 initialized. Default =3D pass all, Logging =3D enabled=0D pccard: card inserted, slot 0=0D pccard: card inserted, slot 1=0D ata1-slave: ata_command: timeout waiting for intr=0D ata1-slave: identify failed=0D ad0: 2067MB [4200/16/63] at ata0-master BIOSPIO=0D acd0: CDROM at ata1-master using BIOSPIO=0D Mounting root from ufs:/dev/ad0s1a=0D WARNING: / was not properly dismounted=0D ed0 at port 0x320-0x33f irq 3 slot 0 on pccard0=0D ed0: address 00:e0:98:78:fc:6d, type Linksys (16 bit) =0D sio4 at port 0x2f8-0x2ff irq 9 slot 1 on pccard1=0D sio4: type 16550A=0D ed0: detached=0D stray irq 3=0D pccard: card disabled, slot 0=0D sio4: unloaded=0D sio4: detached=0D pccard: card disabled, slot 1=0D resumed from suspended mode (slept 00:12:52)=0D ata0: resetting devices .. done=0D ata1: resetting devices .. done=0D pccard: card inserted, slot 0=0D pccard: card inserted, slot 1=0D sio4 at port 0x2f8-0x2ff irq 9 slot 1 on pccard1=0D sio4: type 16550A=0D ed0 at port 0x320-0x33f irq 3 slot 0 on pccard0=0D ed0: address 00:e0:98:78:fc:6d, type Linksys (16 bit) =0D ed0: detached=0D stray irq 3=0D pccard: card disabled, slot 0=0D sio4: unloaded=0D sio4: detached=0D pccard: card disabled, slot 1=0D resumed from suspended mode (slept 00:00:57)=0D ata0: resetting devices .. done=0D ata1: resetting devices .. done=0D pccard: card inserted, slot 0=0D pccard: card inserted, slot 1=0D sio4 at port 0x2f8-0x2ff irq 9 slot 1 on pccard1=0D sio4: type 16550A=0D ed0 at port 0x320-0x33f irq 3 slot 0 on pccard0=0D ed0: address 00:e0:98:78:fc:6d, type Linksys (16 bit) =0D ed0: promiscuous mode enabled=0D ed0: NIC memory corrupt - invalid packet length 1=0D ed0: promiscuous mode disabled=0D =0D =0D Fatal trap 12: page fault while in kernel mode=0D fault virtual address =3D 0x123da=0D fault code =3D supervisor read, page not present=0D instruction pointer =3D 0x8:0xc01e730d=0D stack pointer =3D 0x10:0xc033fbfc=0D frame pointer =3D 0x10:0xc033fc1c=0D code segment =3D base 0x0, limit 0xfffff, type 0x1b=0D =3D DPL 0, pres 1, def32 1, gran 1=0D processor eflags =3D interrupt enabled, resume, IOPL =3D 3=0D current process =3D Idle=0D interrupt mask =3D =0D panic: from debugger=0D panic: from debugger=0D Uptime: 33m53s=0D =0D dumping to dev #ad/0x20001, offset 335744=0D dump ata0: resetting devices .. done=0D 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 = 6 5 4 3 2 1 =0D ---=0D #0 dumpsys () at /usr/src/sys/kern/kern_shutdown.c:469=0D 469 if (dumping++) {=0D (kgdb) where=0D #0 dumpsys () at /usr/src/sys/kern/kern_shutdown.c:469=0D #1 0xc018b83b in boot (howto=3D260) at /usr/src/sys/kern/kern_shutdown.c:3= 09=0D #2 0xc018bbd1 in panic (fmt=3D0xc02fab94 "from debugger")=0D at /usr/src/sys/kern/kern_shutdown.c:556=0D #3 0xc0141e1d in db_panic (addr=3D-1071746291, have_addr=3D0, count=3D-1, = =0D modif=3D0xc033fa68 "") at /usr/src/sys/ddb/db_command.c:433=0D #4 0xc0141dbd in db_command (last_cmdp=3D0xc0345f4c, cmd_table=3D0xc0345da= c, =0D aux_cmd_tablep=3D0xc038a8f0) at /usr/src/sys/ddb/db_command.c:333=0D #5 0xc0141e82 in db_command_loop () at /usr/src/sys/ddb/db_command.c:455=0D #6 0xc0143f8f in db_trap (type=3D12, code=3D0) at /usr/src/sys/ddb/db_trap= .c:71=0D #7 0xc02d0546 in kdb_trap (type=3D12, code=3D0, regs=3D0xc033fbbc)=0D at /usr/src/sys/i386/i386/db_interface.c:158=0D #8 0xc02df62c in trap_fatal (frame=3D0xc033fbbc, eva=3D74714)=0D at /usr/src/sys/i386/i386/trap.c:946=0D #9 0xc02df305 in trap_pfault (frame=3D0xc033fbbc, usermode=3D0, eva=3D7471= 4)=0D at /usr/src/sys/i386/i386/trap.c:844=0D #10 0xc02dee7b in trap (frame=3D{tf_fs =3D 16, tf_es =3D 16, tf_ds =3D 16, = =0D tf_edi =3D -65536, tf_esi =3D 0, tf_ebp =3D -1070334948, tf_isp =3D -= 1070335000, =0D tf_ebx =3D -1064378368, tf_edx =3D -1059952256, tf_ecx =3D -106437830= 8, =0D tf_eax =3D 74676, tf_trapno =3D 12, tf_err =3D 0, tf_eip =3D -1071746= 291, =0D tf_cs =3D 8, tf_eflags =3D 78342, tf_esp =3D -1064378368, tf_ss =3D 0= })=0D at /usr/src/sys/i386/i386/trap.c:443=0D #11 0xc01e730d in ip_input (m=3D0xc08ee000)=0D at /usr/src/sys/netinet/ip_input.c:492=0D ---Type to continue, or q to quit--- =08=1B[K=0D #12 0xc01e764f in ipintr () at /usr/src/sys/netinet/ip_input.c:759=0D (kgdb) help=0D List of classes of commands:=0D =0D aliases -- Aliases of other commands=0D breakpoints -- Making program stop at certain points=0D data -- Examining data=0D files -- Specifying and examining files=0D internals -- Maintenance commands=0D obscure -- Obscure features=0D running -- Running the program=0D stack -- Examining the stack=0D status -- Status inquiries=0D support -- Support facilities=0D tracepoints -- Tracing of program execution without stopping the program=0D user-defined -- User-defined commands=0D =0D Type "help" followed by a class name for a list of commands in that class.= =0D Type "help" followed by command name for full documentation.=0D Command name abbreviations are allowed if unambiguous.=0D (kgdb) s=08 =08=07bt=0D #0 dumpsys () at /usr/src/sys/kern/kern_shutdown.c:469=0D #1 0xc018b83b in boot (howto=3D260) at /usr/src/sys/kern/kern_shutdown.c:3= 09=0D #2 0xc018bbd1 in panic (fmt=3D0xc02fab94 "from debugger")=0D at /usr/src/sys/kern/kern_shutdown.c:556=0D #3 0xc0141e1d in db_panic (addr=3D-1071746291, have_addr=3D0, count=3D-1, = =0D modif=3D0xc033fa68 "") at /usr/src/sys/ddb/db_command.c:433=0D #4 0xc0141dbd in db_command (last_cmdp=3D0xc0345f4c, cmd_table=3D0xc0345da= c, =0D aux_cmd_tablep=3D0xc038a8f0) at /usr/src/sys/ddb/db_command.c:333=0D #5 0xc0141e82 in db_command_loop () at /usr/src/sys/ddb/db_command.c:455=0D #6 0xc0143f8f in db_trap (type=3D12, code=3D0) at /usr/src/sys/ddb/db_trap= .c:71=0D #7 0xc02d0546 in kdb_trap (type=3D12, code=3D0, regs=3D0xc033fbbc)=0D at /usr/src/sys/i386/i386/db_interface.c:158=0D #8 0xc02df62c in trap_fatal (frame=3D0xc033fbbc, eva=3D74714)=0D at /usr/src/sys/i386/i386/trap.c:946=0D #9 0xc02df305 in trap_pfault (frame=3D0xc033fbbc, usermode=3D0, eva=3D7471= 4)=0D at /usr/src/sys/i386/i386/trap.c:844=0D #10 0xc02dee7b in trap (frame=3D{tf_fs =3D 16, tf_es =3D 16, tf_ds =3D 16, = =0D tf_edi =3D -65536, tf_esi =3D 0, tf_ebp =3D -1070334948, tf_isp =3D -= 1070335000, =0D tf_ebx =3D -1064378368, tf_edx =3D -1059952256, tf_ecx =3D -106437830= 8, =0D tf_eax =3D 74676, tf_trapno =3D 12, tf_err =3D 0, tf_eip =3D -1071746= 291, =0D tf_cs =3D 8, tf_eflags =3D 78342, tf_esp =3D -1064378368, tf_ss =3D 0= })=0D at /usr/src/sys/i386/i386/trap.c:443=0D #11 0xc01e730d in ip_input (m=3D0xc08ee000)=0D at /usr/src/sys/netinet/ip_input.c:492=0D ---Type to continue, or q to quit--- =08=1B[K=0D #12 0xc01e764f in ipintr () at /usr/src/sys/netinet/ip_input.c:759=0D (kgdb) quit=0D root-venus> exit=0D exit=0D Script done on Mon Jan 22 14:52:29 2001 --MGYHOYXEY6WxJCY8-- --hHWLQfXTYDoKhP50 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 iD8DBQE6bNREfHaK+uurIAQRApWxAJ4i0kMw7e+4JO0xRqPa0UdFvmiknACg0llV un3bVZnLHRnqGuLi0/PhDXk= =QEkB -----END PGP SIGNATURE----- --hHWLQfXTYDoKhP50-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 22 17: 2:25 2001 Delivered-To: freebsd-stable@freebsd.org Received: from demai05.mw.mediaone.net (demai05.mw.mediaone.net [24.131.1.56]) by hub.freebsd.org (Postfix) with ESMTP id E1D7C37B402 for ; Mon, 22 Jan 2001 17:02:07 -0800 (PST) Received: from ian.batcave.com (nic-131-c233-239.mw.mediaone.net [24.131.233.239]) by demai05.mw.mediaone.net (8.8.7/8.8.7) with SMTP id UAA03955 for ; Mon, 22 Jan 2001 20:02:07 -0500 (EST) From: Ian Cartwright Reply-To: icartwright@mediaone.net To: freebsd-stable@freebsd.org Subject: Compiling XFree86-4_5 Date: Mon, 22 Jan 2001 20:02:07 -0500 X-Mailer: KMail [version 1.1.99] Content-Type: text/plain; charset="iso-8859-1" MIME-Version: 1.0 Message-Id: <01012220020702.00373@ian.batcave.com> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello all, I seem to be having a problem compiling XFree86-4_5 from the ports collection. It downloads and compiles OK, but partway through the linking stage I get some errors that have to do with threading. I'm not sure why this should be since I have another FreeBSD box that compiles it flawlessly... Here is all the relevant info I can think of: FreeBSD-4.2-STABLE (last make world Jan 21, 2001) Current XFree86-4.0.1 (from binaries downloaded from xfree86.org) KDE 2.0.1 (ports with relevant dependencies (qt, Mesa, etc.)) default make arguements are the defaults in /etc/defaults/make.conf plus I added: -mpentiumpro -march=i686 -03 Here are the last few lines from make: making all in programs/appres... LD_LIBRARY_PATH=../../exports/lib cc -O3 -pipe -mpentiumpro -march=i686 -pthread -ansi -pedantic -Dasm=__asm -Wall -Wpointer-arith -I../.. -I../../exports/include -DCSRG_BASED -DFUNCPROTO=15 -DNARROWPROTO -c appres.c rm -f appres LD_LIBRARY_PATH=../../exports/lib cc -o appres -ansi -pedantic -Dasm=__asm -Wall -Wpointer-arith -L../../exports/lib appres.o -lXt -lSM -lICE -lXext -lX11 -L/usr/X11R6/lib -Wl,-rpath,/usr/X11R6/lib ../../exports/lib/libXt.so: undefined reference to `pthread_cond_signal' /usr/X11R6/lib/libXThrStub.so.6: undefined reference to `_Xthr_zero_stub_' ../../exports/lib/libX11.so: undefined reference to `pthread_cond_broadcast' /usr/X11R6/lib/libXThrStub.so.6: undefined reference to `_Xthr_self_stub_' ../../exports/lib/libXt.so: undefined reference to `pthread_cond_init' ../../exports/lib/libXt.so: undefined reference to `pthread_mutex_unlock' ../../exports/lib/libXt.so: undefined reference to `pthread_self' ../../exports/lib/libXt.so: undefined reference to `pthread_mutex_destroy' ../../exports/lib/libXt.so: undefined reference to `pthread_mutex_lock' ../../exports/lib/libXt.so: undefined reference to `pthread_cond_wait' ../../exports/lib/libXt.so: undefined reference to `pthread_cond_destroy' ../../exports/lib/libXt.so: undefined reference to `pthread_mutex_init' *** Error code 1 Stop in /usr/ports/x11/XFree86-4/work/xc/programs/appres. *** Error code 1 Stop in /usr/ports/x11/XFree86-4/work/xc/programs. *** Error code 1 Stop in /usr/ports/x11/XFree86-4/work/xc. *** Error code 1 Stop in /usr/ports/x11/XFree86-4/work/xc. *** Error code 1 Stop in /usr/ports/x11/XFree86-4/work/xc. *** Error code 1 Stop in /usr/ports/x11/XFree86-4. *** Error code 1 Stop in /usr/ports/x11/XFree86-4. *** Error code 1 Stop in /usr/ports/x11/XFree86-4. ------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 22 17:20:57 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 EE96637B402; Mon, 22 Jan 2001 17:20:31 -0800 (PST) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id RAA08963; Mon, 22 Jan 2001 17:20:22 -0800 Date: Mon, 22 Jan 2001 17:20:22 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Lars Eggert , Jan Chrillesen Cc: freebsd-stable@freebsd.org, freebsd-hardware@freebsd.org, usenet@tdk.net Subject: Intel wiseman and livengood Gig support stuff. 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 A couple of things.... There was a bug fixed post 4.2 release that showed up with problems in promiscuous mode... Secondly, I just discovered that the Livengood chipset actually remapped a lot of interesting registers different places. Why I thought things were working at all is a mystery to me as I was scribbling into what are 'reserved' registers for Livengood. I don't know *how* I got any of the LIVENGOOD boards to work at all before. Yuck. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 22 17:21:40 2001 Delivered-To: freebsd-stable@freebsd.org Received: from subnet.sub.net (subnet.sub.net [212.227.14.21]) by hub.freebsd.org (Postfix) with ESMTP id BCE4837B404 for ; Mon, 22 Jan 2001 17:21:19 -0800 (PST) Received: from lyxys.ka.sub.org (uucp@localhost) by subnet.sub.net (8.8.8/8.8.8/1.2subnet-linux) with bsmtp id CAA19778; Tue, 23 Jan 2001 02:21:14 +0100 Received: from localhost (1003 bytes) by lyxys.ka.sub.org via sendmail with P:stdio/R:smart_host/T:inet_uusmtp (sender: ) (ident using unix) id for ; Tue, 23 Jan 2001 02:19:43 +0100 (CET) (Smail-3.2.0.111 2000-Feb-17 #1 built 2000-Aug-23) Message-Id: From: wolfgang@lyxys.ka.sub.org (Wolfgang Zenker) Subject: Re: ftp logins In-Reply-To: "from Jason Watkins at Jan 22, 2001 04:05:01 pm" To: Jason Watkins Date: Tue, 23 Jan 2001 02:19:43 +0100 (CET) Cc: Freebsd-Stable 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 Hi, > I've since built and installed wu-ftpd-2.6.0. Now users are prompted for a > password, however, are still denied login. > Newly created users work just fine. Existing users can login via ssh, etc > just fine. it could have something to do with password encryption methods. Maybe your newly created users have DES-passwords and the old ones MD5 or vice versa? Have a look in /etc/master.passwd, if the password field starts with "$1$" its a MD5-password, otherwise DES. Wolfgang To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 22 17:29:54 2001 Delivered-To: freebsd-stable@freebsd.org Received: from backup.af.speednet.com.au (af.speednet.com.au [202.135.188.244]) by hub.freebsd.org (Postfix) with ESMTP id AD5A537B401 for ; Mon, 22 Jan 2001 17:29:34 -0800 (PST) Received: from backup.af.speednet.com.au (backup.af.speednet.com.au [172.22.2.4]) by backup.af.speednet.com.au (8.11.1/8.11.1) with ESMTP id f0N1T3m37947; Tue, 23 Jan 2001 12:29:04 +1100 (EST) (envelope-from andyf@speednet.com.au) Date: Tue, 23 Jan 2001 12:29:03 +1100 (EST) From: Andy Farkas X-Sender: andyf@backup.af.speednet.com.au To: "Christopher M. Giordano" Cc: stable@FreeBSD.ORG, jdp@polstra.com Subject: Re: preventing cvsup from replacing /usr/ports symlink? In-Reply-To: <3A6C5E6C.3E84EAC0@ids.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, 22 Jan 2001, Christopher M. Giordano 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. > > This happened to me two days ago (jan 20, 1030 AM), and it always > seems to occur when re-cvsup'ing following a failed cvsup. > In this case, the first attempt failed with a message like: > "Updater failed: unable to delete file archivers/arc/Makefile: no > such file or directory", which in itself seemed odd, since I > was starting with a full copy of the ports tree. Restarting > cvsup then filled /usr/ports tree in my /usr filesystem rather > than the linked filesystem. I assume the link is deleted upon > the first failure, but I have no evidence of this. > > I know that's _very_ little to go on.... It just happened to me! I started a cvsup which failed with the same error message (unable to delete...). When I re-cvsup'd, files started to be checked-out into the /usr/ports directory, which used to be a symlink. Hitting ^C, creating the symlink again (after rm'ing the new directory), and then doing a third cvsup run works as per normal. I don't know when the symlink is removed - either after the first cvsup run (with error) or during the startup of the second cvsup run. > > Chris Giordano > CGiordano@ids.net > -- > A man cannot be too careful in the choice of his enemies. > -- Oscar Wilde, "Picture of Dorian Gray" > -- :{ andyf@speednet.com.au Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 22 18:26:19 2001 Delivered-To: freebsd-stable@freebsd.org Received: from smtp.gwi.net (smtp.gwi.net [207.5.128.11]) by hub.freebsd.org (Postfix) with ESMTP id 0333C37B400 for ; Mon, 22 Jan 2001 18:26:00 -0800 (PST) Received: from sss1.gwi.net (sss1.gwi.net [207.5.128.36]) by smtp.gwi.net (8.10.1/8.10.1) with ESMTP id f0N2Pwr01932; Mon, 22 Jan 2001 21:25:58 -0500 (EST) Date: Mon, 22 Jan 2001 21:25:58 -0500 (EST) From: "Jamin A. Brown" To: Ian Cartwright Cc: Subject: Re: Compiling XFree86-4_5 In-Reply-To: <01012220020702.00373@ian.batcave.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 Ian, Had the same problem, reduce O3 to O2 and that fixed my problem. Jamin On Mon, 22 Jan 2001, Ian Cartwright wrote: > Hello all, > > I seem to be having a problem compiling XFree86-4_5 from the ports > collection. It downloads and compiles OK, but partway through the linking > stage I get some errors that have to do with threading. I'm not sure why this > should be since I have another FreeBSD box that compiles it flawlessly... > > Here is all the relevant info I can think of: > > FreeBSD-4.2-STABLE (last make world Jan 21, 2001) > Current XFree86-4.0.1 (from binaries downloaded from xfree86.org) > KDE 2.0.1 (ports with relevant dependencies (qt, Mesa, etc.)) > default make arguements are the defaults in /etc/defaults/make.conf plus I > added: -mpentiumpro -march=i686 -03 > > Here are the last few lines from make: > > making all in programs/appres... > LD_LIBRARY_PATH=../../exports/lib cc -O3 -pipe -mpentiumpro -march=i686 > -pthread -ansi -pedantic -Dasm=__asm -Wall -Wpointer-arith -I../.. > -I../../exports/include -DCSRG_BASED -DFUNCPROTO=15 -DNARROWPROTO -c > appres.c > rm -f appres > LD_LIBRARY_PATH=../../exports/lib cc -o appres -ansi -pedantic -Dasm=__asm > -Wall -Wpointer-arith -L../../exports/lib appres.o -lXt -lSM -lICE -lXext > -lX11 -L/usr/X11R6/lib -Wl,-rpath,/usr/X11R6/lib > ../../exports/lib/libXt.so: undefined reference to `pthread_cond_signal' > /usr/X11R6/lib/libXThrStub.so.6: undefined reference to `_Xthr_zero_stub_' > ../../exports/lib/libX11.so: undefined reference to `pthread_cond_broadcast' > /usr/X11R6/lib/libXThrStub.so.6: undefined reference to `_Xthr_self_stub_' > ../../exports/lib/libXt.so: undefined reference to `pthread_cond_init' > ../../exports/lib/libXt.so: undefined reference to `pthread_mutex_unlock' > ../../exports/lib/libXt.so: undefined reference to `pthread_self' > ../../exports/lib/libXt.so: undefined reference to `pthread_mutex_destroy' > ../../exports/lib/libXt.so: undefined reference to `pthread_mutex_lock' > ../../exports/lib/libXt.so: undefined reference to `pthread_cond_wait' > ../../exports/lib/libXt.so: undefined reference to `pthread_cond_destroy' > ../../exports/lib/libXt.so: undefined reference to `pthread_mutex_init' > *** Error code 1 > > Stop in /usr/ports/x11/XFree86-4/work/xc/programs/appres. > *** Error code 1 > > Stop in /usr/ports/x11/XFree86-4/work/xc/programs. > *** Error code 1 > > Stop in /usr/ports/x11/XFree86-4/work/xc. > *** Error code 1 > > Stop in /usr/ports/x11/XFree86-4/work/xc. > *** Error code 1 > > Stop in /usr/ports/x11/XFree86-4/work/xc. > *** Error code 1 > > Stop in /usr/ports/x11/XFree86-4. > *** Error code 1 > > Stop in /usr/ports/x11/XFree86-4. > *** Error code 1 > > Stop in /usr/ports/x11/XFree86-4. > > ------------------------------------------------------- > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > ----------------------------------------------------------------- Jamin A. Brown Systems Operations Department operations@gwi.net * Great Works Internet * 207.286.8686 x142 RSA PGP Key: http://www.gwi.net/~jamin/pgp/jamin.asc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 22 21: 0:10 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mailserver.aimcomm.com (mailserver.aimcomm.com [216.64.134.14]) by hub.freebsd.org (Postfix) with ESMTP id 396EF37B400 for ; Mon, 22 Jan 2001 20:59:54 -0800 (PST) Received: from aimcomm.com ([208.186.42.241]) by mailserver.aimcomm.com (Post.Office MTA v3.5.3 release 223 ID# 0-12345L500S10000V35) with ESMTP id com for ; Mon, 22 Jan 2001 21:00:32 -0800 Message-ID: <3A6D0FC2.C8435F17@aimcomm.com> Date: Mon, 22 Jan 2001 20:59:46 -0800 From: Randy Creighton X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: FreeBSD-stable@FreeBSD.ORG Subject: subscribe Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: 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 22 22:18:17 2001 Delivered-To: freebsd-stable@freebsd.org Received: from www.evil.2y.net (ip-216-23-53-20.adsl.one.net [216.23.53.20]) by hub.freebsd.org (Postfix) with ESMTP id 68CEC37B401 for ; Mon, 22 Jan 2001 22:17:59 -0800 (PST) Received: (from cokane@localhost) by www.evil.2y.net (8.11.1/8.11.1) id f0N6TBC19728; Tue, 23 Jan 2001 01:29:11 -0500 (EST) (envelope-from cokane) Date: Tue, 23 Jan 2001 01:29:10 -0500 From: Coleman Kane To: Antony T Curtis Cc: "Paul A. Howes" , freebsd-stable@FreeBSD.ORG Subject: Re: New Intel NICs... Message-ID: <20010123012910.C10383@cokane.yi.org> References: <3A6C257A.140E27C2@abacus.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <3A6C257A.140E27C2@abacus.co.uk>; from antony@abacus.co.uk on Mon, Jan 22, 2001 at 09:12:40AM -0500 X-Vim: vim:tw=70:ts=4:sw=4 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG No, the 8250 is the serial UART, the 8255x line is Intel's network division. Antony T Curtis had the audacity to say: > > "Paul A. Howes" wrote: > > > > 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? > > ROTFL! Isn't the 82550A UART chips for serial comms? > Nothing like a bit of chip numbering to confuse everyone. > > > > 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 22 22:42:50 2001 Delivered-To: freebsd-stable@freebsd.org Received: from gecko.eric.net.au (gecko.eric.net.au [203.102.228.3]) by hub.freebsd.org (Postfix) with ESMTP id 4BCD137B402 for ; Mon, 22 Jan 2001 22:42:28 -0800 (PST) Received: (from ghcrompton@localhost) by gecko.eric.net.au (8.9.3/8.8.7) id RAA00601 for freebsd-stable@freebsd.org; Tue, 23 Jan 2001 17:45:58 +1100 Date: Tue, 23 Jan 2001 17:45:58 +1100 From: "Geoffrey Crompton (RMIT Guest)" To: freebsd-stable@freebsd.org Subject: hard read errors Message-ID: <20010123174558.A427@gecko.eric.net.au> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="tThc/1wpZn/ma/RB" X-Mailer: Mutt 1.0pre3us Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --tThc/1wpZn/ma/RB Content-Type: text/plain; charset=us-ascii I'm getting many hard read errors on a machine. I had these errors back in 4.1.1, and still in 4.2. A section of /var/log/messages says: Jan 23 17:12:44 ipv6-gw /kernel: ad0: HARD READ ERROR blk# 14484670ad0: HARD READ ERROR blk# 14484670 status=59 error=40 Jan 23 17:12:44 ipv6-gw /kernel: ad0: DMA problem fallback to PIO mode Jan 23 17:12:44 ipv6-gw /kernel: IPv6 packet filtering initialized, logging disabled Jan 23 17:12:44 ipv6-gw /kernel: ad0: HARD READ ERROR blk# 14484670 status=59 error=40 Jan 23 17:12:44 ipv6-gw /kernel: ad0: HARD READ ERROR blk# 14484670 status=59 error=40 Is there anyway to get rid of these problems? I've included the dmesg output. Thanks for any help that anyone can give me. Geoff Crompton --tThc/1wpZn/ma/RB Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; 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 10:07:57 EST 2001 root@ipv6-gw.eric.net.au:/usr/home/ghc/checkout/kame/freebsd4/sys/compile/P9KAME Timecounter "i8254" frequency 1193182 Hz CPU: Pentium III/Pentium III Xeon/Celeron (735.00-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x683 Stepping = 3 Features=0x383f9ff real memory = 134131712 (130988K bytes) avail memory = 126230528 (123272K bytes) Preloaded elf kernel "kernel" at 0xc0448000. Pentium Pro MTRR support enabled md0: Malloc disk altq: major number is 96 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 pcib2: at device 30.0 on pci0 pci2: on pcib2 pci2: (vendor=0x1274, dev=0x5880) at 9.0 xl0: <3Com 3c905C-TX Fast Etherlink XL> port 0xd400-0xd47f mem 0xf3800000-0xf380007f irq 9 at device 11.0 on pci2 xl0: Ethernet address: 00:01:02:54:c2:4f miibus0: on xl0 xlphy0: <3c905C 10/100 internal PHY> on miibus0 xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto xl1: <3Com 3c905C-TX Fast Etherlink XL> port 0xd000-0xd07f mem 0xf3000000-0xf300007f irq 9 at device 12.0 on pci2 xl1: Ethernet address: 00:01:02:54:c2:4e miibus1: on xl1 xlphy1: <3c905C 10/100 internal PHY> on miibus1 xlphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0xb800-0xb80f at device 31.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: port 0xb400-0xb41f irq 5 at device 31.2 on pci0 uhci0: (New UHCI DeviceId=0x24428086) usb0: on uhci0 usb0: USB revision 1.0 uhub0: (0x24428086) UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered pci0: (vendor=0x8086, dev=0x2443) at 31.3 irq 10 uhci1: port 0xb000-0xb01f irq 9 at device 31.4 on pci0 uhci1: (New UHCI DeviceId=0x24448086) usb1: on uhci1 usb1: USB revision 1.0 uhub1: (0x24448086) UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhub2: ALCOR Generic USB Hub, class 9/0, rev 1.10/1.00, addr 2 uhub2: 4 ports with 4 removable, self powered 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: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/9 bytes threshold plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 IP packet filtering initialized, divert enabled, rule-based forwarding disabled, default to deny, logging disabled faith0 XXX: driver didn't set ifq_maxlen IPsec: Initialized Security Association Processing. IP Filter: v3.4.8 initialized. Default = pass all, Logging = enabled ad0: 14594MB [29651/16/63] at ata0-master UDMA66 acd0: CDROM at ata1-master using PIO4 Mounting root from ufs:/dev/ad0s2a ad0: HARD READ ERROR blk# 14484670ad0: HARD READ ERROR blk# 14484670 status=59 error=40 ad0: DMA problem fallback to PIO mode IPv6 packet filtering initialized, logging disabled ad0: HARD READ ERROR blk# 14484670 status=59 error=40 ad0: HARD READ ERROR blk# 14484670 status=59 error=40 --tThc/1wpZn/ma/RB-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 22 22:57:33 2001 Delivered-To: freebsd-stable@freebsd.org Received: from dnvrpop2.dnvr.uswest.net (dnvrpop2.dnvr.uswest.net [206.196.128.4]) by hub.freebsd.org (Postfix) with SMTP id 4346B37B400 for ; Mon, 22 Jan 2001 22:57:12 -0800 (PST) Received: (qmail 42159 invoked by uid 0); 23 Jan 2001 06:57:10 -0000 Received: from dnvr-dsl-gw7-f-250.dnvr.uswest.net (HELO qwest.net) (63.227.58.250) by dnvrpop2.dnvr.uswest.net with SMTP; 23 Jan 2001 06:57:10 -0000 Date: Mon, 22 Jan 2001 23:57:17 -0700 Message-ID: <3A6D2B4C.4F9382A3@qwest.net> From: "Brad Tombaugh" To: freebsd-stable@freebsd.org X-Mailer: Mozilla 4.75 [en] (X11; U; FreeBSD 4.2-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 Subject: Problems Making Ports Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Several people, including me, have posted articles to comp.unix.bsd.frebsd.misc regarding problems making ports after updating to RELENG_4 (4.2-STABLE). The first symptom that I saw after "making world" was that when I attempted to "make" or "make install" any of several ports I got an error: orion# cd /usr/ports/textproc/docproj orion# make Error: your port uses an old layout. Please update it to match this bsd.port.mk. checking /urs/ports/Mk/bsd.port.mk shows several instances of this or similar messages, generally near a declaration for "pre-everything::" I noticed a comment that stated that you must have an updated INDEX for some targets, so I ran "make index" in /usr/ports with the following result: orion# cd /usr/ports orion# make index Generating INDEX - please wait.."/usr/ports/Mk/bsd.port.mk", line 626: Inconsistent operator for pre-everything make: fatal errors encountered -- cannot continue Done. My /usr/ports/Mk/bsd.port.mk is version: # $FreeBSD: ports/Mk/bsd.port.mk,v 1.361 2001/01/16 09:25:16 asami Exp $ Any ideas? -- Brad Tombaugh mailto:btombau@qwest.net http://www.users.qwest.net/~btombau To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 23 1: 5:23 2001 Delivered-To: freebsd-stable@freebsd.org Received: from aifhs8.alcatel.fr (aifhs8.alcatel.fr [212.208.74.153]) by hub.freebsd.org (Postfix) with ESMTP id A9A1837B400 for ; Tue, 23 Jan 2001 01:05:03 -0800 (PST) Received: from frmta003.netfr.alcatel.fr (frmta003.netfr.alcatel.fr [155.132.251.32]) by aifhs8.alcatel.fr (ALCANET/SMTP2) with SMTP id KAA19655; Tue, 23 Jan 2001 10:04:07 +0100 (MET) Received: by frmta003.netfr.alcatel.fr(Lotus SMTP MTA v4.6.7 (934.1 12-30-1999)) id C12569DD.0031CDD8 ; Tue, 23 Jan 2001 10:03:59 +0100 X-Lotus-FromDomain: ALCATEL From: Thierry.Herbelot@alcatel.fr To: "Geoffrey Crompton (RMIT Guest)" Cc: freebsd-stable@FreeBSD.ORG Message-ID: Date: Tue, 23 Jan 2001 10:03:51 +0100 Subject: Re: hard read errors Mime-Version: 1.0 Content-type: multipart/mixed; Boundary="0__=jK2gew425kNKZebMPzuuLueNsepgJozE3exIQa0GMHJjytzTquvP0P7k" Content-Disposition: inline Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --0__=jK2gew425kNKZebMPzuuLueNsepgJozE3exIQa0GMHJjytzTquvP0P7k Content-type: text/plain; charset=us-ascii Content-Disposition: inline Hello, these error messages tell you that your IDE disk is slowly dying : you should backup your data **as soon as possible**, and then change your disk TfH "Geoffrey Crompton (RMIT Guest)" on 23/01/2001 07:45:58 To: freebsd-stable@FreeBSD.ORG cc: (bcc: Thierry HERBELOT/FR/ALCATEL) Subject: hard read errors I'm getting many hard read errors on a machine. I had these errors back in 4.1.1, and still in 4.2. A section of /var/log/messages says: Jan 23 17:12:44 ipv6-gw /kernel: ad0: HARD READ ERROR blk# 14484670ad0: HARD READ ERROR blk# 14484670 status=59 error=40 Jan 23 17:12:44 ipv6-gw /kernel: ad0: DMA problem fallback to PIO mode Jan 23 17:12:44 ipv6-gw /kernel: IPv6 packet filtering initialized, logging disabled Jan 23 17:12:44 ipv6-gw /kernel: ad0: HARD READ ERROR blk# 14484670 status=59 error=40 Jan 23 17:12:44 ipv6-gw /kernel: ad0: HARD READ ERROR blk# 14484670 status=59 error=40 Is there anyway to get rid of these problems? I've included the dmesg output. Thanks for any help that anyone can give me. Geoff Crompton --0__=jK2gew425kNKZebMPzuuLueNsepgJozE3exIQa0GMHJjytzTquvP0P7k Content-type: application/octet-stream; name="dmesg" Content-Disposition: attachment; filename="dmesg" Content-transfer-encoding: base64 Q29weXJpZ2h0IChjKSAxOTkyLTIwMDAgVGhlIEZyZWVCU0QgUHJvamVjdC4NCkNvcHlyaWdodCAo YykgMTk3OSwgMTk4MCwgMTk4MywgMTk4NiwgMTk4OCwgMTk4OSwgMTk5MSwgMTk5MiwgMTk5Mywg MTk5NA0KCVRoZSBSZWdlbnRzIG9mIHRoZSBVbml2ZXJzaXR5IG9mIENhbGlmb3JuaWEuIEFsbCBy aWdodHMgcmVzZXJ2ZWQuDQpGcmVlQlNEIDQuMi1SRUxFQVNFICMwOiBUdWUgSmFuIDE2IDEwOjA3 OjU3IEVTVCAyMDAxDQogICAgcm9vdEBpcHY2LWd3LmVyaWMubmV0LmF1Oi91c3IvaG9tZS9naGMv Y2hlY2tvdXQva2FtZS9mcmVlYnNkNC9zeXMvY29tcGlsZS9QOUtBTUUNClRpbWVjb3VudGVyICJp ODI1NCIgIGZyZXF1ZW5jeSAxMTkzMTgyIEh6DQpDUFU6IFBlbnRpdW0gSUlJL1BlbnRpdW0gSUlJ IFhlb24vQ2VsZXJvbiAoNzM1LjAwLU1IeiA2ODYtY2xhc3MgQ1BVKQ0KICBPcmlnaW4gPSAiR2Vu dWluZUludGVsIiAgSWQgPSAweDY4MyAgU3RlcHBpbmcgPSAzDQogIEZlYXR1cmVzPTB4MzgzZjlm ZjxGUFUsVk1FLERFLFBTRSxUU0MsTVNSLFBBRSxNQ0UsQ1g4LFNFUCxNVFJSLFBHRSxNQ0EsQ01P VixQQVQsUFNFMzYsTU1YLEZYU1IsU1NFPg0KcmVhbCBtZW1vcnkgID0gMTM0MTMxNzEyICgxMzA5 ODhLIGJ5dGVzKQ0KYXZhaWwgbWVtb3J5ID0gMTI2MjMwNTI4ICgxMjMyNzJLIGJ5dGVzKQ0KUHJl bG9hZGVkIGVsZiBrZXJuZWwgImtlcm5lbCIgYXQgMHhjMDQ0ODAwMC4NClBlbnRpdW0gUHJvIE1U UlIgc3VwcG9ydCBlbmFibGVkDQptZDA6IE1hbGxvYyBkaXNrDQphbHRxOiBtYWpvciBudW1iZXIg aXMgOTYNCm5weDA6IDxtYXRoIHByb2Nlc3Nvcj4gb24gbW90aGVyYm9hcmQNCm5weDA6IElOVCAx NiBpbnRlcmZhY2UNCnBjaWIwOiA8SG9zdCB0byBQQ0kgYnJpZGdlPiBvbiBtb3RoZXJib2FyZA0K cGNpMDogPFBDSSBidXM+IG9uIHBjaWIwDQpwY2liMTogPFBDSSB0byBQQ0kgYnJpZGdlICh2ZW5k b3I9ODA4NiBkZXZpY2U9MTEzMSk+IGF0IGRldmljZSAxLjAgb24gcGNpMA0KcGNpMTogPFBDSSBi dXM+IG9uIHBjaWIxDQpwY2kxOiA8TlZpZGlhIFJpdmEgVmFudGEgVE5UMiBncmFwaGljcyBhY2Nl bGVyYXRvcj4gYXQgMC4wIGlycSAxMQ0KcGNpYjI6IDxQQ0kgdG8gUENJIGJyaWRnZSAodmVuZG9y PTgwODYgZGV2aWNlPTI0NGUpPiBhdCBkZXZpY2UgMzAuMCBvbiBwY2kwDQpwY2kyOiA8UENJIGJ1 cz4gb24gcGNpYjINCnBjaTI6IDx1bmtub3duIGNhcmQ+ICh2ZW5kb3I9MHgxMjc0LCBkZXY9MHg1 ODgwKSBhdCA5LjANCnhsMDogPDNDb20gM2M5MDVDLVRYIEZhc3QgRXRoZXJsaW5rIFhMPiBwb3J0 IDB4ZDQwMC0weGQ0N2YgbWVtIDB4ZjM4MDAwMDAtMHhmMzgwMDA3ZiBpcnEgOSBhdCBkZXZpY2Ug MTEuMCBvbiBwY2kyDQp4bDA6IEV0aGVybmV0IGFkZHJlc3M6IDAwOjAxOjAyOjU0OmMyOjRmDQpt aWlidXMwOiA8TUlJIGJ1cz4gb24geGwwDQp4bHBoeTA6IDwzYzkwNUMgMTAvMTAwIGludGVybmFs IFBIWT4gb24gbWlpYnVzMA0KeGxwaHkwOiAgMTBiYXNlVCwgMTBiYXNlVC1GRFgsIDEwMGJhc2VU WCwgMTAwYmFzZVRYLUZEWCwgYXV0bw0KeGwxOiA8M0NvbSAzYzkwNUMtVFggRmFzdCBFdGhlcmxp bmsgWEw+IHBvcnQgMHhkMDAwLTB4ZDA3ZiBtZW0gMHhmMzAwMDAwMC0weGYzMDAwMDdmIGlycSA5 IGF0IGRldmljZSAxMi4wIG9uIHBjaTINCnhsMTogRXRoZXJuZXQgYWRkcmVzczogMDA6MDE6MDI6 NTQ6YzI6NGUNCm1paWJ1czE6IDxNSUkgYnVzPiBvbiB4bDENCnhscGh5MTogPDNjOTA1QyAxMC8x MDAgaW50ZXJuYWwgUEhZPiBvbiBtaWlidXMxDQp4bHBoeTE6ICAxMGJhc2VULCAxMGJhc2VULUZE WCwgMTAwYmFzZVRYLCAxMDBiYXNlVFgtRkRYLCBhdXRvDQppc2FiMDogPFBDSSB0byBJU0EgYnJp ZGdlICh2ZW5kb3I9ODA4NiBkZXZpY2U9MjQ0MCk+IGF0IGRldmljZSAzMS4wIG9uIHBjaTANCmlz YTA6IDxJU0EgYnVzPiBvbiBpc2FiMA0KYXRhcGNpMDogPEludGVsIElDSDIgQVRBMTAwIGNvbnRy b2xsZXI+IHBvcnQgMHhiODAwLTB4YjgwZiBhdCBkZXZpY2UgMzEuMSBvbiBwY2kwDQphdGEwOiBh dCAweDFmMCBpcnEgMTQgb24gYXRhcGNpMA0KYXRhMTogYXQgMHgxNzAgaXJxIDE1IG9uIGF0YXBj aTANCnVoY2kwOiA8VUhDSSAoZ2VuZXJpYykgVVNCIGNvbnRyb2xsZXI+IHBvcnQgMHhiNDAwLTB4 YjQxZiBpcnEgNSBhdCBkZXZpY2UgMzEuMiBvbiBwY2kwDQp1aGNpMDogKE5ldyBVSENJIERldmlj ZUlkPTB4MjQ0MjgwODYpDQp1c2IwOiA8VUhDSSAoZ2VuZXJpYykgVVNCIGNvbnRyb2xsZXI+IG9u IHVoY2kwDQp1c2IwOiBVU0IgcmV2aXNpb24gMS4wDQp1aHViMDogKDB4MjQ0MjgwODYpIFVIQ0kg cm9vdCBodWIsIGNsYXNzIDkvMCwgcmV2IDEuMDAvMS4wMCwgYWRkciAxDQp1aHViMDogMiBwb3J0 cyB3aXRoIDIgcmVtb3ZhYmxlLCBzZWxmIHBvd2VyZWQNCnBjaTA6IDx1bmtub3duIGNhcmQ+ICh2 ZW5kb3I9MHg4MDg2LCBkZXY9MHgyNDQzKSBhdCAzMS4zIGlycSAxMA0KdWhjaTE6IDxVSENJIChn ZW5lcmljKSBVU0IgY29udHJvbGxlcj4gcG9ydCAweGIwMDAtMHhiMDFmIGlycSA5IGF0IGRldmlj ZSAzMS40IG9uIHBjaTANCnVoY2kxOiAoTmV3IFVIQ0kgRGV2aWNlSWQ9MHgyNDQ0ODA4NikNCnVz YjE6IDxVSENJIChnZW5lcmljKSBVU0IgY29udHJvbGxlcj4gb24gdWhjaTENCnVzYjE6IFVTQiBy ZXZpc2lvbiAxLjANCnVodWIxOiAoMHgyNDQ0ODA4NikgVUhDSSByb290IGh1YiwgY2xhc3MgOS8w LCByZXYgMS4wMC8xLjAwLCBhZGRyIDENCnVodWIxOiAyIHBvcnRzIHdpdGggMiByZW1vdmFibGUs IHNlbGYgcG93ZXJlZA0KdWh1YjI6IEFMQ09SIEdlbmVyaWMgVVNCIEh1YiwgY2xhc3MgOS8wLCBy ZXYgMS4xMC8xLjAwLCBhZGRyIDINCnVodWIyOiA0IHBvcnRzIHdpdGggNCByZW1vdmFibGUsIHNl bGYgcG93ZXJlZA0KZmRjMDogPE5FQyA3MjA2NUIgb3IgY2xvbmU+IGF0IHBvcnQgMHgzZjAtMHgz ZjUsMHgzZjcgaXJxIDYgZHJxIDIgb24gaXNhMA0KZmRjMDogRklGTyBlbmFibGVkLCA4IGJ5dGVz IHRocmVzaG9sZA0KZmQwOiA8MTQ0MC1LQiAzLjUiIGRyaXZlPiBvbiBmZGMwIGRyaXZlIDANCmF0 a2JkYzA6IDxLZXlib2FyZCBjb250cm9sbGVyIChpODA0Mik+IGF0IHBvcnQgMHg2MCwweDY0IG9u IGlzYTANCmF0a2JkMDogPEFUIEtleWJvYXJkPiBmbGFncyAweDEgaXJxIDEgb24gYXRrYmRjMA0K a2JkMCBhdCBhdGtiZDANCnBzbTA6IDxQUy8yIE1vdXNlPiBpcnEgMTIgb24gYXRrYmRjMA0KcHNt MDogbW9kZWwgR2VuZXJpYyBQUy8yIG1vdXNlLCBkZXZpY2UgSUQgMA0KdmdhMDogPEdlbmVyaWMg SVNBIFZHQT4gYXQgcG9ydCAweDNjMC0weDNkZiBpb21lbSAweGEwMDAwLTB4YmZmZmYgb24gaXNh MA0Kc2MwOiA8U3lzdGVtIGNvbnNvbGU+IGF0IGZsYWdzIDB4MTAwIG9uIGlzYTANCnNjMDogVkdB IDwxNiB2aXJ0dWFsIGNvbnNvbGVzLCBmbGFncz0weDMwMD4NCnNpbzAgYXQgcG9ydCAweDNmOC0w eDNmZiBpcnEgNCBmbGFncyAweDEwIG9uIGlzYTANCnNpbzA6IHR5cGUgMTY1NTBBDQpzaW8xIGF0 IHBvcnQgMHgyZjgtMHgyZmYgaXJxIDMgb24gaXNhMA0Kc2lvMTogdHlwZSAxNjU1MEENCnBwYzA6 IDxQYXJhbGxlbCBwb3J0PiBhdCBwb3J0IDB4Mzc4LTB4MzdmIGlycSA3IG9uIGlzYTANCnBwYzA6 IFNNQy1saWtlIGNoaXBzZXQgKEVDUC9FUFAvUFMyL05JQkJMRSkgaW4gQ09NUEFUSUJMRSBtb2Rl DQpwcGMwOiBGSUZPIHdpdGggMTYvMTYvOSBieXRlcyB0aHJlc2hvbGQNCnBsaXAwOiA8UExJUCBu ZXR3b3JrIGludGVyZmFjZT4gb24gcHBidXMwDQpscHQwOiA8UHJpbnRlcj4gb24gcHBidXMwDQps cHQwOiBJbnRlcnJ1cHQtZHJpdmVuIHBvcnQNCnBwaTA6IDxQYXJhbGxlbCBJL08+IG9uIHBwYnVz MA0KSVAgcGFja2V0IGZpbHRlcmluZyBpbml0aWFsaXplZCwgZGl2ZXJ0IGVuYWJsZWQsIHJ1bGUt YmFzZWQgZm9yd2FyZGluZyBkaXNhYmxlZCwgZGVmYXVsdCB0byBkZW55LCBsb2dnaW5nIGRpc2Fi bGVkDQpmYWl0aDAgWFhYOiBkcml2ZXIgZGlkbid0IHNldCBpZnFfbWF4bGVuDQpJUHNlYzogSW5p dGlhbGl6ZWQgU2VjdXJpdHkgQXNzb2NpYXRpb24gUHJvY2Vzc2luZy4NCklQIEZpbHRlcjogdjMu NC44IGluaXRpYWxpemVkLiAgRGVmYXVsdCA9IHBhc3MgYWxsLCBMb2dnaW5nID0gZW5hYmxlZA0K YWQwOiAxNDU5NE1CIDxTVDMxNTMyMEE+IFsyOTY1MS8xNi82M10gYXQgYXRhMC1tYXN0ZXIgVURN QTY2DQphY2QwOiBDRFJPTSA8TFRONDg1Uz4gYXQgYXRhMS1tYXN0ZXIgdXNpbmcgUElPNA0KTW91 bnRpbmcgcm9vdCBmcm9tIHVmczovZGV2L2FkMHMyYQ0KYWQwOiBIQVJEIFJFQUQgRVJST1IgYmxr IyAxNDQ4NDY3MGFkMDogSEFSRCBSRUFEIEVSUk9SIGJsayMgMTQ0ODQ2NzAgc3RhdHVzPTU5IGVy cm9yPTQwDQphZDA6IERNQSBwcm9ibGVtIGZhbGxiYWNrIHRvIFBJTyBtb2RlDQpJUHY2IHBhY2tl dCBmaWx0ZXJpbmcgaW5pdGlhbGl6ZWQsIGxvZ2dpbmcgZGlzYWJsZWQNCmFkMDogSEFSRCBSRUFE IEVSUk9SIGJsayMgMTQ0ODQ2NzAgc3RhdHVzPTU5IGVycm9yPTQwDQphZDA6IEhBUkQgUkVBRCBF UlJPUiBibGsjIDE0NDg0NjcwIHN0YXR1cz01OSBlcnJvcj00MA0KDQo= --0__=jK2gew425kNKZebMPzuuLueNsepgJozE3exIQa0GMHJjytzTquvP0P7k-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 23 1: 9:18 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 AEE6137B401 for ; Tue, 23 Jan 2001 01:08:58 -0800 (PST) Received: from [203.164.12.28] by www.quake.com.au (NTMail 4.30.0012/AH9370.63.d1acf55c) with ESMTP id rgvsaaaa for ; Tue, 23 Jan 2001 20:17:35 +1100 Message-ID: <3A6D4A30.806FCCFD@quake.com.au> Date: Tue, 23 Jan 2001 20:09:04 +1100 From: Kal Torak X-Mailer: Mozilla 4.73 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: "Geoffrey Crompton (RMIT Guest)" Cc: freebsd-stable@freebsd.org Subject: Re: hard read errors References: <20010123174558.A427@gecko.eric.net.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Geoffrey Crompton (RMIT Guest)" wrote: > > I'm getting many hard read errors on a machine. I had these errors > back in 4.1.1, and still in 4.2. A section of /var/log/messages says: > > Jan 23 17:12:44 ipv6-gw /kernel: ad0: HARD READ ERROR blk# 14484670ad0: HARD READ ERROR blk# 14484670 status=59 error=40 > Jan 23 17:12:44 ipv6-gw /kernel: ad0: DMA problem fallback to PIO mode > Jan 23 17:12:44 ipv6-gw /kernel: IPv6 packet filtering initialized, logging disabled > Jan 23 17:12:44 ipv6-gw /kernel: ad0: HARD READ ERROR blk# 14484670 status=59 error=40 > Jan 23 17:12:44 ipv6-gw /kernel: ad0: HARD READ ERROR blk# 14484670 status=59 error=40 Soren MFC'd a new ata-dma.c just a few days ago... Its worth getting the new source and compiling it into your kernel and see if that fixes your problems To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 23 1:12:31 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 AAF6C37B400 for ; Tue, 23 Jan 2001 01:12:13 -0800 (PST) Received: from [203.164.12.28] by www.quake.com.au (NTMail 4.30.0012/AH9370.63.d1acf55c) with ESMTP id tgvsaaaa for ; Tue, 23 Jan 2001 20:20:50 +1100 Message-ID: <3A6D4AF3.69241B5E@quake.com.au> Date: Tue, 23 Jan 2001 20:12:19 +1100 From: Kal Torak X-Mailer: Mozilla 4.73 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Brad Tombaugh Cc: freebsd-stable@freebsd.org Subject: Re: Problems Making Ports References: <3A6D2B4C.4F9382A3@qwest.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brad Tombaugh wrote: > > Several people, including me, have posted articles to > comp.unix.bsd.frebsd.misc regarding problems making ports after updating > to RELENG_4 (4.2-STABLE). > > The first symptom that I saw after "making world" was that when I > attempted to "make" or "make install" any of several ports I got an > error: > > orion# cd /usr/ports/textproc/docproj > orion# make > Error: your port uses an old layout. Please update it to > match this bsd.port.mk. > > checking /urs/ports/Mk/bsd.port.mk shows several instances of this or > similar messages, generally near a declaration for "pre-everything::" > > I noticed a comment that stated that you must have an updated INDEX for > some targets, so I ran "make index" in /usr/ports with the following > result: > > orion# cd /usr/ports > orion# make index > Generating INDEX - please wait.."/usr/ports/Mk/bsd.port.mk", > line 626: Inconsistent operator for pre-everything > make: fatal errors encountered -- cannot continue > Done. > > My /usr/ports/Mk/bsd.port.mk is version: > > # $FreeBSD: ports/Mk/bsd.port.mk,v 1.361 2001/01/16 09:25:16 > asami Exp $ If you had read /usr/src/UPDATING then you would of seen that after an upgrade to 4.2 you are required to cvsup your whole ports tree since changes were made to the base port structure... Reading the UPDATING file properly solves almost all upgrading problems... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 23 1:21:26 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 AF8C937B400 for ; Tue, 23 Jan 2001 01:21:09 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f0N9L9v20582 for stable@freebsd.org; Tue, 23 Jan 2001 01:21:09 -0800 (PST) Date: Tue, 23 Jan 2001 01:21:09 -0800 From: Alfred Perlstein To: stable@freebsd.org Subject: Dell PERC 3 support? Message-ID: <20010123012109.O26076@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A friend just asked me if we support the PERC 3 cards shipped in Dell servers. If not, anyone have a recommendation for a controller in the same price performance category that is supported? thanks, -- -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 Tue Jan 23 1:56:35 2001 Delivered-To: freebsd-stable@freebsd.org Received: from c014.sfo.cp.net (c014-h003.c014.sfo.cp.net [209.228.12.67]) by hub.freebsd.org (Postfix) with SMTP id B25CB37B6A0 for ; Tue, 23 Jan 2001 01:56:14 -0800 (PST) Received: (cpmta 18121 invoked from network); 23 Jan 2001 01:56:13 -0800 Received: from d8c81e5f.dsl.flashcom.net (HELO quadrajet.flashcom.com) (216.200.30.95) by smtp.flashcom.net (209.228.12.67) with SMTP; 23 Jan 2001 01:56:13 -0800 X-Sent: 23 Jan 2001 09:56:13 GMT Received: (from guy@localhost) by quadrajet.flashcom.com (8.9.3/8.9.3) id BAA04898; Tue, 23 Jan 2001 01:56:12 -0800 (PST) (envelope-from gharris) Date: Tue, 23 Jan 2001 01:56:12 -0800 From: Guy Harris To: Neil Brown Cc: Matthias Andree , Linux NFS mailing list , reiserfs-list@namesys.com, FreeBSD Stable Subject: Re: [NFS] Incompatible: FreeBSD 4.2 client, Linux 2.2.18 nfsv3 server, ReiserFS Message-ID: <20010123015612.H345@quadrajet.flashcom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Beware of error messages reported by tcpdump... they are misleading. > The error code in the tcp packet is an "NFS error code" which should > not be confused with an "Unix-errno" error code, though there are > sometimes similarities. > tcpdump seems to assume that nfs error codes *are* unix error codes. "Fixed in 3.6"; tcpdump 3.6 doesn't assume NFS error codes are errno values for the current host. However, the "116" in the 23:22:29.528764 emma1.nfs > freebsd.526363636: reply ok 116 access ERROR: Read-only file system (ttl 64, id 12889) line isn't the error value, it's the length of the packet; "nfsreply_print()' in tcpdump 3.5 does: if (!nflag) (void)printf("%s.nfs > %s.%u: reply %s %d", ipaddr_string(&ip->ip_src), ipaddr_string(&ip->ip_dst), (u_int32_t)ntohl(rp->rm_xid), ntohl(rp->rm_reply.rp_stat) == MSG_ACCEPTED? "ok":"ERR", length); else (void)printf("%s.%u > %s.%u: reply %s %d", ipaddr_string(&ip->ip_src), NFS_PORT, ipaddr_string(&ip->ip_dst), (u_int32_t)ntohl(rp->rm_xid), ntohl(rp->rm_reply.rp_stat) == MSG_ACCEPTED? "ok":"ERR", length); EROFS is 30 on both Linux/x86 and FreeBSD (and 30 goes, I suspect, all the way back to V6 UNIX or earlier, so I suspect just about any UNIX with AT&T code in it, or even that once upon a time had AT&T code in it, e.g. most of the commercial UNIXes, use 30 for EROFS). So... > So my guess is that the reiserfs code which tries to support nfsd (which > may well involve some patches to knfsd) is having problems, and wants > to return ESTALE, but returns it without converting to an NFS error > code. ..."Read-only file system" probably means you got back EROFS from the server, and the ReiserFS code is probably not to blame - the Linux nfsd in 2.2.18 appears to assume that the underlying file system returns Linux errno values (or the negative of same), and maps them to NFS error values. I note, however, that Solaris's NFS server, as I remember, will, if you make a V3 ACCESS call, asking for ACCESS3_MODIFY and/or ACCESS3_EXTEND (and/or, I suspect, ACCESS3_DELETE), will, if the file being asked about is on a read-only file system, just return access permissions with those bits turned off - RFC 1813 doesn't list NFS3ERR_ROFS as one of the error returns permissible from ACCESS. (I remember this because I saw a note on the "toasters" mailing list, where somebody's Solaris client was trying to write to a file on a NetApp file server when that file was in a snapshot, and those files aren't writable; we returned EROFS to that attempt, and the Solaris client apparently decided "well, maybe he hasn't remounted the file system read/write yet", and just kept trying, to no avail. I figured the underlying problem was that we weren't returning "no, you can't write it" to an ACCESS call, and that, were we to do so, the "open()" of the file would fail, and the Solaris box wouldn't try to write to it in the first place; I sent mail back to the person who sent the note, asking him to try it with a Solaris NFS server, and, sure enough, the Solaris box did, as I remember, what I described above. I filed a bug inside NetApp about this, and our server was fixed to do what the Solaris server does. As the original implementor of V3 on NetApp boxes, I'll cheerfully take the 50 lashes with a wet noodle called for here. :-)) Perhaps the Linux server should, in "nfsd_access()", treat "nfserr_rofs" the same way it treats "nfserr_perm" and "nfserr_acces", and just say the access type is denied but the access query succeeded, doing the same thing that Solaris and a future release of the NetApp software will do. (It looks as if the FreeBSD NFS server already does that - it treats all errors from "nfsrv_access()" as meaning "access denied", not "access call failed", so it treats EROFS in that fashion. The same probably applies to other BSDs.) As for why the V2 client doesn't appear to have this problem, the V2 client doesn't make an ACCESS call, because NFS V2 doesn't have an ACCESS call to make. As for why it's a problem with ReiserFS but not ext2fs, if the ReiserFS file system in question wasn't mounted read-only, perhaps somehow it's bogusly reporting read-onlyness to the NFS server. If it *was* mounted read-only, was the ext2 file system also mounted read-only? If not, that might explain it. As for why it's a problem with the FreeBSD client but not the Solaris client, I'm not sure - a quick look at the 4.2 client code doesn't seem to show any way in which the EROFS is "sticky" to the extent that it affects all client accesses, as it doesn't cache the result of an ACCESS call that failed. It may just be that the Solaris client just ignores NFS3ERR_ROFS from an ACCESS call and does an access check based on the permission bits, rather than returning EROFS, whilst the FreeBSD client returns EROFS; if ReiserFS is returning EROFS bogusly, that might cause the symptoms in question. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 23 1:59: 8 2001 Delivered-To: freebsd-stable@freebsd.org Received: from cs.huji.ac.il (cs.huji.ac.il [132.65.16.10]) by hub.freebsd.org (Postfix) with ESMTP id 3A6F537B6A1 for ; Tue, 23 Jan 2001 01:58:51 -0800 (PST) Received: from sexta.cs.huji.ac.il ([132.65.16.13] ident=danny) by cs.huji.ac.il with esmtp (Exim 3.20 #1) id 14L0Dx-0007JE-00; Tue, 23 Jan 2001 11:58:49 +0200 X-Mailer: exmh version 2.2 06/23/2000 with nmh-0.24 To: Alfred Perlstein , stable@freebsd.org Subject: Re: Dell PERC 3 support? In-reply-to: Your message of Tue, 23 Jan 2001 01:21:09 -0800 . Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 23 Jan 2001 11:58:49 +0200 From: Danny Braniss Message-Id: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20010123012109.O26076@fw.wintelcom.net>you write: }A friend just asked me if we support the PERC 3 cards shipped in }Dell servers. If not, anyone have a recommendation for a controller }in the same price performance category that is supported? if it's a Dell p-somthing 2450, then there is support, http://people.freebsd.org/~msmith/RAID i couldn't boot from the raid, and only tested raid0 (only had 2 disks) and the speeds were very nice. btw, if you figure out how to make it bootable, i would like to know. danny To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 23 2:22:34 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 C0C0337B698 for ; Tue, 23 Jan 2001 02:22:13 -0800 (PST) Received: (from dom@localhost) by clove.rp.lan (8.9.3/8.8.7) id KAA29414; Tue, 23 Jan 2001 10:12:38 GMT X-Authentication-Warning: clove.rp.lan: dom set sender to dom@semantico.com using -f Date: Tue, 23 Jan 2001 10:12:38 +0000 From: Dominic Mitchell To: Juraj Lutter Cc: "Patrick M. Hausen" , Ted Sikora , freebsd-stable@FreeBSD.ORG Subject: Re: ssh login Message-ID: <20010123101238.B24385@semantico.com> References: <20010122184442.C48980@wilbury.sk> <200101221801.TAA51972@hugo10.ka.punkt.de> <20010122192025.A51214@wilbury.sk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3us In-Reply-To: <20010122192025.A51214@wilbury.sk> X-Warning: Incoming message from The Big Giant Head! X-OS: Linux 2.2.13 i686 X-Uptime: 9:12am up 25 days, 20:32, 5 users, load average: 0.07, 0.03, 0.00 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jan 22, 2001 at 07:20:25PM +0100, Juraj Lutter wrote: > On Mon, Jan 22, 2001 at 07:01:55PM +0100, Patrick M. Hausen wrote: > > Well, using su would not save you from a patched client recording > > your keystrokes. > > I know that F-Secure SSH client (the old one 16 and 32bit supporting > ssh1 only) is keylogger-proof and it does not start and crashes with a > strange error at startup (tested on Win95). Not against a keyboard tap, it isn't. -Dom (Paranoia, my best friend) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 23 2:40:32 2001 Delivered-To: freebsd-stable@freebsd.org Received: from vexpert.dbai.tuwien.ac.at (vexpert.dbai.tuwien.ac.at [128.130.111.12]) by hub.freebsd.org (Postfix) with ESMTP id ECEB537B400 for ; Tue, 23 Jan 2001 02:40:10 -0800 (PST) Received: from deneb.dbai.tuwien.ac.at (deneb [128.130.111.2]) by vexpert.dbai.tuwien.ac.at (8.11.1/8.11.1) with ESMTP id f0NAe8e02929; Tue, 23 Jan 2001 11:40:08 +0100 (MET) Received: from localhost (pfeifer@localhost) by deneb.dbai.tuwien.ac.at (8.11.1/8.11.1) with ESMTP id f0NAe7Q54293; Tue, 23 Jan 2001 11:40:08 +0100 (CET) (envelope-from pfeifer@dbai.tuwien.ac.at) X-Authentication-Warning: deneb.dbai.tuwien.ac.at: pfeifer owned process doing -bs Date: Tue, 23 Jan 2001 11:40:07 +0100 (CET) From: Gerald Pfeifer To: Cc: Subject: Re: passwd (still) broken in NIS environments 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 Not a single reply. Folks, this *is* a serious problem. We *are* willing to help anyone willing to fix this, but we just cannot fix every problem by ourself (even though we do try to help wherever possible, e.g. by providing FreeBSD portability patches for other software.) Gerald On Fri, 12 Jan 2001, Gerald Pfeifer wrote: > Someone changed passwd/yppasswd such that now (on 4.2-RELEASE, put > presumably also -STABLE) it is broken. > > NIS-Server: Solaris 2.6 /SPARC with current Recommended Patches > NIS-Client: FreeBSD 4.2 /i386 > > Changing NIS password for user on NIS-server. > Old Password: > New password: > Retype new password: > passwd: failed to change NIS password: RPC: Server can't decode arguments > > When trying to debug this on the Solaris box, I got the following output > from snoop: > > client -> server PORTMAP C GETPORT prog=100009 (NISPASSWD) vers=1 proto=UDP > server -> client PORTMAP R GETPORT port=819 > client -> server NISPASSWD C > server -> client RPC R (#196) XID=861861090 Garbage arguments > > Any ideas what might have caused this breakage? This worked w/o problems > for the past three or four years (and corresponding FreeBSD releases). > > Anyone willing to help me debug this? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 23 2:49:31 2001 Delivered-To: freebsd-stable@freebsd.org Received: from m1d-mail.modul1.se (m1d-mail.modul1.se [194.237.144.247]) by hub.freebsd.org (Postfix) with ESMTP id 3AB6D37B401 for ; Tue, 23 Jan 2001 02:49:11 -0800 (PST) Received: by m1d-mail.modul1.se with Internet Mail Service (5.5.2653.19) id ; Tue, 23 Jan 2001 11:49:00 +0100 Message-ID: <94CD9085C1E6D3119C7C00A024A80EF0038948D4@m1d-mail.modul1.se> From: Hallgren Tommy To: "'freebsd-stable@freebsd.org '" Subject: FreebSD 3.5S to FreeBSD 4.x-STABLE problem Date: Tue, 23 Jan 2001 11:48:55 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! I'm trying to upgrade my system to 4.x-STABLE. The system runs a fresh 3.5-stable and I've cvsup'ed the source to RELENG_4. I've tried removing /usr/src and cvsuping, I've tried updating my existant /usr/src to RELENG_4. When I follow /usr/src/UPDATING I always get the same error: Extracting config.h (with variable substitutions) cc -O -pipe -I/usr/src/gnu/usr.bin/perl/miniperl/../../../../contrib/perl5 -I/usr/obj/usr/src/gnu/usr.bin/perl/miniperl -c /usr/src/gnu/usr.bin/perl/miniperl/../../../../contrib/perl5/miniperlmain.c ln -sf /usr/src/gnu/usr.bin/perl/miniperl/../../../../contrib/perl5/op.c opmini.c cc -O -pipe -I/usr/src/gnu/usr.bin/perl/miniperl/../../../../contrib/perl5 -I/usr/obj/usr/src/gnu/usr.bin/perl/miniperl -c opmini.c cc -O -pipe -I/usr/src/gnu/usr.bin/perl/miniperl/../../../../contrib/perl5 -I/usr/obj/usr/src/gnu/usr.bin/perl/miniperl -L/usr/obj/usr/src/gnu/usr.bin/perl/miniperl/../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 function `Perl_pp_aassign': pp_hot.o(.text+0x16a1): undefined reference to `setresuid' pp_hot.o(.text+0x16d4): undefined reference to `setresgid' What am I doing wrong? Thanks in advance, Regards, Tommy PS. Please CC me. DS. ########################################### This message has been scanned by F-Secure Anti-Virus for Microsoft Exchange. For more information, connect to http://www.F-Secure.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 23 2:56:29 2001 Delivered-To: freebsd-stable@freebsd.org Received: from aifhs8.alcatel.fr (aifhs8.alcatel.fr [212.208.74.153]) by hub.freebsd.org (Postfix) with ESMTP id A107837B699 for ; Tue, 23 Jan 2001 02:56:08 -0800 (PST) Received: from frmta003.netfr.alcatel.fr (frmta003.netfr.alcatel.fr [155.132.251.32]) by aifhs8.alcatel.fr (ALCANET/SMTP2) with SMTP id LAA10806; Tue, 23 Jan 2001 11:56:05 +0100 (MET) Received: by frmta003.netfr.alcatel.fr(Lotus SMTP MTA v4.6.7 (934.1 12-30-1999)) id C12569DD.003C0CC3 ; Tue, 23 Jan 2001 11:55:54 +0100 X-Lotus-FromDomain: ALCATEL From: Thierry.Herbelot@alcatel.fr To: Gerald Pfeifer Cc: freebsd-stable@FreeBSD.ORG, admin@dbai.tuwien.ac.at Message-ID: Date: Tue, 23 Jan 2001 11:55:46 +0100 Subject: Re: passwd (still) broken in NIS environments Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Do you have the same crypting algorithm on both ends ? (FreeBSD recently went to MD5 as a standard - Solaris most likely is still using DES) TfH Gerald Pfeifer on 23/01/2001 11:40:07 To: freebsd-stable@FreeBSD.ORG cc: admin@dbai.tuwien.ac.at(bcc: Thierry HERBELOT/FR/ALCATEL) Subject: Re: passwd (still) broken in NIS environments Not a single reply. Folks, this *is* a serious problem. We *are* willing to help anyone willing to fix this, but we just cannot fix every problem by ourself (even though we do try to help wherever possible, e.g. by providing FreeBSD portability patches for other software.) Gerald On Fri, 12 Jan 2001, Gerald Pfeifer wrote: > Someone changed passwd/yppasswd such that now (on 4.2-RELEASE, put > presumably also -STABLE) it is broken. > > NIS-Server: Solaris 2.6 /SPARC with current Recommended Patches > NIS-Client: FreeBSD 4.2 /i386 > > Changing NIS password for user on NIS-server. > Old Password: > New password: > Retype new password: > passwd: failed to change NIS password: RPC: Server can't decode arguments > > When trying to debug this on the Solaris box, I got the following output > from snoop: > > client -> server PORTMAP C GETPORT prog=100009 (NISPASSWD) vers=1 proto=UDP > server -> client PORTMAP R GETPORT port=819 > client -> server NISPASSWD C > server -> client RPC R (#196) XID=861861090 Garbage arguments > > Any ideas what might have caused this breakage? This worked w/o problems > for the past three or four years (and corresponding FreeBSD releases). > > Anyone willing to help me debug this? 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 23 3: 0:45 2001 Delivered-To: freebsd-stable@freebsd.org Received: from aifhs8.alcatel.fr (aifhs8.alcatel.fr [212.208.74.153]) by hub.freebsd.org (Postfix) with ESMTP id 73F8D37B699 for ; Tue, 23 Jan 2001 03:00:28 -0800 (PST) Received: from frmta003.netfr.alcatel.fr (frmta003.netfr.alcatel.fr [155.132.251.32]) by aifhs8.alcatel.fr (ALCANET/SMTP2) with SMTP id MAA12762 for ; Tue, 23 Jan 2001 12:00:33 +0100 (MET) Received: by frmta003.netfr.alcatel.fr(Lotus SMTP MTA v4.6.7 (934.1 12-30-1999)) id C12569DD.003C7591 ; Tue, 23 Jan 2001 12:00:22 +0100 X-Lotus-FromDomain: ALCATEL From: Thierry.Herbelot@alcatel.fr To: stable@freebsd.org Message-ID: Date: Tue, 23 Jan 2001 12:00:17 +0100 Subject: Running with very high HZ ? Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, is there any limitations to the frequency of the clock ? more precisely : is it ok to run a recent PC (P-III + BX chipset) with HZ=5000 ? (I remember a comment in ipfw or dummynet advising the use of HZ=1000, is-it ok to go higher ?) TfH To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 23 3:43:47 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 BDF1537B8BA for ; Tue, 23 Jan 2001 03:43:26 -0800 (PST) Received: from pcle2.cc.univie.ac.at (pcle2.cc.univie.ac.at [131.130.2.177]) by mailbox.univie.ac.at (8.9.3/8.9.3) with ESMTP id MAA95700 for ; Tue, 23 Jan 2001 12:43:24 +0100 Date: Tue, 23 Jan 2001 12:42:26 +0100 (CET) From: Lukas Ertl X-X-Sender: To: Subject: make buildworld fails 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 Hi, "make buildworld" constantly fails on my 4.2-STABLE machine. I cvsup'ed freshly, but the problem persists. Here is the error log: -------------------------------------------------------------- >>> stage 4: make dependencies -------------------------------------------------------------- cd /usr/src; MAKEOBJDIRPREFIX=3D/usr/obj COMPILER_PATH=3D/usr/obj/usr/src/i386/usr/libexec:/usr/obj/usr/src/i386/usr= /bin LIBRARY_PATH=3D/usr/obj/usr/src/i386/usr/lib:/usr/obj/usr/src/i386/usr/lib OBJFORMAT_PATH=3D/usr/obj/usr/src/i386/usr/libexec PERL5LIB=3D/usr/obj/usr/src/i386/usr/libdata/perl/5.00503 DESTDIR=3D/usr/obj/usr/src/i386 INSTALL=3D"sh /usr/src/tools/install.sh" PATH=3D/usr/obj/usr/src/i386/usr/sbin:/usr/obj/usr/src/i386/usr/bin:/usr/ob= j/usr/src/i386/usr/games:/sbin:/bin:/usr/sbin:/usr/bin make -f Makefile.inc1 par-depend =3D=3D=3D> share/info =3D=3D=3D> include =3D=3D=3D> include/rpcsvc =3D=3D=3D> lib =3D=3D=3D> lib/csu/i386-elf =3D=3D=3D> lib/libcom_err =3D=3D=3D> lib/libcom_err/doc =3D=3D=3D> lib/libcrypt =3D=3D=3D> lib/../secure/lib/libcrypt =3D=3D=3D> lib/msun =3D=3D=3D> lib/libmd =3D=3D=3D> lib/libncurses =3D=3D=3D> lib/libradius =3D=3D=3D> lib/libskey =3D=3D=3D> lib/libtacplus =3D=3D=3D> lib/libutil =3D=3D=3D> lib/compat =3D=3D=3D> lib/compat/compat1x =3D=3D=3D> lib/compat/compat20 =3D=3D=3D> lib/compat/compat21 =3D=3D=3D> lib/compat/compat22 =3D=3D=3D> lib/compat/compat3x.i386 =3D=3D=3D> lib/libalias =3D=3D=3D> lib/libatm =3D=3D=3D> lib/libc =3D=3D=3D> lib/libc_r =3D=3D=3D> lib/libcalendar =3D=3D=3D> lib/libcam =3D=3D=3D> lib/libcompat =3D=3D=3D> lib/libdevstat =3D=3D=3D> lib/libdisk =3D=3D=3D> lib/libedit =3D=3D=3D> lib/libfetch =3D=3D=3D> lib/libform =3D=3D=3D> lib/libftpio =3D=3D=3D> lib/libgnumalloc =3D=3D=3D> lib/libipsec =3D=3D=3D> lib/libipx =3D=3D=3D> lib/libisc =3D=3D=3D> lib/libkvm =3D=3D=3D> lib/libmenu =3D=3D=3D> lib/libncp =3D=3D=3D> lib/libnetgraph =3D=3D=3D> lib/libopie =3D=3D=3D> lib/libpam =3D=3D=3D> lib/libpam/modules =3D=3D=3D> lib/libpam/modules/pam_cleartext_pass_ok =3D=3D=3D> lib/libpam/modules/pam_deny =3D=3D=3D> lib/libpam/modules/pam_opie =3D=3D=3D> lib/libpam/modules/pam_permit =3D=3D=3D> lib/libpam/modules/pam_radius =3D=3D=3D> lib/libpam/modules/pam_skey =3D=3D=3D> lib/libpam/modules/pam_ssh =3D=3D=3D> lib/libpam/modules/pam_tacplus =3D=3D=3D> lib/libpam/modules/pam_unix =3D=3D=3D> lib/libpam/libpam =3D=3D=3D> lib/libpanel =3D=3D=3D> lib/libpcap =3D=3D=3D> lib/libposix1e =3D=3D=3D> lib/libresolv =3D=3D=3D> lib/librpcsvc =3D=3D=3D> lib/libsmdb =3D=3D=3D> lib/libsmutil =3D=3D=3D> lib/libss =3D=3D=3D> lib/libstand =3D=3D=3D> lib/libtelnet =3D=3D=3D> lib/libusb =3D=3D=3D> lib/libvgl =3D=3D=3D> lib/libwrap =3D=3D=3D> lib/libxpg4 =3D=3D=3D> lib/liby =3D=3D=3D> lib/libz =3D=3D=3D> bin =3D=3D=3D> bin/cat rm -f .depend mkdep -f .depend -a -I/usr/obj/usr/src/i386/usr/include /usr/src/bin/cat/cat.c cd /usr/src/bin/cat; make _EXTRADEPEND echo cat: /usr/obj/usr/src/i386/usr/lib/libc.a >> .depend =3D=3D=3D> bin/chio rm -f .depend mkdep -f .depend -a -I/usr/src/bin/chio/../../sys -I/usr/obj/usr/src/i386/usr/include /usr/src/bin/chio/chio.c cpp: Memory exhausted. mkdep: compile failed *** Error code 1 Stop in /usr/src/bin/chio. *** Error code 1 /usr/obj was deleted before "make buildworld". The last time I built world was Nov 21 (from 4.2-RELEASE to -STABLE). A friend of mine suggested that my mkdep binary might be broken. Any tips? 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 23 4:13: 4 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 0530737B404 for ; Tue, 23 Jan 2001 04:12:47 -0800 (PST) Received: (qmail 82369 invoked from network); 23 Jan 2001 12:14:15 -0000 Received: from herculeez.demon.co.uk (HELO athena.hq.herculeez.com) (158.152.217.198) by hercules.hiway.co.uk with SMTP; 23 Jan 2001 12:14:15 -0000 Received: (qmail 59778 invoked from network); 23 Jan 2001 12:12:02 -0000 Received: from madoka.hq.herculeez.com (HELO herculeez.com) (192.168.0.23) by athena.hq.herculeez.com with SMTP; 23 Jan 2001 12:12:02 -0000 Message-ID: <3A6D7530.6A8AA1B6@herculeez.com> Date: Tue, 23 Jan 2001 12:12:32 +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: Lukas Ertl Cc: freebsd-stable@FreeBSD.ORG Subject: Re: make buildworld fails References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Lukas Ertl wrote: > > Hi, > > "make buildworld" constantly fails on my 4.2-STABLE machine. I cvsup'ed > freshly, but the problem persists. Here is the error log: > > -I/usr/obj/usr/src/i386/usr/include /usr/src/bin/chio/chio.c > cpp: Memory exhausted. How much memory is in this box ? and what is running at the time of compilation ? -- Simon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 23 4:20:18 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 3A57137B400 for ; Tue, 23 Jan 2001 04:19:58 -0800 (PST) Received: from pcle2.cc.univie.ac.at (pcle2.cc.univie.ac.at [131.130.2.177]) by mailbox.univie.ac.at (8.9.3/8.9.3) with ESMTP id NAA134988; Tue, 23 Jan 2001 13:19:51 +0100 Date: Tue, 23 Jan 2001 13:18:57 +0100 (CET) From: Lukas Ertl X-X-Sender: To: Cc: Subject: Re: make buildworld fails In-Reply-To: <3A6D7530.6A8AA1B6@herculeez.com> 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, 23 Jan 2001, Simon Loader wrote: > Lukas Ertl wrote: > > > > Hi, > > > > "make buildworld" constantly fails on my 4.2-STABLE machine. I cvsup'ed > > freshly, but the problem persists. Here is the error log: > > > > > -I/usr/obj/usr/src/i386/usr/include /usr/src/bin/chio/chio.c > > cpp: Memory exhausted. > > > How much memory is in this box ? > and what is running at the time of compilation ? Sorry, I should have mentioned before: 96MB RAM, 128MB Swap. It looks ok while compiling, I tried in single user mode, too (where 96MB should be quite enough). If I try to issue the mkdep command on the shell in the chio dir it immediatly exits with the same error message. 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 23 4:43:30 2001 Delivered-To: freebsd-stable@freebsd.org Received: from vexpert.dbai.tuwien.ac.at (vexpert.dbai.tuwien.ac.at [128.130.111.12]) by hub.freebsd.org (Postfix) with ESMTP id E1B5A37B400 for ; Tue, 23 Jan 2001 04:43:12 -0800 (PST) Received: from taygeta.dbai.tuwien.ac.at (taygeta [128.130.111.77]) by vexpert.dbai.tuwien.ac.at (8.11.1/8.11.1) with ESMTP id f0NCh0e12760; Tue, 23 Jan 2001 13:43:01 +0100 (MET) Received: from localhost (pfeifer@localhost) by taygeta.dbai.tuwien.ac.at (8.11.1/8.11.1) with ESMTP id f0NCfxj50187; Tue, 23 Jan 2001 13:42:24 +0100 (CET) (envelope-from pfeifer@dbai.tuwien.ac.at) X-Authentication-Warning: taygeta.dbai.tuwien.ac.at: pfeifer owned process doing -bs Date: Tue, 23 Jan 2001 13:41:49 +0100 (CET) From: Gerald Pfeifer To: Cc: , Subject: Re: passwd (still) broken in NIS environments 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, 23 Jan 2001 Thierry.Herbelot@alcatel.fr wrote: > Do you have the same crypting algorithm on both ends ? > (FreeBSD recently went to MD5 as a standard - Solaris most > likely is still using DES) Yes, the Solaris NIS Server is using DES. However, as we don't have problems logging in, just changing passwords, I assume this isn't the reason? Or does passwd use MD5 nevertheless?? That might be an explanation! Hmm... Gerald -- Gerald "Jerry" pfeifer@dbai.tuwien.ac.at http://www.dbai.tuwien.ac.at/~pfeifer/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 23 5:42: 0 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 6B8C537B401 for ; Tue, 23 Jan 2001 05:41:39 -0800 (PST) Received: by arg1.demon.co.uk (Postfix, from userid 300) id 98D359B1E; Tue, 23 Jan 2001 13:41:37 +0000 (GMT) Received: from localhost (localhost [127.0.0.1]) by arg1.demon.co.uk (Postfix) with ESMTP id 8FE9A5D15 for ; Tue, 23 Jan 2001 13:41:37 +0000 (GMT) Date: Tue, 23 Jan 2001 13:41:37 +0000 (GMT) From: Andrew Gordon X-Sender: arg@server.arg.sj.co.uk To: freebsd-stable@freebsd.org Subject: softupdates/NFS/vinum(?) panics 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 been getting frequent panics: softdep_lock: locking against myself These have been occurring since an incident on 16th January, where the SCSI cable was accidentally unplugged on a running system, and vinum had trouble recovering. That incident almost certainly caused some arbitrary corruption to the filesystem; however, there is no obvious vinum involvement in the more recent panics (except that the filesystem in question is almost certainly the vinum one, as the other filesystems on this machine are almost unused). This suggests either: 1) The big crash left some corruption that fsck can't see but causes subsequent problems. 2) There is some vinum interaction that happens to have been arisen around this time (the filesystem has been growing gradually from 25% full when the system was commissioned in November to 50% now) 3) There is some softupdates problem unrelated to vinum. For most of the period, the system has been running a kernel built from -stable as at 1st January; over the weekend I upgraded to -stable (cvsup on Friday 19th), but we've had 3 crashes this morning so that doesn't appear to have helped. All the dumps are rather similar, apparently serving an NFS write; here's the latest one, and an older one: IdlePTD 3162112 initial pcb at 2838e0 panicstr: softdep_lock: locking against myself panic messages: --- panic: allocdirect_check: old 59099240 != new 59099240 || lbn 1 >= 12 (kgdb) where #0 dumpsys () at ../../kern/kern_shutdown.c:469 #1 0xc014ea8b in boot (howto=260) at ../../kern/kern_shutdown.c:309 #2 0xc014ee08 in poweroff_wait (junk=0xc02545c0, howto=-1025022464) at ../../kern/kern_shutdown.c:556 #3 0xc01e7cf1 in acquire_lock (lk=0xc0277fdc) at ../../ufs/ffs/ffs_softdep.c:263 #4 0xc01ebac4 in softdep_update_inodeblock (ip=0xc2e76600, bp=0xc7bf59b0, waitfor=0) at ../../ufs/ffs/ffs_softdep.c:3643 #5 0xc01e6fed in ffs_update (vp=0xcfbabe00, waitfor=0) at ../../ufs/ffs/ffs_inode.c:106 #6 0xc01eed50 in ffs_sync (mp=0xc28da400, waitfor=2, cred=0xc0a3b900, p=0xc0297c20) at ../../ufs/ffs/ffs_vfsops.c:987 #7 0xc017c587 in sync (p=0xc0297c20, uap=0x0) at ../../kern/vfs_syscalls.c:545 #8 0xc014e85e in boot (howto=256) at ../../kern/kern_shutdown.c:233 #9 0xc014ee08 in poweroff_wait (junk=0xc0254be0, howto=59099240) at ../../kern/kern_shutdown.c:556 #10 0xc01e8eff in allocdirect_merge (adphead=0xc2f04c44, newadp=0xc2cc7f80, oldadp=0xc2cd3200) at ../../ufs/ffs/ffs_softdep.c:1323 #11 0xc01ebc7d in merge_inode_lists (inodedep=0xc2f04c00) at ../../ufs/ffs/ffs_softdep.c:3718 #12 0xc01ebb43 in softdep_update_inodeblock (ip=0xc2eb3d00, bp=0xc7b9fee4, waitfor=1) at ../../ufs/ffs/ffs_softdep.c:3665 #13 0xc01e6fed in ffs_update (vp=0xcfbe9600, waitfor=1) at ../../ufs/ffs/ffs_inode.c:106 #14 0xc01efcde in ffs_write (ap=0xcfb3bc88) at ../../ufs/ufs/ufs_readwrite.c:544 #15 0xc01b09f4 in nfsrv_write (nfsd=0xc2eb3a00, slp=0xc2ce3200, procp=0xce781400, mrq=0xcfb3bdfc) at vnode_if.h:363 #16 0xc01c7c9a in nfssvc_nfsd (nsd=0xcfb3be5c, argp=0x807c4a0 "", p=0xce781400) at ../../nfs/nfs_syscalls.c:602 #17 0xc01c75ef in nfssvc (p=0xce781400, uap=0xcfb3bf80) at ../../nfs/nfs_syscalls.c:306 #18 0xc022cb31 in syscall2 (frame={tf_fs = 47, tf_es = 47, tf_ds = 47, tf_edi = 0, tf_esi = 0, tf_ebp = -1077936788, tf_isp = -810303532, tf_ebx = 4, tf_edx = 1, tf_ecx = -3, tf_eax = 155, tf_trapno = 12, tf_err = 2, tf_eip = 134518292, tf_cs = 31, tf_eflags = 647, tf_esp = -1077937216, tf_ss = 47}) at ../../i386/i386/trap.c:1150 #19 0xc0221995 in Xint0x80_syscall () #20 0x8048135 in ?? () (kgdb) Sample dump from January 1st kernel: IdlePTD 3158016 initial pcb at 2823c0 panicstr: softdep_lock: locking against myself panic messages: --- panic: allocdirect_check: old 36273280 != new 36273280 || lbn 4 >= 12 syncing disks... panic: softdep_lock: locking against myself (kgdb) where #0 dumpsys () at ../../kern/kern_shutdown.c:469 #1 0xc014db3f in boot (howto=260) at ../../kern/kern_shutdown.c:309 #2 0xc014debc in poweroff_wait (junk=0xc0253200, howto=0) at ../../kern/kern_shutdown.c:556 #3 0xc01e6b2d in acquire_lock (lk=0xc0276a7c) at ../../ufs/ffs/ffs_softdep.c:263 #4 0xc01eade6 in softdep_fsync_mountdev (vp=0xce77a3c0) at ../../ufs/ffs/ffs_softdep.c:3846 #5 0xc01eeef2 in ffs_fsync (ap=0xcfb39a80) at ../../ufs/ffs/ffs_vnops.c:134 #6 0xc01edbfa in ffs_sync (mp=0xc29d7000, waitfor=2, cred=0xc0a3b900, p=0xc02966c0) at vnode_if.h:537 #7 0xc017b41f in sync (p=0xc02966c0, uap=0x0) at ../../kern/vfs_syscalls.c:545 #8 0xc014d91a in boot (howto=256) at ../../kern/kern_shutdown.c:233 #9 0xc014debc in poweroff_wait (junk=0xc0253820, howto=36273280) at ../../kern/kern_shutdown.c:556 #10 0xc01e7d3b in allocdirect_merge (adphead=0xc2b30244, newadp=0xc305c100, oldadp=0xc305c580) at ../../ufs/ffs/ffs_softdep.c:1323 #11 0xc01eaab9 in merge_inode_lists (inodedep=0xc2b30200) at ../../ufs/ffs/ffs_softdep.c:3718 #12 0xc01ea97f in softdep_update_inodeblock (ip=0xc305fb00, bp=0xc7b80088, waitfor=1) at ../../ufs/ffs/ffs_softdep.c:3665 #13 0xc01e5e29 in ffs_update (vp=0xcfdaecc0, waitfor=1) at ../../ufs/ffs/ffs_inode.c:106 #14 0xc01eeb1a in ffs_write (ap=0xcfb39c88) at ../../ufs/ufs/ufs_readwrite.c:542 #15 0xc01af86c in nfsrv_write (nfsd=0xc3020e00, slp=0xc2b1e900, procp=0xce77f400, mrq=0xcfb39dfc) at vnode_if.h:363 #16 0xc01c6b12 in nfssvc_nfsd (nsd=0xcfb39e5c, argp=0x807c4a0 "", p=0xce77f400) at ../../nfs/nfs_syscalls.c:602 #17 0xc01c6467 in nfssvc (p=0xce77f400, uap=0xcfb39f80) at ../../nfs/nfs_syscalls.c:306 #18 0xc022b909 in syscall2 (frame={tf_fs = 47, tf_es = 47, tf_ds = 47, tf_edi = 0, tf_esi = 0, tf_ebp = -1077936788, tf_isp = -810311724, tf_ebx = 4, tf_edx = 1, tf_ecx = -3, tf_eax = 155, tf_trapno = 12, tf_err = 2, tf_eip = 134518292, tf_cs = 31, tf_eflags = 647, tf_esp = -1077937216, tf_ss = 47}) at ../../i386/i386/trap.c:1150 #19 0xc0220775 in Xint0x80_syscall () #20 0x8048135 in ?? () (kgdb) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 23 6:12:39 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 0099637B6A3 for ; Tue, 23 Jan 2001 06:12:22 -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 JAA11614 for ; Tue, 23 Jan 2001 09:12:20 -0500 (EST) Received: (from sto@localhost) by feta.isds.duke.edu (8.11.1/8.11.1) id f0NECKS59816 for stable@FreeBSD.ORG; Tue, 23 Jan 2001 09:12:20 -0500 (EST) (envelope-from sto) Date: Tue, 23 Jan 2001 09:12:20 -0500 From: "Sean O'Connell" To: stable@FreeBSD.ORG Subject: Re: Dell PERC 3 support? Message-ID: <20010123091220.A59802@stat.Duke.EDU> Reply-To: "Sean O'Connell" Mail-Followup-To: Sean O'Connell , stable@FreeBSD.ORG References: <20010123012109.O26076@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010123012109.O26076@fw.wintelcom.net>; from bright@wintelcom.net on Tue, Jan 23, 2001 at 01:21:09AM -0800 X-Organization: Institute of Statistics and Decision Sciences Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alfred Perlstein stated: : A friend just asked me if we support the PERC 3 cards shipped in : Dell servers. If not, anyone have a recommendation for a controller : in the same price performance category that is supported? Alfred- The PERC 3 cards use the aac driver which was only very recently MFC'd (it should work with a recent snapshot). The card should work and you can download from Dell a Linux command line tool to do some work with the controller (you do need to build a custom kernel to use this that does not have aac statically defined and load the kld out of /boot/loader.conf (aac_load="YES") to get the linux ioctl support (it will not compile statically .. well, I could not get it to compile statically :). HTH, 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 23 6:34: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 DF20537B6A4 for ; Tue, 23 Jan 2001 06:34:32 -0800 (PST) Received: from [203.164.12.28] by www.quake.com.au (NTMail 4.30.0012/AH9370.63.d1acf55c) with ESMTP id givsaaaa for ; Wed, 24 Jan 2001 01:43:10 +1100 Message-ID: <3A6D967F.B464AB45@quake.com.au> Date: Wed, 24 Jan 2001 01:34:39 +1100 From: Kal Torak X-Mailer: Mozilla 4.73 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Gerald Pfeifer Cc: Thierry.Herbelot@alcatel.fr, freebsd-stable@freebsd.org, admin@dbai.tuwien.ac.at Subject: Re: passwd (still) broken in NIS environments References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Gerald Pfeifer wrote: > > On Tue, 23 Jan 2001 Thierry.Herbelot@alcatel.fr wrote: > > Do you have the same crypting algorithm on both ends ? > > (FreeBSD recently went to MD5 as a standard - Solaris most > > likely is still using DES) > > Yes, the Solaris NIS Server is using DES. However, as we don't have > problems logging in, just changing passwords, I assume this isn't the > reason? > > Or does passwd use MD5 nevertheless?? That might be an explanation! passwd uses whatever format you specified in /etc/login.conf for that users login class... Since the default crypt has been changing around with export restrictions being lifted etc. You should just put that you want DES in there... put in the line ":passwd_format=des:\" under "default:\" Good Luck! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 23 6:38:44 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 26D1F37B6A4 for ; Tue, 23 Jan 2001 06:38:26 -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 f0NEZSm01796; Tue, 23 Jan 2001 08:35:28 -0600 (CST) (envelope-from swb@grasslake.net) Message-ID: <001601c0854a$480efdb0$b8209fc0@marlowe> From: "Shawn Barnhart" To: "Sean O'Connell" , References: <20010123012109.O26076@fw.wintelcom.net> <20010123091220.A59802@stat.Duke.EDU> Subject: Re: Dell PERC 3 support? Date: Tue, 23 Jan 2001 08:39:24 -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 ----- Original Message ----- From: "Sean O'Connell" > The PERC 3 cards use the aac driver which was only very recently > MFC'd (it should work with a recent snapshot). The card should > work and you can download from Dell a Linux command line tool to > do some work with the controller (you do need to build a custom > kernel to use this that does not have aac statically defined and > load the kld out of /boot/loader.conf (aac_load="YES") to get the > linux ioctl support (it will not compile statically .. well, I > could not get it to compile statically :). Have you gotten an aac card to work under STABLE? I tried with the following procedure within a week of the MFC of the aac driver. Card make was a HP Netraid 4M connected to a HP rackstorage/12 (6 disks, raid 5): 1) build STABLE kernel on updated STABLE machine 2) grab 5.0 snapshot (4.2 snap had no aac support) install disk, do install with 4.2 CD 3) on boot, copy 4.2-STABLE kernel with aac support to new system 4) reboot with 4.2 stable kernel, cvsup, make buildworld, buildkernel, instal, etc. 5) reboot 6) filesystem refuses to mount, "operation timed out..." During the cvsup operation the system would "pause" for 15-30 seconds for no apparent reason. A console switch to a systat -vmstat screen shows the aac disk at 100%. They'd stay at 100% and then the process would continue. I got the same kind of results during buildworld and installworld. My guess is that either my install process was too smart for my own good, or the driver didn't like my card. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 23 6:44:23 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 DEAE437B6A8; Tue, 23 Jan 2001 06:43:41 -0800 (PST) Received: (from nobody@localhost) by moon.harmonic.co.il (8.9.3/8.9.3) id QAA20151; Tue, 23 Jan 2001 16:41:30 +0200 To: Gerald Pfeifer Subject: Re: libgcc_pic is gone (affects Wine port) Message-ID: <980260890.3a6d981aab6ae@webmail.harmonic.co.il> Date: Tue, 23 Jan 2001 16:41:30 +0200 (IST) From: Roman Shterenzon Cc: freebsd-stable@FreeBSD.ORG, freebsd-ports@FreeBSD.ORG References: In-Reply-To: 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 Quoting Gerald Pfeifer : > Due to a serious bug in the port of GCC used in the base system > (see ) I and > probably others had to explicitly link against libgcc_pic. > > This bug has been fixed (around 4.2-RELEASE), but also libgcc_pic is > gone now, though I'm not sure whether that is directly related. > > So, what is a "portable" way of compiling sources both on 4.1-RELEASE > and 5.0-CURRENT? On the former I need libgcc_pic, on the latter there > is no libgcc_pic at all. > > Or, as this mainly affects the Wine port, should I just ignore older > versions of FreeBSD? Does 4.2-RELEASE already have the fix to PR 21983? > > Gerald AFAIK, there's no libgcc_* in RELENG_4 anymore as well. Ask David . > > > > > 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 Tue Jan 23 7: 5:19 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 E6B5B37B404 for ; Tue, 23 Jan 2001 07:05:01 -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 KAA13312; Tue, 23 Jan 2001 10:05:00 -0500 (EST) Received: (from sto@localhost) by feta.isds.duke.edu (8.11.1/8.11.1) id f0NF50C59957; Tue, 23 Jan 2001 10:05:00 -0500 (EST) (envelope-from sto) Date: Tue, 23 Jan 2001 10:05:00 -0500 From: "Sean O'Connell" To: Shawn Barnhart , FreeBSD stable Subject: Re: Dell PERC 3 support? Message-ID: <20010123100500.G59802@stat.Duke.EDU> Reply-To: "Sean O'Connell" Mail-Followup-To: Sean O'Connell , Shawn Barnhart , FreeBSD stable References: <20010123012109.O26076@fw.wintelcom.net> <20010123091220.A59802@stat.Duke.EDU> <001601c0854a$480efdb0$b8209fc0@marlowe> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <001601c0854a$480efdb0$b8209fc0@marlowe>; from swb@grasslake.net on Tue, Jan 23, 2001 at 08:39:24AM -0600 X-Organization: Institute of Statistics and Decision Sciences Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Shawn Barnhart stated: : Have you gotten an aac card to work under STABLE? I tried with the : following procedure within a week of the MFC of the aac driver. Card make : was a HP Netraid 4M connected to a HP rackstorage/12 (6 disks, raid 5): : : 1) build STABLE kernel on updated STABLE machine : 2) grab 5.0 snapshot (4.2 snap had no aac support) install disk, do install : with 4.2 CD : 3) on boot, copy 4.2-STABLE kernel with aac support to new system : 4) reboot with 4.2 stable kernel, cvsup, make buildworld, buildkernel, : instal, etc. : 5) reboot : 6) filesystem refuses to mount, "operation timed out..." : : During the cvsup operation the system would "pause" for 15-30 seconds for no : apparent reason. A console switch to a systat -vmstat screen shows the aac : disk at 100%. They'd stay at 100% and then the process would continue. I : got the same kind of results during buildworld and installworld. : : My guess is that either my install process was too smart for my own good, or : the driver didn't like my card. Shawn- I have been using a -current. However, -stable should support the controllers. Let me try the latest stable SNAP. Hmmm... GENERIC from the 20010122 SNAPSHOT found the controller and the containers, but sysinstall hasn't been trained to install on the containers :( 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 23 7:30:11 2001 Delivered-To: freebsd-stable@freebsd.org Received: from emma1.emma.line.org (p3EE3C74A.dip.t-dialin.net [62.227.199.74]) by hub.freebsd.org (Postfix) with ESMTP id 0C3A737B699 for ; Tue, 23 Jan 2001 07:29:48 -0800 (PST) Received: by emma1.emma.line.org (Postfix, from userid 500) id 4F336A2002; Tue, 23 Jan 2001 16:29:30 +0100 (CET) Date: Tue, 23 Jan 2001 16:29:30 +0100 From: Matthias Andree To: Guy Harris , Neil Brown , Linux NFS mailing list , reiserfs-list@namesys.com, FreeBSD Stable Subject: Re: [NFS] Incompatible: FreeBSD 4.2 client, Linux 2.2.18 nfsv3 server, read-only export (was: Incompatible: FreeBSD 4.2 client, Linux 2.2.18 nfsv3 server, ReiserFS) Message-ID: <20010123162930.B5443@emma1.emma.line.org> Reply-To: FreeBSD Stable , Linux NFS mailing list Mail-Followup-To: Guy Harris , Neil Brown , Linux NFS mailing list , reiserfs-list@namesys.com, FreeBSD Stable References: <20010123015612.H345@quadrajet.flashcom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010123015612.H345@quadrajet.flashcom.com>; from gharris@flashcom.net on Tue, Jan 23, 2001 at 01:56:12 -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Note: when replying, please remove the (was: ) part of the Subject and the reiserfs-list from the recipients. On Tue, 23 Jan 2001, Guy Harris wrote: > Perhaps the Linux server should, in "nfsd_access()", treat "nfserr_rofs" > the same way it treats "nfserr_perm" and "nfserr_acces", and just say > the access type is denied but the access query succeeded, doing the same > thing that Solaris and a future release of the NetApp software will do. > > (It looks as if the FreeBSD NFS server already does that - it treats all > errors from "nfsrv_access()" as meaning "access denied", not "access > call failed", so it treats EROFS in that fashion. The same probably > applies to other BSDs.) > > As for why the V2 client doesn't appear to have this problem, the V2 > client doesn't make an ACCESS call, because NFS V2 doesn't have an > ACCESS call to make. Ah, so it's a protocol difference which keeps Linux server <-> FreeBSD client compatibility here. > If it *was* mounted read-only, was the ext2 file system also mounted > read-only? If not, that might explain it. I looked again, closely, and found in /etc/exports: /space 192.168.0.0/255.255.255.0 /home 192.168.0.0/255.255.255.0(rw) I looked into exports(5) and found that exports assumes ro unless overriden with rw. Not reporting this and attributing the problem to ReiserFS instead of the RO mount (which looks strange to me as a response to a READ request) was my fault, and I apologize to the ReiserFS people for this bogus allegation. ReiserFS is now out of the play. > As for why it's a problem with the FreeBSD client but not the Solaris > client, I'm not sure - a quick look at the 4.2 client code doesn't seem > to show any way in which the EROFS is "sticky" to the extent that it > affects all client accesses, as it doesn't cache the result of an ACCESS > call that failed. It may just be that the Solaris client just ignores > NFS3ERR_ROFS from an ACCESS call and does an access check based on the > permission bits, rather than returning EROFS, whilst the FreeBSD client > returns EROFS; if ReiserFS is returning EROFS bogusly, that might cause > the symptoms in question. Okay. So, as a conclusion, my original bug report boils down to: "You cannot mount read-only file systems with NFS v3 from a Linux 2.2.18 server to a FreeBSD 4.2-STABLE client. Use NFS v2 instead." The question remains: Linux kernel problem or FreeBSD client problem? -- Matthias Andree To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 23 8:27:21 2001 Delivered-To: freebsd-stable@freebsd.org Received: from bg.sics.se (bg.sics.se [193.10.66.124]) by hub.freebsd.org (Postfix) with ESMTP id 8728337B6A4 for ; Tue, 23 Jan 2001 08:27:03 -0800 (PST) Received: (from bg@localhost) by bg.sics.se (8.11.1/8.11.1) id f0NGRP315049; Tue, 23 Jan 2001 17:27:25 +0100 (CET) (envelope-from bg) To: FreeBSD Stable Cc: Linux NFS mailing list , Guy Harris , Neil Brown , matthias.andree@stud.uni-dortmund.de Subject: Re: [NFS] Incompatible: FreeBSD 4.2 client, Linux 2.2.18 nfsv3 server, read-only export References: <20010123015612.H345@quadrajet.flashcom.com> <20010123162930.B5443@emma1.emma.line.org> From: Bjoern Groenvall Date: 23 Jan 2001 17:26:54 +0100 In-Reply-To: Matthias Andree's message of "Tue, 23 Jan 2001 16:29:30 +0100" Message-ID: Lines: 43 X-Mailer: Gnus v5.7/Emacs 20.6 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "Matthias" == Matthias Andree writes: Matthias> The question remains: Linux kernel problem or FreeBSD client Matthias> problem? Or perhaps we should blame RFC1813? However, 1813 says that ACCESS should return one of the following errors NFS3ERR_IO NFS3ERR_STALE NFS3ERR_BADHANDLE NFS3ERR_SERVERFAULT ,and "The client encodes the set of permissions that are to be checked in a bit mask. The server checks the permissions encoded in the bit mask. A status of NFS3_OK is returned along with a bit mask encoded with the permissions that the client is allowed.". It also says "NFS3ERR_ROFS Read-only file system. A modifying operation was attempted on a read-only file system." The RFC does not explicitly mention how to handle read-only file systems. I think it would be really nice if the server returns those permissions that the client is allowed with the write bits unset. That is also the solution that Guy came up with. Guy> Perhaps the Linux server should, in "nfsd_access()", treat "nfserr_rofs" Guy> the same way it treats "nfserr_perm" and "nfserr_acces", and just say Guy> the access type is denied but the access query succeeded, doing the same Guy> thing that Solaris and a future release of the NetApp software will do. Cheers, Björn -- _ _ ,_______________. Bjorn Gronvall (Björn Grönvall) /_______________/| Swedish Institute of Computer Science | || PO Box 1263, S-164 29 Kista, Sweden | Schroedingers || Email: bg@sics.se, Phone +46 -8 633 15 25 | Cat |/ Cellular +46 -70 768 06 35, Fax +46 -8 751 72 30 `---------------' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 23 8:59:57 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id DBCB037B404 for ; Tue, 23 Jan 2001 08:59:37 -0800 (PST) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.1/8.11.1) with ESMTP id f0NHF1S00658; Tue, 23 Jan 2001 09:15:01 -0800 (PST) (envelope-from msmith@mass.dis.org) Message-Id: <200101231715.f0NHF1S00658@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Alfred Perlstein Cc: stable@freebsd.org Subject: Re: Dell PERC 3 support? In-reply-to: Your message of "Tue, 23 Jan 2001 01:21:09 PST." <20010123012109.O26076@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 23 Jan 2001 09:15:01 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > A friend just asked me if we support the PERC 3 cards shipped in > Dell servers. If not, anyone have a recommendation for a controller > in the same price performance category that is supported? Yes; these are either AMI (3DC) or Adaptec (3Si/Di) controllers, supported by the amr and aac drivers respectively. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 23 9:22:57 2001 Delivered-To: freebsd-stable@freebsd.org Received: from zaphon.llamas.net (zaphon.llamas.net [207.203.36.210]) by hub.freebsd.org (Postfix) with SMTP id 0A2B937B402 for ; Tue, 23 Jan 2001 09:22:39 -0800 (PST) Received: (qmail 94167 invoked by uid 1001); 23 Jan 2001 17:22:37 -0000 Date: Tue, 23 Jan 2001 09:22:37 -0800 From: Greg Rumple To: Mike Smith Cc: Alfred Perlstein , stable@freebsd.org Subject: Re: Dell PERC 3 support? Message-ID: <20010123092236.C84940@zaphon.llamas.net> References: <20010123012109.O26076@fw.wintelcom.net> <200101231715.f0NHF1S00658@mass.dis.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200101231715.f0NHF1S00658@mass.dis.org>; from msmith@freebsd.org on Tue, Jan 23, 2001 at 09:15:01AM -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG So if I was buying a Dell 2450, I can get the Perc 3/Si upgrade for it and use 4.2-STABLE? Or would I have to goto current? I had steared away from this due to messages I had seen in December regarding these controllers. And was instead looking at just getting an Adaptec 3200S instead. But if I can buy it all from Dell, life would be a lot easier. Thanks, Greg * Mike Smith (msmith@freebsd.org) [010123 17:00]: > > A friend just asked me if we support the PERC 3 cards shipped in > > Dell servers. If not, anyone have a recommendation for a controller > > in the same price performance category that is supported? > > Yes; these are either AMI (3DC) or Adaptec (3Si/Di) controllers, > supported by the amr and aac drivers respectively. > > -- > ... 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 -- Greg Rumple grumple@zaphon.llamas.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 23 10: 3:19 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id AF13B37B699 for ; Tue, 23 Jan 2001 10:02:59 -0800 (PST) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.1/8.11.1) with ESMTP id f0NIIGS00820; Tue, 23 Jan 2001 10:18:17 -0800 (PST) (envelope-from msmith@mass.dis.org) Message-Id: <200101231818.f0NIIGS00820@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Danny Braniss Cc: Alfred Perlstein , stable@freebsd.org Subject: Re: Dell PERC 3 support? In-reply-to: Your message of "Tue, 23 Jan 2001 11:58:49 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 23 Jan 2001 10:18:16 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In message <20010123012109.O26076@fw.wintelcom.net>you write: > }A friend just asked me if we support the PERC 3 cards shipped in > }Dell servers. If not, anyone have a recommendation for a controller > }in the same price performance category that is supported? > > if it's a Dell p-somthing 2450, then there is support, > http://people.freebsd.org/~msmith/RAID > > i couldn't boot from the raid, and only tested raid0 (only had 2 disks) > and the speeds were very nice. > > btw, if you figure out how to make it bootable, i would like to know. All of the RAID adapters we support are bootable. The #1 cause of booting problems is a geometry mismatch. The integrated RAID controller in the 2450 is supported by 'aac', which has three geometry options: '2GB' mode: */255/63 '1GB' mode: */128/32 standard: */64/32 The driver picks this setting up from the controller; if there is already data on the disks, sysinstall may be confused into using a different geometry. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 23 10: 9:54 2001 Delivered-To: freebsd-stable@freebsd.org Received: from dilbert.fcg.co.uk (dilbert.firstcallgroup.co.uk [194.203.69.166]) by hub.freebsd.org (Postfix) with ESMTP id 8036F37B69F for ; Tue, 23 Jan 2001 10:09:37 -0800 (PST) Received: from pfrench by dilbert.fcg.co.uk with local (Exim 3.20 #1) id 14L7so-000Kbd-00 for stable@freebsd.org; Tue, 23 Jan 2001 18:09:30 +0000 To: stable@freebsd.org Subject: anybody seen this one ? Message-Id: From: Pete French Date: Tue, 23 Jan 2001 18:09:30 +0000 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG o.k., this is *very* odd. I am using the 4.2 rrelease Cd to install onto a machine. This machine installs 3.4 fine and is currently running it quite happily. Under 3.3 I boot from two floppies, get the screen which allows me to configure the kernel, then it boots into the nice blue screen from sysinstall. All well and good. Under 4.2 I boot from the two floppies and the screen to allow kernel configs never appears - the system runs saright into the boot, starts up sysinstall... and at this point appears to freeze. Or at least I can get no response from the keyboard ! Anybody seen anything liek this, or have any suggestions as to how to get round it ? I've taken as much of the hardware out as I feasibly can, and an identical motherboard appears to work fine.. Hmmmm... system is a K2/450, 64MB of RAM, Adapatec 2940UW SCSII card, G200 AGP card, -pete. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 23 10:14:15 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 C426437B6A2; Tue, 23 Jan 2001 10:13:54 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f0NIDr003211; Tue, 23 Jan 2001 10:13:53 -0800 (PST) Date: Tue, 23 Jan 2001 10:13:53 -0800 From: Alfred Perlstein To: Mike Smith Cc: Danny Braniss , stable@freebsd.org Subject: Re: Dell PERC 3 support? Message-ID: <20010123101353.P26076@fw.wintelcom.net> References: <200101231818.f0NIIGS00820@mass.dis.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200101231818.f0NIIGS00820@mass.dis.org>; from msmith@freebsd.org on Tue, Jan 23, 2001 at 10:18:16AM -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Mike Smith [010123 10:02] wrote: > > In message <20010123012109.O26076@fw.wintelcom.net>you write: > > }A friend just asked me if we support the PERC 3 cards shipped in > > }Dell servers. If not, anyone have a recommendation for a controller > > }in the same price performance category that is supported? > > > > if it's a Dell p-somthing 2450, then there is support, > > http://people.freebsd.org/~msmith/RAID > > > > i couldn't boot from the raid, and only tested raid0 (only had 2 disks) > > and the speeds were very nice. > > > > btw, if you figure out how to make it bootable, i would like to know. > > All of the RAID adapters we support are bootable. The #1 cause of > booting problems is a geometry mismatch. The integrated RAID controller > in the 2450 is supported by 'aac', which has three geometry options: > > '2GB' mode: */255/63 > '1GB' mode: */128/32 > standard: */64/32 > > The driver picks this setting up from the controller; if there is already > data on the disks, sysinstall may be confused into using a different > geometry. Someone complained that sysinstall wasn't aware of the cards, and therefore couldn't install on it. Sort of like the mess I had with amr(4), do you remeber MFC'ing sysinstall support for installing onto the PERC3? thanks, -- -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 Tue Jan 23 10:15:37 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id 6F38B37B6A3 for ; Tue, 23 Jan 2001 10:15:19 -0800 (PST) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.1/8.11.1) with ESMTP id f0NIUXS00941; Tue, 23 Jan 2001 10:30:37 -0800 (PST) (envelope-from msmith@mass.dis.org) Message-Id: <200101231830.f0NIUXS00941@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Shawn Barnhart" Cc: "Sean O'Connell" , stable@FreeBSD.ORG Subject: Re: Dell PERC 3 support? In-reply-to: Your message of "Tue, 23 Jan 2001 08:39:24 CST." <001601c0854a$480efdb0$b8209fc0@marlowe> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 23 Jan 2001 10:30:33 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The MFC of the driver brought back an spl bug that was probably hidden in -current by the way that interrupts currently work there. Paul Saab at Yahoo pointed this out, and I fixed it probably just after you tried this. The symptoms would probably have been similar to what you're describing here. > ----- Original Message ----- > From: "Sean O'Connell" > > > The PERC 3 cards use the aac driver which was only very recently > > MFC'd (it should work with a recent snapshot). The card should > > work and you can download from Dell a Linux command line tool to > > do some work with the controller (you do need to build a custom > > kernel to use this that does not have aac statically defined and > > load the kld out of /boot/loader.conf (aac_load="YES") to get the > > linux ioctl support (it will not compile statically .. well, I > > could not get it to compile statically :). > > Have you gotten an aac card to work under STABLE? I tried with the > following procedure within a week of the MFC of the aac driver. Card make > was a HP Netraid 4M connected to a HP rackstorage/12 (6 disks, raid 5): > > 1) build STABLE kernel on updated STABLE machine > 2) grab 5.0 snapshot (4.2 snap had no aac support) install disk, do install > with 4.2 CD > 3) on boot, copy 4.2-STABLE kernel with aac support to new system > 4) reboot with 4.2 stable kernel, cvsup, make buildworld, buildkernel, > instal, etc. > 5) reboot > 6) filesystem refuses to mount, "operation timed out..." > > During the cvsup operation the system would "pause" for 15-30 seconds for no > apparent reason. A console switch to a systat -vmstat screen shows the aac > disk at 100%. They'd stay at 100% and then the process would continue. I > got the same kind of results during buildworld and installworld. > > My guess is that either my install process was too smart for my own good, or > the driver didn't like my card. > > > > > > 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 Tue Jan 23 10:27:18 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id 9EC7237B401 for ; Tue, 23 Jan 2001 10:26:58 -0800 (PST) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.1/8.11.1) with ESMTP id f0NIgKS01023; Tue, 23 Jan 2001 10:42:20 -0800 (PST) (envelope-from msmith@mass.dis.org) Message-Id: <200101231842.f0NIgKS01023@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Greg Rumple Cc: stable@freebsd.org Subject: Re: Dell PERC 3 support? In-reply-to: Your message of "Tue, 23 Jan 2001 09:22:37 PST." <20010123092236.C84940@zaphon.llamas.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 23 Jan 2001 10:42:20 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > So if I was buying a Dell 2450, I can get the Perc 3/Si upgrade for it > and use 4.2-STABLE? Or would I have to goto current? I had steared > away from this due to messages I had seen in December regarding these > controllers. And was instead looking at just getting an Adaptec 3200S > instead. But if I can buy it all from Dell, life would be a lot easier. You should be able to run -stable on the 3/Si, yes, and I believe that we've nailed down the stability issues now, so you should be fine. Obviously, if you have any problems, I'd like to know about them, but from the reports I have to hand so far, things are finally looking pretty good. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 23 10:27:40 2001 Delivered-To: freebsd-stable@freebsd.org Received: from chuggalug.clues.com (chuggalug.clues.com [194.159.1.85]) by hub.freebsd.org (Postfix) with ESMTP id 5519137B699; Tue, 23 Jan 2001 10:27:19 -0800 (PST) Received: (from geoffb@localhost) by chuggalug.clues.com (8.9.3/8.9.3) id SAA75860; Tue, 23 Jan 2001 18:38:23 GMT (envelope-from geoffb) Date: Tue, 23 Jan 2001 18:38:23 +0000 From: Geoff Buckingham To: Greg Rumple Cc: Mike Smith , Alfred Perlstein , stable@FreeBSD.ORG Subject: Re: Dell PERC 3 support? Message-ID: <20010123183823.A75088@chuggalug.clues.com> References: <20010123012109.O26076@fw.wintelcom.net> <200101231715.f0NHF1S00658@mass.dis.org> <20010123092236.C84940@zaphon.llamas.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <20010123092236.C84940@zaphon.llamas.net>; from Greg Rumple on Tue, Jan 23, 2001 at 09:22:37AM -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I was one of the people with trouble before christmas. Following mike's stirling work they seem to function well in recent stable snapshots. At the time I last installed the GENRIC kernel and sysinstall didn't have the aac configured so I had to use a set of current install floppies having changed options/Release Name to correspond to the stable snapshot I required. There are couple of things to know about Dell PERC controllers. PERC stands for Power Edge Raid Controller. Hence can be anything Dell decice to rebadge. Currently this seems to be restricted to the aac (adaptec) and amr (AMI). The PE2450 has an onboard aac that is enabled with a "raid key' and and a DIMM. This is the PERC3/si. THis seems to be a reasonable controller, the drivers reporting seems to suggest actual PCI controllers of this family may have a battery to protect the uncommited data data in the (large) cache, while this does not. (Write cacheing can be disabled.) While there is no native freebsd managment tool for this card, work is well under way on getting the linux one working and most tasks can be initiated in the contollers bios at boot time and left to happen in the background while FreeBSD runs on the 'degraded' . This means a reboot would be required for most recovories, thogh much of it may be able to occur with the machine up and running. I am not sure of the state of managment tools for the other RAIDS, if you have the time and budget to pick and choose this is an importent criterea. -- GeoffB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 23 10:32:14 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 5A42837B401; Tue, 23 Jan 2001 10:31:56 -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 NAA13186; Tue, 23 Jan 2001 13:31:55 -0500 (EST) Received: (from sto@localhost) by feta.isds.duke.edu (8.11.1/8.11.1) id f0NIVtV60300; Tue, 23 Jan 2001 13:31:55 -0500 (EST) (envelope-from sto) Date: Tue, 23 Jan 2001 13:31:55 -0500 From: "Sean O'Connell" To: Mike Smith , FreeBSD stable Subject: Re: Dell PERC 3 support? Message-ID: <20010123133155.M59802@stat.Duke.EDU> Reply-To: "Sean O'Connell" Mail-Followup-To: Sean O'Connell , Mike Smith , FreeBSD stable References: <20010123092236.C84940@zaphon.llamas.net> <200101231842.f0NIgKS01023@mass.dis.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200101231842.f0NIgKS01023@mass.dis.org>; from msmith@FreeBSD.ORG on Tue, Jan 23, 2001 at 10:42:20AM -0800 X-Organization: Institute of Statistics and Decision Sciences Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith stated: : > So if I was buying a Dell 2450, I can get the Perc 3/Si upgrade for it : > and use 4.2-STABLE? Or would I have to goto current? I had steared : > away from this due to messages I had seen in December regarding these : > controllers. And was instead looking at just getting an Adaptec 3200S : > instead. But if I can buy it all from Dell, life would be a lot easier. : : You should be able to run -stable on the 3/Si, yes, and I believe that : we've nailed down the stability issues now, so you should be fine. : : Obviously, if you have any problems, I'd like to know about them, but : from the reports I have to hand so far, things are finally looking pretty : good. Mike- Any idea why the sysinstall from today's -stable snapshot would not recognize that the aac and all of its containers (all seen in boot probe) were not installable? It claimed I had no disks available (the 3 containers all were labeled with FreeBSD -current .. if that makes a difference) 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 23 10:36:16 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id 2FA7437B404 for ; Tue, 23 Jan 2001 10:35:55 -0800 (PST) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.1/8.11.1) with ESMTP id f0NIpJS01090; Tue, 23 Jan 2001 10:51:19 -0800 (PST) (envelope-from msmith@mass.dis.org) Message-Id: <200101231851.f0NIpJS01090@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Alfred Perlstein Cc: stable@freebsd.org Subject: Re: Dell PERC 3 support? In-reply-to: Your message of "Tue, 23 Jan 2001 10:13:53 PST." <20010123101353.P26076@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 23 Jan 2001 10:51:19 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Someone complained that sysinstall wasn't aware of the cards, and > therefore couldn't install on it. Sort of like the mess I had > with amr(4), do you remeber MFC'ing sysinstall support for installing > onto the PERC3? I didn't do the MFC, Scott Long did. It looks like sysinstall in -stable supports it just fine though. There was an issue with MAKEDEV not knowing how to make the device nodes, which was resolved recently as well. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 23 10:39: 4 2001 Delivered-To: freebsd-stable@freebsd.org Received: from nevermind.kiev.ua (unknown [212.109.53.33]) by hub.freebsd.org (Postfix) with ESMTP id A25A437B402 for ; Tue, 23 Jan 2001 10:38:44 -0800 (PST) Received: (from never@localhost) by nevermind.kiev.ua (8.11.1/8.11.1) id f0NIcY311332; Tue, 23 Jan 2001 20:38:34 +0200 (EET) (envelope-from never) Date: Tue, 23 Jan 2001 20:38:06 +0200 From: Nevermind To: Pete French Cc: stable@FreeBSD.ORG Subject: Re: anybody seen this one ? Message-ID: <20010123203806.C3996@nevermind.kiev.ua> 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 pfrench@firstcallgroup.co.uk on Tue, Jan 23, 2001 at 06:09:30PM +0000 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, Pete French! On Tue, Jan 23, 2001 at 06:09:30PM +0000, you wrote: > Under 4.2 I boot from the two floppies and the screen to allow kernel > configs never appears - the system runs saright into the boot, starts up > sysinstall... and at this point appears to freeze. Or at least I can get no > response from the keyboard ! > > Anybody seen anything liek this, or have any suggestions as to how to get > round it ? I've taken as much of the hardware out as I feasibly can, and > an identical motherboard appears to work fine.. Hmmmm... I'm not sure about this, but let me suggest a solution... I had the same broblem until I've loaded "System Defaults" in BIOS... The did not noticed any of useful changes, but it helped... Sorry if my letter is too lame... -- Alexandr P. Kovalenko http://nevermind.kiev.ua/ NEVE-RIPE To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 23 10:39:56 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id 131D437B404 for ; Tue, 23 Jan 2001 10:39:38 -0800 (PST) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.1/8.11.1) with ESMTP id f0NIt3S01116; Tue, 23 Jan 2001 10:55:03 -0800 (PST) (envelope-from msmith@mass.dis.org) Message-Id: <200101231855.f0NIt3S01116@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Sean O'Connell" Cc: FreeBSD stable Subject: Re: Dell PERC 3 support? In-reply-to: Your message of "Tue, 23 Jan 2001 13:31:55 EST." <20010123133155.M59802@stat.Duke.EDU> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 23 Jan 2001 10:55:03 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > : Obviously, if you have any problems, I'd like to know about them, but > : from the reports I have to hand so far, things are finally looking pretty > : good. > > Any idea why the sysinstall from today's -stable snapshot would not > recognize that the aac and all of its containers (all seen in > boot probe) were not installable? It claimed I had no disks available > (the 3 containers all were labeled with FreeBSD -current .. if that > makes a difference) Bah. Libdisk didn't get updated. Fixing it now... Adding new disk types is just too damn painful. 8( -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 23 10:50:59 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 87E8F37B698; Tue, 23 Jan 2001 10:50:39 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f0NIod704756; Tue, 23 Jan 2001 10:50:39 -0800 (PST) Date: Tue, 23 Jan 2001 10:50:39 -0800 From: Alfred Perlstein To: Mike Smith Cc: "Sean O'Connell" , FreeBSD stable Subject: Re: Dell PERC 3 support? Message-ID: <20010123105038.S26076@fw.wintelcom.net> References: <20010123133155.M59802@stat.Duke.EDU> <200101231855.f0NIt3S01116@mass.dis.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200101231855.f0NIt3S01116@mass.dis.org>; from msmith@FreeBSD.ORG on Tue, Jan 23, 2001 at 10:55:03AM -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Mike Smith [010123 10:40] wrote: > > : Obviously, if you have any problems, I'd like to know about them, but > > : from the reports I have to hand so far, things are finally looking pretty > > : good. > > > > Any idea why the sysinstall from today's -stable snapshot would not > > recognize that the aac and all of its containers (all seen in > > boot probe) were not installable? It claimed I had no disks available > > (the 3 containers all were labeled with FreeBSD -current .. if that > > makes a difference) > > Bah. Libdisk didn't get updated. Fixing it now... > > Adding new disk types is just too damn painful. 8( How about a mini-howto? Both you and I messed it up several times. It would help to reduce the chance if there was a step-by-step out there to remind the disk driver gurus. :) -- -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 Tue Jan 23 11: 7:39 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id DE6E837B404; Tue, 23 Jan 2001 11:07:15 -0800 (PST) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.1/8.11.1) with ESMTP id f0NJMgS01273; Tue, 23 Jan 2001 11:22:42 -0800 (PST) (envelope-from msmith@mass.dis.org) Message-Id: <200101231922.f0NJMgS01273@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Alfred Perlstein Cc: FreeBSD stable , doc@FreeBSD.ORG Subject: Re: Dell PERC 3 support? In-reply-to: Your message of "Tue, 23 Jan 2001 10:50:39 PST." <20010123105038.S26076@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 23 Jan 2001 11:22:42 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Adding new disk types is just too damn painful. 8( > > How about a mini-howto? Both you and I messed it up several times. > It would help to reduce the chance if there was a step-by-step > out there to remind the disk driver gurus. :) Please arrange to have this put wherever it'll do the most good... Adding Your new Disk Driver, Mini-Howto r1.0 ------------------------------------------------------------------ (c) 2001 Michael Smith Adding a disk driver to FreeBSD is relatively easy, but there are a number of non-obvious steps that must be followed for it to all work right. We assume here that you have already successfully developed and tested your driver, and that you're ready to commit it to the tree. If you're not committing it, you can still generate diffs for the various files to make the actual commit process move more quickly. 1) Commit the driver. This part is obvious. 2) Commit the module Makefile. All drivers should build as modules. You probably built as a module while you were testing, so don't forget this part. Don't forget to add your module to the parent Makefile as well. 3) Commit the manpage. All drivers should have manpages. The manpage should try to list all the hardware your driver supports, as well as all the diagnostic messages it might print and their causes. Don't forget to add the manpage to the list in the Makefile. Don't put your manpage in an arch-specific directory unless the driver or device is *absolutely* architecture-specific. 4) Update the list in sysinstall/devices.c. For a disk device, the entry should look like: {DEVICE_TYPE_DISK, "foo%d", "FOO disk", , 65538, 8, 4}, Where is the cdev major number of your driver. 5) Update libdisk/create_chunk.c, by adding a line to parse the disk name in MakeDev(): else if (!strncmp(p, "foo", 4)) cmaj = , p += strlen("foo"); 6) Update libdisk/disk.c, by adding an entry for your disk driver's name in the device_list[] array. 7) Update MAKEDEV to create disk devices for your driver, and (optionally) a control device. You should update: - The 'Disks:' comment at the head of the file. - The 'Individual slices.' conditional. - The (unmarked) 'whole disk' conditional. Use one of the other disk device entries as an example here. The 'name' and 'chr' variables are set to the name and character major number of the disk respectively. The subconditionals exist to deal with the different name lengths (to parse the unit number), and you should add your driver to the appropriate case. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 23 11:29:17 2001 Delivered-To: freebsd-stable@freebsd.org Received: from sttlpop3.sttl.uswest.net (sttlpop3.sttl.uswest.net [206.81.192.3]) by hub.freebsd.org (Postfix) with SMTP id 2EEFF37B401 for ; Tue, 23 Jan 2001 11:28:57 -0800 (PST) Received: (qmail 10798 invoked by alias); 23 Jan 2001 18:54:56 -0000 Delivered-To: fixup-freebsd-stable@freebsd.org@fixme Received: (qmail 1048 invoked by uid 0); 23 Jan 2001 18:42:03 -0000 Received: from www.a6l.net (HELO a6l.net) (63.229.13.49) by sttlpop3.sttl.uswest.net with SMTP; 23 Jan 2001 18:42:03 -0000 Received: (qmail 64292 invoked by uid 1002); 23 Jan 2001 18:42:20 -0000 To: "Chris Faulhaber" Cc: freebsd-stable@freebsd.org Subject: Re: building a debug world References: <85r91v7741.fsf@diablo.in.a6l.net> <20010122141949.B51247@peitho.fxp.org> <85ofwzntw2.fsf@diablo.in.a6l.net> <20010122165415.A28683@peitho.fxp.org> From: Kevin Mills Date: 23 Jan 2001 10:42:20 -0800 In-Reply-To: "Chris Faulhaber"'s message of "Mon, 22 Jan 2001 16:54:15 -0500" Message-ID: <85r91uf6ur.fsf@diablo.in.a6l.net> Lines: 17 X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Chris Faulhaber" writes: > > > You also probably don't want to strip the binaries > > > hint: STRIP= > > > > OK... is there somewhere I can set this globally? I did a quick grep and > > didn't find many Makefiles with STRIP defined. Mostly contrib/bind and a few > > other places under gnu/usr.bin. Am I looking in the right place(s)? > > > > /etc/make.conf Hmmm, well that didn't seem to do it. Actually, I now have a stripped kernel after rebuilding everything...? Any other ideas? Anyone? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 23 12: 2:25 2001 Delivered-To: freebsd-stable@freebsd.org Received: from c014.sfo.cp.net (c014-h003.c014.sfo.cp.net [209.228.12.67]) by hub.freebsd.org (Postfix) with SMTP id 0A1B937B401 for ; Tue, 23 Jan 2001 12:02:05 -0800 (PST) Received: (cpmta 14878 invoked from network); 23 Jan 2001 11:10:06 -0800 Received: from d8c81e5f.dsl.flashcom.net (HELO quadrajet.flashcom.com) (216.200.30.95) by smtp.flashcom.net (209.228.12.67) with SMTP; 23 Jan 2001 11:10:06 -0800 X-Sent: 23 Jan 2001 19:10:06 GMT Received: (from guy@localhost) by quadrajet.flashcom.com (8.9.3/8.9.3) id LAA00428; Tue, 23 Jan 2001 11:10:05 -0800 (PST) (envelope-from gharris) Date: Tue, 23 Jan 2001 11:10:05 -0800 From: Guy Harris To: Guy Harris , Neil Brown , Linux NFS mailing list , FreeBSD Stable Subject: Re: [NFS] Incompatible: FreeBSD 4.2 client, Linux 2.2.18 nfsv3 server, read-only export Message-ID: <20010123111005.D344@quadrajet.flashcom.com> References: <20010123015612.H345@quadrajet.flashcom.com> <20010123162930.B5443@emma1.emma.line.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <20010123162930.B5443@emma1.emma.line.org>; from matthias.andree@stud.uni-dortmund.de on Tue, Jan 23, 2001 at 04:29:30PM +0100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jan 23, 2001 at 04:29:30PM +0100, Matthias Andree wrote: > Okay. So, as a conclusion, my original bug report boils down to: > > "You cannot mount read-only file systems with NFS v3 from a Linux 2.2.18 > server to a FreeBSD 4.2-STABLE client. Use NFS v2 instead." > > The question remains: Linux kernel problem or FreeBSD client problem? I'd consider the Linux kernel sending NFS3ERR_ROFS over the wire in the response to an ACCESS call checking write access to be an error on the part of the Linux NFS server, as 1) the spec doesn't list NFS3ERR_ROFS as a valid reply and 2) as per my other mail, it means it can't properly report what's permitted if the ACCESS call checks both read and write access - NFS3ERR_ROFS doesn't say "reading is OK, writing isn't" Presumably that's why the protocol spec doesn't list NFS3ERR_ROFS (Perhaps it would've been better had the V3 protocol specified that either 0 or an NFS3ERR_xxx value be supplied for each of the permission bits checked, although that raises the question of whether any server would, say, allow read access and allow write access but disallow simultaneous read/write access.) One might also consider it a FreeBSD client problem that it can't cope with this, if the Solaris client can, although that one might be a weaker claim (i.e., the Linux server is arguably violating the spec, whilst the FreeBSD client is merely apparently not doing as good a job of coping with servers violating the spec as the Solaris client is, in this case). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 23 12: 7:47 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 D6F2037B400; Tue, 23 Jan 2001 12:07:28 -0800 (PST) Received: from jesup.eng.tvol.net ([10.32.2.26]) by mail.wgate.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21) id CX5HSM6D; Tue, 23 Jan 2001 15:07:27 -0500 Reply-To: Randell Jesup To: obrien@FreeBSD.ORG Cc: Randell Jesup , freebsd-stable@FreeBSD.ORG Subject: Re: "Malloc type lacks magic" show-stopper solved References: <20001105113907.B2656@dragon.nuxi.com> From: Randell Jesup Date: 23 Jan 2001 15:10:35 -0500 In-Reply-To: "David O'Brien"'s message of "Sun, 5 Nov 2000 11:39:07 -0800" Message-ID: User-Agent: Gnus/5.0807 (Gnus v5.8.7) 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 "David O'Brien" writes: >On Thu, Nov 02, 2000 at 11:37:09AM -0500, Randell Jesup wrote: >> -O2 should work. I've never seen a bug with -O2 code generation >> from GCC (not that they can't happen, of course). Most bugs I've seen in >> my career with optimization levels were actually timing holes in the >> source code, where someone was accessing a shared resource and counting >> on ordering/etc, or bugs with accessing hardware registers where structures >> weren't properly marked volatile. >> >> If there's a problem, find it and report it. IMHO. > >Love to, but its often too hard -- unless handing over an entire kernel >source directory as the test case showing the bug is acceptable. (Response to an old article) The point I was trying to make was that my first assumption would be that the bug is due to race conditions or missing 'volatile' statements, probably in hardware drivers or code that interacts with CPU hardware (page tables, etc). Perhaps it's a holdover (in habits) from the days before useful optimizers in Unix C compilers. When one typically runs/compiles unoptimized code (or minimally optimized code), it's easy to get out of the habit of using volatile. (Witness all the 'register' statements in Unix kernels, which almost any compiler worth it's salt should ignore.) Now, certainly there are LOTS of volatile statements in the kernel - but it only takes a few (or even one) missing volatile to leave you in danger from optimizers. And just because -O happens to work doesn't mean there isn't a hole - it may just be smaller, or it may show up the next time the compiler is revved, or if someone uses a different compiler, or ports to a different architecture. And, as I mentioned, perhaps it's a -O2 compiler bug, in which case I want to see it fixed anyways. It wouldn't surprise me if there's only one or two problems (in the kernel or compiler). IMHO. -- Randell Jesup, Worldgate Communications, ex-Scala, ex-Amiga OS team ('88-94) rjesup@wgate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 23 12: 9:12 2001 Delivered-To: freebsd-stable@freebsd.org Received: from vexpert.dbai.tuwien.ac.at (vexpert.dbai.tuwien.ac.at [128.130.111.12]) by hub.freebsd.org (Postfix) with ESMTP id 57F4737B402 for ; Tue, 23 Jan 2001 12:08:54 -0800 (PST) Received: from taygeta.dbai.tuwien.ac.at (taygeta [128.130.111.77]) by vexpert.dbai.tuwien.ac.at (8.11.1/8.11.1) with ESMTP id f0NH6xe02198; Tue, 23 Jan 2001 18:07:00 +0100 (MET) Received: from localhost (pfeifer@localhost) by taygeta.dbai.tuwien.ac.at (8.11.1/8.11.1) with ESMTP id f0NH6xG66250; Tue, 23 Jan 2001 18:06:59 +0100 (CET) (envelope-from pfeifer@dbai.tuwien.ac.at) X-Authentication-Warning: taygeta.dbai.tuwien.ac.at: pfeifer owned process doing -bs Date: Tue, 23 Jan 2001 18:06:58 +0100 (CET) From: Gerald Pfeifer To: Cc: Kal Torak , , Subject: Re: passwd (still) broken in NIS environments In-Reply-To: <3A6D967F.B464AB45@quake.com.au> 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, 24 Jan 2001, Kal Torak wrote: > passwd uses whatever format you specified in /etc/login.conf for that > users login class... > Since the default crypt has been changing around with export restrictions > being lifted etc. You should just put that you want DES in there... > > put in the line ":passwd_format=des:\" under "default:\" Thanks, that did it! What really confuses me is that logging it had worked all the time; just the passwd command on NIS clients broke. Weird, very weird. While we are at it, how about adding default:\ :passwd_format=md5:\ :... to /etc/login.conf to make clear that MD5 is now the default? Yes, I had checked , it's just that the string MD5 does not appear on that page at all. :-( :-( Thanks to all who helped! Gerald -- Gerald "Jerry" pfeifer@dbai.tuwien.ac.at http://www.dbai.tuwien.ac.at/~pfeifer/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 23 12:12:54 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 C3BCA37B402 for ; Tue, 23 Jan 2001 12:12:34 -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 HAA17284 for ; Wed, 24 Jan 2001 07:12:29 +1100 (EDT) Received: from gsmx07.alcatel.com.au by cim.alcatel.com.au (PMDF V5.2-32 #37640) with ESMTP id <01JZ9ZCL573K8ZUIYT@cim.alcatel.com.au> for stable@FreeBSD.ORG; Wed, 24 Jan 2001 07:12:28 +1100 Received: (from jeremyp@localhost) by gsmx07.alcatel.com.au (8.11.1/8.11.1) id f0NKCR462206; Wed, 24 Jan 2001 07:12:27 +1100 (EST envelope-from jeremyp) Content-return: prohibited Date: Wed, 24 Jan 2001 07:12:27 +1100 From: Peter Jeremy Subject: Re: Running with very high HZ ? In-reply-to: ; from Thierry.Herbelot@alcatel.fr on Tue, Jan 23, 2001 at 12:00:17PM +0100 To: Thierry.Herbelot@alcatel.fr Cc: stable@FreeBSD.ORG Mail-followup-to: Thierry.Herbelot@alcatel.fr, stable@FreeBSD.ORG Message-id: <20010124071227.K52423@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: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 2001-Jan-23 12:00:17 +0100, Thierry.Herbelot@alcatel.fr wrote: >more precisely : is it ok to run a recent PC (P-III + BX chipset) with >HZ=5000 ? There may be a problem with integer overflow in some tape timeout calculations at very high HZ rates. (There was a reference to it on freebsd-current recently). Other than that I don't know of any problems, though Alfred Perlstein mentioned (in mid-January) that he knew of someone who had had problems that went away when he changed HZ back to 100 - unfortunately he doesn't have any other details. I have a P-133 and a PIII-600 both running with HZ=2000 to provide reasonable accuracy with small dummynet delays. Even on the P-133, there's still negligible system/interrupt load as a result. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 23 14:12: 8 2001 Delivered-To: freebsd-stable@freebsd.org Received: from gecko.eric.net.au (gecko.eric.net.au [203.102.228.3]) by hub.freebsd.org (Postfix) with ESMTP id C8FE437B6A0 for ; Tue, 23 Jan 2001 14:11:43 -0800 (PST) Received: (from ghcrompton@localhost) by gecko.eric.net.au (8.9.3/8.8.7) id JAA07136 for freebsd-stable@freebsd.org; Wed, 24 Jan 2001 09:15:23 +1100 Date: Wed, 24 Jan 2001 09:15:23 +1100 From: "Geoffrey Crompton (RMIT Guest)" To: freebsd-stable@freebsd.org Subject: getting Creative Vibra 128 PCI running Message-ID: <20010124091523.A7087@gecko.eric.net.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3us Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've been having problems getting freebsd 4.1 recognizing my sound card. The card is: Creative Vibra 128 PCI (compatible with Sound Blaster PCI) Chips: CT5880-DCQ and CT4810 Product code: CLVIBPCI128 In the config file for the kernel I have enabled pcm: # Sound card support device pcm # for sound card #device sbc # for Creative Sound Blaster but the dmesg for the pcm device says: pcm0: at device 9.0 on pci2 pcm0: unable to map register space device_probe_and_attach: pcm0 attach returned 6 Doing sh MAKEDEV /dev/snd0 after it has booted (with that dmesg) appears to run without any errors, but cat /dev/sndstat reports cat: sndstat: Device not configured (Which isn't that surprising considering the dmesg errors) Has anyone had any luck getting this sound working? Have I done something obviously wrong? Thanks Geoff Crompton To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 23 14:21:22 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 5FBAC37B402 for ; Tue, 23 Jan 2001 14:20:56 -0800 (PST) Received: from dwcjr (DWCJR.inethouston.net [216.118.21.147]) by leviathan.inethouston.net (Postfix) with ESMTP id 0A0A6177EA3; Tue, 23 Jan 2001 16:20:55 -0600 (CST) Message-ID: <01bf01c0858a$be2d6140$931576d8@inethouston.net> From: "David W. Chapman Jr." To: "Geoffrey Crompton (RMIT Guest)" , References: <20010124091523.A7087@gecko.eric.net.au> Subject: Re: getting Creative Vibra 128 PCI running Date: Tue, 23 Jan 2001 16:20:50 -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 The last time I ran 4.2-stable it seemed to work fine. Can't vouch for 4.1 or -stable though because I am running -current, but it did work for me while I was using stable. ----- Original Message ----- From: "Geoffrey Crompton (RMIT Guest)" To: Sent: Tuesday, January 23, 2001 4:15 PM Subject: getting Creative Vibra 128 PCI running > I've been having problems getting freebsd 4.1 recognizing my sound card. > The card is: > > Creative Vibra 128 PCI (compatible with Sound Blaster PCI) > Chips: CT5880-DCQ and CT4810 > Product code: CLVIBPCI128 > > > In the config file for the kernel I have enabled pcm: > # Sound card support > device pcm # for sound card > #device sbc # for Creative Sound Blaster > > but the dmesg for the pcm device says: > > pcm0: at device 9.0 on pci2 > pcm0: unable to map register space > device_probe_and_attach: pcm0 attach returned 6 > > Doing sh MAKEDEV /dev/snd0 after it has booted (with that dmesg) appears > to run without any errors, but > cat /dev/sndstat reports > cat: sndstat: Device not configured > (Which isn't that surprising considering the dmesg errors) > > Has anyone had any luck getting this sound working? Have I done > something obviously wrong? > > Thanks > Geoff Crompton > > > 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 23 15: 8:49 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 2037537B400 for ; Tue, 23 Jan 2001 15:08:30 -0800 (PST) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.11.1/8.11.1) with ESMTP id f0NN8Qj06713; Tue, 23 Jan 2001 15:08:26 -0800 (PST) (envelope-from jdp@wall.polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.11.1/8.11.0) id f0NN8QT25018; Tue, 23 Jan 2001 15:08:26 -0800 (PST) (envelope-from jdp) Date: Tue, 23 Jan 2001 15:08:26 -0800 (PST) Message-Id: <200101232308.f0NN8QT25018@vashon.polstra.com> To: stable@freebsd.org From: John Polstra Cc: CGiordano@ids.net Subject: Re: preventing cvsup from replacing /usr/ports symlink? In-Reply-To: <3A6C5E6C.3E84EAC0@ids.net> References: <200101202028.f0KKSUr80758@saturn.home.ben.com> <20010121021117.A2300@snark.ptc.spbu.ru> <200101210047.f0L0lBq15592@vashon.polstra.com> <3A6C5E6C.3E84EAC0@ids.net> Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <3A6C5E6C.3E84EAC0@ids.net>, Christopher M. Giordano wrote: > This happened to me two days ago (jan 20, 1030 AM), and it always > seems to occur when re-cvsup'ing following a failed cvsup. In > this case, the first attempt failed with a message like: "Updater > failed: unable to delete file archivers/arc/Makefile: no such file > or directory", which in itself seemed odd, since I was starting with > a full copy of the ports tree. I agree, that is very odd. It's especially odd since CVSup should have no reason to want to delete that particular file. It's alive and well in the CVS repository. :-} > Restarting cvsup then filled /usr/ports tree in my /usr filesystem > rather than the linked filesystem. I assume the link is deleted > upon the first failure, but I have no evidence of this. > > I know that's _very_ little to go on.... True, but it does help. Thanks to you and the others who sent information about this. Questions for those who have seen this happen: 1. You're using checkout mode, right? 2. Are you using "-s" on the cvsup command line? Finally, you can avoid any chance of this happening by making sure that CVSup's "prefix" setting points to the real parent directory of your ports tree -- not to a symlink that points there. Here's an easy way to find out, if there's any doubt: vashon$ cd /usr/ports vashon$ /bin/pwd /c/ports So in this case you should have "prefix=/c" in your supfile, either in a "*default" line or on the same line(s) as your ports collection(s). 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 Tue Jan 23 15:12: 9 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 B763737B402; Tue, 23 Jan 2001 15:11:46 -0800 (PST) Received: from awww.jeah.net (awww.jeah.net [216.111.239.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5DF996E337A; Tue, 23 Jan 2001 15:11:37 -0800 (PST) Received: from localhost (chris@localhost) by awww.jeah.net (8.11.1/8.11.0) with ESMTP id f0NN8XX43222; Tue, 23 Jan 2001 17:08:33 -0600 (CST) (envelope-from chris@jeah.net) Date: Tue, 23 Jan 2001 17:08:32 -0600 (CST) From: Chris Byrnes To: questions@freebsd.org Cc: stable@freebsd.org 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 default:\ :if=/etc/issue: in gettytab should display 'issue' at login. It doesnt anymore. Any idea why? Chris Byrnes JEAH Communications (Direct) 608-256-6167 (Toll-Free) 866-299-5324 http://www.JEAH.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 23 15:27:30 2001 Delivered-To: freebsd-stable@freebsd.org Received: from vexpert.dbai.tuwien.ac.at (vexpert.dbai.tuwien.ac.at [128.130.111.12]) by hub.freebsd.org (Postfix) with ESMTP id 7DDAD37B69C for ; Tue, 23 Jan 2001 15:27:13 -0800 (PST) Received: from deneb.dbai.tuwien.ac.at (deneb [128.130.111.2]) by vexpert.dbai.tuwien.ac.at (8.11.1/8.11.1) with ESMTP id f0NNR9e08814; Wed, 24 Jan 2001 00:27:10 +0100 (MET) Received: from localhost (pfeifer@localhost) by deneb.dbai.tuwien.ac.at (8.11.1/8.11.1) with ESMTP id f0NNR8957448; Wed, 24 Jan 2001 00:27:09 +0100 (CET) (envelope-from pfeifer@dbai.tuwien.ac.at) X-Authentication-Warning: deneb.dbai.tuwien.ac.at: pfeifer owned process doing -bs Date: Wed, 24 Jan 2001 00:27:08 +0100 (CET) From: Gerald Pfeifer To: , "David O'Brien" Subject: MFC: /etc/login.conf 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'd like to suggest MCFing this, especially the "password_format=md5" bit: revision 1.38 date: 2000/11/21 23:25:39; author: obrien; state: Exp; lines: +9 -1 Add `password_format=md5' to the default settings. I've had this locally for a while, but a recent email to -stable suggests it should be spelled out as the documentation of "password_format" is sparse. Also add a `des_users' entry. Submitted by: Sean O'Connell See my earlier messages today on some background. This would have saved us quite a bit of time, so at least it would be nice to see it in 4.3-RELEASE. Gerald -- Gerald "Jerry" pfeifer@dbai.tuwien.ac.at http://www.dbai.tuwien.ac.at/~pfeifer/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 23 15:29: 9 2001 Delivered-To: freebsd-stable@freebsd.org Received: from subnet.sub.net (subnet.sub.net [212.227.14.21]) by hub.freebsd.org (Postfix) with ESMTP id 8889D37B69F for ; Tue, 23 Jan 2001 15:28:51 -0800 (PST) Received: from lyxys.ka.sub.org (uucp@localhost) by subnet.sub.net (8.8.8/8.8.8/1.2subnet-linux) with bsmtp id AAA28366; Wed, 24 Jan 2001 00:28:45 +0100 Received: from localhost (1832 bytes) by lyxys.ka.sub.org via sendmail with P:stdio/R:smart_host/T:inet_uusmtp (sender: ) (ident using unix) id for ; Tue, 23 Jan 2001 23:41:54 +0100 (CET) (Smail-3.2.0.111 2000-Feb-17 #1 built 2000-Aug-23) Message-Id: From: wolfgang@lyxys.ka.sub.org (Wolfgang Zenker) Subject: Re: [NFS] Incompatible: FreeBSD 4.2 client, Linux 2.2.18 nfsv3 server, read-only export In-Reply-To: "from Bjoern Groenvall at Jan 23, 2001 05:26:54 pm" To: Bjoern Groenvall Date: Tue, 23 Jan 2001 23:41:54 +0100 (CET) Cc: FreeBSD Stable , Linux NFS mailing list , Guy Harris , Neil Brown , matthias.andree@stud.uni-dortmund.de 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 > Matthias> The question remains: Linux kernel problem or FreeBSD client > Matthias> problem? > Or perhaps we should blame RFC1813? I don't think so, because .. > However, 1813 says that ACCESS > should return one of the following errors > NFS3ERR_IO > NFS3ERR_STALE > NFS3ERR_BADHANDLE > NFS3ERR_SERVERFAULT > ,and "The client encodes the > set of permissions that are to be checked in a bit mask. > The server checks the permissions encoded in the bit mask. > A status of NFS3_OK is returned along with a bit mask > encoded with the permissions that the client is allowed.". The wording here is totally clear: The client is not allowed write access on a read-only filesystem, so return NFS3_OK with the write bits turned off. > It also says > "NFS3ERR_ROFS > Read-only file system. A modifying operation was > attempted on a read-only file system." As ACCESS is not a "modifying operation", there is no contradiction here. Wolfgang To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 23 15:49:16 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 64D2037B6A4 for ; Tue, 23 Jan 2001 15:48:59 -0800 (PST) Received: (from dbushong@localhost) by firebat.bushong.net (8.11.0/8.11.0) id f0NNmt376334; Tue, 23 Jan 2001 15:48:55 -0800 (PST) (envelope-from dbushong) Date: Tue, 23 Jan 2001 15:48:55 -0800 From: David Bushong To: John Polstra Cc: stable@FreeBSD.ORG, CGiordano@ids.net Subject: Re: preventing cvsup from replacing /usr/ports symlink? Message-ID: <20010123154855.U16505@bushong.net> References: <200101202028.f0KKSUr80758@saturn.home.ben.com> <20010121021117.A2300@snark.ptc.spbu.ru> <200101210047.f0L0lBq15592@vashon.polstra.com> <3A6C5E6C.3E84EAC0@ids.net> <200101232308.f0NN8QT25018@vashon.polstra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200101232308.f0NN8QT25018@vashon.polstra.com>; from jdp@polstra.com on Tue, Jan 23, 2001 at 03:08:26PM -0800 X-Floating-Sheep-Port: 0xbaa Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jan 23, 2001 at 03:08:26PM -0800, John Polstra wrote: > > ... > > Questions for those who have seen this happen: > > 1. You're using checkout mode, right? > Yep. > 2. Are you using "-s" on the cvsup command line? > Yep. > Finally, you can avoid any chance of this happening by making sure > that CVSup's "prefix" setting points to the real parent directory of > your ports tree -- not to a symlink that points there. Here's an > easy way to find out, if there's any doubt: > > vashon$ cd /usr/ports > vashon$ /bin/pwd > /c/ports > > So in this case you should have "prefix=/c" in your supfile, either in > a "*default" line or on the same line(s) as your ports collection(s). > Did that a week ago; seems to have fixed the problem. --David Bushong To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 23 16: 7:24 2001 Delivered-To: freebsd-stable@freebsd.org Received: from c014.sfo.cp.net (c014-h001.c014.sfo.cp.net [209.228.12.65]) by hub.freebsd.org (Postfix) with SMTP id F0F1637B400 for ; Tue, 23 Jan 2001 16:07:03 -0800 (PST) Received: (cpmta 6706 invoked from network); 23 Jan 2001 10:53:51 -0800 Received: from d8c81e5f.dsl.flashcom.net (HELO quadrajet.flashcom.com) (216.200.30.95) by smtp.flashcom.net (209.228.12.65) with SMTP; 23 Jan 2001 10:53:51 -0800 X-Sent: 23 Jan 2001 18:53:51 GMT Received: (from guy@localhost) by quadrajet.flashcom.com (8.9.3/8.9.3) id KAA00392; Tue, 23 Jan 2001 10:53:50 -0800 (PST) (envelope-from gharris) Date: Tue, 23 Jan 2001 10:53:50 -0800 From: Guy Harris To: Bjoern Groenvall Cc: FreeBSD Stable , Linux NFS mailing list , Guy Harris , Neil Brown , matthias.andree@stud.uni-dortmund.de Subject: Re: [NFS] Incompatible: FreeBSD 4.2 client, Linux 2.2.18 nfsv3 server, read-only export Message-ID: <20010123105350.B344@quadrajet.flashcom.com> References: <20010123015612.H345@quadrajet.flashcom.com> <20010123162930.B5443@emma1.emma.line.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: ; from bg@sics.se on Tue, Jan 23, 2001 at 05:26:54PM +0100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jan 23, 2001 at 05:26:54PM +0100, Bjoern Groenvall wrote: > The RFC does not explicitly mention how to handle read-only file > systems. I think it would be really nice if the server returns those > permissions that the client is allowed with the write bits unset. Yes - for one thing, that means that if some client decides, while it's asking whether the server whether it can write to a file, to check also whether it can read from the file, it can get back an answer to both of those questions, even if the file is on a read-only file system. > That is also the solution that Guy came up with. I can't claim credit for the notion of handling ACCESS requests to files on read-only file systems in that fashion - I just checked what Solaris did. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 23 17:11:12 2001 Delivered-To: freebsd-stable@freebsd.org Received: from www.evil.2y.net (ip-216-23-53-20.adsl.one.net [216.23.53.20]) by hub.freebsd.org (Postfix) with ESMTP id 54CE937B6B6 for ; Tue, 23 Jan 2001 17:10:55 -0800 (PST) Received: (from cokane@localhost) by www.evil.2y.net (8.11.1/8.11.1) id f0O1NAX72988; Tue, 23 Jan 2001 20:23:10 -0500 (EST) (envelope-from cokane) Date: Tue, 23 Jan 2001 20:23:10 -0500 From: Coleman Kane To: Kal Torak Cc: "Geoffrey Crompton (RMIT Guest)" , freebsd-stable@freebsd.org Subject: Re: hard read errors Message-ID: <20010123202310.A72951@cokane.yi.org> References: <20010123174558.A427@gecko.eric.net.au> <3A6D4A30.806FCCFD@quake.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <3A6D4A30.806FCCFD@quake.com.au>; from kaltorak@quake.com.au on Tue, Jan 23, 2001 at 04:09:33AM -0500 X-Vim: vim:tw=70:ts=4:sw=4 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'd still back up the data as soon as possible. I have seen that message preclude a hard drive crash so many times, it's not even funny. Kal Torak had the audacity to say: > > "Geoffrey Crompton (RMIT Guest)" wrote: > > > > I'm getting many hard read errors on a machine. I had these errors > > back in 4.1.1, and still in 4.2. A section of /var/log/messages says: > > > > Jan 23 17:12:44 ipv6-gw /kernel: ad0: HARD READ ERROR blk# 14484670ad0: HARD READ ERROR blk# 14484670 status=59 error=40 > > Jan 23 17:12:44 ipv6-gw /kernel: ad0: DMA problem fallback to PIO mode > > Jan 23 17:12:44 ipv6-gw /kernel: IPv6 packet filtering initialized, logging disabled > > Jan 23 17:12:44 ipv6-gw /kernel: ad0: HARD READ ERROR blk# 14484670 status=59 error=40 > > Jan 23 17:12:44 ipv6-gw /kernel: ad0: HARD READ ERROR blk# 14484670 status=59 error=40 > > > Soren MFC'd a new ata-dma.c just a few days ago... > Its worth getting the new source and compiling it into your kernel > and see if that fixes your problems > > > 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 23 17:20: 3 2001 Delivered-To: freebsd-stable@freebsd.org Received: from aeon.invision.net (aeon.invision.net [206.112.34.19]) by hub.freebsd.org (Postfix) with ESMTP id B644837B6B6 for ; Tue, 23 Jan 2001 17:19:42 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by aeon.invision.net (8.11.1/8.11.0) with ESMTP id f0O1Jfj53525 for ; Tue, 23 Jan 2001 20:19:41 -0500 (EST) (envelope-from martini@invision.net) Date: Tue, 23 Jan 2001 20:19:41 -0500 (EST) From: Matt Martini Reply-To: "Matthew E. Martini" To: freebsd-stable@FreeBSD.ORG Subject: invalid partition 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 recently added a 3ware ATA Raid card to a 4.2-R box. Now I get "invalid partition" messages on bootup. Does anyone know how to fix this? I am able to get the system to run with manual intervnetion, but reboot fails. Here is more detail on what happens at boot: 3ware Storage Controller BIOS BEXX 1.03.00.027 ARRAY UNIT 0 STRIPE 64K 120.0 GB PORT 0 ST340823A 40.0GB PORT 1 ST340823A 40.0GB PORT 2 ST340823A 40.0GB 3ware BIOS installed successfully Adaptec AHA-2940 Ultra/Ultra w/ BIOS v1.25 SCSI ID:LUN NUMBER #:# 0:0 - SEAGATE ST34527N - Drive D: (81h) SCSI ID:LUN NUMBER #:# 2:0 - SEAGATE ST34527N - Drive 82h SCSI ID:LUN NUMBER #:# 3:0 - TEAK CD-R58S SCSI BIOS installed successfully invalid partition invalid partition No /boot/loader >>FreeBSD/i386 BOOT Default: 0:ad(0,a)/kernel boot: invalid partition No /kernel >>FreeBSD/i386 BOOT Default: 0:ad(0,a)/kernel boot: At this point if type in 1:ad(0,a)/kernel the boot will start to proceed. Then it will stop with: no devsw (majdev=30 bootdev=0x020001e) Manual root filesystem specification: : mountroot> Now I can type ufs:/dev/da0s1a and the machine will come up. What do I have to do so that machine will boot normally? Thanks for your help, Matt __________________________ http://www.invision.net/ _______________________ Matthew E. Martini, PE InVision.com, Inc. (631) 543-1000 x104 Chief Technology Officer matt@invision.net (631) 864-8896 Fax _______________________________________________________________________pgp_ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 23 17:24:31 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id B705A37B6B6 for ; Tue, 23 Jan 2001 17:24:14 -0800 (PST) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.1/8.11.1) with ESMTP id f0O1dXS06434; Tue, 23 Jan 2001 17:39:37 -0800 (PST) (envelope-from msmith@mass.dis.org) Message-Id: <200101240139.f0O1dXS06434@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Matthew E. Martini" Cc: freebsd-stable@FreeBSD.ORG Subject: Re: invalid partition In-reply-to: Your message of "Tue, 23 Jan 2001 20:19:41 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 23 Jan 2001 17:39:33 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I recently added a 3ware ATA Raid card to a 4.2-R box. Now I get > "invalid partition" messages on bootup. > > Does anyone know how to fix this? Reconfigure your system so that it's not trying to boot from the 3ware array. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 23 17:52:39 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 5838437B400 for ; Tue, 23 Jan 2001 17:52:20 -0800 (PST) Received: from dwcjr (DWCJR.inethouston.net [216.118.21.147]) by leviathan.inethouston.net (Postfix) with ESMTP id 18608177EA7 for ; Tue, 23 Jan 2001 19:52:18 -0600 (CST) Message-ID: <030601c085a8$491e5b20$931576d8@inethouston.net> From: "David W. Chapman Jr." To: References: <20010123174558.A427@gecko.eric.net.au> <3A6D4A30.806FCCFD@quake.com.au> <20010123202310.A72951@cokane.yi.org> Subject: Hard drive errors Date: Tue, 23 Jan 2001 19:52:19 -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 freebsd any better at handling bad sectors/blocks than it was around 2.2.8/3.0? Just curious, because I remember it not handling them too good. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 23 19:14:23 2001 Delivered-To: freebsd-stable@freebsd.org Received: from topsecret.net (unknown [216.19.133.97]) by hub.freebsd.org (Postfix) with SMTP id 1EF4737B6A3 for ; Tue, 23 Jan 2001 19:14:03 -0800 (PST) Received: from pacific.net128.101.101.10.in-addr.arpa by topsecret.net with SMTP (MDaemon.v2.7.SP5.R) for ; Tue, 23 Jan 2001 22:12:25 -0500 Date: Tue, 23 Jan 2001 22:11:54 -0500 (EST) From: "[gill]" X-Sender: gill@pacific.int.topsecret.net To: freebsd-stable@freebsd.org Subject: and IDea I had Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-MDaemon-Deliver-To: freebsd-stable@freebsd.org X-Return-Path: gill@topsecret.net Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG today I ran into a problem that was my fault and involved careless use of mergemaster (ConnectionsPerPeriod is depricated, fwiw). I had cvsup'd a brand new box from 4.2-R to 4.2-S and a single file which i had NOT edited from the original version that installed with 4.2-R did not get replaced. I started thinking, I see this tag that is related to the CVS revisioning on each of the files: # $FreeBSD: src/etc/hosts,v 1.11.2.1 2000/08/18 18:29:19 ume Exp $ and i wondered: what if this tag were expanded to include a checksum of that file so that mergemaster could decide if the file had been edited and ifF not, it could (as an option) automagically replace. then again, maybe i'm being too lazy ... but if i'm going to wholesale update my bins, why not the same with confs? --gill -- This is my ~/.signature file. It is the digital equivalent of a bumpersticker. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 23 19:15: 8 2001 Delivered-To: freebsd-stable@freebsd.org Received: from emma1.emma.line.org (p3EE3CBDA.dip.t-dialin.net [62.227.203.218]) by hub.freebsd.org (Postfix) with ESMTP id 98E9537B69F for ; Tue, 23 Jan 2001 19:14:48 -0800 (PST) Received: by emma1.emma.line.org (Postfix, from userid 500) id A65C1A2001; Wed, 24 Jan 2001 04:14:37 +0100 (CET) Date: Wed, 24 Jan 2001 04:14:37 +0100 From: Matthias Andree Cc: FreeBSD Stable , Linux NFS mailing list , Linux-Kernel mailing list , Alan Cox Subject: Linux 2.2.18 nfs v3 server bug (was: Incompatible: FreeBSD 4.2 client, Linux 2.2.18 nfsv3 server, read-only export) Message-ID: <20010124041437.A28212@emma1.emma.line.org> References: <20010123015612.H345@quadrajet.flashcom.com> <20010123162930.B5443@emma1.emma.line.org> <20010123105350.B344@quadrajet.flashcom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010123105350.B344@quadrajet.flashcom.com>; from gharris@flashcom.net on Tue, Jan 23, 2001 at 10:53:50 -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG (Please consider removing FreeBSD-stable from the recipient list when replying.) Summary: The Linux 2.2.18 NFS v3 server returns bogus and as per RFC-1813 invalid NFS3ERR_ROFS to ACCESS procedure calls when exporting a file system read-only, when it should instead return "OK" along with the actual permissions the client has, ANDed with the permissions the client queried. The bug is visible on FreeBSD 4.2-STABLE client which cannot ls The mounted file system (NFS v2 is fine since it does not have ACCESS). There is no related log entry in the 2.2.19pre7 change log. I did not check Linux 2.4.0, 2.4.0-acX or 2.4.1-preX either. On Tue, 23 Jan 2001, Guy Harris wrote: > Yes - for one thing, that means that if some client decides, while it's > asking whether the server whether it can write to a file, to check also > whether it can read from the file, it can get back an answer to both of > those questions, even if the file is on a read-only file system. Yup. Looks like a Linux kernel bug, so I'm cc'ing Alan Cox as kernel release maintainer as well as linux-kernel to make this a known issue. I got libpcap 0.6.1 and ethereal 0.8.15 and that's what I found: FreeBSD 4.2-STABLE sends three NFSPROC3_ACCESS requests, with 0x3f argument (meaning READ|LOOKUP|MODIFY|EXTEND|DELETE|EXECUTE), and to each, Linux 2.2.18 sends NFS3ERR_ROFS back, obj_attributes contains the stat data. ERR_ROFS is invalid here and makes indeed no sense, proper behaviour would be NFS3_OK with just READ|LOOKUP|EXECUTE set, since the server can actually access or stat the exported FS. Please correct me if I'm mistaking what RFC 1813 demands. client: $ mount server:/space /mnt $ ls /mnt ls: mnt: Read-only file system (FreeBSD 4.2-STABLE) server: $ ls -ld /space/ drwxrwxrwt 23 root root 706 Jan 2 11:53 /space/ $ grep /space /etc/exports /space 192.168.0.0/255.255.255.0(ro) (Linux 2.2.18, nfs-utils 0.2.1) -- Matthias Andree To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 23 19:20: 7 2001 Delivered-To: freebsd-stable@freebsd.org Received: from emma1.emma.line.org (p3EE3CBDA.dip.t-dialin.net [62.227.203.218]) by hub.freebsd.org (Postfix) with ESMTP id 0A06437B6A5 for ; Tue, 23 Jan 2001 19:19:48 -0800 (PST) Received: by emma1.emma.line.org (Postfix, from userid 500) id 8A8EEA2001; Wed, 24 Jan 2001 04:19:41 +0100 (CET) Date: Wed, 24 Jan 2001 04:19:41 +0100 From: Matthias Andree To: Bjoern Groenvall Cc: FreeBSD Stable , Linux NFS mailing list Subject: Re: [NFS] Incompatible: FreeBSD 4.2 client, Linux 2.2.18 nfsv3 server, read-only export Message-ID: <20010124041941.B28212@emma1.emma.line.org> References: <20010123015612.H345@quadrajet.flashcom.com> <20010123162930.B5443@emma1.emma.line.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from bg@sics.se on Tue, Jan 23, 2001 at 17:26:54 +0100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 23 Jan 2001, Bjoern Groenvall wrote: > Or perhaps we should blame RFC1813? No. > However, 1813 says that ACCESS > should return one of the following errors > NFS3ERR_IO > NFS3ERR_STALE > NFS3ERR_BADHANDLE > NFS3ERR_SERVERFAULT > ,and "The client encodes the > set of permissions that are to be checked in a bit mask. > The server checks the permissions encoded in the bit mask. > A status of NFS3_OK is returned along with a bit mask > encoded with the permissions that the client is allowed.". That's what Linux does not do ATM. > It also says > "NFS3ERR_ROFS > Read-only file system. A modifying operation was > attempted on a read-only file system." ACCESS is not a modification attempt, so ROFS in response to ACCESS is always bogus. There is no contradiction here, so the server is at fault. > The RFC does not explicitly mention how to handle read-only file > systems. No need to. > I think it would be really nice if the server returns those > permissions that the client is allowed with the write bits unset. That > is also the solution that Guy came up with. Agreed. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 23 19:35: 4 2001 Delivered-To: freebsd-stable@freebsd.org Received: from emma1.emma.line.org (p3EE3CBDA.dip.t-dialin.net [62.227.203.218]) by hub.freebsd.org (Postfix) with ESMTP id 5D57A37B400 for ; Tue, 23 Jan 2001 19:34:46 -0800 (PST) Received: by emma1.emma.line.org (Postfix, from userid 500) id 8FE5BA2001; Wed, 24 Jan 2001 04:34:36 +0100 (CET) To: Guy Harris Cc: Linux NFS mailing list , FreeBSD Stable Subject: Re: [NFS] Incompatible: FreeBSD 4.2 client, Linux 2.2.18 nfsv3 server, read-only export References: <20010123015612.H345@quadrajet.flashcom.com> <20010123162930.B5443@emma1.emma.line.org> <20010123111005.D344@quadrajet.flashcom.com> In-Reply-To: <20010123111005.D344@quadrajet.flashcom.com> From: Matthias Andree Date: 24 Jan 2001 04:34:36 +0100 Message-ID: Lines: 34 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 > (Perhaps it would've been better had the V3 protocol specified that > either 0 or an NFS3ERR_xxx value be supplied for each of the permission > bits checked, although that raises the question of whether any server > would, say, allow read access and allow write access but disallow > simultaneous read/write access.) No, the plan is simple. In the ACCESS call, the client asks if it has a certain set of permissions, the sender weeds the actions the client may not take at the moment of the ACCESS call, and returns a possibly stripped-down set of allowed actions (which may then change later). There's nothing wrong with this approach. Plus, I don't expect that ACCESS has context-sensitive semantics (like: allow each of read or write on its own, but deny read-write), or I may have overlooked the explicit statement it has these semantics. > One might also consider it a FreeBSD client problem that it can't cope > with this, if the Solaris client can, No, FreeBSD just passed the error on to the application. Keeping it simple and refraining from workarounds is a virtue. > although that one might be a weaker claim (i.e., the Linux server is > arguably violating the spec, whilst the FreeBSD client is merely > apparently not doing as good a job of coping with servers violating > the spec as the Solaris client is, in this case). Tolerance (FreeBSD kludging around broken Linux server) may be good for making these systems cooperate, but fixing the problem rather than its symptoms is the right way to go. Until then, mount_nfs -2 is a viable alternative for many, if not most, FreeBSD users. -- Matthias Andree To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 23 20:50:16 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 6E7BE37B400 for ; Tue, 23 Jan 2001 20:49:58 -0800 (PST) Received: (from kris@localhost) by citusc17.usc.edu (8.11.1/8.11.1) id f0O4rRA26472; Tue, 23 Jan 2001 20:53:27 -0800 (PST) (envelope-from kris) Date: Tue, 23 Jan 2001 20:53:27 -0800 From: Kris Kennaway To: "[gill]" Cc: freebsd-stable@FreeBSD.ORG Subject: Re: and IDea I had Message-ID: <20010123205327.B26378@citusc17.usc.edu> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="tsOsTdHNUZQcU9Ye" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from gill@topsecret.net on Tue, Jan 23, 2001 at 10:11:54PM -0500 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --tsOsTdHNUZQcU9Ye Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Jan 23, 2001 at 10:11:54PM -0500, [gill] wrote: >=20 > today I ran into a problem that was my fault and involved careless use of > mergemaster (ConnectionsPerPeriod is depricated, fwiw). I had cvsup'd a > brand new box from 4.2-R to 4.2-S and a single file which i had NOT edited > from the original version that installed with 4.2-R did not get replaced. >=20 > I started thinking, I see this tag that is related to the CVS revisioning > on each of the files: > # $FreeBSD: src/etc/hosts,v 1.11.2.1 2000/08/18 18:29:19 ume Exp $ >=20 > and i wondered: what if this tag were expanded to include a checksum of > that file so that mergemaster could decide if the file had been edited and > ifF not, it could (as an option) automagically replace. And where would it compare the checksum against? ;-) Mergemaster can already do this by diffing the installed version with the one in /usr/src - by default it doesn't though, and only checks the $FreeBSD$ headers because it results in less spurious merge dialogs (i.e. every time you run the program it will ask for merges on the same set of files, because they're still different). Check the manpage. Kris --=20 NOTE: To fetch an updated copy of my GPG key which has not expired, finger kris@FreeBSD.org --tsOsTdHNUZQcU9Ye 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 iD8DBQE6bl/GWry0BWjoQKURAqSjAJ9Wwtv/pg04GeE5B7prKs5ygxJ7CQCbBElR 8nIuCWFh8AMo7ooV5Ly9gm0= =oEAq -----END PGP SIGNATURE----- --tsOsTdHNUZQcU9Ye-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 23 20:54:51 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 114FE37B400 for ; Tue, 23 Jan 2001 20:54:30 -0800 (PST) Received: (from kris@localhost) by citusc17.usc.edu (8.11.1/8.11.1) id f0O4vxn26542; Tue, 23 Jan 2001 20:57:59 -0800 (PST) (envelope-from kris) Date: Tue, 23 Jan 2001 20:57:59 -0800 From: Kris Kennaway To: Shawn Barnhart Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Non-sequential one-time passwords? Message-ID: <20010123205759.C26378@citusc17.usc.edu> References: <00a601c0848b$e9600ac0$b8209fc0@marlowe> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="FsscpQKzF/jJk6ya" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <00a601c0848b$e9600ac0$b8209fc0@marlowe>; from swb@grasslake.net on Mon, Jan 22, 2001 at 09:56:40AM -0600 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --FsscpQKzF/jJk6ya Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Jan 22, 2001 at 09:56:40AM -0600, Shawn Barnhart wrote: > I'm looking for a way to do one time passwords. S/Key would work great, = but > when generating several passwords it turns out they have to be used > sequentially rather than at random. The sequential nature of S/Key passwo= rds > is kind of a problem, because I don't think I can rely on the people givi= ng > out the one-time passwords to properly ensure they're given out in sequen= ce > and they can't guarantee they will be used in sequence. >=20 > The basic idea is to have say five accounts, each with a block of 10 > one-time passwords. These could be given out on an as-needed basis to > freelancers for access to an FTP site. >=20 > Is there some scheme for doing this or am I SOL? Nope. There are security implications to doing this anyway..this would partly defeat the protection afforded by OTP schemes. What you need is to teach your users how to calculate password challenge responses themselves, either using one of the FreeBSD tools or an online javascript calculator (these exist, but I don't have a URL handy). This is as simple as pasting the OTP challenge into a website and entering their passphrase, then pasting the response in. Providing your users with a list of the next n passwords they will need to use is only a convenience, they can do it on demand when presented with the login challenge, given an available OTP calculator. Kris --=20 NOTE: To fetch an updated copy of my GPG key which has not expired, finger kris@FreeBSD.org --FsscpQKzF/jJk6ya 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 iD8DBQE6bmDXWry0BWjoQKURAtHvAKCbuniVy+dDOJ49tGQoY+TLNosJrgCfQS2j doQfwrb+8uJaLJskgF5OKag= =hg/k -----END PGP SIGNATURE----- --FsscpQKzF/jJk6ya-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 23 21:11:57 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 C4BD437B400; Tue, 23 Jan 2001 21:11:34 -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 PAA04760; Wed, 24 Jan 2001 15:41:23 +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: <20010123205759.C26378@citusc17.usc.edu> Date: Wed, 24 Jan 2001 15:41:23 +1030 (CST) From: "Daniel O'Connor" To: Kris Kennaway Subject: Re: Non-sequential one-time passwords? Cc: freebsd-stable@FreeBSD.ORG, Shawn Barnhart Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 24-Jan-01 Kris Kennaway wrote: > What you need is to teach your users how to calculate password > challenge responses themselves, either using one of the FreeBSD tools > or an online javascript calculator (these exist, but I don't have a > URL handy). This is as simple as pasting the OTP challenge into a > website and entering their passphrase, then pasting the response in. You can get a S/Key generater for the Palm Pilot at http://www.dimensional.com/~bgiles/pilot/skey/ Works fine for me. Here is a Java one - http://www.cs.umd.edu/~harry/jotp/ Couldn't find a JS one though :) --- 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 23 21:15:56 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 B5C5A37B400 for ; Tue, 23 Jan 2001 21:15:38 -0800 (PST) Received: from localhost (darren@localhost) by tzeench.dhs.org (8.11.1/8.11.1) with ESMTP id f0O5FiQ06478 for ; Tue, 23 Jan 2001 22:15:44 -0700 (MST) (envelope-from darren@tzeench.dhs.org) Date: Tue, 23 Jan 2001 22:15:43 -0700 (MST) From: Darren To: Subject: hard drive crashes related to maxtor 60 gigs. 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 at first thinking the problem was related to software, I posted to this mailing list getting lots of replies back. It appears to me as though the maxtor 60 gig harddrive is defective, it likes to overheat. I am running a 15 gig drive (maxtor) very well on udma66 mode. I have kept the ide cables the same and turned my 60 gig down to pio4 mode. I don't get any errors and nothing seems to be overheating. -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 23 21:17: 4 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 6AD5737B400 for ; Tue, 23 Jan 2001 21:16:46 -0800 (PST) Received: from [203.164.12.28] by www.quake.com.au (NTMail 4.30.0012/AH9370.63.d1acf55c) with ESMTP id ynvsaaaa for ; Wed, 24 Jan 2001 16:25:21 +1100 Message-ID: <3A6E6543.B5D9A8E3@quake.com.au> Date: Wed, 24 Jan 2001 16:16:51 +1100 From: Kal Torak X-Mailer: Mozilla 4.73 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Pete French Cc: stable@freebsd.org Subject: Re: anybody seen this one ? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Pete French wrote: > > o.k., this is *very* odd. > > I am using the 4.2 rrelease Cd to install onto a machine. This machine > installs 3.4 fine and is currently running it quite happily. > > Under 3.3 I boot from two floppies, get the screen which allows me to > configure the kernel, then it boots into the nice blue screen from > sysinstall. All well and good. > > Under 4.2 I boot from the two floppies and the screen to allow kernel > configs never appears - the system runs saright into the boot, starts up > sysinstall... and at this point appears to freeze. Or at least I can get no > response from the keyboard ! > > Anybody seen anything liek this, or have any suggestions as to how to get > round it ? I've taken as much of the hardware out as I feasibly can, and > an identical motherboard appears to work fine.. Hmmmm... Yes I have seen this happen... Its not that the computer is frozen its that the keyboard driver cant load because of a conflict, strange I know, but if you look at the messages that scroll past when its loading into sysinstall you will see the keyboard driver isnt loading... You can fix this by tweaking some bios settings... I cant remember exactly what I changed to fix that, but try setting PnP OS to NO and reset the ESCD data... If that doesnt work disable things you dont need, like USB and the like... I have had problems twice with USB causing a conflict with something else on different systems... Good Luck, Hope this helps! Kal. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 23 21:27:59 2001 Delivered-To: freebsd-stable@freebsd.org Received: from aeon.invision.net (aeon.invision.net [206.112.34.19]) by hub.freebsd.org (Postfix) with ESMTP id D622637B402; Tue, 23 Jan 2001 21:27:37 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by aeon.invision.net (8.11.1/8.11.0) with ESMTP id f0O5Raj55755; Wed, 24 Jan 2001 00:27:36 -0500 (EST) (envelope-from martini@invision.net) Date: Wed, 24 Jan 2001 00:27:35 -0500 (EST) From: Matt Martini Reply-To: "Matthew E. Martini" To: Mike Smith Cc: freebsd-stable@FreeBSD.ORG Subject: Re: invalid partition In-Reply-To: <200101240139.f0O1dXS06434@mass.dis.org> 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 -----BEGIN PGP SIGNED MESSAGE----- Mike, Thanks for the reply. When I built the system I did not "set bootable" during the config of the raid array. I don't know why it is tring to boot off that first. Could you pls. point me in the right direction so I can do this. There doesn't seem to be an option in the twe config screens, nor could I find one in the scsi bios setup. Should I be playing with the boot loader? Pls. point me towards some documentation to get me started. Thanks, Matt On Tue, 23 Jan 2001, Mike Smith wrote: > > > > I recently added a 3ware ATA Raid card to a 4.2-R box. Now I get > > "invalid partition" messages on bootup. > > > > Does anyone know how to fix this? > > Reconfigure your system so that it's not trying to boot from the 3ware > array. > __________________________ http://www.invision.net/ _______________________ Matthew E. Martini, PE InVision.com, Inc. (631) 543-1000 x104 Chief Technology Officer matt@invision.net (631) 864-8896 Fax _______________________________________________________________________pgp_ -----BEGIN PGP SIGNATURE----- Version: PGP 6.5.1i iQEVAwUBOm5nx2tXn16/JS7ZAQEI1AgAidjgVYSptRdJzRHelM8zTOEtWRt/9Pvj tNacFPyQp6BG1TJGhuzk21r4NSX1cQOJMMovDOim8eV7Tx/VlQ/mg3aG6TsXJe0u FB7Wf1irQ3l9t/UEmH2JLDwyEohdfuVKhU1roZH3018JGArFImgtSEZvXxXNOly5 Cfr4oRqmTTvuR6ULOe8fEkFkimwNfMwMjzq62I73g+pcQqhJcByJUe9PRWSVyyjX /5ui55cH1bTDTMUq0Nhc8gjwrPdA2FdkZGeoTBNiNd+nkxepfunL0IhYe9j5AcRu EKZ1beA3Vjx3isQ523wEnHQGZHqhUm8uT/OioCBNW3M7NrUGUL/WtQ== =B1Ik -----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 23 21:31: 2 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 C05D637B401 for ; Tue, 23 Jan 2001 21:30:41 -0800 (PST) Received: (from smtpd@localhost) by oberon.tpgi.com.au (8.8.7/8.8.7) id QAA21720; Wed, 24 Jan 2001 16:30:32 +1100 Received: from buffy.tpgi.com.au(203.12.160.34) via SMTP by oberon.tpgi.com.au, id smtpda21191; Wed Jan 24 16:29:34 2001 Received: (from smtpd@localhost) by buffy.tpgi.com.au (8.9.3/8.9.3) id QAA29576; Wed, 24 Jan 2001 16:29:27 +1100 Received: from tar-56k-196.tpgi.com.au(203.26.26.196), claiming to be "tpgi.com.au" via SMTP by buffy.tpgi.com.au, id smtpdMfOKjj; Wed Jan 24 16:28:36 2001 Message-ID: <3A6E67CD.3DCF8040@tpgi.com.au> Date: Wed, 24 Jan 2001 16:27:41 +1100 From: eirvine X-Mailer: Mozilla 4.6 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: "David W. Chapman Jr." Cc: "Geoffrey Crompton (RMIT Guest)" , freebsd-stable@FreeBSD.ORG Subject: Re: getting Creative Vibra 128 PCI running References: <20010124091523.A7087@gecko.eric.net.au> <01bf01c0858a$be2d6140$931576d8@inethouston.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Me too. I've been tracking stable since 4.0 There was a period of a few months (?) when it started working but now it fails again. Eddie. "David W. Chapman Jr." wrote: > > The last time I ran 4.2-stable it seemed to work fine. Can't vouch for 4.1 > or -stable though because I am running -current, but it did work for me > while I was using stable. > ----- Original Message ----- > From: "Geoffrey Crompton (RMIT Guest)" > To: > Sent: Tuesday, January 23, 2001 4:15 PM > Subject: getting Creative Vibra 128 PCI running > > > I've been having problems getting freebsd 4.1 recognizing my sound card. > > The card is: > > > > Creative Vibra 128 PCI (compatible with Sound Blaster PCI) > > Chips: CT5880-DCQ and CT4810 > > Product code: CLVIBPCI128 > > > > > > In the config file for the kernel I have enabled pcm: > > # Sound card support > > device pcm # for sound card > > #device sbc # for Creative Sound Blaster > > > > but the dmesg for the pcm device says: > > > > pcm0: at device 9.0 on pci2 > > pcm0: unable to map register space > > device_probe_and_attach: pcm0 attach returned 6 > > > > Doing sh MAKEDEV /dev/snd0 after it has booted (with that dmesg) appears > > to run without any errors, but > > cat /dev/sndstat reports > > cat: sndstat: Device not configured > > (Which isn't that surprising considering the dmesg errors) > > > > Has anyone had any luck getting this sound working? Have I done > > something obviously wrong? > > > > Thanks > > Geoff Crompton > > > > > > 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 23 21:55:47 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail1.rdc2.bc.home.com (mail1.rdc2.bc.home.com [24.2.10.84]) by hub.freebsd.org (Postfix) with ESMTP id EACE937B400 for ; Tue, 23 Jan 2001 21:55:25 -0800 (PST) Received: from ardbeg ([24.77.8.34]) by mail1.rdc2.bc.home.com (InterMail vM.4.01.03.00 201-229-121) with SMTP id <20010124055524.BFYD25505.mail1.rdc2.bc.home.com@ardbeg> for ; Tue, 23 Jan 2001 21:55:24 -0800 From: Gord Broom Reply-To: Gordon.Broom@home.com To: Subject: Re: make buildworld fails Date: Tue, 23 Jan 2001 21:35:12 -0800 X-Mailer: KMail [version 1.0.28] Content-Type: Multipart/Mixed; charset="ISO-8859-1"; boundary="Boundary-=_WfAZyzAZOHsNGHcxSfUBSnsNWfUJ" References: In-Reply-To: MIME-Version: 1.0 Message-Id: <01012321552400.75594@ardbeg> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --Boundary-=_WfAZyzAZOHsNGHcxSfUBSnsNWfUJ Content-Type: text/plain Content-Transfer-Encoding: 7bit On Tue, 23 Jan 2001, Lukas Ertl wrote: > On Tue, 23 Jan 2001, Simon Loader wrote: > > > "make buildworld" constantly fails on my 4.2-STABLE machine. I cvsup'ed > freshly, but the problem persists. Here is the error log: > I haven't had a clean "make buildworld" yet since I upgraded to 4.2 (4.2-STABLE/ 250MB / 530 MB swap), and it's been dying two hours in or so (script(1) is handy here), I've attached an abridged error log below. executive summary [...] ===> usr.sbin/setkey [...] cc -O -pipe -g -I/usr/src/usr.sbin/setkey/../../lib/libipsec -I/usr/src/usr.sbin/setkey/../../lib/libipsec -I/usr/src/usr.sbin/setkey/../../sys/netkey -DIPSEC_DEBUG -DINET6 -DYY_NO_UNPUT -I. -I/usr/obj/usr/src/i386/usr/include -c parse.c cc -O -pipe -g -I/usr/src/usr.sbin/setkey/../../lib/libipsec -I/usr/src/usr.sbin/setkey/../../lib/libipsec -I/usr/src/usr.sbin/setkey/../../sys/netkey -DIPSEC_DEBUG -DINET6 -DYY_NO_UNPUT -I. -I/usr/obj/usr/src/i386/usr/include -c token.c /usr/src/usr.sbin/setkey/token.l: In function `yylex': /usr/src/usr.sbin/setkey/token.l:122: `ADD' undeclared (first use in this function) [similarly for 'DELETE', 'FLUSH', 'DUMP', etc.] Silly me assumed that something called "STABLE" would actually compile :-) Anyone had any success in cvsup / make buildworld? I certainly haven't (oh, my cvsupfile's attached as well). I have no idea what state my system is in now, because I ended up (after an unsuccesful but naively-trusting "make world") reinstalling the "bin" distribution from the CD. This was after discovering that my kernel/rc.firewall/ipfw configuration was mismatched (but boy was I secure :-), and attempting to follow the instructions in /usr/src/UPDATING. Sigh. Not a happy camper. Gord Broom --Boundary-=_WfAZyzAZOHsNGHcxSfUBSnsNWfUJ Content-Type: text/plain; name="error-log" Content-Transfer-Encoding: 8bit Content-Disposition: attachment; filename="error-log" Script started on Tue Jan 23 19:25:08 2001 ardbeg# make buildworld [... lots and lots of stuff deleted (available on request) ...] ===> usr.sbin/setkey cc -O -pipe -g -I/usr/src/usr.sbin/setkey/../../lib/libipsec -I/usr/src/usr.sbin/setkey/../../lib/libipsec -I/usr/src/usr.sbin/setkey/../../sys/netkey -DIPSEC_DEBUG -DINET6 -DYY_NO_UNPUT -I. -I/usr/obj/usr/src/i386/usr/include -c /usr/src/usr.sbin/setkey/setkey.c cc -O -pipe -g -I/usr/src/usr.sbin/setkey/../../lib/libipsec -I/usr/src/usr.sbin/setkey/../../lib/libipsec -I/usr/src/usr.sbin/setkey/../../sys/netkey -DIPSEC_DEBUG -DINET6 -DYY_NO_UNPUT -I. -I/usr/obj/usr/src/i386/usr/include -c parse.c cc -O -pipe -g -I/usr/src/usr.sbin/setkey/../../lib/libipsec -I/usr/src/usr.sbin/setkey/../../lib/libipsec -I/usr/src/usr.sbin/setkey/../../sys/netkey -DIPSEC_DEBUG -DINET6 -DYY_NO_UNPUT -I. -I/usr/obj/usr/src/i386/usr/include -c token.c /usr/src/usr.sbin/setkey/token.l: In function `yylex': /usr/src/usr.sbin/setkey/token.l:122: `ADD' undeclared (first use in this function) /usr/src/usr.sbin/setkey/token.l:122: (Each undeclared identifier is reported only once /usr/src/usr.sbin/setkey/token.l:122: for each function it appears in.) /usr/src/usr.sbin/setkey/token.l:123: `DELETE' undeclared (first use in this function) /usr/src/usr.sbin/setkey/token.l:124: `GET' undeclared (first use in this function) /usr/src/usr.sbin/setkey/token.l:125: `FLUSH' undeclared (first use in this function) /usr/src/usr.sbin/setkey/token.l:126: `DUMP' undeclared (first use in this function) /usr/src/usr.sbin/setkey/token.l:129: `SPDADD' undeclared (first use in this function) /usr/src/usr.sbin/setkey/token.l:130: `SPDDELETE' undeclared (first use in this function) /usr/src/usr.sbin/setkey/token.l:131: `SPDDUMP' undeclared (first use in this function) /usr/src/usr.sbin/setkey/token.l:132: `SPDFLUSH' undeclared (first use in this function) /usr/src/usr.sbin/setkey/token.l:133: `F_POLICY' undeclared (first use in this function) /usr/src/usr.sbin/setkey/token.l:145: `yylval' undeclared (first use in this function) /usr/src/usr.sbin/setkey/token.l:148: `PL_REQUESTS' undeclared (first use in this function) /usr/src/usr.sbin/setkey/token.l:150: `EOT' undeclared (first use in this function) /usr/src/usr.sbin/setkey/token.l:153: `PR_AH' undeclared (first use in this function) /usr/src/usr.sbin/setkey/token.l:154: `PR_ESP' undeclared (first use in this function) /usr/src/usr.sbin/setkey/token.l:157: `PR_IPCOMP' undeclared (first use in this function) /usr/src/usr.sbin/setkey/token.l:160: `F_AUTH' undeclared (first use in this function) /usr/src/usr.sbin/setkey/token.l:161: `ALG_AUTH' undeclared (first use in this function) /usr/src/usr.sbin/setkey/token.l:168: `F_ENC' undeclared (first use in this function) /usr/src/usr.sbin/setkey/token.l:169: `ALG_ENC' undeclared (first use in this function) /usr/src/usr.sbin/setkey/token.l:175: `ALG_ENC_DESDERIV' undeclared (first use in this function) /usr/src/usr.sbin/setkey/token.l:176: `ALG_ENC_DES32IV' undeclared (first use in this function) /usr/src/usr.sbin/setkey/token.l:179: `F_COMP' undeclared (first use in this function) /usr/src/usr.sbin/setkey/token.l:180: `ALG_COMP' undeclared (first use in this function) /usr/src/usr.sbin/setkey/token.l:183: `F_RAWCPI' undeclared (first use in this function) /usr/src/usr.sbin/setkey/token.l:186: `F_MODE' undeclared (first use in this function) /usr/src/usr.sbin/setkey/token.l:189: `F_REQID' undeclared (first use in this function) /usr/src/usr.sbin/setkey/token.l:190: `F_EXT' undeclared (first use in this function) /usr/src/usr.sbin/setkey/token.l:191: `EXTENSION' undeclared (first use in this function) /usr/src/usr.sbin/setkey/token.l:194: `NOCYCLICSEQ' undeclared (first use in this function) /usr/src/usr.sbin/setkey/token.l:195: `F_REPLAY' undeclared (first use in this function) /usr/src/usr.sbin/setkey/token.l:196: `F_LIFETIME_HARD' undeclared (first use in this function) /usr/src/usr.sbin/setkey/token.l:197: `F_LIFETIME_SOFT' undeclared (first use in this function) /usr/src/usr.sbin/setkey/token.l:201: `UP_PROTO' undeclared (first use in this function) /usr/src/usr.sbin/setkey/token.l:219: `DECSTRING' undeclared (first use in this function) /usr/src/usr.sbin/setkey/token.l:228: `ADDRESS' undeclared (first use in this function) /usr/src/usr.sbin/setkey/token.l:235: `PREFIX' undeclared (first use in this function) /usr/src/usr.sbin/setkey/token.l:245: `PORT' undeclared (first use in this function) /usr/src/usr.sbin/setkey/token.l:250: `PORTANY' undeclared (first use in this function) /usr/src/usr.sbin/setkey/token.l:264: `HEXSTRING' undeclared (first use in this function) /usr/src/usr.sbin/setkey/token.l:276: `QUOTEDSTRING' undeclared (first use in this function) *** Error code 1 Stop in /usr/src/usr.sbin/setkey. *** Error code 1 Stop in /usr/src/usr.sbin. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. ardbeg# exit Script done on Tue Jan 23 21:34:21 2001 --Boundary-=_WfAZyzAZOHsNGHcxSfUBSnsNWfUJ Content-Type: text/plain; name="cvsupfile" Content-Transfer-Encoding: 8bit Content-Disposition: attachment; filename="cvsupfile" # $Id: //depot/users/gord/ardbeg/cvsupfile#2 $ *default host=cvsup.ca.FreeBSD.org *default base=/usr *default prefix=/usr *default release=cvs *default tag=RELENG_4 *default delete use-rel-suffix src-all src-crypto src-secure *default tag=. ports-all doc-all --Boundary-=_WfAZyzAZOHsNGHcxSfUBSnsNWfUJ-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 23 22: 3:13 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail2.rdc2.bc.home.com (mail2.rdc2.bc.home.com [24.2.10.85]) by hub.freebsd.org (Postfix) with ESMTP id 6FEF537B402 for ; Tue, 23 Jan 2001 22:02:55 -0800 (PST) Received: from ardbeg ([24.77.8.34]) by mail2.rdc2.bc.home.com (InterMail vM.4.01.03.00 201-229-121) with SMTP id <20010124060254.PDDP1774.mail2.rdc2.bc.home.com@ardbeg>; Tue, 23 Jan 2001 22:02:54 -0800 From: Gord Broom Reply-To: Gordon.Broom@home.com To: Kal Torak , Brad Tombaugh Subject: Re: Problems Making Ports Date: Tue, 23 Jan 2001 21:58:10 -0800 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain; charset="us-ascii" Cc: freebsd-stable@FreeBSD.ORG References: <3A6D2B4C.4F9382A3@qwest.net> <3A6D4AF3.69241B5E@quake.com.au> In-Reply-To: <3A6D4AF3.69241B5E@quake.com.au> MIME-Version: 1.0 Message-Id: <01012322025301.75594@ardbeg> Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 23 Jan 2001, Kal Torak wrote: > Brad Tombaugh wrote: > >=20 > > Several people, including me, have posted articles to > > comp.unix.bsd.frebsd.misc regarding problems making ports after updat= ing > > to RELENG_4 (4.2-STABLE). > >=20 > > The first symptom that I saw after "making world" was that when I > > attempted to "make" or "make install" any of several ports I got an > > error: > >=20 > > orion# cd /usr/ports/textproc/docproj > > orion# make > > Error: your port uses an old layout. Please update it to > > match this bsd.port.mk. > >=20 > > checking /urs/ports/Mk/bsd.port.mk shows several instances of this or > > similar messages, generally near a declaration for "pre-everything::" > >=20 > If you had read /usr/src/UPDATING then you would of seen that after > an upgrade to 4.2 you are required to cvsup your whole ports tree since > changes were made to the base port structure... > Reading the UPDATING file properly solves almost all upgrading problems= =2E.. >=20 Also, you may have to delete empty directories in each of the individual = ports (which cvsup left behind, as I've seen CVS do), which confuse both bsd.po= rt.mk and users. I thought I had written down which directories they were, but hunt around= in bsd.ports.mk for the specific error it gives you, and it'll point you the= re. I know one of them was 'patches/', I can't remember the second. Gord. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 23 22:18: 5 2001 Delivered-To: freebsd-stable@freebsd.org Received: from pop3.ids.net (pop3.ids.net [155.212.1.107]) by hub.freebsd.org (Postfix) with ESMTP id 6493837B401 for ; Tue, 23 Jan 2001 22:17:47 -0800 (PST) Received: from ids.net (dialup120f.egr-ri.ids.net [155.212.222.120]) by pop3.ids.net (8.10.1/8.10.1) with ESMTP id f0O6Hh923111; Wed, 24 Jan 2001 01:17:43 -0500 (EST) Message-ID: <3A6E7353.4C441CD5@ids.net> Date: Wed, 24 Jan 2001 01:16:51 -0500 From: "Christopher M. Giordano" Reply-To: CGiordano@ids.net X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: John Polstra Cc: stable@freebsd.org Subject: Re: preventing cvsup from replacing /usr/ports symlink? References: <200101202028.f0KKSUr80758@saturn.home.ben.com> <20010121021117.A2300@snark.ptc.spbu.ru> <200101210047.f0L0lBq15592@vashon.polstra.com> <3A6C5E6C.3E84EAC0@ids.net> <200101232308.f0NN8QT25018@vashon.polstra.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Polstra wrote: > > True, but it does help. Thanks to you and the others who sent > information about this. > > Questions for those who have seen this happen: > > 1. You're using checkout mode, right? Yes. > 2. Are you using "-s" on the cvsup command line? No, because cvsup(1)'s man page says "the results are undefined" if files have been locally modified and -s is used. I do make minor local mods, and that "undefined" part doesn't give me a good feeling, regardless of how appealing a reduction in disk activity is. > Finally, you can avoid any chance of this happening by making sure > that CVSup's "prefix" setting points to the real parent directory of > your ports tree -- not to a symlink that points there. Here's an Ahhh, Bach. I am definitely using the symlink; I'll try it with the actual parent directory. Thanks. Chris Giordano CGiordano@ids.net -- All cats are grey in the dark. -- Benjamin Franklin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 23 22:56: 1 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id 671C337B401 for ; Tue, 23 Jan 2001 22:55:40 -0800 (PST) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.1/8.11.1) with ESMTP id f0O7B4S08821; Tue, 23 Jan 2001 23:11:04 -0800 (PST) (envelope-from msmith@mass.dis.org) Message-Id: <200101240711.f0O7B4S08821@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Matthew E. Martini" Cc: freebsd-stable@FreeBSD.ORG Subject: Re: invalid partition In-reply-to: Your message of "Wed, 24 Jan 2001 00:27:35 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 23 Jan 2001 23:11:04 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Boot ordering is typically controlled by your system and/or peripheral BIOS config. Since I have no idea what your system BIOS is like, I can't really help you a lot here. You should check the Adaptec BIOS setup to see if the version you have allows you to tweak it's boot ordering position. Note also that a BIOS upgrade for your board and/or the Adaptec controller may help things out. Unfortunately, I can't really offer much more assistance here, other than to tell you the source of your woes. If you had an 'a' partition on the first drive on the 3ware controller, you could put 1:da(0,a)/boot/loader in /boot.config on that partition, which would be a functional but irritating workaround. > -----BEGIN PGP SIGNED MESSAGE----- > > Mike, > > Thanks for the reply. When I built the system I did not "set > bootable" during the config of the raid array. I don't know why it is tring > to boot off that first. > > Could you pls. point me in the right direction so I can do this. There > doesn't seem to be an option in the twe config screens, nor could I find one > in the scsi bios setup. Should I be playing with the boot loader? > > Pls. point me towards some documentation to get me started. > > Thanks, > > Matt > > > On Tue, 23 Jan 2001, Mike Smith wrote: > > > > > > > I recently added a 3ware ATA Raid card to a 4.2-R box. Now I get > > > "invalid partition" messages on bootup. > > > > > > Does anyone know how to fix this? > > > > Reconfigure your system so that it's not trying to boot from the 3ware > > array. > > > __________________________ http://www.invision.net/ _______________________ > > Matthew E. Martini, PE InVision.com, Inc. (631) 543-1000 x104 > Chief Technology Officer matt@invision.net (631) 864-8896 Fax > _______________________________________________________________________pgp_ > > > -----BEGIN PGP SIGNATURE----- > Version: PGP 6.5.1i > > iQEVAwUBOm5nx2tXn16/JS7ZAQEI1AgAidjgVYSptRdJzRHelM8zTOEtWRt/9Pvj > tNacFPyQp6BG1TJGhuzk21r4NSX1cQOJMMovDOim8eV7Tx/VlQ/mg3aG6TsXJe0u > FB7Wf1irQ3l9t/UEmH2JLDwyEohdfuVKhU1roZH3018JGArFImgtSEZvXxXNOly5 > Cfr4oRqmTTvuR6ULOe8fEkFkimwNfMwMjzq62I73g+pcQqhJcByJUe9PRWSVyyjX > /5ui55cH1bTDTMUq0Nhc8gjwrPdA2FdkZGeoTBNiNd+nkxepfunL0IhYe9j5AcRu > EKZ1beA3Vjx3isQ523wEnHQGZHqhUm8uT/OioCBNW3M7NrUGUL/WtQ== > =B1Ik > -----END PGP SIGNATURE----- > > -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 23 23:10: 9 2001 Delivered-To: freebsd-stable@freebsd.org Received: from cs.huji.ac.il (cs.huji.ac.il [132.65.16.10]) by hub.freebsd.org (Postfix) with ESMTP id 7B81A37B69F; Tue, 23 Jan 2001 23:09:51 -0800 (PST) Received: from sexta.cs.huji.ac.il ([132.65.16.13] ident=danny) by cs.huji.ac.il with esmtp (Exim 3.20 #1) id 14LK3m-0004So-00; Wed, 24 Jan 2001 09:09:38 +0200 X-Mailer: exmh version 2.2 06/23/2000 with nmh-0.24 To: Mike Smith Cc: Alfred Perlstein , stable@freebsd.org Subject: Re: Dell PERC 3 support? In-reply-to: Your message of Tue, 23 Jan 2001 10:18:16 -0800 . Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 24 Jan 2001 09:09:38 +0200 From: Danny Braniss Message-Id: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200101231818.f0NIIGS00820@mass.dis.org>you write: [...] }All of the RAID adapters we support are bootable. The #1 cause of }booting problems is a geometry mismatch. The integrated RAID controller }in the 2450 is supported by 'aac', which has three geometry options: } }'2GB' mode: */255/63 }'1GB' mode: */128/32 }standard: */64/32 } }The driver picks this setting up from the controller; if there is already }data on the disks, sysinstall may be confused into using a different }geometry. the problem i have is that after installing a boot/mbr/dd or whatever, the BIOS gets stuck, it never got to the boot part. danny To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 23 23:20:16 2001 Delivered-To: freebsd-stable@freebsd.org Received: from dnvrpop3.dnvr.uswest.net (dnvrpop3.dnvr.uswest.net [206.196.128.5]) by hub.freebsd.org (Postfix) with SMTP id 1B5E937B69F for ; Tue, 23 Jan 2001 23:19:55 -0800 (PST) Received: (qmail 7419 invoked by uid 0); 24 Jan 2001 07:19:53 -0000 Received: from dnvr-dsl-gw7-f-250.dnvr.uswest.net (HELO qwest.net) (63.227.58.250) by dnvrpop3.dnvr.uswest.net with SMTP; 24 Jan 2001 07:19:53 -0000 Date: Wed, 24 Jan 2001 00:20:10 -0700 Message-ID: <3A6E822A.9801D16@qwest.net> From: "Brad Tombaugh" To: freebsd-stable@FreeBSD.ORG Cc: Gordon.Broom@home.com, "Kal Torak" , rtoren@bronzedragon.net, gfoster@gfoster.com X-Mailer: Mozilla 4.75 [en] (X11; U; FreeBSD 4.2-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 Subject: Re: Problems Making Ports References: <3A6D2B4C.4F9382A3@qwest.net> <3A6D4AF3.69241B5E@quake.com.au> <01012322025301.75594@ardbeg> Content-Type: multipart/alternative; boundary="------------5368AA1CBC5514256AF49FCB" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --------------5368AA1CBC5514256AF49FCB Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Thanks to all who responded... I had cvsup'd the ports tree, but this did not update everything. Glen Foster's suggestion to delete the ports tree and cvsup again did the trick! Glen Foster wrote: > Some time last fall the ports tree hierarchy changed eliminating the > subdirectories "pkg" and "patches" in each port directory. This was > announced on the list as a "heads up" at the time and has been covered > several times since then. The presence of these directories generates > the "old layout" message. Do this: > > # cd /usr/ports > # find . -name CVS | xargs rm -rf > # find . -name pkg | xargs rm -rf > # find . -name patches | xargs rm -rf > # make update > > Of course, your /etc/make.conf has to be set correctly for the last to > work. > > Alternatively, delete your entire ports tree and re-cvsup. This is > cleaner but will take longer, remove any local changes, and require > re-fetching distfiles on subsequent port rebuilds.Gord Broom wrote: > On Tue, 23 Jan 2001, Kal Torak wrote: > > Brad Tombaugh wrote: > > > > > > Several people, including me, have posted articles to > > > comp.unix.bsd.frebsd.misc regarding problems making ports after updating > > > to RELENG_4 (4.2-STABLE). > > > > > > The first symptom that I saw after "making world" was that when I > > > attempted to "make" or "make install" any of several ports I got an > > > error: > > > > > > orion# cd /usr/ports/textproc/docproj > > > orion# make > > > Error: your port uses an old layout. Please update it to > > > match this bsd.port.mk. > > > > > > checking /urs/ports/Mk/bsd.port.mk shows several instances of this or > > > similar messages, generally near a declaration for "pre-everything::" > > > > > > If you had read /usr/src/UPDATING then you would of seen that after > > an upgrade to 4.2 you are required to cvsup your whole ports tree since > > changes were made to the base port structure... > > Reading the UPDATING file properly solves almost all upgrading problems... > > > > Also, you may have to delete empty directories in each of the individual ports > (which cvsup left behind, as I've seen CVS do), which confuse both bsd.port.mk > and users. > > I thought I had written down which directories they were, but hunt around in > bsd.ports.mk for the specific error it gives you, and it'll point you there. I > know one of them was 'patches/', I can't remember the second. > > Gord. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- Brad Tombaugh mailto:btombau@qwest.net http://www.users.qwest.net/~btombau --------------5368AA1CBC5514256AF49FCB Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit Thanks to all who responded...  I had cvsup'd the ports tree, but this did not update everything.  Glen Foster's suggestion to delete the ports tree and cvsup again did the trick!

Glen Foster wrote:

Some time last fall the ports tree hierarchy changed eliminating the
subdirectories "pkg" and "patches" in each port directory.  This was
announced on the list as a "heads up" at the time and has been covered
several times since then.  The presence of these directories generates
the "old layout" message.  Do this:

# cd /usr/ports
# find . -name CVS | xargs rm -rf
# find . -name pkg | xargs rm -rf
# find . -name patches | xargs rm -rf
# make update

Of course, your /etc/make.conf has to be set correctly for the last to
work.

Alternatively, delete your entire ports tree and re-cvsup.  This is
cleaner but will take longer, remove any local changes, and require
re-fetching distfiles on subsequent port rebuilds.Gord Broom wrote:

On Tue, 23 Jan 2001, Kal Torak wrote:
> Brad Tombaugh wrote:
> >
> > Several people, including me, have posted articles to
> > comp.unix.bsd.frebsd.misc regarding problems making ports after updating
> > to RELENG_4 (4.2-STABLE).
> >
> > The first symptom that I saw after "making world" was that when I
> > attempted to "make" or "make install" any of several ports I got an
> > error:
> >
> >      orion# cd /usr/ports/textproc/docproj
> >      orion# make
> >      Error: your port uses an old layout.  Please update it to
> >      match this bsd.port.mk.
> >
> > checking /urs/ports/Mk/bsd.port.mk shows several instances of this or
> > similar messages, generally near a declaration for "pre-everything::"
> >

> If you had read /usr/src/UPDATING then you would of seen that after
> an upgrade to 4.2 you are required to cvsup your whole ports tree since
> changes were made to the base port structure...
> Reading the UPDATING file properly solves almost all upgrading problems...
>

Also, you may have to delete empty directories in each of the individual ports
(which cvsup left behind, as I've seen CVS do), which confuse both bsd.port.mk
and users.

I thought I had written down which directories they were, but hunt around in
bsd.ports.mk for the specific error it gives you, and it'll point you there.  I
know one of them was 'patches/', I can't remember the second.

Gord.

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

-- 
Brad Tombaugh
mailto:btombau@qwest.net
http://www.users.qwest.net/~btombau
  --------------5368AA1CBC5514256AF49FCB-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 23 23:21:19 2001 Delivered-To: freebsd-stable@freebsd.org Received: from relay.ultimanet.com (relay.ultimanet.com [205.179.129.1]) by hub.freebsd.org (Postfix) with ESMTP id 04ECE37B69F for ; Tue, 23 Jan 2001 23:21:01 -0800 (PST) Received: from Cloudfactory.ORG (cloudfactory.org [205.179.129.18]) by relay.ultimanet.com (8.9.3/8.9.3) with ESMTP id AAA00508 for ; Wed, 24 Jan 2001 00:00:12 -0800 Message-Id: <200101240800.AAA00508@relay.ultimanet.com> To: freebsd-stable@freebsd.org Organization: Cloud Factory Collective X-Mailer: nmh 1.0.4 + mh-e Subject: system freeze, softupdates? Date: Tue, 23 Jan 2001 23:21:00 -0800 From: Randy Primeaux Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Issue: I had a system freeze this week, and upon boot the next day, found: /dev/ad4s1f: CANNOT READ: BLK 16 /dev/ad4s1f: NOT LABELED AS A BSD FILE SYSTEM (unused) /dev/ad4s1f is /usr including /usr/home Questions/concerns: I'd like to pin down the cause of the freeze. I'd like to contribute data regarding the freeze, if it will benefit future software development. I plan to preserve the DTLA disk, as I'd like to recover the data if possible, but I'm not sure how to recover. Can you offer any guidance or url's regarding data recovery from that filesystem? I plan to build a new desktop system on same (new) hardware, with a new pair of disks using software raid-1. I've been following the RAID-5 discussion on this list, but I'm still back at January 6th, and trying to catch up, and not yet knowledgeable regarding RAID. I'm currently reading through Greg Lehey's vinum docs. Is software or hardware RAID preferred? Details: As of the first week of January, I was running the following: Asus P5A AMD K6-III/400 128MB PC-100 IBM DTLA 307030 pci audio cd-rom running 4-STABLE from Dec 20, 2000. Some time between the 1st and the 11th, I enabled softupdates on /usr On the 15th, I bought: Asus A7V AMD Athlon Thunderbird 800 128MB PC-133 Cooler Master fan I completed the upgrade on Friday the 19th, after recompiling the kernel with I686_CPU support, and adjusting /etc/fstab . I do not overclock. I log to my fileserver, and logs from that evening show: Jan 19 22:01:45 daemon sudo: randy : TTY=ttyp3 ; PWD=/usr/ports/graphics/xanim ; USER=root ; COMMAND=/usr/bin/make install Jan 19 22:56:29 daemon sudo: randy : TTY=ttyp3 ; PWD=/usr/ports/graphics/xanim ; USER=root ; COMMAND=/usr/bin/make clean Jan 19 22:57:22 daemon sudo: randy : TTY=ttyp3 ; PWD=/usr/ports ; USER=root ; COMMAND=/usr/bin/make update Jan 19 22:57:35 daemon /kernel: dc0: TX underrun -- increasing TX threshold Jan 19 22:57:57 daemon last message repeated 2 times Jan 19 22:57:58 daemon /kernel: dc0: TX underrun -- using store and forward mode I think the system froze at this point. It was the last log message from "daemon". The desktop and mouse froze, and I could not ssh to daemon from another system on my network. I was running setiathome, tkseti, tkined, `make update` in ports, xwindows, netscape, xmms, ntpd, healthd, mrtg, gnome-terminals, and probably other stuff as well. I believe I had about 8GB free on /usr . In my logs, I found a previous TX underrun: Jan 11 03:03:04 daemon /kernel: dc0: TX underrun -- increasing TX threshold I can submit dmesg output upon request, and I'll be recovering /var/log/messages later this week. -- Randy Primeaux randy@cloudfactory.org FreeBSD - the power to serve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 23 23:38:51 2001 Delivered-To: freebsd-stable@freebsd.org Received: from lucifer.ninth-circle.org (lucifer.bart.nl [194.158.168.74]) by hub.freebsd.org (Postfix) with ESMTP id 6676E37B401 for ; Tue, 23 Jan 2001 23:38:34 -0800 (PST) Received: (from asmodai@localhost) by lucifer.ninth-circle.org (8.11.1/8.11.0) id f0O7cUS74675; Wed, 24 Jan 2001 08:38:30 +0100 (CET) (envelope-from asmodai) Date: Wed, 24 Jan 2001 08:38:30 +0100 From: Jeroen Ruigrok van der Werven To: Gerald Pfeifer Cc: freebsd-stable@FreeBSD.ORG, "David O'Brien" Subject: Re: MFC: /etc/login.conf Message-ID: <20010124083830.A74377@lucifer.bart.nl> 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 pfeifer@dbai.tuwien.ac.at on Wed, Jan 24, 2001 at 12:27:08AM +0100 Organisation: VIA Net.Works The Netherlands Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -On [20010124 00:30], Gerald Pfeifer (pfeifer@dbai.tuwien.ac.at) wrote: >I'd like to suggest MCFing this, especially the "password_format=md5" bit: [snip] >See my earlier messages today on some background. This would have saved us >quite a bit of time, so at least it would be nice to see it in 4.3-RELEASE. You got it. [After I do my usual testing.] -- Jeroen Ruigrok van der Werven VIA Net.Works The Netherlands BSD: Technical excellence at its best Network- and systemadministrator D78D D0AD 244D 1D12 C9CA 7152 035C 1138 546A B867 Misery loves company... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 24 0:17:21 2001 Delivered-To: freebsd-stable@freebsd.org Received: from c014.sfo.cp.net (c014-h022.c014.sfo.cp.net [209.228.12.86]) by hub.freebsd.org (Postfix) with SMTP id 4642937B402 for ; Wed, 24 Jan 2001 00:17:03 -0800 (PST) Received: (cpmta 7047 invoked from network); 24 Jan 2001 00:17:02 -0800 Received: from d8c81e5f.dsl.flashcom.net (HELO quadrajet.flashcom.com) (216.200.30.95) by smtp.flashcom.net (209.228.12.86) with SMTP; 24 Jan 2001 00:17:02 -0800 X-Sent: 24 Jan 2001 08:17:02 GMT Received: (from guy@localhost) by quadrajet.flashcom.com (8.9.3/8.9.3) id AAA00765; Wed, 24 Jan 2001 00:17:01 -0800 (PST) (envelope-from gharris) Date: Wed, 24 Jan 2001 00:17:01 -0800 From: Guy Harris To: Matthias Andree Cc: Guy Harris , Linux NFS mailing list , FreeBSD Stable Subject: Re: [NFS] Incompatible: FreeBSD 4.2 client, Linux 2.2.18 nfsv3 server, read-only export Message-ID: <20010124001701.F344@quadrajet.flashcom.com> References: <20010123015612.H345@quadrajet.flashcom.com> <20010123162930.B5443@emma1.emma.line.org> <20010123111005.D344@quadrajet.flashcom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: ; from ma@dt.e-technik.uni-dortmund.de on Wed, Jan 24, 2001 at 04:34:36AM +0100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 24, 2001 at 04:34:36AM +0100, Matthias Andree wrote: > > (Perhaps it would've been better had the V3 protocol specified that > > either 0 or an NFS3ERR_xxx value be supplied for each of the permission > > bits checked, although that raises the question of whether any server > > would, say, allow read access and allow write access but disallow > > simultaneous read/write access.) > > No, the plan is simple. In the ACCESS call, the client asks if it has a > certain set of permissions, the sender weeds the actions the client may > not take at the moment of the ACCESS call, and returns a possibly > stripped-down set of allowed actions (which may then change > later). There's nothing wrong with this approach. The problem is that it only allows the client to know what it can or can't do; it doesn't let the client know, in more detail, *why* it can't do the things it's not allowed to do. For example, a UNIX "open()" call that calls an "access" vnode operation couldn't, if that file is mounted over NFS, find out that the open for writing is forbidden because the file system is read-only; even if that's the reason, the answer you get back is probably EACCES (that's what happens in the Solaris NFS, for example). BTW, I suspect the reason why FreeBSD is seeing a problem and Solaris isn't *might* be because FreeBSD is, at least if it's caching the results of ACCESS requests, sending over the wire an ACCESS request with all the bits turned on - the intent is, presumably, to find out as much as you can in one ACCESS call, even if you don't need all that information right now - which would provoke the Linux server to return an EROFS error rather than READ|EXECUTE|LOOKUP. If Solaris doesn't do that (I think Solaris *does* cache ACCESS replies, but it may, when it gets the reply back, cache only the answers to the questions it asked and, if another question is asked later and the answer to that question wasn't cached, ask that other question over the wire), then it may be that: on Solaris, an operation that doesn't require write permission causes an ACCESS request to go over the wire with none of MODIFY, EXTEND, or DELETE set, so Linux replies with a bitset of those operations that are actually allowed and, if the operation in question is one of them, the access vnode op returns "OK"; on FreeBSD, an operation that doesn't require write permission causes an ACCESS request to go over the wire with *all* bits set, so Linux replies with EROFS even though the operation is perfectly OK on a read-only file system, and the operation (e.g., opening a directory in order to list its contents) fails with EROFS. This means another workaround may be to set the "vfs.nfs.access_cache_timeout" sysctl value to 0, which turns off access reply caching. However, if I remember correctly something Brian Pawlowski mentioned a while ago, that can hurt NFS performance; I don't remember the details, but I seem to remember that access reply caching was being disabled on FreeBSD for some reason at some point (I also vaguely remember Mike Smith being involved in the discussion; Mike, if you're listening, do you remember any of this? Brian's out of town right now, and I'm at home rather than the office so I can't plow through my work mail archives). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 24 0:34:38 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 9AA7537B401 for ; Wed, 24 Jan 2001 00:34:16 -0800 (PST) Received: (qmail 31581 invoked by uid 0); 24 Jan 2001 08:34:15 -0000 Received: from unknown (HELO urx.com) (206.159.132.160) by mail.urx.com with SMTP; 24 Jan 2001 08:34:15 -0000 Message-ID: <3A6E9387.BB156E60@urx.com> Date: Wed, 24 Jan 2001 00:34:15 -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: Gordon.Broom@home.com Cc: freebsd-stable@FreeBSD.ORG Subject: Re: make buildworld fails References: <01012321552400.75594@ardbeg> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Gord Broom wrote: > > On Tue, 23 Jan 2001, Lukas Ertl wrote: > > On Tue, 23 Jan 2001, Simon Loader wrote: > > > > > > "make buildworld" constantly fails on my 4.2-STABLE machine. I cvsup'ed > > freshly, but the problem persists. Here is the error log: > > > > I haven't had a clean "make buildworld" yet since I upgraded to 4.2 (4.2-STABLE/ > 250MB / 530 MB swap), and it's been dying two hours in or so (script(1) is > handy here), I've attached an abridged error log below. Here are some recents builds by me FreeBSD topaz 4.2-STABLE FreeBSD 4.2-STABLE #0: Thu Jan 18 04:28:21 PST 2001 root@topaz:/usr/obj/usr/src/sys/TOPAZ i386 FreeBSD jade 4.2-STABLE FreeBSD 4.2-STABLE #0: Sun Jan 21 22:52:18 PST 2001 root@jade:/usr/obj/usr/src/sys/JADE i386 FreeBSD opal 4.2-STABLE FreeBSD 4.2-STABLE #0: Tue Jan 23 00:16:17 PST 2001 root@opal:/usr/obj/usr/src/sys/OPAL i386 FreeBSD topaz 4.2-STABLE FreeBSD 4.2-STABLE #0: Tue Jan 23 23:55:30 PST 2001 root@topaz:/usr/obj/usr/src/sys/TOPAZ i386 I think I would wipe out /usr/obj and start over. You might even consider a coupld of "make cleandir" in /usr/src. This time pay attention to the sequence in /usr/src/UPDATING. As you can see, it works. Kent > > executive summary > > [...] > ===> usr.sbin/setkey > [...] > cc -O -pipe -g -I/usr/src/usr.sbin/setkey/../../lib/libipsec -I/usr/src/usr.sbin/setkey/../../lib/libipsec -I/usr/src/usr.sbin/setkey/../../sys/netkey -DIPSEC_DEBUG -DINET6 -DYY_NO_UNPUT -I. -I/usr/obj/usr/src/i386/usr/include -c parse.c > cc -O -pipe -g -I/usr/src/usr.sbin/setkey/../../lib/libipsec -I/usr/src/usr.sbin/setkey/../../lib/libipsec -I/usr/src/usr.sbin/setkey/../../sys/netkey -DIPSEC_DEBUG -DINET6 -DYY_NO_UNPUT -I. -I/usr/obj/usr/src/i386/usr/include -c token.c > /usr/src/usr.sbin/setkey/token.l: In function `yylex': > /usr/src/usr.sbin/setkey/token.l:122: `ADD' undeclared (first use in this function) > [similarly for 'DELETE', 'FLUSH', 'DUMP', etc.] > > Silly me assumed that something called "STABLE" would actually compile :-) > > Anyone had any success in cvsup / make buildworld? I certainly haven't (oh, my > cvsupfile's attached as well). > > I have no idea what state my system is in now, because I ended up (after an > unsuccesful but naively-trusting "make world") reinstalling the "bin" > distribution from the CD. This was after discovering that my > kernel/rc.firewall/ipfw configuration was mismatched (but boy was I secure :-), > and attempting to follow the instructions in /usr/src/UPDATING. > > Sigh. Not a happy camper. > > Gord Broom > > > ---------------------------------------------------------------------- > Name: error-log > error-log Type: Plain Text (text/plain) > Encoding: 8bit > > Name: cvsupfile > cvsupfile Type: Plain Text (text/plain) > Encoding: 8bit -- 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 Wed Jan 24 2:51: 9 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id C1D6337B401 for ; Wed, 24 Jan 2001 02:50:49 -0800 (PST) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.1/8.11.1) with ESMTP id f0OB4sS10071; Wed, 24 Jan 2001 03:04:54 -0800 (PST) (envelope-from msmith@mass.dis.org) Message-Id: <200101241104.f0OB4sS10071@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Guy Harris Cc: Matthias Andree , Linux NFS mailing list , FreeBSD Stable Subject: Re: [NFS] Incompatible: FreeBSD 4.2 client, Linux 2.2.18 nfsv3 server, read-only export In-reply-to: Your message of "Wed, 24 Jan 2001 00:17:01 PST." <20010124001701.F344@quadrajet.flashcom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 24 Jan 2001 03:04:54 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Wed, Jan 24, 2001 at 04:34:36AM +0100, Matthias Andree wrote: > > > (Perhaps it would've been better had the V3 protocol specified that > > > either 0 or an NFS3ERR_xxx value be supplied for each of the permission > > > bits checked, although that raises the question of whether any server > > > would, say, allow read access and allow write access but disallow > > > simultaneous read/write access.) > > > > No, the plan is simple. In the ACCESS call, the client asks if it has a > > certain set of permissions, the sender weeds the actions the client may > > not take at the moment of the ACCESS call, and returns a possibly > > stripped-down set of allowed actions (which may then change > > later). There's nothing wrong with this approach. > > The problem is that it only allows the client to know what it can or > can't do; it doesn't let the client know, in more detail, *why* it can't > do the things it's not allowed to do. I'm not sure that the v3 specification actually cares about telling the client "why", and if it did, it should probably have defined it. I'm not really happy that an ACCESS operation should ever return EROFS; the operation itself doesn't attempt to write anything to the filesystem. > For example, a UNIX "open()" call that calls an "access" vnode operation > couldn't, if that file is mounted over NFS, find out that the open for > writing is forbidden because the file system is read-only; even if > that's the reason, the answer you get back is probably EACCES (that's > what happens in the Solaris NFS, for example). This would be more or less what I'd expect. From the client's point of view, returning "this is a read-only filesystem" is not very useful anyway. What's a read-only filesystem? The NFS mount? The filesystem backing the mount? > BTW, I suspect the reason why FreeBSD is seeing a problem and Solaris > isn't *might* be because FreeBSD is, at least if it's caching the > results of ACCESS requests, sending over the wire an ACCESS request with > all the bits turned on - the intent is, presumably, to find out as much > as you can in one ACCESS call, even if you don't need all that > information right now - which would provoke the Linux server to return > an EROFS error rather than READ|EXECUTE|LOOKUP. I still don't really understand why the Linux code would return EROFS; we send READ|MODIFY|EXTEND|EXECUTE|DELETE|LOOKUP. If the filesystem is read-only, we'd expect to see READ|EXECUTE|LOOKUP (at most) come back, but with an OK response. > If Solaris doesn't do that (I think Solaris *does* cache ACCESS replies, > but it may, when it gets the reply back, cache only the answers to the > questions it asked and, if another question is asked later and the > answer to that question wasn't cached, ask that other question over the > wire), then it may be that: I believe, from discussions with you and Brian when I was doing this before, that Solaris does track just the questions that we asked. Because I didn't really have anywhere to remember what had been asked, I just went ahead and asked for everything. > on Solaris, an operation that doesn't require write permission > causes an ACCESS request to go over the wire with none of > MODIFY, EXTEND, or DELETE set, so Linux replies with a bitset of > those operations that are actually allowed and, if the operation > in question is one of them, the access vnode op returns "OK"; > > on FreeBSD, an operation that doesn't require write permission > causes an ACCESS request to go over the wire with *all* bits > set, so Linux replies with EROFS even though the operation is > perfectly OK on a read-only file system, and the operation > (e.g., opening a directory in order to list its contents) fails > with EROFS. This sounds about right. I'd argue that the Linux server is probably in error, but the "easy" solution here will simply be to discard EROFS as "No means Yes for Linux", since it's a nonsense response to the query. (For those following this, see attached diff. Test results would be appreciated.) > This means another workaround may be to set the > "vfs.nfs.access_cache_timeout" sysctl value to 0, which turns off access > reply caching. However, if I remember correctly something Brian > Pawlowski mentioned a while ago, that can hurt NFS performance; I don't > remember the details, but I seem to remember that access reply caching > was being disabled on FreeBSD for some reason at some point (I also > vaguely remember Mike Smith being involved in the discussion; Mike, if > you're listening, do you remember any of this? Brian's out of town > right now, and I'm at home rather than the office so I can't plow > through my work mail archives). Turning the access cache off will significantly increase wire traffic and harm your NFS v3 performance a lot. I'd ask the plaintiff to test the attached patch and let me know how it goes; if it seems to avoid the problem, I'll go ahead and bring it in. In the meantime, I'd also ask the Linux NFS maintainers (if they're listening) to consider altering their server's behaviour just for the sake of correctness (if it hasn't already been done subsequent to this relatively ancient release). Regards, Mike -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 24 3: 2: 0 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id C6C8737B402; Wed, 24 Jan 2001 03:01:40 -0800 (PST) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.1/8.11.1) with ESMTP id f0OBH7S10154; Wed, 24 Jan 2001 03:17:08 -0800 (PST) (envelope-from msmith@mass.dis.org) Message-Id: <200101241117.f0OBH7S10154@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Mike Smith Cc: Guy Harris , Matthias Andree , Linux NFS mailing list , FreeBSD Stable Subject: Re: [NFS] Incompatible: FreeBSD 4.2 client, Linux 2.2.18 nfsv3 server, read-only export In-reply-to: Your message of "Wed, 24 Jan 2001 03:04:54 PST." <200101241104.f0OB4sS10071@mass.dis.org> Mime-Version: 1.0 Content-Type: multipart/mixed ; boundary="==_Exmh_-7315860230" Date: Wed, 24 Jan 2001 03:17:07 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multipart MIME message. --==_Exmh_-7315860230 Content-Type: text/plain; charset=us-ascii > (For those following this, see attached diff. Test results would be > appreciated.) Of course, attaching the diff would make me look more intelligent. Take two... --==_Exmh_-7315860230 Content-Type: text/plain ; name="nfs_vnops.diff"; charset=us-ascii Content-Description: nfs_vnops.diff Content-Disposition: attachment; filename="nfs_vnops.diff" --- /sys/nfs/nfs_vnops.c Fri Jan 12 14:15:00 2001 +++ nfs_vnops.c Wed Jan 24 03:01:52 2001 @@ -387,6 +387,14 @@ */ nfsstats.accesscache_misses++; error = nfs3_access_otw(vp, wmode, ap->a_p,ap->a_cred); + /* + * Linux server may return EROFS despite this being + * only an ACCESS rpc if we are asking about bits that + * might allow us to write to the FS. The workaround + * is to ignore EROFS as a return here. + */ + if (error == EROFS) + error = 0; if (!error) { if ((np->n_mode & mode) != mode) { error = EACCES; --==_Exmh_-7315860230 Content-Type: text/plain; charset=us-ascii ... 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 --==_Exmh_-7315860230-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 24 3:31:27 2001 Delivered-To: freebsd-stable@freebsd.org Received: from nothing-going-on.demon.co.uk (unknown [194.128.198.234]) by hub.freebsd.org (Postfix) with ESMTP id D60F437B6A3 for ; Wed, 24 Jan 2001 03:31:09 -0800 (PST) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.11.1/8.11.1) id f0OB9D002141; Wed, 24 Jan 2001 11:09:13 GMT (envelope-from nik) Date: Wed, 24 Jan 2001 11:09:12 +0000 From: Nik Clayton To: John Polstra Cc: stable@freebsd.org, CGiordano@ids.net Subject: Re: preventing cvsup from replacing /usr/ports symlink? Message-ID: <20010124110912.A2127@canyon.nothing-going-on.org> References: <200101202028.f0KKSUr80758@saturn.home.ben.com> <20010121021117.A2300@snark.ptc.spbu.ru> <200101210047.f0L0lBq15592@vashon.polstra.com> <3A6C5E6C.3E84EAC0@ids.net> <200101232308.f0NN8QT25018@vashon.polstra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200101232308.f0NN8QT25018@vashon.polstra.com>; from jdp@polstra.com on Tue, Jan 23, 2001 at 03:08:26PM -0800 Organization: FreeBSD Project Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jan 23, 2001 at 03:08:26PM -0800, John Polstra wrote: > Questions for those who have seen this happen: > > 1. You're using checkout mode, right? Yes (but only the ports tree), the supfile entry looks like ports-all prefix=/usr tag=. I know I could change 'prefix', but the whole point of this disk configuration is to enable me to flexibly move things around disks and partitions without needing to update application config files. > 2. Are you using "-s" on the cvsup command line? No. cvsup -g /usr/local/etc/supfile N -- Internet connection, $19.95 a month. Computer, $799.95. Modem, $149.95. Telephone line, $24.95 a month. Software, free. USENET transmission, hundreds if not thousands of dollars. Thinking before posting, priceless. Somethings in life you can't buy. For everything else, there's MasterCard. -- Graham Reed, in the Scary Devil Monastery To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 24 4:12:21 2001 Delivered-To: freebsd-stable@freebsd.org Received: from emma1.emma.line.org (p3EE3CBF7.dip.t-dialin.net [62.227.203.247]) by hub.freebsd.org (Postfix) with ESMTP id D925637B69B for ; Wed, 24 Jan 2001 04:11:59 -0800 (PST) Received: by emma1.emma.line.org (Postfix, from userid 500) id 1FA30A2001; Wed, 24 Jan 2001 13:11:50 +0100 (CET) Date: Wed, 24 Jan 2001 13:11:50 +0100 From: Matthias Andree To: Guy Harris Cc: Linux NFS mailing list , FreeBSD Stable Subject: Re: [NFS] Incompatible: FreeBSD 4.2 client, Linux 2.2.18 nfsv3 server, read-only export Message-ID: <20010124131150.B1839@emma1.emma.line.org> References: <20010123015612.H345@quadrajet.flashcom.com> <20010123162930.B5443@emma1.emma.line.org> <20010123111005.D344@quadrajet.flashcom.com> <20010124001701.F344@quadrajet.flashcom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010124001701.F344@quadrajet.flashcom.com>; from gharris@flashcom.net on Wed, Jan 24, 2001 at 00:17:01 -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 24 Jan 2001, Guy Harris wrote: > The problem is that it only allows the client to know what it can or > can't do; it doesn't let the client know, in more detail, *why* it can't > do the things it's not allowed to do. That's a different problem. > BTW, I suspect the reason why FreeBSD is seeing a problem and Solaris > isn't *might* be because FreeBSD is, at least if it's caching the > results of ACCESS requests, sending over the wire an ACCESS request with > all the bits turned on - the intent is, presumably, to find out as much > as you can in one ACCESS call, even if you don't need all that > information right now - which would provoke the Linux server to return > an EROFS error rather than READ|EXECUTE|LOOKUP. I tcpdumped Solaris <-> Linux conversation, on a Linux 2.2.17 kernel with nfs v3 patched (I'm off-site ATM and don't want to reboot the server with a different kernel remotely.) Here's what Solaris does for ls: 1. GETATTR 2. ACCESS - ask ONLY for READ 3. GETATTR Linux sends OK back with the READ permission bit set. > on FreeBSD, an operation that doesn't require write permission > causes an ACCESS request to go over the wire with *all* bits > set, so Linux replies with EROFS even though the operation is > perfectly OK on a read-only file system, and the operation > (e.g., opening a directory in order to list its contents) fails > with EROFS. Yes. That's not bad by itself, the Linux server is obviously broken and needs fixing. No action required on FreeBSD client part here. Linux can (I didn't check RFC 1813) probably still return ROFS in response to a later modification request. > This means another workaround may be to set the > "vfs.nfs.access_cache_timeout" sysctl value to 0, which turns off access > reply caching. However, if I remember correctly something Brian > Pawlowski mentioned a while ago, that can hurt NFS performance; I don't > remember the details, but I seem to remember that access reply caching > was being disabled on FreeBSD for some reason at some point (I also > vaguely remember Mike Smith being involved in the discussion; Mike, if > you're listening, do you remember any of this? That's not the point. It won't help either, since FreeBSD ONLY sends three identical ACCESS requests with all 6 flags sets each time, it does not even try to access anything. -- Matthias Andree To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 24 4:16: 8 2001 Delivered-To: freebsd-stable@freebsd.org Received: from emma1.emma.line.org (p3EE3CBF7.dip.t-dialin.net [62.227.203.247]) by hub.freebsd.org (Postfix) with ESMTP id 592A337B402 for ; Wed, 24 Jan 2001 04:15:47 -0800 (PST) Received: by emma1.emma.line.org (Postfix, from userid 500) id 58A52A2001; Wed, 24 Jan 2001 13:15:41 +0100 (CET) Date: Wed, 24 Jan 2001 13:15:41 +0100 From: Matthias Andree To: Linux NFS mailing list , FreeBSD Stable Subject: Re: [NFS] Incompatible: FreeBSD 4.2 client, Linux 2.2.18 nfsv3 server, read-only export Message-ID: <20010124131541.C1839@emma1.emma.line.org> References: <20010124001701.F344@quadrajet.flashcom.com> <200101241104.f0OB4sS10071@mass.dis.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200101241104.f0OB4sS10071@mass.dis.org>; from msmith@freebsd.org on Wed, Jan 24, 2001 at 03:04:54 -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 24 Jan 2001, Mike Smith wrote: > I'm not sure that the v3 specification actually cares about telling the > client "why", and if it did, it should probably have defined it. I'm not > really happy that an ACCESS operation should ever return EROFS; the > operation itself doesn't attempt to write anything to the filesystem. ROFS is not a valid response to ACCESS, as pointed out by Guy before. Don't waste your time on working clients. > I still don't really understand why the Linux code would return EROFS; we > send READ|MODIFY|EXTEND|EXECUTE|DELETE|LOOKUP. If the filesystem is > read-only, we'd expect to see READ|EXECUTE|LOOKUP (at most) come back, > but with an OK response. Because it's broken. Nobody has claimed Linux to be bug-free. > This sounds about right. I'd argue that the Linux server is probably in > error, but the "easy" solution here will simply be to discard EROFS as > "No means Yes for Linux", since it's a nonsense response to the query. I don't think working around server bugs in servers that can be fixed is the proper approach. You can still work around if the Linux NFSD maintainers refuse to fix. I'll try to have a look myself later if possible. > In the meantime, I'd also ask the Linux NFS maintainers (if they're > listening) to consider altering their server's behaviour just for the > sake of correctness (if it hasn't already been done subsequent to this > relatively ancient release). I'll take care of reminding them until this issue is fixed. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 24 5:30:54 2001 Delivered-To: freebsd-stable@freebsd.org Received: from freenix.no (atreides.freenix.no [213.188.21.6]) by hub.freebsd.org (Postfix) with ESMTP id 6BAA237B402 for ; Wed, 24 Jan 2001 05:30:33 -0800 (PST) Received: (from morten@localhost) by freenix.no (8.11.1/8.9.3) id f0ODURl63073 for freebsd-stable@freebsd.org; Wed, 24 Jan 2001 14:30:27 +0100 (CET) (envelope-from morten) Date: Wed, 24 Jan 2001 14:30:26 +0100 From: "Morten A . Middelthon" To: freebsd-stable@freebsd.org Subject: ipnat problem? Message-ID: <20010124143026.A61137@freenix.no> 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 X-Warning: So cunning you could brush your teeth with it. Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm currently using a FreeBSD box with ipf/ipnat as a gateway for our internal network (10.0.0/24), and this, ofcourse, works like a charm. But(!) today I set up an extra net internally (10.0.1/24) for some testing purposes. Talking between 10.0.0/24 and 10.0.1/24 is easy, but I couldn't get any hosts on 10.0.1/24 to go through my ipf/ipnat box. In my ipnat config I've already got 'map fxp0 10.0.0/24 -> xxx.xxx.xxx.xxx/32', and so now I added map fxp0 10.0.1/24 -> xxx.xxx.xxx.xxx/32' for the new net, but that didn't help. xxx.xxx.xxx.xxx is ofcourse not in my actual config... 'ipnat -l' doesn't show the new mapping I added. The network layout looks roughly like this: inet <-- [Host A, ipnat gateway] <-- 10.0.0/24 <-- [Host B, gateway] <-- 10.0.1/24 Any suggestions to how I might fix this problem? -- Morten A. Middelthon Freenix Norge http://www.freenix.no/ -- The older I grow, the less important the comma becomes. Let the reader catch his own breath. -- Elizabeth Clarkson Zwart To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 24 6: 4:20 2001 Delivered-To: freebsd-stable@freebsd.org Received: from gate.trident-uk.co.uk (mail.trident-uk.co.uk [195.166.16.10]) by hub.freebsd.org (Postfix) with ESMTP id 6040637B404 for ; Wed, 24 Jan 2001 06:03:54 -0800 (PST) Received: from [194.207.93.139] by gate.trident-uk.co.uk for freebsd-stable@freebsd.org id NAA14048; Wed Jan 24 13:55:52 2001 Date: Wed, 24 Jan 2001 14:08:21 +0000 Subject: make world fails Message-ID: <20010124140820.K238@freefire.psi-domain.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Balsa 1.0.0 Lines: 49 To: freebsd-stable@freebsd.org From: Jamie Heckford Reply-To: heckfordj@psi-domain.co.uk Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, make world is failing - after a cvs up at appoximatly 2.00pm GMT. Here is the ouptut: ########### cd /usr/src/gnu/usr.bin/gperf; make obj; make depend; make all; make install /usr/obj/usr/src/i386/usr/src/gnu/usr.bin/gperf created for /usr/src/gnu/ usr.bin/gperf ===> doc /usr/obj/usr/src/i386/usr/src/gnu/usr.bin/gperf/doc created for /usr/src/gnu/usr.bin/gperf/doc make: don't know how to make options.c Stop *** Error code 2 Stop in /usr/src. *** Error code 1 Stop in .usr/src. *** Error code 1 Stop in /usr/src. ########### I hope this helps. Thanks -- Jamie Heckford Chief Network Engineer Psi-Domain - Innovative Linux Solutions. Ask Us How. ===================================== email: heckfordj@psi-domain.co.uk web: http://www.psi-domain.co.uk/ tel: +44 (0)1737 789 246 fax: +44 (0)1737 789 245 mobile: +44 (0)7866 724 224 ===================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 24 6:12: 9 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 E7B5137B404 for ; Wed, 24 Jan 2001 06:11:50 -0800 (PST) Received: from pcle2.cc.univie.ac.at (pcle2.cc.univie.ac.at [131.130.2.177]) by mailbox.univie.ac.at (8.9.3/8.9.3) with ESMTP id PAA54500; Wed, 24 Jan 2001 15:11:46 +0100 Date: Wed, 24 Jan 2001 15:10:53 +0100 (CET) From: Lukas Ertl X-X-Sender: To: "Thomas T. Veldhouse" Cc: Subject: Re: make buildworld fails In-Reply-To: <006401c08547$6f167990$3028680a@tgt.com> 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, 23 Jan 2001, Thomas T. Veldhouse wrote: > Did you 'make clean' and remove the stale object files from /usr/obj befo= re > you tried to build world? This looks like old dependencies sitting aroun= d. > > cd /usr/src && make clean > cd /usr/obj && chflags -R noschg usr && rm -rf usr I did that and removed the whole /usr/obj tree. Now I get signal 11 coredumps from ld. I guess this is a hardware problem? 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 Wed Jan 24 6:16:18 2001 Delivered-To: freebsd-stable@freebsd.org Received: from burdell.cc.gatech.edu (burdell.cc.gatech.edu [130.207.3.207]) by hub.freebsd.org (Postfix) with ESMTP id 9285A37B404 for ; Wed, 24 Jan 2001 06:16:00 -0800 (PST) Received: from felix.cc.gatech.edu (felix.cc.gatech.edu [130.207.107.11]) by burdell.cc.gatech.edu (8.9.1/8.9.1) with ESMTP id JAA10986; Wed, 24 Jan 2001 09:15:58 -0500 (EST) Received: from localhost (dibble@localhost) by felix.cc.gatech.edu (8.9.3+Sun/8.9.1) with ESMTP id JAA14811; Wed, 24 Jan 2001 09:15:56 -0500 (EST) Date: Wed, 24 Jan 2001 09:15:56 -0500 (EST) From: Dibble To: Jamie Heckford Cc: freebsd-stable@freebsd.org Subject: Re: make world fails In-Reply-To: <20010124140820.K238@freefire.psi-domain.co.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 Try doing a make clean in /usr/src. That usually helps me when this happens. On Wed, 24 Jan 2001, Jamie Heckford wrote: > Hi, > > make world is failing - after a cvs up at appoximatly 2.00pm GMT. > > Here is the ouptut: > > ########### > > cd /usr/src/gnu/usr.bin/gperf; make obj; make > depend; make all; > make install > > /usr/obj/usr/src/i386/usr/src/gnu/usr.bin/gperf created for /usr/src/gnu/ > usr.bin/gperf > ===> doc > /usr/obj/usr/src/i386/usr/src/gnu/usr.bin/gperf/doc created for > /usr/src/gnu/usr.bin/gperf/doc > make: don't know how to make options.c Stop > *** Error code 2 > > Stop in /usr/src. > *** Error code 1 > > Stop in .usr/src. > *** Error code 1 > > Stop in /usr/src. > > ########### > > > I hope this helps. > > Thanks > > -- > Jamie Heckford > Chief Network Engineer > Psi-Domain - Innovative Linux Solutions. Ask Us How. > > ===================================== > email: heckfordj@psi-domain.co.uk > web: http://www.psi-domain.co.uk/ > > tel: +44 (0)1737 789 246 > fax: +44 (0)1737 789 245 > mobile: +44 (0)7866 724 224 > > ===================================== > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > ####################### Jeff Lee http://www.cc.gatech.edu/~dibble/ Student Assistant Dibble@cc.gatech.edu GTRI-ITTL 404-206-1365 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 24 6:36:20 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 D919E37B6A1 for ; Wed, 24 Jan 2001 06:36:01 -0800 (PST) Received: by lunatic.oneinsane.net (Postfix, from userid 1000) id 0F31415551; Wed, 24 Jan 2001 06:36:01 -0800 (PST) Date: Wed, 24 Jan 2001 06:36:00 -0800 From: Ron 'The InSaNe One' Rosson To: freebsd-stable@freebsd.org Subject: Re: ipnat problem? Message-ID: <20010124063600.A46017@lunatic.oneinsane.net> Reply-To: Ron Rosson Mail-Followup-To: freebsd-stable@freebsd.org References: <20010124143026.A61137@freenix.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010124143026.A61137@freenix.no>; from morten@freenix.no on Wed, Jan 24, 2001 at 02:30:26PM +0100 X-Operating-System: FreeBSD lunatic.oneinsane.net 4.1.1-STABLE X-Moon: The Moon is New 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: 6:33AM up 87 days, 8:48, 1 user, load averages: 0.16, 0.07, 0.07 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Morten A . Middelthon (morten@freenix.no) wrote: > > I'm currently using a FreeBSD box with ipf/ipnat as a gateway for our internal > network (10.0.0/24), and this, ofcourse, works like a charm. But(!) today I set > up an extra net internally (10.0.1/24) for some testing purposes. Talking > between 10.0.0/24 and 10.0.1/24 is easy, but I couldn't get any hosts on > 10.0.1/24 to go through my ipf/ipnat box. In my ipnat config I've already got > 'map fxp0 10.0.0/24 -> xxx.xxx.xxx.xxx/32', and so now I added > map fxp0 10.0.1/24 -> xxx.xxx.xxx.xxx/32' for the new net, but that didn't help. > xxx.xxx.xxx.xxx is ofcourse not in my actual config... > > 'ipnat -l' doesn't show the new mapping I added. > > The network layout looks roughly like this: > > inet <-- [Host A, ipnat gateway] <-- 10.0.0/24 <-- [Host B, gateway] <-- 10.0.1/24 > > Any suggestions to how I might fix this problem? > I would try replacing this entry: map fxp0 10.0.0/24 -> xxx.xxx.xxx.xxx/32 with map fxp0 10.0.0/23 -> xxx.xxx.xxx.xxx/32 I assume you are using class C subnets. Hope this helps TIA -- ------------------------------------------------------------------------------ Ron Rosson ... and a UNIX user said ... The InSaNe One rm -rf * insane@oneinsane.net and all was /dev/null and *void() ------------------------------------------------------------------------------ Just because I'm moody doesn't mean you're not irritating. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 24 7:37:37 2001 Delivered-To: freebsd-stable@freebsd.org Received: from granny.bwa.penx.com (granny.bwa.penx.com [207.149.143.101]) by hub.freebsd.org (Postfix) with ESMTP id DD46037B404 for ; Wed, 24 Jan 2001 07:37:19 -0800 (PST) Received: (from root@localhost) by granny.bwa.penx.com (8.11.2/8.11.2) id f0OFbHd07268 for stable@freebsd.org; Wed, 24 Jan 2001 07:37:17 -0800 (PST) Date: Wed, 24 Jan 2001 07:37:17 -0800 (PST) From: Charlie Root Message-Id: <200101241537.f0OFbHd07268@granny.bwa.penx.com> To: stable@freebsd.org Subject: ftp in free(): warning: junk pointer, too high to make sense. Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I cvsup yesterday against RELENG_4. Today, when I when to install a port, this happened: granny# mk >> mysql-3.23.32.tar.gz doesn't seem to exist in /usr/ports/distfiles/. >> Attempting to fetch from http://www.kernelnotes.de/MySQL/Downloads/MySQL-3.23/. Requesting http://www.kernelnotes.de/MySQL/Downloads/MySQL-3.23/mysql-3.23.32.tar.gz ftp: Error retrieving file: 404 Not Found ftp in free(): warning: junk pointer, too high to make sense. Segmentation fault - core dumped >> Attempting to fetch from http://www.mysql.net/Downloads/MySQL-3.23/. Requesting http://www.mysql.net/Downloads/MySQL-3.23/mysql-3.23.32.tar.gz Clue, please. dennisg@penx.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 24 7:40:24 2001 Delivered-To: freebsd-stable@freebsd.org Received: from netcabo.pt (mail.netcabo.pt [212.113.161.135]) by hub.freebsd.org (Postfix) with ESMTP id BD95137B401 for ; Wed, 24 Jan 2001 07:40:05 -0800 (PST) Received: from netcabo ([213.22.31.177]) by netcabo.pt with Microsoft SMTPSVC(5.5.1877.537.53); Wed, 24 Jan 2001 15:37:03 +0000 From: "Bruno Miguel" Organization: Artists, Inc. To: freebsd-stable@freebsd.org Date: Wed, 24 Jan 2001 15:38:18 -0000 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: ipnat problem? Reply-To: brunomiguel@netcabo.pt Message-ID: <3A6EF6EA.3332.A2053@localhost> In-reply-to: <20010124063600.A46017@lunatic.oneinsane.net> References: <20010124143026.A61137@freenix.no>; from morten@freenix.no on Wed, Jan 24, 2001 at 02:30:26PM +0100 X-mailer: Pegasus Mail for Win32 (v3.12c) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I would try replacing this entry: > map fxp0 10.0.0/24 -> xxx.xxx.xxx.xxx/32 > with > map fxp0 10.0.0/23 -> xxx.xxx.xxx.xxx/32 > > I assume you are using class C subnets. > map fxp0 10.0.0.0/24 -> ip/32 map fxp0 10.0.1.0/24 -> ip/32 or simply map fxp0 10.0.0.0/16 -> ip/32 now, you have to ipnat -FC -f /etc/natrules if your config is at /etc/natrules... :) ipnat -l *has* to show you that. Use x.y.z.w/ll formatting. ...:-=>> The freaking Mail Band <<=-:... hununu@netcabo.pt D.E.Q. @ I.S.T. - Portugal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 24 8: 9:15 2001 Delivered-To: freebsd-stable@freebsd.org Received: from freenix.no (atreides.freenix.no [213.188.21.6]) by hub.freebsd.org (Postfix) with ESMTP id 9B9B037B401 for ; Wed, 24 Jan 2001 08:08:57 -0800 (PST) Received: (from morten@localhost) by freenix.no (8.11.1/8.9.3) id f0OG8lK64039; Wed, 24 Jan 2001 17:08:47 +0100 (CET) (envelope-from morten) Date: Wed, 24 Jan 2001 17:08:47 +0100 From: "Morten A . Middelthon" To: Bruno Miguel Cc: freebsd-stable@freebsd.org Subject: Re: ipnat problem? Message-ID: <20010124170847.B61137@freenix.no> References: <20010124143026.A61137@freenix.no>; <20010124063600.A46017@lunatic.oneinsane.net> <3A6EF6EA.3332.A2053@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3A6EF6EA.3332.A2053@localhost>; from brunomiguel@netcabo.pt on Wed, Jan 24, 2001 at 03:38:18PM -0000 X-Operating-System: FreeBSD 4.2-STABLE X-Warning: So cunning you could brush your teeth with it. Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 24, 2001 at 03:38:18PM -0000, Bruno Miguel wrote: > > I would try replacing this entry: > > map fxp0 10.0.0/24 -> xxx.xxx.xxx.xxx/32 > > with > > map fxp0 10.0.0/23 -> xxx.xxx.xxx.xxx/32 > > > > I assume you are using class C subnets. > > > > map fxp0 10.0.0.0/24 -> ip/32 > map fxp0 10.0.1.0/24 -> ip/32 > > or simply > > map fxp0 10.0.0.0/16 -> ip/32 Yes, that worked wonderfully, and it was kinda logic too :} Thanks. -- Morten A. Middelthon Freenix Norge http://www.freenix.no/ -- "For every complex question, there is a simple answer-- and it's wrong." -- H.L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 24 9:10:22 2001 Delivered-To: freebsd-stable@freebsd.org Received: from VL-MS-MR002.sc1.videotron.ca (relais.videotron.ca [24.201.245.36]) by hub.freebsd.org (Postfix) with ESMTP id 4BB6937B698 for ; Wed, 24 Jan 2001 09:10:02 -0800 (PST) Received: from southpark ([24.201.143.157]) by VL-MS-MR002.sc1.videotron.ca (Netscape Messaging Server 4.15) with SMTP id G7OFOP00.9CA for ; Wed, 24 Jan 2001 12:10:01 -0500 Message-ID: <001001c08628$8db16180$9d8fc918@videotron.ca> From: "Luc Morin" To: Subject: Network stops working Date: Wed, 24 Jan 2001 12:10:29 -0500 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_000D_01C085FE.A4A8FEE0" 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_000D_01C085FE.A4A8FEE0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi, I have recently started experiencing network problems on my -stable box. The last cvsup dates a few weeks back, and everything was working fine = up until a few days ago. Strangest thing is that everything works just fine under Win98, and that = when I reboot under FreeBSD, network will be ok for a few minutes and = then hang. After that, I can't even ping my gateway. I have an NE2000 clone (ed driver), and I use a cable modem to connect = to the Internet. At this point, I'm only asking if anyone else has experienced those = problems. As I have to write my e-amil under Win98, I don't have access right now = to my FreeBSD partitions. I will happilly provide detailed information = if this problem is not already know and cared for. Thansk all, Luc Morin ------=_NextPart_000_000D_01C085FE.A4A8FEE0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi,
 
I have recently started experiencing = network=20 problems on my -stable box.
 
The last cvsup dates a few weeks back, = and=20 everything was working fine up until a few days ago.
 
Strangest thing is that everything = works just fine=20 under Win98, and that when I reboot under FreeBSD, network will be ok = for a few=20 minutes and then hang. After that, I can't even ping my = gateway.
 
I have an NE2000 clone (ed driver), and = I use a=20 cable modem to connect to the Internet.
 
At this point, I'm only asking if = anyone else has=20 experienced those problems.
 
As I have to write my e-amil under = Win98, I don't=20 have access right now to my FreeBSD partitions. I will happilly provide = detailed=20 information if this problem is not already know and cared = for.
 
Thansk all,
 
Luc Morin
------=_NextPart_000_000D_01C085FE.A4A8FEE0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 24 9:14:13 2001 Delivered-To: freebsd-stable@freebsd.org Received: from gate.trident-uk.co.uk (mail.trident-uk.co.uk [195.166.16.10]) by hub.freebsd.org (Postfix) with ESMTP id 513E037B404 for ; Wed, 24 Jan 2001 09:13:49 -0800 (PST) Received: from [194.207.93.139] by gate.trident-uk.co.uk for dibble@cc.gatech.edu id OAA15252; Wed Jan 24 14:20:49 2001 Date: Wed, 24 Jan 2001 14:33:18 +0000 Subject: Re: make world fails Message-ID: <20010124143318.S238@freefire.psi-domain.co.uk> References: <20010124140820.K238@freefire.psi-domain.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit In-Reply-To: ; from dibble@cc.gatech.edu on Wed, Jan 24, 2001 at 14:15:56 +0000 X-Mailer: Balsa 1.0.0 Lines: 115 To: Dibble From: Jamie Heckford Reply-To: heckfordj@psi-domain.co.uk Cc: freebsd-stable@freebsd.org Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I tried this but no joy. I have also followed the handbook steps for removing /usr/obj files. make clean gives the error: ########### ===> gnu/usr.bin/groff/devX100 "Makefile", line 8: could not find /usr/src/gnu/usr.bin/groff/devX100/ ./../../../contrib/groff/devX100/Makefile.sub make: fatal errors encountered -- cannot continue *** Error code 1 Stop in /usr/src/gnu/usr.bin/groff. *** Error code 1 Stop in /usr/src/gnu/usr.bin. *** Error code 1 Stop in /usr/src/gnu. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. ############### On 2001.01.24 14:15:56 +0000 Dibble wrote: > Try doing a make clean in /usr/src. That usually helps me when this > happens. > > On Wed, 24 Jan 2001, Jamie Heckford wrote: > > > Hi, > > > > make world is failing - after a cvs up at appoximatly 2.00pm GMT. > > > > Here is the ouptut: > > > > ########### > > > > cd /usr/src/gnu/usr.bin/gperf; make obj; make > > depend; make all; > > make install > > > > /usr/obj/usr/src/i386/usr/src/gnu/usr.bin/gperf created for > /usr/src/gnu/ > > usr.bin/gperf > > ===> doc > > /usr/obj/usr/src/i386/usr/src/gnu/usr.bin/gperf/doc created for > > /usr/src/gnu/usr.bin/gperf/doc > > make: don't know how to make options.c Stop > > *** Error code 2 > > > > Stop in /usr/src. > > *** Error code 1 > > > > Stop in .usr/src. > > *** Error code 1 > > > > Stop in /usr/src. > > > > ########### > > > > > > I hope this helps. > > > > Thanks > > > > -- > > Jamie Heckford > > Chief Network Engineer > > Psi-Domain - Innovative Linux Solutions. Ask Us How. > > > > ===================================== > > email: heckfordj@psi-domain.co.uk > > web: http://www.psi-domain.co.uk/ > > > > tel: +44 (0)1737 789 246 > > fax: +44 (0)1737 789 245 > > mobile: +44 (0)7866 724 224 > > > > ===================================== > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-stable" in the body of the message > > > > ####################### > Jeff Lee http://www.cc.gatech.edu/~dibble/ > Student Assistant Dibble@cc.gatech.edu > GTRI-ITTL 404-206-1365 > > > -- Jamie Heckford Chief Network Engineer Psi-Domain - Innovative Linux Solutions. Ask Us How. ===================================== email: heckfordj@psi-domain.co.uk web: http://www.psi-domain.co.uk/ tel: +44 (0)1737 789 246 fax: +44 (0)1737 789 245 mobile: +44 (0)7866 724 224 ===================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 24 9:25:27 2001 Delivered-To: freebsd-stable@freebsd.org Received: from eos.umsl.edu (eos.umsl.edu [134.124.42.103]) by hub.freebsd.org (Postfix) with ESMTP id 7B21637B400 for ; Wed, 24 Jan 2001 09:25:07 -0800 (PST) Received: from eos.umsl.edu (localhost [127.0.0.1]) by eos.umsl.edu (8.11.1/8.11.0) with ESMTP id f0OHP3P92815 for ; Wed, 24 Jan 2001 11:25:04 -0600 (CST) (envelope-from tom@eos.umsl.edu) Message-ID: <3A6F0FEF.F4A4BAD9@eos.umsl.edu> Date: Wed, 24 Jan 2001 11:25:03 -0600 From: Tom Kyle Organization: University of Missouri-St. Louis X-Mailer: Mozilla 4.75 [en] (X11; U; FreeBSD 4.2-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: make installworld fails Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I'm tracking STABLE and 'make installworld' fails part of the way through the perl section: ===> gnu/usr.bin/perl/suidperl install -c -s -o root -g wheel -m 511 suidperl /usr/bin /usr/bin/sperl5 -> /usr/bin/suidperl /usr/bin/sperl5.00503 -> /usr/bin/suidperl ===> gnu/usr.bin/perl/library install: opnames.h: No such file or directory *** Error code 71 Stop in /usr/src/gnu/usr.bin/perl/library. *** Error code 1 Stop in /usr/src/gnu/usr.bin/perl. *** Error code 1 Stop in /usr/src/gnu/usr.bin. *** Error code 1 Stop in /usr/src/gnu. *** 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. I blew away /usr/src, ran cvsup again, and then did a `make buildworld,` 'make buildkernel,' 'make installkernel,' and then the 'make installworld', where it died in the same place with the same error. My supfile contains the following: *default host=cvsup2.FreeBSD.org *default base=/usr *default prefix=/usr *default release=cvs tag=RELENG_4 *default delete use-rel-suffix src-all Any tips or suggestions? Tom - Thomas A. Kyle Network Security Administrator University of Missouri-St. Louis tkyle@jinx.umsl.edu (314) 516-6012 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 24 9:35: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 8BAD337B699 for ; Wed, 24 Jan 2001 09:35:30 -0800 (PST) Received: from [203.164.12.28] by www.quake.com.au (NTMail 4.30.0012/AH9370.63.d1acf55c) with ESMTP id trvsaaaa for ; Thu, 25 Jan 2001 04:44:06 +1100 Message-ID: <3A6F126A.19B0EC6C@quake.com.au> Date: Thu, 25 Jan 2001 04:35:38 +1100 From: Kal Torak X-Mailer: Mozilla 4.73 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Charlie Root Cc: stable@freebsd.org Subject: Re: ftp in free(): warning: junk pointer, too high to make sense. References: <200101241537.f0OFbHd07268@granny.bwa.penx.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Charlie Root wrote: > > I cvsup yesterday against RELENG_4. Today, when I when to > install a port, this happened: > > granny# mk > >> mysql-3.23.32.tar.gz doesn't seem to exist in /usr/ports/distfiles/. > >> Attempting to fetch from http://www.kernelnotes.de/MySQL/Downloads/MySQL-3.23/. > Requesting http://www.kernelnotes.de/MySQL/Downloads/MySQL-3.23/mysql-3.23.32.tar.gz > ftp: Error retrieving file: 404 Not Found > > ftp in free(): warning: junk pointer, too high to make sense. > Segmentation fault - core dumped > >> Attempting to fetch from http://www.mysql.net/Downloads/MySQL-3.23/. > Requesting http://www.mysql.net/Downloads/MySQL-3.23/mysql-3.23.32.tar.gz > > Clue, please. And did you also cvsup the ports collection? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 24 9:40:40 2001 Delivered-To: freebsd-stable@freebsd.org Received: from VL-MS-MR002.sc1.videotron.ca (relais.videotron.ca [24.201.245.36]) by hub.freebsd.org (Postfix) with ESMTP id 4995137B400 for ; Wed, 24 Jan 2001 09:40:17 -0800 (PST) Received: from southpark ([24.201.143.157]) by VL-MS-MR002.sc1.videotron.ca (Netscape Messaging Server 4.15) with SMTP id G7OH3401.LEE for ; Wed, 24 Jan 2001 12:40:16 -0500 Message-ID: <001201c0862c$c72a6020$9d8fc918@videotron.ca> From: "Luc Morin" To: References: <001001c08628$8db16180$9d8fc918@videotron.ca> Subject: Re: Network stops working Date: Wed, 24 Jan 2001 12:40:44 -0500 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_000E_01C08602.DE1A5C60" 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_000E_01C08602.DE1A5C60 Content-Type: multipart/alternative; boundary="----=_NextPart_001_000F_01C08602.DE1A5C60" ------=_NextPart_001_000F_01C08602.DE1A5C60 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi, I have tested a few more times by rebooting my box and pinging a known = good host. Every time I see the same pattern. it works for a few minutes, then = stops working completely. Attached is a text file with various system information. thanks, Luc Morin ------=_NextPart_001_000F_01C08602.DE1A5C60 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi,
 
I have tested a few more times by = rebooting my box=20 and pinging a known good host.
 
Every time I see the same pattern. it = works for a=20 few minutes, then stops working completely.
 
Attached is a text file with = various system=20 information.
 
thanks,
 
Luc Morin
 
 
------=_NextPart_001_000F_01C08602.DE1A5C60-- ------=_NextPart_000_000E_01C08602.DE1A5C60 Content-Type: text/plain; name="info.txt" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="info.txt" uname -a ouput:=0A= =0A= FreeBSD southpark.videotron.ca 4.2-STABLE FreeBSD 4.2-STABLE #0: Thu Jan = 18 18:00:27 EST 2001 = root@southpark.videotron.ca:/usr/obj/usr/src/sys/MYKERN4 i386=0A= =0A= =0A= dmesg output=0A= =0A= Copyright (c) 1992-2001 The FreeBSD Project.=0A= Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994=0A= The Regents of the University of California. All rights reserved.=0A= FreeBSD 4.2-STABLE #0: Thu Jan 18 18:00:27 EST 2001=0A= root@southpark.videotron.ca:/usr/obj/usr/src/sys/MYKERN4=0A= Timecounter "i8254" frequency 1193182 Hz=0A= CPU: Pentium III/Pentium III Xeon/Celeron (501.14-MHz 686-class CPU)=0A= Origin =3D "GenuineIntel" Id =3D 0x673 Stepping =3D 3=0A= = Features=3D0x383f9ff=0A= real memory =3D 134201344 (131056K bytes)=0A= Invalid command or syntax. Type `?' for help.=0A= avail memory =3D 127844352 (124848K bytes)=0A= Preloaded elf kernel "kernel" at 0xc02d7000.=0A= Preloaded userconfig_script "/boot/kernel.conf" at 0xc02d709c.=0A= Pentium Pro MTRR support enabled=0A= npx0: on motherboard=0A= npx0: INT 16 interface=0A= pcib0: on motherboard=0A= pci0: on pcib0=0A= pcib1: at device 1.0 on = pci0=0A= pci1: on pcib1=0A= pci1: at 0.0 irq 11=0A= isab0: at device 4.0 on pci0=0A= isa0: on isab0=0A= atapci0: port 0xb800-0xb80f at device 4.1 = on pci0=0A= ata0: at 0x1f0 irq 14 on atapci0=0A= ata1: at 0x170 irq 15 on atapci0=0A= pci0: at 4.2 irq 5=0A= chip1: port 0xe800-0xe80f at = device 4.3 on pci0=0A= pcm0: port 0xb000-0xb03f irq 10 at device 10.0 on pci0=0A= ed0: port 0xa800-0xa81f irq 5 at = device 13.0 on pci0=0A= ed0: address 00:e0:29:40:c0:4f, type NE2000 (16 bit) =0A= fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0=0A= fdc0: FIFO enabled, 8 bytes threshold=0A= fd0: <1440-KB 3.5" drive> on fdc0 drive 0=0A= atkbdc0: at port 0x60,0x64 on isa0=0A= atkbd0: irq 1 on atkbdc0=0A= psm0: irq 12 on atkbdc0=0A= psm0: model IntelliMouse, device ID 3=0A= vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0=0A= sc0: on isa0=0A= sc0: VGA <16 virtual consoles, flags=3D0x200>=0A= sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0=0A= sio0: type 16550A=0A= sio1 at port 0x2f8-0x2ff irq 3 on isa0=0A= sio1: type 16550A=0A= ppc0: at port 0x378-0x37f irq 7 on isa0=0A= ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode=0A= ppbus0: IEEE1284 device found /NIBBLE/ECP=0A= Probing for PnP devices on ppbus0:=0A= ppbus0: PRINTER MLC,PCL,PJL=0A= lpt0: on ppbus0=0A= lpt0: Interrupt-driven port=0A= IP Filter: v3.4.8 initialized. Default =3D pass all, Logging =3D = disabled=0A= ata0-master: DMA limited to UDMA33, non-ATA66 compliant cable=0A= ad0: 13216MB [26853/16/63] at ata0-master = UDMA33=0A= ata1-master: DMA limited to UDMA33, non-ATA66 compliant cable=0A= ad2: 8063MB [16383/16/63] at ata1-master UDMA33=0A= ad3: 3079MB [6256/16/63] at ata1-slave UDMA33=0A= acd0: CDROM at ata0-slave using PIO4=0A= Mounting root from ufs:/dev/ad0s2a=0A= =0A= =0A= ifconfig -a output:=0A= =0A= ed0: flags=3D8843 mtu 1500=0A= inet 24.200.211.9 netmask 0xffffff00 broadcast 255.255.255.255=0A= ether 00:e0:29:40:c0:4f =0A= lo0: flags=3D8049 mtu 16384=0A= inet 127.0.0.1 netmask 0xff000000 =0A= =0A= =0A= cat /usr/src/sys/i386/conf/MYKERN4 ouput:=0A= =0A= machine i386=0A= cpu I686_CPU=0A= ident MYKERN4=0A= maxusers 10=0A= =0A= =0A= options INET #InterNETworking=0A= options IPFILTER=0A= options FFS #Berkeley Fast Filesystem=0A= options FFS_ROOT #FFS usable as root device [keep this!]=0A= options MSDOSFS #MSDOS Filesystem=0A= options CD9660 #ISO 9660 Filesystem=0A= options PROCFS #Process filesystem=0A= options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!]=0A= options UCONSOLE #Allow users to grab the console=0A= options USERCONFIG #boot -c editor=0A= options VISUAL_USERCONFIG #visual boot -c editor=0A= options KTRACE #ktrace(1) support=0A= options SYSVSHM #SYSV-style shared memory=0A= options SYSVMSG #SYSV-style message queues=0A= options SYSVSEM #SYSV-style semaphores=0A= options USER_LDT=0A= options P1003_1B #Posix P1003_1B real-time extentions=0A= options _KPOSIX_PRIORITY_SCHEDULING=0A= options ICMP_BANDLIM #Rate limit bad replies=0A= =0A= device isa=0A= device pci=0A= =0A= # Floppy drives=0A= device fdc0 at isa? port IO_FD1 irq 6 drq 2=0A= device fd0 at fdc0 drive 0=0A= =0A= # ATA and ATAPI devices=0A= device ata=0A= device atadisk # ATA disk drives=0A= device atapicd # ATAPI CDROM drives=0A= options ATA_STATIC_ID #Static device numbering=0A= options ATA_ENABLE_ATAPI_DMA #Enable DMA on ATAPI devices=0A= =0A= =0A= # atkbdc0 controls both the keyboard and the PS/2 mouse=0A= device atkbdc0 at isa? port IO_KBD=0A= device atkbd0 at atkbdc? irq 1=0A= device psm0 at atkbdc? irq 12=0A= =0A= device vga0 at isa?=0A= =0A= # splash screen/screen saver=0A= pseudo-device splash=0A= =0A= # syscons is the default console driver, resembling an SCO console=0A= device sc0 at isa?=0A= =0A= # Floating point support - do not disable.=0A= device npx0 at nexus? port IO_NPX irq 13=0A= =0A= # Power management support (see LINT for more options)=0A= device apm0 at nexus? disable flags 0x20 # Advanced Power Management=0A= =0A= # Serial (COM) ports=0A= device sio0 at isa? port IO_COM1 flags 0x10 irq 4=0A= device sio1 at isa? port IO_COM2 irq 3=0A= =0A= # Parallel port=0A= device ppc0 at isa? irq 7=0A= device ppbus # Parallel port bus (required)=0A= device lpt # Printer=0A= =0A= # PCI Ethernet NICs.=0A= device ed0=0A= =0A= # Pseudo devices - the number indicates how many units to allocated.=0A= pseudo-device loop # Network loopback=0A= pseudo-device ether # Ethernet support=0A= pseudo-device tun # Packet tunnel.=0A= pseudo-device pty # Pseudo-ttys (telnet etc)=0A= =0A= # The `bpf' pseudo-device enables the Berkeley Packet Filter.=0A= # Be aware of the administrative consequences of enabling this!=0A= pseudo-device bpf #Berkeley packet filter=0A= =0A= options TCP_DROP_SYNFIN #drop TCP packets with SYN+FIN=0A= options TCP_RESTRICT_RST #restrict emission of TCP RST =0A= =0A= #Sound=0A= device pcm=0A= PID TT STAT TIME COMMAND=0A= 0 ?? DLs 0:00.00 (swapper)=0A= 1 ?? ILs 0:00.01 /sbin/init --=0A= 2 ?? DL 0:00.00 (pagedaemon)=0A= 3 ?? DL 0:00.00 (vmdaemon)=0A= 4 ?? DL 0:00.00 (bufdaemon)=0A= 5 ?? DL 0:00.00 (syncer)=0A= 40 ?? Is 0:00.00 adjkerntz -i=0A= 115 ?? Is 0:00.00 /sbin/dhclient ed0=0A= 139 ?? Ss 0:00.03 syslogd -s=0A= 158 ?? Is 0:00.00 cron=0A= 227 v0 Ss 0:00.06 -bash (bash)=0A= 248 v0 R+ 0:00.00 ps -ax=0A= 228 v1 Is+ 0:00.00 /usr/libexec/getty Pc ttyv1=0A= 229 v2 Is+ 0:00.00 /usr/libexec/getty Pc ttyv2=0A= 230 v3 Is+ 0:00.01 /usr/libexec/getty Pc ttyv3=0A= 231 v4 Is+ 0:00.00 /usr/libexec/getty Pc ttyv4=0A= 232 v5 Is+ 0:00.00 /usr/libexec/getty Pc ttyv5=0A= 233 v6 Is+ 0:00.00 /usr/libexec/getty Pc ttyv6=0A= 234 v7 Is+ 0:00.00 /usr/libexec/getty Pc ttyv7=0A= ------=_NextPart_000_000E_01C08602.DE1A5C60-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 24 9:44:36 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 9F3C937B401 for ; Wed, 24 Jan 2001 09:44:17 -0800 (PST) Received: from [203.164.12.28] by www.quake.com.au (NTMail 4.30.0012/AH9370.63.d1acf55c) with ESMTP id yrvsaaaa for ; Thu, 25 Jan 2001 04:52:50 +1100 Message-ID: <3A6F1476.F0C80D6A@quake.com.au> Date: Thu, 25 Jan 2001 04:44:22 +1100 From: Kal Torak X-Mailer: Mozilla 4.73 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Luc Morin Cc: freebsd-stable@freebsd.org Subject: Re: Network stops working References: <001001c08628$8db16180$9d8fc918@videotron.ca> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Luc Morin wrote: > > Hi, > > I have recently started experiencing network problems on my -stable box. > > The last cvsup dates a few weeks back, and everything was working fine up until a few days ago. > > Strangest thing is that everything works just fine under Win98, and that when I reboot under FreeBSD, network will be ok for a few minutes and then hang. After that, I can't even ping my gateway. > > I have an NE2000 clone (ed driver), and I use a cable modem to connect to the Internet. > > At this point, I'm only asking if anyone else has experienced those problems. > > As I have to write my e-amil under Win98, I don't have access right now to my FreeBSD partitions. I will happilly provide detailed information if this problem is not already know and cared for. > > Thansk all, > > Luc Morin I just love mail thats quoted printable and in html, its just so easy to read... Besides the obvious problems with your mail client, you need to provide some more info, e.g.. uname -a , dmesg and any errors generated would be helpful... I seem to remember some problems similar to this one before, you should search the mail archives, if no joy come back with more info and readable mail... Netscape mail might suck, but its better than outlook! Kal. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 24 9:44:40 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 66F4337B402; Wed, 24 Jan 2001 09:44:18 -0800 (PST) Received: from localhost (swb@localhost) by accord.grasslake.net (8.11.1/8.11.1) with ESMTP id f0OHeSZ04167; Wed, 24 Jan 2001 11:40:28 -0600 (CST) (envelope-from swb@accord.grasslake.net) Date: Wed, 24 Jan 2001 11:40:28 -0600 (CST) From: Shawn Barnhart To: Kris Kennaway Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Non-sequential one-time passwords? In-Reply-To: <20010123205759.C26378@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 Tue, 23 Jan 2001, Kris Kennaway wrote: > Nope. There are security implications to doing this anyway..this would > partly defeat the protection afforded by OTP schemes. I presume the security implications are algorithmic to the S/Key system, and not just the risk associated with N "good" passwords available at any one time. Because as far as I'm concerned, having N good one-time passwords in the hands of the internal people that will pass them out is less risky than handing out a "permanent" password. > What you need is to teach your users how to calculate password > challenge responses themselves, either using one of the FreeBSD tools > or an online javascript calculator (these exist, but I don't have a > URL handy). This is as simple as pasting the OTP challenge into a > website and entering their passphrase, then pasting the response in. I agree. But then again, this is a group that as a whole finds basic Macintosh tasks challenging, and the people who would use this are as of yet unknown to me or our organization, so there's no "advance" teaching possible. Trying to explain why a publicly writable and readable FTP site was a bad idea in the first place was a challenge itself. > Providing your users with a list of the next n passwords they will > need to use is only a convenience, they can do it on demand when > presented with the login challenge, given an available OTP calculator. With any normal group of people, yes. Not with this lot. -- swb@grasslake.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 24 10:10:36 2001 Delivered-To: freebsd-stable@freebsd.org Received: from c014.sfo.cp.net (c014-h017.c014.sfo.cp.net [209.228.12.81]) by hub.freebsd.org (Postfix) with SMTP id 8386E37B698 for ; Wed, 24 Jan 2001 10:10:16 -0800 (PST) Received: (cpmta 8923 invoked from network); 24 Jan 2001 10:10:08 -0800 Received: from d8c81e5f.dsl.flashcom.net (HELO quadrajet.flashcom.com) (216.200.30.95) by smtp.flashcom.net (209.228.12.81) with SMTP; 24 Jan 2001 10:10:08 -0800 X-Sent: 24 Jan 2001 18:10:08 GMT Received: (from guy@localhost) by quadrajet.flashcom.com (8.9.3/8.9.3) id KAA00373; Wed, 24 Jan 2001 10:10:07 -0800 (PST) (envelope-from gharris) Date: Wed, 24 Jan 2001 10:10:07 -0800 From: Guy Harris To: Mike Smith Cc: Guy Harris , Matthias Andree , Linux NFS mailing list , FreeBSD Stable Subject: Re: [NFS] Incompatible: FreeBSD 4.2 client, Linux 2.2.18 nfsv3 server, read-only export Message-ID: <20010124101007.A344@quadrajet.flashcom.com> References: <20010124001701.F344@quadrajet.flashcom.com> <200101241104.f0OB4sS10071@mass.dis.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <200101241104.f0OB4sS10071@mass.dis.org>; from msmith@freebsd.org on Wed, Jan 24, 2001 at 03:04:54AM -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 24, 2001 at 03:04:54AM -0800, Mike Smith wrote: > I'm not sure that the v3 specification actually cares about telling the > client "why", It doesn't, which I think may have been a mistake. > > For example, a UNIX "open()" call that calls an "access" vnode operation > > couldn't, if that file is mounted over NFS, find out that the open for > > writing is forbidden because the file system is read-only; even if > > that's the reason, the answer you get back is probably EACCES (that's > > what happens in the Solaris NFS, for example). > > This would be more or less what I'd expect. From the client's point of > view, returning "this is a read-only filesystem" is not very useful > anyway. What's a read-only filesystem? The NFS mount? The filesystem > backing the mount? I'm not sure "Permission denied" is all that useful, either; if the file has permissions rw-r--r-- and is owned by me, "Permission denied" is a bit of a weird error - I'd rather have the message the program shows me or logs to a file or whatever say "Read-only file system", as that tells me that the underlying problem is that *something* is read-only, even if it doesn't tell me whether it's the client machine's fault for NFS-mounting it read-only or the server's fault for {locally mounting it, exporting it} read-only. > I still don't really understand why the Linux code would return EROFS; Because it's buggy. > In the meantime, I'd also ask the Linux NFS maintainers (if they're > listening) to consider altering their server's behaviour just for the > sake of correctness (if it hasn't already been done subsequent to this > relatively ancient release). 2.4.0, which is definitely not an ancient release, still appears, from looking at the code in question, to have that buggy behavior. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 24 10:28:25 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 1A50737B6B5 for ; Wed, 24 Jan 2001 10:28:03 -0800 (PST) Received: (from dillon@localhost) by earth.backplane.com (8.11.1/8.9.3) id f0OIS2m68965; Wed, 24 Jan 2001 10:28:02 -0800 (PST) (envelope-from dillon) Date: Wed, 24 Jan 2001 10:28:02 -0800 (PST) From: Matt Dillon Message-Id: <200101241828.f0OIS2m68965@earth.backplane.com> To: Guy Harris Cc: Matthias Andree , Guy Harris , Linux NFS mailing list , FreeBSD Stable Subject: Re: [NFS] Incompatible: FreeBSD 4.2 client, Linux 2.2.18 nfsv3 server, read-only export References: <20010123015612.H345@quadrajet.flashcom.com> <20010123162930.B5443@emma1.emma.line.org> <20010123111005.D344@quadrajet.flashcom.com> <20010124001701.F344@quadrajet.flashcom.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG All this discussion over the right way to do ACCESS is moot. The NFSv3 protocol docs are absolutely clear on how ACCESS is supposed to work, and if Linux wants to be NFSv3 interoperable it has to follow the protocol. The FreeBSD client is following the protocol properly... it just happens to use more of the documented protocol then Solaris does, to good effect I might add. Over the last few years ocassional protocol bugs have cropped up in FreeBSD - and we've fixed them. For example, we weren't handling O_EXCL file creation under NFSv3 properly (just recently fixed in the last two months), and this caused solaris clients in default configurations to error out on files created with O_EXCL from FreeBSD clients. An example of a bug the other way around -- Solaris clients don't handle directory scan restarts properly. It turned out that the FreeBSD server could relax a certain error return (two lines of code) to fix solaris clients, while still keeping within protocol parameters. We did that in the name of interoperability because it was trivial and didn't impact performance. Because of this work, FreeBSD's NFSv3 implementation is interoperable with just about everything else out there. It's rep is well deserved. This particular problem, however, is entirely Linux's problem to fix. We are not going to rewrite our properly implemented access cache in order to workaround a linux NFSv3 server bug that can be fixed trivially in Linux. You don't have to like the NFSv3 protocol spec -- heavens knows there are big pieces of it that I don't like. But you do have to follow it if you want interoperability with non-Linux NFS servers. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 24 10:41:59 2001 Delivered-To: freebsd-stable@freebsd.org Received: from c014.sfo.cp.net (c014-h003.c014.sfo.cp.net [209.228.12.67]) by hub.freebsd.org (Postfix) with SMTP id E830E37B400 for ; Wed, 24 Jan 2001 10:41:42 -0800 (PST) Received: (cpmta 27096 invoked from network); 24 Jan 2001 10:31:04 -0800 Received: from d8c81e5f.dsl.flashcom.net (HELO quadrajet.flashcom.com) (216.200.30.95) by smtp.flashcom.net (209.228.12.67) with SMTP; 24 Jan 2001 10:31:04 -0800 X-Sent: 24 Jan 2001 18:31:04 GMT Received: (from guy@localhost) by quadrajet.flashcom.com (8.9.3/8.9.3) id KAA00449; Wed, 24 Jan 2001 10:31:03 -0800 (PST) (envelope-from gharris) Date: Wed, 24 Jan 2001 10:31:03 -0800 From: Guy Harris To: Matt Dillon Cc: Guy Harris , Matthias Andree , Linux NFS mailing list , FreeBSD Stable Subject: Re: [NFS] Incompatible: FreeBSD 4.2 client, Linux 2.2.18 nfsv3 server, read-only export Message-ID: <20010124103103.E344@quadrajet.flashcom.com> References: <20010123015612.H345@quadrajet.flashcom.com> <20010123162930.B5443@emma1.emma.line.org> <20010123111005.D344@quadrajet.flashcom.com> <20010124001701.F344@quadrajet.flashcom.com> <200101241828.f0OIS2m68965@earth.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <200101241828.f0OIS2m68965@earth.backplane.com>; from dillon@earth.backplane.com on Wed, Jan 24, 2001 at 10:28:02AM -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 24, 2001 at 10:28:02AM -0800, Matt Dillon wrote: > This particular problem, however, is entirely Linux's problem to fix. Umm, could somebody *PLEASE* show me *ANY* place where I argued that it wasn't a Linux bug? I can show at least one mail message where I said it *WAS* a Linux bug.... (Heck, are there any places where *anybody* argued that this wasn't a Linux bug?) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 24 10:46:50 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 1A35837B69C for ; Wed, 24 Jan 2001 10:46:23 -0800 (PST) Received: (from dillon@localhost) by earth.backplane.com (8.11.1/8.9.3) id f0OIkMl69319; Wed, 24 Jan 2001 10:46:22 -0800 (PST) (envelope-from dillon) Date: Wed, 24 Jan 2001 10:46:22 -0800 (PST) From: Matt Dillon Message-Id: <200101241846.f0OIkMl69319@earth.backplane.com> To: Guy Harris Cc: Guy Harris , Matthias Andree , Linux NFS mailing list , FreeBSD Stable Subject: Re: [NFS] Incompatible: FreeBSD 4.2 client, Linux 2.2.18 nfsv3 server, read-only export References: <20010123015612.H345@quadrajet.flashcom.com> <20010123162930.B5443@emma1.emma.line.org> <20010123111005.D344@quadrajet.flashcom.com> <20010124001701.F344@quadrajet.flashcom.com> <200101241828.f0OIS2m68965@earth.backplane.com> <20010124103103.E344@quadrajet.flashcom.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :On Wed, Jan 24, 2001 at 10:28:02AM -0800, Matt Dillon wrote: :> This particular problem, however, is entirely Linux's problem to fix. : :Umm, could somebody *PLEASE* show me *ANY* place where I argued that it :wasn't a Linux bug? I can show at least one mail message where I :said it *WAS* a Linux bug.... : :(Heck, are there any places where *anybody* argued that this wasn't a :Linux bug?) I didn't mean to say that someone argued it wasn't :-). I'm just saying that in the world of interoperability, it may actually be more of a problem hacking a solution into the FreeBSD client side then waiting for a solution on the Linux side. Even though a FreeBSD hack could be made to work, introducing that sort of pollution into the client code will only make interoperability testing between various systems (Linux, FreeBSD, solaris, NetApp, HPUX, and a host of other systems) more difficult and less definitive. NFSv3 is an industry standard today mainly because vendors have worked hard towards fixing interoperability problems, and one of the things that makes this possible is to enforce error reporting & failure conditions on the client-side. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 24 10:47: 5 2001 Delivered-To: freebsd-stable@freebsd.org Received: from c014.sfo.cp.net (c014-h017.c014.sfo.cp.net [209.228.12.81]) by hub.freebsd.org (Postfix) with SMTP id 01BE337B698 for ; Wed, 24 Jan 2001 10:46:32 -0800 (PST) Received: (cpmta 25273 invoked from network); 24 Jan 2001 10:42:17 -0800 Received: from d8c81e5f.dsl.flashcom.net (HELO quadrajet.flashcom.com) (216.200.30.95) by smtp.flashcom.net (209.228.12.81) with SMTP; 24 Jan 2001 10:42:17 -0800 X-Sent: 24 Jan 2001 18:42:17 GMT Received: (from guy@localhost) by quadrajet.flashcom.com (8.9.3/8.9.3) id KAA00488; Wed, 24 Jan 2001 10:42:16 -0800 (PST) (envelope-from gharris) Date: Wed, 24 Jan 2001 10:42:16 -0800 From: Guy Harris To: Mike Smith Cc: Guy Harris , Matthias Andree , Linux NFS mailing list , FreeBSD Stable Subject: Re: [NFS] Incompatible: FreeBSD 4.2 client, Linux 2.2.18 nfsv3 server, read-only export Message-ID: <20010124104216.F344@quadrajet.flashcom.com> References: <200101241104.f0OB4sS10071@mass.dis.org> <200101241117.f0OBH7S10154@mass.dis.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <200101241117.f0OBH7S10154@mass.dis.org>; from msmith@freebsd.org on Wed, Jan 24, 2001 at 03:17:07AM -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 24, 2001 at 03:17:07AM -0800, Mike Smith wrote: Content-Description: nfs_vnops.diff > --- /sys/nfs/nfs_vnops.c Fri Jan 12 14:15:00 2001 > +++ nfs_vnops.c Wed Jan 24 03:01:52 2001 > @@ -387,6 +387,14 @@ > */ > nfsstats.accesscache_misses++; > error = nfs3_access_otw(vp, wmode, ap->a_p,ap->a_cred); > + /* > + * Linux server may return EROFS despite this being > + * only an ACCESS rpc if we are asking about bits that > + * might allow us to write to the FS. The workaround > + * is to ignore EROFS as a return here. > + */ > + if (error == EROFS) > + error = 0; At least from looking at the Linux 2.2.18 code, if you get EROFS back from the Linux server, the actual set of access bits you get back won't have the right bits set; "nfsd_access()" just jumps to "out:" if it gets a "read-only file system" error, and that doesn't set "*access" to the result. If you do want to work around the Linux bug, you'd probably have to send another ACCESS request over the wire, with the write bits turned off; I'm not sure whether that's worth the effort or not. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 24 10:57:24 2001 Delivered-To: freebsd-stable@freebsd.org Received: from c014.sfo.cp.net (c014-h023.c014.sfo.cp.net [209.228.12.87]) by hub.freebsd.org (Postfix) with SMTP id 791EF37B402 for ; Wed, 24 Jan 2001 10:57:05 -0800 (PST) Received: (cpmta 15354 invoked from network); 24 Jan 2001 10:57:04 -0800 Received: from d8c81e5f.dsl.flashcom.net (HELO quadrajet.flashcom.com) (216.200.30.95) by smtp.flashcom.net (209.228.12.87) with SMTP; 24 Jan 2001 10:57:04 -0800 X-Sent: 24 Jan 2001 18:57:04 GMT Received: (from guy@localhost) by quadrajet.flashcom.com (8.9.3/8.9.3) id KAA00535; Wed, 24 Jan 2001 10:57:03 -0800 (PST) (envelope-from gharris) Date: Wed, 24 Jan 2001 10:57:03 -0800 From: Guy Harris To: Guy Harris Cc: Mike Smith , Matthias Andree , Linux NFS mailing list , FreeBSD Stable Subject: Re: [NFS] Incompatible: FreeBSD 4.2 client, Linux 2.2.18 nfsv3 server, read-only export Message-ID: <20010124105703.G344@quadrajet.flashcom.com> References: <200101241104.f0OB4sS10071@mass.dis.org> <200101241117.f0OBH7S10154@mass.dis.org> <20010124104216.F344@quadrajet.flashcom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <20010124104216.F344@quadrajet.flashcom.com>; from gharris@flashcom.net on Wed, Jan 24, 2001 at 10:42:16AM -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 24, 2001 at 10:42:16AM -0800, Guy Harris wrote: > If you do want to work around the Linux bug, you'd probably have to send > another ACCESS request over the wire, with the write bits turned off; > I'm not sure whether that's worth the effort or not. An alternative patch is *** vfs.c.dist Sun Dec 10 16:49:44 2000 --- vfs.c Wed Jan 24 10:54:15 2001 *************** *** 448,454 **** error = nfsd_permission(export, dentry, (map->how | NO_OWNER_OVERRIDE)); if (error == 0) result |= map->access; ! else if ((error == nfserr_perm) || (error == nfserr_acces)) { /* * This access type is denyed; but the * access query itself succeeds. --- 448,455 ---- error = nfsd_permission(export, dentry, (map->how | NO_OWNER_OVERRIDE)); if (error == 0) result |= map->access; ! else if ((error == nfserr_perm) || (error == nfserr_acces) || ! (error == nfserr_rofs)) { /* * This access type is denyed; but the * access query itself succeeds. but you apply that one to the Linux NFS server code (in "fs/nfsd/vfs.c"), which should fix the Linux server bug. (I haven't tried it, or compiled it, as my machine is currently running FreeBSD, but I think it should, at least compile, and I expect it to solve the problem.) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 24 11: 2:24 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 D8B4D37B400 for ; Wed, 24 Jan 2001 11:02:03 -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 f0OIxLo14908; Wed, 24 Jan 2001 18:59:21 GMT From: Tony Byrne To: Andrew J Caines Cc: freebsd-stable@freebsd.org Subject: Re: syslogd throwing a hissy fit Date: Wed, 24 Jan 2001 19:06:36 +0000 Organization: Nua Ltd. Message-ID: <7q9u6t0tkj5ktplad6k8468koar3j8jvi9@4ax.com> References: <20010121021039.A442@hal9000.bsdonline.org> In-Reply-To: <20010121021039.A442@hal9000.bsdonline.org> 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 =46olks, I'm seeing this behaviour too, as of my make world of today (using up to date CVSup'd sources). Has anyone found the source of the problem. It's bloody annoying. I've had to kill syslogd. Regards, Tony. On Sun, 21 Jan 2001 02:10:40 -0500, you wrote: >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 Jan 21 01:22:06 hal9000 /kernel: :21:51 = hal9000 /kernel:=20 >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=3Drw, 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 >This is even wierder: > ># truss dmesg >:05 >Here's some extra system info. I'll happily provide more on request. > ># uname -a >FreeBSD hal9000.bsdonline.org 4.2-STABLE FreeBSD 4.2-STABLE #0: Sat Jan = 20 18:32 > ># egrep syslogd /etc/rc.conf # Usually YES, of course >syslogd_enable=3D"NO" # Run syslog daemon (or NO). >syslogd_flags=3D"-s -vv -a 127.0.0.1:*" # Flags to syslogd (if = enabled). > ># ls -l /dev/*log /var/run/*log >ls: /var/run/*log: No such file or directory >crw------- 1 root wheel 7, 0 Jan 21 00:10 /dev/klog >lrwxr-xr-x 1 root wheel 12 Sep 9 15:16 /dev/log -> = /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- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 24 11:13: 1 2001 Delivered-To: freebsd-stable@freebsd.org Received: from gofur.oct.co.za (gofur.oct.co.za [196.31.78.38]) by hub.freebsd.org (Postfix) with ESMTP id 5BCC137B404 for ; Wed, 24 Jan 2001 11:12:38 -0800 (PST) Received: from alrpc (alrpc.oct.co.za [196.31.72.106]) by gofur.oct.co.za (8.11.0/8.11.0) with SMTP id f0OJCZx76512 for ; Wed, 24 Jan 2001 21:12:35 +0200 (SAST) (envelope-from tonyr@cs-cape.co.za) Reply-To: From: "Antony Russell" To: Subject: Sound on Intel Easton Date: Wed, 24 Jan 2001 21:12:34 +0200 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Importance: Normal Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi I am running FreeBSD 4.2-STABLE (cvsup'd 21 Jan) on an Intel Easton (D815EEA) board with onboard sound and am having problem getting the on-board sound working. The sound is reported to be AC'97 v1.03 compliant. I have included the following (from LINT) in my kernel configuration file...... # For non-pnp sound cards with no bridge drivers only: device pcm0 at isa? irq 10 drq 1 flags 0x0 # # For PnP/PCI sound cards device pcm # For non-PnP cards: device sbc0 at isa? port 0x220 irq 5 drq 1 flags 0x15 device gusc0 at isa? port 0x220 irq 5 drq 1 flags 0x13 # Not controlled by `snd' device pca0 at isa? port IO_TIMER1 and here is the 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: Wed Jan 24 20:38:44 SAST 2001 root@cfggate.cfg.co.za:/usr/obj/usr/src/sys/CFG Timecounter "i8254" frequency 1193182 Hz CPU: Pentium III/Pentium III Xeon/Celeron (697.88-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x683 Stepping = 3 Features=0x387f9ff real memory = 65798144 (64256K bytes) avail memory = 60321792 (58908K bytes) Preloaded elf kernel "kernel" at 0xc034f000. Pentium Pro MTRR support enabled md0: Malloc disk npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pci0: at 2.0 irq 11 pcib1: at device 30.0 on pci0 pci1: on pcib1 fxp0: port 0xde80-0xdebf mem 0xff8fe000-0xff8fefff irq 11 at device 8.0 on pci1 fxp0: Ethernet address 00:03:47:3e:c9:25 fxp1: port 0xdf00-0xdf3f mem 0xff700000-0xff7fffff,0xff8ff000-0xff8fffff irq 11 at device 9.0 on pci1 fxp1: Ethernet address 00:02:b3:09:c3:a0 isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0xffa0-0xffaf at device 31.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 pci0: at 31.2 irq 11 pci0: (vendor=0x8086, dev=0x2443) at 31.3 irq 9 pci0: at 31.4 irq 10 pci0: (vendor=0x8086, dev=0x2445) at 31.5 irq 9 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 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 pca0 at port 0x40 on isa0 unknown: can't assign resources unknown: can't assign resources pca1: at port 0x61 on isa0 unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources ad0: 9768MB [19846/16/63] at ata0-master UDMA66 Mounting root from ufs:/dev/ad0s1a Any suggestions would be greatly appreciated Tony Russell Technical Director Clarotech Consulting To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 24 11:18:57 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 2362337B404 for ; Wed, 24 Jan 2001 11:18:40 -0800 (PST) Received: from darkstar (darkstar.rings [10.2.4.16]) by vilnya.demon.co.uk (Postfix) with SMTP id 2665ED9B8; Wed, 24 Jan 2001 19:18:38 +0000 (GMT) Message-ID: <03ac01c08639$f2982910$1004020a@darkstar> From: "Cameron Grant" To: , References: Subject: Re: Sound on Intel Easton Date: Wed, 24 Jan 2001 19:15:00 -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 > Any suggestions would be greatly appreciated not yet supported. -cg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 24 12:12: 1 2001 Delivered-To: freebsd-stable@freebsd.org Received: from luke.immure.com (luke.immure.com [207.8.42.74]) by hub.freebsd.org (Postfix) with ESMTP id EF80D37B6A4 for ; Wed, 24 Jan 2001 12:11:43 -0800 (PST) Received: (from bob@localhost) by luke.immure.com (8.11.1/8.11.1) id f0OKBQi99174; Wed, 24 Jan 2001 14:11:26 -0600 (CST) (envelope-from bob) Date: Wed, 24 Jan 2001 14:11:26 -0600 From: Bob Willcox To: Bernhard Beck Cc: "Thomas T. Veldhouse" , freebsd-stable@FreeBSD.ORG Subject: Re: Athlon Thunderbird 700 w. Asus K7M Motherboard vs. FreeBSD 4.2 Message-ID: <20010124141126.A97916@luke.immure.com> Reply-To: Bob Willcox References: <3A5F1F43.EE70CB3C@inode.at> <20010112161044.A97484@walton.maths.tcd.ie> <009e01c07cb7$132d9e30$3028680a@tgt.com> <3A5F3951.9932EED5@mindmaker.com> <00d101c07cbe$4f1f84b0$3028680a@tgt.com> <3A5F95AF.F8B120D4@mindmaker.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3A5F95AF.F8B120D4@mindmaker.com>; from bbeck@mindmaker.com on Fri, Jan 12, 2001 at 03:39:27PM -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I can attest to the fact that Slot A thunderbirds do exist. I own 3 of them (one 900 and 2 700 MHz). I guess I was fortunate that my Slot A thuderbirds worked properly (all running FreeBSD) in the MBs (MSI and Abit) that I have, though I have also heard that problems exist with some MBs Bob On Fri, Jan 12, 2001 at 03:39:27PM -0800, Bernhard Beck wrote: > According to an article published in c't 14/2000, page 32 (online at > http://www.heise.de/ct/00/14/032/default.shtml, use Altavista's > Babelfish to translate), Slot A Thunderbirds do exist. In a nutshell > among other things AMD slightly changed the bus interface design on the > Thunderbirds so that you need chipsets like VIA KT133, KM133 or AMD 760. > But under certain conditions the Thunderbird can also work with a KX133 > or the Irongate chipset. > There is a nice table at the end of the article listing a few Slot A > motherboards and if they worked or not with the two sample Slot A > Thunderbirds c't had available in their lab at that time. > Michael's Asus K7M with Irongate chipset is listed as working with the > exact same BIOS version. ... snip ... -- Bob Willcox The reason we come up with new versions is not to bob@vieo.com fix bugs. It's absolutely not. Austin, TX -- Bill Gates To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 24 12:16:33 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id BB70F37B6A0 for ; Wed, 24 Jan 2001 12:16:13 -0800 (PST) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.1/8.11.1) with ESMTP id f0OKUTI00828; Wed, 24 Jan 2001 12:30:29 -0800 (PST) (envelope-from msmith@mass.dis.org) Message-Id: <200101242030.f0OKUTI00828@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Guy Harris Cc: Matthias Andree , Linux NFS mailing list , FreeBSD Stable Subject: Re: [NFS] Incompatible: FreeBSD 4.2 client, Linux 2.2.18 nfsv3 server, read-only export In-reply-to: Your message of "Wed, 24 Jan 2001 10:42:16 PST." <20010124104216.F344@quadrajet.flashcom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 24 Jan 2001 12:30:29 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > At least from looking at the Linux 2.2.18 code, if you get EROFS back > from the Linux server, the actual set of access bits you get back won't > have the right bits set; "nfsd_access()" just jumps to "out:" if it gets > a "read-only file system" error, and that doesn't set "*access" to the > result. Oh. "Joy". > If you do want to work around the Linux bug, you'd probably have to send > another ACCESS request over the wire, with the write bits turned off; > I'm not sure whether that's worth the effort or not. Based on that; no. I think if people want to run v3 against a Linux server, they will just have to turn the ACCESS cache off. In the meantime, is there any constructive way we can encourage the Linux NFS folks to fix this behaviour? -- ... 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 24 12:19:22 2001 Delivered-To: freebsd-stable@freebsd.org Received: from rainbow.samovar.ru (unknown [192.124.176.109]) by hub.freebsd.org (Postfix) with ESMTP id E3D2637B6A0 for ; Wed, 24 Jan 2001 12:19:04 -0800 (PST) Received: from mikhail ([212.12.71.30]) by rainbow.samovar.ru (8.9.3/8.9.3) with SMTP id XAA91777 for ; Wed, 24 Jan 2001 23:18:47 +0300 (MSK) Message-ID: <024301c08642$e09fb3a0$210aa8c0@mikhail> From: "Mikhail Kononenko" To: References: <03ac01c08639$f2982910$1004020a@darkstar> Subject: Re: EtherExpress100 on Intel Easton Date: Wed, 24 Jan 2001 23:18:52 +0300 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 Sorry, if this is offtopic here, but I could not get answer from native lists... Linux kernel-2.2.17 on D815EEAL (with integrated NIC). The driver used: eepro100. The card sporadically issues wait_for_command_done_timeout messages (many times in a row). Needless to say the network is unaccesible until it regains consciouseness... And I am trying to run a server... Does someone know _any_ clues as what might be wrong? (Please, don't say "The OS" :-) ) Thanks. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 24 12:22:44 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 C4CEB37B402 for ; Wed, 24 Jan 2001 12:22:26 -0800 (PST) Received: from HP2500B (veldy.net [64.1.117.28]) by veldy.net (Postfix) with SMTP id EFFA18C2C; Wed, 24 Jan 2001 14:21:55 -0600 (CST) Message-ID: <031e01c08643$0134c420$3028680a@tgt.com> From: "Thomas T. Veldhouse" To: "Bob Willcox" , "Bernhard Beck" Cc: References: <3A5F1F43.EE70CB3C@inode.at> <20010112161044.A97484@walton.maths.tcd.ie> <009e01c07cb7$132d9e30$3028680a@tgt.com> <3A5F3951.9932EED5@mindmaker.com> <00d101c07cbe$4f1f84b0$3028680a@tgt.com> <3A5F95AF.F8B120D4@mindmaker.com> <20010124141126.A97916@luke.immure.com> Subject: Re: Athlon Thunderbird 700 w. Asus K7M Motherboard vs. FreeBSD 4.2 Date: Wed, 24 Jan 2001 14:19:49 -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 Yes - I have since found that you are correct. I have found or heard rumor of many people out there (especially on EBAY) selling Athlons as a Thunderbird when in fact it was a classic. Usually, I have found this out when I specifically queried them about it - or they simply refused to answer. Tom Veldhouse veldy@veldy.net ----- Original Message ----- From: "Bob Willcox" To: "Bernhard Beck" Cc: "Thomas T. Veldhouse" ; Sent: Wednesday, January 24, 2001 2:11 PM Subject: Re: Athlon Thunderbird 700 w. Asus K7M Motherboard vs. FreeBSD 4.2 > I can attest to the fact that Slot A thunderbirds do exist. I own 3 of > them (one 900 and 2 700 MHz). I guess I was fortunate that my Slot A > thuderbirds worked properly (all running FreeBSD) in the MBs (MSI and > Abit) that I have, though I have also heard that problems exist with > some MBs > > Bob > > On Fri, Jan 12, 2001 at 03:39:27PM -0800, Bernhard Beck wrote: > > According to an article published in c't 14/2000, page 32 (online at > > http://www.heise.de/ct/00/14/032/default.shtml, use Altavista's > > Babelfish to translate), Slot A Thunderbirds do exist. In a nutshell > > among other things AMD slightly changed the bus interface design on the > > Thunderbirds so that you need chipsets like VIA KT133, KM133 or AMD 760. > > But under certain conditions the Thunderbird can also work with a KX133 > > or the Irongate chipset. > > There is a nice table at the end of the article listing a few Slot A > > motherboards and if they worked or not with the two sample Slot A > > Thunderbirds c't had available in their lab at that time. > > Michael's Asus K7M with Irongate chipset is listed as working with the > > exact same BIOS version. > > ... snip ... > > -- > Bob Willcox The reason we come up with new versions is not to > bob@vieo.com fix bugs. It's absolutely not. > Austin, TX -- Bill Gates > > > 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 24 12:25: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 0945437B400 for ; Wed, 24 Jan 2001 12:25:37 -0800 (PST) Received: (qmail 23894 invoked by uid 0); 24 Jan 2001 20:25:33 -0000 Received: from p3ee2162c.dip.t-dialin.net (HELO speedy.gsinet) (62.226.22.44) by mail.gmx.net (mp009-rz3) with SMTP; 24 Jan 2001 20:25:33 -0000 Received: (from sittig@localhost) by speedy.gsinet (8.8.8/8.8.8) id SAA30900 for freebsd-stable@freebsd.org; Wed, 24 Jan 2001 18:57:44 +0100 Date: Wed, 24 Jan 2001 18:57:44 +0100 From: Gerhard Sittig To: freebsd-stable@freebsd.org Subject: Re: Hard drive errors Message-ID: <20010124185744.K253@speedy.gsinet> Mail-Followup-To: freebsd-stable@freebsd.org References: <20010123174558.A427@gecko.eric.net.au> <3A6D4A30.806FCCFD@quake.com.au> <20010123202310.A72951@cokane.yi.org> <030601c085a8$491e5b20$931576d8@inethouston.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <030601c085a8$491e5b20$931576d8@inethouston.net>; from dwcjr@inethouston.net on Tue, Jan 23, 2001 at 07:52:19PM -0600 Organization: System Defenestrators Inc. Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jan 23, 2001 at 19:52 -0600, David W. Chapman Jr. wrote: > > Is freebsd any better at handling bad sectors/blocks than it > was around 2.2.8/3.0? Just curious, because I remember it not > handling them too good. I wouldn't think about it too long. Today's disks have their internal remapping without anyone outside noticing. Once you see errors outside (i.e. in your OS) internal capacity for recovery is *exhausted*. Your disk is damaged beyond acceptable limits once you start _noticing_ problems! Take these messages seriously and swap the device -- unless you don't care about the data ... virtually yours 82D1 9B9C 01DC 4FB4 D7B4 61BE 3F49 4F77 72DE DA76 Gerhard Sittig true | mail -s "get gpg key" Gerhard.Sittig@gmx.net -- If you don't understand or are scared by any of the above ask your parents or an adult to help you. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 24 13: 0:17 2001 Delivered-To: freebsd-stable@freebsd.org Received: from luke.immure.com (luke.immure.com [207.8.42.74]) by hub.freebsd.org (Postfix) with ESMTP id 5457C37B6B0 for ; Wed, 24 Jan 2001 12:59:53 -0800 (PST) Received: (from bob@localhost) by luke.immure.com (8.11.1/8.11.1) id f0OKxli99994; Wed, 24 Jan 2001 14:59:47 -0600 (CST) (envelope-from bob) Date: Wed, 24 Jan 2001 14:59:47 -0600 From: Bob Willcox To: "Thomas T. Veldhouse" Cc: Bernhard Beck , freebsd-stable@FreeBSD.ORG Subject: Re: Athlon Thunderbird 700 w. Asus K7M Motherboard vs. FreeBSD 4.2 Message-ID: <20010124145947.C97916@luke.immure.com> Reply-To: Bob Willcox References: <3A5F1F43.EE70CB3C@inode.at> <20010112161044.A97484@walton.maths.tcd.ie> <009e01c07cb7$132d9e30$3028680a@tgt.com> <3A5F3951.9932EED5@mindmaker.com> <00d101c07cbe$4f1f84b0$3028680a@tgt.com> <3A5F95AF.F8B120D4@mindmaker.com> <20010124141126.A97916@luke.immure.com> <031e01c08643$0134c420$3028680a@tgt.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <031e01c08643$0134c420$3028680a@tgt.com>; from veldy@veldy.net on Wed, Jan 24, 2001 at 02:19:49PM -0600 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I think that there is alot of confusion about this. If you look closely at the code printed on the top of the processor and compare it to the specifications for the code on the AMD web site (somewhere, I don't remember exactly where) you can definitively determine whether or not a particular CPU is a Thunderbird or not. You can also look inside the cover for the L2 cache chips on either side of the CPU chip. If they aren't there, it's a Thunderbird. Bob On Wed, Jan 24, 2001 at 02:19:49PM -0600, Thomas T. Veldhouse wrote: > Yes - I have since found that you are correct. I have found or heard rumor > of many people out there (especially on EBAY) selling Athlons as a > Thunderbird when in fact it was a classic. Usually, I have found this out > when I specifically queried them about it - or they simply refused to > answer. > > Tom Veldhouse > veldy@veldy.net > > ----- Original Message ----- > From: "Bob Willcox" > To: "Bernhard Beck" > Cc: "Thomas T. Veldhouse" ; > Sent: Wednesday, January 24, 2001 2:11 PM > Subject: Re: Athlon Thunderbird 700 w. Asus K7M Motherboard vs. FreeBSD 4.2 > > > > I can attest to the fact that Slot A thunderbirds do exist. I own 3 of > > them (one 900 and 2 700 MHz). I guess I was fortunate that my Slot A > > thuderbirds worked properly (all running FreeBSD) in the MBs (MSI and > > Abit) that I have, though I have also heard that problems exist with > > some MBs > > > > Bob > > > > On Fri, Jan 12, 2001 at 03:39:27PM -0800, Bernhard Beck wrote: > > > According to an article published in c't 14/2000, page 32 (online at > > > http://www.heise.de/ct/00/14/032/default.shtml, use Altavista's > > > Babelfish to translate), Slot A Thunderbirds do exist. In a nutshell > > > among other things AMD slightly changed the bus interface design on the > > > Thunderbirds so that you need chipsets like VIA KT133, KM133 or AMD 760. > > > But under certain conditions the Thunderbird can also work with a KX133 > > > or the Irongate chipset. > > > There is a nice table at the end of the article listing a few Slot A > > > motherboards and if they worked or not with the two sample Slot A > > > Thunderbirds c't had available in their lab at that time. > > > Michael's Asus K7M with Irongate chipset is listed as working with the > > > exact same BIOS version. > > > > ... snip ... > > > > -- > > Bob Willcox The reason we come up with new versions is not to > > bob@vieo.com fix bugs. It's absolutely not. > > Austin, TX -- Bill Gates > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-stable" in the body of the message > > -- Bob Willcox The reason we come up with new versions is not to bob@vieo.com fix bugs. It's absolutely not. Austin, TX -- Bill Gates To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 24 13:11:37 2001 Delivered-To: freebsd-stable@freebsd.org Received: from p133.inode.at (p133.inode.at [195.58.160.3]) by hub.freebsd.org (Postfix) with ESMTP id D018037B401 for ; Wed, 24 Jan 2001 13:11:18 -0800 (PST) Received: from inode.at (line48.adsl.wien.inode.at [213.229.7.48]) by p133.inode.at (8.11.1/8.10.0.0) with ESMTP id f0OLBGh22526 for ; Wed, 24 Jan 2001 22:11:16 +0100 Message-ID: <3A6F4533.2DEE76D@inode.at> Date: Wed, 24 Jan 2001 22:12:19 +0100 From: Michael Bretterklieber X-Mailer: Mozilla 4.75 [de] (Windows NT 5.0; U) X-Accept-Language: de MIME-Version: 1.0 To: stable@FreeBSD.org Subject: Re: Athlon Thunderbird 700 w. Asus K7M Motherboard vs. FreeBSD 4.2 References: <3A5F1F43.EE70CB3C@inode.at> <20010112161044.A97484@walton.maths.tcd.ie> <009e01c07cb7$132d9e30$3028680a@tgt.com> <3A5F3951.9932EED5@mindmaker.com> <00d101c07cbe$4f1f84b0$3028680a@tgt.com> <3A5F95AF.F8B120D4@mindmaker.com> <20010124141126.A97916@luke.immure.com> <031e01c08643$0134c420$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 Hi, I don't wanna be impolite, but my problem is not, if there exists SlotA TB or not. The points is, that my hardware works correctly with W2k and W98, but not with FreeBSD :-(, but I'd like to work with FreeBSD :-). I hope, that somone from the FreeBSD-community can help. bye, -- -------------------------------------- E-mail: Michael.Bretterklieber@jawa.at ---------------------------- JAWA MANAGEMENT und SOFTWARE Liebenauer Hauptstr. 200 A-8041 GRAZ Tel: ++43-(0)316-403274-12 Fax: ++43-(0)316-403274-10 GSM: ++43-(0)676-93 96 698 homepage: http://www.jawa.at --------- privat ----------- E-mail: mbretter@inode.at homepage: http://www.inode.at/mbretter -------------------------------------- Sorry for my bad english! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 24 13:40: 4 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 A45BC37B400 for ; Wed, 24 Jan 2001 13:39:43 -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 f0OLaio17649; Wed, 24 Jan 2001 21:36:44 GMT From: Tony Byrne To: Tony Byrne Cc: Andrew J Caines , freebsd-stable@freebsd.org Subject: Re: syslogd throwing a hissy fit Date: Wed, 24 Jan 2001 21:43:59 +0000 Organization: Nua Ltd. Message-ID: References: <20010121021039.A442@hal9000.bsdonline.org> <7q9u6t0tkj5ktplad6k8468koar3j8jvi9@4ax.com> In-Reply-To: <7q9u6t0tkj5ktplad6k8468koar3j8jvi9@4ax.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 Andrew, I believe that I've narrowed down the problem to the point where someone with a better knowledge of the internal workings of syslogd should be able to pinpoint it: My last CVSup & build world pulled in the same MFC that your's did. Now I'm seeing the same strange behavior after the usual build and install. Regarding the MFC change to syslogd since our last CVSup: The comment by the committer seems to suggest that the changes introduced a new syslog facility called LOG_CONSOLE. They also mention that the change includes code to prevent messages with the LOG_CONSOLE facility from being sent to /dev/console. My investigations using "syslogd -v" show that the all of the looped and corrupt log lines that I am seeing are of the LOG_CONSOLE facility with the 'info' priority. (console.info) (14.6) It's my guess that syslogd is entering a tight loop whenever syslog.conf is configured so that a log message with facility LOG_CONSOLE is directed to /dev/console. The committer seems to have been aware of the problem, but maybe an incorrectly configured syslog.conf would circumvent the checks within the code? The work around to the problem is to ensure that syslog.conf does not send console.* to /dev/console. For me that involved replacing my local syslog.conf line: *.* /dev/console with something a little bit more conservative. Regards, Tony. On Wed, 24 Jan 2001 19:06:36 +0000, you wrote: >Folks, > >I'm seeing this behaviour too, as of my make world of today (using up to >date CVSup'd sources). Has anyone found the source of the problem. >It's bloody annoying. I've had to kill syslogd. > >Regards, > >> 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 >Jan 21 01:22:06 hal9000 /kernel: :21:51 = hal9000 /kernel:=20 >>Jan 21 01:22:06 hal9000 /kernel: :04 hal9000= /kernel: :48 hal9000 /kernel: Jan 21 01:21:48 = hal9000 /kernel: Jan 21 0 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 24 14:37:25 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 28F9837B400 for ; Wed, 24 Jan 2001 14:37:08 -0800 (PST) Received: from gosset.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 24 Jan 2001 22:37:06 +0000 (GMT) Date: Wed, 24 Jan 2001 22:37:05 +0000 From: David Malone To: Tony Byrne Cc: Andrew J Caines , freebsd-stable@freebsd.org Subject: Re: syslogd throwing a hissy fit Message-ID: <20010124223705.A92362@gosset.maths.tcd.ie> References: <20010121021039.A442@hal9000.bsdonline.org> <7q9u6t0tkj5ktplad6k8468koar3j8jvi9@4ax.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 tony@nua.ie on Wed, Jan 24, 2001 at 09:43:59PM +0000 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 24, 2001 at 09:43:59PM +0000, Tony Byrne wrote: > My investigations using "syslogd -v" show that the all of the looped and > corrupt log lines that I am seeing are of the LOG_CONSOLE facility with > the 'info' priority. (console.info) (14.6) > > It's my guess that syslogd is entering a tight loop whenever syslog.conf > is configured so that a log message with facility LOG_CONSOLE is > directed to /dev/console. The committer seems to have been aware of the > problem, but maybe an incorrectly configured syslog.conf would > circumvent the checks within the code? There should be code to prevent this looping, as you point out. Can you send me the output of syslogd -d while it's looping and I'll try to figure out what is going on. 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 24 14:38:33 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 63E3137B401 for ; Wed, 24 Jan 2001 14:38:16 -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 <20010124223815.NJFP12341.mail2.rdc1.il.home.com@marx.marvic.chum> for ; Wed, 24 Jan 2001 14:38:15 -0800 Received: (from vcardona@localhost) by marx.marvic.chum (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) id QAA12712 for freebsd-stable@FreeBSD.ORG; Wed, 24 Jan 2001 16:41:25 -0600 Date: Wed, 24 Jan 2001 16:41:25 -0600 From: "Victor R. Cardona" To: freebsd-stable@FreeBSD.ORG Subject: Re: Network stops working Message-ID: <20010124164125.A12612@home.com> Mail-Followup-To: freebsd-stable@FreeBSD.ORG References: <001001c08628$8db16180$9d8fc918@videotron.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <001001c08628$8db16180$9d8fc918@videotron.ca>; from luc_m@videotron.ca on Wed, Jan 24, 2001 at 12:10:29PM -0500 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 24, 2001 at 12:10:29PM -0500, Luc Morin wrote: > Hi, > > I have recently started experiencing network problems on my -stable box. > > The last cvsup dates a few weeks back, and everything was working fine up until a few days ago. > > Strangest thing is that everything works just fine under Win98, and that when I reboot under FreeBSD, network will be ok for a few minutes and then hang. After that, I can't even ping my gateway. > > I have an NE2000 clone (ed driver), and I use a cable modem to connect to the Internet. > > At this point, I'm only asking if anyone else has experienced those problems. > > As I have to write my e-amil under Win98, I don't have access right now to my FreeBSD partitions. I will happilly provide detailed information if this problem is not already know and cared for. By any chance are you running ipf/ipnat? I had something similar happen with my gateway. I never did find the cause, but I am sure it was either hardware or something with ipnat. -- Victor R. 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 Wed Jan 24 15:22:59 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 ABBA537B401 for ; Wed, 24 Jan 2001 15:22: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 f0ONJjo19077; Wed, 24 Jan 2001 23:19:45 GMT From: Tony Byrne To: David Malone Cc: Andrew J Caines , freebsd-stable@freebsd.org Subject: Re: syslogd throwing a hissy fit Date: Wed, 24 Jan 2001 23:27:01 +0000 Organization: Nua Ltd. Message-ID: <5qou6tkiba9jk6nbjepe9hn2g45hq560ep@4ax.com> References: <20010121021039.A442@hal9000.bsdonline.org> <7q9u6t0tkj5ktplad6k8468koar3j8jvi9@4ax.com> <20010124223705.A92362@gosset.maths.tcd.ie> In-Reply-To: <20010124223705.A92362@gosset.maths.tcd.ie> 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 Wed, 24 Jan 2001 22:37:05 +0000, you wrote: >On Wed, Jan 24, 2001 at 09:43:59PM +0000, Tony Byrne wrote: > >> My investigations using "syslogd -v" show that the all of the looped = and >> corrupt log lines that I am seeing are of the LOG_CONSOLE facility = with >> the 'info' priority. (console.info) (14.6) >>=20 >> It's my guess that syslogd is entering a tight loop whenever = syslog.conf >> is configured so that a log message with facility LOG_CONSOLE is >> directed to /dev/console. The committer seems to have been aware of = the >> problem, but maybe an incorrectly configured syslog.conf would >> circumvent the checks within the code? > >There should be code to prevent this looping, as you point out. >Can you send me the output of syslogd -d while it's looping and >I'll try to figure out what is going on. > > David. Here is the output that is going to the console and to my messages file: Jan 24 23:14:49 cerberus /kernel: Jan 24 23:14:49 cerberus /kernel: Jan 24 23:14:49 cerberus /kernel: Jan 24 23:14:49 cerberus /kernel: Jan 24 23:14:49 cerberus /kernel: Jan 24 23:14:49 cerberus /kernel: Jan 24 23:14:49 cerberus /kernel: Jan 24 23:14:4 9 cerberus /kernel: Jan 24 23:14:49 cerberus /kernel: Jan 24 23:14:48 cerberus /kernel: Jan 24 23:14:48 cerberus /kernel: Jan=20 24 23:14:48 cerberus /kernel: Jan 24 23:14:48 cerberus /kernel: Jan 24 23:14:48 cerberus /kernel: Jan 24 23:14:48 cerberus /ke rnel: Jan 24 23:14:48 cerberus /kernel: Jan 24 23:14:48 cerberus /kernel: Jan 24 23:14:48 cerberus /kernel: Jan 24 23:14:48 ce rberus /kernel: Jan 24 23:14:48 cerberus /kernel: Jan 24 23:14:48 cerberus /kernel: Jan 24 23:14:48 cerberus /kernel: Jan 24 2 3:14:48 cerberus /kernel: Jan 24 23:14:48 cerberus /kernel: Jan 24 23:14:48 cerberus /kernel: Jan 24 23:14:48 cerberus /kernel : Jan 24 23:14:47 cerberus /kernel: Jan 24 23:14:47 cerberus /kernel: Jan 24 23:14:47 cerberus /kernel: Jan 24 23:14:47 cerber us /kernel: Jan 24 23:14:47 cerberus /ker Note the lack of linefeeds and the corruption. The following is the output of 'syslogd -d'. The log messages are interspersed with the debug output: cerberus{tony}/var/log# syslogd -d off & running.... init cfline("*.* /var/log/messages", f, "*", "*") cfline("*.* @gamekeeper.merrion.nua.net", f, "*", "*") cfline("*.* /var/log/syslog.debug", f, "*", "*") cfline("*.info /dev/console", f, "*", "*") cfline("security.* /var/log/security", f, "*", "*") cfline("mail.info /var/log/maillog", f, "*", "*") cfline("lpr.info /var/log/lpd-errs", f, "*", "*") cfline("cron.* /var/log/cron", f, "*", "*") cfline("*.err root", f, "*", "*") cfline("*.notice;news.err root", f, "*", "*") cfline("*.alert root", f, "*", "*") cfline("*.emerg *", f, "*", "*") cfline("*.* /var/log/slip.log", f, "startslip", "*") cfline("*.* /var/log/ppp.log", f, "ppp", "*") 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 X FILE: /var/log/messages 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 X FORW: gamekeeper.merrion.nua.net 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 X FILE: /var/log/syslog.debug 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 X CONSOLE: /dev/console X X X X X X X X X X X X X 8 X X X X X X X X X X X FILE: /var/log/security X X 6 X X X X X X X X X X X X X X X X X X X X X X FILE: /var/log/maillog X X X X X X 6 X X X X X X X X X X X X X X X X X X FILE: /var/log/lpd-errs X X X X X X X X X 8 X X X X X X X X X X X X X X X FILE: /var/log/cron 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 X USERS: root,=20 5 5 5 5 5 5 5 3 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 X USERS: root,=20 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 X USERS: root,=20 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 X WALL:=20 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 X FILE: /var/log/slip.log (startslip) 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 X FILE: /var/log/ppp.log (ppp) logmsg: pri 56, flags 4, from cerberus, msg syslogd: restart Logging to FILE /var/log/messages Logging to FORW gamekeeper.merrion.nua.net Logging to FILE /var/log/syslog.debug Logging to CONSOLE /dev/console syslogd: restarted logmsg: pri 2, flags 17, from cerberus, msg :17:23 cerberus /kernel: Jan 24 23:17:23 cerberus /kernel: Jan 24 23:17:23 cerberus /kernel: Jan 24 23:17:23 cerberus syslogd: restart Logging to FILE /var/log/messages Logging to FORW gamekeeper.merrion.nua.net Logging to FILE /var/log/syslog.debug Logging to USERS Logging to USERS logmsg: pri 166, flags 16, from cerberus, msg Jan 24 23:17:23 cerberus /kernel: Jan 24 23:17:23 cerberus /kernel: Jan 24 23:17:23 cerberus /kernel: Jan 24 23:17:23 cerberus /kernel: Jan 24 23:17:23 cerberus /kernel: Jan 24 23:17:23 cerberus /kernel: Jan 24 23:17:23 cerberus /kernel: Jan 24 23:17:23 cerberus /kernel: Jan 24 23:17:23 cerberus /kernel: Jan 24 23:17:23 cerberus /kernel: Jan 24 23:17:23 cerberus /kernel: Jan 24 23:17:23 cerberus /kernel: Jan 24 23:17:23 cerberus /kernel: Jan 24 23:17:23 cerberus /kernel: Jan 24 23:17:23 cerberus /kernel: Jan 24 23:17:23 cerberus /kernel: Jan 24 23:14:49 cerberus /kernel: Jan 24 23:14:49 cerberus /kernel: Jan 24 23:14:49 cerberus /kernel: Jan 24 23:14:49 cerberus /kernel: Jan 24 23:14:49 cerberus /kernel: Jan 24 23:14:49 cerberus /kernel: Jan 24 23:14:49 cerberus /kernel: Jan 24 23:14:49 cerberus /kernel: Jan 24 23:14:49 cerberus /kernel: Jan 24 23:14:49 cerberus /kernel: Jan 24 23:14:49 cerberus /kernel: Jan 24 23:14:48 cerberus /kernel: Jan 24 23:14:48 cerberus /kernel: Jan 24 23:14:48 cerberus /kernel Logging to FILE /var/log/messages Logging to FORW gamekeeper.merrion.nua.net Logging to FILE /var/log/syslog.debug Logging to CONSOLE /dev/console logmsg: pri 2, flags 17, from cerberus, msg : Jan 24 23:14:48 cerberus /ker Logging to FILE /var/log/messages Logging to FORW gamekeeper.merrion.nua.net Logging to FILE /var/log/syslog.debug Logging to USERS Logging to USERS logmsg: pri 166, flags 16, from cerberus, msg Jan 24 23:17:23 cerberus syslogd: exiting on signal 2 Logging to FILE /var/log/messages Logging to FORW gamekeeper.merrion.nua.net Logging to FILE /var/log/syslog.debug Logging to CONSOLE /dev/console logmsg: pri 166, flags 16, from cerberus, msg Jan 24 23:17:50 cerberus syslogd: restart Logging to FILE /var/log/messages Logging to FORW gamekeeper.merrion.nua.net Logging to FILE /var/log/syslog.debug Logging to CONSOLE /dev/console logmsg: pri 166, flags 16, from cerberus, msg Jan 24 23:17:50 cerberus /kernel: Jan 24 23:17:23 cerberus /kernel: Jan 24 23:17:23 cerberus /kernel: Jan 24 23:17:23 cerberus /kernel: Jan 24 23:17:23 cerberus /kernel: Jan 24 23:17:23 cerberus /kernel: Jan 24 23:17:23 cerberus /kernel: Jan 24 23:17:23 cerberus /kernel: Jan 24 23:17:23 cerberus /kernel: Jan 24 23:17:23 cerberus /kernel: Jan 24 23:17:23 cerberus /kernel: Jan 24 23:17:23 cerberus /kernel: Jan 24 23:17:23 cerberus /kernel: Jan 24 23:17:23 cerberus /kernel: Jan 24 23:17:23 cerberus /kernel: Jan 24 23:17:23 cerberus /kernel: Jan 24 23:17:23 cerberus /kernel: Jan 24 23:14:49 cerberus /kernel: Jan 24 23:14:49 cerberus /kernel: Jan 24 23:14:49 cerberus /kernel: Jan 24 23:14:49 cerberus /kernel: Jan 24 23:14:49 cerberus /kernel: Jan 24 23:14:49 cerberus /kernel: Jan 24 23:14:49 cerberus /kernel: Jan 24 23:14:49 cerberus /kernel: Jan 24 23:14:49 cerberus /kernel: Jan 24 23:14:49 cerberus /kernel: Jan 24 23:14:49 cerberus /kernel: Jan 24 23:14:48 cerberus /kernel: Jan 24 23:14:48 cerberus /kernel Logging to FILE /var/log/messages Logging to FORW gamekeeper.merrion.nua.net Logging to FILE /var/log/syslog.debug Logging to CONSOLE /dev/console logmsg: pri 2, flags 17, from cerberus, msg : Jan 24 23:14:48 cerberus /ker Logging to FILE /var/log/messages Logging to FORW gamekeeper.merrion.nua.net Logging to FILE /var/log/syslog.debug msg repeated 1 times, 0 sec of 30 msg repeated 1 times, 0 sec of 30 Regards, Tony. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 24 15:31:54 2001 Delivered-To: freebsd-stable@freebsd.org Received: from smtp.wedgev.com (cm57-70.liwest.at [212.33.57.70]) by hub.freebsd.org (Postfix) with ESMTP id 5A9AD37B400 for ; Wed, 24 Jan 2001 15:31:36 -0800 (PST) Received: from localhost.home ([127.0.0.1] helo=cipher.home) by smtp.wedgev.com with esmtp (Exim 3.16 #1 (FreeBSD)) id 14LZNx-0000CQ-00 for ; Thu, 25 Jan 2001 00:31:29 +0100 X-Mailer: exmh version 2.3.1 01/18/2001 with nmh-1.0.4 To: freebsd-stable@freebsd.org From: Bernhard Valenti Subject: cracks with sblive Reply-To: Bernhard Valenti X-Operating-System: FreeBSD i386 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 25 Jan 2001 00:31:28 +0100 Message-Id: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi, i'm experiencing cracks/pops ( whatever you want to call that ) with the sblive. when playing mp3/wav. i first thought its the mp3's, cause for some time the sblive worked fine in fbsd, but then i played them in windows and the play fine. maybe someone else has the same problems ?(its not alot of cracks, but too much to be able to enjoy musix ;) there is a crack ~every 5-10 seconds when playing mp3s. FreeBSD 4.2-STABLE #7: Tue Jan 16 20:58:19 CET 2001 (had the problems with some severak weeks olds 4.2-stable too) i think the problem appeared when i changed my celeron to a athlon system. maybe its because the usb controller share the irq with the soundcard? (i have my mouse on uhci0) uhci0: port 0xd400-0xd41f irq 5 at device 7.2 on pci0 uhci1: port 0xd800-0xd81f irq 5 at device 7.3 on pci0 pcm0: port 0xdc00-0xdc1f irq 5 at device 11.0 on pci0 any input appreciated, bernhard To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 24 15:48:12 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 1EC8C37B401 for ; Wed, 24 Jan 2001 15:47:54 -0800 (PST) Received: (qmail 32386 invoked from network); 24 Jan 2001 23:47:42 -0000 Received: from klee.esec.com.au (HELO esec.com.au) (203.21.85.206) by lynx.esec.com.au with SMTP; 24 Jan 2001 23:47:42 -0000 Message-ID: <3A6F69FD.97E74874@esec.com.au> Date: Thu, 25 Jan 2001 10:49:17 +1100 From: Kevin LEE X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 Newsgroups: comp.unix.bsd.freebsd.misc To: freebsd-stable@freebsd.org Subject: How to mount iso image file???? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all: In RH7.0, there is a option of loop in the mount command which allows you to mount a iso image file to a specified mount point, so that the actual content of the iso file can be,viiew.. ie mount -t iso9660 -o ro,loop /somedir/somedir.iso /mnt/iso/ and cd /mnt/iso You can view the content of the iso file. But I can find this option in the mount command in FreeBSD ? Is there any to view the context of an iso file before I burn it into a CD ???? -- Kevin LEE Tel: +61 3 8371 5300 Software Architect Direct: +61 3 8371 5378 eSec Limited Fax: +61 3 8371 5399 "Protecting Your e-Business" Web: http://www.esec.com.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 24 15:49: 2 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 74C1537B404 for ; Wed, 24 Jan 2001 15:48:45 -0800 (PST) Received: from daemon (unknown [207.8.144.30]) by scribe.pobox.com (Postfix) with SMTP id A2CC632589; Wed, 24 Jan 2001 18:48:43 -0500 (EST) From: "Jamil Taylor" To: "Bernhard Valenti" Cc: Subject: RE: cracks with sblive Date: Wed, 24 Jan 2001 18:48:44 -0500 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: X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have had crackling sounds with an SB Live card on an Athlon based system and my current Intel based Dell. As soon as I upgraded to XFree 4.0.2 and KDE2, the crackling stopped. The SB Live is crystal clear now playing everything. I did not change any hardware before or after the upgrade. I do not know if this upgrade would have removed the crackling from the Athlon system (as I don't own it anymore), but it did for the Intel. -----Original Message----- From: owner-freebsd-stable@FreeBSD.ORG [mailto:owner-freebsd-stable@FreeBSD.ORG]On Behalf Of Bernhard Valenti Sent: Wednesday, January 24, 2001 6:31 PM To: freebsd-stable@FreeBSD.ORG Subject: cracks with sblive hi, i'm experiencing cracks/pops ( whatever you want to call that ) with the sblive. when playing mp3/wav. i first thought its the mp3's, cause for some time the sblive worked fine in fbsd, but then i played them in windows and the play fine. maybe someone else has the same problems ?(its not alot of cracks, but too much to be able to enjoy musix ;) there is a crack ~every 5-10 seconds when playing mp3s. FreeBSD 4.2-STABLE #7: Tue Jan 16 20:58:19 CET 2001 (had the problems with some severak weeks olds 4.2-stable too) i think the problem appeared when i changed my celeron to a athlon system. maybe its because the usb controller share the irq with the soundcard? (i have my mouse on uhci0) uhci0: port 0xd400-0xd41f irq 5 at device 7.2 on pci0 uhci1: port 0xd800-0xd81f irq 5 at device 7.3 on pci0 pcm0: port 0xdc00-0xdc1f irq 5 at device 11.0 on pci0 any input appreciated, bernhard 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 24 15:57:44 2001 Delivered-To: freebsd-stable@freebsd.org Received: from pan.ch.intel.com (pan.ch.intel.com [143.182.246.24]) by hub.freebsd.org (Postfix) with ESMTP id 73F1037B401 for ; Wed, 24 Jan 2001 15:57:23 -0800 (PST) Received: from sedona.intel.com (sedona.ch.intel.com [143.182.218.21]) by pan.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 QAA24564; Wed, 24 Jan 2001 16:57:04 -0700 (MST) 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 QAA20315; Wed, 24 Jan 2001 16:57:03 -0700 (MST) 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 SAA01662; Wed, 24 Jan 2001 18:57:03 -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: <14959.27599.550911.821713@hip186.ch.intel.com> Date: Wed, 24 Jan 2001 16:57:03 -0700 (MST) To: Kevin LEE Subject: Re: How to mount iso image file???? Newsgroups: comp.unix.bsd.freebsd.misc In-Reply-To: <3A6F69FD.97E74874@esec.com.au> References: <3A6F69FD.97E74874@esec.com.au> X-Mailer: VM 6.75 under Emacs 20.6.3 Cc: stable@freebsd.org Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ On Thursday, January 25, Kevin LEE wrote: ] > Hi all: > > In RH7.0, there is a option of loop in the mount command which > allows you to mount a iso image file to a specified mount point, so that > the actual content of the iso file can be,viiew.. > > ie > > mount -t iso9660 -o ro,loop /somedir/somedir.iso /mnt/iso/ > and > cd /mnt/iso > You can view the content of the iso file. > > But I can find this option in the mount command in FreeBSD ? > Is there any to view the context of an iso file before I burn it into a > CD ???? > Yup. You have to have 'pseudo-device vn' in your kernel config and you have to make sure the vn* devices are made in /dev. Once you do that, the following commands will work: vnconfig -c /dev/vn0c filename.iso mount -t cd9660 /dev/vn0c /mnt Then you can "cd /mnt" and play around in that "loopback" filesystem to your heart's content. Just be sure to umount it, and "vnconfig -u /dev/vn0c" the vn0c device after you're done with it. See the man page on vnconfig for more information. -Jr ps: actually, now that I look in /modules, there is "vn.ko" so you might be able to get away with doing "kldload vn.ko" (and make sure the device nodes are in /dev/). -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= | 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 24 15:59:18 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 4E1D037B400; Wed, 24 Jan 2001 15:58:59 -0800 (PST) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.11.1/8.11.1) with ESMTP id f0ONwwa20403; Wed, 24 Jan 2001 15:58:58 -0800 (PST) (envelope-from jdp@wall.polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.11.1/8.11.0) id f0ONwwA28772; Wed, 24 Jan 2001 15:58:58 -0800 (PST) (envelope-from jdp) Date: Wed, 24 Jan 2001 15:58:58 -0800 (PST) Message-Id: <200101242358.f0ONwwA28772@vashon.polstra.com> To: stable@freebsd.org From: John Polstra Cc: nik@freebsd.org Subject: Re: preventing cvsup from replacing /usr/ports symlink? In-Reply-To: <20010124110912.A2127@canyon.nothing-going-on.org> References: <200101202028.f0KKSUr80758@saturn.home.ben.com> <3A6C5E6C.3E84EAC0@ids.net> <200101232308.f0NN8QT25018@vashon.polstra.com> <20010124110912.A2127@canyon.nothing-going-on.org> Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks for the answers, guys. I was finally able to reproduce the bug and I can see what's causing it. It shouldn't be too hard to fix. Meanwhile, the safest work-around is to make sure your prefix points to the true parent directory of "/usr/ports". 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 Wed Jan 24 16: 9:53 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 E937C37B400 for ; Wed, 24 Jan 2001 16:09:30 -0800 (PST) Received: from home.com ([24.2.169.205]) by femail8.sdc1.sfba.home.com (InterMail vM.4.01.03.00 201-229-121) with ESMTP id <20010125000923.UBVR18735.femail8.sdc1.sfba.home.com@home.com> for ; Wed, 24 Jan 2001 16:09:23 -0800 Message-ID: <3A6EE108.25026852@home.com> Date: Wed, 24 Jan 2001 09:04:56 -0500 From: Ted Sikora Reply-To: tsikora@powerusersbbs.com Organization: Jtl Development Group X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.18 i686) X-Accept-Language: en-US, en MIME-Version: 1.0 To: "freebsd-stable@FreeBSD.ORG" Subject: Re: Athlon Thunderbird 700 w. Asus K7M Motherboard vs. FreeBSD 4.2 References: <3A5F1F43.EE70CB3C@inode.at> <20010112161044.A97484@walton.maths.tcd.ie> <009e01c07cb7$132d9e30$3028680a@tgt.com> <3A5F3951.9932EED5@mindmaker.com> <00d101c07cbe$4f1f84b0$3028680a@tgt.com> <3A5F95AF.F8B120D4@mindmaker.com> <20010124141126.A97916@luke.immure.com> <031e01c08643$0134c420$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 "Thomas T. Veldhouse" wrote: > > Yes - I have since found that you are correct. I have found or heard rumor > of many people out there (especially on EBAY) selling Athlons as a > Thunderbird when in fact it was a classic. Usually, I have found this out > when I specifically queried them about it - or they simply refused to > answer. > > Tom Veldhouse > veldy@veldy.net > > ----- Original Message ----- > From: "Bob Willcox" > To: "Bernhard Beck" > Cc: "Thomas T. Veldhouse" ; > Sent: Wednesday, January 24, 2001 2:11 PM > Subject: Re: Athlon Thunderbird 700 w. Asus K7M Motherboard vs. FreeBSD 4.2 > > > I can attest to the fact that Slot A thunderbirds do exist. I own 3 of > > them (one 900 and 2 700 MHz). I guess I was fortunate that my Slot A > > thuderbirds worked properly (all running FreeBSD) in the MBs (MSI and > > Abit) that I have, though I have also heard that problems exist with > > some MBs > > > > Bob > > > > On Fri, Jan 12, 2001 at 03:39:27PM -0800, Bernhard Beck wrote: > > > According to an article published in c't 14/2000, page 32 (online at > > > http://www.heise.de/ct/00/14/032/default.shtml, use Altavista's > > > Babelfish to translate), Slot A Thunderbirds do exist. In a nutshell > > > among other things AMD slightly changed the bus interface design on the > > > Thunderbirds so that you need chipsets like VIA KT133, KM133 or AMD 760. > > > But under certain conditions the Thunderbird can also work with a KX133 > > > or the Irongate chipset. > > > There is a nice table at the end of the article listing a few Slot A > > > motherboards and if they worked or not with the two sample Slot A > > > Thunderbirds c't had available in their lab at that time. > > > Michael's Asus K7M with Irongate chipset is listed as working with the > > > exact same BIOS version. Count it as a blessing the Slot A classic's are more robust under load... 512 cache is still more than 256 no matter what the speed. Usually worth 10% look at the Celeron vs Pentium II. I don't care what the benchmarks say in the real world there is a difference. -- Ted Sikora Jtl Development Group http://powerusersbbs.com Linux the choice of a GNU generation............ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 24 16:10: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 BD0A637B402 for ; Wed, 24 Jan 2001 16:10:15 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f0P0ABp24323; Wed, 24 Jan 2001 16:10:11 -0800 (PST) Date: Wed, 24 Jan 2001 16:10:11 -0800 From: Alfred Perlstein To: Kevin LEE Cc: freebsd-stable@FreeBSD.ORG Subject: Re: How to mount iso image file???? Message-ID: <20010124161010.F26076@fw.wintelcom.net> References: <3A6F69FD.97E74874@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: <3A6F69FD.97E74874@esec.com.au>; from klee@esec.com.au on Thu, Jan 25, 2001 at 10:49:17AM +1100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Kevin LEE [010124 15:48] wrote: > Hi all: > > In RH7.0, there is a option of loop in the mount command which > allows you to mount a iso image file to a specified mount point, so that > the actual content of the iso file can be,viiew.. man vnconfig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 24 16:11:59 2001 Delivered-To: freebsd-stable@freebsd.org Received: from emma1.emma.line.org (p3EE3C781.dip.t-dialin.net [62.227.199.129]) by hub.freebsd.org (Postfix) with ESMTP id E85C137B402; Wed, 24 Jan 2001 16:11:37 -0800 (PST) Received: by emma1.emma.line.org (Postfix, from userid 500) id 2C506A2002; Thu, 25 Jan 2001 01:11:12 +0100 (CET) Date: Thu, 25 Jan 2001 01:11:12 +0100 From: Matthias Andree To: Guy Harris Cc: Mike Smith , Matthias Andree , Linux NFS mailing list , FreeBSD Stable Subject: Re: [NFS] Incompatible: FreeBSD 4.2 client, Linux 2.2.18 nfsv3 server, read-only export Message-ID: <20010125011111.A12526@emma1.emma.line.org> References: <20010124001701.F344@quadrajet.flashcom.com> <200101241104.f0OB4sS10071@mass.dis.org> <20010124101007.A344@quadrajet.flashcom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010124101007.A344@quadrajet.flashcom.com>; from gharris@flashcom.net on Wed, Jan 24, 2001 at 10:10:07 -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 24 Jan 2001, Guy Harris wrote: > I'm not sure "Permission denied" is all that useful, either; if the file > has permissions rw-r--r-- and is owned by me, "Permission denied" is a > bit of a weird error - I'd rather have the message the program shows me > or logs to a file or whatever say "Read-only file system", as that tells > me that the underlying problem is that *something* is read-only, even if > it doesn't tell me whether it's the client machine's fault for > NFS-mounting it read-only or the server's fault for {locally mounting > it, exporting it} read-only. You're wasting your time. Access permissions may map differently on different systems, and may be changed by the server at any time. > 2.4.0, which is definitely not an ancient release, still appears, from > looking at the code in question, to have that buggy behavior. There has been a mail on the Linux-kernel mailing list claiming otherwise, I haven't tested it. -- Matthias Andree To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 24 16:13:30 2001 Delivered-To: freebsd-stable@freebsd.org Received: from emma1.emma.line.org (p3EE3C781.dip.t-dialin.net [62.227.199.129]) by hub.freebsd.org (Postfix) with ESMTP id A335237B404; Wed, 24 Jan 2001 16:13:13 -0800 (PST) Received: by emma1.emma.line.org (Postfix, from userid 500) id 73FE5A2001; Thu, 25 Jan 2001 01:13:11 +0100 (CET) Date: Thu, 25 Jan 2001 01:13:11 +0100 From: Matthias Andree To: Guy Harris Cc: Mike Smith , Matthias Andree , Linux NFS mailing list , FreeBSD Stable Subject: Re: [NFS] Incompatible: FreeBSD 4.2 client, Linux 2.2.18 nfsv3 server, read-only export Message-ID: <20010125011311.B12526@emma1.emma.line.org> References: <200101241104.f0OB4sS10071@mass.dis.org> <200101241117.f0OBH7S10154@mass.dis.org> <20010124104216.F344@quadrajet.flashcom.com> <20010124105703.G344@quadrajet.flashcom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010124105703.G344@quadrajet.flashcom.com>; from gharris@flashcom.net on Wed, Jan 24, 2001 at 10:57:03 -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 24 Jan 2001, Guy Harris wrote: > An alternative patch is Has been posted to the Linux-kernel mailing list bei Neil B, and "mostly works". FreeBSD and Linux chat almost properly, but Linux does not report EXECUTE permissions though the exported directory is mode 1777. It does however return READ|LOOKUP which is sufficient for FreeBSD to do the ls. -- Matthias Andree To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 24 16:15:11 2001 Delivered-To: freebsd-stable@freebsd.org Received: from emma1.emma.line.org (p3EE3C781.dip.t-dialin.net [62.227.199.129]) by hub.freebsd.org (Postfix) with ESMTP id BBAE637B400; Wed, 24 Jan 2001 16:14:53 -0800 (PST) Received: by emma1.emma.line.org (Postfix, from userid 500) id D512AA2001; Thu, 25 Jan 2001 01:14:52 +0100 (CET) Date: Thu, 25 Jan 2001 01:14:52 +0100 From: Matthias Andree To: Mike Smith Cc: Guy Harris , Matthias Andree , Linux NFS mailing list , FreeBSD Stable Subject: Re: [NFS] Incompatible: FreeBSD 4.2 client, Linux 2.2.18 nfsv3 server, read-only export Message-ID: <20010125011452.C12526@emma1.emma.line.org> References: <20010124104216.F344@quadrajet.flashcom.com> <200101242030.f0OKUTI00828@mass.dis.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200101242030.f0OKUTI00828@mass.dis.org>; from msmith@freebsd.org on Wed, Jan 24, 2001 at 12:30:29 -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Oh. "Joy". > > > If you do want to work around the Linux bug, you'd probably have to send > > another ACCESS request over the wire, with the write bits turned off; > > I'm not sure whether that's worth the effort or not. > > Based on that; no. I think if people want to run v3 against a Linux > server, they will just have to turn the ACCESS cache off. In the > meantime, is there any constructive way we can encourage the Linux NFS > folks to fix this behaviour? No need to, a patch that makes my boxes work has been published on the Linux-kernel mailing list and I think it may be integrated into 2.2.19 if someone asks Alan to merge it, and Linus would certainly not reject a similar fix for 2.4.1 if needed. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 24 16:21:20 2001 Delivered-To: freebsd-stable@freebsd.org Received: from vexpert.dbai.tuwien.ac.at (vexpert.dbai.tuwien.ac.at [128.130.111.12]) by hub.freebsd.org (Postfix) with ESMTP id B4B0C37B400 for ; Wed, 24 Jan 2001 16:21:01 -0800 (PST) Received: from deneb.dbai.tuwien.ac.at (deneb [128.130.111.2]) by vexpert.dbai.tuwien.ac.at (8.11.1/8.11.1) with ESMTP id f0P0Kse10989 for ; Thu, 25 Jan 2001 01:20:54 +0100 (MET) Received: from localhost (pfeifer@localhost) by deneb.dbai.tuwien.ac.at (8.11.1/8.11.1) with ESMTP id f0P0Kqn72835 for ; Thu, 25 Jan 2001 01:20:53 +0100 (CET) (envelope-from pfeifer@dbai.tuwien.ac.at) X-Authentication-Warning: deneb.dbai.tuwien.ac.at: pfeifer owned process doing -bs Date: Thu, 25 Jan 2001 01:20:52 +0100 (CET) From: Gerald Pfeifer To: Subject: Re: amq -v 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 haven't received any response to this. If I should file this somewhere else, please let me know. (Or am I just wasting time, yours and mine, reporting issues like this??) Gerald On Thu, 28 Dec 2000, Gerald Pfeifer wrote: > ...on my FreeBSD 4.2-RELEASE systems prints > > % amq -v > [...] > Built by root@bento.FreeBSD.org on date Mon Nov 20 11:26:50 GMT 2000. > cpu=i386 (little-endian), arch=i386, karch=i386. > full_os=freebsd4.2-BETA, os=freebsd4, osver=4.2-BETA, vendor=unknown. > ^^^^^ ^^^^^ > > which is not really correct. > > I believe this should be fixed for future releases. > > Gerald To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 24 17: 8:40 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 CE36837B400 for ; Wed, 24 Jan 2001 17:08:21 -0800 (PST) Received: from cascade (cascade.veldy.net [64.1.117.29]) by veldy.net (Postfix) with SMTP id 4E9818C2C; Wed, 24 Jan 2001 19:07:50 -0600 (CST) Message-ID: <003201c0866b$2c23a4d0$1d750140@cascade> From: "Thomas T. Veldhouse" To: "Michael Bretterklieber" , References: <3A5F1F43.EE70CB3C@inode.at> <20010112161044.A97484@walton.maths.tcd.ie> <009e01c07cb7$132d9e30$3028680a@tgt.com> <3A5F3951.9932EED5@mindmaker.com> <00d101c07cbe$4f1f84b0$3028680a@tgt.com> <3A5F95AF.F8B120D4@mindmaker.com> <20010124141126.A97916@luke.immure.com> <031e01c08643$0134c420$3028680a@tgt.com> <3A6F4533.2DEE76D@inode.at> Subject: Re: Athlon Thunderbird 700 w. Asus K7M Motherboard vs. FreeBSD 4.2 Date: Wed, 24 Jan 2001 19:07:22 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG That is my fault that the thread diverted. I originally supposed the you didn't have a TBird and thought you did. Then when I found out you probably actually had one that your board did not support it and thus caused you problems. Since neither seems to be the case - perhaps this thread will once again follow the correct line of reasoning. Tom Veldhouse veldy@veldy.net ----- Original Message ----- From: "Michael Bretterklieber" To: Sent: Wednesday, January 24, 2001 3:12 PM Subject: Re: Athlon Thunderbird 700 w. Asus K7M Motherboard vs. FreeBSD 4.2 > Hi, > > I don't wanna be impolite, but my problem is not, if there exists SlotA TB or > not. > The points is, that my hardware works correctly with W2k and W98, but not with > FreeBSD :-(, but I'd like to work with FreeBSD :-). > I hope, that somone from the FreeBSD-community can help. > > bye, > -- > -------------------------------------- > E-mail: Michael.Bretterklieber@jawa.at > ---------------------------- > JAWA MANAGEMENT und SOFTWARE > Liebenauer Hauptstr. 200 > A-8041 GRAZ > Tel: ++43-(0)316-403274-12 > Fax: ++43-(0)316-403274-10 > GSM: ++43-(0)676-93 96 698 > homepage: http://www.jawa.at > --------- privat ----------- > E-mail: mbretter@inode.at > homepage: http://www.inode.at/mbretter > -------------------------------------- > Sorry for my bad english! > > > > 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 24 19:54:43 2001 Delivered-To: freebsd-stable@freebsd.org Received: from eos.umsl.edu (eos.umsl.edu [134.124.42.103]) by hub.freebsd.org (Postfix) with ESMTP id B2B9237B401 for ; Wed, 24 Jan 2001 19:54:25 -0800 (PST) Received: from eos.umsl.edu (localhost [127.0.0.1]) by eos.umsl.edu (8.11.1/8.11.1) with ESMTP id f0P3sM500362 for ; Wed, 24 Jan 2001 21:54:23 -0600 (CST) (envelope-from tom@eos.umsl.edu) Message-ID: <3A6FA36E.5B7D7BAD@eos.umsl.edu> Date: Wed, 24 Jan 2001 21:54:22 -0600 From: Tom Kyle Organization: University of Missouri-St. Louis X-Mailer: Mozilla 4.75 [en] (X11; U; FreeBSD 4.2-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-stable@FreeBSD.ORG Subject: Re: make installworld fails *RESOLVED* References: <3A6F0FEF.F4A4BAD9@eos.umsl.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG My own fault. Forgot to rm -rf /usr/obj before compiling a new source tree. Tom Kyle wrote: > > Hi, I'm tracking STABLE and 'make installworld' fails part of the way > through the perl section: > > ===> gnu/usr.bin/perl/suidperl > install -c -s -o root -g wheel -m 511 suidperl /usr/bin > /usr/bin/sperl5 -> /usr/bin/suidperl > /usr/bin/sperl5.00503 -> /usr/bin/suidperl > ===> gnu/usr.bin/perl/library > install: opnames.h: No such file or directory > *** Error code 71 > > Stop in /usr/src/gnu/usr.bin/perl/library. > *** Error code 1 > > Stop in /usr/src/gnu/usr.bin/perl. > *** Error code 1 > > Stop in /usr/src/gnu/usr.bin. > *** Error code 1 > > Stop in /usr/src/gnu. > *** 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. > > I blew away /usr/src, ran cvsup again, and then did a `make buildworld,` > 'make buildkernel,' 'make installkernel,' and then the 'make > installworld', where it died in the same place with the same error. > > My supfile contains the following: > > *default host=cvsup2.FreeBSD.org > *default base=/usr > *default prefix=/usr > *default release=cvs tag=RELENG_4 > *default delete use-rel-suffix > src-all > > Any tips or suggestions? > > Tom > > - > > Thomas A. Kyle > Network Security Administrator > University of Missouri-St. Louis > tkyle@jinx.umsl.edu > (314) 516-6012 > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- Thomas A. Kyle Network Security Administrator University of Missouri-St. Louis tkyle@jinx.umsl.edu (314) 516-6012 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 24 19:59:50 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 C4C4F37B401 for ; Wed, 24 Jan 2001 19:59:30 -0800 (PST) Received: from boom.forrie.com (forrie.ne.mediaone.net [24.147.132.133]) by forrie.net with id f0P3xM153836 for ; Wed, 24 Jan 2001 22:59:24 -0500 (EST) Message-Id: <5.0.2.1.2.20010124225607.00a59380@216.67.14.69> X-Sender: forrie@216.67.14.69 X-Mailer: QUALCOMM Windows Eudora Version 5.0.2 Date: Wed, 24 Jan 2001 22:59:13 -0500 To: freebsd-stable@freebsd.org From: Forrest Aldrich Subject: Interscan Viruswall for Linux.... on FreeBSD-4.x 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 would like to hear from anyone who is successfully using Interscan Viruswall for Linux on FreeBSD, under Linux emulation (via the linux_base port). It seems this should work with ease; however, TrendMicro refuses to disclose what "configuration adjustments" need to be made, citing that it's not "officially supported" (ie: some of their programs have hard coded path requirements, which they've been notified about from others who use this on FreeBSD). Thanks in advance. _F To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 24 20:37:12 2001 Delivered-To: freebsd-stable@freebsd.org Received: from luke.immure.com (luke.immure.com [207.8.42.74]) by hub.freebsd.org (Postfix) with ESMTP id F16BF37B400 for ; Wed, 24 Jan 2001 20:36:53 -0800 (PST) Received: (from bob@localhost) by luke.immure.com (8.11.1/8.11.1) id f0P4apU05517; Wed, 24 Jan 2001 22:36:51 -0600 (CST) (envelope-from bob) Date: Wed, 24 Jan 2001 22:36:51 -0600 From: Bob Willcox To: tsikora@powerusersbbs.com Cc: "freebsd-stable@FreeBSD.ORG" Subject: Re: Athlon Thunderbird 700 w. Asus K7M Motherboard vs. FreeBSD 4.2 Message-ID: <20010124223651.A5269@luke.immure.com> Reply-To: Bob Willcox References: <3A5F1F43.EE70CB3C@inode.at> <20010112161044.A97484@walton.maths.tcd.ie> <009e01c07cb7$132d9e30$3028680a@tgt.com> <3A5F3951.9932EED5@mindmaker.com> <00d101c07cbe$4f1f84b0$3028680a@tgt.com> <3A5F95AF.F8B120D4@mindmaker.com> <20010124141126.A97916@luke.immure.com> <031e01c08643$0134c420$3028680a@tgt.com> <3A6EE108.25026852@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: <3A6EE108.25026852@home.com>; from tsikora@home.com on Wed, Jan 24, 2001 at 09:04:56AM -0500 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 24, 2001 at 09:04:56AM -0500, Ted Sikora wrote: > > Count it as a blessing the Slot A classic's are more robust under > load... 512 cache is still more than 256 no matter what the speed. > Usually worth 10% look at the Celeron vs Pentium II. I don't care what > the benchmarks say in the real world there is a difference. For the workload that I often run (FreeBSD "make world" :-) I seem to remember about a 10% improvment when I switched one of my systems from a 512KB half-speed cache (orig Athlon) to a 256KB full-speed cache Thunderbird where the processor speed was the same. I certainly wouldn't argue that a different job mix could produce a different or even the opposite result, it's just that it appears that "make world" isn't one of them. Note that this was all that the system was doing at the time. Bob -- Bob Willcox The reason we come up with new versions is not to bob@vieo.com fix bugs. It's absolutely not. Austin, TX -- Bill Gates To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 24 20:38:41 2001 Delivered-To: freebsd-stable@freebsd.org Received: from c014.sfo.cp.net (c014-h024.c014.sfo.cp.net [209.228.12.88]) by hub.freebsd.org (Postfix) with SMTP id 98C4937B400 for ; Wed, 24 Jan 2001 20:38:23 -0800 (PST) Received: (cpmta 4814 invoked from network); 24 Jan 2001 19:45:29 -0800 Received: from d8c81e5f.dsl.flashcom.net (HELO quadrajet.flashcom.com) (216.200.30.95) by smtp.flashcom.net (209.228.12.88) with SMTP; 24 Jan 2001 19:45:29 -0800 X-Sent: 25 Jan 2001 03:45:29 GMT Received: (from guy@localhost) by quadrajet.flashcom.com (8.9.3/8.9.3) id TAA00437; Wed, 24 Jan 2001 19:45:28 -0800 (PST) (envelope-from gharris) Date: Wed, 24 Jan 2001 19:45:28 -0800 From: Guy Harris To: Matthias Andree Cc: Guy Harris , Mike Smith , Matthias Andree , Linux NFS mailing list , FreeBSD Stable Subject: Re: [NFS] Incompatible: FreeBSD 4.2 client, Linux 2.2.18 nfsv3 server, read-only export Message-ID: <20010124194528.B345@quadrajet.flashcom.com> References: <20010124001701.F344@quadrajet.flashcom.com> <200101241104.f0OB4sS10071@mass.dis.org> <20010124101007.A344@quadrajet.flashcom.com> <20010125011111.A12526@emma1.emma.line.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <20010125011111.A12526@emma1.emma.line.org>; from matthias.andree@stud.uni-dortmund.de on Thu, Jan 25, 2001 at 01:11:12AM +0100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 25, 2001 at 01:11:12AM +0100, Matthias Andree wrote: > > 2.4.0, which is definitely not an ancient release, still appears, from > > looking at the code in question, to have that buggy behavior. > > There has been a mail on the Linux-kernel mailing list claiming > otherwise, I haven't tested it. I must've been looking at the wrong source tree or something (either one of the 2.2.x trees, or maybe one of the 2.4.0-testX trees, although I think the tree I had before I grabbed 2.4.0 was 2.4.0-test11, which also has the fix) - 2.4.0 does treat nfserr_rofs the same way it treats nfserr_acces or nfserr_perm, so it shouldn't have the problem. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 24 20:58:58 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 2EA9337B6B0 for ; Wed, 24 Jan 2001 20:58:39 -0800 (PST) Received: (qmail 17306 invoked from network); 25 Jan 2001 04:58:35 -0000 Received: from swun.esec.com.au (HELO esec.com.au) (203.21.85.207) by lynx.esec.com.au with SMTP; 25 Jan 2001 04:58:35 -0000 Message-ID: <3A6FB3AC.22BA40BF@esec.com.au> Date: Thu, 25 Jan 2001 16:03:41 +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: John Reynolds~ Cc: Kevin LEE , stable@freebsd.org Subject: Re: How to mount iso image file???? References: <3A6F69FD.97E74874@esec.com.au> <14959.27599.550911.821713@hip186.ch.intel.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 got the following errors: #vnconfig -c /dev/vn0c songs.iso vnconfig: VNIOCATTACH: Device busy Sam John Reynolds~ wrote: > [ On Thursday, January 25, Kevin LEE wrote: ] > > Hi all: > > > > In RH7.0, there is a option of loop in the mount command which > > allows you to mount a iso image file to a specified mount point, so that > > the actual content of the iso file can be,viiew.. > > > > ie > > > > mount -t iso9660 -o ro,loop /somedir/somedir.iso /mnt/iso/ > > and > > cd /mnt/iso > > You can view the content of the iso file. > > > > But I can find this option in the mount command in FreeBSD ? > > Is there any to view the context of an iso file before I burn it into a > > CD ???? > > > > Yup. You have to have 'pseudo-device vn' in your kernel config and you have > to make sure the vn* devices are made in /dev. Once you do that, the following > commands will work: > > vnconfig -c /dev/vn0c filename.iso > mount -t cd9660 /dev/vn0c /mnt > > Then you can "cd /mnt" and play around in that "loopback" filesystem to your > heart's content. > > Just be sure to umount it, and "vnconfig -u /dev/vn0c" the vn0c device after > you're done with it. See the man page on vnconfig for more information. > > -Jr > > ps: actually, now that I look in /modules, there is "vn.ko" so you might be > able to get away with doing "kldload vn.ko" (and make sure the device nodes > are in /dev/). > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 24 21:21:50 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail2.rdc2.bc.home.com (mail2.rdc2.bc.home.com [24.2.10.85]) by hub.freebsd.org (Postfix) with ESMTP id F327237B402 for ; Wed, 24 Jan 2001 21:21:33 -0800 (PST) Received: from ardbeg ([24.77.8.34]) by mail2.rdc2.bc.home.com (InterMail vM.4.01.03.00 201-229-121) with SMTP id <20010125052133.HGHC12679.mail2.rdc2.bc.home.com@ardbeg>; Wed, 24 Jan 2001 21:21:33 -0800 From: Gord Broom Reply-To: Gordon.Broom@home.com To: Kent Stewart Subject: Re: make buildworld fails Date: Wed, 24 Jan 2001 21:17:45 -0800 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain; charset="us-ascii" Cc: freebsd-stable@FreeBSD.ORG References: <01012321552400.75594@ardbeg> <3A6E9387.BB156E60@urx.com> In-Reply-To: <3A6E9387.BB156E60@urx.com> MIME-Version: 1.0 Message-Id: <01012421213500.00463@ardbeg> Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 24 Jan 2001, Kent Stewart wrote: > I think I would wipe out /usr/obj and start over. You might even > consider a coupld of "make cleandir" in /usr/src. This time pay > attention to the sequence in /usr/src/UPDATING. As you can see, it > works. >=20 > During my many previous attempts, I had blown /usr/obj away and started a= fresh. This time, I tried the 'make cleandir' as well, and then followed the "Upgrading 4.0 (and later) to 4.x-STABLE" instructions in /usr/src/UPDATI= NG. Worked like a charm (yay!), thanks! ardbeg:src$ uname -a FreeBSD ardbeg 4.2-STABLE FreeBSD 4.2-STABLE #0: Wed Jan 24 20:31:22 PST = 2001 root@ardbeg:/usr/local/obj/usr/src/sys/ARDBEG i386 ardbeg:src$ Gord. [who notes that 'make cleandir' isn't mentioned anywhere in /usr/src/UPDATING :-( ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 24 21:30:34 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 4486037B400 for ; Wed, 24 Jan 2001 21:30:15 -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 f0P5QP964863; Wed, 24 Jan 2001 22:26:26 -0700 (MST) (envelope-from imp@harmony.village.org) Message-Id: <200101250526.f0P5QP964863@harmony.village.org> To: Gordon.Broom@home.com Subject: Re: make buildworld fails Cc: Kent Stewart , freebsd-stable@FreeBSD.ORG In-reply-to: Your message of "Wed, 24 Jan 2001 21:17:45 PST." <01012421213500.00463@ardbeg> References: <01012421213500.00463@ardbeg> <01012321552400.75594@ardbeg> <3A6E9387.BB156E60@urx.com> Date: Wed, 24 Jan 2001 22:26:25 -0700 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <01012421213500.00463@ardbeg> Gord Broom writes: : Gord. [who notes that 'make cleandir' isn't mentioned anywhere in : /usr/src/UPDATING :-( ] Well, it usually isn't needed and rm -rf /usr/obj is faster. But I suppose that following rm -rf /usr/obj by a make cleandir might not be a bad idea just to make sure that your /usr/src tree is in a pristine state. 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 24 22:49:47 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 E847737B402 for ; Wed, 24 Jan 2001 22:49:28 -0800 (PST) Received: from jamestown.enteract.com (24-148-57-6.na.21stcentury.net [24.148.57.6]) by mail.enteract.com (8.9.3/8.9.3) with ESMTP id AAA05830 for ; Thu, 25 Jan 2001 00:49:28 -0600 (CST) (envelope-from jtm@enteract.com) Received: by jamestown.enteract.com (8.9.3/8.9.3) id AAA04840 for freebsd-stable@freebsd.org; Thu, 25 Jan 2001 00:48:08 -0600 (CST) (envelope-from jtm) From: James McNaughton Reply-To: jtm63@enteract.com To: freebsd-stable@freebsd.org Subject: Re: Network stops working Date: Thu, 25 Jan 2001 00:26:32 -0600 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain References: <001001c08628$8db16180$9d8fc918@videotron.ca> <20010124164125.A12612@home.com> In-Reply-To: <20010124164125.A12612@home.com> MIME-Version: 1.0 Message-Id: <01012500480800.01077@jamestown.enteract.com> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have experienced a similar issue with my cable modem service. Look at this from /var/log/messages: Jan 23 14:20:56 jamestown /kernel: arp: 00:20:78:d0:28:12 is using my IP address 0.0.0.0! Jan 23 14:20:56 jamestown /kernel: arp: 00:20:78:d0:28:12 is using my IP address 0.0.0.0! Jan 24 21:39:25 jamestown /kernel: arp: 00:50:8b:aa:68:a9 is using my IP address 24.148.62.76! What you need to know first is: Do you have a static IP address or is the ISP using DHCP? Set your configuration accordingly. See Section 17.8 DHCP of the FreeBSD Handbook for help on DHCP. It's really simple. Are you getting messages like I am above? This could be a sign of a misconfigured NIC. Jim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 24 23:18:45 2001 Delivered-To: freebsd-stable@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.122.47]) by hub.freebsd.org (Postfix) with ESMTP id 23EC237B400 for ; Wed, 24 Jan 2001 23:18:27 -0800 (PST) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.10.1/8.10.1) with ESMTP id f0P7HrE28494; Wed, 24 Jan 2001 23:17:54 -0800 (PST) Date: Wed, 24 Jan 2001 23:17:53 -0800 (PST) From: Doug White To: Mikhail Kononenko Cc: freebsd-stable@FreeBSD.ORG Subject: Re: EtherExpress100 on Intel Easton In-Reply-To: <024301c08642$e09fb3a0$210aa8c0@mikhail> 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, 24 Jan 2001, Mikhail Kononenko wrote: > Sorry, if this is offtopic here, but I could not get answer from native > lists... > > Linux kernel-2.2.17 on D815EEAL (with integrated NIC). The driver used: > eepro100. Traditionally, the Linux Intel EtherExpress Pro/100 drivers have, quite frankly, sucked. This is a known problem with no solution. This is counter to FreeBSD, where the fxp driver is one of the best ethernet drivers in the system :-) Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | 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 Wed Jan 24 23:20:21 2001 Delivered-To: freebsd-stable@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.122.47]) by hub.freebsd.org (Postfix) with ESMTP id 98D3E37B698 for ; Wed, 24 Jan 2001 23:20:03 -0800 (PST) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.10.1/8.10.1) with ESMTP id f0P7Igo28502; Wed, 24 Jan 2001 23:18:42 -0800 (PST) Date: Wed, 24 Jan 2001 23:18:41 -0800 (PST) From: Doug White To: Sam Wun Cc: John Reynolds~ , Kevin LEE , stable@FreeBSD.ORG Subject: Re: How to mount iso image file???? In-Reply-To: <3A6FB3AC.22BA40BF@esec.com.au> 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, 25 Jan 2001, Sam Wun wrote: > I got the following errors: > > #vnconfig -c /dev/vn0c songs.iso > vnconfig: VNIOCATTACH: Device busy Well, something's already there! Detach it first: vnconfig -u /dev/vn0 (use vn0, not vn0c, btw) Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | 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 Wed Jan 24 23:27:12 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 6980F37B401 for ; Wed, 24 Jan 2001 23:26:51 -0800 (PST) Received: from [203.164.12.28] by www.quake.com.au (NTMail 4.30.0012/AH9370.63.d1acf55c) with ESMTP id nxvsaaaa for ; Thu, 25 Jan 2001 18:35:28 +1100 Message-ID: <3A6FD545.3D329446@quake.com.au> Date: Thu, 25 Jan 2001 18:27:01 +1100 From: Kal Torak X-Mailer: Mozilla 4.73 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: jtm63@enteract.com Cc: freebsd-stable@freebsd.org Subject: Re: Network stops working References: <001001c08628$8db16180$9d8fc918@videotron.ca> <20010124164125.A12612@home.com> <01012500480800.01077@jamestown.enteract.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG James McNaughton wrote: > > I have experienced a similar issue with my cable modem service. Look at > this from /var/log/messages: > > Jan 23 14:20:56 jamestown /kernel: arp: 00:20:78:d0:28:12 is using my IP address 0.0.0.0! > Jan 23 14:20:56 jamestown /kernel: arp: 00:20:78:d0:28:12 is using my IP address 0.0.0.0! > > Jan 24 21:39:25 jamestown /kernel: arp: 00:50:8b:aa:68:a9 is using > my IP address 24.148.62.76! > > What you need to know first is: > > Do you have a static IP address or is the ISP using DHCP? Set your > configuration accordingly. See Section 17.8 DHCP of the FreeBSD > Handbook for help on DHCP. > It's really simple. > > Are you getting messages like I am above? This could be a sign of a > misconfigured NIC. From what they said in the original post it looks like they were behind a gateway for internet access... So I dont think this is a DHCP with cable issue, BUT they also seemed to be using DHCP internally on there lan, so it could still be a DHCP problem... Since it works again after a reboot (which would get fresh DHCP info) it seems likely that its the case... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 25 1: 5:42 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 4C06E37B400 for ; Thu, 25 Jan 2001 01:05:24 -0800 (PST) Received: (qmail 1765 invoked by uid 0); 25 Jan 2001 09:05:23 -0000 Received: from unknown (HELO urx.com) (206.159.132.160) by mail.urx.com with SMTP; 25 Jan 2001 09:05:23 -0000 Message-ID: <3A6FEC53.5A49024F@urx.com> Date: Thu, 25 Jan 2001 01:05:23 -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: Gordon.Broom@home.com Cc: freebsd-stable@FreeBSD.ORG Subject: Re: make buildworld fails References: <01012321552400.75594@ardbeg> <3A6E9387.BB156E60@urx.com> <01012421213500.00463@ardbeg> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Gord Broom wrote: > > On Wed, 24 Jan 2001, Kent Stewart wrote: > > > I think I would wipe out /usr/obj and start over. You might even > > consider a coupld of "make cleandir" in /usr/src. This time pay > > attention to the sequence in /usr/src/UPDATING. As you can see, it > > works. > > > > > > During my many previous attempts, I had blown /usr/obj away and started afresh. > This time, I tried the 'make cleandir' as well, and then followed the > "Upgrading 4.0 (and later) to 4.x-STABLE" instructions in /usr/src/UPDATING. > > Worked like a charm (yay!), thanks! > > ardbeg:src$ uname -a > FreeBSD ardbeg 4.2-STABLE FreeBSD 4.2-STABLE #0: Wed Jan 24 20:31:22 PST 2001 root@ardbeg:/usr/local/obj/usr/src/sys/ARDBEG i386 > ardbeg:src$ > > Gord. [who notes that 'make cleandir' isn't mentioned anywhere in > /usr/src/UPDATING :-( ] Cool! It was something that seemed appropriate to suggest that you try. I could not see why some people in fairly clean conditions had trouble and I didn't unless something like this was going on. Your first email was also the first time that it popped into my mind to try that high in the source tree. Kent > > 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 Thu Jan 25 1:30:31 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 8EF7C37B400 for ; Thu, 25 Jan 2001 01:30:13 -0800 (PST) Received: from dogma.freebsd-uk.eu.org ([130.88.200.97] ident=root) by serenity.mcc.ac.uk with esmtp (Exim 2.05 #4) id 14LijM-0009GW-00 for stable@freebsd.org; Thu, 25 Jan 2001 09:30:12 +0000 Received: (from rasputin@localhost) by dogma.freebsd-uk.eu.org (8.11.1/8.11.1) id f0P9UCA26915 for stable@freebsd.org; Thu, 25 Jan 2001 09:30:12 GMT (envelope-from rasputin) Date: Thu, 25 Jan 2001 09:30:12 +0000 From: Rasputin To: stable@freebsd.org Subject: Re: ftp in free(): warning: junk pointer, too high to make sense. Message-ID: <20010125093011.A26874@dogma.freebsd-uk.eu.org> References: <200101241537.f0OFbHd07268@granny.bwa.penx.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200101241537.f0OFbHd07268@granny.bwa.penx.com>; from root@penx.com on Wed, Jan 24, 2001 at 07:37:17AM -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Charlie Root [010124 15:38]: > > I cvsup yesterday against RELENG_4. Today, when I when to > install a port, this happened: > > granny# mk > >> mysql-3.23.32.tar.gz doesn't seem to exist in /usr/ports/distfiles/. > >> Attempting to fetch from http://www.kernelnotes.de/MySQL/Downloads/MySQL-3.23/. > Requesting http://www.kernelnotes.de/MySQL/Downloads/MySQL-3.23/mysql-3.23.32.tar.gz > ftp: Error retrieving file: 404 Not Found I normally use fetch myself.... > ftp in free(): warning: junk pointer, too high to make sense. > Segmentation fault - core dumped Maybe ftp doesn't understand http:// URLs? -- 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 Thu Jan 25 2:26:23 2001 Delivered-To: freebsd-stable@freebsd.org Received: from dilbert.fcg.co.uk (dilbert.firstcallgroup.co.uk [194.203.69.166]) by hub.freebsd.org (Postfix) with ESMTP id 1872A37B401 for ; Thu, 25 Jan 2001 02:26:06 -0800 (PST) Received: from pfrench by dilbert.fcg.co.uk with local (Exim 3.20 #1) id 14LjbG-000OcJ-00; Thu, 25 Jan 2001 10:25:54 +0000 To: kaltorak@quake.com.au Subject: Re: anybody seen this one ? Cc: stable@freebsd.org In-Reply-To: <3A6E6543.B5D9A8E3@quake.com.au> Message-Id: From: Pete French Date: Thu, 25 Jan 2001 10:25:54 +0000 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Yes I have seen this happen... Its not that the computer is frozen its that > the keyboard driver cant load because of a conflict, strange I know, but if > you look at the messages that scroll past when its loading into sysinstall you > will see the keyboard driver isnt loading... Aha, yes, found that. Returns '6'. No amount of BIOS tweaking has solved the problem as yet, though I have discovered that the two "identical" motherboads apparrently have slightly different BIOS revisions on them. I;ve set the two up with identical settings and identical cards in them now - one works, the other doesn't. However, as 3.4 still works on the machine I have a starting point to try and work out what the difference is between what 3.4 is doing and what 4.2 is doing. cheers, -pete. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 25 3:25:12 2001 Delivered-To: freebsd-stable@freebsd.org Received: from bumper.jellybaby.net (bumper.jellybaby.net [194.159.247.1]) by hub.freebsd.org (Postfix) with ESMTP id 4AB4537B400 for ; Thu, 25 Jan 2001 03:24:53 -0800 (PST) Received: (from simond@localhost) by bumper.jellybaby.net (8.9.2/8.9.2) id LAA93647; Thu, 25 Jan 2001 11:24:47 GMT (envelope-from simond) Date: Thu, 25 Jan 2001 11:24:47 +0000 From: simond@irrelevant.org To: Pete French Cc: kaltorak@quake.com.au, stable@FreeBSD.ORG Subject: Re: anybody seen this one ? Message-ID: <20010125112447.A91024@irrelevant.org> References: <3A6E6543.B5D9A8E3@quake.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from pfrench@firstcallgroup.co.uk on Thu, Jan 25, 2001 at 10:25:54AM +0000 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 25, 2001 at 10:25:54AM +0000, Pete French wrote: > > Yes I have seen this happen... Its not that the computer is frozen its that > > the keyboard driver cant load because of a conflict, strange I know, but if > > you look at the messages that scroll past when its loading into sysinstall you > > will see the keyboard driver isnt loading... > > Aha, yes, found that. Returns '6'. No amount of BIOS tweaking has solved > the problem as yet, though I have discovered that the two "identical" > motherboads apparrently have slightly different BIOS revisions on them. > I;ve set the two up with identical settings and identical cards in them > now - one works, the other doesn't. However, as 3.4 still works on the > machine I have a starting point to try and work out what the difference > is between what 3.4 is doing and what 4.2 is doing. I had this problem too a while back, I fixed it for myself at the time by removing the flags 0x1 from the atkbd0 entry in the kernel config file, this can also be done via boot -c and similar, I then managed to fix it in the long term by playing with some options in my BIOS, it seemed to be related to USB keyboards for some reason (despite me not using them) -- Simon Dick simond@irrelevant.org "Why do I get this urge to go bowling everytime I see Tux?" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 25 3:35:28 2001 Delivered-To: freebsd-stable@freebsd.org Received: from plab.ku.dk (plab.ku.dk [130.225.105.65]) by hub.freebsd.org (Postfix) with ESMTP id 8DD0937B400 for ; Thu, 25 Jan 2001 03:35:10 -0800 (PST) Received: (from root@localhost) by plab.ku.dk (8.11.0/8.9.3) id f0PBZ4524608 for freebsd-stable@freebsd.org.AVP; Thu, 25 Jan 2001 12:35:04 +0100 (CET) (envelope-from postmaster@plab.ku.dk) Received: from raven.plab.ku.dk (raven.plab.ku.dk [130.225.105.67]) by plab.ku.dk (8.11.0/8.9.3) with ESMTP id f0PBZ2b24600 for ; Thu, 25 Jan 2001 12:35:03 +0100 (CET) (envelope-from postmaster@plab.ku.dk) Subject: Ports update - is something broken? Content-Transfer-Encoding: 8bit To: freebsd-stable@freebsd.org From: Dmitry Karasik Content-Type: text/plain; charset="koi8-r" Lines: 29 Mime-Version: 1.0 Date: 25 Jan 2001 12:32:50 +0100 X-Mailer: Mail::Mailer[v1.18] Net::SMTP[v2.13] Message-Id: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! I recently cvsupped the ports tree on my 4.1-stable, but after that make refused to deal with ports - 'Your system is too old to use this bsd.port.mk.'. I believed that ports update procedure should be more or less aware of current version, and do not fetch files that force to buildworld the whole system - but that is just because I never had that kind of situation before. Could anyone explain what happened, or at least point to the relevant piece of documentation? man cvsup either is not enough or is too obscure... my ports-supfile is *default host=localhost *default base=/usr *default prefix=/usr *default release=cvs tag=. *default delete use-rel-suffix ports-all looks ok for me, or should I hack it on every buildworld? -- Sincerely, Dmitry --- www.karasik.eu.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 25 4:43:27 2001 Delivered-To: freebsd-stable@freebsd.org Received: from femail3.rdc1.on.home.com (femail3.rdc1.on.home.com [24.2.9.90]) by hub.freebsd.org (Postfix) with ESMTP id 0C96B37B402 for ; Thu, 25 Jan 2001 04:43:10 -0800 (PST) Received: from foo ([24.114.70.142]) by femail3.rdc1.on.home.com (InterMail vM.4.01.03.00 201-229-121) with SMTP id <20010125124247.CZXE844.femail3.rdc1.on.home.com@foo> for ; Thu, 25 Jan 2001 04:42:47 -0800 Message-ID: <000a01c086e5$aecbd2c0$0a00000a@foo> From: "Mike Poirier" To: Subject: Date: Thu, 25 Jan 2001 07:44:19 -0800 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0007_01C086A2.A0656F40" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 Disposition-Notification-To: "Mike Poirier" 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_0007_01C086A2.A0656F40 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable subscribe ------=_NextPart_000_0007_01C086A2.A0656F40 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
subscribe
------=_NextPart_000_0007_01C086A2.A0656F40-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 25 5:33:27 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 18AE337B401 for ; Thu, 25 Jan 2001 05:33:10 -0800 (PST) Received: from [203.164.12.28] by www.quake.com.au (NTMail 4.30.0012/AH9370.63.d1acf55c) with ESMTP id cawsaaaa for ; Fri, 26 Jan 2001 00:41:47 +1100 Message-ID: <3A702B20.EBEE505@quake.com.au> Date: Fri, 26 Jan 2001 00:33:20 +1100 From: Kal Torak X-Mailer: Mozilla 4.73 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Dmitry Karasik Cc: freebsd-stable@freebsd.org Subject: Re: Ports update - is something broken? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dmitry Karasik wrote: > > Hi! > > I recently cvsupped the ports tree on my 4.1-stable, but after that > make refused to deal with ports - 'Your system is too old to use this > bsd.port.mk.'. I believed that ports update procedure should be more or > less aware of current version, and do not fetch files that force to > buildworld the whole system - but that is just because I never had that kind of > situation before. Could anyone explain what happened, or at least point > to the relevant piece of documentation? man cvsup either is not enough or > is too obscure... I think you will find cvsup didnt remove some of the old stuff in your ports tree... A simple solution if you have the time is to rm -rf your ports and cvsup them again... Im sure there is a more elegant solution, check the mail archives, this has been discussed at least twice before... Good luck! Kal. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 25 6:13: 1 2001 Delivered-To: freebsd-stable@freebsd.org Received: from yip.org (yip.org [199.45.111.121]) by hub.freebsd.org (Postfix) with ESMTP id 1542E37B401 for ; Thu, 25 Jan 2001 06:12:41 -0800 (PST) Received: from localhost (melange@localhost) by yip.org (8.11.1/8.11.1) with ESMTP id f0PECZB27764; Thu, 25 Jan 2001 09:12:35 -0500 (EST) (envelope-from melange@yip.org) Date: Thu, 25 Jan 2001 09:12:35 -0500 (EST) From: Bob K To: Kal Torak Cc: Dmitry Karasik , freebsd-stable@FreeBSD.ORG Subject: Re: Ports update - is something broken? In-Reply-To: <3A702B20.EBEE505@quake.com.au> 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, 26 Jan 2001, Kal Torak wrote: > I think you will find cvsup didnt remove some of the old stuff in your > ports tree... A simple solution if you have the time is to rm -rf your > ports and cvsup them again... Actually, Dmitry probably needs to download an upgrade kit from http://www.freebsd.org/ports/ . -- Bob | iNFp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 25 7:18:46 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 A3C9037B402 for ; Thu, 25 Jan 2001 07:18:28 -0800 (PST) Received: (from daemon@localhost) by point.osg.gov.bc.ca (8.8.7/8.8.8) id HAA08827; Thu, 25 Jan 2001 07:18:18 -0800 Received: from passer.osg.gov.bc.ca(142.32.110.29) via SMTP by point.osg.gov.bc.ca, id smtpda08825; Thu Jan 25 07:18:17 2001 Received: (from uucp@localhost) by passer.osg.gov.bc.ca (8.11.2/8.9.1) id f0PFIB707861; Thu, 25 Jan 2001 07:18:11 -0800 (PST) Received: from cwsys9.cwsent.com(10.2.2.1), claiming to be "cwsys.cwsent.com" via SMTP by passer9.cwsent.com, id smtpdtO7859; Thu Jan 25 07:17:21 2001 Received: (from uucp@localhost) by cwsys.cwsent.com (8.11.2/8.9.1) id f0PFHL614920; Thu, 25 Jan 2001 07:17:21 -0800 (PST) Message-Id: <200101251517.f0PFHL614920@cwsys.cwsent.com> Received: from localhost.cwsent.com(127.0.0.1), claiming to be "cwsys" via SMTP by localhost.cwsent.com, id smtpdo14916; Thu Jan 25 07:17:12 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-Sender: schubert To: Gerald Pfeifer Cc: freebsd-stable@FreeBSD.ORG Subject: Re: amq -v In-reply-to: Your message of "Thu, 25 Jan 2001 01:20:52 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 25 Jan 2001 07:17:12 -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Gerald Pfeifer writes: > I haven't received any response to this. > > If I should file this somewhere else, please let me know. (Or am I > just wasting time, yours and mine, reporting issues like this??) > > Gerald > > On Thu, 28 Dec 2000, Gerald Pfeifer wrote: > > ...on my FreeBSD 4.2-RELEASE systems prints > > > > % amq -v > > [...] > > Built by root@bento.FreeBSD.org on date Mon Nov 20 11:26:50 GMT 2000. > > cpu=i386 (little-endian), arch=i386, karch=i386. > > full_os=freebsd4.2-BETA, os=freebsd4, osver=4.2-BETA, vendor=unknown. > > ^^^^^ ^^^^^ > > > > which is not really correct. > > > > I believe this should be fixed for future releases. I noticed this too. After applying David O'Brien's pthread patch and building world again, e.g. I didn't cvsup a new source tree, it now says freebsd4.2-RELEASE. What I think is happening, w/o looking at the source, is that full_os and osver are obtained from the system that amd was built on, not the system it was built for. 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 Thu Jan 25 7:32: 8 2001 Delivered-To: freebsd-stable@freebsd.org Received: from tele-post-20.mail.demon.net (tele-post-20.mail.demon.net [194.217.242.20]) by hub.freebsd.org (Postfix) with ESMTP id 2080137B69C for ; Thu, 25 Jan 2001 07:31:48 -0800 (PST) Received: from partex.demon.co.uk ([212.229.12.157] helo=partex01.partex.co.uk) by tele-post-20.mail.demon.net with esmtp (Exim 2.12 #2) id 14LoNH-00041c-0K for freebsd-stable@FreeBSD.org; Thu, 25 Jan 2001 15:31:47 +0000 Received: by PARTEX01 with Internet Mail Service (5.5.2650.21) id ; Thu, 25 Jan 2001 15:18:00 -0000 Message-ID: <515383C0C799D3119326204C4F4F502009419D@PARTEX01> From: Simon Hooper To: "'freebsd-stable@FreeBSD.org'" Subject: Date: Thu, 25 Jan 2001 15:17:58 -0000 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 subscribe freebsd-stable To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 25 7:33:23 2001 Delivered-To: freebsd-stable@freebsd.org Received: from VL-MS-MR003.sc1.videotron.ca (relais.videotron.ca [24.201.245.36]) by hub.freebsd.org (Postfix) with ESMTP id C34FF37B6A0 for ; Thu, 25 Jan 2001 07:33:05 -0800 (PST) Received: from southpark ([24.201.143.157]) by VL-MS-MR003.sc1.videotron.ca (Netscape Messaging Server 4.15) with SMTP id G7Q5V502.5HK for ; Thu, 25 Jan 2001 10:33:05 -0500 Message-ID: <002b01c086e4$2c843060$9d8fc918@videotron.ca> From: "Luc Morin" To: References: <001001c08628$8db16180$9d8fc918@videotron.ca> <20010124164125.A12612@home.com> <01012500480800.01077@jamestown.enteract.com> <3A6FD545.3D329446@quake.com.au> Subject: Re: Network stops working Date: Thu, 25 Jan 2001 10:33:31 -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.4133.2400 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'm sorry, but I seem to have misled some people by forgeting to mention that I do indeed need to use DHCP to get my IP assigned. Now, that being said, I contacted a service representative from my ISP this morning, and while I had 100% packet loss when trying to ping a known good host, he said he could ping me with 0% packet loss from his side. Also, I have noticed that although I can't reach out, I still see connection attempts made to my box (I have log_in_vain="YES" in rc.conf). I hope this can shed some new light. Thanks. Luc Morin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 25 9:13:25 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 A7F1937B401 for ; Thu, 25 Jan 2001 09:13:04 -0800 (PST) Received: from [203.164.12.28] by www.quake.com.au (NTMail 4.30.0012/AH9370.63.d1acf55c) with ESMTP id cbwsaaaa for ; Fri, 26 Jan 2001 04:21:41 +1100 Message-ID: <3A705EAA.23BD59B4@quake.com.au> Date: Fri, 26 Jan 2001 04:13:14 +1100 From: Kal Torak X-Mailer: Mozilla 4.73 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Luc Morin Cc: freebsd-stable@freebsd.org Subject: Re: Network stops working References: <001001c08628$8db16180$9d8fc918@videotron.ca> <20010124164125.A12612@home.com> <01012500480800.01077@jamestown.enteract.com> <3A6FD545.3D329446@quake.com.au> <002b01c086e4$2c843060$9d8fc918@videotron.ca> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Luc Morin wrote: > > Hi all, > > I'm sorry, but I seem to have misled some people by forgeting to > mention that I do indeed need to use DHCP to get my IP assigned. > > Now, that being said, I contacted a service representative from > my ISP this morning, and while I had 100% packet loss when trying > to ping a known good host, he said he could ping me with 0% > packet loss from his side. Explain what your setup is? FreeBSD is the gateway for your lan? I dont understand why you need to use DHCP internally unless you have some special deal where you get multiple external IP's? Is the system that stops working your gateway? Before you said you couldnt even ping your gateway? Please clarify your topology :) Kal. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 25 9:44:28 2001 Delivered-To: freebsd-stable@freebsd.org Received: from burka.carrier.kiev.ua (burka.carrier.kiev.ua [193.193.193.107]) by hub.freebsd.org (Postfix) with ESMTP id BD68937B404 for ; Thu, 25 Jan 2001 09:44:08 -0800 (PST) Received: from netch@localhost by burka.carrier.kiev.ua id TQY38285 for freebsd-stable@freebsd.org; Thu, 25 Jan 2001 19:44:05 +0200 (EET) (envelope-from netch) Date: Thu, 25 Jan 2001 19:44:05 +0200 From: Valentin Nechayev To: freebsd-stable@freebsd.org Subject: make buildworld fails: share/doc/usd/13.viref Message-ID: <20010125194405.W31587@lucky.net> Reply-To: netch@lucky.net Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i X-42: On Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ===> share/doc/usd/13.viref (cd /m4/REL4/src/share/doc/usd/13.viref/../../../../contrib/nvi/docs/USD.doc/vi. ref; sed -e\ 's:\(\.so[\ \ ][\ \ ]*\)\(vi.ref\)$:\1/m4/REL4/src/share/doc /usd/13.viref/../../../../contrib/nvi/docs/USD.doc/vi.ref/\2:' -e\ 's:\(\.so[\ \ ][\ \ ]*\)\(ex.cmd.roff\)$:\1/m4/REL4/src/share/doc/usd/13.viref/../.. /../../contrib/nvi/docs/USD.doc/vi.ref/\2:' -e\ 's:\(\.so[\ \ ][\ \ ]*\)\(re f.so\)$:\1/m4/REL4/src/share/doc/usd/13.viref/../../../../contrib/nvi/docs/USD.d oc/vi.ref/\2:' -e\ 's:\(\.so[\ \ ][\ \ ]*\)\(set.opt.roff\)$:\1/m4/REL4 /src/share/doc/usd/13.viref/../../../../contrib/nvi/docs/USD.doc/vi.ref/\2:' -e\ 's:\(\.so[\ \ ][\ \ ]*\)\(vi.cmd.roff\)$:\1/m4/REL4/src/share/doc/usd/13.vir ef/../../../../contrib/nvi/docs/USD.doc/vi.ref/\2:' -e 's:^\.so index.so$::' vi. ref) | groff -mtty-char -Tascii -t -s -me -U -o1- > /dev/null groff: illegal option -- U usage: groff [-abehilpstvzCENRSVXZ] [-Fdir] [-mname] [-Tdev] [-ffam] [-wname] [-Wname] [ -Mdir] [-dcs] [-rcn] [-nnum] [-olist] [-Parg] [-Larg] [files...] groff -h gives more help host OS is `FreeBSD 3.4-STABLE i386' No words in src/UPDATING about it /netch To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 25 9:49:33 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 AC0B637B69F for ; Thu, 25 Jan 2001 09:49:06 -0800 (PST) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.11.0/8.11.0) id f0PHmWV42870; Thu, 25 Jan 2001 19:48:32 +0200 (EET) (envelope-from ru) Date: Thu, 25 Jan 2001 19:48:32 +0200 From: Ruslan Ermilov To: Valentin Nechayev Cc: freebsd-stable@FreeBSD.ORG Subject: Re: make buildworld fails: share/doc/usd/13.viref Message-ID: <20010125194832.A42750@sunbay.com> Mail-Followup-To: Valentin Nechayev , freebsd-stable@FreeBSD.ORG References: <20010125194405.W31587@lucky.net> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="uAKRQypu60I7Lcqm" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010125194405.W31587@lucky.net>; from netch@lucky.net on Thu, Jan 25, 2001 at 07:44:05PM +0200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --uAKRQypu60I7Lcqm Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Please try with attached patch. On Thu, Jan 25, 2001 at 07:44:05PM +0200, Valentin Nechayev wrote: > ===> share/doc/usd/13.viref > (cd /m4/REL4/src/share/doc/usd/13.viref/../../../../contrib/nvi/docs/USD.doc/vi. > ref; sed -e\ 's:\(\.so[\ \ ][\ \ ]*\)\(vi.ref\)$:\1/m4/REL4/src/share/doc > /usd/13.viref/../../../../contrib/nvi/docs/USD.doc/vi.ref/\2:' -e\ 's:\(\.so[\ \ > ][\ \ ]*\)\(ex.cmd.roff\)$:\1/m4/REL4/src/share/doc/usd/13.viref/../.. > /../../contrib/nvi/docs/USD.doc/vi.ref/\2:' -e\ 's:\(\.so[\ \ ][\ \ ]*\)\(re > f.so\)$:\1/m4/REL4/src/share/doc/usd/13.viref/../../../../contrib/nvi/docs/USD.d > oc/vi.ref/\2:' -e\ 's:\(\.so[\ \ ][\ \ ]*\)\(set.opt.roff\)$:\1/m4/REL4 > /src/share/doc/usd/13.viref/../../../../contrib/nvi/docs/USD.doc/vi.ref/\2:' -e\ > 's:\(\.so[\ \ ][\ \ ]*\)\(vi.cmd.roff\)$:\1/m4/REL4/src/share/doc/usd/13.vir > ef/../../../../contrib/nvi/docs/USD.doc/vi.ref/\2:' -e 's:^\.so index.so$::' vi. > ref) | groff -mtty-char -Tascii -t -s -me -U -o1- > /dev/null > groff: illegal option -- U > usage: groff [-abehilpstvzCENRSVXZ] [-Fdir] [-mname] [-Tdev] [-ffam] [-wname] > [-Wname] [ -Mdir] [-dcs] [-rcn] [-nnum] [-olist] [-Parg] [-Larg] > [files...] > groff -h gives more help > > > host OS is `FreeBSD 3.4-STABLE i386' > No words in src/UPDATING about it > > > /netch -- 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 --uAKRQypu60I7Lcqm Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=p Index: Makefile.inc1 =================================================================== RCS file: /home/ncvs/src/Makefile.inc1,v retrieving revision 1.141.2.19 diff -u -p -r1.141.2.19 Makefile.inc1 --- Makefile.inc1 2001/01/22 23:26:15 1.141.2.19 +++ Makefile.inc1 2001/01/25 17:47:57 @@ -168,6 +168,8 @@ CROSSENV= MAKEOBJDIRPREFIX=${OBJTREE} \ COMPILER_PATH=${WORLDTMP}/usr/libexec:${WORLDTMP}/usr/bin \ LIBRARY_PATH=${WORLDTMP}${SHLIBDIR}:${WORLDTMP}/usr/lib \ OBJFORMAT_PATH=${WORLDTMP}/usr/libexec \ + GROFF_FONT_PATH=${WORLDTMP}/usr/share/groff_font \ + GROFF_TMAC_PATH=${WORLDTMP}/usr/share/tmac \ PERL5LIB=${WORLDTMP}/usr/libdata/perl/5.00503 # bootstrap-tool stage @@ -199,7 +201,24 @@ IMAKEENV= ${CROSSENV} \ IMAKE= ${IMAKEENV} ${MAKE} -f Makefile.inc1 USRDIRS= usr/bin usr/lib/compat/aout usr/games usr/libdata/ldscripts \ - usr/libexec/${OBJFORMAT} usr/sbin usr/share/misc + usr/libexec/${OBJFORMAT} usr/sbin usr/share/misc \ + usr/share/tmac/locale usr/share/tmac/mdoc/locale \ + usr/share/tmac/mm \ + usr/share/groff_font/devX100 \ + usr/share/groff_font/devX100-12 \ + usr/share/groff_font/devX75 \ + usr/share/groff_font/devX75-12 \ + usr/share/groff_font/devascii \ + usr/share/groff_font/devcp1047 \ + usr/share/groff_font/devdvi \ + usr/share/groff_font/devhtml \ + usr/share/groff_font/devkoi8-r \ + usr/share/groff_font/devlatin1 \ + usr/share/groff_font/devlbp \ + usr/share/groff_font/devlj4 \ + usr/share/groff_font/devps \ + usr/share/groff_font/devutf8 \ + usr/share/dict .if ${MACHINE_ARCH} == "i386" && ${MACHINE} == "pc98" USRDIRS+= usr/libexec/aout @@ -222,7 +241,7 @@ buildworld: .if !defined(NOCLEAN) rm -rf ${WORLDTMP} .else - for dir in bin games include lib sbin; do \ + for dir in bin games include lib sbin share; do \ rm -rf ${WORLDTMP}/usr/$$dir; \ done rm -f ${WORLDTMP}/sys @@ -512,7 +531,7 @@ _strfile= games/fortune/strfile bootstrap-tools: .for _tool in ${_strfile} usr.bin/yacc usr.bin/colldef usr.sbin/config \ - gnu/usr.bin/gperf gnu/usr.bin/texinfo + gnu/usr.bin/gperf gnu/usr.bin/groff gnu/usr.bin/texinfo cd ${.CURDIR}/${_tool}; \ ${MAKE} obj; \ ${MAKE} depend; \ --uAKRQypu60I7Lcqm-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 25 9:52:10 2001 Delivered-To: freebsd-stable@freebsd.org Received: from VL-MS-MR003.sc1.videotron.ca (relais.videotron.ca [24.201.245.36]) by hub.freebsd.org (Postfix) with ESMTP id 25BC437B6A2 for ; Thu, 25 Jan 2001 09:51:48 -0800 (PST) Received: from southpark ([24.201.143.157]) by VL-MS-MR003.sc1.videotron.ca (Netscape Messaging Server 4.15) with SMTP id G7QC6505.BKX for ; Thu, 25 Jan 2001 12:49:17 -0500 Message-ID: <005a01c086f7$337f51c0$9d8fc918@videotron.ca> From: "Luc Morin" To: References: <001001c08628$8db16180$9d8fc918@videotron.ca> <20010124164125.A12612@home.com> <01012500480800.01077@jamestown.enteract.com> <3A6FD545.3D329446@quake.com.au> <002b01c086e4$2c843060$9d8fc918@videotron.ca> <3A705EAA.23BD59B4@quake.com.au> Subject: Re: Network stops working Date: Thu, 25 Jan 2001 12:49:43 -0500 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_0057_01C086CD.4A1239E0" 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_0057_01C086CD.4A1239E0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Hi, I've been asked to clarify the topology of my system. Very simple setup. All I have is my home box connected to my ISP thru cable-modem. My NIC is a PCI NE2000 clone using the ed driver. My ISP uses DHCP to assign my IP, so I run dhclient at boot time from my rc.conf file. This setup has been running fine for me for over a year now. Even after my last cvsup/buildworld everything was still perfectly working. A few days ago, I started getting a situation where after a few minutes of operation (after boot), I can't reach anything, not even my default gateway (assigned by my ISP as part of DHCP). I've talked to my ISP's tech support rep, and he told me he could ping my box just fine ( 0% packet loss ), while I couldn't ping anything ( 100% packet loss ). I also noticed that even though I can't reach the outside world, I still see some syslogd messages about failed attempt to connect to my box (I have log_in_vain="YES" in rc.conf). Please see attached file for specifics of my system (kernel config file, dmesg output, uname -a, ps -ax etc...) I hope this clarifies the situation :-) Many thanks, Luc Morin ------=_NextPart_000_0057_01C086CD.4A1239E0 Content-Type: text/plain; name="info.txt" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="info.txt" uname -a ouput:=0A= =0A= FreeBSD southpark.videotron.ca 4.2-STABLE FreeBSD 4.2-STABLE #0: Thu Jan = 18 18:00:27 EST 2001 = root@southpark.videotron.ca:/usr/obj/usr/src/sys/MYKERN4 i386=0A= =0A= =0A= dmesg output=0A= =0A= Copyright (c) 1992-2001 The FreeBSD Project.=0A= Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994=0A= The Regents of the University of California. All rights reserved.=0A= FreeBSD 4.2-STABLE #0: Thu Jan 18 18:00:27 EST 2001=0A= root@southpark.videotron.ca:/usr/obj/usr/src/sys/MYKERN4=0A= Timecounter "i8254" frequency 1193182 Hz=0A= CPU: Pentium III/Pentium III Xeon/Celeron (501.14-MHz 686-class CPU)=0A= Origin =3D "GenuineIntel" Id =3D 0x673 Stepping =3D 3=0A= = Features=3D0x383f9ff=0A= real memory =3D 134201344 (131056K bytes)=0A= Invalid command or syntax. Type `?' for help.=0A= avail memory =3D 127844352 (124848K bytes)=0A= Preloaded elf kernel "kernel" at 0xc02d7000.=0A= Preloaded userconfig_script "/boot/kernel.conf" at 0xc02d709c.=0A= Pentium Pro MTRR support enabled=0A= npx0: on motherboard=0A= npx0: INT 16 interface=0A= pcib0: on motherboard=0A= pci0: on pcib0=0A= pcib1: at device 1.0 on = pci0=0A= pci1: on pcib1=0A= pci1: at 0.0 irq 11=0A= isab0: at device 4.0 on pci0=0A= isa0: on isab0=0A= atapci0: port 0xb800-0xb80f at device 4.1 = on pci0=0A= ata0: at 0x1f0 irq 14 on atapci0=0A= ata1: at 0x170 irq 15 on atapci0=0A= pci0: at 4.2 irq 5=0A= chip1: port 0xe800-0xe80f at = device 4.3 on pci0=0A= pcm0: port 0xb000-0xb03f irq 10 at device 10.0 on pci0=0A= ed0: port 0xa800-0xa81f irq 5 at = device 13.0 on pci0=0A= ed0: address 00:e0:29:40:c0:4f, type NE2000 (16 bit) =0A= fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0=0A= fdc0: FIFO enabled, 8 bytes threshold=0A= fd0: <1440-KB 3.5" drive> on fdc0 drive 0=0A= atkbdc0: at port 0x60,0x64 on isa0=0A= atkbd0: irq 1 on atkbdc0=0A= psm0: irq 12 on atkbdc0=0A= psm0: model IntelliMouse, device ID 3=0A= vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0=0A= sc0: on isa0=0A= sc0: VGA <16 virtual consoles, flags=3D0x200>=0A= sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0=0A= sio0: type 16550A=0A= sio1 at port 0x2f8-0x2ff irq 3 on isa0=0A= sio1: type 16550A=0A= ppc0: at port 0x378-0x37f irq 7 on isa0=0A= ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode=0A= ppbus0: IEEE1284 device found /NIBBLE/ECP=0A= Probing for PnP devices on ppbus0:=0A= ppbus0: PRINTER MLC,PCL,PJL=0A= lpt0: on ppbus0=0A= lpt0: Interrupt-driven port=0A= IP Filter: v3.4.8 initialized. Default =3D pass all, Logging =3D = disabled=0A= ata0-master: DMA limited to UDMA33, non-ATA66 compliant cable=0A= ad0: 13216MB [26853/16/63] at ata0-master = UDMA33=0A= ata1-master: DMA limited to UDMA33, non-ATA66 compliant cable=0A= ad2: 8063MB [16383/16/63] at ata1-master UDMA33=0A= ad3: 3079MB [6256/16/63] at ata1-slave UDMA33=0A= acd0: CDROM at ata0-slave using PIO4=0A= Mounting root from ufs:/dev/ad0s2a=0A= =0A= =0A= ifconfig -a output:=0A= =0A= ed0: flags=3D8843 mtu 1500=0A= inet 24.200.211.9 netmask 0xffffff00 broadcast 255.255.255.255=0A= ether 00:e0:29:40:c0:4f =0A= lo0: flags=3D8049 mtu 16384=0A= inet 127.0.0.1 netmask 0xff000000 =0A= =0A= =0A= cat /usr/src/sys/i386/conf/MYKERN4 ouput:=0A= =0A= machine i386=0A= cpu I686_CPU=0A= ident MYKERN4=0A= maxusers 10=0A= =0A= =0A= options INET #InterNETworking=0A= options IPFILTER=0A= options FFS #Berkeley Fast Filesystem=0A= options FFS_ROOT #FFS usable as root device [keep this!]=0A= options MSDOSFS #MSDOS Filesystem=0A= options CD9660 #ISO 9660 Filesystem=0A= options PROCFS #Process filesystem=0A= options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!]=0A= options UCONSOLE #Allow users to grab the console=0A= options USERCONFIG #boot -c editor=0A= options VISUAL_USERCONFIG #visual boot -c editor=0A= options KTRACE #ktrace(1) support=0A= options SYSVSHM #SYSV-style shared memory=0A= options SYSVMSG #SYSV-style message queues=0A= options SYSVSEM #SYSV-style semaphores=0A= options USER_LDT=0A= options P1003_1B #Posix P1003_1B real-time extentions=0A= options _KPOSIX_PRIORITY_SCHEDULING=0A= options ICMP_BANDLIM #Rate limit bad replies=0A= =0A= device isa=0A= device pci=0A= =0A= # Floppy drives=0A= device fdc0 at isa? port IO_FD1 irq 6 drq 2=0A= device fd0 at fdc0 drive 0=0A= =0A= # ATA and ATAPI devices=0A= device ata=0A= device atadisk # ATA disk drives=0A= device atapicd # ATAPI CDROM drives=0A= options ATA_STATIC_ID #Static device numbering=0A= options ATA_ENABLE_ATAPI_DMA #Enable DMA on ATAPI devices=0A= =0A= =0A= # atkbdc0 controls both the keyboard and the PS/2 mouse=0A= device atkbdc0 at isa? port IO_KBD=0A= device atkbd0 at atkbdc? irq 1=0A= device psm0 at atkbdc? irq 12=0A= =0A= device vga0 at isa?=0A= =0A= # splash screen/screen saver=0A= pseudo-device splash=0A= =0A= # syscons is the default console driver, resembling an SCO console=0A= device sc0 at isa?=0A= =0A= # Floating point support - do not disable.=0A= device npx0 at nexus? port IO_NPX irq 13=0A= =0A= # Power management support (see LINT for more options)=0A= device apm0 at nexus? disable flags 0x20 # Advanced Power Management=0A= =0A= # Serial (COM) ports=0A= device sio0 at isa? port IO_COM1 flags 0x10 irq 4=0A= device sio1 at isa? port IO_COM2 irq 3=0A= =0A= # Parallel port=0A= device ppc0 at isa? irq 7=0A= device ppbus # Parallel port bus (required)=0A= device lpt # Printer=0A= =0A= # PCI Ethernet NICs.=0A= device ed0=0A= =0A= # Pseudo devices - the number indicates how many units to allocated.=0A= pseudo-device loop # Network loopback=0A= pseudo-device ether # Ethernet support=0A= pseudo-device tun # Packet tunnel.=0A= pseudo-device pty # Pseudo-ttys (telnet etc)=0A= =0A= # The `bpf' pseudo-device enables the Berkeley Packet Filter.=0A= # Be aware of the administrative consequences of enabling this!=0A= pseudo-device bpf #Berkeley packet filter=0A= =0A= options TCP_DROP_SYNFIN #drop TCP packets with SYN+FIN=0A= options TCP_RESTRICT_RST #restrict emission of TCP RST =0A= =0A= #Sound=0A= device pcm=0A= PID TT STAT TIME COMMAND=0A= 0 ?? DLs 0:00.00 (swapper)=0A= 1 ?? ILs 0:00.01 /sbin/init --=0A= 2 ?? DL 0:00.00 (pagedaemon)=0A= 3 ?? DL 0:00.00 (vmdaemon)=0A= 4 ?? DL 0:00.00 (bufdaemon)=0A= 5 ?? DL 0:00.00 (syncer)=0A= 40 ?? Is 0:00.00 adjkerntz -i=0A= 115 ?? Is 0:00.00 /sbin/dhclient ed0=0A= 139 ?? Ss 0:00.03 syslogd -s=0A= 158 ?? Is 0:00.00 cron=0A= 227 v0 Ss 0:00.06 -bash (bash)=0A= 248 v0 R+ 0:00.00 ps -ax=0A= 228 v1 Is+ 0:00.00 /usr/libexec/getty Pc ttyv1=0A= 229 v2 Is+ 0:00.00 /usr/libexec/getty Pc ttyv2=0A= 230 v3 Is+ 0:00.01 /usr/libexec/getty Pc ttyv3=0A= 231 v4 Is+ 0:00.00 /usr/libexec/getty Pc ttyv4=0A= 232 v5 Is+ 0:00.00 /usr/libexec/getty Pc ttyv5=0A= 233 v6 Is+ 0:00.00 /usr/libexec/getty Pc ttyv6=0A= 234 v7 Is+ 0:00.00 /usr/libexec/getty Pc ttyv7=0A= ------=_NextPart_000_0057_01C086CD.4A1239E0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 25 10: 2:50 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail.rdc1.il.home.com (ha1.rdc1.il.home.com [24.2.1.66]) by hub.freebsd.org (Postfix) with ESMTP id 3867537B400 for ; Thu, 25 Jan 2001 10:02:29 -0800 (PST) Received: from math.missouri.edu ([24.12.197.197]) by mail.rdc1.il.home.com (InterMail vM.4.01.03.00 201-229-121) with ESMTP id <20010125180228.QQGI24109.mail.rdc1.il.home.com@math.missouri.edu>; Thu, 25 Jan 2001 10:02:28 -0800 Message-ID: <3A706A34.E5F1C502@math.missouri.edu> Date: Thu, 25 Jan 2001 12:02:28 -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: Luc Morin Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Network stops working References: <001001c08628$8db16180$9d8fc918@videotron.ca> <20010124164125.A12612@home.com> <01012500480800.01077@jamestown.enteract.com> <3A6FD545.3D329446@quake.com.au> <002b01c086e4$2c843060$9d8fc918@videotron.ca> <3A705EAA.23BD59B4@quake.com.au> <005a01c086f7$337f51c0$9d8fc918@videotron.ca> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG That's interesting - I have a similar problem that also just started recently (coincided with changing my power supply but I'm sure that it is unrelated). I find that one of three things happens: 1. dhcp simply does not successfully negotiate 2. dhcp negotiates, gets an IP number and a router, but then I get 100% packet loss. (Never tried calling them to see if they got through to me.) 3. It actually works. Option 2 is what usually happens, but if I restarting dhcp enough times, I get option 3. Since I keep the connection up all the time, I only worry about the problem sporadically. So I have never tried to investigate its cause. (The ISP is att@home if that is useful. My NIC is a RealTek 8139.) Luc Morin wrote: > > Hi, > > I've been asked to clarify the topology of my system. > > Very simple setup. All I have is my home box connected to my ISP > thru cable-modem. My NIC is a PCI NE2000 clone using the ed driver. > > My ISP uses DHCP to assign my IP, so I run dhclient at boot time > from my rc.conf file. This setup has been running fine for me for over > a year now. Even after my last cvsup/buildworld everything was > still perfectly working. > > A few days ago, I started getting a situation where after a few > minutes of operation (after boot), I can't reach anything, not even > my default gateway (assigned by my ISP as part of DHCP). > > I've talked to my ISP's tech support rep, and he told me he could > ping my box just fine ( 0% packet loss ), while I couldn't ping > anything ( 100% packet loss ). I also noticed that even though > I can't reach the outside world, I still see some syslogd messages > about failed attempt to connect to my box (I have log_in_vain="YES" > in rc.conf). > > Please see attached file for specifics of my system (kernel config > file, dmesg output, uname -a, ps -ax etc...) > > I hope this clarifies the situation :-) > > Many thanks, > > Luc Morin > > -------------------------------------------------------------------------------- > Name: info.txt > info.txt Type: Plain Text (text/plain) > Encoding: quoted-printable -- 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 25 10: 6:18 2001 Delivered-To: freebsd-stable@freebsd.org Received: from nova.fnal.gov (nova.fnal.gov [131.225.18.207]) by hub.freebsd.org (Postfix) with ESMTP id 398D837B400 for ; Thu, 25 Jan 2001 10:05:53 -0800 (PST) Received: from localhost (tez@localhost) by nova.fnal.gov (8.9.3+Sun/8.9.1) with ESMTP id MAA19836; Thu, 25 Jan 2001 12:05:42 -0600 (CST) X-Authentication-Warning: nova.fnal.gov: tez owned process doing -bs Date: Thu, 25 Jan 2001 12:05:41 -0600 (CST) From: Tim Zingelman X-Sender: To: Kent Stewart Cc: Mike Tancsa , Dag-Erling Smorgrav , Subject: Re: broken pipes on make world In-Reply-To: <3A62636D.4DB982AD@urx.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 > 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 I just checked out, built, installed, & mergemastered... # uname -a FreeBSD xxx.xxx.xxx 4.2-STABLE FreeBSD 4.2-STABLE #0: Mon Dec 25 14:22:10 CST 2000 tez@xxx.xxx.xxx:/usr/obj/usr/src/sys/DELLQUAD i386 I can not duplicate your problem... $ ssh xxx.xxx.xxx xxx@xxx's password: xxx $ su toor Password: xxx # cd /usr/src/share/man # makewhatis -v /usr/share/man ... Maybe /usr/share/man/man3/heap.3.gz is not a manpage ... The above message is the only warning or error I get. - Tim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 25 10:15: 6 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 1A81F37B6A6 for ; Thu, 25 Jan 2001 10:14:45 -0800 (PST) Received: from onceler.kciLink.com (onceler.kciLink.com [208.184.13.196]) by yertle.kciLink.com (Postfix) with ESMTP id 5FA1F2E443 for ; Thu, 25 Jan 2001 13:14:44 -0500 (EST) Received: (from khera@localhost) by onceler.kciLink.com (8.11.1/8.11.1) id f0PIEik41998; Thu, 25 Jan 2001 13:14:44 -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: <14960.27924.178649.827064@onceler.kciLink.com> Date: Thu, 25 Jan 2001 13:14:44 -0500 To: stable@freebsd.org Subject: Re: How to mount iso image file???? Newsgroups: comp.unix.bsd.freebsd.misc In-Reply-To: <14959.27599.550911.821713@hip186.ch.intel.com> References: <3A6F69FD.97E74874@esec.com.au> <14959.27599.550911.821713@hip186.ch.intel.com> 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 >>>>> "j" == jreynold writes: j> Yup. You have to have 'pseudo-device vn' in your kernel config and you have j> to make sure the vn* devices are made in /dev. Once you do that, the following j> commands will work: vnconfig will automagically load the vn kernel module if it needs. you don't have to have it statically built in your kernel. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 25 10:21: 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 9637437B6A7 for ; Thu, 25 Jan 2001 10:20:45 -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 f0PIKhj38107; Thu, 25 Jan 2001 13:20:43 -0500 (EST) (envelope-from mike@sentex.net) Message-Id: <5.0.1.4.0.20010125131220.02b2b320@marble.sentex.ca> X-Sender: mdtpop@marble.sentex.ca X-Mailer: QUALCOMM Windows Eudora Version 5.0.1 Date: Thu, 25 Jan 2001 13:14:58 -0500 To: Tim Zingelman From: Mike Tancsa Subject: Re: broken pipes on make world Cc: In-Reply-To: References: <3A62636D.4DB982AD@urx.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 12:05 PM 1/25/01 -0600, Tim Zingelman wrote: ># uname -a >FreeBSD xxx.xxx.xxx 4.2-STABLE FreeBSD 4.2-STABLE #0: Mon Dec 25 >14:22:10 CST 2000 tez@xxx.xxx.xxx:/usr/obj/usr/src/sys/DELLQUAD i386 Try a more recent build. i.e. one after the recent ssh commits green 2001/01/11 20:26:22 PST Modified files: (Branch: RELENG_4) crypto/openssh LICENCE Makefile.inc RFC.nroff atomicio.c auth-krb4.c auth-options.c auth-options.h To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 25 10:28:51 2001 Delivered-To: freebsd-stable@freebsd.org Received: from hedwig.internal.webtrends.com (unknown [206.58.83.57]) by hub.freebsd.org (Postfix) with ESMTP id 5771437B402 for ; Thu, 25 Jan 2001 10:28:30 -0800 (PST) Received: by HEDWIG.internal.webtrends.com with Internet Mail Service (5.5.2653.19) id ; Thu, 25 Jan 2001 10:26:41 -0800 Message-ID: <0145F0769FECD411BF8400508BFDF6E4048E80@newman.internal.webtrends.com> From: Dustin Harris To: 'Doug White' , Mikhail Kononenko Cc: freebsd-stable@FreeBSD.ORG Subject: RE: EtherExpress100 on Intel Easton Date: Thu, 25 Jan 2001 10:28:28 -0800 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG There is usually a newer eepro100 driver at the maintainer's site than what is distributed in the kernel source (ftp://ftp.scyld.com/pub/network/test/eepro100.c). --dustin -----Original Message----- From: Doug White [mailto:dwhite@resnet.uoregon.edu] Sent: Wednesday, January 24, 2001 11:18 PM To: Mikhail Kononenko Cc: freebsd-stable@FreeBSD.ORG Subject: Re: EtherExpress100 on Intel Easton On Wed, 24 Jan 2001, Mikhail Kononenko wrote: > Sorry, if this is offtopic here, but I could not get answer from native > lists... > > Linux kernel-2.2.17 on D815EEAL (with integrated NIC). The driver used: > eepro100. Traditionally, the Linux Intel EtherExpress Pro/100 drivers have, quite frankly, sucked. This is a known problem with no solution. This is counter to FreeBSD, where the fxp driver is one of the best ethernet drivers in the system :-) Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | www.FreeBSD.org 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 25 10:38:47 2001 Delivered-To: freebsd-stable@freebsd.org Received: from rainbow.samovar.ru (unknown [192.124.176.109]) by hub.freebsd.org (Postfix) with ESMTP id AD14E37B402 for ; Thu, 25 Jan 2001 10:38:25 -0800 (PST) Received: from mikhail ([212.12.71.30]) by rainbow.samovar.ru (8.9.3/8.9.3) with SMTP id VAA23248; Thu, 25 Jan 2001 21:37:51 +0300 (MSK) Message-ID: <026801c086fd$f270cae0$210aa8c0@mikhail> From: "Mikhail Kononenko" To: "Dustin Harris" Cc: References: <0145F0769FECD411BF8400508BFDF6E4048E80@newman.internal.webtrends.com> Subject: Re: EtherExpress100 on Intel Easton Date: Thu, 25 Jan 2001 21:37:47 +0300 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 Dustin Harris wrote: > There is usually a newer eepro100 driver at the maintainer's site than what > is distributed in the kernel source > (ftp://ftp.scyld.com/pub/network/test/eepro100.c). Thanks, Dustin! It was exactly what I did. The new version (1.03) seems to work. But we'll see. Anyway, thanks to all, who replied to me off-line, and for Ben Lutgens: I checked the driver file, #define USE IO=1 was alredy there... Since I now have weird problem with hard drives detection, which prevents me to build reliable soft RAID-1, I wonder if this (soft RAID-1,5) possible under FreeBSD? But first I should pinpoint the problem with HD detection on this damn Intel Easton, of course. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 25 11: 1:20 2001 Delivered-To: freebsd-stable@freebsd.org Received: from blandings.com (adsl-216-103-90-79.dsl.snfc21.pacbell.net [216.103.90.79]) by hub.freebsd.org (Postfix) with ESMTP id B009737B6B1; Thu, 25 Jan 2001 11:00:57 -0800 (PST) Received: (from anand@localhost) by blandings.com (8.11.1/8.11.1) id f0PIfdI03203; Thu, 25 Jan 2001 10:41:39 -0800 (PST) (envelope-from anand) Date: Thu, 25 Jan 2001 10:41:38 -0800 From: Anand To: stable@freebsd.org, multimedia@freebsd.org Subject: soundmax card? Message-ID: <20010125104138.A3123@Psmith.blandings.com> Reply-To: anand@blandings.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 Hi, I have a Dell desktop with an integrated soundmax card. It uses an AD 188x chip. I'm wondering if this is supported under FreeBSD or if people have had success with this card. Thanks a lot. Anand -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 25 11: 2:53 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 CA0A237B6B0 for ; Thu, 25 Jan 2001 11:02:33 -0800 (PST) Received: from boomer.forrie.com (dhcp-north-71-168.navipath.net [64.20.71.168]) by forrie.net with id f0PJ2W156507 for ; Thu, 25 Jan 2001 14:02:32 -0500 (EST) Message-Id: <5.0.2.1.2.20010125140054.00a8ab30@216.67.14.69> X-Sender: forrie@216.67.14.69 X-Mailer: QUALCOMM Windows Eudora Version 5.0.2 Date: Thu, 25 Jan 2001 14:01:35 -0500 To: freebsd-stable@freebsd.org From: Forrest Aldrich Subject: World build failure 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 Make world is failing on /usr/src/games/morse (despite my telling make.conf not to build games). Can someone please fix this. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 25 11: 7: 3 2001 Delivered-To: freebsd-stable@freebsd.org Received: from vexpert.dbai.tuwien.ac.at (vexpert.dbai.tuwien.ac.at [128.130.111.12]) by hub.freebsd.org (Postfix) with ESMTP id 68C1937B6AD; Thu, 25 Jan 2001 11:06:38 -0800 (PST) Received: from taygeta.dbai.tuwien.ac.at (taygeta [128.130.111.77]) by vexpert.dbai.tuwien.ac.at (8.11.1/8.11.1) with ESMTP id f0PJ6ae03717; Thu, 25 Jan 2001 20:06:36 +0100 (MET) Received: from localhost (pfeifer@localhost) by taygeta.dbai.tuwien.ac.at (8.11.1/8.11.1) with ESMTP id f0PJ6aG14022; Thu, 25 Jan 2001 20:06:38 +0100 (CET) (envelope-from pfeifer@dbai.tuwien.ac.at) X-Authentication-Warning: taygeta.dbai.tuwien.ac.at: pfeifer owned process doing -bs Date: Thu, 25 Jan 2001 20:06:36 +0100 (CET) From: Gerald Pfeifer To: Cc: Subject: http://www.freebsd.org/releases/4.2R/errata.html 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 ...is out of date and does not match the version found at ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/4.2-RELEASE/ERRATA.TXT I strongly feel that the version on the web should be up-to-date, and indeed this seems to have been the case for earlier releases. Also having *both* online versions say "This ERRATA.TXT file is obviously already out of date by definition" does not seem correct, either. Gerald -- Gerald "Jerry" pfeifer@dbai.tuwien.ac.at http://www.dbai.tuwien.ac.at/~pfeifer/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 25 11:10:38 2001 Delivered-To: freebsd-stable@freebsd.org Received: from burka.carrier.kiev.ua (burka.carrier.kiev.ua [193.193.193.107]) by hub.freebsd.org (Postfix) with ESMTP id 2938D37B6AD; Thu, 25 Jan 2001 11:10:17 -0800 (PST) Received: from netch@localhost by burka.carrier.kiev.ua id VDY45063; Thu, 25 Jan 2001 21:10:15 +0200 (EET) (envelope-from netch) Date: Thu, 25 Jan 2001 21:10:15 +0200 From: Valentin Nechayev To: freebsd-stable@FreeBSD.ORG, ru@FreeBSD.ORG Subject: Re: make buildworld fails: share/doc/usd/13.viref Message-ID: <20010125211015.Z31587@lucky.net> Reply-To: netch@lucky.net References: <20010125194405.W31587@lucky.net> <20010125194832.A42750@sunbay.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20010125194832.A42750@sunbay.com>; from ru@FreeBSD.ORG on Thu, Jan 25, 2001 at 07:48:32PM +0200 X-42: On Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thu, Jan 25, 2001 at 19:48:32, ru wrote about "Re: make buildworld fails: share/doc/usd/13.viref": > Please try with attached patch. === cut === ===> libgroff c++ -I/usr/obj/m4/REL4/src/i386/usr/include/g++ -O -m486 -pipe -I/m4/REL4/src/gn u/usr.bin/groff/libgroff/../include -DHAVE_UNISTD_H=1 -DHAVE_DIRENT_H=1 -DHAVE_L IMITS_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_STRINGS_H=1 -DHAVE_MATH_H=1 -DRET_TYPE_SRAND_IS_VOID=1 -DHAVE_SYS_NERR=1 -DHAVE_SYS_ERRLIST=1 -DHAVE_CC_LIM ITS_H=1 -DRETSIGTYPE=void -DHAVE_STRUCT_EXCEPTION=1 -DHAVE_GETPAGESIZE=1 -DHAVE_ MMAP=1 -DHAVE_FMOD=1 -DHAVE_STRTOL=1 -DHAVE_GETCWD=1 -DHAVE_STRERROR=1 -DHAVE_PU TENV=1 -DHAVE_RENAME=1 -DHAVE_MKSTEMP=1 -DHAVE_STRCASECMP=1 -DHAVE_STRNCASECMP=1 -DHAVE_STRSEP=1 -DHAVE_STRDUP=1 -DSYS_SIGLIST_DECLARED=1 -I/m4/REL4/src/gnu/usr .bin/groff/libgroff/../../../../contrib/groff/include -fno-for-scope -I/usr/obj/ m4/REL4/src/i386/usr/include -fno-rtti -fno-exceptions -c /m4/REL4/src/gnu/usr.b in/groff/libgroff/../../../../contrib/groff/libgroff/assert.cc -o assert.o cc1plus: Invalid option `-fno-exceptions' *** Error code 1 === end cut === The same conditions: target system is 4-stable, host one is 3.4-stable > On Thu, Jan 25, 2001 at 07:44:05PM +0200, Valentin Nechayev wrote: > > ===> share/doc/usd/13.viref > > (cd /m4/REL4/src/share/doc/usd/13.viref/../../../../contrib/nvi/docs/USD.doc/vi. > > ref; sed -e\ 's:\(\.so[\ \ ][\ \ ]*\)\(vi.ref\)$:\1/m4/REL4/src/share/doc > > /usd/13.viref/../../../../contrib/nvi/docs/USD.doc/vi.ref/\2:' -e\ 's:\(\.so[\ \ > > ][\ \ ]*\)\(ex.cmd.roff\)$:\1/m4/REL4/src/share/doc/usd/13.viref/../.. > > /../../contrib/nvi/docs/USD.doc/vi.ref/\2:' -e\ 's:\(\.so[\ \ ][\ \ ]*\)\(re > > f.so\)$:\1/m4/REL4/src/share/doc/usd/13.viref/../../../../contrib/nvi/docs/USD.d > > oc/vi.ref/\2:' -e\ 's:\(\.so[\ \ ][\ \ ]*\)\(set.opt.roff\)$:\1/m4/REL4 > > /src/share/doc/usd/13.viref/../../../../contrib/nvi/docs/USD.doc/vi.ref/\2:' -e\ > > 's:\(\.so[\ \ ][\ \ ]*\)\(vi.cmd.roff\)$:\1/m4/REL4/src/share/doc/usd/13.vir > > ef/../../../../contrib/nvi/docs/USD.doc/vi.ref/\2:' -e 's:^\.so index.so$::' vi. > > ref) | groff -mtty-char -Tascii -t -s -me -U -o1- > /dev/null > > groff: illegal option -- U > > usage: groff [-abehilpstvzCENRSVXZ] [-Fdir] [-mname] [-Tdev] [-ffam] [-wname] > > [-Wname] [ -Mdir] [-dcs] [-rcn] [-nnum] [-olist] [-Parg] [-Larg] > > [files...] > > groff -h gives more help > > > > > > host OS is `FreeBSD 3.4-STABLE i386' > > No words in src/UPDATING about it > > > > > > /netch > > -- > 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 > Index: Makefile.inc1 > =================================================================== > RCS file: /home/ncvs/src/Makefile.inc1,v > retrieving revision 1.141.2.19 > diff -u -p -r1.141.2.19 Makefile.inc1 > --- Makefile.inc1 2001/01/22 23:26:15 1.141.2.19 > +++ Makefile.inc1 2001/01/25 17:47:57 > @@ -168,6 +168,8 @@ CROSSENV= MAKEOBJDIRPREFIX=${OBJTREE} \ > COMPILER_PATH=${WORLDTMP}/usr/libexec:${WORLDTMP}/usr/bin \ > LIBRARY_PATH=${WORLDTMP}${SHLIBDIR}:${WORLDTMP}/usr/lib \ > OBJFORMAT_PATH=${WORLDTMP}/usr/libexec \ > + GROFF_FONT_PATH=${WORLDTMP}/usr/share/groff_font \ > + GROFF_TMAC_PATH=${WORLDTMP}/usr/share/tmac \ > PERL5LIB=${WORLDTMP}/usr/libdata/perl/5.00503 > > # bootstrap-tool stage > @@ -199,7 +201,24 @@ IMAKEENV= ${CROSSENV} \ > IMAKE= ${IMAKEENV} ${MAKE} -f Makefile.inc1 > > USRDIRS= usr/bin usr/lib/compat/aout usr/games usr/libdata/ldscripts \ > - usr/libexec/${OBJFORMAT} usr/sbin usr/share/misc > + usr/libexec/${OBJFORMAT} usr/sbin usr/share/misc \ > + usr/share/tmac/locale usr/share/tmac/mdoc/locale \ > + usr/share/tmac/mm \ > + usr/share/groff_font/devX100 \ > + usr/share/groff_font/devX100-12 \ > + usr/share/groff_font/devX75 \ > + usr/share/groff_font/devX75-12 \ > + usr/share/groff_font/devascii \ > + usr/share/groff_font/devcp1047 \ > + usr/share/groff_font/devdvi \ > + usr/share/groff_font/devhtml \ > + usr/share/groff_font/devkoi8-r \ > + usr/share/groff_font/devlatin1 \ > + usr/share/groff_font/devlbp \ > + usr/share/groff_font/devlj4 \ > + usr/share/groff_font/devps \ > + usr/share/groff_font/devutf8 \ > + usr/share/dict > > .if ${MACHINE_ARCH} == "i386" && ${MACHINE} == "pc98" > USRDIRS+= usr/libexec/aout > @@ -222,7 +241,7 @@ buildworld: > .if !defined(NOCLEAN) > rm -rf ${WORLDTMP} > .else > - for dir in bin games include lib sbin; do \ > + for dir in bin games include lib sbin share; do \ > rm -rf ${WORLDTMP}/usr/$$dir; \ > done > rm -f ${WORLDTMP}/sys > @@ -512,7 +531,7 @@ _strfile= games/fortune/strfile > > bootstrap-tools: > .for _tool in ${_strfile} usr.bin/yacc usr.bin/colldef usr.sbin/config \ > - gnu/usr.bin/gperf gnu/usr.bin/texinfo > + gnu/usr.bin/gperf gnu/usr.bin/groff gnu/usr.bin/texinfo > cd ${.CURDIR}/${_tool}; \ > ${MAKE} obj; \ > ${MAKE} depend; \ /netch To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 25 11:13:17 2001 Delivered-To: freebsd-stable@freebsd.org Received: from palrel3.hp.com (palrel3.hp.com [156.153.255.226]) by hub.freebsd.org (Postfix) with ESMTP id C175237B6AD; Thu, 25 Jan 2001 11:12:56 -0800 (PST) Received: from adlmail.cup.hp.com (adlmail.cup.hp.com [15.0.100.30]) by palrel3.hp.com (Postfix) with ESMTP id ED0DEAE3; Thu, 25 Jan 2001 11:12:55 -0800 (PST) Received: from cup.hp.com (gauss.cup.hp.com [15.28.97.152]) by adlmail.cup.hp.com (8.9.3 (PHNE_18546)/8.9.3 SMKit7.02) with ESMTP id LAA27469; Thu, 25 Jan 2001 11:12:55 -0800 (PST) Message-ID: <3A707AB7.53C0BB11@cup.hp.com> Date: Thu, 25 Jan 2001 11:12:55 -0800 From: Marcel Moolenaar Organization: Hewlett-Packard X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Ruslan Ermilov Cc: rene@xs4all.nl, stable@FreeBSD.org Subject: Re: Bootstrapping issues with groff(1) References: <20001216171526.A28853@sunbay.com> <20010124182729.A22713@xs4all.nl> <20001208181908.A12716@sunbay.com> <3A319751.D2C9E5AB@cup.hp.com> <20001209154347.A78374@sunbay.com> <3A329641.CC6D8447@cup.hp.com> <20001211094815.D96665@sunbay.com> <3A3509E9.F1D19305@cup.hp.com> <20001212102344.B92312@sunbay.com> <3A3663DB.2DA71F0E@cup.hp.com> <20010125142504.A15489@sunbay.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 don't know why -current is CC'd this is clearly about -stable] Ruslan Ermilov wrote: > > Attached is the patch for RELENG_4. It works but I don't like > how it pollutes the Makefile.inc1. Anyone with a better idea? Allow me to sidetrack for a moment: I just ugraded a machine from 4.1 to 4.2-stable without any problems. I'm a bit confused. Rene picks up RELENG_4 and sees his build fail. Why did it work for me? -- Marcel Moolenaar mail: marcel@cup.hp.com / marcel@FreeBSD.org tel: (408) 447-4222 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 25 11:36:33 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 9D7FE37B6B4 for ; Thu, 25 Jan 2001 11:36:08 -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 14LsAL-000C0c-00 for freebsd-stable@freebsd.org; Thu, 25 Jan 2001 22:34:42 +0300 Received: from wash by poeza.iconnect.co.ke with local (Exim 3.20 #1) id 14LsCB-000IRP-00 for freebsd-stable@FreeBSD.ORG; Thu, 25 Jan 2001 22:36:35 +0300 Date: Thu, 25 Jan 2001 22:36:35 +0300 From: Odhiambo Washington To: freebsd-stable@FreeBSD.ORG Subject: Re: Ports update - is something broken? Message-ID: <20010125223635.F70366@poeza.iconnect.co.ke> Mail-Followup-To: Odhiambo Washington , freebsd-stable@FreeBSD.ORG References: <3A702B20.EBEE505@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: ; from "Bob K" on Thu, Jan 25, 2001 at 09:12:35AM -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 * Bob K [20010125 17:14]: writing on the subject 'Re: Ports update - is something broken?' Bob> On Fri, 26 Jan 2001, Kal Torak wrote: Bob> Bob> > I think you will find cvsup didnt remove some of the old stuff in your Bob> > ports tree... A simple solution if you have the time is to rm -rf your Bob> > ports and cvsup them again... Bob> Bob> Actually, Dmitry probably needs to download an upgrade kit from Bob> http://www.freebsd.org/ports/ . *default host=CHANGE_THIS.FreeBSD.org *default base=/usr *default prefix=/usr *default release=cvs tag=. *default delete use-rel-suffix ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Or did he remove that from the supfile? -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. Many come to bring their clothes to church rather than themselves. -Thomas Fuller To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 25 11:41:58 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 DC51F37B6B7 for ; Thu, 25 Jan 2001 11:41:31 -0800 (PST) Received: from boomer.forrie.com (dhcp-north-71-168.navipath.net [64.20.71.168]) by forrie.net with id f0PJfU156612 for ; Thu, 25 Jan 2001 14:41:31 -0500 (EST) Message-Id: <5.0.2.1.2.20010125143821.00a7e770@216.67.14.69> X-Sender: forrie@216.67.14.69 X-Mailer: QUALCOMM Windows Eudora Version 5.0.2 Date: Thu, 25 Jan 2001 14:40:35 -0500 To: freebsd-stable@freebsd.org From: Forrest Aldrich Subject: Re: World build failure In-Reply-To: <20010125223159.E70366@poeza.iconnect.co.ke> References: <5.0.2.1.2.20010125140054.00a8ab30@216.67.14.69> <5.0.2.1.2.20010125140054.00a8ab30@216.67.14.69> 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 It seems that it should be configured (in the build process) as a non-fatal error. My opinion: "games" is hardly an important part of the operating system. In fact, why cannot "games" be split into ports, so that they can be maintained differently and otherwise optionally installed. _F At 10:31 PM 1/25/2001 +0300, Odhiambo Washington wrote: >* Forrest Aldrich [20010125 22:03]: writing on the >subject 'World build failure' >Forrest> Make world is failing on /usr/src/games/morse (despite my telling >make.conf >Forrest> not to build games). Can someone please fix this. > >It did for me after a cvsup today - I have the source tree on another >machine cvsupped a few days back so I just went in there, got the files >and moved them to this other one where things were failing and it worked. > >It is amazing that this happens. I don't know what reasons to give - >probably whoever did the files 'had an oversight' - it is normal for human >beings. That I wholly accept. But it gets worse when after a rebuild you >cannot access an expensive piece of hardware, like happened to my T20 tape >after I moved from 3.5-S to 4.2-STABLE...using some very fine laid out >procedure. > > >-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. > >As the poet said, "Only God can make a tree" -- probably because it's so hard >to figure out how to get the bark on. -Woody Allen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 25 11:46:42 2001 Delivered-To: freebsd-stable@freebsd.org Received: from hedwig.internal.webtrends.com (unknown [206.58.83.57]) by hub.freebsd.org (Postfix) with ESMTP id DEB8337B6B8 for ; Thu, 25 Jan 2001 11:46:23 -0800 (PST) Received: by HEDWIG.internal.webtrends.com with Internet Mail Service (5.5.2653.19) id ; Thu, 25 Jan 2001 11:44:34 -0800 Message-ID: <0145F0769FECD411BF8400508BFDF6E4048E82@newman.internal.webtrends.com> From: Dustin Harris To: 'Forrest Aldrich' , freebsd-stable@freebsd.org Subject: RE: World build failure Date: Thu, 25 Jan 2001 11:46:22 -0800 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Try the -DNOGAMES option. --dustin -----Original Message----- From: Forrest Aldrich [mailto:forrie@forrie.com] Sent: Thursday, January 25, 2001 11:41 AM To: freebsd-stable@freebsd.org Subject: Re: World build failure It seems that it should be configured (in the build process) as a non-fatal error. My opinion: "games" is hardly an important part of the operating system. In fact, why cannot "games" be split into ports, so that they can be maintained differently and otherwise optionally installed. _F At 10:31 PM 1/25/2001 +0300, Odhiambo Washington wrote: >* Forrest Aldrich [20010125 22:03]: writing on the >subject 'World build failure' >Forrest> Make world is failing on /usr/src/games/morse (despite my telling >make.conf >Forrest> not to build games). Can someone please fix this. > >It did for me after a cvsup today - I have the source tree on another >machine cvsupped a few days back so I just went in there, got the files >and moved them to this other one where things were failing and it worked. > >It is amazing that this happens. I don't know what reasons to give - >probably whoever did the files 'had an oversight' - it is normal for human >beings. That I wholly accept. But it gets worse when after a rebuild you >cannot access an expensive piece of hardware, like happened to my T20 tape >after I moved from 3.5-S to 4.2-STABLE...using some very fine laid out >procedure. > > >-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. > >As the poet said, "Only God can make a tree" -- probably because it's so hard >to figure out how to get the bark on. -Woody Allen 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 25 11:53:25 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail2.wi.rr.com (fe2.rdc-kc.rr.com [24.94.163.49]) by hub.freebsd.org (Postfix) with ESMTP id 22BFA37B400 for ; Thu, 25 Jan 2001 11:53:02 -0800 (PST) Received: from woodstock.monkey.net ([24.167.246.123]) by mail2.wi.rr.com with Microsoft SMTPSVC(5.5.1877.357.35); Thu, 25 Jan 2001 13:50:35 -0600 Received: from pobox.com (localhost [127.0.0.1]) by woodstock.monkey.net (Postfix) with ESMTP id 67841201; Thu, 25 Jan 2001 13:52:56 -0600 (CST) X-Mailer: exmh version 2.3.1 01/23/2001 with version: MH 6.8.4 #1[UCI] To: Stephen Montgomery-Smith Cc: Luc Morin , freebsd-stable@FreeBSD.ORG Subject: Re: Network stops working In-reply-to: Your message of "Thu, 25 Jan 2001 12:02:28 CST." <3A706A34.E5F1C502@math.missouri.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 25 Jan 2001 13:52:56 -0600 From: Jon Hamilton Message-Id: <20010125195256.67841201@woodstock.monkey.net> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <3A706A34.E5F1C502@math.missouri.edu>, Stephen Montgomery-Smith wrot e: [ responding to a message from Luc Morin, who mentioned that in a recent-ish -STABLE, his network would stop working after a while ] } That's interesting - I have a similar problem that also } just started recently (coincided with changing my power } supply but I'm sure that it is unrelated). I find that } one of three things happens: } } 1. dhcp simply does not successfully negotiate } } 2. dhcp negotiates, gets an IP number and a router, but } then I get 100% packet loss. (Never tried calling them to } see if they got through to me.) } } 3. It actually works. } } Option 2 is what usually happens, but if I restarting } dhcp enough times, I get option 3. Since I keep the } connection up all the time, I only worry about the } problem sporadically. So I have never tried to investigate } its cause. (The ISP is att@home if that is useful. My } NIC is a RealTek 8139.) I've recently had problems too, that don't exactly match any of what I've seen in this thread, but which "feel" similar, and may be related. The background: I have a Compaq 1200 laptop, which travels between two or three netoworks. At home, it's behind a NAT/firewall connection, and at work it's on one of two LANs. The laptop uses DHCP to get its IP address in all situations. With -STABLE from 12/31/00, everything is fine. When I went to -STABLE from 1/24/01, I saw the following behavior: At home: gets IP address from DHCP server fine. Can connect to various other machines on the subnet ok. Can ssh to various machines both on the home LAN and outside the NATted subnet, but cannot connect from other machines to the laptop. Packets come in, but for some reason (according to both the ipfw logs and tcpdump) the kernel on the laptop doesn't seem to respond with outgoing packets at all. The firewall is not blocking the packets; they don't even get that far (tested by logging all traffic to/from all interfaces on the laptop). This bizarreness holds for TCP and ICMP traffic. The odd thing is, for "outgoing" connections (ssh from laptop to server) everything is fine; traffic moves just fine both directions. At work (two different subnets, but similar configuration between them): can get IP address via DHCP (it's not falling back to its last lease, but is actually getting a response from the DHCP server), but dhclient can't ping the gateway. Configuring everything by hand, I still can't get traffic to go out. I also get lots of complaints about corrupt NIC memory, with odd packet sizes ranging from 1 to about the MTU. I've tested this with two different Netgear FA-410tx cards (which I've been using for about 6 months, though these _are_ the cards that require fa_select.c to set them up). I did try without fa_select hoping that there were some changes to the driver that made it unnecessary, but that wasn't the case. This card uses the ed driver; unfortunately I don't have any PCMCIA cards I can use to test other drivers. I've backed down to a src tree from 12/31/00 and everything is once again working normally. I wasn't able to keep around the bogus tree, though I can check it out again and poke at it on an unused partition if it'll help. I did blow away /usr/src and /usr/obj when the problems first started and rebuilt from scratch, with the same results. Even GENERIC had the same symptoms. I did run mergemaster after updating. My NIC is configured for: ed0 at port 0x240-0x25f irq 3 slot 0 on pccard0 One last bit of info: the loopback driver does respond normally, for whatever that's worth. I can ping localhost and tcpdump -i lo0 will show both the incoming and outgoing packets. -- Jon Hamilton hamilton@pobox.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 25 12: 3:50 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 C975737B400 for ; Thu, 25 Jan 2001 12:03:28 -0800 (PST) Received: (from daemon@localhost) by point.osg.gov.bc.ca (8.8.7/8.8.8) id MAA09845; Thu, 25 Jan 2001 12:03:25 -0800 Received: from passer.osg.gov.bc.ca(142.32.110.29) via SMTP by point.osg.gov.bc.ca, id smtpda09839; Thu Jan 25 12:03:06 2001 Received: (from uucp@localhost) by passer.osg.gov.bc.ca (8.11.2/8.9.1) id f0PK2tf10396; Thu, 25 Jan 2001 12:02:55 -0800 (PST) Received: from cwsys9.cwsent.com(10.2.2.1), claiming to be "cwsys.cwsent.com" via SMTP by passer9.cwsent.com, id smtpda10390; Thu Jan 25 12:02:47 2001 Received: (from uucp@localhost) by cwsys.cwsent.com (8.11.2/8.9.1) id f0PK2l616273; Thu, 25 Jan 2001 12:02:47 -0800 (PST) Message-Id: <200101252002.f0PK2l616273@cwsys.cwsent.com> Received: from localhost.cwsent.com(127.0.0.1), claiming to be "cwsys" via SMTP by localhost.cwsent.com, id smtpdp16269; Thu Jan 25 12:02:05 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-Sender: schubert To: "Luc Morin" Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Network stops working In-reply-to: Your message of "Thu, 25 Jan 2001 10:33:31 EST." <002b01c086e4$2c843060$9d8fc918@videotron.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 25 Jan 2001 12:02:05 -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <002b01c086e4$2c843060$9d8fc918@videotron.ca>, "Luc Morin" writes: > Hi all, > > I'm sorry, but I seem to have misled some people by forgeting to > mention that I do indeed need to use DHCP to get my IP assigned. > > Now, that being said, I contacted a service representative from > my ISP this morning, and while I had 100% packet loss when trying > to ping a known good host, he said he could ping me with 0% > packet loss from his side. > > Also, I have noticed that although I can't reach out, I still see > connection attempts made to my box (I have log_in_vain="YES" > in rc.conf). > > I hope this can shed some new light. I've noticed similar problems at home, however they only occur after what my cable provider performs what they call "upgrades". In those cases, not only does my IP address change but so does the network and the netmask, making it impossible for my system using the "old" IP address, network address, and netmask to get a new lease from the DHCP server. If this is what is occurring to you, the only advice I have for you is to either reboot or kill and restart dhclient. 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 Thu Jan 25 12: 4:12 2001 Delivered-To: freebsd-stable@freebsd.org Received: from nova.fnal.gov (nova.fnal.gov [131.225.18.207]) by hub.freebsd.org (Postfix) with ESMTP id 0DE6937B6C0 for ; Thu, 25 Jan 2001 12:03:50 -0800 (PST) Received: from localhost (tez@localhost) by nova.fnal.gov (8.9.3+Sun/8.9.1) with ESMTP id OAA22177; Thu, 25 Jan 2001 14:03:45 -0600 (CST) X-Authentication-Warning: nova.fnal.gov: tez owned process doing -bs Date: Thu, 25 Jan 2001 14:03:45 -0600 (CST) From: Tim Zingelman X-Sender: To: Mike Tancsa , Mike Murphree Cc: Subject: Re: broken pipes on make world In-Reply-To: <5.0.1.4.0.20010125131220.02b2b320@marble.sentex.ca> 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, 25 Jan 2001, Mike Tancsa wrote: > Try a more recent build. i.e. one after the recent ssh commits > green 2001/01/11 20:26:22 PST > Modified files: (Branch: RELENG_4) > crypto/openssh LICENCE Makefile.inc RFC.nroff atomicio.c > auth-krb4.c auth-options.c auth-options.h Sorry about that... the world was 4.2-STABLE as of Jan 24 14:30, but I booted an old kernel from last month... Now the kernel too is 4.2-STABLE as of Jan 24 14:30... # uname -a FreeBSD xxx.fnal.gov 4.2-STABLE FreeBSD 4.2-STABLE #0: Thu Jan 25 12:08:18 CST 2001 tez@xxx.fnal.gov:/usr/obj/usr/src/sys/DELLQUAD i386 # ssh -V SSH Version OpenSSH_2.3.0, protocol versions 1.5/2.0. Compiled with SSL (0x0090600f). My /etc/make.conf & /etc/ssh/sshd_config files are attached. If you'd like me to change something and try again to re-create the problem, I'd be glad to help... But still this works... while logged in via ssh... (I tried this logging in from a solaris 2.7 box, a FreeBSD 3.2 box and also logging back into the FreeBSD 4.2-STABLE from itself after initially coming in from the 3.2 box.) # cd /usr/src/share/man # makewhatis -v /usr/share/man Open /usr/share/man/whatis.tmp open manpath directory ``/usr/share/man'' traverse /usr/share/man/man1 ... traverse /usr/share/man/man8 *+****+*****+***+********************************************+*************************+++++*****+++*********+*+++*+******+****************++++++++*************+**********************************+****************************************+****+*************+*******************+**************************++**********************+****+******************* traverse /usr/share/man/man9 *******************************************************************************************************************************************+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++*+++++++++++++++++ traverse /usr/share/man/mann sort -u > /usr/share/man/whatis.tmp Rename /usr/share/man/whatis.tmp to /usr/share/man/whatis 1987 entries in /usr/share/man/whatis # - Tim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 25 12: 4:30 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 A6AE737B6A4 for ; Thu, 25 Jan 2001 12:04:07 -0800 (PST) Received: from boomer.forrie.com (dhcp-north-71-168.navipath.net [64.20.71.168]) by forrie.net with id f0PK42156707 for ; Thu, 25 Jan 2001 15:04:02 -0500 (EST) Message-Id: <5.0.2.1.2.20010125150201.00a879d0@216.67.14.69> X-Sender: forrie@216.67.14.69 X-Mailer: QUALCOMM Windows Eudora Version 5.0.2 Date: Thu, 25 Jan 2001 15:03:06 -0500 To: freebsd-stable@freebsd.org From: Forrest Aldrich Subject: RE: World build failure In-Reply-To: <0145F0769FECD411BF8400508BFDF6E4048E82@newman.internal.web trends.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 Indeed we had NO_GAMES configured in make.conf, but somewhere it changed to NOGAMES (no underscore). The rest of the NO options are preceded by an underscore. A minor nitpick, but it could be made uniform. Trying this again, and reported the problem from the cvs commit to the committer :) _F At 11:46 AM 1/25/2001 -0800, Dustin Harris wrote: >Try the -DNOGAMES option. > >--dustin > >-----Original Message----- >From: Forrest Aldrich [mailto:forrie@forrie.com] >Sent: Thursday, January 25, 2001 11:41 AM >To: freebsd-stable@freebsd.org >Subject: Re: World build failure > > >It seems that it should be configured (in the build process) as a non-fatal >error. My opinion: "games" is hardly an important part of the operating >system. In fact, why cannot "games" be split into ports, so that they can >be maintained differently and otherwise optionally installed. > > >_F > > >At 10:31 PM 1/25/2001 +0300, Odhiambo Washington wrote: > >* Forrest Aldrich [20010125 22:03]: writing on the > >subject 'World build failure' > >Forrest> Make world is failing on /usr/src/games/morse (despite my telling > >make.conf > >Forrest> not to build games). Can someone please fix this. > > > >It did for me after a cvsup today - I have the source tree on another > >machine cvsupped a few days back so I just went in there, got the files > >and moved them to this other one where things were failing and it worked. > > > >It is amazing that this happens. I don't know what reasons to give - > >probably whoever did the files 'had an oversight' - it is normal for human > >beings. That I wholly accept. But it gets worse when after a rebuild you > >cannot access an expensive piece of hardware, like happened to my T20 tape > >after I moved from 3.5-S to 4.2-STABLE...using some very fine laid out > >procedure. > > > > > >-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. > > > >As the poet said, "Only God can make a tree" -- probably because it's so >hard > >to figure out how to get the bark on. -Woody Allen > > > > >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 25 12:37:54 2001 Delivered-To: freebsd-stable@freebsd.org Received: from oscar2.yerpso.net (209-164-208-189.telares.com [209.164.208.189]) by hub.freebsd.org (Postfix) with ESMTP id D1A7737B698 for ; Thu, 25 Jan 2001 12:37:32 -0800 (PST) Received: (from hmarq@localhost) by oscar2.yerpso.net (8.11.1/8.11.0) id f0PL7Nf00300 for freebsd-stable@freebsd.org; Thu, 25 Jan 2001 15:07:23 -0600 (CST) (envelope-from hmarq) Date: Thu, 25 Jan 2001 15:07:23 -0600 From: Hank Marquardt To: freebsd-stable@freebsd.org Subject: Dying disk ... Message-ID: <20010125150722.A288@oscar2.yerpso.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG If born out, this would be my first hardware failure under BSD so I'm just looking for another set of eyes to look at this dmesg: WARNING: / was not properly dismounted (da0:ahc0:0:0:0): SCB 0x31 - timed out while idle, SEQADDR == 0x3 STACK == 0x1, 0xe8, 0x143, 0x16b SXFRCTL0 == 0x80 SCB count = 50 QINFIFO entries: Waiting Queue entries: Disconnected Queue entries: 2:20 0:49 QOUTFIFO entries: Sequencer Free SCB List: 13 14 15 3 9 1 10 12 5 6 11 4 7 8 Pending list: 20 49 Kernel Free SCB list: 33 11 24 35 34 48 17 18 14 47 45 31 22 21 27 36 16 4 5 9 12 15 25 26 28 46 2 10 29 23 7 38 13 0 8 6 32 30 3 19 37 1 44 43 42 41 40 sg[0] - Addr 0x1134000 : Length 1024 (da0:ahc0:0:0:0): Queuing a BDR SCB (da0:ahc0:0:0:0): Bus Device Reset Message Sent (da0:ahc0:0:0:0): no longer in timeout, status = 34b ahc0: Bus Device Reset on A:0. 2 SCBs aborted The machine has locked solid under X a couple times and then refused to boot, not seeing the disk at all even under the SCSI ROM startup, so I popped the case thinking it might be a loose cable or something and sure enough it booted ... though you see it fschked the disk from the crash ... I left it be for a while, came back and saw the errors on the screen .. a quick look at syslog showed similar entries at each of the crashes. It seems to be running now (I'm writing this on it) ... but if the disk if flaked, I may as well go buy a new one now rather than wonder when it's going to die. Hank To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 25 12:42:14 2001 Delivered-To: freebsd-stable@freebsd.org Received: from zmamail04.zma.compaq.com (zmamail04.zma.compaq.com [161.114.64.104]) by hub.freebsd.org (Postfix) with ESMTP id 33CA837B698; Thu, 25 Jan 2001 12:41:56 -0800 (PST) Received: by zmamail04.zma.compaq.com (Postfix, from userid 12345) id 6A5984A0B; Thu, 25 Jan 2001 15:41:51 -0500 (EST) Received: from mailrelay01.cce.cpqcorp.net (mailrelay01.cce.cpqcorp.net [16.47.68.171]) by zmamail04.zma.compaq.com (Postfix) with ESMTP id 10F0247EE; Thu, 25 Jan 2001 15:40:41 -0500 (EST) Received: by mailrelay01.cce.cpqcorp.net (Postfix, from userid 12345) id 8B9292F4; Thu, 25 Jan 2001 14:42:36 -0600 (CST) Received: from anw.zk3.dec.com (wasted.zk3.dec.com [16.140.32.3]) by mailrelay01.cce.cpqcorp.net (Postfix) with ESMTP id 1B84035E; Thu, 25 Jan 2001 14:42:36 -0600 (CST) Received: by anw.zk3.dec.com (8.9.3/1.1.22.2/08Sep98-0251PM) id PAA0000803167; Thu, 25 Jan 2001 15:40:06 -0500 (EST) Date: Thu, 25 Jan 2001 15:40:06 -0500 (EST) Message-Id: <200101252040.PAA0000803167@anw.zk3.dec.com> From: Eric Werme USG To: Mike Smith , Linux NFS mailing list , FreeBSD Stable Cc: Guy Harris Subject: Re: [NFS] Incompatible: FreeBSD 4.2 client, Linux 2.2.18 nfsv3 server, read-only export Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > At least from looking at the Linux 2.2.18 code, if you get EROFS back > from the Linux server, the actual set of access bits you get back won't > have the right bits set; "nfsd_access()" just jumps to "out:" if it gets > a "read-only file system" error, and that doesn't set "*access" to the > result. Umm, either I'm reading your post wrong, or you've glitched on your recall of the protocol. If you get EROFS back from ACCESS, you won't get access bits: /* * The following union defines the results from invoking the * procedure ACCESS. */ struct ACCESS3resok { post_op_attr obj_attributes; uint32 access; /* bit mask - see above */ }; struct ACCESS3resfail { post_op_attr obj_attributes; }; union ACCESS3res switch (nfsstat3 status) { case NFS3_OK: ACCESS3resok resok; default: ACCESS3resfail resfail; }; If status == NFS3ERR_ROFS, then you get ACCESS3resfail which does not have the bit mask that is only returned as part of ACCESS3resok. Folks, I think we've beaten this dead molehill into a mountain. What's going to happen when someone finds a big problem? -Ric Werme -- Eric (Ric) Werme | werme@zk3.dec.com Compaq Computer Corp. >>>> http://people.ne.mediaone.net/werme/h8dcyf.html <<<< To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 25 12:45: 4 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 1F2E537B401 for ; Thu, 25 Jan 2001 12:44:45 -0800 (PST) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id VAA91091; Thu, 25 Jan 2001 21:44: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: Charlie Root Cc: stable@FreeBSD.ORG Subject: Re: ftp in free(): warning: junk pointer, too high to make sense. References: <200101241537.f0OFbHd07268@granny.bwa.penx.com> From: Dag-Erling Smorgrav Date: 25 Jan 2001 21:44:02 +0100 In-Reply-To: Charlie Root's message of "Wed, 24 Jan 2001 07:37:17 -0800 (PST)" Message-ID: Lines: 21 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 Charlie Root writes: > granny# mk > >> mysql-3.23.32.tar.gz doesn't seem to exist in /usr/ports/distfiles/. > >> Attempting to fetch from http://www.kernelnotes.de/MySQL/Downloads/MySQL-3.23/. > Requesting http://www.kernelnotes.de/MySQL/Downloads/MySQL-3.23/mysql-3.23.32.tar.gz > ftp: Error retrieving file: 404 Not Found > > ftp in free(): warning: junk pointer, too high to make sense. > Segmentation fault - core dumped > >> Attempting to fetch from http://www.mysql.net/Downloads/MySQL-3.23/. > Requesting http://www.mysql.net/Downloads/MySQL-3.23/mysql-3.23.32.tar.gz Why are you using ftp(1) to fetch ports instead of fetch(1) which is the default? Don't even think about it - ftp(1)'s HTTP support is symbolic at best. It pretends to be an HTTP/1.0 client, but in practice is little more than an HTTP/0.9 client using HTTP/1.0 request syntax. 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 Thu Jan 25 12:47:28 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 AB67137B404 for ; Thu, 25 Jan 2001 12:47:08 -0800 (PST) Received: (from kris@localhost) by citusc17.usc.edu (8.11.1/8.11.1) id f0PKoTG61822; Thu, 25 Jan 2001 12:50:29 -0800 (PST) (envelope-from kris) Date: Thu, 25 Jan 2001 12:50:28 -0800 From: Kris Kennaway To: Forrest Aldrich Cc: freebsd-stable@FreeBSD.ORG Subject: Re: World build failure Message-ID: <20010125125028.B59267@citusc17.usc.edu> References: <0145F0769FECD411BF8400508BFDF6E4048E82@newman.internal.web trends.com> <5.0.2.1.2.20010125150201.00a879d0@216.67.14.69> 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: <5.0.2.1.2.20010125150201.00a879d0@216.67.14.69>; from forrie@forrie.com on Thu, Jan 25, 2001 at 03:03:06PM -0500 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 25, 2001 at 03:03:06PM -0500, Forrest Aldrich wrote: > Indeed we had NO_GAMES configured in make.conf, but somewhere it changed = to=20 > NOGAMES (no underscore). The rest of the NO options are preceded by an= =20 > underscore. A minor nitpick, but it could be made uniform. It's always been NOGAMES. The newer options are NO_*, and I'd like to make them uniform on the latter. 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 iD8DBQE6cJGUWry0BWjoQKURAoFHAKCvAlymKljkLY4UWyvotKrYQtcKSACcDpGA vDE35gWJn6tGdHPLMwOrCEY= =gyNd -----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 25 13:15:19 2001 Delivered-To: freebsd-stable@freebsd.org Received: from granny.bwa.penx.com (granny.bwa.penx.com [207.149.143.101]) by hub.freebsd.org (Postfix) with ESMTP id 2B71A37B404 for ; Thu, 25 Jan 2001 13:15:01 -0800 (PST) Received: from faq (faq.bwa.penx.com [172.19.8.128]) by granny.bwa.penx.com (8.11.2/8.11.2) with SMTP id f0PLEIL12158; Thu, 25 Jan 2001 13:14:18 -0800 (PST) From: "Dennis Glatting" To: , "Charlie Root" Cc: Subject: RE: ftp in free(): warning: junk pointer, too high to make sense. Date: Thu, 25 Jan 2001 13:14:18 -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) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 In-Reply-To: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Charlie Root writes: > > granny# mk > > >> mysql-3.23.32.tar.gz doesn't seem to exist in /usr/ports/distfiles/. > > >> Attempting to fetch from > http://www.kernelnotes.de/MySQL/Downloads/MySQL-3.23/. > > Requesting > http://www.kernelnotes.de/MySQL/Downloads/MySQL-3.23/mysql-3.23.32.tar.gz > > ftp: Error retrieving file: 404 Not Found > > > > ftp in free(): warning: junk pointer, too high to make sense. > > Segmentation fault - core dumped > > >> Attempting to fetch from http://www.mysql.net/Downloads/MySQL-3.23/. > > Requesting > http://www.mysql.net/Downloads/MySQL-3.23/mysql-3.23.32.tar.gz > > Why are you using ftp(1) to fetch ports instead of fetch(1) which is > the default? Don't even think about it - ftp(1)'s HTTP support is > symbolic at best. It pretends to be an HTTP/1.0 client, but in > practice is little more than an HTTP/0.9 client using HTTP/1.0 request > syntax. > Ah. I am using FTP because FETCH often has trouble going through proxies. Here, FTP is allowed out but web traffic must go through a proxy for audit. FETCH tries to FTP through the proxy because the HTTP_PROXY variable is set. Admittedly, I haven't tried FETCH in over a month. The proxy is Squid 2.3. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 25 13:22:10 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 EF07337B402 for ; Thu, 25 Jan 2001 13:21:53 -0800 (PST) Received: (qmail 11121 invoked by uid 1078); 25 Jan 2001 21:21:54 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 25 Jan 2001 21:21:54 -0000 Date: Thu, 25 Jan 2001 13:21:54 -0800 (PST) From: Gordon Tetlow X-X-Sender: To: Jason Watkins Cc: Freebsd-Stable Subject: Re: ftp logins 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 Did you check to see if ftp was listed in /etc/pam.conf? My ftpd from -stable is linked against it. Also, when you upgraded the box, did you run mergemaster? I know people were having problems with pam.conf being upgraded so you might want to take a look at that thread. -gordon On Mon, 22 Jan 2001, Jason Watkins wrote: > Since rebuilding from 4.1 release to -stable, I've had a curious problem > with ftp logins. Users which should be allowed to log into ftp will get a > denial message immedately after entrying the login name, the password prompt > is never given. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 25 13:59:20 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 8BCEE37B6AE for ; Thu, 25 Jan 2001 13:59:01 -0800 (PST) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id WAA91360; Thu, 25 Jan 2001 22:58:57 +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: "Dennis Glatting" Cc: "Charlie Root" , Subject: Re: ftp in free(): warning: junk pointer, too high to make sense. References: From: Dag-Erling Smorgrav Date: 25 Jan 2001 22:58:57 +0100 In-Reply-To: "Dennis Glatting"'s message of "Thu, 25 Jan 2001 13:14:18 -0800" 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 "Dennis Glatting" writes: > I am using FTP because FETCH often has trouble going through proxies. Here, > FTP is allowed out but web traffic must go through a proxy for audit. FETCH > tries to FTP through the proxy because the HTTP_PROXY variable is set. Please read the "ENVIRONMENT VARIABLES" section of the fetch(3) man page (that's fetch(3), not fetch(1)). If you still have problems, please submit a PR. > Admittedly, I haven't tried FETCH in over a month. It hasn't changed much in a month, except for a slight fix to the login procedure for anonymous FTP. > The proxy is Squid 2.3. fetch(1) works just fine with Squid and most other commonplace HTTP and FTP proxies. 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 Thu Jan 25 15:28:58 2001 Delivered-To: freebsd-stable@freebsd.org Received: from front001.cluster1.charter.net (outbound.charter.net [24.216.159.200]) by hub.freebsd.org (Postfix) with ESMTP id 688C537B6A3 for ; Thu, 25 Jan 2001 15:28:40 -0800 (PST) Received: from [24.217.145.132] (HELO dave) by front001.cluster1.charter.net (CommuniGate Pro SMTP 3.4b8) with SMTP id 16676228; Thu, 25 Jan 2001 18:28:39 -0500 From: Dave Uhring To: Stephen Montgomery-Smith , Luc Morin Subject: Re: Network stops working Date: Thu, 25 Jan 2001 17:28:32 -0600 X-Mailer: KMail [version 1.1.99] Content-Type: text/plain; charset="us-ascii" Cc: freebsd-stable@FreeBSD.ORG References: <001001c08628$8db16180$9d8fc918@videotron.ca> <005a01c086f7$337f51c0$9d8fc918@videotron.ca> <3A706A34.E5F1C502@math.missouri.edu> In-Reply-To: <3A706A34.E5F1C502@math.missouri.edu> MIME-Version: 1.0 Message-Id: <01012517283203.22152@dave> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Power cycle your cable modem. Pull the power plug and reinstall it 5 minutes later. Then kill the dhclient process and restart it after the cable modem status light remains steady. On occasion I have had the same problem with my service - using 3Com Cable Modem CMX. Dave On Thursday 25 January 2001 12:02, Stephen Montgomery-Smith wrote: > That's interesting - I have a similar problem that also > just started recently (coincided with changing my power > supply but I'm sure that it is unrelated). I find that > one of three things happens: > > 1. dhcp simply does not successfully negotiate > > 2. dhcp negotiates, gets an IP number and a router, but > then I get 100% packet loss. (Never tried calling them to > see if they got through to me.) > > 3. It actually works. > > Option 2 is what usually happens, but if I restarting > dhcp enough times, I get option 3. Since I keep the > connection up all the time, I only worry about the > problem sporadically. So I have never tried to investigate > its cause. (The ISP is att@home if that is useful. My > NIC is a RealTek 8139.) > > Luc Morin wrote: > > Hi, > > > > I've been asked to clarify the topology of my system. > > > > Very simple setup. All I have is my home box connected to my ISP > > thru cable-modem. My NIC is a PCI NE2000 clone using the ed driver. > > > > My ISP uses DHCP to assign my IP, so I run dhclient at boot time > > from my rc.conf file. This setup has been running fine for me for > > over a year now. Even after my last cvsup/buildworld everything was > > still perfectly working. > > > > A few days ago, I started getting a situation where after a few > > minutes of operation (after boot), I can't reach anything, not even > > my default gateway (assigned by my ISP as part of DHCP). > > > > I've talked to my ISP's tech support rep, and he told me he could > > ping my box just fine ( 0% packet loss ), while I couldn't ping > > anything ( 100% packet loss ). I also noticed that even though > > I can't reach the outside world, I still see some syslogd messages > > about failed attempt to connect to my box (I have log_in_vain="YES" > > in rc.conf). > > > > Please see attached file for specifics of my system (kernel config > > file, dmesg output, uname -a, ps -ax etc...) > > > > I hope this clarifies the situation :-) > > > > Many thanks, > > > > Luc Morin > > > > > > ------------------------------------------------------------------- > >------------- Name: info.txt > > info.txt Type: Plain Text (text/plain) > > Encoding: quoted-printable To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 25 15:31: 0 2001 Delivered-To: freebsd-stable@freebsd.org Received: from VL-MS-MR002.sc1.videotron.ca (relais.videotron.ca [24.201.245.36]) by hub.freebsd.org (Postfix) with ESMTP id D195837B6A4 for ; Thu, 25 Jan 2001 15:30:40 -0800 (PST) Received: from southpark ([24.201.143.157]) by VL-MS-MR002.sc1.videotron.ca (Netscape Messaging Server 4.15) with SMTP id G7QRU903.FGD for ; Thu, 25 Jan 2001 18:27:45 -0500 Message-ID: <000701c08726$7c6d0380$9d8fc918@videotron.ca> From: "Luc Morin" To: References: <200101252002.f0PK2l616273@cwsys.cwsent.com> Subject: Re: Network stops working Date: Thu, 25 Jan 2001 18:28:12 -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.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, here's something interesting. I noticed that under Win98, the DHCP server will assign me 24.201.143.157, and under FreeBSD it will assign 24.200.211.9 How come ? Could this be a lead as to what's going on ? The one thing that bugs me most with this problem is that I have no problem under Windows. I'd rather it be the other way around :-) Regards, Luc Morin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 25 15:41:49 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 5D29437B400 for ; Thu, 25 Jan 2001 15:41:32 -0800 (PST) Received: from dwcjr (DWCJR.inethouston.net [216.118.21.147]) by leviathan.inethouston.net (Postfix) with ESMTP id 598B4177E3F; Thu, 25 Jan 2001 17:41:29 -0600 (CST) Message-ID: <00e701c08728$5544fcc0$931576d8@inethouston.net> From: "David W. Chapman Jr." To: "Luc Morin" , References: <200101252002.f0PK2l616273@cwsys.cwsent.com> <000701c08726$7c6d0380$9d8fc918@videotron.ca> Subject: Re: Network stops working Date: Thu, 25 Jan 2001 17:41:26 -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 Are both os's on the same machine? A friend of mine had this problem, had the cable modem plugged into the 98 workstation. then when we connected it to the freebsd workstation it wouldn't get a lease. Apparently the dhcp server keeps a record of the mac address. ----- Original Message ----- From: "Luc Morin" To: Sent: Thursday, January 25, 2001 5:28 PM Subject: Re: Network stops working > Hi all, > > here's something interesting. > > I noticed that under Win98, the DHCP server will assign me > 24.201.143.157, and under FreeBSD it will assign 24.200.211.9 > > How come ? Could this be a lead as to what's going on ? > > The one thing that bugs me most with this problem is that > I have no problem under Windows. I'd rather it be the other > way around :-) > > Regards, > > Luc Morin > > > > > 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 25 15:48:31 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id 4AD5937B401 for ; Thu, 25 Jan 2001 15:48:14 -0800 (PST) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.1/8.11.1) with ESMTP id f0Q03o100584; Thu, 25 Jan 2001 16:03:50 -0800 (PST) (envelope-from msmith@mass.dis.org) Message-Id: <200101260003.f0Q03o100584@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Eric Werme USG Cc: Linux NFS mailing list , FreeBSD Stable , Guy Harris Subject: Re: [NFS] Incompatible: FreeBSD 4.2 client, Linux 2.2.18 nfsv3 server, read-only export In-reply-to: Your message of "Thu, 25 Jan 2001 15:40:06 EST." <200101252040.PAA0000803167@anw.zk3.dec.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 25 Jan 2001 16:03:50 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Folks, I think we've beaten this dead molehill into a mountain. > What's going to happen when someone finds a big problem? It'll just get quietly fixed. Welcome to the "bikeshed phenomenon". 8) -- ... 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 25 16:24:36 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mrynet.com (mrynet.com [63.228.57.57]) by hub.freebsd.org (Postfix) with ESMTP id BC4B737B6AB for ; Thu, 25 Jan 2001 16:24:10 -0800 (PST) Received: (from freebsd@localhost) by mrynet.com (8.11.1/8.11.1) id f0Q0O8l01300 for freebsd-stable@freebsd.org; Thu, 25 Jan 2001 18:24:08 -0600 (CST) (envelope-from freebsd) Message-Id: <200101260024.f0Q0O8l01300@mrynet.com> From: freebsd@mrynet.com (FreeBSD list) Date: Thu, 25 Jan 2001 18:24:08 -0600 X-Mailer: Mail User's Shell (7.2.6 beta(3) 11/17/96) To: freebsd-stable@freebsd.org Subject: NFS hangs root on today's CVSUP -- Unaddressed issue Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Previously, on Mon, 22 Jan 2001 18:42:23, I wrote: > After CVSUP'ing today and building world and installing a new kernel, > ALL NFS mounts hang, and root (/) suddenly becomes unreadable with > "/bin/ls -F"--it hangs as well. Also, df(1) and mount(8) hang > forever. I've re-CVSUP'ed in case I caught something mid-stream, > but the problem still prevails. > > Would others please check this? This NFS breakage renders a > client of NFS unable to operate. This problem still exists and is a critical issue -- No NFS mounts of filesystems from another machine can be made: # mount some.foreign.host:/path /path <<>> >From another shell: # df <<>> >From yet another shell: # /bin/ls -F / <<>> Same for "# mount". The NFS host is running FreeBSD 5.0, which hasn't changed in a while. It all started when a system was built from a cvsup on Jan 22. Since then, I've cleared out /usr/src and /usr/obj and re-cvsup'd. The problem persists. I've also tried "*default date=2000.01.01.00.00.01" in the cvsup file to go back to a (presumably working) source date, but cvsup munged the source tree beyond use. Can't anyone suggest a recourse here? Thanks, -scott To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 25 16:33:41 2001 Delivered-To: freebsd-stable@freebsd.org Received: from emma1.emma.line.org (p3EE3C868.dip.t-dialin.net [62.227.200.104]) by hub.freebsd.org (Postfix) with ESMTP id 8689137B401; Thu, 25 Jan 2001 16:33:21 -0800 (PST) Received: by emma1.emma.line.org (Postfix, from userid 500) id 26A20A2068; Fri, 26 Jan 2001 01:16:44 +0100 (CET) To: Eric Werme USG Cc: Mike Smith , Linux NFS mailing list , FreeBSD Stable , Guy Harris Subject: Resolved: Incompatible: FreeBSD 4.2 client, Linux 2.2.18 nfsv3 server, read-only export References: <200101252040.PAA0000803167@anw.zk3.dec.com> In-Reply-To: <200101252040.PAA0000803167@anw.zk3.dec.com> From: Matthias Andree Date: 26 Jan 2001 01:16:44 +0100 Message-ID: Lines: 76 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 Eric Werme USG writes: > Umm, either I'm reading your post wrong, or you've glitched on your > recall of the protocol. > > If status == NFS3ERR_ROFS, then you get ACCESS3resfail which does not > have the bit mask that is only returned as part of ACCESS3resok. Evident when using a good packet dissector like ethereal. :*) > Folks, I think we've beaten this dead molehill into a mountain. > What's going to happen when someone finds a big problem? Message flood without hope to escape the Big Chaos[tm]. Seriously, Neil Brown has posted a really short (3 line) patch to the linux-kernel mailing list which does the expected job: fix the server problem. I'm using it and my FreeBSD 4.2 client and Linux 2.2.18 server happily chat to each other "in NFSv3". As a reference and for the records and archives, I'm attaching the patch (against vanilla 2.2.18 Linux) that Neil Brown sent to the linux-kernel mailing list. Thanks for all helpful mails and tracking and tracing. Thanks to Neil for fixing things. Again, Neil's patch is against a stock kernel.org Linux 2.2.18 tree. To apply in /usr/src/linux with patch -p0. Matthias Andree Neil's patch to follow, headers mutilated and quotes and attribution of the body stripped (already there): From: Neil Brown To: Matthias Andree Date: Wed, 24 Jan 2001 17:06:55 +1100 (EST) Message-ID: <14958.28927.756597.940445@notabene.cse.unsw.edu.au> Cc: Linux NFS mailing list , Linux-Kernel mailing list , Alan Cox Subject: Re: [NFS] Linux 2.2.18 nfs v3 server bug (was: Incompatible: FreeBSD 4.2 client, Linux 2.2.18 nfsv3 server, read-only export) References: <20010123015612.H345@quadrajet.flashcom.com> <20010123162930.B5443@emma1.emma.line.org> <20010123105350.B344@quadrajet.flashcom.com> <20010124041437.A28212@emma1.emma.line.org> [...] I stuffed up when I tried to interpret the error, but after much sensible correction, here is a patch. Please try it, and suggest any other errs that should be tested for (or maybe we should invert the sense of the test, and test for error codes that ACCESS is allowed to return. 2.4.0 seems to get it right. NeilBrown --- ./fs/nfsd/vfs.c 2001/01/10 05:03:28 1.11 +++ ./fs/nfsd/vfs.c 2001/01/24 06:02:01 @@ -448,7 +448,9 @@ error = nfsd_permission(export, dentry, (map->how | NO_OWNER_OVERRIDE)); if (error == 0) result |= map->access; - else if ((error == nfserr_perm) || (error == nfserr_acces)) { + else if ((error == nfserr_perm) || + (error == nfserr_acces) || + (error == nfserr_rofs)) { /* * This access type is denyed; but the * access query itself succeeds. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 25 16:46:56 2001 Delivered-To: freebsd-stable@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 7AB3837B402 for ; Thu, 25 Jan 2001 16:46:38 -0800 (PST) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id RAA37062; Thu, 25 Jan 2001 17:46:24 -0700 (MST) (envelope-from ken) Date: Thu, 25 Jan 2001 17:46:24 -0700 From: "Kenneth D. Merry" To: Hank Marquardt Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Dying disk ... Message-ID: <20010125174624.A37036@panzer.kdm.org> References: <20010125150722.A288@oscar2.yerpso.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20010125150722.A288@oscar2.yerpso.net>; from hmarq@oscar2.yerpso.net on Thu, Jan 25, 2001 at 03:07:23PM -0600 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ Try to hit return every 70 characters or so. If you're using vi, type ESC and then :se wm=10 ] On Thu, Jan 25, 2001 at 15:07:23 -0600, Hank Marquardt wrote: > If born out, this would be my first hardware failure under BSD so I'm just looking for another set of eyes to look at this dmesg: > > > WARNING: / was not properly dismounted > (da0:ahc0:0:0:0): SCB 0x31 - timed out while idle, SEQADDR == 0x3 Timed out while idle, for a disk, generally means that we sent a command to the disk and it still hadn't returned it after 60 seconds. So we assume that the disk is out to lunch and hasn't come back, and therefore we reset it to wake it up. > STACK == 0x1, 0xe8, 0x143, 0x16b > SXFRCTL0 == 0x80 > SCB count = 50 > QINFIFO entries: > Waiting Queue entries: > Disconnected Queue entries: 2:20 0:49 > QOUTFIFO entries: > Sequencer Free SCB List: 13 14 15 3 9 1 10 12 5 6 11 4 7 8 > Pending list: 20 49 > Kernel Free SCB list: 33 11 24 35 34 48 17 18 14 47 45 31 22 21 27 36 16 4 5 9 12 15 25 26 28 46 2 10 29 23 7 38 13 0 8 6 32 30 3 19 37 1 44 43 42 41 40 > sg[0] - Addr 0x1134000 : Length 1024 > (da0:ahc0:0:0:0): Queuing a BDR SCB > (da0:ahc0:0:0:0): Bus Device Reset Message Sent > (da0:ahc0:0:0:0): no longer in timeout, status = 34b > ahc0: Bus Device Reset on A:0. 2 SCBs aborted > > The machine has locked solid under X a couple times and then refused to boot, not seeing the disk at all even under the SCSI ROM startup, so I popped the case thinking it might be a loose cable or something and sure enough it booted ... though you see it fschked the disk from the crash ... I left it be for a while, came back and saw the errors on the screen .. a quick look at syslog showed similar entries at each of the crashes. > > It seems to be running now (I'm writing this on it) ... but if the disk if flaked, I may as well go buy a new one now rather than wonder when it's going to die. You should make sure your disk is properly cooled (is it hot to the touch?). You should also check your cabling and termination. If your disk wasn't showing up during your SCSI controller's BIOS probe, that could indicate a cabling or termination problem. It could also mean the disk is on its way out. What sort of disk is it? Some disks are known to have firmware issues that cause them to go "out to lunch" and not come back. Ken -- Kenneth Merry ken@kdm.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 25 17:34: 4 2001 Delivered-To: freebsd-stable@freebsd.org Received: from f05n15.cac.psu.edu (f05s15.cac.psu.edu [128.118.141.58]) by hub.freebsd.org (Postfix) with ESMTP id F0B4B37B401 for ; Thu, 25 Jan 2001 17:33:42 -0800 (PST) Received: from maverick.psu.edu (adsl-209-158-236-40.cptl.adsl.bellatlantic.net [209.158.236.40]) by f05n15.cac.psu.edu (8.9.3/8.9.3) with ESMTP id UAA45868 for ; Thu, 25 Jan 2001 20:33:41 -0500 Message-Id: <5.0.2.1.2.20010125203128.00a72b80@email.psu.edu> X-Sender: hpk104@email.psu.edu X-Mailer: QUALCOMM Windows Eudora Version 5.0.2 Date: Thu, 25 Jan 2001 20:33:40 -0500 To: stable@freebsd.org From: Harris Kauffman Subject: installworld failing at groff 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 am having a problem installing todays stable, buildworld/buildkernel/installkernel all completed without problem, but installworld is failing at groff with multiple: ls: not found ls: not found tr: not found in every directory starting in gnu/usr.bin/groff/afmtodit, and finally ending with: ===> gnu/usr.bin/groff/devascii Making R expr: not found *** Error code 127 Any help would, as always, be greatly appreciated. TIA, Harris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 25 18: 6:12 2001 Delivered-To: freebsd-stable@freebsd.org Received: from femail1.rdc1.on.home.com (femail1.rdc1.on.home.com [24.2.9.88]) by hub.freebsd.org (Postfix) with ESMTP id 6652C37B400 for ; Thu, 25 Jan 2001 18:05:52 -0800 (PST) Received: from tristan.net ([24.156.220.43]) by femail1.rdc1.on.home.com (InterMail vM.4.01.03.00 201-229-121) with ESMTP id <20010126020453.CRTC764.femail1.rdc1.on.home.com@tristan.net>; Thu, 25 Jan 2001 18:04:53 -0800 Content-Length: 2532 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: <00e701c08728$5544fcc0$931576d8@inethouston.net> Date: Thu, 25 Jan 2001 21:04:27 -0500 (EST) From: Colin To: "David W. Chapman Jr." Subject: Re: Network stops working Cc: freebsd-stable@FreeBSD.ORG, Luc Morin Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The DHCP server has to keep a record of the lease or there will be all kinds of interesting problems. The server will see the mac address of the client in the DHCP-DISCOVER, and if it has a record of a valid, non-expired lease, it will send that information to the requesting client. I haven't done a lot of (ok, any :)) work with the BSD DHCP client, but there should be a command parameter or signal or something that says "please tell the server to expire my existing address" (on your Win box, AFAIR it's ipconfig -release) and from there you should be able to get a valid address. Your only other options are leaving the BSD box off the network for the duration of it's lease (could be a week or more) or calling the ISP and saying "Please kill the entry for my machine, IP 24.200.211.9, from the DHCP servers .cur file" which they will probably be more than a little hesitant to do. I'm guessing the ISP has recently renumbered the network (I know my cable-modem based provider has been doing that a lot recently) and the Win box was not connected before it's lease expired. This all assumes that the Win box and BSD box are in fact seperate, not a dual boot system. If it is a dual boot system, the ISP's DHCP server has issues, as it should not issue 2 seperate addresses for the same mac address. Cheers, Colin Wass On 25-Jan-01 David W. Chapman Jr. wrote: > Are both os's on the same machine? A friend of mine had this problem, had > the cable modem plugged into the 98 workstation. then when we connected it > to the freebsd workstation it wouldn't get a lease. Apparently the dhcp > server keeps a record of the mac address. > > ----- Original Message ----- > From: "Luc Morin" > To: > Sent: Thursday, January 25, 2001 5:28 PM > Subject: Re: Network stops working > > >> Hi all, >> >> here's something interesting. >> >> I noticed that under Win98, the DHCP server will assign me >> 24.201.143.157, and under FreeBSD it will assign 24.200.211.9 >> >> How come ? Could this be a lead as to what's going on ? >> >> The one thing that bugs me most with this problem is that >> I have no problem under Windows. I'd rather it be the other >> way around :-) >> >> Regards, >> >> Luc Morin >> >> >> >> >> 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 25 18:22:39 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 A7E2E37B404 for ; Thu, 25 Jan 2001 18:22:19 -0800 (PST) Received: from dogma.freebsd-uk.eu.org ([130.88.200.97] ident=root) by probity.mcc.ac.uk with esmtp (Exim 2.05 #4) id 14LyWp-0001om-00 for stable@freebsd.org; Fri, 26 Jan 2001 02:22:19 +0000 Received: (from rasputin@localhost) by dogma.freebsd-uk.eu.org (8.11.1/8.11.1) id f0Q2MId02177 for stable@freebsd.org; Fri, 26 Jan 2001 02:22:18 GMT (envelope-from rasputin) Date: Fri, 26 Jan 2001 02:22:18 +0000 From: Rasputin To: stable@freebsd.org Subject: Re: World build failure Message-ID: <20010126022218.A2153@dogma.freebsd-uk.eu.org> References: <0145F0769FECD411BF8400508BFDF6E4048E82@newman.internal.web <5.0.2.1.2.20010125150201.00a879d0@216.67.14.69> <20010125125028.B59267@citusc17.usc.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20010125125028.B59267@citusc17.usc.edu>; from kris@freebsd.org on Thu, Jan 25, 2001 at 12:50:28PM -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Kris Kennaway [010125 20:48]: > On Thu, Jan 25, 2001 at 03:03:06PM -0500, Forrest Aldrich wrote: > > Indeed we had NO_GAMES configured in make.conf, but somewhere it changed to > > NOGAMES (no underscore). The rest of the NO options are preceded by an > > underscore. A minor nitpick, but it could be made uniform. > > It's always been NOGAMES. The newer options are NO_*, and I'd like to > make them uniform on the latter. While we're on the subject, is there a good reason why the uucp user/group is required to installworld when NOUUCP is set in /etc/make.conf? I couldn't find much left on the system used/owned by that account, yet the build fails after a few seconds without it... -- 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 Thu Jan 25 18:30:29 2001 Delivered-To: freebsd-stable@freebsd.org Received: from front003.cluster1.charter.net (outbound.charter.net [24.216.159.200]) by hub.freebsd.org (Postfix) with ESMTP id 023A337B400 for ; Thu, 25 Jan 2001 18:30:08 -0800 (PST) Received: from [24.217.145.132] (HELO dave) by front003.cluster1.charter.net (CommuniGate Pro SMTP 3.4b8) with SMTP id 11155034; Thu, 25 Jan 2001 21:28:38 -0500 From: Dave Uhring To: Colin , "David W. Chapman Jr." Subject: Re: Network stops working Date: Thu, 25 Jan 2001 20:30:06 -0600 X-Mailer: KMail [version 1.1.99] Content-Type: text/plain; charset="us-ascii" Cc: freebsd-stable@FreeBSD.ORG, Luc Morin References: In-Reply-To: MIME-Version: 1.0 Message-Id: <01012520300600.04280@dave> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG If his cable modem is similar to mine, it recognizes only one NIC and must be power cycled in order to attach a different NIC. After killing dhclient and restarting it, he will also receive a different IP address from his ISP. The important thing is to kill the power to the cable modem for at least 1 minute then power it back up again. Dave On Thursday 25 January 2001 20:04, Colin wrote: > The DHCP server has to keep a record of the lease or there will be > all kinds of interesting problems. The server will see the mac > address of the client in the DHCP-DISCOVER, and if it has a record of > a valid, non-expired lease, it will send that information to the > requesting client. I haven't done a lot of (ok, any :)) work with the > BSD DHCP client, but there should be a command parameter or signal or > something that says "please tell the server to expire my existing > address" (on your Win box, AFAIR it's ipconfig -release) and from > there you should be able to get a valid address. Your only other > options are leaving the BSD box off the network for the duration of > it's lease (could be a week or more) or calling the ISP and saying > "Please kill the entry for my machine, IP 24.200.211.9, from the DHCP > servers ..cur file" which they will probably be more than a little > hesitant to do. I'm guessing the ISP has recently renumbered the > network (I know my cable-modem based provider has been doing that a > lot recently) and the Win box was not connected before it's lease > expired. > This all assumes that the Win box and BSD box are in fact > seperate, not a dual boot system. If it is a dual boot system, the > ISP's DHCP server has issues, as it should not issue 2 seperate > addresses for the same mac address. > > Cheers, > Colin Wass > > On 25-Jan-01 David W. Chapman Jr. wrote: > > Are both os's on the same machine? A friend of mine had this > > problem, had the cable modem plugged into the 98 workstation. then > > when we connected it to the freebsd workstation it wouldn't get a > > lease. Apparently the dhcp server keeps a record of the mac > > address. > > > > ----- Original Message ----- > > From: "Luc Morin" > > To: > > Sent: Thursday, January 25, 2001 5:28 PM > > Subject: Re: Network stops working > > > >> Hi all, > >> > >> here's something interesting. > >> > >> I noticed that under Win98, the DHCP server will assign me > >> 24.201.143.157, and under FreeBSD it will assign 24.200.211.9 > >> > >> How come ? Could this be a lead as to what's going on ? > >> > >> The one thing that bugs me most with this problem is that > >> I have no problem under Windows. I'd rather it be the other > >> way around :-) > >> > >> Regards, > >> > >> Luc Morin > >> > >> > >> > >> > >> 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 25 18:52:13 2001 Delivered-To: freebsd-stable@freebsd.org Received: from hermes.yerpso.net (209-164-208-189.telares.com [209.164.208.189]) by hub.freebsd.org (Postfix) with ESMTP id B20DC37B402 for ; Thu, 25 Jan 2001 18:51:51 -0800 (PST) Received: (from hmarq@localhost) by hermes.yerpso.net (8.11.1/8.9.3) id f0Q2dlP53582; Thu, 25 Jan 2001 20:39:47 -0600 (CST) (envelope-from hmarq) Date: Thu, 25 Jan 2001 20:39:47 -0600 From: Hank Marquardt To: "Kenneth D. Merry" Cc: Hank Marquardt , freebsd-stable@FreeBSD.ORG Subject: Re: Dying disk ... Message-ID: <20010125203946.A53543@hermes.yerpso.net> References: <20010125150722.A288@oscar2.yerpso.net> <20010125174624.A37036@panzer.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010125174624.A37036@panzer.kdm.org>; from ken@kdm.org on Thu, Jan 25, 2001 at 05:46:24PM -0700 X-Do-sys: Systems Management and Security - Linux / FreeBSD X-Do-dev: Custom development in PHP - MySQL - PostgreSQL X-web: http://web.yerpso.net X-phone: 708-524-1365 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks, heat is an interesting thought ... it's a dual P133 machine in fairly close quarters (inside the case); though it was running solid for close to 30 days before the first lockup (4.2 Stable update/boot around 12/15) and another couple months before that with no issues -- further, the dmesg I originally sent was from less than 15 minutes running after having been powered off for over 24 hours -- I don't think I'd get a heat problem that quick unless something was seriously screwed up -- of which there was no evidence when I opened the case. The drive is a Segate ST19171W attached to a 2940 card -- CD also SCSI has functioned and been recognized throughout all the episodes. Hank On Thu, Jan 25, 2001 at 05:46:24PM -0700, Kenneth D. Merry wrote: > [ Try to hit return every 70 characters or so. If you're using vi, > type ESC and then :se wm=10 ] > > On Thu, Jan 25, 2001 at 15:07:23 -0600, Hank Marquardt wrote: > > If born out, this would be my first hardware failure under BSD so I'm just looking for another set of eyes to look at this dmesg: > > > > > > WARNING: / was not properly dismounted > > (da0:ahc0:0:0:0): SCB 0x31 - timed out while idle, SEQADDR == 0x3 > > Timed out while idle, for a disk, generally means that we sent a > command to the disk and it still hadn't returned it after 60 seconds. > So we assume that the disk is out to lunch and hasn't come back, and > therefore we reset it to wake it up. > > > STACK == 0x1, 0xe8, 0x143, 0x16b > > SXFRCTL0 == 0x80 > > SCB count = 50 > > QINFIFO entries: > > Waiting Queue entries: > > Disconnected Queue entries: 2:20 0:49 > > QOUTFIFO entries: > > Sequencer Free SCB List: 13 14 15 3 9 1 10 12 5 6 11 4 7 8 > > Pending list: 20 49 > > Kernel Free SCB list: 33 11 24 35 34 48 17 18 14 47 45 31 22 21 27 36 16 4 5 9 12 15 25 26 28 46 2 10 29 23 7 38 13 0 8 6 32 30 3 19 37 1 44 43 42 41 40 > > sg[0] - Addr 0x1134000 : Length 1024 > > (da0:ahc0:0:0:0): Queuing a BDR SCB > > (da0:ahc0:0:0:0): Bus Device Reset Message Sent > > (da0:ahc0:0:0:0): no longer in timeout, status = 34b > > ahc0: Bus Device Reset on A:0. 2 SCBs aborted > > > > The machine has locked solid under X a couple times and then refused to boot, not seeing the disk at all even under the SCSI ROM startup, so I popped the case thinking it might be a loose cable or something and sure enough it booted ... though you see it fschked the disk from the crash ... I left it be for a while, came back and saw the errors on the screen .. a quick look at syslog showed similar entries at each of the crashes. > > > > It seems to be running now (I'm writing this on it) ... but if the disk if flaked, I may as well go buy a new one now rather than wonder when it's going to die. > > You should make sure your disk is properly cooled (is it hot to the > touch?). You should also check your cabling and termination. > > If your disk wasn't showing up during your SCSI controller's BIOS > probe, that could indicate a cabling or termination problem. It could > also mean the disk is on its way out. > > What sort of disk is it? Some disks are known to have firmware issues > that cause them to go "out to lunch" and not come back. > > Ken > -- > Kenneth Merry > ken@kdm.org > > > 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 25 18:54: 7 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 C3B0737B402 for ; Thu, 25 Jan 2001 18:53:49 -0800 (PST) Received: (from dillon@localhost) by earth.backplane.com (8.11.1/8.9.3) id f0Q2rJv99848; Thu, 25 Jan 2001 18:53:19 -0800 (PST) (envelope-from dillon) Date: Thu, 25 Jan 2001 18:53:19 -0800 (PST) From: Matt Dillon Message-Id: <200101260253.f0Q2rJv99848@earth.backplane.com> To: freebsd@mrynet.com (FreeBSD list) Cc: freebsd-stable@FreeBSD.ORG Subject: Re: NFS hangs root on today's CVSUP -- Unaddressed issue References: <200101260024.f0Q0O8l01300@mrynet.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It sounds like a network, firewall, or configuration problem. It is also possible that the 5.0 server is to blame (being -current). The best thing to do is to try to narrow down why your mount is failing. Look at /var/log/messages and see if there are any error messages from mountd. Use tcpdump to snarf the packets to see if the mount requests are being sent out and acknowledgements returned. There are only about a thousand things that could be causing problem. It's unlikely that -stable is inherently flawed here, though it is possible. -Matt :Previously, on Mon, 22 Jan 2001 18:42:23, I wrote: : :> After CVSUP'ing today and building world and installing a new kernel, :> ALL NFS mounts hang, and root (/) suddenly becomes unreadable with :> "/bin/ls -F"--it hangs as well. Also, df(1) and mount(8) hang :> forever. I've re-CVSUP'ed in case I caught something mid-stream, :> but the problem still prevails. :> :> Would others please check this? This NFS breakage renders a :> client of NFS unable to operate. : :This problem still exists and is a critical issue -- No NFS :mounts of filesystems from another machine can be made: : :# mount some.foreign.host:/path /path :<<>> : :>From another shell: :# df :<<>> : :>From yet another shell: :# /bin/ls -F / :<<>> : :Same for "# mount". : :The NFS host is running FreeBSD 5.0, which hasn't changed in a while. :It all started when a system was built from a cvsup on Jan 22. :Since then, I've cleared out /usr/src and /usr/obj and re-cvsup'd. :The problem persists. : :I've also tried "*default date=2000.01.01.00.00.01" in the cvsup file :to go back to a (presumably working) source date, but cvsup munged the :source tree beyond use. : :Can't anyone suggest a recourse here? : :Thanks, :-scott : To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 25 19: 3:25 2001 Delivered-To: freebsd-stable@freebsd.org Received: from thelab.hub.org (SHW1-154.accesscable.net [24.71.144.154]) by hub.freebsd.org (Postfix) with ESMTP id 70E6137B401; Thu, 25 Jan 2001 19:03:04 -0800 (PST) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.11.2/8.11.1) with ESMTP id f0Q314K30200; Thu, 25 Jan 2001 23:01:04 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Thu, 25 Jan 2001 23:01:04 -0400 (AST) From: The Hermit Hacker To: Cc: Subject: Read error on booting system ... 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 Morning all ... I have a 4.x system running on an old ALR server ... EISA bus, etc ... the drives are brand new QUANTUM Atlas V's ... the controller is an Adaptec controller per 3 drives (6 drives total) ... This evening, I got a call from the office that, when booting the machine, it gives a 'Read error', so I went in and tried a few things I could think of ... Finished off with putting in a boot floppy, getting to the 'boot:' prompt and trying to boot from there, and nadda ... lsdev shows the hard drives, and file systems, with the kernel file system being disk1s1a: ... how should I try and boot from there? 'boot disk1s1a:/kernel'? Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.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 25 19:25:38 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 B6DDE37B6A0 for ; Thu, 25 Jan 2001 19:25:19 -0800 (PST) Received: from dwcjr (DWCJR.inethouston.net [216.118.21.147]) by leviathan.inethouston.net (Postfix) with ESMTP id 917D9177E3F; Thu, 25 Jan 2001 21:25:25 -0600 (CST) Message-ID: <016501c08747$9d6a6fc0$931576d8@inethouston.net> From: "David W. Chapman Jr." To: "Dave Uhring" , "Colin" Cc: , "Luc Morin" References: <01012520300600.04280@dave> Subject: Re: Network stops working Date: Thu, 25 Jan 2001 21:25:21 -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's one thing I didn't try, leaving it off for a full minute, but I did wait for about 30 seconds. ----- Original Message ----- From: "Dave Uhring" To: "Colin" ; "David W. Chapman Jr." Cc: ; "Luc Morin" Sent: Thursday, January 25, 2001 8:30 PM Subject: Re: Network stops working > If his cable modem is similar to mine, it recognizes only one NIC and > must be power cycled in order to attach a different NIC. After killing > dhclient and restarting it, he will also receive a different IP address > from his ISP. The important thing is to kill the power to the cable > modem for at least 1 minute then power it back up again. > > Dave > > > On Thursday 25 January 2001 20:04, Colin wrote: > > The DHCP server has to keep a record of the lease or there will be > > all kinds of interesting problems. The server will see the mac > > address of the client in the DHCP-DISCOVER, and if it has a record of > > a valid, non-expired lease, it will send that information to the > > requesting client. I haven't done a lot of (ok, any :)) work with the > > BSD DHCP client, but there should be a command parameter or signal or > > something that says "please tell the server to expire my existing > > address" (on your Win box, AFAIR it's ipconfig -release) and from > > there you should be able to get a valid address. Your only other > > options are leaving the BSD box off the network for the duration of > > it's lease (could be a week or more) or calling the ISP and saying > > "Please kill the entry for my machine, IP 24.200.211.9, from the DHCP > > servers ..cur file" which they will probably be more than a little > > hesitant to do. I'm guessing the ISP has recently renumbered the > > network (I know my cable-modem based provider has been doing that a > > lot recently) and the Win box was not connected before it's lease > > expired. > > This all assumes that the Win box and BSD box are in fact > > seperate, not a dual boot system. If it is a dual boot system, the > > ISP's DHCP server has issues, as it should not issue 2 seperate > > addresses for the same mac address. > > > > Cheers, > > Colin Wass > > > > On 25-Jan-01 David W. Chapman Jr. wrote: > > > Are both os's on the same machine? A friend of mine had this > > > problem, had the cable modem plugged into the 98 workstation. then > > > when we connected it to the freebsd workstation it wouldn't get a > > > lease. Apparently the dhcp server keeps a record of the mac > > > address. > > > > > > ----- Original Message ----- > > > From: "Luc Morin" > > > To: > > > Sent: Thursday, January 25, 2001 5:28 PM > > > Subject: Re: Network stops working > > > > > >> Hi all, > > >> > > >> here's something interesting. > > >> > > >> I noticed that under Win98, the DHCP server will assign me > > >> 24.201.143.157, and under FreeBSD it will assign 24.200.211.9 > > >> > > >> How come ? Could this be a lead as to what's going on ? > > >> > > >> The one thing that bugs me most with this problem is that > > >> I have no problem under Windows. I'd rather it be the other > > >> way around :-) > > >> > > >> Regards, > > >> > > >> Luc Morin > > >> > > >> > > >> > > >> > > >> 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 > > > 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 25 19:32:37 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 75D0B37B69B for ; Thu, 25 Jan 2001 19:32:20 -0800 (PST) Received: by bazooka.unixfreak.org (Postfix, from userid 1000) id E543E3E0C; Thu, 25 Jan 2001 19:32:19 -0800 (PST) Received: from unixfreak.org (localhost [127.0.0.1]) by bazooka.unixfreak.org (Postfix) with ESMTP id E40343C10A; Thu, 25 Jan 2001 19:32:19 -0800 (PST) To: Rasputin Cc: stable@freebsd.org Subject: Re: World build failure In-Reply-To: Message from Rasputin of "Fri, 26 Jan 2001 02:22:18 GMT." <20010126022218.A2153@dogma.freebsd-uk.eu.org> Date: Thu, 25 Jan 2001 19:32:14 -0800 From: Dima Dorfman Message-Id: <20010126033219.E543E3E0C@bazooka.unixfreak.org> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > While we're on the subject, is there a good reason why the uucp > user/group is required to installworld when NOUUCP is set in > /etc/make.conf? The directories for UUCP are created with the correct permissions (i.e., uucp as the owner) regardless of whether NOUUCP is set. I guess this stems from the fact that mtree isn't very flexible in terms of excluding certain directories depending on options (and can you imagine having to maintain a set of mtree files for every possible combination of options?). Dima Dorfman dima@unixfreak.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 25 21: 2:10 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 ABBC237B400 for ; Thu, 25 Jan 2001 21:01:53 -0800 (PST) Received: from [203.164.12.28] by www.quake.com.au (NTMail 4.30.0012/AH9370.63.d1acf55c) with ESMTP id dgwsaaaa for ; Fri, 26 Jan 2001 16:10:31 +1100 Message-ID: <3A7104CE.3EF662AD@quake.com.au> Date: Fri, 26 Jan 2001 16:02:06 +1100 From: Kal Torak X-Mailer: Mozilla 4.73 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Jon Hamilton Cc: Stephen Montgomery-Smith , Luc Morin , freebsd-stable@FreeBSD.ORG Subject: Re: Network stops working References: <20010125195256.67841201@woodstock.monkey.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > At home: gets IP address from DHCP server fine. Can connect to various > other machines on the subnet ok. Can ssh to various machines both on the > home LAN and outside the NATted subnet, but cannot connect from other machines > to the laptop. Packets come in, but for some reason (according to both > the ipfw logs and tcpdump) the kernel on the laptop doesn't seem to respond > with outgoing packets at all. The firewall is not blocking the packets; they > don't even get that far (tested by logging all traffic to/from all interfaces > on the laptop). This bizarreness holds for TCP and ICMP traffic. The odd > thing is, for "outgoing" connections (ssh from laptop to server) everything > is fine; traffic moves just fine both directions. This sounds like the driver isnt detecting the MAC address correctly... There was a problem with some new netgear and cards that used the same chip recently like that, it has been fixed but maybe this is a new one... You should probably file a PR about it since its only in the newer stable! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 25 21:11:26 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 D4EF337B401 for ; Thu, 25 Jan 2001 21:11:08 -0800 (PST) Received: from [203.164.12.28] by www.quake.com.au (NTMail 4.30.0012/AH9370.63.d1acf55c) with ESMTP id fgwsaaaa for ; Fri, 26 Jan 2001 16:19:41 +1100 Message-ID: <3A7106F5.720A4F2C@quake.com.au> Date: Fri, 26 Jan 2001 16:11:17 +1100 From: Kal Torak X-Mailer: Mozilla 4.73 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Luc Morin Cc: freebsd-stable@freebsd.org Subject: Re: Network stops working References: <200101252002.f0PK2l616273@cwsys.cwsent.com> <000701c08726$7c6d0380$9d8fc918@videotron.ca> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Luc Morin wrote: > > Hi all, > > here's something interesting. > > I noticed that under Win98, the DHCP server will assign me > 24.201.143.157, and under FreeBSD it will assign 24.200.211.9 > > How come ? Could this be a lead as to what's going on ? Hmmm, this also sounds like an incorrect MAC address being detected by the driver... I thought not at first because you said it was working after the upgrade but this really looks like it... Have you got another FreeBSD system you could network them with? Because if I am right when you boot into windows after being in FreeBSD, the other system should give you an ARP message on the console saying IP x.x.x.x has moved from to ... Since some cable providers work of your cards MAC address for what IP you should get this seems probable... You are all using the ed driver? Looks as if a some changes took place recently thats broken it for some cards maybe... Or it could be something totally different :) Good luck! Kal. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 25 22:25:19 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail.nbrewer.com (unknown [208.42.68.70]) by hub.freebsd.org (Postfix) with ESMTP id 17D9C37B69B for ; Thu, 25 Jan 2001 22:25:02 -0800 (PST) Received: by mail.nbrewer.com (Postfix, from userid 1009) id 8DB1E4C4; Fri, 26 Jan 2001 00:25:01 -0600 (CST) Date: Fri, 26 Jan 2001 00:25:01 -0600 From: Christopher Farley To: Odhiambo Washington Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Ports update - is something broken? Message-ID: <20010126002500.F5272@northernbrewer.com> Mail-Followup-To: Christopher Farley , Odhiambo Washington , freebsd-stable@FreeBSD.ORG References: <3A702B20.EBEE505@quake.com.au> <20010125223635.F70366@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: <20010125223635.F70366@poeza.iconnect.co.ke>; from wash@iconnect.co.ke on Thu, Jan 25, 2001 at 10:36:35PM +0300 Organization: Northern Brewer, St. Paul, MN Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Odhiambo Washington (wash@iconnect.co.ke) wrote: > *default host=CHANGE_THIS.FreeBSD.org > *default base=/usr > *default prefix=/usr > *default release=cvs tag=. > *default delete use-rel-suffix > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > Or did he remove that from the supfile? "default delete" sounds tempting, but the cvsup server doesn't delete files it doesn't know about. As stated, the proper solution is to install the ports upgrade kit. The "brute force" method of deleting the ports tree and re-cvsupping also works. -- Christopher Farley www.northernbrewer.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 26 0:41: 3 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 8499537B401 for ; Fri, 26 Jan 2001 00:40:46 -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 f0Q8eWt95365; Fri, 26 Jan 2001 00:40:32 -0800 (PST) (envelope-from jkh@winston.osd.bsdi.com) To: freebsd@mrynet.com (FreeBSD list) Cc: freebsd-stable@FreeBSD.ORG Subject: Re: NFS hangs root on today's CVSUP -- Unaddressed issue In-Reply-To: Message from freebsd@mrynet.com (FreeBSD list) of "Thu, 25 Jan 2001 18:24:08 CST." <200101260024.f0Q0O8l01300@mrynet.com> Date: Fri, 26 Jan 2001 00:40:32 -0800 Message-ID: <95361.980498432@winston.osd.bsdi.com> From: Jordan Hubbard Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > This problem still exists and is a critical issue -- No NFS > mounts of filesystems from another machine can be made: I beg to differ. NFS works just fine for me as a client in -current: root@zippy-> uname -a FreeBSD zippy.osd.bsdi.com 5.0-CURRENT FreeBSD 5.0-CURRENT #2: Thu Jan 25 01:10:31 PST 2001 jkh@zippy.osd.bsdi.com:/usr/obj/usr/src/sys/ZIPPY i386 root@zippy-> mount winston:/usr /mnt root@zippy-> ls /mnt X11R6 compat home lib libexec mdec ports share tmp bin games include libdata local obj sbin src root@zippy-> umount /mnt root@zippy-> ls /mnt root@zippy-> And just to show that it works as a server too: root@winston-> uname -a FreeBSD winston.osd.bsdi.com 4.2-STABLE FreeBSD 4.2-STABLE #0: Wed Jan 17 12:26:40 PST 2001 jkh@winston.osd.bsdi.com:/a/obj/a/src/sys/WINSTON i386 root@winston-> mount zippy:/usr /mnt root@winston-> ls /mnt X11R6 games libdata mdec share bin home libexec obj src compat include local ports tmp doc lib lost+found sbin root@winston-> umount /mnt root@winston-> ls /mnt > Can't anyone suggest a recourse here? Be easier if it were even reproducible. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 26 2:59:20 2001 Delivered-To: freebsd-stable@freebsd.org Received: from plab.ku.dk (plab.ku.dk [130.225.105.65]) by hub.freebsd.org (Postfix) with ESMTP id 9CC8C37B400 for ; Fri, 26 Jan 2001 02:59:02 -0800 (PST) Received: (from root@localhost) by plab.ku.dk (8.11.0/8.9.3) id f0QAx0m11101 for freebsd-stable@freebsd.org.AVP; Fri, 26 Jan 2001 11:59:00 +0100 (CET) (envelope-from postmaster@plab.ku.dk) Received: from raven.plab.ku.dk (raven.plab.ku.dk [130.225.105.67]) by plab.ku.dk (8.11.0/8.9.3) with ESMTP id f0QAx0b11093 for ; Fri, 26 Jan 2001 11:59:00 +0100 (CET) (envelope-from postmaster@plab.ku.dk) In-Reply-To: Bob K's message of "Thu, 25 Jan 2001 09:12:35 -0500 (EST)" Subject: Re: Ports update - is something broken? Content-Transfer-Encoding: 8bit References: To: freebsd-stable@freebsd.org From: Dmitry Karasik X-Comment-To: Bob K Content-Type: text/plain; charset="koi8-r" Lines: 21 Mime-Version: 1.0 Date: 26 Jan 2001 11:56:49 +0100 X-Mailer: Mail::Mailer[v1.18] Net::SMTP[v2.13] Message-Id: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Bob! On 25 Jan 01 at 09:12, "Bob" (Bob K) wrote: Bob> On Fri, 26 Jan 2001, Kal Torak wrote: >> I think you will find cvsup didnt remove some of the old stuff in your >> ports tree... A simple solution if you have the time is to rm -rf your >> ports and cvsup them again... Bob> Actually, Dmitry probably needs to download an upgrade kit from Bob> http://www.freebsd.org/ports/ . Thanks you all - upgrade was just fine. BTW, rm -rf didn't work, just FYI. -- Sincerely, Dmitry --- www.karasik.eu.org --- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 26 6:27:21 2001 Delivered-To: freebsd-stable@freebsd.org Received: from gate.trident-uk.co.uk (mail.trident-uk.co.uk [195.166.16.10]) by hub.freebsd.org (Postfix) with ESMTP id 8197737B400 for ; Fri, 26 Jan 2001 06:27:00 -0800 (PST) Received: from [194.207.93.139] by gate.trident-uk.co.uk for dibble@cc.gatech.edu id OAA20256; Fri Jan 26 14:20:32 2001 Date: Fri, 26 Jan 2001 14:33:26 +0000 Subject: Make World Fails! Message-ID: <20010126143326.E615@freefire.psi-domain.co.uk> References: <20010124143318.S238@freefire.psi-domain.co.uk> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="SLDf9lqlvOQaIe6s" Content-Transfer-Encoding: 8bit In-Reply-To: ; from dibble@cc.gatech.edu on Wed, Jan 24, 2001 at 18:22:55 +0000 X-Mailer: Balsa 1.0.0 Lines: 159 To: Dibble From: Jamie Heckford Reply-To: heckfordj@psi-domain.co.uk Cc: freebsd-stable@freebsd.org Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --SLDf9lqlvOQaIe6s Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Hi, Still no success after CVS'uping again - after follwing dibbles instructions. I have attatched the output as a text file. Please Help!! Thanks Jamie On 2001.01.24 18:22:55 +0000 Dibble wrote: > On Wed, 24 Jan 2001, Jamie Heckford wrote: > > > I tried this but no joy. > > > > I have also followed the handbook steps for removing /usr/obj files. > > > > make clean gives the error: > > > Alright, Try: > rm -rf /usr/obj > cvsup > make buildworld > make buildkernel > make installkernel > make installworld > mergemaster > > If that doesnt' work... > Hmmm... > > > > > -- Jamie Heckford Chief Network Engineer Psi-Domain - Innovative Linux Solutions. Ask Us How. ===================================== email: heckfordj@psi-domain.co.uk web: http://www.psi-domain.co.uk/ tel: +44 (0)1737 789 246 fax: +44 (0)1737 789 245 mobile: +44 (0)7866 724 224 ===================================== --SLDf9lqlvOQaIe6s Content-Type: application/octet-stream; charset=us-ascii Content-Disposition: attachment; filename=makebuildworld-failure -------------------------------------------------------------- >>> 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/usr.bin/yacc; make obj; make depend; make all; make install /usr/obj/usr/src/i386/usr/src/usr.bin/yacc created for /usr/src/usr.bin/yacc rm -f .depend mkdep -f .depend -a -I/usr/obj/usr/src/i386/usr/include /usr/src/usr.bin/yacc/closure.c /usr/src/usr.bin/yacc/error.c /usr/src/usr.bin/yacc/lalr.c /usr/src/usr.bin/yacc/lr0.c /usr/src/usr.bin/yacc/main.c /usr/src/usr.bin/yacc/mkpar.c /usr/src/usr.bin/yacc/output.c /usr/src/usr.bin/yacc/reader.c /usr/src/usr.bin/yacc/skeleton.c /usr/src/usr.bin/yacc/symtab.c /usr/src/usr.bin/yacc/verbose.c /usr/src/usr.bin/yacc/warshall.c cd /usr/src/usr.bin/yacc; make _EXTRADEPEND echo yacc: /usr/obj/usr/src/i386/usr/lib/libc.a >> .depend cc -O -pipe -I/usr/obj/usr/src/i386/usr/include -c /usr/src/usr.bin/yacc/closure.c cc -O -pipe -I/usr/obj/usr/src/i386/usr/include -c /usr/src/usr.bin/yacc/error.c cc -O -pipe -I/usr/obj/usr/src/i386/usr/include -c /usr/src/usr.bin/yacc/lalr.c cc -O -pipe -I/usr/obj/usr/src/i386/usr/include -c /usr/src/usr.bin/yacc/lr0.c cc -O -pipe -I/usr/obj/usr/src/i386/usr/include -c /usr/src/usr.bin/yacc/main.c cc -O -pipe -I/usr/obj/usr/src/i386/usr/include -c /usr/src/usr.bin/yacc/mkpar.c cc -O -pipe -I/usr/obj/usr/src/i386/usr/include -c /usr/src/usr.bin/yacc/output.c cc -O -pipe -I/usr/obj/usr/src/i386/usr/include -c /usr/src/usr.bin/yacc/reader.c cc -O -pipe -I/usr/obj/usr/src/i386/usr/include -c /usr/src/usr.bin/yacc/skeleton.c cc -O -pipe -I/usr/obj/usr/src/i386/usr/include -c /usr/src/usr.bin/yacc/symtab.c cc -O -pipe -I/usr/obj/usr/src/i386/usr/include -c /usr/src/usr.bin/yacc/verbose.c cc -O -pipe -I/usr/obj/usr/src/i386/usr/include -c /usr/src/usr.bin/yacc/warshall.c cc -O -pipe -I/usr/obj/usr/src/i386/usr/include -o yacc closure.o error.o lalr.o lr0.o main.o mkpar.o output.o reader.o skeleton.o symtab.o verbose.o warshall.o sh /usr/src/tools/install.sh -c -o root -g wheel -m 555 /usr/src/usr.bin/yacc/yyfix.sh /usr/obj/usr/src/i386/usr/bin/yyfix sh /usr/src/tools/install.sh -c -s -o root -g wheel -m 555 yacc /usr/obj/usr/src/i386/usr/bin /usr/obj/usr/src/i386/usr/bin/byacc -> /usr/obj/usr/src/i386/usr/bin/yacc cd /usr/src/usr.bin/colldef; make obj; make depend; make all; make install /usr/obj/usr/src/i386/usr/src/usr.bin/colldef created for /usr/src/usr.bin/colldef yacc -d /usr/src/usr.bin/colldef/parse.y cp y.tab.c parse.c lex -t -8 -i /usr/src/usr.bin/colldef/scan.l > scan.c rm -f .depend mkdep -f .depend -a -I. -I/usr/src/usr.bin/colldef/../../lib/libc/locale -DCOLLATE_DEBUG -I/usr/obj/usr/src/i386/usr/include parse.c scan.c cd /usr/src/usr.bin/colldef; make _EXTRADEPEND echo colldef: /usr/obj/usr/src/i386/usr/lib/libc.a /usr/obj/usr/src/i386/usr/lib/libl.a >> .depend cc -O -pipe -Wall -I. -I/usr/src/usr.bin/colldef/../../lib/libc/locale -DCOLLATE_DEBUG -I/usr/obj/usr/src/i386/usr/include -c parse.c cc -O -pipe -Wall -I. -I/usr/src/usr.bin/colldef/../../lib/libc/locale -DCOLLATE_DEBUG -I/usr/obj/usr/src/i386/usr/include -c scan.c cc -O -pipe -Wall -I. -I/usr/src/usr.bin/colldef/../../lib/libc/locale -DCOLLATE_DEBUG -I/usr/obj/usr/src/i386/usr/include -o colldef parse.o scan.o -ll sh /usr/src/tools/install.sh -c -s -o root -g wheel -m 555 colldef /usr/obj/usr/src/i386/usr/bin cd /usr/src/usr.sbin/config; make obj; make depend; make all; make install /usr/obj/usr/src/i386/usr/src/usr.sbin/config created for /usr/src/usr.sbin/config yacc -d /usr/src/usr.sbin/config/config.y cp y.tab.c config.c lex -t /usr/src/usr.sbin/config/lang.l > lang.c rm -f .depend mkdep -f .depend -a -I. -I/usr/src/usr.sbin/config -I/usr/obj/usr/src/i386/usr/include config.c /usr/src/usr.sbin/config/main.c lang.c /usr/src/usr.sbin/config/mkioconf.c /usr/src/usr.sbin/config/mkmakefile.c /usr/src/usr.sbin/config/mkheaders.c /usr/src/usr.sbin/config/mkoptions.c cd /usr/src/usr.sbin/config; make _EXTRADEPEND echo config: /usr/obj/usr/src/i386/usr/lib/libc.a /usr/obj/usr/src/i386/usr/lib/libl.a >> .depend cc -O -pipe -I. -I/usr/src/usr.sbin/config -Wall -Wunused -Wmissing-prototypes -Wredundant-decls -I/usr/obj/usr/src/i386/usr/include -c config.c cc -O -pipe -I. -I/usr/src/usr.sbin/config -Wall -Wunused -Wmissing-prototypes -Wredundant-decls -I/usr/obj/usr/src/i386/usr/include -c /usr/src/usr.sbin/config/main.c cc -O -pipe -I. -I/usr/src/usr.sbin/config -Wall -Wunused -Wmissing-prototypes -Wredundant-decls -I/usr/obj/usr/src/i386/usr/include -c lang.c cc -O -pipe -I. -I/usr/src/usr.sbin/config -Wall -Wunused -Wmissing-prototypes -Wredundant-decls -I/usr/obj/usr/src/i386/usr/include -c /usr/src/usr.sbin/config/mkioconf.c cc -O -pipe -I. -I/usr/src/usr.sbin/config -Wall -Wunused -Wmissing-prototypes -Wredundant-decls -I/usr/obj/usr/src/i386/usr/include -c /usr/src/usr.sbin/config/mkmakefile.c cc -O -pipe -I. -I/usr/src/usr.sbin/config -Wall -Wunused -Wmissing-prototypes -Wredundant-decls -I/usr/obj/usr/src/i386/usr/include -c /usr/src/usr.sbin/config/mkheaders.c cc -O -pipe -I. -I/usr/src/usr.sbin/config -Wall -Wunused -Wmissing-prototypes -Wredundant-decls -I/usr/obj/usr/src/i386/usr/include -c /usr/src/usr.sbin/config/mkoptions.c cc -O -pipe -I. -I/usr/src/usr.sbin/config -Wall -Wunused -Wmissing-prototypes -Wredundant-decls -I/usr/obj/usr/src/i386/usr/include -o config config.o main.o lang.o mkioconf.o mkmakefile.o mkheaders.o mkoptions.o -ll sh /usr/src/tools/install.sh -c -s -o root -g wheel -m 555 config /usr/obj/usr/src/i386/usr/sbin cd /usr/src/gnu/usr.bin/gperf; make obj; make depend; make all; make install /usr/obj/usr/src/i386/usr/src/gnu/usr.bin/gperf created for /usr/src/gnu/usr.bin/gperf ===> doc /usr/obj/usr/src/i386/usr/src/gnu/usr.bin/gperf/doc created for /usr/src/gnu/usr.bin/gperf/doc *** Error code 2 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. --SLDf9lqlvOQaIe6s-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 26 7:13:24 2001 Delivered-To: freebsd-stable@freebsd.org Received: from dilbert.fcg.co.uk (dilbert.firstcallgroup.co.uk [194.203.69.166]) by hub.freebsd.org (Postfix) with ESMTP id 1640A37B400 for ; Fri, 26 Jan 2001 07:13:08 -0800 (PST) Received: from pfrench by dilbert.fcg.co.uk with local (Exim 3.20 #1) id 14MAYR-0000Zc-00; Fri, 26 Jan 2001 15:12:47 +0000 To: simond@irrelevant.org Subject: Re: anybody seen this one ? Cc: kaltorak@quake.com.au, stable@FreeBSD.ORG In-Reply-To: <20010125112447.A91024@irrelevant.org> Message-Id: From: Pete French Date: Fri, 26 Jan 2001 15:12:48 +0000 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I had this problem too a while back, I fixed it for myself at the time > by removing the flags 0x1 from the atkbd0 entry in the kernel config file, > this can also be done via boot -c and similar, I then managed to fix it Sadly even boot -c doesnt work - that just goes into a loop scrolling 'config." up the screen blurringly fast. I have now disabled just about everuthing I can in the BIOS, time too try reflashing it with anewer version I guess. -pete. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 26 7:30:16 2001 Delivered-To: freebsd-stable@freebsd.org Received: from loki.fbibuildings.com (unknown [12.37.16.82]) by hub.freebsd.org (Postfix) with ESMTP id 2C04537B401; Fri, 26 Jan 2001 07:29:49 -0800 (PST) Received: by loki with Internet Mail Service (5.5.2650.21) id ; Fri, 26 Jan 2001 10:29:39 -0500 Message-ID: <81B7EF64291AD41187AA00B0D02083FD51D036@loki> From: Steve McNelly To: "'questions@freebsd.org'" , "'stable@freebsd.org'" Subject: Make Buildworld Fails Here: Date: Fri, 26 Jan 2001 10:29:38 -0500 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 Could Someone Please Help Me With This Problem? I Am Currently Running 3.4-RELEASE. I Used cvsup To Update My Source Files.(Several Times) To 3.x-STABLE. This Was My cvsupfile: *default host=cvsup.FreeBSD.org *default base=/usr *default prefix=/usr *default release=cvs *default tag=RELENG_3 *default delete use-rel-suffix src-all src-crypto src-secure *default tag=. ports-all doc-all When I Do "make buildworld" It Fails Here Everytime. I Have Read Through The Mail Archives I Have Read The Updating Stuff But I Can not Find An Answer. I Have tried "make cleandir" I Have Tried Deleting "/usr/obj" Still Doesn't Work. Don't Know What Else To Try. Help Please. Thanks In Advance, /usr/obj/usr/dest/usr/src/tmp/usr/bin/make -DNOINFO -DNOMAN -DNOPIC -DNOPROFILE -DNOSHARED all; /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 /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 /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 -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 -I/usr/obj/usr/dest/usr/src/tmp/usr/include -c parse.c lex -t /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 -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 -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 -I/usr/obj/usr/dest/usr/src/tmp/usr/include -static -o compile_et compile_et.o parse.o lex.o getarg.o 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 Fri Jan 26 8: 0:43 2001 Delivered-To: freebsd-stable@freebsd.org Received: from netcabo.pt (unknown [212.113.161.137]) by hub.freebsd.org (Postfix) with ESMTP id B1E7837B401 for ; Fri, 26 Jan 2001 08:00:22 -0800 (PST) Received: from OpsyDopsy.net.dhis.org ([213.22.2.137]) by netcabo.pt with Microsoft SMTPSVC(5.5.1877.537.53); Fri, 26 Jan 2001 15:58:46 +0000 From: =?iso-8859-1?q?Jo=E3o=20Fernandes?= To: stable@freebsd.org Subject: Re: Network stops working Date: Fri, 26 Jan 2001 16:01:58 +0000 X-Mailer: KMail [version 1.1.99] Content-Type: text/plain; charset="iso-8859-1" MIME-Version: 1.0 Message-Id: <01012616015800.01690@OpsyDopsy.net.dhis.org> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Me also have been having similar problems. I have a realtek 8139 and a cable modem. I use DHCP to connect to the network and my /etc/dhclient.conf has nothing on it. My problems are: The speed of my connections are way slower in FreeBSD than are in windows; To the extent of downloading at 2 kps when in windows I would download the same file from the same site at 70kps. My connection gets 100% packets lost if I put for example cvsup and a download from the ports tree working at the same time. (and sometimes even with a single download it just hangs...) I shall now insert a few system info: I'm running a 4.2 stable box, cvsupdated about 2 weeks ago. I have IPFilter running. ipf.rules: #Block all from all protocols block in log first on rl0 proto icmp from any to any block in log first on rl0 proto tcp from any to any block in log first on rl0 proto udp from any to any #Block in for X block in log first on rl0 proto tcp/udp/icmp from any to any port = 6000 #Block in for smtp block in log first on rl0 proto tcp/udp/icmp from any to any port = smtp #Anti spoofing rules block in quick on rl0 from 127.0.0.0/8 to any block in quick on rl0 from 0.0.0.0/8 to any #Pass mail #pass in on rl0 proto tcp from any to any port = smtp #Pass FTP Connections pass in on rl0 proto tcp from any to any port = ftp pass in on rl0 proto tcp from any to any port = ftp-data #Pass dhis pass in on rl0 proto udp from any to any port = 58800 #Pass out all pass out on rl0 proto tcp from any to any keep state keep frags pass out on rl0 proto udp from any to any keep state keep frags pass out on rl0 proto icmp from any to any keep state keep frags dmesg: 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 #1: Tue Jan 23 10:47:42 WET 2001 root@OpsyDopsy.net.dhis.org:/usr/src/sys/compile/PIII-650 Timecounter "i8254" frequency 1193182 Hz CPU: Pentium III/Pentium III Xeon/Celeron (651.48-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x681 Stepping = 1 Features=0x383f9ff real memory = 134201344 (131056K bytes) avail memory = 127410176 (124424K bytes) Preloaded elf kernel "kernel" at 0xc0328000. VESA: v3.0, 4096k memory, flags:0x1, mode table:0xc02ca222 (1000022) VESA: NVidia 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 irq 11 isab0: at device 4.0 on pci0 isa0: on isab0 atapci0: port 0xd800-0xd80f at device 4.1 on pci0ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: at 4.2 irq 5 chip1: port 0xe800-0xe80f at device 4.3 on pci0 rl0: port 0xd000-0xd0ff mem 0xc5800000-0xc58000ff irq 5 at device 9.0 on pci0 rl0: Ethernet address: 00:00:b4:c2:2d:28 miibus0: on rl0 rlphy0: on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto pcm0: port 0xb800-0xb81f irq 10 at device 10.0 on pci0 atapci1: port 0x9800-0x983f,0xa000-0xa003,0xa400-0xa407,0xa800-0xa803,0xb000-0xb007 mem 0xc5000000-0xc501ffff irq 10 at device 14.0 on pci0 ata2: at 0xb000 on atapci1 ata3: at 0xa400 on atapci1 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 IntelliMouse, device ID 3 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: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/9 bytes threshold lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 IP Filter: v3.4.8 initialized. Default = pass all, Logging = enabled ad4: 19541MB [39703/16/63] at ata2-master UDMA66 acd0: CDROM at ata1-master using PIO4 Mounting root from ufs:/dev/ad4s3a Hope some one gets to the bottom of this. Joao Fernandes To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 26 8:18:22 2001 Delivered-To: freebsd-stable@freebsd.org Received: from wyattearp.stanford.edu (wyattearp.Stanford.EDU [171.64.180.171]) by hub.freebsd.org (Postfix) with ESMTP id EDBDB37B401 for ; Fri, 26 Jan 2001 08:18:00 -0800 (PST) Received: (from richw@localhost) by wyattearp.stanford.edu (8.9.3/8.9.3) id IAA36629; Fri, 26 Jan 2001 08:17:59 -0800 (PST) (envelope-from richw) Date: Fri, 26 Jan 2001 08:17:58 -0800 (PST) From: Rich Wales X-Sender: richw@wyattearp.stanford.edu To: freebsd-stable@freebsd.org Subject: Can't get a crash dump?!? Message-ID: <20010126153344.35549.richw@wyattearp.stanford.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm running 4.2-STABLE (cvsup'ed on January 20) on a Pentium which I'm using as a firewall/bridge at home. For the most part, the system works well, but it crashes under a sus- tained heavy network load with "panic: m_dup: bogus m_pkthdr.len". I can produce this panic at will by trying to download a very large file. However, I've been completely unable to get a crash dump. I have "dumpdev" set in /etc/rc.conf, and the "swapon" command works during startup. (The box has 24MB of RAM, and the swap partition is over twice that big, so dumping should theoretically work.) If I include "options DDB" in the kernel configuration, then the system (eventually) panics and drops into DDB. I can do a trace and other DDB commands, but nothing I've tried so far will cause a crash dump to be written out. In particular, I've tried combinations of panic continue call boot(0) call boot(256) [ RB_DUMP flag value in ] but the best I can manage to do is get a "page fault while in kernel mode" panic and another DDB prompt. If I don't include "options DDB", then when the system eventually crashes, it goes haywire. Screenful after screenful of (presumably) panic messages whiz by on the monitor, and then a bunch of random color bars are displayed (as if video memory has been overwritten with random junk?), and then it reboots. I tried adding some "printf"s to dumpsys() (in kern/kern_shutdown.c), in order to see why it wasn't dumping, but none of my extra messages get printed -- suggesting that dumpsys() isn't even being called. Any ideas? Rich Wales richw@webcom.com http://www.webcom.com/richw/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 26 8:18:52 2001 Delivered-To: freebsd-stable@freebsd.org Received: from vexpert.dbai.tuwien.ac.at (vexpert.dbai.tuwien.ac.at [128.130.111.12]) by hub.freebsd.org (Postfix) with ESMTP id 23A6B37B402 for ; Fri, 26 Jan 2001 08:18:35 -0800 (PST) Received: from deneb.dbai.tuwien.ac.at (deneb [128.130.111.2]) by vexpert.dbai.tuwien.ac.at (8.11.1/8.11.1) with ESMTP id f0QGHYe00424; Fri, 26 Jan 2001 17:17:35 +0100 (MET) Received: from localhost (pfeifer@localhost) by deneb.dbai.tuwien.ac.at (8.11.1/8.11.1) with ESMTP id f0QGHWb11368; Fri, 26 Jan 2001 17:17:34 +0100 (CET) (envelope-from pfeifer@dbai.tuwien.ac.at) X-Authentication-Warning: deneb.dbai.tuwien.ac.at: pfeifer owned process doing -bs Date: Fri, 26 Jan 2001 17:17:31 +0100 (CET) From: Gerald Pfeifer To: Cc: Cy Schubert - ITSD Open Systems Group Subject: Re: amq -v In-Reply-To: <200101251517.f0PFHL614920@cwsys.cwsent.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 Thu, 25 Jan 2001, Cy Schubert - ITSD Open Systems Group wrote: >>> full_os=freebsd4.2-BETA, os=freebsd4, osver=4.2-BETA, vendor=unknown. >>> ^^^^^ ^^^^^ > What I think is happening, w/o looking at the source, is that full_os > and osver are obtained from the system that amd was built on, not the > system it was built for. I agree. As someone suggested in private e-mail: I guess it might [make sense] to lay the tags, build the world, install the world, reboot and do a clean make release. As this really confused users ``Now, do I have 4.2-RELEASE or don't I?'', it would be good addressing this for future releases. Gerald -- Gerald "Jerry" pfeifer@dbai.tuwien.ac.at http://www.dbai.tuwien.ac.at/~pfeifer/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 26 9:12: 3 2001 Delivered-To: freebsd-stable@freebsd.org Received: from math.missouri.edu (math.missouri.edu [128.206.49.180]) by hub.freebsd.org (Postfix) with ESMTP id CDD2C37B402 for ; Fri, 26 Jan 2001 09:11:45 -0800 (PST) Received: from math.missouri.edu (stephen@cauchy.math.missouri.edu [128.206.49.166]) by math.missouri.edu (8.9.3/8.9.3) with ESMTP id LAA90104; Fri, 26 Jan 2001 11:11:39 -0600 (CST) (envelope-from stephen@math.missouri.edu) Message-ID: <3A71AFD1.4813ED39@math.missouri.edu> Date: Fri, 26 Jan 2001 11:11:45 -0600 From: Stephen Montgomery-Smith Organization: University of Missouri X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Luc Morin , freebsd-stable@FreeBSD.ORG Subject: Re: Network stops working References: <001001c08628$8db16180$9d8fc918@videotron.ca> <20010124164125.A12612@home.com> <01012500480800.01077@jamestown.enteract.com> <3A6FD545.3D329446@quake.com.au> <002b01c086e4$2c843060$9d8fc918@videotron.ca> <3A705EAA.23BD59B4@quake.com.au> <005a01c086f7$337f51c0$9d8fc918@videotron.ca> <3A706A34.E5F1C502@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 Just to add - when dhcp does successfully negotiate, it does take a very long time to do it - several minutes - certainly a lot longer than it used to. Stephen Montgomery-Smith wrote: > > That's interesting - I have a similar problem that also > just started recently (coincided with changing my power > supply but I'm sure that it is unrelated). I find that > one of three things happens: > > 1. dhcp simply does not successfully negotiate > > 2. dhcp negotiates, gets an IP number and a router, but > then I get 100% packet loss. (Never tried calling them to > see if they got through to me.) > > 3. It actually works. > > Option 2 is what usually happens, but if I restarting > dhcp enough times, I get option 3. Since I keep the > connection up all the time, I only worry about the > problem sporadically. So I have never tried to investigate > its cause. (The ISP is att@home if that is useful. My > NIC is a RealTek 8139.) > -- Stephen Montgomery-Smith stephen@math.missouri.edu 307 Math Science Building stephen@showme.missouri.edu Department of Mathematics stephen@missouri.edu University of Missouri-Columbia Columbia, MO 65211 USA Phone (573) 882 4540 Fax (573) 882 1869 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 Fri Jan 26 11:28:23 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 EAEF837B699 for ; Fri, 26 Jan 2001 11:28:01 -0800 (PST) Received: from localhost (dwagner@localhost) by cj409896-a.reston1.va.home.com (8.11.1/8.11.1) with ESMTP id f0QJRvv33230; Fri, 26 Jan 2001 14:27:57 -0500 (EST) (envelope-from dawagner@vt.edu) Date: Fri, 26 Jan 2001 14:27:57 -0500 (EST) From: David Wagner X-X-Sender: To: =?iso-8859-1?q?Jo=E3o=20Fernandes?= Cc: Subject: Re: Network stops working In-Reply-To: <01012616015800.01690@OpsyDopsy.net.dhis.org> 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 Fri, 26 Jan 2001, Jo=E3o Fernandes wrote: > I have a realtek 8139 and a cable modem. I use DHCP to connect to the net= work > and my /etc/dhclient.conf has nothing on it. > > My problems are: > =09The speed of my connections are way slower in FreeBSD than are > in windows; To the extent of downloading at 2 kps when in windows I > would download the same file from the same site at 70kps. Well, I have a theory, because I had somewhat similar behavior. Some cable modem + nic combinations have trouble autdetecting the line speed. Try forcing your connection to 10BaseT half duplex (which is almost guaranteed to be what the cable modem supports). Example: % ifconfig rl0 media 10baseT/UTP This managed to triple my connection speed in most cases... ______________________________________________________________________ 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 Fri Jan 26 11:45:58 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 7FC6C37B402 for ; Fri, 26 Jan 2001 11:45:35 -0800 (PST) Received: (from kris@localhost) by citusc17.usc.edu (8.11.1/8.11.1) id f0QJmfA83043; Fri, 26 Jan 2001 11:48:41 -0800 (PST) (envelope-from kris) Date: Fri, 26 Jan 2001 11:48:41 -0800 From: Kris Kennaway To: Christopher Farley Cc: Odhiambo Washington , freebsd-stable@FreeBSD.ORG Subject: Re: Ports update - is something broken? Message-ID: <20010126114841.C82866@citusc17.usc.edu> References: <3A702B20.EBEE505@quake.com.au> <20010125223635.F70366@poeza.iconnect.co.ke> <20010126002500.F5272@northernbrewer.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="KDt/GgjP6HVcx58l" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010126002500.F5272@northernbrewer.com>; from chris@northernbrewer.com on Fri, Jan 26, 2001 at 12:25:01AM -0600 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --KDt/GgjP6HVcx58l Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jan 26, 2001 at 12:25:01AM -0600, Christopher Farley wrote: > Odhiambo Washington (wash@iconnect.co.ke) wrote: >=20 > > *default host=3DCHANGE_THIS.FreeBSD.org > > *default base=3D/usr > > *default prefix=3D/usr > > *default release=3Dcvs tag=3D. > > *default delete use-rel-suffix > > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > >=20 > > Or did he remove that from the supfile? >=20 > "default delete" sounds tempting, but the cvsup server doesn't > delete files it doesn't know about. As stated, the proper solution=20 > is to install the ports upgrade kit. The "brute force" method > of deleting the ports tree and re-cvsupping also works. Or see Q12 and Q13 in teh cvsup FAQ on www.polstra.com Kris --=20 NOTE: To fetch an updated copy of my GPG key which has not expired, finger kris@FreeBSD.org --KDt/GgjP6HVcx58l 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 iD8DBQE6cdSZWry0BWjoQKURAtIkAKC3fij7FUpwfwb3fzKKgA6Zv+iCdwCfe/ez r0E9zu8EwdckJ1xWV2ixDJM= =HtSa -----END PGP SIGNATURE----- --KDt/GgjP6HVcx58l-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 26 13:40: 2 2001 Delivered-To: freebsd-stable@freebsd.org Received: from cs.huji.ac.il (cs.huji.ac.il [132.65.16.10]) by hub.freebsd.org (Postfix) with ESMTP id 76E6637B401 for ; Fri, 26 Jan 2001 13:39:45 -0800 (PST) Received: from sexta.cs.huji.ac.il ([132.65.16.13] ident=danny) by cs.huji.ac.il with esmtp (Exim 3.20 #1) id 14MGas-00056U-00 for freebsd-stable@FreeBSD.ORG; Fri, 26 Jan 2001 23:39:42 +0200 X-Mailer: exmh version 2.2 06/23/2000 with nmh-0.24 To: freebsd-stable@FreeBSD.ORG Subject: 2 make |!2 make ... Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 26 Jan 2001 23:39:42 +0200 From: Danny Braniss Message-Id: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi, in /usr/src, while make buildworld works fine, a plain make runs along but chokes on pam_ssh.so, it's missing -lssh. i can fix this by going (cd secure; make), and then again make. is there a better way? oh, i need the make to write in /usr/src, not /usr/obj, im testing vinum. danny To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 26 13:54: 9 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 EA72337B699 for ; Fri, 26 Jan 2001 13:53:48 -0800 (PST) Received: (from kris@localhost) by citusc17.usc.edu (8.11.1/8.11.1) id f0QLv5f85523; Fri, 26 Jan 2001 13:57:05 -0800 (PST) (envelope-from kris) Date: Fri, 26 Jan 2001 13:57:05 -0800 From: Kris Kennaway To: Danny Braniss Cc: freebsd-stable@FreeBSD.ORG Subject: Re: 2 make |!2 make ... Message-ID: <20010126135705.A85472@citusc17.usc.edu> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="PNTmBPCT7hxwcZjr" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from danny@cs.huji.ac.il on Fri, Jan 26, 2001 at 11:39:42PM +0200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --PNTmBPCT7hxwcZjr Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jan 26, 2001 at 11:39:42PM +0200, Danny Braniss wrote: > hi, > in /usr/src, while make buildworld works fine, a plain make runs along > but chokes on pam_ssh.so, it's missing -lssh. i can fix this by going > (cd secure; make), and then again make. is there a better way? > oh, i need the make to write in /usr/src, not /usr/obj, im testing vinum. I don't understand..this should already be built before libpam by buildworld. Are you sure you don't have NOSECURE or NOCRYPT set in your /etc/make.conf, or evironment? Kris --=20 NOTE: To fetch an updated copy of my GPG key which has not expired, finger kris@FreeBSD.org --PNTmBPCT7hxwcZjr 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 iD8DBQE6cfKxWry0BWjoQKURArXmAJ4hVyAPURR6m/gmxE4RalJO2y/n/ACfWlUT uxXtNZGJIfY7m6QtZdmkXQU= =N3hW -----END PGP SIGNATURE----- --PNTmBPCT7hxwcZjr-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 26 14:19:30 2001 Delivered-To: freebsd-stable@freebsd.org Received: from eagle.prod.itd.earthlink.net (eagle.prod.itd.earthlink.net [207.217.120.24]) by hub.freebsd.org (Postfix) with ESMTP id 9383F37B402 for ; Fri, 26 Jan 2001 14:19:12 -0800 (PST) Received: from dionysos.yi.org (1Cust78.tnt3.phoenix.az.da.uu.net [63.14.194.78]) by eagle.prod.itd.earthlink.net (8.9.3-EL_1_3/8.9.3) with ESMTP id OAA19504 for ; Fri, 26 Jan 2001 14:19:11 -0800 (PST) Received: by dionysos.yi.org (Postfix, from userid 1001) id 997E01C57; Fri, 26 Jan 2001 15:17:48 -0700 (MST) Date: Fri, 26 Jan 2001 15:17:48 -0700 From: Dionysos To: freebsd-stable@freebsd.org Subject: Buildworld failure using two disks Message-ID: <20010126151748.A1958@dionysos.yi.org> Reply-To: james@m-a.net Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, Using the latest -stable source I get an error at the beginning of the build only when I have /usr/obj mounted on a separate physical disk. I used to be able to build across two disks a couple months ago on another machine but not so far on this one in the past week or so. When I do have /usr/obj on the same disk, it runs fine. Nonetheless, the performance benefits of building across disks gives me hope that there's some solution to this. Following is the log and a df. -------------------------------------------------------------- >>> 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 ln: /usr/obj/usr/src/i386/sys: Operation not supported *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. and a df output Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/ad6s1a 198399 30033 152495 16% / /dev/ad6s1f 7184492 1032671 5577062 16% /usr /dev/ad6s1e 198399 2465 180063 1% /var procfs 4 4 0 100% /proc /dev/ad0s4 1745465 31 1745434 0% /usr/obj TIA, James To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 26 17:13:21 2001 Delivered-To: freebsd-stable@freebsd.org Received: from tao.ca (tao.ca [198.96.117.188]) by hub.freebsd.org (Postfix) with ESMTP id 2748637B401 for ; Fri, 26 Jan 2001 17:12:50 -0800 (PST) Received: (from anarcat@localhost) by tao.ca (Collective/TAO6) id f0R1Cm702090; Fri, 26 Jan 2001 20:12:48 -0500 Date: Fri, 26 Jan 2001 20:12:48 -0500 From: anarcat To: freebsd-stable@freebsd.org Cc: anarcat Subject: Can't build kernel under stable-2000.12.31 Message-ID: <20010126201248.A1832@dojo.tao.ca> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="O5XBE6gyVG5Rl6Rj" Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --O5XBE6gyVG5Rl6Rj Content-Type: multipart/mixed; boundary="YZ5djTAD1cGYuMQK" Content-Disposition: inline --YZ5djTAD1cGYuMQK Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi! (please CC: me, I'm not on the list) Building a custom kernel under freebsd-stable (cvsup'd and made world on=20 2000-12-31) fails with the following, any idea why? shall# make KERNEL=3DSHALL buildkernel installkernel =2E.. =3D=3D=3D> wi @ -> /usr/src/sys machine -> /usr/src/sys/i386/include perl @/kern/makedevops.pl -h @/kern/device_if.m perl @/kern/makedevops.pl -h @/kern/bus_if.m rm -f .depend mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -I- -I. -I@=20 -I@/../include -I/usr/obj/usr/src/i386/usr/include =20 /usr/src/sys/modules/wi/../../i386/isa/if_wi.c cd /usr/obj/usr/src/sys/SHALL; MAKEOBJDIRPREFIX=3D/usr/obj =20 COMPILER_PATH=3D/usr/obj/usr/src/i386/usr/libexec:/usr/obj/usr/src/i386/usr= /bin =20 LIBRARY_PATH=3D/usr/obj/usr/src/i386/usr/lib:/usr/obj/usr/src/i386/usr/lib = =20 OBJFORMAT_PATH=3D/usr/obj/usr/src/i386/usr/libexec =20 PERL5LIB=3D/usr/obj/usr/src/i386/usr/libdata/perl/5.00503 =20 DESTDIR=3D/usr/obj/usr/src/i386 INSTALL=3D"sh /usr/src/tools/install.sh" = =20 PATH=3D/usr/obj/usr/src/i386/usr/sbin:/usr/obj/usr/src/i386/usr/bin:/usr/ob= j/usr/src/i386/usr/games:/sbin:/bin:/usr/sbin:/usr/bin=20 MACHINE=3Di386 make KERNEL=3Dkernel all cc -c -x assembler-with-cpp -DLOCORE -O -Wall -Wredundant-decls=20 -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith= =20 -Winline -Wcast-qual -fformat-extensions -ansi -g -nostdinc -I- -I.=20 -I/usr/src/sys -I/usr/src/sys/../include -D_KERNEL -include opt_global.h= =20 -elf -mpreferred-stack-boundary=3D2 /usr/src/sys/i386/i386/locore.s /tmp/ccO18745.s: Assembler messages: /tmp/ccO18745.s:1744: Error: .space specifies non-absolute value /tmp/ccO18745.s:2455: Error: undefined symbol L0 in operation setting=20 PTmap /tmp/ccO18745.s:2455: Error: undefined symbol PDRSHIFT in operation=20 setting PTmap /tmp/ccO18745.s:1712: Error: undefined symbol L0 in operation /tmp/ccO18745.s:1712: Error: undefined symbol PAGE_SIZE in operation /tmp/ccO18745.s:1713: Error: undefined symbol L0 in operation /tmp/ccO18745.s:1713: Error: undefined symbol PDESIZE in operation /tmp/ccO18745.s:2455: Error: undefined symbol L0 in operation setting=20 APTmap /tmp/ccO18745.s:2455: Error: undefined symbol PDRSHIFT in operation=20 setting APTmap /tmp/ccO18745.s:1721: Error: undefined symbol L0 in operation /tmp/ccO18745.s:1721: Error: undefined symbol PAGE_SIZE in operation /tmp/ccO18745.s:1722: Error: undefined symbol L0 in operation /tmp/ccO18745.s:1722: Error: undefined symbol PDESIZE in operation /tmp/ccO18745.s:1928: Error: undefined symbol UPAGES in operation /tmp/ccO18745.s:1928: Error: undefined symbol PAGE_SIZE in operation /tmp/ccO18745.s:2316: Error: undefined symbol BI_ESYMTAB in operation /tmp/ccO18745.s:2321: Error: undefined symbol BI_SYMTAB in operation /tmp/ccO18745.s:2322: Error: undefined symbol BI_ESYMTAB in operation /tmp/ccO18745.s:2326: Error: undefined symbol BI_KERNEND in operation /tmp/ccO18745.s:2338: Error: undefined symbol PAGE_SIZE in operation /tmp/ccO18745.s:2338: Error: undefined symbol PAGE_SIZE in operation /tmp/ccO18745.s:2342: Error: undefined symbol PAGE_SIZE in operation /tmp/ccO18745.s:2342: Error: undefined symbol PAGE_SIZE in operation /tmp/ccO18745.s:2346: Error: undefined symbol UPAGES in operation /tmp/ccO18745.s:2346: Error: undefined symbol PAGE_SIZE in operation /tmp/ccO18745.s:2346: Error: undefined symbol UPAGES in operation /tmp/ccO18745.s:2346: Error: undefined symbol PAGE_SIZE in operation /tmp/ccO18745.s:2351: Error: undefined symbol PAGE_SIZE in operation /tmp/ccO18745.s:2351: Error: undefined symbol PAGE_SIZE in operation /tmp/ccO18745.s:2354: Error: undefined symbol PAGE_SIZE in operation /tmp/ccO18745.s:2354: Error: undefined symbol PAGE_SIZE in operation /tmp/ccO18745.s:2411: Error: undefined symbol PAGE_SHIFT in operation /tmp/ccO18745.s:2427: Error: undefined symbol PAGE_SHIFT in operation /tmp/ccO18745.s:2428: Error: undefined symbol PAGE_SHIFT in operation /tmp/ccO18745.s:1854: Error: Subtraction of two symbols in different=20 sections ".tmpstk" {.data section} - "KERNBASE" {*UND* section} at file=20 address 28. /tmp/ccO18745.s:1877: Error: Subtraction of two symbols in different=20 sections "end" {*UND* section} - "KERNBASE" {*UND* section} at file=20 address 38. /tmp/ccO18745.s:1878: Error: Subtraction of two symbols in different=20 sections "edata" {*UND* section} - "KERNBASE" {*UND* section} at file=20 address 43. /tmp/ccO18745.s:1890: Error: Subtraction of two symbols in different=20 sections "cpu_feature" {.data section} - "KERNBASE" {*UND* section} at=20 file address 61. /tmp/ccO18745.s:1906: Error: Subtraction of two symbols in different=20 sections "IdlePTD" {.data section} - "KERNBASE" {*UND* section} at file=20 address 81. /tmp/ccO18745.s:2115: Error: Subtraction of two symbols in different=20 sections "kernelname" {*UND* section} - "KERNBASE" {*UND* section} at file= =20 address 371. /tmp/ccO18745.s:2143: Error: Subtraction of two symbols in different=20 sections "bootinfo" {.data section} - "KERNBASE" {*UND* section} at file=20 address 411. /tmp/ccO18745.s:2163: Error: Subtraction of two symbols in different=20 sections "boothowto" {*UND* section} - "KERNBASE" {*UND* section} at file= =20 address 435. /tmp/ccO18745.s:2165: Error: Subtraction of two symbols in different=20 sections "bootdev" {*UND* section} - "KERNBASE" {*UND* section} at file=20 address 443. /tmp/ccO18745.s:2203: Error: Subtraction of two symbols in different=20 sections "cpu" {.data section} - "KERNBASE" {*UND* section} at file=20 address 495. /tmp/ccO18745.s:2208: Error: Subtraction of two symbols in different=20 sections "cpu" {.data section} - "KERNBASE" {*UND* section} at file=20 address 511. /tmp/ccO18745.s:2209: Error: Subtraction of two symbols in different=20 sections "cpu_vendor" {.data section} - "KERNBASE" {*UND* section} at file= =20 address 521. /tmp/ccO18745.s:2210: Error: Subtraction of two symbols in different=20 sections "cpu_vendor" {.data section} - "KERNBASE" {*UND* section} at file= =20 address 531. /tmp/ccO18745.s:2211: Error: Subtraction of two symbols in different=20 sections "cpu_vendor" {.data section} - "KERNBASE" {*UND* section} at file= =20 address 541. /tmp/ccO18745.s:2212: Error: Subtraction of two symbols in different=20 sections "cpu_vendor" {.data section} - "KERNBASE" {*UND* section} at file= =20 address 551. /tmp/ccO18745.s:2231: Error: Subtraction of two symbols in different=20 sections "cpu" {.data section} - "KERNBASE" {*UND* section} at file=20 address 592. /tmp/ccO18745.s:2258: Error: Subtraction of two symbols in different=20 sections "cpu_vendor" {.data section} - "KERNBASE" {*UND* section} at file= =20 address 627. /tmp/ccO18745.s:2259: Error: Subtraction of two symbols in different=20 sections "cpu_vendor" {.data section} - "KERNBASE" {*UND* section} at file= =20 address 637. /tmp/ccO18745.s:2260: Error: Subtraction of two symbols in different=20 sections "cpu_vendor" {.data section} - "KERNBASE" {*UND* section} at file= =20 address 647. /tmp/ccO18745.s:2266: Error: Subtraction of two symbols in different=20 sections "cpu_high" {.data section} - "KERNBASE" {*UND* section} at file=20 address 662. /tmp/ccO18745.s:2267: Error: Subtraction of two symbols in different=20 sections "cpu_vendor" {.data section} - "KERNBASE" {*UND* section} at file= =20 address 668. /tmp/ccO18745.s:2268: Error: Subtraction of two symbols in different=20 sections "cpu_vendor" {.data section} - "KERNBASE" {*UND* section} at file= =20 address 674. /tmp/ccO18745.s:2269: Error: Subtraction of two symbols in different=20 sections "cpu_vendor" {.data section} - "KERNBASE" {*UND* section} at file= =20 address 680. /tmp/ccO18745.s:2270: Error: Subtraction of two symbols in different=20 sections "cpu_vendor" {.data section} - "KERNBASE" {*UND* section} at file= =20 address 686. /tmp/ccO18745.s:2274: Error: Subtraction of two symbols in different=20 sections "cpu_id" {.data section} - "KERNBASE" {*UND* section} at file=20 address 699. /tmp/ccO18745.s:2275: Error: Subtraction of two symbols in different=20 sections "cpu_feature" {.data section} - "KERNBASE" {*UND* section} at=20 file address 705. /tmp/ccO18745.s:2282: Error: Subtraction of two symbols in different=20 sections "cpu" {.data section} - "KERNBASE" {*UND* section} at file=20 address 722. /tmp/ccO18745.s:2288: Error: Subtraction of two symbols in different=20 sections "cpu" {.data section} - "KERNBASE" {*UND* section} at file=20 address 739. /tmp/ccO18745.s:2292: Error: Subtraction of two symbols in different=20 sections "cpu" {.data section} - "KERNBASE" {*UND* section} at file=20 address 751. /tmp/ccO18745.s:2305: Error: Subtraction of two symbols in different=20 sections "cpu_feature" {.data section} - "KERNBASE" {*UND* section} at=20 file address 762. /tmp/ccO18745.s:2313: Error: Subtraction of two symbols in different=20 sections "end" {*UND* section} - "KERNBASE" {*UND* section} at file=20 address 784. /tmp/ccO18745.s:2316: Error: Negative of non-absolute symbol KERNBASE /tmp/ccO18745.s:2321: Error: Negative of non-absolute symbol KERNBASE /tmp/ccO18745.s:2322: Error: Negative of non-absolute symbol KERNBASE /tmp/ccO18745.s:2326: Error: Negative of non-absolute symbol KERNBASE /tmp/ccO18745.s:2334: Error: Subtraction of two symbols in different=20 sections ".data" {.data section} - "KERNBASE" {*UND* section} at file=20 address 843. /tmp/ccO18745.s:2335: Error: Subtraction of two symbols in different=20 sections ".data" {.data section} - "KERNBASE" {*UND* section} at file=20 address 849. /tmp/ccO18745.s:2338: Error: Subtraction of two symbols in different=20 sections ".data" {.data section} - "KERNBASE" {*UND* section} at file=20 address 855. /tmp/ccO18745.s:2338: Error: Subtraction of two symbols in different=20 sections ".data" {.data section} - "KERNBASE" {*UND* section} at file=20 address 867. /tmp/ccO18745.s:2339: Error: Subtraction of two symbols in different=20 sections ".data" {.data section} - "KERNBASE" {*UND* section} at file=20 address 885. /tmp/ccO18745.s:2342: Error: Subtraction of two symbols in different=20 sections ".data" {.data section} - "KERNBASE" {*UND* section} at file=20 address 891. /tmp/ccO18745.s:2342: Error: Subtraction of two symbols in different=20 sections ".data" {.data section} - "KERNBASE" {*UND* section} at file=20 address 903. /tmp/ccO18745.s:2343: Error: Subtraction of two symbols in different=20 sections "IdlePTD" {.data section} - "KERNBASE" {*UND* section} at file=20 address 921. /tmp/ccO18745.s:2346: Error: Subtraction of two symbols in different=20 sections ".data" {.data section} - "KERNBASE" {*UND* section} at file=20 address 927. /tmp/ccO18745.s:2346: Error: Subtraction of two symbols in different=20 sections ".data" {.data section} - "KERNBASE" {*UND* section} at file=20 address 939. /tmp/ccO18745.s:2347: Error: Subtraction of two symbols in different=20 sections ".data" {.data section} - "KERNBASE" {*UND* section} at file=20 address 957. /tmp/ccO18745.s:2349: Error: Subtraction of two symbols in different=20 sections "proc0paddr" {.data section} - "KERNBASE" {*UND* section} at file= =20 address 969. /tmp/ccO18745.s:2351: Error: Subtraction of two symbols in different=20 sections ".data" {.data section} - "KERNBASE" {*UND* section} at file=20 address 975. /tmp/ccO18745.s:2351: Error: Subtraction of two symbols in different=20 sections ".data" {.data section} - "KERNBASE" {*UND* section} at file=20 address 987. /tmp/ccO18745.s:2352: Error: Subtraction of two symbols in different=20 sections ".data" {.data section} - "KERNBASE" {*UND* section} at file=20 address 1005. /tmp/ccO18745.s:2354: Error: Subtraction of two symbols in different=20 sections ".data" {.data section} - "KERNBASE" {*UND* section} at file=20 address 1011. /tmp/ccO18745.s:2354: Error: Subtraction of two symbols in different=20 sections ".data" {.data section} - "KERNBASE" {*UND* section} at file=20 address 1023. /tmp/ccO18745.s:2355: Error: Subtraction of two symbols in different=20 sections "vm86pa" {.data section} - "KERNBASE" {*UND* section} at file=20 address 1041. /tmp/ccO18745.s:2357: Error: Subtraction of two symbols in different=20 sections "vm86paddr" {.data section} - "KERNBASE" {*UND* section} at file= =20 address 1053. /tmp/ccO18745.s:2372: Error: Subtraction of two symbols in different=20 sections "cpu_feature" {.data section} - "KERNBASE" {*UND* section} at=20 file address 1063. /tmp/ccO18745.s:2377: Error: Subtraction of two symbols in different=20 sections "etext" {*UND* section} - "KERNBASE" {*UND* section} at file=20 address 1080. /tmp/ccO18745.s:2380: Error: Subtraction of two symbols in different=20 sections ".data" {.data section} - "KERNBASE" {*UND* section} at file=20 address 1103. /tmp/ccO18745.s:2383: Error: Subtraction of two symbols in different=20 sections "etext" {*UND* section} - "KERNBASE" {*UND* section} at file=20 address 1125. /tmp/ccO18745.s:2389: Error: Subtraction of two symbols in different=20 sections "cpu_feature" {.data section} - "KERNBASE" {*UND* section} at=20 file address 1146. /tmp/ccO18745.s:2394: Error: Subtraction of two symbols in different=20 sections ".data" {.data section} - "KERNBASE" {*UND* section} at file=20 address 1164. /tmp/ccO18745.s:2397: Error: Subtraction of two symbols in different=20 sections ".data" {.data section} - "KERNBASE" {*UND* section} at file=20 address 1183. /tmp/ccO18745.s:2400: Error: Subtraction of two symbols in different=20 sections "IdlePTD" {.data section} - "KERNBASE" {*UND* section} at file=20 address 1205. /tmp/ccO18745.s:2402: Error: Subtraction of two symbols in different=20 sections ".data" {.data section} - "KERNBASE" {*UND* section} at file=20 address 1224. /tmp/ccO18745.s:2405: Error: Subtraction of two symbols in different=20 sections ".data" {.data section} - "KERNBASE" {*UND* section} at file=20 address 1247. /tmp/ccO18745.s:2407: Error: Subtraction of two symbols in different=20 sections ".data" {.data section} - "KERNBASE" {*UND* section} at file=20 address 1266. /tmp/ccO18745.s:2412: Error: Subtraction of two symbols in different=20 sections ".data" {.data section} - "KERNBASE" {*UND* section} at file=20 address 1308. /tmp/ccO18745.s:2415: Error: Subtraction of two symbols in different=20 sections ".data" {.data section} - "KERNBASE" {*UND* section} at file=20 address 1331. /tmp/ccO18745.s:2417: Error: Subtraction of two symbols in different=20 sections ".data" {.data section} - "KERNBASE" {*UND* section} at file=20 address 1350. /tmp/ccO18745.s:2423: Error: Subtraction of two symbols in different=20 sections "vm86pa" {.data section} - "KERNBASE" {*UND* section} at file=20 address 1392. /tmp/ccO18745.s:2429: Error: Subtraction of two symbols in different=20 sections "vm86pa" {.data section} - "KERNBASE" {*UND* section} at file=20 address 1434. /tmp/ccO18745.s:2435: Error: Subtraction of two symbols in different=20 sections ".data" {.data section} - "KERNBASE" {*UND* section} at file=20 address 1457. /tmp/ccO18745.s:2438: Error: Subtraction of two symbols in different=20 sections "IdlePTD" {.data section} - "KERNBASE" {*UND* section} at file=20 address 1473. /tmp/ccO18745.s:2441: Error: Subtraction of two symbols in different=20 sections ".data" {.data section} - "KERNBASE" {*UND* section} at file=20 address 1496. /tmp/ccO18745.s:2444: Error: Subtraction of two symbols in different=20 sections "IdlePTD" {.data section} - "KERNBASE" {*UND* section} at file=20 address 1515. /tmp/ccO18745.s:2447: Error: Subtraction of two symbols in different=20 sections "IdlePTD" {.data section} - "KERNBASE" {*UND* section} at file=20 address 1538. /tmp/ccO18745.s:2450: Error: Subtraction of two symbols in different=20 sections "IdlePTD" {.data section} - "KERNBASE" {*UND* section} at file=20 address 1557. *** Error code 1 Stop in /u/obj/usr/src/sys/SHALL. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. shall#=20 --YZ5djTAD1cGYuMQK Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=SHALL Content-Transfer-Encoding: quoted-printable ######################################################################## # # S H A L L # ######################################################################## # CPU & kernel options ident SHALL maxusers 32 machine i386 cpu I586_CPU #Pentium MMX options CPU_FASTER_5X86_FPU #Faster FPU exception handler # FPU onboard, do not need this #options MATH_EMULATE #Support for x87 emulation ##################################################################### # DEBUGGING OPTIONS options DDB # Enable the kernel debugger. # # Don't drop into DDB for a panic. Intended for unattended operation # where you may want to drop to DDB from the console, but still want # the machine to recover from a panic # #options DDB_UNATTENDED # It's important to put this back on makeoptions DEBUG=3D-g #Build kernel with gdb(1) debug symbols ######################################################################## # Compatibility options options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores ######################################################################## # Networking options options INET #InterNETworking #options INET6 #IPv6 communications protocols options ICMP_BANDLIM #Rate limit bad replies #options NETGRAPH #netgraph(4) system #options NETGRAPH_PPPOE #options NETGRAPH_SOCKET # 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 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 ######################################################################## # Filesystem options options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep this!] options SOFTUPDATES #Enable FFS soft updates support #options MFS #Memory Filesystem #options MD_ROOT #MD is a potential root device options MSDOSFS #MSDOS Filesystem options CD9660 #ISO 9660 Filesystem options CD9660_ROOT #CD-ROM usable as root, CD9660 required options PROCFS #Process filesystem options QUOTA #Enable disk quotas #options NFS #Network Filesystem #options NFS_ROOT #NFS usable as root device, NFS required #options NFS_NOSERVER #Disable the NFS server code ######################################################################## # POSIX P1003.1B options P1003_1B #Posix P1003_1B real-time extensions options _KPOSIX_PRIORITY_SCHEDULING ######################################################################## # SCSI device configuration options SCSI_DELAY=3D2000 #Delay (in ms) before probing SCSI # SCSI Controllers device ahc # AHA2940 and onboard AIC7xxx devices # 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) device pt #Scanner ######################################################################## # Miscellaneous devices and options pseudo-device pty # Pseudo-ttys (telnet etc) pseudo-device md # Memory "disks" 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 ######################################################################## # Hardware device configuration device isa device eisa device pci # 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 KBD_INSTALL_CDEV # install a CDEV entry in /dev # syscons is the default console driver, resembling an SCO console device sc0 at isa? flags 0x100 # Enable this and PCVT_FREEBSD for pcvt vt220 compatible console driver #device vt0 at isa? #options XSERVER # support for X server on a vt console #options FAT_CURSOR # start with block cursor # If you have a ThinkPAD, uncomment this along with the rest of the PCVT li= nes #options PCVT_SCANSET=3D2 # IBM keyboards are non-std # splash screen/screen saver pseudo-device splash # Floating point support - do not disable. device npx0 at nexus? port IO_NPX irq 13 # 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 #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 # 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 # Power management support (see LINT for more options) device apm0 at nexus? disable flags 0x20 # Advanced Power Management # Serial (COM) ports device sio0 at isa? port IO_COM1 flags 0x10 irq 4 device sio1 at isa? port IO_COM2 irq 3 device sio2 at isa? port IO_COM3 irq 12 #device sio3 at isa? disable port IO_COM4 irq 9 # 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 #device vpo # Requires scbus and da #controller pnp0 # Why has this disappeared in 4.x? # ISA el'cheapo NIC=20 #ep0: <3Com 3C509-TPO EtherLink III> at port 0x200-0x20f irq 5 on isa0 #ep0: Ethernet address 00:10:5a:aa:51:33 device ep ######################################################################## # Sound devices device pcm device sbc # at isa? port 0x220 irq 10 drq 1 flags 0x15 #device snd0 #device sb0 at isa? port 0x220 irq 9 drq 3 #device sbxvi0 at isa? drq 7 #device sbmidi0 at isa? port 0x300 #device awe0 at isa? port 0x620 device speaker device pca0 at isa? port IO_TIMER1 device joy0 at isa? port IO_GAME #this conflicts with NIC ######################################################################## # USB Support device uhci #device ohci device usb #USB bus #device ugen #Generic --YZ5djTAD1cGYuMQK-- --O5XBE6gyVG5Rl6Rj Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.0 (GNU/Linux) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjpyII4ACgkQ7uV99pHLOSJuRgCguY/Ukx41xuRGvlLp//JwTSld 93cAnj61r3OJAl1aLLe51l6q8v3Pb+sj =1w3x -----END PGP SIGNATURE----- --O5XBE6gyVG5Rl6Rj-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 26 17:15: 2 2001 Delivered-To: freebsd-stable@freebsd.org Received: from usagi.cts.com (usagi.cts.com [209.68.192.66]) by hub.freebsd.org (Postfix) with ESMTP id BD7B837B6A2 for ; Fri, 26 Jan 2001 17:14:44 -0800 (PST) Received: from golf.cts.com (golf.cts.com [205.163.23.102]) by usagi.cts.com (8.9.3/8.9.3) with ESMTP id RAA29603 for ; Fri, 26 Jan 2001 17:14:44 -0800 (PST) Received: from ctsd2 (ctsd2.cts.com [205.163.23.182]) by golf.cts.com (8.11.1/8.11.1) with SMTP id f0R1Ei354952 for ; Fri, 26 Jan 2001 17:14:44 -0800 (PST) (envelope-from mdavis@cts.com) From: "Morgan Davis" To: Subject: don't know how to make linux_file.c Date: Fri, 26 Jan 2001 17:14:44 -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) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This happened yesterday and today after doing a cvsup of RELENG_4 from cvsup2.freebsd.org. Compiling GENERIC is failing: ===> linux make: don't know how to make /usr/src/sys/modules/linux/../../i386/linux/linux_file.c. Stop *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error Advise? --Morgan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 26 18:59:39 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 6016B37B698 for ; Fri, 26 Jan 2001 18:59:14 -0800 (PST) Received: (qmail 4977 invoked by uid 0); 27 Jan 2001 02:59:12 -0000 Received: from unknown (HELO urx.com) (206.159.132.160) by mail.urx.com with SMTP; 27 Jan 2001 02:59:12 -0000 Message-ID: <3A723980.DEDEE04E@urx.com> Date: Fri, 26 Jan 2001 18:59:12 -0800 From: Kent Stewart Reply-To: kstewart@urx.com Organization: Dynacom X-Mailer: Mozilla 4.75 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: anarcat Cc: freebsd-stable@freebsd.org Subject: Re: Can't build kernel under stable-2000.12.31 References: <20010126201248.A1832@dojo.tao.ca> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG anarcat wrote: > > Hi! > > (please CC: me, I'm not on the list) > > Building a custom kernel under freebsd-stable (cvsup'd and made world on > 2000-12-31) fails with the following, any idea why? This error usually occurs beause you didn't do a buildworld to populate /usr/obj first. Read /usr/src/UPDATING because the sequence isn't an option. If you already have a current userland, then the choice can include the config method. They way it looks, you mixed your world's and that doesn't work. Kent > > shall# make KERNEL=SHALL buildkernel installkernel > ... > ===> wi > @ -> /usr/src/sys > machine -> /usr/src/sys/i386/include > perl @/kern/makedevops.pl -h @/kern/device_if.m > perl @/kern/makedevops.pl -h @/kern/bus_if.m > rm -f .depend > mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -I- -I. -I@ > -I@/../include -I/usr/obj/usr/src/i386/usr/include > /usr/src/sys/modules/wi/../../i386/isa/if_wi.c > cd /usr/obj/usr/src/sys/SHALL; MAKEOBJDIRPREFIX=/usr/obj > COMPILER_PATH=/usr/obj/usr/src/i386/usr/libexec:/usr/obj/usr/src/i386/usr/bin > LIBRARY_PATH=/usr/obj/usr/src/i386/usr/lib:/usr/obj/usr/src/i386/usr/lib > OBJFORMAT_PATH=/usr/obj/usr/src/i386/usr/libexec > PERL5LIB=/usr/obj/usr/src/i386/usr/libdata/perl/5.00503 > DESTDIR=/usr/obj/usr/src/i386 INSTALL="sh /usr/src/tools/install.sh" > 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 > MACHINE=i386 make KERNEL=kernel all > cc -c -x assembler-with-cpp -DLOCORE -O -Wall -Wredundant-decls > -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith > -Winline -Wcast-qual -fformat-extensions -ansi -g -nostdinc -I- -I. > -I/usr/src/sys -I/usr/src/sys/../include -D_KERNEL -include opt_global.h > -elf -mpreferred-stack-boundary=2 /usr/src/sys/i386/i386/locore.s > /tmp/ccO18745.s: Assembler messages: > /tmp/ccO18745.s:1744: Error: .space specifies non-absolute value > /tmp/ccO18745.s:2455: Error: undefined symbol L0 in operation setting > PTmap > /tmp/ccO18745.s:2455: Error: undefined symbol PDRSHIFT in operation > setting PTmap > /tmp/ccO18745.s:1712: Error: undefined symbol L0 in operation > /tmp/ccO18745.s:1712: Error: undefined symbol PAGE_SIZE in operation > /tmp/ccO18745.s:1713: Error: undefined symbol L0 in operation > /tmp/ccO18745.s:1713: Error: undefined symbol PDESIZE in operation > /tmp/ccO18745.s:2455: Error: undefined symbol L0 in operation setting > APTmap > /tmp/ccO18745.s:2455: Error: undefined symbol PDRSHIFT in operation > setting APTmap > /tmp/ccO18745.s:1721: Error: undefined symbol L0 in operation > /tmp/ccO18745.s:1721: Error: undefined symbol PAGE_SIZE in operation > /tmp/ccO18745.s:1722: Error: undefined symbol L0 in operation > /tmp/ccO18745.s:1722: Error: undefined symbol PDESIZE in operation > /tmp/ccO18745.s:1928: Error: undefined symbol UPAGES in operation > /tmp/ccO18745.s:1928: Error: undefined symbol PAGE_SIZE in operation > /tmp/ccO18745.s:2316: Error: undefined symbol BI_ESYMTAB in operation > /tmp/ccO18745.s:2321: Error: undefined symbol BI_SYMTAB in operation > /tmp/ccO18745.s:2322: Error: undefined symbol BI_ESYMTAB in operation > /tmp/ccO18745.s:2326: Error: undefined symbol BI_KERNEND in operation > /tmp/ccO18745.s:2338: Error: undefined symbol PAGE_SIZE in operation > /tmp/ccO18745.s:2338: Error: undefined symbol PAGE_SIZE in operation > /tmp/ccO18745.s:2342: Error: undefined symbol PAGE_SIZE in operation > /tmp/ccO18745.s:2342: Error: undefined symbol PAGE_SIZE in operation > /tmp/ccO18745.s:2346: Error: undefined symbol UPAGES in operation > /tmp/ccO18745.s:2346: Error: undefined symbol PAGE_SIZE in operation > /tmp/ccO18745.s:2346: Error: undefined symbol UPAGES in operation > /tmp/ccO18745.s:2346: Error: undefined symbol PAGE_SIZE in operation > /tmp/ccO18745.s:2351: Error: undefined symbol PAGE_SIZE in operation > /tmp/ccO18745.s:2351: Error: undefined symbol PAGE_SIZE in operation > /tmp/ccO18745.s:2354: Error: undefined symbol PAGE_SIZE in operation > /tmp/ccO18745.s:2354: Error: undefined symbol PAGE_SIZE in operation > /tmp/ccO18745.s:2411: Error: undefined symbol PAGE_SHIFT in operation > /tmp/ccO18745.s:2427: Error: undefined symbol PAGE_SHIFT in operation > /tmp/ccO18745.s:2428: Error: undefined symbol PAGE_SHIFT in operation > /tmp/ccO18745.s:1854: Error: Subtraction of two symbols in different > sections ".tmpstk" {.data section} - "KERNBASE" {*UND* section} at file > address 28. > /tmp/ccO18745.s:1877: Error: Subtraction of two symbols in different > sections "end" {*UND* section} - "KERNBASE" {*UND* section} at file > address 38. > /tmp/ccO18745.s:1878: Error: Subtraction of two symbols in different > sections "edata" {*UND* section} - "KERNBASE" {*UND* section} at file > address 43. > /tmp/ccO18745.s:1890: Error: Subtraction of two symbols in different > sections "cpu_feature" {.data section} - "KERNBASE" {*UND* section} at > file address 61. > /tmp/ccO18745.s:1906: Error: Subtraction of two symbols in different > sections "IdlePTD" {.data section} - "KERNBASE" {*UND* section} at file > address 81. > /tmp/ccO18745.s:2115: Error: Subtraction of two symbols in different > sections "kernelname" {*UND* section} - "KERNBASE" {*UND* section} at file > address 371. > /tmp/ccO18745.s:2143: Error: Subtraction of two symbols in different > sections "bootinfo" {.data section} - "KERNBASE" {*UND* section} at file > address 411. > /tmp/ccO18745.s:2163: Error: Subtraction of two symbols in different > sections "boothowto" {*UND* section} - "KERNBASE" {*UND* section} at file > address 435. > /tmp/ccO18745.s:2165: Error: Subtraction of two symbols in different > sections "bootdev" {*UND* section} - "KERNBASE" {*UND* section} at file > address 443. > /tmp/ccO18745.s:2203: Error: Subtraction of two symbols in different > sections "cpu" {.data section} - "KERNBASE" {*UND* section} at file > address 495. > /tmp/ccO18745.s:2208: Error: Subtraction of two symbols in different > sections "cpu" {.data section} - "KERNBASE" {*UND* section} at file > address 511. > /tmp/ccO18745.s:2209: Error: Subtraction of two symbols in different > sections "cpu_vendor" {.data section} - "KERNBASE" {*UND* section} at file > address 521. > /tmp/ccO18745.s:2210: Error: Subtraction of two symbols in different > sections "cpu_vendor" {.data section} - "KERNBASE" {*UND* section} at file > address 531. > /tmp/ccO18745.s:2211: Error: Subtraction of two symbols in different > sections "cpu_vendor" {.data section} - "KERNBASE" {*UND* section} at file > address 541. > /tmp/ccO18745.s:2212: Error: Subtraction of two symbols in different > sections "cpu_vendor" {.data section} - "KERNBASE" {*UND* section} at file > address 551. > /tmp/ccO18745.s:2231: Error: Subtraction of two symbols in different > sections "cpu" {.data section} - "KERNBASE" {*UND* section} at file > address 592. > /tmp/ccO18745.s:2258: Error: Subtraction of two symbols in different > sections "cpu_vendor" {.data section} - "KERNBASE" {*UND* section} at file > address 627. > /tmp/ccO18745.s:2259: Error: Subtraction of two symbols in different > sections "cpu_vendor" {.data section} - "KERNBASE" {*UND* section} at file > address 637. > /tmp/ccO18745.s:2260: Error: Subtraction of two symbols in different > sections "cpu_vendor" {.data section} - "KERNBASE" {*UND* section} at file > address 647. > /tmp/ccO18745.s:2266: Error: Subtraction of two symbols in different > sections "cpu_high" {.data section} - "KERNBASE" {*UND* section} at file > address 662. > /tmp/ccO18745.s:2267: Error: Subtraction of two symbols in different > sections "cpu_vendor" {.data section} - "KERNBASE" {*UND* section} at file > address 668. > /tmp/ccO18745.s:2268: Error: Subtraction of two symbols in different > sections "cpu_vendor" {.data section} - "KERNBASE" {*UND* section} at file > address 674. > /tmp/ccO18745.s:2269: Error: Subtraction of two symbols in different > sections "cpu_vendor" {.data section} - "KERNBASE" {*UND* section} at file > address 680. > /tmp/ccO18745.s:2270: Error: Subtraction of two symbols in different > sections "cpu_vendor" {.data section} - "KERNBASE" {*UND* section} at file > address 686. > /tmp/ccO18745.s:2274: Error: Subtraction of two symbols in different > sections "cpu_id" {.data section} - "KERNBASE" {*UND* section} at file > address 699. > /tmp/ccO18745.s:2275: Error: Subtraction of two symbols in different > sections "cpu_feature" {.data section} - "KERNBASE" {*UND* section} at > file address 705. > /tmp/ccO18745.s:2282: Error: Subtraction of two symbols in different > sections "cpu" {.data section} - "KERNBASE" {*UND* section} at file > address 722. > /tmp/ccO18745.s:2288: Error: Subtraction of two symbols in different > sections "cpu" {.data section} - "KERNBASE" {*UND* section} at file > address 739. > /tmp/ccO18745.s:2292: Error: Subtraction of two symbols in different > sections "cpu" {.data section} - "KERNBASE" {*UND* section} at file > address 751. > /tmp/ccO18745.s:2305: Error: Subtraction of two symbols in different > sections "cpu_feature" {.data section} - "KERNBASE" {*UND* section} at > file address 762. > /tmp/ccO18745.s:2313: Error: Subtraction of two symbols in different > sections "end" {*UND* section} - "KERNBASE" {*UND* section} at file > address 784. > /tmp/ccO18745.s:2316: Error: Negative of non-absolute symbol KERNBASE > /tmp/ccO18745.s:2321: Error: Negative of non-absolute symbol KERNBASE > /tmp/ccO18745.s:2322: Error: Negative of non-absolute symbol KERNBASE > /tmp/ccO18745.s:2326: Error: Negative of non-absolute symbol KERNBASE > /tmp/ccO18745.s:2334: Error: Subtraction of two symbols in different > sections ".data" {.data section} - "KERNBASE" {*UND* section} at file > address 843. > /tmp/ccO18745.s:2335: Error: Subtraction of two symbols in different > sections ".data" {.data section} - "KERNBASE" {*UND* section} at file > address 849. > /tmp/ccO18745.s:2338: Error: Subtraction of two symbols in different > sections ".data" {.data section} - "KERNBASE" {*UND* section} at file > address 855. > /tmp/ccO18745.s:2338: Error: Subtraction of two symbols in different > sections ".data" {.data section} - "KERNBASE" {*UND* section} at file > address 867. > /tmp/ccO18745.s:2339: Error: Subtraction of two symbols in different > sections ".data" {.data section} - "KERNBASE" {*UND* section} at file > address 885. > /tmp/ccO18745.s:2342: Error: Subtraction of two symbols in different > sections ".data" {.data section} - "KERNBASE" {*UND* section} at file > address 891. > /tmp/ccO18745.s:2342: Error: Subtraction of two symbols in different > sections ".data" {.data section} - "KERNBASE" {*UND* section} at file > address 903. > /tmp/ccO18745.s:2343: Error: Subtraction of two symbols in different > sections "IdlePTD" {.data section} - "KERNBASE" {*UND* section} at file > address 921. > /tmp/ccO18745.s:2346: Error: Subtraction of two symbols in different > sections ".data" {.data section} - "KERNBASE" {*UND* section} at file > address 927. > /tmp/ccO18745.s:2346: Error: Subtraction of two symbols in different > sections ".data" {.data section} - "KERNBASE" {*UND* section} at file > address 939. > /tmp/ccO18745.s:2347: Error: Subtraction of two symbols in different > sections ".data" {.data section} - "KERNBASE" {*UND* section} at file > address 957. > /tmp/ccO18745.s:2349: Error: Subtraction of two symbols in different > sections "proc0paddr" {.data section} - "KERNBASE" {*UND* section} at file > address 969. > /tmp/ccO18745.s:2351: Error: Subtraction of two symbols in different > sections ".data" {.data section} - "KERNBASE" {*UND* section} at file > address 975. > /tmp/ccO18745.s:2351: Error: Subtraction of two symbols in different > sections ".data" {.data section} - "KERNBASE" {*UND* section} at file > address 987. > /tmp/ccO18745.s:2352: Error: Subtraction of two symbols in different > sections ".data" {.data section} - "KERNBASE" {*UND* section} at file > address 1005. > /tmp/ccO18745.s:2354: Error: Subtraction of two symbols in different > sections ".data" {.data section} - "KERNBASE" {*UND* section} at file > address 1011. > /tmp/ccO18745.s:2354: Error: Subtraction of two symbols in different > sections ".data" {.data section} - "KERNBASE" {*UND* section} at file > address 1023. > /tmp/ccO18745.s:2355: Error: Subtraction of two symbols in different > sections "vm86pa" {.data section} - "KERNBASE" {*UND* section} at file > address 1041. > /tmp/ccO18745.s:2357: Error: Subtraction of two symbols in different > sections "vm86paddr" {.data section} - "KERNBASE" {*UND* section} at file > address 1053. > /tmp/ccO18745.s:2372: Error: Subtraction of two symbols in different > sections "cpu_feature" {.data section} - "KERNBASE" {*UND* section} at > file address 1063. > /tmp/ccO18745.s:2377: Error: Subtraction of two symbols in different > sections "etext" {*UND* section} - "KERNBASE" {*UND* section} at file > address 1080. > /tmp/ccO18745.s:2380: Error: Subtraction of two symbols in different > sections ".data" {.data section} - "KERNBASE" {*UND* section} at file > address 1103. > /tmp/ccO18745.s:2383: Error: Subtraction of two symbols in different > sections "etext" {*UND* section} - "KERNBASE" {*UND* section} at file > address 1125. > /tmp/ccO18745.s:2389: Error: Subtraction of two symbols in different > sections "cpu_feature" {.data section} - "KERNBASE" {*UND* section} at > file address 1146. > /tmp/ccO18745.s:2394: Error: Subtraction of two symbols in different > sections ".data" {.data section} - "KERNBASE" {*UND* section} at file > address 1164. > /tmp/ccO18745.s:2397: Error: Subtraction of two symbols in different > sections ".data" {.data section} - "KERNBASE" {*UND* section} at file > address 1183. > /tmp/ccO18745.s:2400: Error: Subtraction of two symbols in different > sections "IdlePTD" {.data section} - "KERNBASE" {*UND* section} at file > address 1205. > /tmp/ccO18745.s:2402: Error: Subtraction of two symbols in different > sections ".data" {.data section} - "KERNBASE" {*UND* section} at file > address 1224. > /tmp/ccO18745.s:2405: Error: Subtraction of two symbols in different > sections ".data" {.data section} - "KERNBASE" {*UND* section} at file > address 1247. > /tmp/ccO18745.s:2407: Error: Subtraction of two symbols in different > sections ".data" {.data section} - "KERNBASE" {*UND* section} at file > address 1266. > /tmp/ccO18745.s:2412: Error: Subtraction of two symbols in different > sections ".data" {.data section} - "KERNBASE" {*UND* section} at file > address 1308. > /tmp/ccO18745.s:2415: Error: Subtraction of two symbols in different > sections ".data" {.data section} - "KERNBASE" {*UND* section} at file > address 1331. > /tmp/ccO18745.s:2417: Error: Subtraction of two symbols in different > sections ".data" {.data section} - "KERNBASE" {*UND* section} at file > address 1350. > /tmp/ccO18745.s:2423: Error: Subtraction of two symbols in different > sections "vm86pa" {.data section} - "KERNBASE" {*UND* section} at file > address 1392. > /tmp/ccO18745.s:2429: Error: Subtraction of two symbols in different > sections "vm86pa" {.data section} - "KERNBASE" {*UND* section} at file > address 1434. > /tmp/ccO18745.s:2435: Error: Subtraction of two symbols in different > sections ".data" {.data section} - "KERNBASE" {*UND* section} at file > address 1457. > /tmp/ccO18745.s:2438: Error: Subtraction of two symbols in different > sections "IdlePTD" {.data section} - "KERNBASE" {*UND* section} at file > address 1473. > /tmp/ccO18745.s:2441: Error: Subtraction of two symbols in different > sections ".data" {.data section} - "KERNBASE" {*UND* section} at file > address 1496. > /tmp/ccO18745.s:2444: Error: Subtraction of two symbols in different > sections "IdlePTD" {.data section} - "KERNBASE" {*UND* section} at file > address 1515. > /tmp/ccO18745.s:2447: Error: Subtraction of two symbols in different > sections "IdlePTD" {.data section} - "KERNBASE" {*UND* section} at file > address 1538. > /tmp/ccO18745.s:2450: Error: Subtraction of two symbols in different > sections "IdlePTD" {.data section} - "KERNBASE" {*UND* section} at file > address 1557. > *** Error code 1 > > Stop in /u/obj/usr/src/sys/SHALL. > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > > Stop in /usr/src. > shall# > > ---------------------------------------------------------------------- > Name: SHALL > SHALL Type: Plain Text (text/plain) > Encoding: quoted-printable > > Part 1.2Type: application/pgp-signature -- Kent Stewart Richland, WA mailto:kstewart@3-cities.com http://kstewart.urx.com/kstewart/index.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 26 19:59:33 2001 Delivered-To: freebsd-stable@freebsd.org Received: from obsecurity.org (adsl-64-165-226-71.dsl.lsan03.pacbell.net [64.165.226.71]) by hub.freebsd.org (Postfix) with ESMTP id 5705437B400 for ; Fri, 26 Jan 2001 19:59:16 -0800 (PST) Received: by obsecurity.org (Postfix, from userid 1000) id 4FA6ABA4C0; Fri, 26 Jan 2001 19:59:46 -0800 (PST) Date: Fri, 26 Jan 2001 19:59:45 -0800 From: Kris Kennaway To: Morgan Davis Cc: freebsd-stable@FreeBSD.ORG Subject: Re: don't know how to make linux_file.c Message-ID: <20010126195945.A52838@xor.obsecurity.org> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="fUYQa+Pmc3FrFX/N" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from mdavis@cts.com on Fri, Jan 26, 2001 at 05:14:44PM -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --fUYQa+Pmc3FrFX/N Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Fri, Jan 26, 2001 at 05:14:44PM -0800, Morgan Davis wrote: > This happened yesterday and today after doing a cvsup of RELENG_4 from > cvsup2.freebsd.org. Compiling GENERIC is failing: What commands did you use to build the kernel? Kris --fUYQa+Pmc3FrFX/N 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 iD8DBQE6ckexWry0BWjoQKURAmKMAJwKIz+I+pwvqIv/S4nhv6kl0JppbQCg0X+7 oa3FMekwmSzrtVFgoFOq6jw= =kha+ -----END PGP SIGNATURE----- --fUYQa+Pmc3FrFX/N-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 26 20: 1:29 2001 Delivered-To: freebsd-stable@freebsd.org Received: from obsecurity.org (adsl-64-165-226-71.dsl.lsan03.pacbell.net [64.165.226.71]) by hub.freebsd.org (Postfix) with ESMTP id 2CB5A37B400 for ; Fri, 26 Jan 2001 20:01:08 -0800 (PST) Received: by obsecurity.org (Postfix, from userid 1000) id 4F3B7BA4C0; Fri, 26 Jan 2001 20:01:38 -0800 (PST) Date: Fri, 26 Jan 2001 20:01:38 -0800 From: Kris Kennaway To: james@m-a.net Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Buildworld failure using two disks Message-ID: <20010126200138.B52838@xor.obsecurity.org> References: <20010126151748.A1958@dionysos.yi.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="V0207lvV8h4k8FAm" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010126151748.A1958@dionysos.yi.org>; from dionysos@dionysos.yi.org on Fri, Jan 26, 2001 at 03:17:48PM -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --V0207lvV8h4k8FAm Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Fri, Jan 26, 2001 at 03:17:48PM -0700, Dionysos wrote: > Hi all, > Using the latest -stable source I get an error at the beginning of > the build only when I have /usr/obj mounted on a separate physical > disk. It should work. Try blowing away /usr/obj. Kris --V0207lvV8h4k8FAm 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 iD8DBQE6ckghWry0BWjoQKURAlnhAJ4oIl2zvnFOib1+Zd7NrDDGfdp/lgCgmxeU BdANP6Sx2TIjBrlpwN02YzE= =ZkKf -----END PGP SIGNATURE----- --V0207lvV8h4k8FAm-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 26 20: 2:11 2001 Delivered-To: freebsd-stable@freebsd.org Received: from clmboh1-smtp3.columbus.rr.com (unknown [65.24.0.112]) by hub.freebsd.org (Postfix) with ESMTP id 0959B37B401 for ; Fri, 26 Jan 2001 20:01:54 -0800 (PST) Received: from mail.iowna.com (dhcp065-024-023-038.columbus.rr.com [65.24.23.38]) by clmboh1-smtp3.columbus.rr.com (8.11.2/8.11.2) with ESMTP id f0R3xWr20429 for ; Fri, 26 Jan 2001 22:59:33 -0500 (EST) Message-ID: <3A72474D.979B84FA@mail.iowna.com> Date: Fri, 26 Jan 2001 22:58:05 -0500 From: Bill Moran X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.2-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: stable@freebsd.org Subject: Problems with BIND in 4.2-STABLE (resource leak?) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm having trouble with BIND in 4.2-STABLE (Jan 18 22:16:33) I'm running the version of BIND that installs by default (named -v reports 8.2.3-T6B) This machine is a firewall/email/web server. The DNS is currently running as a local cache - although I have a reverse lookup file to resolve the private IPs on the network. Here's what's happening. On startup a listing in "top" shows named using around 5M of memory and minimal processor usage. Under normal circumstances this doesn't seem to vary much. However, occasionally (I have yet to find out what triggers this) named will go psycho. CPU utilization will max out and the size of the process will bloat up to 15M. When this happens a "kill -HUP" will bring the CPU usage back to a sane level, but the program remains bloated to 15M. All the while, named seems to be answering queries just fine. A slowdown is noticable when the processor usage is maxed out, however. Has anyone else seen this, or have I got some unique problem here? Currently I have a cronjob doing a "killall -HUP named" every 6 hours which is at least keeping the CPU usage sane, and the machine has enough RAM that the 15M usage doesn't cripple it in the slightest. This behavious makes me nervious, however, and I'd like to resolve it as quickly as possible. I asked about this on -questions and got no response, so I'm starting to wonder if nobody else has seen this. Any information, including a "me too" would be helpful. If you'd like more data on the hardware type or details of the config, just ask. -Bill Moran To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 26 21:25: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 F2DCC37B401 for ; Fri, 26 Jan 2001 21:25:16 -0800 (PST) Received: (from root@localhost) by cage.simianscience.com (8.11.1/8.11.1) id f0R5PBI67960 for stable@freebsd.org; Sat, 27 Jan 2001 00:25: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 f0R5P5d67952 for ; Sat, 27 Jan 2001 00:25:05 -0500 (EST) (envelope-from mike@sentex.net) Message-Id: <4.2.2.20010127001841.03015358@marble.sentex.net> X-Sender: mdtancsa@marble.sentex.net X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Sat, 27 Jan 2001 00:25:04 -0500 To: stable@freebsd.org From: Mike Tancsa Subject: more strange DNS issues in BIND and STABLE. 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 Ok, here is a domain I cant figure out why BIND behaves differently from before. Jan 27 00:12:17 marble named[166]: Lame server on 'moody.edu' (in 'moody.edu'?): [131.103.1.101].53 'SECONDARY.DNS.IAGNET.NET' One of its authoritative servers is LAME, but the other is not. If bind happens to pick the LAME one first, why does it not try the other server listed ? Its like he gives up on the first try. This did not seem to be the behaviour before no ? marble# nslookup Default Server: ns2.sentex.ca Address: 199.212.134.2 > set type=ns > moody.edu. Server: ns2.sentex.ca Address: 199.212.134.2 Non-authoritative answer: moody.edu nameserver = SECONDARY.DNS.IAGNET.NET moody.edu nameserver = MBIGATE.moody.edu Authoritative answers can be found from: SECONDARY.DNS.IAGNET.NET internet address = 131.103.1.101 MBIGATE.moody.edu internet address = 206.68.228.41 > lserver 131.103.1.101 Default Server: [131.103.1.101] Address: 131.103.1.101 > moody.edu. Server: [131.103.1.101] Address: 131.103.1.101 Non-authoritative answer: moody.edu nameserver = SECONDARY.DNS.IAGNET.NET moody.edu nameserver = MBIGATE.moody.edu Authoritative answers can be found from: SECONDARY.DNS.IAGNET.NET internet address = 131.103.1.101 MBIGATE.moody.edu internet address = 206.68.228.41 > lserver mbigate.moody.edu Default Server: mbigate.moody.edu Address: 206.68.228.41 > moody.edu. Server: mbigate.moody.edu Address: 206.68.228.41 moody.edu nameserver = X.ns.verio.net moody.edu nameserver = mbigate.moody.edu moody.edu nameserver = S.ns.verio.net moody.edu nameserver = Y.ns.verio.net Y.ns.verio.net internet address = 129.250.35.251 S.ns.verio.net internet address = 192.67.14.15 mbigate.moody.edu internet address = 206.68.228.41 X.ns.verio.net internet address = 129.250.35.250 > -------------------------------------------------------------------- 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 Fri Jan 26 22:10: 2 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail.kconline.com (kconline.com [216.241.132.2]) by hub.freebsd.org (Postfix) with ESMTP id 33C3D37B401 for ; Fri, 26 Jan 2001 22:09:41 -0800 (PST) Received: from barsoom (barsoom.kconline.com [216.241.133.19]) by mail.kconline.com (8.11.1/8.11.1) with SMTP id f0R69YH20093; Sat, 27 Jan 2001 01:09:34 -0500 (EST) (envelope-from mikea@kconline.com) Message-ID: <034601c08827$b8e08d80$1385f1d8@kconline.com> From: "Mike Atkinson" To: References: <4.2.2.20010127001841.03015358@marble.sentex.net> Subject: Re: more strange DNS issues in BIND and STABLE. Date: Sat, 27 Jan 2001 01:09:34 -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 Just as a follow up on this thread, we are seeing the same behavior with the moody.edu domain and currently have thousands of pieces of undeliverable mail in our mailqueue and are rejecting similar numbers of incoming mails for them and others. We realized before seeing this and similar threads that the problem is due to lame servers but we do not have the resources to knock the rest of these morons into line; complaints from our users are becoming quite vocal. We've also discovered that Cable & Wireless is not responding authoritatively on quite a few domains that they are secondary for. Fortunately they are still responding authoritatively on our primary domains but not on about half of our virtual hosts. We've reverted to an earlier version of named which seems to have at least reduced the problem to an intermittent one instead of continuous failure to resolve (as far as Sendmail was concerned.) Before reverting to the earlier version of named we also had periods when none of our nameservers could resolve certain locally popular websites (ones that have no nameservers responding authoritatively.) We would be willing to let these improperly configured sites wither and die if only we had some external reference to point people at instead of it being our word against theirs. It is too bad that the 1996 resolution to unlist domains with non-authoritative nameservers never made it into reality.. ----- Mike Atkinson - mikea@kconline.com KC Online, Inc. - System Administration ----- ----- Original Message ----- From: "Mike Tancsa" To: Sent: Saturday, January 27, 2001 12:25 AM Subject: more strange DNS issues in BIND and STABLE. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 26 22:38:33 2001 Delivered-To: freebsd-stable@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 1A49637B401 for ; Fri, 26 Jan 2001 22:38:16 -0800 (PST) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id XAA47049; Fri, 26 Jan 2001 23:38:13 -0700 (MST) (envelope-from ken) Date: Fri, 26 Jan 2001 23:38:13 -0700 From: "Kenneth D. Merry" To: Hank Marquardt Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Dying disk ... Message-ID: <20010126233813.A46986@panzer.kdm.org> References: <20010125150722.A288@oscar2.yerpso.net> <20010125174624.A37036@panzer.kdm.org> <20010125203946.A53543@hermes.yerpso.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20010125203946.A53543@hermes.yerpso.net>; from hmarq@yerpso.net on Thu, Jan 25, 2001 at 08:39:47PM -0600 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 25, 2001 at 20:39:47 -0600, Hank Marquardt wrote: > Thanks, heat is an interesting thought ... it's a dual P133 machine in > fairly close quarters (inside the case); though it was running solid > for close to 30 days before the first lockup (4.2 Stable update/boot > around 12/15) and another couple months before that with no issues -- > further, the dmesg I originally sent was from less than 15 minutes > running after having been powered off for over 24 hours -- I don't > think I'd get a heat problem that quick unless something was seriously > screwed up -- of which there was no evidence when I opened the case. > > The drive is a Segate ST19171W attached to a 2940 card -- CD also SCSI > has functioned and been recognized throughout all the episodes. That disk isn't known for any particularly bad behavior, IIRC. So your disk may indeed be on its way out. I'd suggest getting a new one, that way you aren't up a creek if it does finally croak. If it doesn't, you've got some extra disk space. :) Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 26 22:59:58 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 DAD3B37B401 for ; Fri, 26 Jan 2001 22:59:41 -0800 (PST) Received: from [203.164.12.28] by www.quake.com.au (NTMail 4.30.0012/AH9370.63.d1acf55c) with ESMTP id hnwsaaaa for ; Sat, 27 Jan 2001 18:08:17 +1100 Message-ID: <3A7271EB.360D9954@quake.com.au> Date: Sat, 27 Jan 2001 17:59:55 +1100 From: Kal Torak X-Mailer: Mozilla 4.73 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Pete French Cc: simond@irrelevant.org, stable@FreeBSD.ORG Subject: Re: anybody seen this one ? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Pete French wrote: > > > I had this problem too a while back, I fixed it for myself at the time > > by removing the flags 0x1 from the atkbd0 entry in the kernel config file, > > this can also be done via boot -c and similar, I then managed to fix it > > Sadly even boot -c doesnt work - that just goes into a loop scrolling > 'config." up the screen blurringly fast. I have now disabled just about > everuthing I can in the BIOS, time too try reflashing it with anewer version > I guess. That sounds like a good idea... But for me I found this is usually related to the USB settings... If the new bios doesnt work you may need to make/get a custom install kernel... Good Luck! Kal. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 26 23: 6:57 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 1633737B401 for ; Fri, 26 Jan 2001 23:06:37 -0800 (PST) Received: from [203.164.12.28] by www.quake.com.au (NTMail 4.30.0012/AH9370.63.d1acf55c) with ESMTP id jnwsaaaa for ; Sat, 27 Jan 2001 18:15:14 +1100 Message-ID: <3A72738C.CDB9A9F4@quake.com.au> Date: Sat, 27 Jan 2001 18:06:52 +1100 From: Kal Torak X-Mailer: Mozilla 4.73 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: David Wagner Cc: =?iso-8859-1?Q?Jo=E3o?= Fernandes , stable@FreeBSD.ORG Subject: Re: Network stops working References: Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David Wagner wrote: > > On Fri, 26 Jan 2001, João Fernandes wrote: > > > I have a realtek 8139 and a cable modem. I use DHCP to connect to the network > > and my /etc/dhclient.conf has nothing on it. > > > > My problems are: > > The speed of my connections are way slower in FreeBSD than are > > in windows; To the extent of downloading at 2 kps when in windows I > > would download the same file from the same site at 70kps. > > Well, I have a theory, because I had somewhat similar behavior. Some > cable modem + nic combinations have trouble autdetecting the line speed. > Try forcing your connection to 10BaseT half duplex (which is almost > guaranteed to be what the cable modem supports). Example: > > % ifconfig rl0 media 10baseT/UTP > > This managed to triple my connection speed in most cases... Yeah this most defiantly sounds like an incorrect media or duplex setting... I wouldnt use the NIC the cable company gave you since its most probably a pile of crap... They basically never have any hardware features, and I have had them just die on me of there own will... The reason it probably works in windows, is because you have the driver from the cable company installed for it with the correct settings set... Anyway Good Luck! Kal. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 26 23:25: 7 2001 Delivered-To: freebsd-stable@freebsd.org Received: from usagi.cts.com (usagi.cts.com [209.68.192.66]) by hub.freebsd.org (Postfix) with ESMTP id 3116F37B404 for ; Fri, 26 Jan 2001 23:24:50 -0800 (PST) Received: from io.cts.com (io.cts.com [198.68.174.34]) by usagi.cts.com (8.9.3/8.9.3) with ESMTP id XAA07084; Fri, 26 Jan 2001 23:24:49 -0800 (PST) Received: from orion.cts.com (orion.cts.com [216.120.25.39]) by io.cts.com (8.11.1/8.11.1) with ESMTP id f0R7Omq54443; Fri, 26 Jan 2001 23:24:48 -0800 (PST) (envelope-from mdavis@cts.com) Message-Id: <5.1.0.6.0.20010126232241.00b1e9e0@golf.cts.com> X-Sender: mdavis@golf.cts.com (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 5.1.0.6 (Beta) Date: Fri, 26 Jan 2001 23:24:54 -0800 To: Kris Kennaway From: Morgan Davis Subject: Re: don't know how to make linux_file.c Cc: freebsd-stable@freebsd.org In-Reply-To: <20010126195945.A52838@xor.obsecurity.org> 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 Kris, The problem turned out to be some old remnant bits. After trying for two days to figure out what could be the problem, I decided to wipe /usr/src, /usr/sup, and /usr/obj. Then I did a cvsup and buildworld. After that making GENERIC worked perfectly no errors. --Morgan At 07:59 PM 1/26/2001 -0800, you wrote: >On Fri, Jan 26, 2001 at 05:14:44PM -0800, Morgan Davis wrote: > > This happened yesterday and today after doing a cvsup of RELENG_4 from > > cvsup2.freebsd.org. Compiling GENERIC is failing: > >What commands did you use to build the kernel? > >Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 26 23:54:41 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 9333B37B401 for ; Fri, 26 Jan 2001 23:54:21 -0800 (PST) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #2) id 14MQBg-0001QW-00; Sat, 27 Jan 2001 07:54:20 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.11.1/8.11.1) id f0R7uFl09606; Sat, 27 Jan 2001 08:56:15 +0100 (CET) (envelope-from wkb) Date: Sat, 27 Jan 2001 08:56:15 +0100 From: Wilko Bulte To: Kris Kennaway Cc: james@m-a.net, freebsd-stable@freebsd.org Subject: Re: Buildworld failure using two disks Message-ID: <20010127085615.A9048@freebie.demon.nl> References: <20010126151748.A1958@dionysos.yi.org> <20010126200138.B52838@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20010126200138.B52838@xor.obsecurity.org>; from kris@obsecurity.org on Fri, Jan 26, 2001 at 08:01:38PM -0800 X-OS: FreeBSD 4.2-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jan 26, 2001 at 08:01:38PM -0800, Kris Kennaway wrote: > On Fri, Jan 26, 2001 at 03:17:48PM -0700, Dionysos wrote: > > Hi all, > > > Using the latest -stable source I get an error at the beginning of > > the build only when I have /usr/obj mounted on a separate physical > > disk. > > It should work. Try blowing away /usr/obj. I does work. I built -stable on a config like that last week. W/ -- | / o / / _ Arnhem, The Netherlands email: wilko@freebsd.org |/|/ / / /( (_) Bulte http://www.freebsd.org http://www.nlfug.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jan 27 0:36:35 2001 Delivered-To: freebsd-stable@freebsd.org Received: from netcabo.pt (unknown [212.113.161.137]) by hub.freebsd.org (Postfix) with ESMTP id B3AAD37B6A0 for ; Sat, 27 Jan 2001 00:36:18 -0800 (PST) Received: from OpsyDopsy.net.dhis.org ([213.22.2.137]) by netcabo.pt with Microsoft SMTPSVC(5.5.1877.537.53); Sat, 27 Jan 2001 08:34:49 +0000 From: =?iso-8859-1?q?Jo=E3o=20Fernandes?= To: stable@freebsd.org Subject: Re: Network stops working Date: Sat, 27 Jan 2001 08:38:08 +0000 X-Mailer: KMail [version 1.1.99] Content-Type: text/plain; charset="iso-8859-1" MIME-Version: 1.0 Message-Id: <01012708380800.22959@OpsyDopsy.net.dhis.org> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks you all for all your help in my problem. It's fixed. I had to force the 10baseT/UTP half-duplex connection and allow some icmp packages. Joao Fernandes To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jan 27 0:56: 3 2001 Delivered-To: freebsd-stable@freebsd.org Received: from hummingbird.prod.itd.earthlink.net (hummingbird.prod.itd.earthlink.net [207.217.120.125]) by hub.freebsd.org (Postfix) with ESMTP id 82A8C37B6B0 for ; Sat, 27 Jan 2001 00:55:45 -0800 (PST) Received: from dionysos.yi.org (1Cust136.tnt3.phoenix.az.da.uu.net [63.14.194.136]) by hummingbird.prod.itd.earthlink.net (8.9.3-EL_1_3/8.9.3) with ESMTP id AAA20444; Sat, 27 Jan 2001 00:54:44 -0800 (PST) Received: by dionysos.yi.org (Postfix, from userid 1001) id 714D91C56; Sat, 27 Jan 2001 01:53:22 -0700 (MST) Date: Sat, 27 Jan 2001 01:53:22 -0700 From: Dionysos To: Wilko Bulte Cc: Kris Kennaway , james@m-a.net, freebsd-stable@freebsd.org Subject: Re: Buildworld failure using two disks Message-ID: <20010127015322.A679@dionysos.yi.org> Reply-To: james@m-a.net References: <20010126151748.A1958@dionysos.yi.org> <20010126200138.B52838@xor.obsecurity.org> <20010127085615.A9048@freebie.demon.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010127085615.A9048@freebie.demon.nl>; from wkb@freebie.demon.nl on Sat, Jan 27, 2001 at 08:56:15AM +0100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Jan 27, 2001 at 08:56:15AM +0100, Wilko Bulte wrote: > On Fri, Jan 26, 2001 at 08:01:38PM -0800, Kris Kennaway wrote: > > On Fri, Jan 26, 2001 at 03:17:48PM -0700, Dionysos wrote: > > > Hi all, > > > > > Using the latest -stable source I get an error at the beginning of > > > the build only when I have /usr/obj mounted on a separate physical > > > disk. > > > > It should work. Try blowing away /usr/obj. > > I does work. I built -stable on a config like that last week. > You'll get no argument from me that it should work, but further attempts (even after cleaning out /usr/obj) continue to fail. On a hunch, I went ahead and compiled and installed the latest version of ln, but it continues to be unable to make a symbolic link across disks. For now, it's not a serious issue for me to simply make world using the one disk only, but I'd still appreciate suggestions as to what I could even look at with regard to fixing this since it seems to be some kind of issue beyond the ln command itself. James To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jan 27 1: 2:22 2001 Delivered-To: freebsd-stable@freebsd.org Received: from lucifer.ninth-circle.org (lucifer.bart.nl [194.158.168.74]) by hub.freebsd.org (Postfix) with ESMTP id 8BD9637B6B1 for ; Sat, 27 Jan 2001 01:02:04 -0800 (PST) Received: (from asmodai@localhost) by lucifer.ninth-circle.org (8.11.1/8.11.0) id f0R920r52098; Sat, 27 Jan 2001 10:02:00 +0100 (CET) (envelope-from asmodai) Date: Sat, 27 Jan 2001 10:02:00 +0100 From: Jeroen Ruigrok van der Werven To: Bill Moran Cc: stable@FreeBSD.ORG Subject: Re: Problems with BIND in 4.2-STABLE (resource leak?) Message-ID: <20010127100200.B51681@lucifer.bart.nl> References: <3A72474D.979B84FA@mail.iowna.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3A72474D.979B84FA@mail.iowna.com>; from wmoran@mail.iowna.com on Fri, Jan 26, 2001 at 10:58:05PM -0500 Organisation: VIA Net.Works The Netherlands Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -On [20010127 05:05], Bill Moran (wmoran@mail.iowna.com) wrote: >I'm having trouble with BIND in 4.2-STABLE (Jan 18 22:16:33) >I'm running the version of BIND that installs by default (named -v >reports 8.2.3-T6B) [snip RAM problem] >Has anyone else seen this, or have I got some unique problem here? There were a fair amount of bugs in 8.2.3 betas. I am in the progress of preparing the import, and importing 8.2.3, which is the released version. As soon as I have it imported in CURRENT, and after I have done my usual round of testing in STABLE I will MFC it. -- Jeroen Ruigrok van der Werven VIA Net.Works The Netherlands BSD: Technical excellence at its best Network- and systemadministrator D78D D0AD 244D 1D12 C9CA 7152 035C 1138 546A B867 Misery loves company... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jan 27 2:36:23 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 212FB37B69C for ; Sat, 27 Jan 2001 02:36:06 -0800 (PST) Received: (from daemon@localhost) by point.osg.gov.bc.ca (8.8.7/8.8.8) id CAA16092; Sat, 27 Jan 2001 02:35:30 -0800 Received: from passer.osg.gov.bc.ca(142.32.110.29) via SMTP by point.osg.gov.bc.ca, id smtpda16090; Sat Jan 27 02:35:15 2001 Received: (from uucp@localhost) by passer.osg.gov.bc.ca (8.11.2/8.9.1) id f0RAZ9p01657; Sat, 27 Jan 2001 02:35:09 -0800 (PST) Received: from cwsys9.cwsent.com(10.2.2.1), claiming to be "cwsys.cwsent.com" via SMTP by passer9.cwsent.com, id smtpdxg1652; Sat Jan 27 02:34:55 2001 Received: (from uucp@localhost) by cwsys.cwsent.com (8.11.2/8.9.1) id f0RAYs453785; Sat, 27 Jan 2001 02:34:54 -0800 (PST) Message-Id: <200101271034.f0RAYs453785@cwsys.cwsent.com> Received: from localhost.cwsent.com(127.0.0.1), claiming to be "cwsys" via SMTP by localhost.cwsent.com, id smtpdd53780; Sat Jan 27 02:34:09 2001 X-Mailer: exmh version 2.3.1 01/18/2001 with nmh-1.0.4 Reply-To: Cy Schubert - ITSD Open Systems Group From: Cy Schubert - ITSD Open Systems Group X-Sender: schubert To: Jeroen Ruigrok van der Werven Cc: Bill Moran , stable@FreeBSD.ORG Subject: Re: Problems with BIND in 4.2-STABLE (resource leak?) In-reply-to: Your message of "Sat, 27 Jan 2001 10:02:00 +0100." <20010127100200.B51681@lucifer.bart.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 27 Jan 2001 02:34:08 -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20010127100200.B51681@lucifer.bart.nl>, Jeroen Ruigrok van der Werv en writes: > -On [20010127 05:05], Bill Moran (wmoran@mail.iowna.com) wrote: > >I'm having trouble with BIND in 4.2-STABLE (Jan 18 22:16:33) > >I'm running the version of BIND that installs by default (named -v > >reports 8.2.3-T6B) > > [snip RAM problem] > > >Has anyone else seen this, or have I got some unique problem here? > > There were a fair amount of bugs in 8.2.3 betas. > > I am in the progress of preparing the import, and importing 8.2.3, which > is the released version. As soon as I have it imported in CURRENT, and > after I have done my usual round of testing in STABLE I will MFC it. Do we know when BIND9 might be imported into -CURRENT? 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 Sat Jan 27 3:20:53 2001 Delivered-To: freebsd-stable@freebsd.org Received: from sender.ngi.de (sender.ngi.de [212.79.47.18]) by hub.freebsd.org (Postfix) with ESMTP id 9DF8C37B401; Sat, 27 Jan 2001 03:20:35 -0800 (PST) Received: from Gatekeeper.FreeBSD.org (koln-3e3664d6.pool.mediaWays.net [62.54.100.214]) by sender.ngi.de (Postfix) with ESMTP id 35D8796D45; Sat, 27 Jan 2001 12:08:10 +0100 (CET) Received: from StefanEsser.FreeBSD.org (StefanEsser [10.0.0.1]) by Gatekeeper.FreeBSD.org (Postfix) with ESMTP id 858C534; Sat, 27 Jan 2001 11:52:19 +0100 (CET) Received: by StefanEsser.FreeBSD.org (Postfix, from userid 200) id D7D851478; Sat, 27 Jan 2001 11:55:10 +0100 (CET) Date: Sat, 27 Jan 2001 11:55:10 +0100 From: Stefan Esser To: Forrest Aldrich Cc: freebsd-stable@FreeBSD.ORG, Stefan Esser Subject: Re: Interscan Viruswall for Linux.... on FreeBSD-4.x Message-ID: <20010127115510.A1581@StefanEsser.FreeBSD.org> Reply-To: Stefan Esser References: <5.0.2.1.2.20010124225607.00a59380@216.67.14.69> 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.20010124225607.00a59380@216.67.14.69>; from forrie@forrie.com on Wed, Jan 24, 2001 at 10:59:13PM -0500 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 2001-01-24 22:59 -0500, Forrest Aldrich wrote: > I would like to hear from anyone who is successfully using Interscan > Viruswall for Linux on FreeBSD, under Linux emulation (via the linux_base > port). I ordered the Solaris version and received a single CD-ROM that installs on all supported platforms (Unix and Win32). At first, I didn't find the distribution files for Solaris (the box came with NT docs, but I checked with the vendor, that I received a licence that is valid on Solaris). To my surprise, the Linux version on that media was 3.6, while the Solaris version was still at 3.5! Anyway, I tried the Linux version on a 4.2-STABLE box, just to compare the performance to that of our productive system, and found that the Linux version works just fine. > It seems this should work with ease; however, TrendMicro refuses to > disclose what "configuration adjustments" need to be made, citing that it's > not "officially supported" (ie: some of their programs have hard coded path > requirements, which they've been notified about from others who use this on > FreeBSD). Well, if you know about rc files and are not afraid to use symbolic links between file systems, all should be well ;-) I even considered creating a FreeBSD port, that installs VirusWall from a CD-ROM ... My trial period is over, but I have not yet de-installed the software from my test box, so I may help get you started, in case you find any problems. My only nit is, that you can't bind VirusWall to a single interface. My firewall architecture requires strictly independent configurations for incoming and outgoing messages. For that reason, I have separate instances of VirusWall for either direction, and it required some magic to get all the parts working together on a single box. Regards, STefan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jan 27 4: 0:17 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mailsrv.otenet.gr (mailsrv.otenet.gr [195.170.0.5]) by hub.freebsd.org (Postfix) with ESMTP id CE12637B400 for ; Sat, 27 Jan 2001 03:59:58 -0800 (PST) Received: from hades.hell.gr (root@patr530-b019.otenet.gr [195.167.121.147]) by mailsrv.otenet.gr (8.11.1/8.11.1) with ESMTP id f0RBxlK17656; Sat, 27 Jan 2001 13:59:48 +0200 (EET) Received: (from charon@localhost) by hades.hell.gr (8.11.1/8.11.1) id f0RARYD49513; Sat, 27 Jan 2001 12:27:34 +0200 (EET) Date: Sat, 27 Jan 2001 12:27:33 +0200 From: Giorgos Keramidas To: Josef Karthauser Cc: Warner Losh , Matt Heckaman , Shawn Barnhart , freebsd-stable@FreeBSD.ORG Subject: Re: Limit on the number of disklabel entries? Message-ID: <20010127122733.C49085@hades.hell.gr> References: <200101212233.f0LMXVs03655@billy-club.village.org> <20010121235644.A29517@tao.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <20010121235644.A29517@tao.org.uk>; from joe@tao.org.uk on Sun, Jan 21, 2001 at 11:56:44PM +0000 X-PGP-Fingerprint: 3A 75 52 EB F1 58 56 0D - C5 B8 21 B6 1B 5E 4A C2 X-URL: http://students.ceid.upatras.gr/~keramida/index.html Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jan 21, 2001 at 11:56:44PM +0000, Josef Karthauser wrote: > On Sun, Jan 21, 2001 at 03:33:31PM -0700, Warner Losh wrote: > > In message Matt Heckaman writes: > > : Brand new system, installed 3 days ago, 4.2-RELEASE. Creating the > > : partition on the newly sliced da1 via sysinstall put it on "e". > > > > 'e' is the first slice that sysinstall uses. Since you wanted the > > whole disk, it gave you the whole disk as 'e'. Nothing magical about > > it. 'c' being the whole disk *IS* magical. > > Does 'c' include the disklabel itself, and the boot blocks? Actually in /usr/src/sys/sys/disklabel.h you can see three constants defined. #define LABEL_PART 2 /* partition containing label */ #define RAW_PART 2 /* partition containing whole disk */ #define SWAP_PART 1 /* partition normally containing swap */ The code uses LABEL_PART when it wants to access the partition containing the entire disk, together with the disklabel, but as you can see, this is the same as RAW_PART which is defined to `2'. Now, lemme guess... 'a', 'b', 'c'.. '0', '1', '2'.. SWAP_PART is '1' and default swap partition is 'b'. RAW_PART is '2' and the default `entire disk' partition is 'c'. HAHHAHHH. I'm beginning to love this source thing! Absolutely amazing, how clearly ideas and things can jump out on you, if you read a few lines of code :-) Cheers, Giorgos. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jan 27 5:12:41 2001 Delivered-To: freebsd-stable@freebsd.org Received: from republic.netfish.au.com (CPE-61-9-156-104.vic.bigpond.net.au [61.9.156.104]) by hub.freebsd.org (Postfix) with ESMTP id 945F037B402 for ; Sat, 27 Jan 2001 05:12:23 -0800 (PST) Received: (from nobody@localhost) by republic.netfish.au.com (8.11.1/8.11.1) id f0RDC0f50642; Sun, 28 Jan 2001 00:12:00 +1100 (EST) (envelope-from nobody) Date: Sun, 28 Jan 2001 00:12:00 +1100 (EST) Message-Id: <200101271312.f0RDC0f50642@republic.netfish.au.com> To: freebsd-stable@freebsd.org Subject: From: Nick Grundy X-Mailer: Postaci 1.1.0 (ftp://ftp.onar.com.tr/pub/linux/postaci) X-Comment: This message was sent from 10.0.13.110 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary = b764c1464b1e9a909ca24c0512ab03736 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a MIME encoded message. --b764c1464b1e9a909ca24c0512ab03736 Content-Type: text/plain Content-Transfer-Encoding: base64 c3Vic2NyaWJlIGZyZWVic2Qtc3RhYmxlLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tClRoaXMgbWVzc2FnZSB3YXMgc2VudCB1c2luZyBQb3N0YWNpIFdlYm1haWwuIChodHRw Oi8vd3d3LnRybGludXguY29tKQ== --b764c1464b1e9a909ca24c0512ab03736-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jan 27 5:21:13 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 823BC37B402 for ; Sat, 27 Jan 2001 05:20:54 -0800 (PST) Received: from [203.164.12.28] by www.quake.com.au (NTMail 4.30.0012/AH9370.63.d1acf55c) with ESMTP id towsaaaa for ; Sun, 28 Jan 2001 00:29:32 +1100 Message-ID: <3A72CB47.7A5DD83@quake.com.au> Date: Sun, 28 Jan 2001 00:21:11 +1100 From: Kal Torak X-Mailer: Mozilla 4.73 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: FreeBSD-stable Subject: ipfw forwarding Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hiyas, I am hoping someone will be able to to tell me what im doing wrong with this forwarding rules... And dont anyone complain that this should go to a different list or there will be trouble :P Anyway here is what I am trying to do... I have a FreeBSD box as my gateway / firewall so it has an external ip and internal lan ip (naturally), I am using nat for internet access... My gateway is an old p166 with 250mb hdd, so its not practical to run any servers on it, this is why I want to forward connections to certain ports to other systems in the local lan... Ok, so I have another FreeBSD box running a server on port 27015/udp and I put a rule in my ipfw list saying "${fwcmd} 600 fwd 10.0.0.4 udp from any to any 27015" this seems like it should do the job, and when I connect from the outside a "ipfw -at l" shows that the rule was hit, yet on the system the data was meant to be forwarded to nothing comes... I have tested with netcat to see if anything comes, but nothing dose and the activity lights on the nic never flash... So I figure since everything works fine inside the network I must be using the fwd rule wrong or something... I dont really want to use any of those redirection thingys like plug-gw, I am hoping to just use the fwd rule? Or do I have to use some sort of udp forwarding program? Thanks, any help or comments would be good :) Kal. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jan 27 6:39:19 2001 Delivered-To: freebsd-stable@freebsd.org Received: from arianna.webcraft99.alt (unknown [202.151.212.19]) by hub.freebsd.org (Postfix) with ESMTP id F3A4D37B69E for ; Sat, 27 Jan 2001 06:39:01 -0800 (PST) Received: from jenna.webcraft99.alt (jenna.webcraft99.alt [192.168.1.22]) by arianna.webcraft99.alt (AriAnnA) with ESMTP id AA1907C20; Sat, 27 Jan 2001 23:04:04 +0800 (MYT) Received: from webcraft99.com (lexus.webcraft99.alt [192.168.1.31]) by jenna.webcraft99.alt (JEnnA) with ESMTP id DA09C3DB2; Sat, 27 Jan 2001 22:43:45 +0800 (MYT) Message-ID: <3A72DEA1.A31EC401@webcraft99.com> Date: Sat, 27 Jan 2001 22:43:45 +0800 From: Feisal Umar Organization: Webcraft Sdn Bhd (http://www.webcraft99.com) X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-stable@freebsd.org, ipfilter@coombs.anu.edu.au Subject: IPFILTER 3.4.16 and FreeBSD-4.2 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Are the startup scripts for FreeBSD-4.2 broken for IPFILTER/IPNAT support? I have a gateway machine configured with IPFILTER/IPNAT via the rc.conf with the following entries: ipfilter_enable="YES" ipfilter_flags="" ipnat_enable="YES" ipmon_enable="YES" Hosts behind the GATEWAY can't traverse to outside via the NAT after the GATEWAY is rebooted with a new Kernel Build (yesterday). I had to manually specify "ipnat -CF -f /etc/ipnat.rules" before everything works as normal. Ipmon behaviour has also changed, ie nothing is being passed to syslog except an entry saying ipmon was started. I can't find anything is the system logs to suggest anything is amiss. PS: Everything was working A-OK prior to yesterday's build (except that ipmon_enable wasn't supported). My IPfilter isn't the stock 3.4.8. Hasn't been a problem before. Thanks for any inputs or pointers. -- Feisal Umar Webcraft Sdn Bhd - http://www.webcraft99.com You cannot kill time without injuring eternity. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jan 27 7: 4:23 2001 Delivered-To: freebsd-stable@freebsd.org Received: from pendragon.tacni.net (unknown [216.178.136.165]) by hub.freebsd.org (Postfix) with SMTP id B5EA837B402 for ; Sat, 27 Jan 2001 07:04:06 -0800 (PST) Received: (qmail 37018 invoked by alias); 27 Jan 2001 15:04:19 -0000 Received: from unknown (HELO mail.tacni.net) (204.155.159.82) by ns2.sohos.net with SMTP; 27 Jan 2001 15:04:19 -0000 Received: (qmail 93427 invoked by uid 1000); 27 Jan 2001 15:03:18 -0000 Date: Sat, 27 Jan 2001 09:03:18 -0600 From: Erich Zigler To: stable@freebsd.org Subject: Malloc Problems Message-ID: <20010127090318.A93412@superhero.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Eric-Conspiracy: There is no conspiracy. X-Shane: Hi Shane! Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG One of my FreeBSD 3.2 servers is displaying this.. CRON in malloc(): warning: pointer to wrong page. This happens when newsyslog is executed, and adjkerntz -a is ran. It also happens with another simple shell script is ran. I was wondering what the cause was. -- Erich Zigler My email went to Urbana, but all I got was this stupid router! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jan 27 7: 8:30 2001 Delivered-To: freebsd-stable@freebsd.org Received: from clmboh1-smtp3.columbus.rr.com (unknown [65.24.0.112]) by hub.freebsd.org (Postfix) with ESMTP id D579F37B401 for ; Sat, 27 Jan 2001 07:08:10 -0800 (PST) Received: from mail.iowna.com (dhcp065-024-023-038.columbus.rr.com [65.24.23.38]) by clmboh1-smtp3.columbus.rr.com (8.11.2/8.11.2) with ESMTP id f0RF5jr09368; Sat, 27 Jan 2001 10:05:46 -0500 (EST) Message-ID: <3A72E375.C71C175F@mail.iowna.com> Date: Sat, 27 Jan 2001 10:04:21 -0500 From: Bill Moran X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.2-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: Jeroen Ruigrok van der Werven Cc: stable@FreeBSD.ORG Subject: Additional BIND ???s (was Re: Problems with BIND in 4.2-STABLE (resource leak?)) References: <3A72474D.979B84FA@mail.iowna.com> <20010127100200.B51681@lucifer.bart.nl> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jeroen Ruigrok van der Werven wrote: > > -On [20010127 05:05], Bill Moran (wmoran@mail.iowna.com) wrote: > >I'm having trouble with BIND in 4.2-STABLE (Jan 18 22:16:33) > >I'm running the version of BIND that installs by default (named -v > >reports 8.2.3-T6B) > > [snip RAM problem] > > >Has anyone else seen this, or have I got some unique problem here? > > There were a fair amount of bugs in 8.2.3 betas. > > I am in the progress of preparing the import, and importing 8.2.3, which > is the released version. As soon as I have it imported in CURRENT, and > after I have done my usual round of testing in STABLE I will MFC it. In a nutshell then, you're telling me: a) problems like this have been seen before b) the solution is to use a different version of BIND That brings me to one other question: In reviewing the list archives I noticed some early complaints about beta code being used in -STABLE. The response to this was (if I understood it correctly) that the 8.2.3 beta code was better than the 8.2.2 stable code. The ultimate reason for this question is simple: Should I switch to bind 8.2.2 or wait for the latest MFC? Is 8.2.2 going to increase the reliability of this machine or am I better off dealing with 8.2.3 for now? This is a production machine and I'd like to get it to as stable a point as possible and quit messing with it. TIA -Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jan 27 7:59: 3 2001 Delivered-To: freebsd-stable@freebsd.org Received: from volatile.chemikals.org (ci391991-a.grnvle1.sc.home.com [24.9.31.75]) by hub.freebsd.org (Postfix) with ESMTP id C173037B400 for ; Sat, 27 Jan 2001 07:58:43 -0800 (PST) Received: (from morganw@localhost) by volatile.chemikals.org (8.11.1/8.11.1) id f0RFwe698750; Sat, 27 Jan 2001 10:58:40 -0500 (EST) (envelope-from morganw) Date: Sat, 27 Jan 2001 10:58:40 -0500 (EST) From: Wesley Morgan To: Cc: Subject: weirdness on freebsd-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 I have 2 boxes running -stable and I am seeing very very weird behavior. ipfilter suddenly decides that the current rules are nuts and won't allow any outbound connections. After much frustration and moving around of rules, I managed to get it working on one machine... Only to suddenly see that a few days later now inbound connections are not allowed! The second machine today began to deny the outbound connections and is exhibiting the identical behavior as the first. I think I have narrowed it down to some problem with state. The original failed machine will allow a connection to be negotiated (flags S) but no further packets. Removal of the 'flags S' parameter on all rules appears to fix the problem. Upgrading to the latest ipfilter does not seem to fix it. What on earth could this be? My world and kernel are not currently in sync (except for ipfilter) but how can that effect the firewall? -- _ __ ___ ____ ___ ___ ___ Wesley N Morgan _ __ ___ | _ ) __| \ morganw@chemikals.org _ __ | _ \._ \ |) | FreeBSD: The Power To Serve _ |___/___/___/ 6bone: 3ffe:1ce3:7::b4ff:fe53:c297 Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jan 27 8: 0:19 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 D287137B400 for ; Sat, 27 Jan 2001 08:00:00 -0800 (PST) Received: by lunatic.oneinsane.net (Postfix, from userid 1000) id 0082015556; Sat, 27 Jan 2001 07:59:59 -0800 (PST) Date: Sat, 27 Jan 2001 07:59:59 -0800 From: Ron 'The InSaNe One' Rosson To: freebsd-stable@freebsd.org Subject: IPFilter will not allow traceroute anymore Message-ID: <20010127075959.A83055@lunatic.oneinsane.net> Reply-To: Ron Rosson 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-Operating-System: FreeBSD lunatic.oneinsane.net 4.2-STABLE X-Moon: The Moon is Waxing Crescent (9% 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: 7:52AM up 2 days, 13:58, 2 users, load averages: 1.16, 1.12, 1.08 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 01/23/2001 there was a change made to IPFilters ip_state.c file. The change for some reason has cuased tracerouting to stop working when using the following ruleset: # Ruleset taken from http://www.obfuscation.org/ipf/ipf-howto.txt # Section 7.1 pass in quick on lo0 all pass out quick on lo0 all block in log all block out all # This allows for AUTH pass in quick proto tcp from any to any port = 113 flags S/SA keep state #This allows for FTP pass in quick proto tcp from any port = 20 to any port 39999 >< 45000 flags S/SA keep state pass out quick proto icmp from any to any keep state pass out quick proto tcp/udp from any to any keep state keep frags The earlier version of this file had the same problem as well but there was a patch available that I have been using. With the changes made to the ip_state.c file this patch no longer applies cleanly. I will attach the patch as an attatchment to this email. If I should turn this into a send-pr Just say the word and it will done. TIA P.S. An admin who misses his traceroute ;-) -- ------------------------------------------------------------------------------ Ron Rosson ... and a UNIX user said ... The InSaNe One rm -rf * insane@oneinsane.net and all was /dev/null and *void() ------------------------------------------------------------------------------ It only rains straight down. God doesn't do windows. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jan 27 8:14:53 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 E6BCD37B402 for ; Sat, 27 Jan 2001 08:14:32 -0800 (PST) Received: by lunatic.oneinsane.net (Postfix, from userid 1000) id 387BD15556; Sat, 27 Jan 2001 08:14:32 -0800 (PST) Date: Sat, 27 Jan 2001 08:14:32 -0800 From: Ron 'The InSaNe One' Rosson To: freebsd-stable@freebsd.org Subject: Re: IPFilter will not allow traceroute anymore Message-ID: <20010127081431.B83055@lunatic.oneinsane.net> Reply-To: Ron Rosson Mail-Followup-To: freebsd-stable@freebsd.org References: <20010127075959.A83055@lunatic.oneinsane.net> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="9amGYk9869ThD9tj" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010127075959.A83055@lunatic.oneinsane.net>; from insane@lunatic.oneinsane.net on Sat, Jan 27, 2001 at 07:59:59AM -0800 X-Operating-System: FreeBSD lunatic.oneinsane.net 4.2-STABLE X-Moon: The Moon is Waxing Crescent (9% 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: 8:13AM up 2 days, 14:19, 2 users, load averages: 1.03, 1.05, 1.06 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --9amGYk9869ThD9tj Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Ron 'The InSaNe One' Rosson (insane@lunatic.oneinsane.net) wrote: > On 01/23/2001 there was a change made to IPFilters ip_state.c file. The > change for some reason has cuased tracerouting to stop working when > using the following ruleset: > > # Ruleset taken from http://www.obfuscation.org/ipf/ipf-howto.txt > # Section 7.1 > > pass in quick on lo0 all > pass out quick on lo0 all > > block in log all > block out all > > # This allows for AUTH > pass in quick proto tcp from any to any port = 113 flags S/SA keep state > > #This allows for FTP > pass in quick proto tcp from any port = 20 to any port 39999 >< 45000 > flags S/SA > keep state > > pass out quick proto icmp from any to any keep state > pass out quick proto tcp/udp from any to any keep state keep frags > > The earlier version of this file had the same problem as well but there > was a patch available that I have been using. With the changes made to > the ip_state.c file this patch no longer applies cleanly. I will attach > the patch as an attatchment to this email. > > If I should turn this into a send-pr Just say the word and it will done. > > TIA > > P.S. An admin who misses his traceroute ;-) Damn.... Forgot to attatch the dan file -- ------------------------------------------------------------------------------ Ron Rosson ... and a UNIX user said ... The InSaNe One rm -rf * insane@oneinsane.net and all was /dev/null and *void() ------------------------------------------------------------------------------ You can be replaced by a machine that flushes. --9amGYk9869ThD9tj Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="icmp.patch" Index: ip_state.c =================================================================== RCS file: /home/freebsd/CVS/src/sys/netinet/ip_state.c,v retrieving revision 1.13.2.3 diff -u -u -w -r1.13.2.3 ip_state.c --- ip_state.c 2000/07/19 23:27:55 1.13.2.3 +++ ip_state.c 2000/07/29 10:44:21 @@ -1000,6 +1000,12 @@ if (fin->fin_plen < ICMPERR_MAXPKTLEN + ((oip->ip_hl - 5) << 2)) return NULL; + /* in the IPv4 case we must zero the i6addr union otherwise + the IP6EQ and IP6NEQ macros produce the wrong results because + of the 'junk' in the unused part of the union */ + bzero(&src, sizeof(src)); + bzero(&dst, sizeof(dst)); + if (oip->ip_p == IPPROTO_ICMP) { icmp = (icmphdr_t *)((char *)oip + (oip->ip_hl << 2)); @@ -1029,6 +1035,7 @@ hv %= fr_statesize; oip->ip_len = ntohs(oip->ip_len); + ofin.fin_v = 4; fr_makefrip(oip->ip_hl << 2, oip, &ofin); oip->ip_len = htons(oip->ip_len); ofin.fin_ifp = fin->fin_ifp; @@ -1078,6 +1085,7 @@ */ savelen = oip->ip_len; oip->ip_len = ip->ip_len - (ip->ip_hl << 2) - ICMPERR_ICMPHLEN; + ofin.fin_v = 4; /* without this fr_makefrip gets very confused */ fr_makefrip(oip->ip_hl << 2, oip, &ofin); oip->ip_len = savelen; ofin.fin_ifp = fin->fin_ifp; @@ -1579,6 +1587,7 @@ hv %= fr_statesize; oip->ip6_plen = ntohs(oip->ip6_plen); + ofin.fin_v = 6; fr_makefrip(sizeof(*oip), (ip_t *)oip, &ofin); oip->ip6_plen = htons(oip->ip6_plen); ofin.fin_ifp = fin->fin_ifp; --9amGYk9869ThD9tj-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jan 27 8:24:46 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 23DF337B404 for ; Sat, 27 Jan 2001 08:24:27 -0800 (PST) Received: (from daemon@localhost) by point.osg.gov.bc.ca (8.8.7/8.8.8) id IAA17346; Sat, 27 Jan 2001 08:24:23 -0800 Received: from passer.osg.gov.bc.ca(142.32.110.29) via SMTP by point.osg.gov.bc.ca, id smtpda17344; Sat Jan 27 08:24:15 2001 Received: (from uucp@localhost) by passer.osg.gov.bc.ca (8.11.2/8.9.1) id f0RGOAn09051; Sat, 27 Jan 2001 08:24:10 -0800 (PST) Received: from cwsys9.cwsent.com(10.2.2.1), claiming to be "cwsys.cwsent.com" via SMTP by passer9.cwsent.com, id smtpdiP9049; Sat Jan 27 08:24:00 2001 Received: (from uucp@localhost) by cwsys.cwsent.com (8.11.2/8.9.1) id f0RGO0c57680; Sat, 27 Jan 2001 08:24:00 -0800 (PST) Message-Id: <200101271624.f0RGO0c57680@cwsys.cwsent.com> Received: from localhost.cwsent.com(127.0.0.1), claiming to be "cwsys" via SMTP by localhost.cwsent.com, id smtpdR57676; Sat Jan 27 08:23:30 2001 X-Mailer: exmh version 2.3.1 01/18/2001 with nmh-1.0.4 Reply-To: Cy Schubert - ITSD Open Systems Group From: Cy Schubert - ITSD Open Systems Group X-Sender: schubert To: Ron Rosson Cc: freebsd-stable@FreeBSD.ORG Subject: Re: IPFilter will not allow traceroute anymore In-reply-to: Your message of "Sat, 27 Jan 2001 08:14:32 PST." <20010127081431.B83055@lunatic.oneinsane.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 27 Jan 2001 08:23:30 -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG You're probably better of installing IPF 3.4.16. There have been many bugfixes and improvements since 3.4.8 (version of IPF packaged with FreeBSD-STABLE). 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 In message <20010127081431.B83055@lunatic.oneinsane.net>, "Ron 'The InSaNe One' Rosson" writes: > > --9amGYk9869ThD9tj > Content-Type: text/plain; charset=us-ascii > Content-Disposition: inline > > Ron 'The InSaNe One' Rosson (insane@lunatic.oneinsane.net) wrote: > > On 01/23/2001 there was a change made to IPFilters ip_state.c file. The > > change for some reason has cuased tracerouting to stop working when > > using the following ruleset: > > > > # Ruleset taken from http://www.obfuscation.org/ipf/ipf-howto.txt > > # Section 7.1 > > > > pass in quick on lo0 all > > pass out quick on lo0 all > > > > block in log all > > block out all > > > > # This allows for AUTH > > pass in quick proto tcp from any to any port = 113 flags S/SA keep state > > > > #This allows for FTP > > pass in quick proto tcp from any port = 20 to any port 39999 >< 45000 > > flags S/SA > > keep state > > > > pass out quick proto icmp from any to any keep state > > pass out quick proto tcp/udp from any to any keep state keep frags > > > > The earlier version of this file had the same problem as well but there > > was a patch available that I have been using. With the changes made to > > the ip_state.c file this patch no longer applies cleanly. I will attach > > the patch as an attatchment to this email. > > > > If I should turn this into a send-pr Just say the word and it will done. > > > > TIA > > > > P.S. An admin who misses his traceroute ;-) > > > Damn.... Forgot to attatch the dan file > -- > ----------------------------------------------------------------------------- > - > Ron Rosson ... and a UNIX user said ... > The InSaNe One rm -rf * > insane@oneinsane.net and all was /dev/null and *void() > ----------------------------------------------------------------------------- > - > You can be replaced by a machine that flushes. > > --9amGYk9869ThD9tj > Content-Type: text/plain; charset=us-ascii > Content-Disposition: attachment; filename="icmp.patch" > > Index: ip_state.c > =================================================================== > RCS file: /home/freebsd/CVS/src/sys/netinet/ip_state.c,v > retrieving revision 1.13.2.3 > diff -u -u -w -r1.13.2.3 ip_state.c > --- ip_state.c 2000/07/19 23:27:55 1.13.2.3 > +++ ip_state.c 2000/07/29 10:44:21 > @@ -1000,6 +1000,12 @@ > if (fin->fin_plen < ICMPERR_MAXPKTLEN + ((oip->ip_hl - 5) << 2)) > return NULL; > > + /* in the IPv4 case we must zero the i6addr union otherwise > + the IP6EQ and IP6NEQ macros produce the wrong results because > + of the 'junk' in the unused part of the union */ > + bzero(&src, sizeof(src)); > + bzero(&dst, sizeof(dst)); > + > if (oip->ip_p == IPPROTO_ICMP) { > icmp = (icmphdr_t *)((char *)oip + (oip->ip_hl << 2)); > > @@ -1029,6 +1035,7 @@ > hv %= fr_statesize; > > oip->ip_len = ntohs(oip->ip_len); > + ofin.fin_v = 4; > fr_makefrip(oip->ip_hl << 2, oip, &ofin); > oip->ip_len = htons(oip->ip_len); > ofin.fin_ifp = fin->fin_ifp; > @@ -1078,6 +1085,7 @@ > */ > savelen = oip->ip_len; > oip->ip_len = ip->ip_len - (ip->ip_hl << 2) - ICMPERR_ICMPHLEN; > + ofin.fin_v = 4; /* without this fr_makefrip gets very confused */ > fr_makefrip(oip->ip_hl << 2, oip, &ofin); > oip->ip_len = savelen; > ofin.fin_ifp = fin->fin_ifp; > @@ -1579,6 +1587,7 @@ > hv %= fr_statesize; > > oip->ip6_plen = ntohs(oip->ip6_plen); > + ofin.fin_v = 6; > fr_makefrip(sizeof(*oip), (ip_t *)oip, &ofin); > oip->ip6_plen = htons(oip->ip6_plen); > ofin.fin_ifp = fin->fin_ifp; > > --9amGYk9869ThD9tj-- > > > 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 27 9: 8:16 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 437DC37B400 for ; Sat, 27 Jan 2001 09:07:59 -0800 (PST) Received: (qmail 77027 invoked by uid 1001); 27 Jan 2001 17:07:55 -0000 Date: Sat, 27 Jan 2001 12:07:55 -0500 From: Pete Fritchman To: Feisal Umar Cc: freebsd-stable@freebsd.org Subject: Re: IPFILTER 3.4.16 and FreeBSD-4.2 Message-ID: <20010127120755.A76777@databits.net> References: <3A72DEA1.A31EC401@webcraft99.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3A72DEA1.A31EC401@webcraft99.com>; from afu@webcraft99.com on Sat, Jan 27, 2001 at 10:43:45PM +0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ++ 27/01/01 22:43 +0800 - Feisal Umar: >Hi > >Are the startup scripts for FreeBSD-4.2 broken for IPFILTER/IPNAT >support? >I have a gateway machine configured with IPFILTER/IPNAT via the rc.conf >with the following entries: >ipfilter_enable="YES" >ipfilter_flags="" >ipnat_enable="YES" >ipmon_enable="YES" > You might need: ipfilter_rules="/etc/ipf.rules" ipnat_rules="/etc/ipnat.rules" [...] -pete. > >-- >Feisal Umar >Webcraft Sdn Bhd - http://www.webcraft99.com > >You cannot kill time without injuring eternity. -- 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 27 9:12:46 2001 Delivered-To: freebsd-stable@freebsd.org Received: from penguin.prod.itd.earthlink.net (penguin.prod.itd.earthlink.net [207.217.120.134]) by hub.freebsd.org (Postfix) with ESMTP id 2341C37B401 for ; Sat, 27 Jan 2001 09:12:29 -0800 (PST) Received: from dionysos.yi.org (1Cust20.tnt14.phoenix.az.da.uu.net [63.14.185.20]) by penguin.prod.itd.earthlink.net (8.9.3-EL_1_3/8.9.3) with ESMTP id JAA11189; Sat, 27 Jan 2001 09:11:06 -0800 (PST) Received: by dionysos.yi.org (Postfix, from userid 1001) id D37141C57; Fri, 26 Jan 2001 23:21:27 -0700 (MST) Date: Fri, 26 Jan 2001 23:21:27 -0700 From: Dionysos To: Kris Kennaway Cc: james@m-a.net, freebsd-stable@FreeBSD.ORG Subject: Re: Buildworld failure using two disks Message-ID: <20010126232127.A294@dionysos.yi.org> Reply-To: james@m-a.net References: <20010126151748.A1958@dionysos.yi.org> <20010126200138.B52838@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010126200138.B52838@xor.obsecurity.org>; from kris@obsecurity.org on Fri, Jan 26, 2001 at 08:01:38PM -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jan 26, 2001 at 08:01:38PM -0800, Kris Kennaway wrote: > On Fri, Jan 26, 2001 at 03:17:48PM -0700, Dionysos wrote: > > Hi all, > > > Using the latest -stable source I get an error at the beginning of > > the build only when I have /usr/obj mounted on a separate physical > > disk. > > It should work. Try blowing away /usr/obj. > > Kris already did more than once. To expand on this a bit, I tried doing some links in a context outside of make buildworld. Symbolic links do work across filesystems still but I continue to get errors when trying to make symbolic links across filesystems that are on different disks. I've contemplated sending in a PR for it, but I'll still entertain that something wierd (and fixable) is going on with my system in particular. Here's some output from my last try to link as well as uname -a output if it'll help... dionysos# ln -sf /root/.login /usr/obj/.login.link.test ln: /usr/obj/.login.link.test: Operation not supported dionysos# uname -a FreeBSD dionysos.yi.org 4.2-STABLE FreeBSD 4.2-STABLE #0: Thu Jan 11 12:43:58 MST 2001 root@dionysos.yi.org:/usr/obj/usr/src/sys/MYKERNEL i386 James To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jan 27 10: 2:40 2001 Delivered-To: freebsd-stable@freebsd.org Received: from subnet.sub.net (subnet.sub.net [212.227.14.21]) by hub.freebsd.org (Postfix) with ESMTP id 9AEAC37B400 for ; Sat, 27 Jan 2001 10:02:21 -0800 (PST) Received: from lyxys.ka.sub.org (uucp@localhost) by subnet.sub.net (8.8.8/8.8.8/1.2subnet-linux) with bsmtp id TAA02259; Sat, 27 Jan 2001 19:02:13 +0100 Received: from localhost (1653 bytes) by lyxys.ka.sub.org via sendmail with P:stdio/R:smart_host/T:inet_uusmtp (sender: ) (ident using unix) id for ; Sat, 27 Jan 2001 18:59:38 +0100 (CET) (Smail-3.2.0.111 2000-Feb-17 #1 built 2000-Aug-23) Message-Id: From: wolfgang@lyxys.ka.sub.org (Wolfgang Zenker) Subject: Re: Buildworld failure using two disks In-Reply-To: <20010126232127.A294@dionysos.yi.org> "from Dionysos at Jan 26, 2001 11:21:27 pm" To: james@m-a.net Date: Sat, 27 Jan 2001 18:59:38 +0100 (CET) Cc: Kris Kennaway , freebsd-stable@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 Hi, > On Fri, Jan 26, 2001 at 08:01:38PM -0800, Kris Kennaway wrote: >> On Fri, Jan 26, 2001 at 03:17:48PM -0700, Dionysos wrote: >>> [..] >>> Using the latest -stable source I get an error at the beginning of >>> the build only when I have /usr/obj mounted on a separate physical >>> disk. >> It should work. Try blowing away /usr/obj. > already did more than once. To expand on this a bit, I tried doing some links > in a context outside of make buildworld. Symbolic links do work across > filesystems still but I continue to get errors when trying to make symbolic > links across filesystems that are on different disks. I've contemplated > sending in a PR for it, but I'll still entertain that something wierd (and > fixable) is going on with my system in particular. Here's some output from my > last try to link as well as uname -a output if it'll help... > dionysos# ln -sf /root/.login /usr/obj/.login.link.test > ln: /usr/obj/.login.link.test: Operation not supported Could we see the output of "mount" please? Called without parameters it should tell you some details about all mounted filesystems. Wolfgang To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jan 27 10:12: 5 2001 Delivered-To: freebsd-stable@freebsd.org Received: from lucifer.ninth-circle.org (lucifer.bart.nl [194.158.168.74]) by hub.freebsd.org (Postfix) with ESMTP id AB22137B401 for ; Sat, 27 Jan 2001 10:11:47 -0800 (PST) Received: (from asmodai@localhost) by lucifer.ninth-circle.org (8.11.1/8.11.0) id f0RIAo057882; Sat, 27 Jan 2001 19:10:50 +0100 (CET) (envelope-from asmodai) Date: Sat, 27 Jan 2001 19:10:50 +0100 From: Jeroen Ruigrok van der Werven To: Cy Schubert - ITSD Open Systems Group Cc: Bill Moran , stable@FreeBSD.ORG Subject: Re: Problems with BIND in 4.2-STABLE (resource leak?) Message-ID: <20010127191050.C51681@lucifer.bart.nl> References: <20010127100200.B51681@lucifer.bart.nl> <200101271034.f0RAYs453785@cwsys.cwsent.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200101271034.f0RAYs453785@cwsys.cwsent.com>; from Cy.Schubert@uumail.gov.bc.ca on Sat, Jan 27, 2001 at 02:34:08AM -0800 Organisation: VIA Net.Works The Netherlands Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -On [20010127 11:40], Cy Schubert - ITSD Open Systems Group (Cy.Schubert@uumail.gov.bc.ca) wrote: >Do we know when BIND9 might be imported into -CURRENT? As soon as I am done with 8.2.3 import. One thing at a time please. :) -- Jeroen Ruigrok van der Werven VIA Net.Works The Netherlands BSD: Technical excellence at its best Network- and systemadministrator D78D D0AD 244D 1D12 C9CA 7152 035C 1138 546A B867 Misery loves company... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jan 27 10:20:19 2001 Delivered-To: freebsd-stable@freebsd.org Received: from lucifer.ninth-circle.org (lucifer.bart.nl [194.158.168.74]) by hub.freebsd.org (Postfix) with ESMTP id EF67937B400 for ; Sat, 27 Jan 2001 10:20:00 -0800 (PST) Received: (from asmodai@localhost) by lucifer.ninth-circle.org (8.11.1/8.11.0) id f0RIJwg57950; Sat, 27 Jan 2001 19:19:58 +0100 (CET) (envelope-from asmodai) Date: Sat, 27 Jan 2001 19:19:58 +0100 From: Jeroen Ruigrok van der Werven To: Bill Moran Cc: stable@FreeBSD.ORG Subject: Re: Additional BIND ???s (was Re: Problems with BIND in 4.2-STABLE (resource leak?)) Message-ID: <20010127191958.D51681@lucifer.bart.nl> References: <3A72474D.979B84FA@mail.iowna.com> <20010127100200.B51681@lucifer.bart.nl> <3A72E375.C71C175F@mail.iowna.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3A72E375.C71C175F@mail.iowna.com>; from wmoran@mail.iowna.com on Sat, Jan 27, 2001 at 10:04:21AM -0500 Organisation: VIA Net.Works The Netherlands Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -On [20010127 16:10], Bill Moran (wmoran@mail.iowna.com) wrote: >Jeroen Ruigrok van der Werven wrote: >> >> [snip RAM problem] >> >> >Has anyone else seen this, or have I got some unique problem here? >> >> There were a fair amount of bugs in 8.2.3 betas. >> >> I am in the progress of preparing the import, and importing 8.2.3, which >> is the released version. As soon as I have it imported in CURRENT, and >> after I have done my usual round of testing in STABLE I will MFC it. > >In a nutshell then, you're telling me: >a) problems like this have been seen before No, where did I say that? I merely said that there are a few bugs in BIND TxB. But BIND 8.2.2-pX have problems as well. I just read over the CHANGES and there have been fixed a number of memory leaks. So you might be tripping over these. >b) the solution is to use a different version of BIND Possibly. >That brings me to one other question: >In reviewing the list archives I noticed some early complaints about >beta code being used in -STABLE. The response to this was (if I >understood it correctly) that the 8.2.3 beta code was better than the >8.2.2 stable code. 8.2.2 has had problems as well. And the MFC was done in the prospect that the beta period would not take over 6 months. >The ultimate reason for this question is simple: Should I switch to bind >8.2.2 or wait for the latest MFC? Is 8.2.2 going to increase the >reliability of this machine or am I better off dealing with 8.2.3 for >now? This is a production machine and I'd like to get it to as stable a >point as possible and quit messing with it. 8.2.3 hasn't had problems with regard to security as 8.2.2 has/had. -- Jeroen Ruigrok van der Werven VIA Net.Works The Netherlands BSD: Technical excellence at its best Network- and systemadministrator D78D D0AD 244D 1D12 C9CA 7152 035C 1138 546A B867 Misery loves company... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jan 27 11: 2:32 2001 Delivered-To: freebsd-stable@freebsd.org Received: from tao.ca (tao.ca [198.96.117.188]) by hub.freebsd.org (Postfix) with ESMTP id BEB1137B400 for ; Sat, 27 Jan 2001 11:02:06 -0800 (PST) Received: (from anarcat@localhost) by tao.ca (Collective/TAO6) id f0RJ23x26543; Sat, 27 Jan 2001 14:02:03 -0500 Date: Sat, 27 Jan 2001 14:02:03 -0500 From: anarcat To: Kent Stewart Cc: anarcat , freebsd-stable@freebsd.org Subject: Re: Can't build kernel under stable-2000.12.31 Message-ID: <20010127140203.A26460@dojo.tao.ca> References: <20010126201248.A1832@dojo.tao.ca> <3A723980.DEDEE04E@urx.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="5mCyUwZo2JvN/JJP" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3A723980.DEDEE04E@urx.com>; from kstewart@urx.com on Fri, Jan 26, 2001 at 06:59:12PM -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --5mCyUwZo2JvN/JJP Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Ok. I do not understand very clearly why, but: # rm -rf /sys/compile/SHALL and then using the traditional "config" method (config && cd ... && make=20 depend && make && make install) works.=20 Why can't buildkernel do this by itself? thanks. A. On Fri, Jan 26, 2001 at 06:59:12PM -0800, Big Brother made Kent Stewart wri= te: >=20 >=20 > anarcat wrote: > >=20 > > Hi! > >=20 > > (please CC: me, I'm not on the list) > >=20 > > Building a custom kernel under freebsd-stable (cvsup'd and made world on > > 2000-12-31) fails with the following, any idea why? >=20 > This error usually occurs beause you didn't do a buildworld to > populate /usr/obj first. Read /usr/src/UPDATING because the sequence > isn't an option. If you already have a current userland, then the > choice can include the config method. They way it looks, you mixed > your world's and that doesn't work. >=20 > Kent >=20 > >=20 > > shall# make KERNEL=3DSHALL buildkernel installkernel > > ... > > =3D=3D=3D> wi > > @ -> /usr/src/sys > > machine -> /usr/src/sys/i386/include > > perl @/kern/makedevops.pl -h @/kern/device_if.m > > perl @/kern/makedevops.pl -h @/kern/bus_if.m > > rm -f .depend > > mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -I- -I. -I@ > > -I@/../include -I/usr/obj/usr/src/i386/usr/include > > /usr/src/sys/modules/wi/../../i386/isa/if_wi.c > > cd /usr/obj/usr/src/sys/SHALL; MAKEOBJDIRPREFIX=3D/usr/obj > > COMPILER_PATH=3D/usr/obj/usr/src/i386/usr/libexec:/usr/obj/usr/src/i386= /usr/bin > > LIBRARY_PATH=3D/usr/obj/usr/src/i386/usr/lib:/usr/obj/usr/src/i386/usr/= lib > > OBJFORMAT_PATH=3D/usr/obj/usr/src/i386/usr/libexec > > PERL5LIB=3D/usr/obj/usr/src/i386/usr/libdata/perl/5.00503 > > DESTDIR=3D/usr/obj/usr/src/i386 INSTALL=3D"sh /usr/src/tools/install.s= h" > > PATH=3D/usr/obj/usr/src/i386/usr/sbin:/usr/obj/usr/src/i386/usr/bin:/us= r/obj/usr/src/i386/usr/games:/sbin:/bin:/usr/sbin:/usr/bin > > MACHINE=3Di386 make KERNEL=3Dkernel all > > cc -c -x assembler-with-cpp -DLOCORE -O -Wall -Wredundant-decls > > -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-ar= ith > > -Winline -Wcast-qual -fformat-extensions -ansi -g -nostdinc -I- -I. > > -I/usr/src/sys -I/usr/src/sys/../include -D_KERNEL -include opt_global= .h > > -elf -mpreferred-stack-boundary=3D2 /usr/src/sys/i386/i386/locore.s > > /tmp/ccO18745.s: Assembler messages: > > /tmp/ccO18745.s:1744: Error: .space specifies non-absolute value > > /tmp/ccO18745.s:2455: Error: undefined symbol L0 in operation setting > > PTmap > > /tmp/ccO18745.s:2455: Error: undefined symbol PDRSHIFT in operation > > setting PTmap > > /tmp/ccO18745.s:1712: Error: undefined symbol L0 in operation > > /tmp/ccO18745.s:1712: Error: undefined symbol PAGE_SIZE in operation > > /tmp/ccO18745.s:1713: Error: undefined symbol L0 in operation > > /tmp/ccO18745.s:1713: Error: undefined symbol PDESIZE in operation > > /tmp/ccO18745.s:2455: Error: undefined symbol L0 in operation setting > > APTmap > > /tmp/ccO18745.s:2455: Error: undefined symbol PDRSHIFT in operation > > setting APTmap > > /tmp/ccO18745.s:1721: Error: undefined symbol L0 in operation > > /tmp/ccO18745.s:1721: Error: undefined symbol PAGE_SIZE in operation > > /tmp/ccO18745.s:1722: Error: undefined symbol L0 in operation > > /tmp/ccO18745.s:1722: Error: undefined symbol PDESIZE in operation > > /tmp/ccO18745.s:1928: Error: undefined symbol UPAGES in operation > > /tmp/ccO18745.s:1928: Error: undefined symbol PAGE_SIZE in operation > > /tmp/ccO18745.s:2316: Error: undefined symbol BI_ESYMTAB in operation > > /tmp/ccO18745.s:2321: Error: undefined symbol BI_SYMTAB in operation > > /tmp/ccO18745.s:2322: Error: undefined symbol BI_ESYMTAB in operation > > /tmp/ccO18745.s:2326: Error: undefined symbol BI_KERNEND in operation > > /tmp/ccO18745.s:2338: Error: undefined symbol PAGE_SIZE in operation > > /tmp/ccO18745.s:2338: Error: undefined symbol PAGE_SIZE in operation > > /tmp/ccO18745.s:2342: Error: undefined symbol PAGE_SIZE in operation > > /tmp/ccO18745.s:2342: Error: undefined symbol PAGE_SIZE in operation > > /tmp/ccO18745.s:2346: Error: undefined symbol UPAGES in operation > > /tmp/ccO18745.s:2346: Error: undefined symbol PAGE_SIZE in operation > > /tmp/ccO18745.s:2346: Error: undefined symbol UPAGES in operation > > /tmp/ccO18745.s:2346: Error: undefined symbol PAGE_SIZE in operation > > /tmp/ccO18745.s:2351: Error: undefined symbol PAGE_SIZE in operation > > /tmp/ccO18745.s:2351: Error: undefined symbol PAGE_SIZE in operation > > /tmp/ccO18745.s:2354: Error: undefined symbol PAGE_SIZE in operation > > /tmp/ccO18745.s:2354: Error: undefined symbol PAGE_SIZE in operation > > /tmp/ccO18745.s:2411: Error: undefined symbol PAGE_SHIFT in operation > > /tmp/ccO18745.s:2427: Error: undefined symbol PAGE_SHIFT in operation > > /tmp/ccO18745.s:2428: Error: undefined symbol PAGE_SHIFT in operation > > /tmp/ccO18745.s:1854: Error: Subtraction of two symbols in different > > sections ".tmpstk" {.data section} - "KERNBASE" {*UND* section} at file > > address 28. > > /tmp/ccO18745.s:1877: Error: Subtraction of two symbols in different > > sections "end" {*UND* section} - "KERNBASE" {*UND* section} at file > > address 38. > > /tmp/ccO18745.s:1878: Error: Subtraction of two symbols in different > > sections "edata" {*UND* section} - "KERNBASE" {*UND* section} at file > > address 43. > > /tmp/ccO18745.s:1890: Error: Subtraction of two symbols in different > > sections "cpu_feature" {.data section} - "KERNBASE" {*UND* section} at > > file address 61. > > /tmp/ccO18745.s:1906: Error: Subtraction of two symbols in different > > sections "IdlePTD" {.data section} - "KERNBASE" {*UND* section} at file > > address 81. > > /tmp/ccO18745.s:2115: Error: Subtraction of two symbols in different > > sections "kernelname" {*UND* section} - "KERNBASE" {*UND* section} at f= ile > > address 371. > > /tmp/ccO18745.s:2143: Error: Subtraction of two symbols in different > > sections "bootinfo" {.data section} - "KERNBASE" {*UND* section} at file > > address 411. > > /tmp/ccO18745.s:2163: Error: Subtraction of two symbols in different > > sections "boothowto" {*UND* section} - "KERNBASE" {*UND* section} at fi= le > > address 435. > > /tmp/ccO18745.s:2165: Error: Subtraction of two symbols in different > > sections "bootdev" {*UND* section} - "KERNBASE" {*UND* section} at file > > address 443. > > /tmp/ccO18745.s:2203: Error: Subtraction of two symbols in different > > sections "cpu" {.data section} - "KERNBASE" {*UND* section} at file > > address 495. > > /tmp/ccO18745.s:2208: Error: Subtraction of two symbols in different > > sections "cpu" {.data section} - "KERNBASE" {*UND* section} at file > > address 511. > > /tmp/ccO18745.s:2209: Error: Subtraction of two symbols in different > > sections "cpu_vendor" {.data section} - "KERNBASE" {*UND* section} at f= ile > > address 521. > > /tmp/ccO18745.s:2210: Error: Subtraction of two symbols in different > > sections "cpu_vendor" {.data section} - "KERNBASE" {*UND* section} at f= ile > > address 531. > > /tmp/ccO18745.s:2211: Error: Subtraction of two symbols in different > > sections "cpu_vendor" {.data section} - "KERNBASE" {*UND* section} at f= ile > > address 541. > > /tmp/ccO18745.s:2212: Error: Subtraction of two symbols in different > > sections "cpu_vendor" {.data section} - "KERNBASE" {*UND* section} at f= ile > > address 551. > > /tmp/ccO18745.s:2231: Error: Subtraction of two symbols in different > > sections "cpu" {.data section} - "KERNBASE" {*UND* section} at file > > address 592. > > /tmp/ccO18745.s:2258: Error: Subtraction of two symbols in different > > sections "cpu_vendor" {.data section} - "KERNBASE" {*UND* section} at f= ile > > address 627. > > /tmp/ccO18745.s:2259: Error: Subtraction of two symbols in different > > sections "cpu_vendor" {.data section} - "KERNBASE" {*UND* section} at f= ile > > address 637. > > /tmp/ccO18745.s:2260: Error: Subtraction of two symbols in different > > sections "cpu_vendor" {.data section} - "KERNBASE" {*UND* section} at f= ile > > address 647. > > /tmp/ccO18745.s:2266: Error: Subtraction of two symbols in different > > sections "cpu_high" {.data section} - "KERNBASE" {*UND* section} at file > > address 662. > > /tmp/ccO18745.s:2267: Error: Subtraction of two symbols in different > > sections "cpu_vendor" {.data section} - "KERNBASE" {*UND* section} at f= ile > > address 668. > > /tmp/ccO18745.s:2268: Error: Subtraction of two symbols in different > > sections "cpu_vendor" {.data section} - "KERNBASE" {*UND* section} at f= ile > > address 674. > > /tmp/ccO18745.s:2269: Error: Subtraction of two symbols in different > > sections "cpu_vendor" {.data section} - "KERNBASE" {*UND* section} at f= ile > > address 680. > > /tmp/ccO18745.s:2270: Error: Subtraction of two symbols in different > > sections "cpu_vendor" {.data section} - "KERNBASE" {*UND* section} at f= ile > > address 686. > > /tmp/ccO18745.s:2274: Error: Subtraction of two symbols in different > > sections "cpu_id" {.data section} - "KERNBASE" {*UND* section} at file > > address 699. > > /tmp/ccO18745.s:2275: Error: Subtraction of two symbols in different > > sections "cpu_feature" {.data section} - "KERNBASE" {*UND* section} at > > file address 705. > > /tmp/ccO18745.s:2282: Error: Subtraction of two symbols in different > > sections "cpu" {.data section} - "KERNBASE" {*UND* section} at file > > address 722. > > /tmp/ccO18745.s:2288: Error: Subtraction of two symbols in different > > sections "cpu" {.data section} - "KERNBASE" {*UND* section} at file > > address 739. > > /tmp/ccO18745.s:2292: Error: Subtraction of two symbols in different > > sections "cpu" {.data section} - "KERNBASE" {*UND* section} at file > > address 751. > > /tmp/ccO18745.s:2305: Error: Subtraction of two symbols in different > > sections "cpu_feature" {.data section} - "KERNBASE" {*UND* section} at > > file address 762. > > /tmp/ccO18745.s:2313: Error: Subtraction of two symbols in different > > sections "end" {*UND* section} - "KERNBASE" {*UND* section} at file > > address 784. > > /tmp/ccO18745.s:2316: Error: Negative of non-absolute symbol KERNBASE > > /tmp/ccO18745.s:2321: Error: Negative of non-absolute symbol KERNBASE > > /tmp/ccO18745.s:2322: Error: Negative of non-absolute symbol KERNBASE > > /tmp/ccO18745.s:2326: Error: Negative of non-absolute symbol KERNBASE > > /tmp/ccO18745.s:2334: Error: Subtraction of two symbols in different > > sections ".data" {.data section} - "KERNBASE" {*UND* section} at file > > address 843. > > /tmp/ccO18745.s:2335: Error: Subtraction of two symbols in different > > sections ".data" {.data section} - "KERNBASE" {*UND* section} at file > > address 849. > > /tmp/ccO18745.s:2338: Error: Subtraction of two symbols in different > > sections ".data" {.data section} - "KERNBASE" {*UND* section} at file > > address 855. > > /tmp/ccO18745.s:2338: Error: Subtraction of two symbols in different > > sections ".data" {.data section} - "KERNBASE" {*UND* section} at file > > address 867. > > /tmp/ccO18745.s:2339: Error: Subtraction of two symbols in different > > sections ".data" {.data section} - "KERNBASE" {*UND* section} at file > > address 885. > > /tmp/ccO18745.s:2342: Error: Subtraction of two symbols in different > > sections ".data" {.data section} - "KERNBASE" {*UND* section} at file > > address 891. > > /tmp/ccO18745.s:2342: Error: Subtraction of two symbols in different > > sections ".data" {.data section} - "KERNBASE" {*UND* section} at file > > address 903. > > /tmp/ccO18745.s:2343: Error: Subtraction of two symbols in different > > sections "IdlePTD" {.data section} - "KERNBASE" {*UND* section} at file > > address 921. > > /tmp/ccO18745.s:2346: Error: Subtraction of two symbols in different > > sections ".data" {.data section} - "KERNBASE" {*UND* section} at file > > address 927. > > /tmp/ccO18745.s:2346: Error: Subtraction of two symbols in different > > sections ".data" {.data section} - "KERNBASE" {*UND* section} at file > > address 939. > > /tmp/ccO18745.s:2347: Error: Subtraction of two symbols in different > > sections ".data" {.data section} - "KERNBASE" {*UND* section} at file > > address 957. > > /tmp/ccO18745.s:2349: Error: Subtraction of two symbols in different > > sections "proc0paddr" {.data section} - "KERNBASE" {*UND* section} at f= ile > > address 969. > > /tmp/ccO18745.s:2351: Error: Subtraction of two symbols in different > > sections ".data" {.data section} - "KERNBASE" {*UND* section} at file > > address 975. > > /tmp/ccO18745.s:2351: Error: Subtraction of two symbols in different > > sections ".data" {.data section} - "KERNBASE" {*UND* section} at file > > address 987. > > /tmp/ccO18745.s:2352: Error: Subtraction of two symbols in different > > sections ".data" {.data section} - "KERNBASE" {*UND* section} at file > > address 1005. > > /tmp/ccO18745.s:2354: Error: Subtraction of two symbols in different > > sections ".data" {.data section} - "KERNBASE" {*UND* section} at file > > address 1011. > > /tmp/ccO18745.s:2354: Error: Subtraction of two symbols in different > > sections ".data" {.data section} - "KERNBASE" {*UND* section} at file > > address 1023. > > /tmp/ccO18745.s:2355: Error: Subtraction of two symbols in different > > sections "vm86pa" {.data section} - "KERNBASE" {*UND* section} at file > > address 1041. > > /tmp/ccO18745.s:2357: Error: Subtraction of two symbols in different > > sections "vm86paddr" {.data section} - "KERNBASE" {*UND* section} at fi= le > > address 1053. > > /tmp/ccO18745.s:2372: Error: Subtraction of two symbols in different > > sections "cpu_feature" {.data section} - "KERNBASE" {*UND* section} at > > file address 1063. > > /tmp/ccO18745.s:2377: Error: Subtraction of two symbols in different > > sections "etext" {*UND* section} - "KERNBASE" {*UND* section} at file > > address 1080. > > /tmp/ccO18745.s:2380: Error: Subtraction of two symbols in different > > sections ".data" {.data section} - "KERNBASE" {*UND* section} at file > > address 1103. > > /tmp/ccO18745.s:2383: Error: Subtraction of two symbols in different > > sections "etext" {*UND* section} - "KERNBASE" {*UND* section} at file > > address 1125. > > /tmp/ccO18745.s:2389: Error: Subtraction of two symbols in different > > sections "cpu_feature" {.data section} - "KERNBASE" {*UND* section} at > > file address 1146. > > /tmp/ccO18745.s:2394: Error: Subtraction of two symbols in different > > sections ".data" {.data section} - "KERNBASE" {*UND* section} at file > > address 1164. > > /tmp/ccO18745.s:2397: Error: Subtraction of two symbols in different > > sections ".data" {.data section} - "KERNBASE" {*UND* section} at file > > address 1183. > > /tmp/ccO18745.s:2400: Error: Subtraction of two symbols in different > > sections "IdlePTD" {.data section} - "KERNBASE" {*UND* section} at file > > address 1205. > > /tmp/ccO18745.s:2402: Error: Subtraction of two symbols in different > > sections ".data" {.data section} - "KERNBASE" {*UND* section} at file > > address 1224. > > /tmp/ccO18745.s:2405: Error: Subtraction of two symbols in different > > sections ".data" {.data section} - "KERNBASE" {*UND* section} at file > > address 1247. > > /tmp/ccO18745.s:2407: Error: Subtraction of two symbols in different > > sections ".data" {.data section} - "KERNBASE" {*UND* section} at file > > address 1266. > > /tmp/ccO18745.s:2412: Error: Subtraction of two symbols in different > > sections ".data" {.data section} - "KERNBASE" {*UND* section} at file > > address 1308. > > /tmp/ccO18745.s:2415: Error: Subtraction of two symbols in different > > sections ".data" {.data section} - "KERNBASE" {*UND* section} at file > > address 1331. > > /tmp/ccO18745.s:2417: Error: Subtraction of two symbols in different > > sections ".data" {.data section} - "KERNBASE" {*UND* section} at file > > address 1350. > > /tmp/ccO18745.s:2423: Error: Subtraction of two symbols in different > > sections "vm86pa" {.data section} - "KERNBASE" {*UND* section} at file > > address 1392. > > /tmp/ccO18745.s:2429: Error: Subtraction of two symbols in different > > sections "vm86pa" {.data section} - "KERNBASE" {*UND* section} at file > > address 1434. > > /tmp/ccO18745.s:2435: Error: Subtraction of two symbols in different > > sections ".data" {.data section} - "KERNBASE" {*UND* section} at file > > address 1457. > > /tmp/ccO18745.s:2438: Error: Subtraction of two symbols in different > > sections "IdlePTD" {.data section} - "KERNBASE" {*UND* section} at file > > address 1473. > > /tmp/ccO18745.s:2441: Error: Subtraction of two symbols in different > > sections ".data" {.data section} - "KERNBASE" {*UND* section} at file > > address 1496. > > /tmp/ccO18745.s:2444: Error: Subtraction of two symbols in different > > sections "IdlePTD" {.data section} - "KERNBASE" {*UND* section} at file > > address 1515. > > /tmp/ccO18745.s:2447: Error: Subtraction of two symbols in different > > sections "IdlePTD" {.data section} - "KERNBASE" {*UND* section} at file > > address 1538. > > /tmp/ccO18745.s:2450: Error: Subtraction of two symbols in different > > sections "IdlePTD" {.data section} - "KERNBASE" {*UND* section} at file > > address 1557. > > *** Error code 1 > >=20 > > Stop in /u/obj/usr/src/sys/SHALL. > > *** Error code 1 > >=20 > > Stop in /usr/src. > > *** Error code 1 > >=20 > > Stop in /usr/src. > > shall# > >=20 > > ---------------------------------------------------------------------- > > Name: SHALL > > SHALL Type: Plain Text (text/plain) > > Encoding: quoted-printable > >=20 > > Part 1.2Type: application/pgp-signature >=20 > --=20 > Kent Stewart > Richland, WA >=20 > mailto:kstewart@3-cities.com > http://kstewart.urx.com/kstewart/index.html --5mCyUwZo2JvN/JJP Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.0 (GNU/Linux) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjpzGyoACgkQ7uV99pHLOSIZbQCfbZZtOk4NgJjpr7Px8Sgij9Mo 6pMAn0TmswaHNMhbnRrS3kplye7l0vYV =pssw -----END PGP SIGNATURE----- --5mCyUwZo2JvN/JJP-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jan 27 11: 7:21 2001 Delivered-To: freebsd-stable@freebsd.org Received: from merlin.prod.itd.earthlink.net (merlin.prod.itd.earthlink.net [207.217.120.156]) by hub.freebsd.org (Postfix) with ESMTP id 06AFA37B400 for ; Sat, 27 Jan 2001 11:07:03 -0800 (PST) Received: from dionysos.yi.org (1Cust11.tnt8.phoenix.az.da.uu.net [63.14.200.11]) by merlin.prod.itd.earthlink.net (8.9.3-EL_1_3/8.9.3) with ESMTP id LAA04285; Sat, 27 Jan 2001 11:06:59 -0800 (PST) Received: by dionysos.yi.org (Postfix, from userid 1001) id 4C17B1C56; Sat, 27 Jan 2001 12:05:37 -0700 (MST) Date: Sat, 27 Jan 2001 12:05:37 -0700 From: Dionysos To: Wolfgang Zenker Cc: james@m-a.net, Kris Kennaway , freebsd-stable@FreeBSD.ORG Subject: Re: Buildworld failure using two disks Message-ID: <20010127120537.A420@dionysos.yi.org> References: <20010126232127.A294@dionysos.yi.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from wolfgang@lyxys.ka.sub.org on Sat, Jan 27, 2001 at 06:59:38PM +0100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Jan 27, 2001 at 06:59:38PM +0100, Wolfgang Zenker wrote: > Hi, > > > On Fri, Jan 26, 2001 at 08:01:38PM -0800, Kris Kennaway wrote: > >> On Fri, Jan 26, 2001 at 03:17:48PM -0700, Dionysos wrote: > >>> [..] > > >>> Using the latest -stable source I get an error at the beginning of > >>> the build only when I have /usr/obj mounted on a separate physical > >>> disk. > > >> It should work. Try blowing away /usr/obj. > > > already did more than once. To expand on this a bit, I tried doing some links > > in a context outside of make buildworld. Symbolic links do work across > > filesystems still but I continue to get errors when trying to make symbolic > > links across filesystems that are on different disks. I've contemplated > > sending in a PR for it, but I'll still entertain that something wierd (and > > fixable) is going on with my system in particular. Here's some output from my > > last try to link as well as uname -a output if it'll help... > > > dionysos# ln -sf /root/.login /usr/obj/.login.link.test > > ln: /usr/obj/.login.link.test: Operation not supported > > Could we see the output of "mount" please? Called without parameters it > should tell you some details about all mounted filesystems. > > Wolfgang > > Problem solved actually and I should have probably known better. When I created my /usr/obj partition, I had done so using partition magic and just created an msdos partition. Apparently, though the man page for ln doesn't state this, you can't make symbolic links across file systems of different type (or at least involving msdosfs). Once I reformatted it to ufs, it all worked fine. James To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jan 27 12: 3:48 2001 Delivered-To: freebsd-stable@freebsd.org Received: from nevermind.kiev.ua (office.imt.com.ua [212.109.53.33]) by hub.freebsd.org (Postfix) with ESMTP id 414C337B400 for ; Sat, 27 Jan 2001 12:03:29 -0800 (PST) Received: (from never@localhost) by nevermind.kiev.ua (8.11.1/8.11.1) id f0RK3Db37574; Sat, 27 Jan 2001 22:03:13 +0200 (EET) (envelope-from never) Date: Sat, 27 Jan 2001 22:02:57 +0200 From: Nevermind To: Kal Torak Cc: FreeBSD-stable Subject: Re: ipfw forwarding Message-ID: <20010127220257.B28504@nevermind.kiev.ua> References: <3A72CB47.7A5DD83@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: <3A72CB47.7A5DD83@quake.com.au>; from kaltorak@quake.com.au on Sun, Jan 28, 2001 at 12:21:11AM +1100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, Kal Torak! On Sun, Jan 28, 2001 at 12:21:11AM +1100, you wrote: > Ok, so I have another FreeBSD box running a server on port 27015/udp > and I put a rule in my ipfw list saying "${fwcmd} 600 fwd 10.0.0.4 udp from > any to any 27015" this seems like it should do the job, and when I connect should this be: ${fwcmd} 600 fwd 10.0.0.4,27015 udp from any to any 27015 ? Correct me if I wrong... -- Alexandr P. Kovalenko http://nevermind.kiev.ua/ NEVE-RIPE To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jan 27 12:13:30 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 C500D37B400 for ; Sat, 27 Jan 2001 12:13:12 -0800 (PST) Received: from [203.164.12.28] by www.quake.com.au (NTMail 4.30.0012/AH9370.63.d1acf55c) with ESMTP id dqwsaaaa for ; Sun, 28 Jan 2001 07:21:50 +1100 Message-ID: <3A732BE9.F559820D@quake.com.au> Date: Sun, 28 Jan 2001 07:13:29 +1100 From: Kal Torak X-Mailer: Mozilla 4.73 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Nevermind Cc: FreeBSD-stable Subject: Re: ipfw forwarding References: <3A72CB47.7A5DD83@quake.com.au> <20010127220257.B28504@nevermind.kiev.ua> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nevermind wrote: > > Hello, Kal Torak! > > On Sun, Jan 28, 2001 at 12:21:11AM +1100, you wrote: > > > Ok, so I have another FreeBSD box running a server on port 27015/udp > > and I put a rule in my ipfw list saying "${fwcmd} 600 fwd 10.0.0.4 udp from > > any to any 27015" this seems like it should do the job, and when I connect > should this be: > ${fwcmd} 600 fwd 10.0.0.4,27015 udp from any to any 27015 > ? > > Correct me if I wrong... AFAIK you only need to specify the destination port if its different from the source... I just dont get this... it *should* work from what I know... yet it doesnt... I am considering recompiling with ipf and see if I can get that to do what I want.. but thats a bit of a pain since ipfw should be able to do this... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jan 27 12:26:36 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 C454637B400 for ; Sat, 27 Jan 2001 12:26:18 -0800 (PST) Received: from [203.164.12.28] by www.quake.com.au (NTMail 4.30.0012/AH9370.63.d1acf55c) with ESMTP id gqwsaaaa for ; Sun, 28 Jan 2001 07:34:55 +1100 Message-ID: <3A732EFB.E7E743BA@quake.com.au> Date: Sun, 28 Jan 2001 07:26:35 +1100 From: Kal Torak X-Mailer: Mozilla 4.73 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: FreeBSD-stable Subject: Re: ipfw forwarding (more info) References: <3A72CB47.7A5DD83@quake.com.au> <20010127220257.B28504@nevermind.kiev.ua> <3A732BE9.F559820D@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 After some more fiddling around, I have noticed that the ipfw rule is hit, but nothing seems to happen... The data just continues on to the local port instead of being forwarded to the remote one... Maybe I am missing something that needs to be loaded for this to work? Kal Torak wrote: > > Nevermind wrote: > > > > Hello, Kal Torak! > > > > On Sun, Jan 28, 2001 at 12:21:11AM +1100, you wrote: > > > > > Ok, so I have another FreeBSD box running a server on port 27015/udp > > > and I put a rule in my ipfw list saying "${fwcmd} 600 fwd 10.0.0.4 udp from > > > any to any 27015" this seems like it should do the job, and when I connect > > should this be: > > ${fwcmd} 600 fwd 10.0.0.4,27015 udp from any to any 27015 > > ? > > > > Correct me if I wrong... > > AFAIK you only need to specify the destination port if its different from the > source... > I just dont get this... it *should* work from what I know... yet it doesnt... > > I am considering recompiling with ipf and see if I can get that to do what I > want.. but thats a bit of a pain since ipfw should be able to do this... > > 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 27 12:32:18 2001 Delivered-To: freebsd-stable@freebsd.org Received: from arianna.webcraft99.alt (unknown [202.151.212.7]) by hub.freebsd.org (Postfix) with ESMTP id 39F5C37B400 for ; Sat, 27 Jan 2001 12:32:00 -0800 (PST) Received: from jenna.webcraft99.alt (jenna.webcraft99.alt [192.168.1.22]) by arianna.webcraft99.alt (AriAnnA) with ESMTP id A48737C6E; Sun, 28 Jan 2001 04:57:02 +0800 (MYT) Received: from webcraft99.com (lexus.webcraft99.alt [192.168.1.31]) by jenna.webcraft99.alt (JEnnA) with ESMTP id BE0FE3DB2; Sun, 28 Jan 2001 04:36:38 +0800 (MYT) Message-ID: <3A733156.4BF6465@webcraft99.com> Date: Sun, 28 Jan 2001 04:36:38 +0800 From: Feisal Umar Reply-To: aeefyu@webcraft99.com Organization: Webcraft Sdn Bhd (http://www.webcraft99.com) X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Pete Fritchman , freebsd-stable@freebsd.org Subject: Re: IPFILTER 3.4.16 and FreeBSD-4.2 References: <3A72DEA1.A31EC401@webcraft99.com> <20010127120755.A76777@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 Those directives are omitted from my rc.conf as they are the default rules as per /etc/defaults/rc.conf. /etc/ipf.rules and /etc/ipnat.rules do exist --Feisal Pete Fritchman wrote: > > ++ 27/01/01 22:43 +0800 - Feisal Umar: > >Hi > > > >Are the startup scripts for FreeBSD-4.2 broken for IPFILTER/IPNAT > >support? > >I have a gateway machine configured with IPFILTER/IPNAT via the rc.conf > >with the following entries: > >ipfilter_enable="YES" > >ipfilter_flags="" > >ipnat_enable="YES" > >ipmon_enable="YES" > > > > You might need: > > ipfilter_rules="/etc/ipf.rules" > ipnat_rules="/etc/ipnat.rules" > > [...] > > -pete. > > > > >-- > >Feisal Umar > >Webcraft Sdn Bhd - http://www.webcraft99.com > > > >You cannot kill time without injuring eternity. > > -- > Pete Fritchman > Databits Network Services, Inc. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- Feisal Umar Webcraft Sdn Bhd - http://www.webcraft99.com Did I say 2? I lied. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jan 27 12:51:17 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail1.javanet.com (mail1.javanet.com [205.219.162.10]) by hub.freebsd.org (Postfix) with ESMTP id 9DBB537B69E for ; Sat, 27 Jan 2001 12:50:54 -0800 (PST) Received: from wintermute.sekt7.org (209-6-248-127.c3-0.lex-ubr1.sbo-lex.ma.cable.rcn.com [209.6.248.127]) by mail1.javanet.com (8.9.3/8.9.2) with ESMTP id PAA17758 for ; Sat, 27 Jan 2001 15:50:48 -0500 (EST) Date: Sat, 27 Jan 2001 15:54:18 -0500 (EST) From: Evan S X-Sender: kaworu@wintermute.sekt7 To: freebsd-stable@freebsd.org Subject: Strange network behavior. 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, I'm not sure if this belongs in freebsd-stable, -security, or -misc, so I'll take my chances and post it here, in -stable. I was fooling around with nmap one day, reading the man page, and stumbled upon the -D, decoy option. So, to test it out, I nmapped one of my boxen with the decoys of www.daemonnews.org, www.slashdot.org, and acs.bu.edu. It worked, and it was kind of neat. However, after it completed the nmap, I am now unable to connect to www.slashdot.org, or www.daemonnews.org. So I began investigating a bit. Heres some of the weird things that are happening. The internal interface on my router has two ip addresses, 169.69.7.1, and 169.69.6.1. I have all of my computers using the gateway 169.69.6.1, however, when I traceroute, it sends the packets to its alias 169.69.7.1. Still works though. This is what happens when I traceroute www.slashdot.org, and the same for acs.bu.edu, or daily.daemonnews.org. Thankfully, I can connect to acs2.bu.edu and so on. kaworu@teqnix kern> traceroute www.slashdot.org traceroute to slashdot.org (64.28.67.48), 30 hops max, 40 byte packets 1 169.69.7.1 (169.69.7.1) 1.440 ms 1.439 ms 1.387 ms 2 149.112.50.65 (149.112.50.65) 4.668 ms 3.730 ms 3.560 ms 3 * * Here is the output from netstat -nr on my router. [kaworu@interorbos]$netstat -nr Routing tables Internet: Destination Gateway Flags Refs Use Mtu Interface default 149.112.50.65 UGS 3 2067979 1500 ep0 127/8 127.0.0.1 UGRS 0 0 32972 lo0 127.0.0.1 127.0.0.1 UH 3 62 32972 lo0 149.112.50.65 0:50:da:fb:c5:75 UHL 1 96 1500 ep0 149.112.50.98 127.0.0.1 UGHS 0 0 32972 lo0 169.69.6/24 link#2 UC 0 0 1500 ep1 169.69.6.2 0:a0:cc:73:d1:a7 UHL 0 836 1500 ep1 169.69.6.3 0:a0:cc:63:e1:8f UHL 2 1694450 1500 ep1 169.69.6.5 8:0:20:c:f5:86 UHL 0 123 1500 ep1 169.69.7/24 link#2 UC 0 0 1500 ep1 169.69.7.2 0:40:5:4e:24:91 UHL 0 1133 1500 ep1 209.6.248/23 link#1 UC 0 0 1500 ep0 209.6.248.1 0:30:19:3b:a5:54 UHL 0 0 1500 ep0 209.6.248.127 127.0.0.1 UGHS 0 0 32972 lo0 224/4 127.0.0.1 URS 0 0 32972 lo0 Uname -ap output for the computer I nmapped from: FreeBSD teqnix.sekt7.org 4.2-STABLE FreeBSD 4.2-STABLE #20: Sat Jan 6 10:09:59 GMT 2001 kaworu@teqnix.sekt7.org:/usr/src/sys/compile/KAWORU i386 Thanks in advance, Evan Sarmiento (kaworu@sektor7.ath.cx) http://sekt7.org/es To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jan 27 13:37:18 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 B697137B401 for ; Sat, 27 Jan 2001 13:37:01 -0800 (PST) Received: (from bjj@localhost) by saturn.home.ben.com (8.11.1/8.9.3) id f0RLavv28020; Sat, 27 Jan 2001 13:36:57 -0800 (PST) From: Ben Jackson Message-Id: <200101272136.f0RLavv28020@saturn.home.ben.com> Subject: Re: ipfw forwarding In-Reply-To: <3A72CB47.7A5DD83@quake.com.au> from Kal Torak at "Jan 28, 2001 00:21:11 am" To: Kal Torak Date: Sat, 27 Jan 2001 13:36:57 -0800 (PST) Cc: FreeBSD-stable 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 > Ok, so I have another FreeBSD box running a server on port 27015/udp > and I put a rule in my ipfw list saying "${fwcmd} 600 fwd 10.0.0.4 udp from > any to any 27015" this seems like it should do the job, and when I connect You should be changing your nat command line to include: -redirect_port udp 10.0.0.4 --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 27 13:53:18 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 48E0637B400 for ; Sat, 27 Jan 2001 13:52:52 -0800 (PST) Received: (qmail 6424 invoked by uid 0); 27 Jan 2001 21:52:45 -0000 Received: from unknown (HELO urx.com) (206.159.132.160) by mail.urx.com with SMTP; 27 Jan 2001 21:52:45 -0000 Message-ID: <3A73432D.3D8C2C74@urx.com> Date: Sat, 27 Jan 2001 13:52:45 -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: anarcat Cc: freebsd-stable@freebsd.org Subject: Re: Can't build kernel under stable-2000.12.31 References: <20010126201248.A1832@dojo.tao.ca> <3A723980.DEDEE04E@urx.com> <20010127140203.A26460@dojo.tao.ca> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG anarcat wrote: > > Ok. I do not understand very clearly why, but: > > # rm -rf /sys/compile/SHALL > > and then using the traditional "config" method (config && cd ... && make > depend && make && make install) works. > > Why can't buildkernel do this by itself? They are setting it up to do that but for right now it doesn't work. There was a thread that I was following on this subject. For right now, the buildkernel has to be looked at as if it is doing a cross compile and it totally depends on /usr/obj being populated. The config method is used for updating an existing system or fine tuning a existing system. Around the time 4.0 was upgraded to 4.1, there was a switch to a new version of the utilities and such. You had to use the buildkernel for these to be done properly. That was when I first saw the locore.s message. It wasn't too long after upgrading to 4.1 that I developed a simple script to do the cvsup and upgrade userland and my kernel. It only stops if something is broken and the rest of the time it finishes with the two "makewhatis" messages on a telnet session. I rarely do a build on the system console. A lot of the time I also exit KDE-2 on the system being upgraded, which gives the build process around 50MB more memory to play with. Running in a pure terminal session reminds me too much of MSDOS :). The config method has additional benefits. For example, once you have built a kernel using the config method, it only has to make the code that you have added using your kernel config file. The 2nd make and on can build much faster then the buildkernel appears to. The buildkernel seems to default to doing a make clean and then do the compiles. Kent > > thanks. > > A. > > On Fri, Jan 26, 2001 at 06:59:12PM -0800, Big Brother made Kent Stewart write: > > > > > > anarcat wrote: > > > > > > Hi! > > > > > > (please CC: me, I'm not on the list) > > > > > > Building a custom kernel under freebsd-stable (cvsup'd and made world on > > > 2000-12-31) fails with the following, any idea why? > > > > This error usually occurs beause you didn't do a buildworld to > > populate /usr/obj first. Read /usr/src/UPDATING because the sequence > > isn't an option. If you already have a current userland, then the > > choice can include the config method. They way it looks, you mixed > > your world's and that doesn't work. > > > > Kent > > > > > > > > shall# make KERNEL=SHALL buildkernel installkernel > > > ... > > > ===> wi > > > @ -> /usr/src/sys > > > machine -> /usr/src/sys/i386/include > > > perl @/kern/makedevops.pl -h @/kern/device_if.m > > > perl @/kern/makedevops.pl -h @/kern/bus_if.m > > > rm -f .depend > > > mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -I- -I. -I@ > > > -I@/../include -I/usr/obj/usr/src/i386/usr/include > > > /usr/src/sys/modules/wi/../../i386/isa/if_wi.c > > > cd /usr/obj/usr/src/sys/SHALL; MAKEOBJDIRPREFIX=/usr/obj > > > COMPILER_PATH=/usr/obj/usr/src/i386/usr/libexec:/usr/obj/usr/src/i386/usr/bin > > > LIBRARY_PATH=/usr/obj/usr/src/i386/usr/lib:/usr/obj/usr/src/i386/usr/lib > > > OBJFORMAT_PATH=/usr/obj/usr/src/i386/usr/libexec > > > PERL5LIB=/usr/obj/usr/src/i386/usr/libdata/perl/5.00503 > > > DESTDIR=/usr/obj/usr/src/i386 INSTALL="sh /usr/src/tools/install.sh" > > > 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 > > > MACHINE=i386 make KERNEL=kernel all > > > cc -c -x assembler-with-cpp -DLOCORE -O -Wall -Wredundant-decls > > > -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith > > > -Winline -Wcast-qual -fformat-extensions -ansi -g -nostdinc -I- -I. > > > -I/usr/src/sys -I/usr/src/sys/../include -D_KERNEL -include opt_global.h > > > -elf -mpreferred-stack-boundary=2 /usr/src/sys/i386/i386/locore.s > > > /tmp/ccO18745.s: Assembler messages: > > > /tmp/ccO18745.s:1744: Error: .space specifies non-absolute value > > > /tmp/ccO18745.s:2455: Error: undefined symbol L0 in operation setting > > > PTmap > > > /tmp/ccO18745.s:2455: Error: undefined symbol PDRSHIFT in operation > > > setting PTmap > > > /tmp/ccO18745.s:1712: Error: undefined symbol L0 in operation > > > /tmp/ccO18745.s:1712: Error: undefined symbol PAGE_SIZE in operation > > > /tmp/ccO18745.s:1713: Error: undefined symbol L0 in operation > > > /tmp/ccO18745.s:1713: Error: undefined symbol PDESIZE in operation > > > /tmp/ccO18745.s:2455: Error: undefined symbol L0 in operation setting > > > APTmap > > > /tmp/ccO18745.s:2455: Error: undefined symbol PDRSHIFT in operation > > > setting APTmap > > > /tmp/ccO18745.s:1721: Error: undefined symbol L0 in operation > > > /tmp/ccO18745.s:1721: Error: undefined symbol PAGE_SIZE in operation > > > /tmp/ccO18745.s:1722: Error: undefined symbol L0 in operation > > > /tmp/ccO18745.s:1722: Error: undefined symbol PDESIZE in operation > > > /tmp/ccO18745.s:1928: Error: undefined symbol UPAGES in operation > > > /tmp/ccO18745.s:1928: Error: undefined symbol PAGE_SIZE in operation > > > /tmp/ccO18745.s:2316: Error: undefined symbol BI_ESYMTAB in operation > > > /tmp/ccO18745.s:2321: Error: undefined symbol BI_SYMTAB in operation > > > /tmp/ccO18745.s:2322: Error: undefined symbol BI_ESYMTAB in operation > > > /tmp/ccO18745.s:2326: Error: undefined symbol BI_KERNEND in operation > > > /tmp/ccO18745.s:2338: Error: undefined symbol PAGE_SIZE in operation > > > /tmp/ccO18745.s:2338: Error: undefined symbol PAGE_SIZE in operation > > > /tmp/ccO18745.s:2342: Error: undefined symbol PAGE_SIZE in operation > > > /tmp/ccO18745.s:2342: Error: undefined symbol PAGE_SIZE in operation > > > /tmp/ccO18745.s:2346: Error: undefined symbol UPAGES in operation > > > /tmp/ccO18745.s:2346: Error: undefined symbol PAGE_SIZE in operation > > > /tmp/ccO18745.s:2346: Error: undefined symbol UPAGES in operation > > > /tmp/ccO18745.s:2346: Error: undefined symbol PAGE_SIZE in operation > > > /tmp/ccO18745.s:2351: Error: undefined symbol PAGE_SIZE in operation > > > /tmp/ccO18745.s:2351: Error: undefined symbol PAGE_SIZE in operation > > > /tmp/ccO18745.s:2354: Error: undefined symbol PAGE_SIZE in operation > > > /tmp/ccO18745.s:2354: Error: undefined symbol PAGE_SIZE in operation > > > /tmp/ccO18745.s:2411: Error: undefined symbol PAGE_SHIFT in operation > > > /tmp/ccO18745.s:2427: Error: undefined symbol PAGE_SHIFT in operation > > > /tmp/ccO18745.s:2428: Error: undefined symbol PAGE_SHIFT in operation > > > /tmp/ccO18745.s:1854: Error: Subtraction of two symbols in different > > > sections ".tmpstk" {.data section} - "KERNBASE" {*UND* section} at file > > > address 28. > > > /tmp/ccO18745.s:1877: Error: Subtraction of two symbols in different > > > sections "end" {*UND* section} - "KERNBASE" {*UND* section} at file > > > address 38. > > > /tmp/ccO18745.s:1878: Error: Subtraction of two symbols in different > > > sections "edata" {*UND* section} - "KERNBASE" {*UND* section} at file > > > address 43. > > > /tmp/ccO18745.s:1890: Error: Subtraction of two symbols in different > > > sections "cpu_feature" {.data section} - "KERNBASE" {*UND* section} at > > > file address 61. > > > /tmp/ccO18745.s:1906: Error: Subtraction of two symbols in different > > > sections "IdlePTD" {.data section} - "KERNBASE" {*UND* section} at file > > > address 81. > > > /tmp/ccO18745.s:2115: Error: Subtraction of two symbols in different > > > sections "kernelname" {*UND* section} - "KERNBASE" {*UND* section} at file > > > address 371. > > > /tmp/ccO18745.s:2143: Error: Subtraction of two symbols in different > > > sections "bootinfo" {.data section} - "KERNBASE" {*UND* section} at file > > > address 411. > > > /tmp/ccO18745.s:2163: Error: Subtraction of two symbols in different > > > sections "boothowto" {*UND* section} - "KERNBASE" {*UND* section} at file > > > address 435. > > > /tmp/ccO18745.s:2165: Error: Subtraction of two symbols in different > > > sections "bootdev" {*UND* section} - "KERNBASE" {*UND* section} at file > > > address 443. > > > /tmp/ccO18745.s:2203: Error: Subtraction of two symbols in different > > > sections "cpu" {.data section} - "KERNBASE" {*UND* section} at file > > > address 495. > > > /tmp/ccO18745.s:2208: Error: Subtraction of two symbols in different > > > sections "cpu" {.data section} - "KERNBASE" {*UND* section} at file > > > address 511. > > > /tmp/ccO18745.s:2209: Error: Subtraction of two symbols in different > > > sections "cpu_vendor" {.data section} - "KERNBASE" {*UND* section} at file > > > address 521. > > > /tmp/ccO18745.s:2210: Error: Subtraction of two symbols in different > > > sections "cpu_vendor" {.data section} - "KERNBASE" {*UND* section} at file > > > address 531. > > > /tmp/ccO18745.s:2211: Error: Subtraction of two symbols in different > > > sections "cpu_vendor" {.data section} - "KERNBASE" {*UND* section} at file > > > address 541. > > > /tmp/ccO18745.s:2212: Error: Subtraction of two symbols in different > > > sections "cpu_vendor" {.data section} - "KERNBASE" {*UND* section} at file > > > address 551. > > > /tmp/ccO18745.s:2231: Error: Subtraction of two symbols in different > > > sections "cpu" {.data section} - "KERNBASE" {*UND* section} at file > > > address 592. > > > /tmp/ccO18745.s:2258: Error: Subtraction of two symbols in different > > > sections "cpu_vendor" {.data section} - "KERNBASE" {*UND* section} at file > > > address 627. > > > /tmp/ccO18745.s:2259: Error: Subtraction of two symbols in different > > > sections "cpu_vendor" {.data section} - "KERNBASE" {*UND* section} at file > > > address 637. > > > /tmp/ccO18745.s:2260: Error: Subtraction of two symbols in different > > > sections "cpu_vendor" {.data section} - "KERNBASE" {*UND* section} at file > > > address 647. > > > /tmp/ccO18745.s:2266: Error: Subtraction of two symbols in different > > > sections "cpu_high" {.data section} - "KERNBASE" {*UND* section} at file > > > address 662. > > > /tmp/ccO18745.s:2267: Error: Subtraction of two symbols in different > > > sections "cpu_vendor" {.data section} - "KERNBASE" {*UND* section} at file > > > address 668. > > > /tmp/ccO18745.s:2268: Error: Subtraction of two symbols in different > > > sections "cpu_vendor" {.data section} - "KERNBASE" {*UND* section} at file > > > address 674. > > > /tmp/ccO18745.s:2269: Error: Subtraction of two symbols in different > > > sections "cpu_vendor" {.data section} - "KERNBASE" {*UND* section} at file > > > address 680. > > > /tmp/ccO18745.s:2270: Error: Subtraction of two symbols in different > > > sections "cpu_vendor" {.data section} - "KERNBASE" {*UND* section} at file > > > address 686. > > > /tmp/ccO18745.s:2274: Error: Subtraction of two symbols in different > > > sections "cpu_id" {.data section} - "KERNBASE" {*UND* section} at file > > > address 699. > > > /tmp/ccO18745.s:2275: Error: Subtraction of two symbols in different > > > sections "cpu_feature" {.data section} - "KERNBASE" {*UND* section} at > > > file address 705. > > > /tmp/ccO18745.s:2282: Error: Subtraction of two symbols in different > > > sections "cpu" {.data section} - "KERNBASE" {*UND* section} at file > > > address 722. > > > /tmp/ccO18745.s:2288: Error: Subtraction of two symbols in different > > > sections "cpu" {.data section} - "KERNBASE" {*UND* section} at file > > > address 739. > > > /tmp/ccO18745.s:2292: Error: Subtraction of two symbols in different > > > sections "cpu" {.data section} - "KERNBASE" {*UND* section} at file > > > address 751. > > > /tmp/ccO18745.s:2305: Error: Subtraction of two symbols in different > > > sections "cpu_feature" {.data section} - "KERNBASE" {*UND* section} at > > > file address 762. > > > /tmp/ccO18745.s:2313: Error: Subtraction of two symbols in different > > > sections "end" {*UND* section} - "KERNBASE" {*UND* section} at file > > > address 784. > > > /tmp/ccO18745.s:2316: Error: Negative of non-absolute symbol KERNBASE > > > /tmp/ccO18745.s:2321: Error: Negative of non-absolute symbol KERNBASE > > > /tmp/ccO18745.s:2322: Error: Negative of non-absolute symbol KERNBASE > > > /tmp/ccO18745.s:2326: Error: Negative of non-absolute symbol KERNBASE > > > /tmp/ccO18745.s:2334: Error: Subtraction of two symbols in different > > > sections ".data" {.data section} - "KERNBASE" {*UND* section} at file > > > address 843. > > > /tmp/ccO18745.s:2335: Error: Subtraction of two symbols in different > > > sections ".data" {.data section} - "KERNBASE" {*UND* section} at file > > > address 849. > > > /tmp/ccO18745.s:2338: Error: Subtraction of two symbols in different > > > sections ".data" {.data section} - "KERNBASE" {*UND* section} at file > > > address 855. > > > /tmp/ccO18745.s:2338: Error: Subtraction of two symbols in different > > > sections ".data" {.data section} - "KERNBASE" {*UND* section} at file > > > address 867. > > > /tmp/ccO18745.s:2339: Error: Subtraction of two symbols in different > > > sections ".data" {.data section} - "KERNBASE" {*UND* section} at file > > > address 885. > > > /tmp/ccO18745.s:2342: Error: Subtraction of two symbols in different > > > sections ".data" {.data section} - "KERNBASE" {*UND* section} at file > > > address 891. > > > /tmp/ccO18745.s:2342: Error: Subtraction of two symbols in different > > > sections ".data" {.data section} - "KERNBASE" {*UND* section} at file > > > address 903. > > > /tmp/ccO18745.s:2343: Error: Subtraction of two symbols in different > > > sections "IdlePTD" {.data section} - "KERNBASE" {*UND* section} at file > > > address 921. > > > /tmp/ccO18745.s:2346: Error: Subtraction of two symbols in different > > > sections ".data" {.data section} - "KERNBASE" {*UND* section} at file > > > address 927. > > > /tmp/ccO18745.s:2346: Error: Subtraction of two symbols in different > > > sections ".data" {.data section} - "KERNBASE" {*UND* section} at file > > > address 939. > > > /tmp/ccO18745.s:2347: Error: Subtraction of two symbols in different > > > sections ".data" {.data section} - "KERNBASE" {*UND* section} at file > > > address 957. > > > /tmp/ccO18745.s:2349: Error: Subtraction of two symbols in different > > > sections "proc0paddr" {.data section} - "KERNBASE" {*UND* section} at file > > > address 969. > > > /tmp/ccO18745.s:2351: Error: Subtraction of two symbols in different > > > sections ".data" {.data section} - "KERNBASE" {*UND* section} at file > > > address 975. > > > /tmp/ccO18745.s:2351: Error: Subtraction of two symbols in different > > > sections ".data" {.data section} - "KERNBASE" {*UND* section} at file > > > address 987. > > > /tmp/ccO18745.s:2352: Error: Subtraction of two symbols in different > > > sections ".data" {.data section} - "KERNBASE" {*UND* section} at file > > > address 1005. > > > /tmp/ccO18745.s:2354: Error: Subtraction of two symbols in different > > > sections ".data" {.data section} - "KERNBASE" {*UND* section} at file > > > address 1011. > > > /tmp/ccO18745.s:2354: Error: Subtraction of two symbols in different > > > sections ".data" {.data section} - "KERNBASE" {*UND* section} at file > > > address 1023. > > > /tmp/ccO18745.s:2355: Error: Subtraction of two symbols in different > > > sections "vm86pa" {.data section} - "KERNBASE" {*UND* section} at file > > > address 1041. > > > /tmp/ccO18745.s:2357: Error: Subtraction of two symbols in different > > > sections "vm86paddr" {.data section} - "KERNBASE" {*UND* section} at file > > > address 1053. > > > /tmp/ccO18745.s:2372: Error: Subtraction of two symbols in different > > > sections "cpu_feature" {.data section} - "KERNBASE" {*UND* section} at > > > file address 1063. > > > /tmp/ccO18745.s:2377: Error: Subtraction of two symbols in different > > > sections "etext" {*UND* section} - "KERNBASE" {*UND* section} at file > > > address 1080. > > > /tmp/ccO18745.s:2380: Error: Subtraction of two symbols in different > > > sections ".data" {.data section} - "KERNBASE" {*UND* section} at file > > > address 1103. > > > /tmp/ccO18745.s:2383: Error: Subtraction of two symbols in different > > > sections "etext" {*UND* section} - "KERNBASE" {*UND* section} at file > > > address 1125. > > > /tmp/ccO18745.s:2389: Error: Subtraction of two symbols in different > > > sections "cpu_feature" {.data section} - "KERNBASE" {*UND* section} at > > > file address 1146. > > > /tmp/ccO18745.s:2394: Error: Subtraction of two symbols in different > > > sections ".data" {.data section} - "KERNBASE" {*UND* section} at file > > > address 1164. > > > /tmp/ccO18745.s:2397: Error: Subtraction of two symbols in different > > > sections ".data" {.data section} - "KERNBASE" {*UND* section} at file > > > address 1183. > > > /tmp/ccO18745.s:2400: Error: Subtraction of two symbols in different > > > sections "IdlePTD" {.data section} - "KERNBASE" {*UND* section} at file > > > address 1205. > > > /tmp/ccO18745.s:2402: Error: Subtraction of two symbols in different > > > sections ".data" {.data section} - "KERNBASE" {*UND* section} at file > > > address 1224. > > > /tmp/ccO18745.s:2405: Error: Subtraction of two symbols in different > > > sections ".data" {.data section} - "KERNBASE" {*UND* section} at file > > > address 1247. > > > /tmp/ccO18745.s:2407: Error: Subtraction of two symbols in different > > > sections ".data" {.data section} - "KERNBASE" {*UND* section} at file > > > address 1266. > > > /tmp/ccO18745.s:2412: Error: Subtraction of two symbols in different > > > sections ".data" {.data section} - "KERNBASE" {*UND* section} at file > > > address 1308. > > > /tmp/ccO18745.s:2415: Error: Subtraction of two symbols in different > > > sections ".data" {.data section} - "KERNBASE" {*UND* section} at file > > > address 1331. > > > /tmp/ccO18745.s:2417: Error: Subtraction of two symbols in different > > > sections ".data" {.data section} - "KERNBASE" {*UND* section} at file > > > address 1350. > > > /tmp/ccO18745.s:2423: Error: Subtraction of two symbols in different > > > sections "vm86pa" {.data section} - "KERNBASE" {*UND* section} at file > > > address 1392. > > > /tmp/ccO18745.s:2429: Error: Subtraction of two symbols in different > > > sections "vm86pa" {.data section} - "KERNBASE" {*UND* section} at file > > > address 1434. > > > /tmp/ccO18745.s:2435: Error: Subtraction of two symbols in different > > > sections ".data" {.data section} - "KERNBASE" {*UND* section} at file > > > address 1457. > > > /tmp/ccO18745.s:2438: Error: Subtraction of two symbols in different > > > sections "IdlePTD" {.data section} - "KERNBASE" {*UND* section} at file > > > address 1473. > > > /tmp/ccO18745.s:2441: Error: Subtraction of two symbols in different > > > sections ".data" {.data section} - "KERNBASE" {*UND* section} at file > > > address 1496. > > > /tmp/ccO18745.s:2444: Error: Subtraction of two symbols in different > > > sections "IdlePTD" {.data section} - "KERNBASE" {*UND* section} at file > > > address 1515. > > > /tmp/ccO18745.s:2447: Error: Subtraction of two symbols in different > > > sections "IdlePTD" {.data section} - "KERNBASE" {*UND* section} at file > > > address 1538. > > > /tmp/ccO18745.s:2450: Error: Subtraction of two symbols in different > > > sections "IdlePTD" {.data section} - "KERNBASE" {*UND* section} at file > > > address 1557. > > > *** Error code 1 > > > > > > Stop in /u/obj/usr/src/sys/SHALL. > > > *** Error code 1 > > > > > > Stop in /usr/src. > > > *** Error code 1 > > > > > > Stop in /usr/src. > > > shall# > > > > > > ---------------------------------------------------------------------- > > > Name: SHALL > > > SHALL Type: Plain Text (text/plain) > > > Encoding: quoted-printable > > > > > > Part 1.2Type: application/pgp-signature > > > > -- > > Kent Stewart > > Richland, WA > > > > mailto:kstewart@3-cities.com > > http://kstewart.urx.com/kstewart/index.html > > ---------------------------------------------------------------------- > Part 1.2Type: application/pgp-signature -- 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 Sat Jan 27 15:32:20 2001 Delivered-To: freebsd-stable@freebsd.org Received: from shemp.palomine.net (shemp.palomine.net [205.198.88.200]) by hub.freebsd.org (Postfix) with SMTP id 956AC37B400 for ; Sat, 27 Jan 2001 15:32:03 -0800 (PST) Received: (qmail 9924 invoked by uid 1000); 27 Jan 2001 23:31:47 -0000 Date: Sat, 27 Jan 2001 18:31:47 -0500 From: Chris Johnson To: Mike Atkinson Cc: stable@freebsd.org Subject: Re: more strange DNS issues in BIND and STABLE. Message-ID: <20010127183147.A9810@palomine.net> References: <4.2.2.20010127001841.03015358@marble.sentex.net> <034601c08827$b8e08d80$1385f1d8@kconline.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <034601c08827$b8e08d80$1385f1d8@kconline.com>; from mikea@kconline.com on Sat, Jan 27, 2001 at 01:09:34AM -0500 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Jan 27, 2001 at 01:09:34AM -0500, Mike Atkinson wrote: > We've reverted to an earlier version of named which seems to have at least > reduced the problem to an intermittent one instead of continuous failure to > resolve (as far as Sendmail was concerned.) One solution to all of these BIND problems that nobody has mentioned yet is to use something other than BIND for DNS. I've been using Dan Bernstein's djbdns with great success since its early alpha days. Like everything he writes (most notably qmail), it's small, robust, and secure, and it just plain works. http://cr.yp.to/djbdns.html Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jan 27 15:38:24 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 3D66237B400 for ; Sat, 27 Jan 2001 15:38:07 -0800 (PST) Received: by veldy.net (Postfix, from userid 1000) id 9ECB88C2C; Sat, 27 Jan 2001 17:37:20 -0600 (CST) Received: from localhost (localhost [127.0.0.1]) by veldy.net (Postfix) with ESMTP id 9A6A71C6B; Sat, 27 Jan 2001 17:37:20 -0600 (CST) Date: Sat, 27 Jan 2001 17:37:20 -0600 (CST) From: "Thomas T. Veldhouse" To: Ben Jackson Cc: Kal Torak , FreeBSD-stable Subject: Re: ipfw forwarding In-Reply-To: <200101272136.f0RLavv28020@saturn.home.ben.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 What if you don't run NAT? My network is bridged, so I don't run NATD. Forwarding ports is a pain in the arse - since it does not appear to work with ipfw. I have had to use "socket" with inetd. Tom Veldhouse veldy@veldy.net On Sat, 27 Jan 2001, Ben Jackson wrote: > > Ok, so I have another FreeBSD box running a server on port 27015/udp > > and I put a rule in my ipfw list saying "${fwcmd} 600 fwd 10.0.0.4 udp from > > any to any 27015" this seems like it should do the job, and when I connect > > You should be changing your nat command line to include: > > -redirect_port udp 10.0.0.4 > > --Ben > > > 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 27 16:20:33 2001 Delivered-To: freebsd-stable@freebsd.org Received: from espen.oysnet.lan (login.oysnet.eu.org [64.32.206.153]) by hub.freebsd.org (Postfix) with ESMTP id 59D2737B400 for ; Sat, 27 Jan 2001 16:20:16 -0800 (PST) Received: from localhost (eoyslebo@localhost) by espen.oysnet.lan (8.11.1/8.11.1) with ESMTP id f0S0KHq35317 for ; Sat, 27 Jan 2001 19:20:18 -0500 (EST) (envelope-from oys@powertech.no) X-Authentication-Warning: espen.oysnet.lan: eoyslebo owned process doing -bs Date: Sat, 27 Jan 2001 19:20:16 -0500 (EST) From: Espen Oyslebo X-Sender: eoyslebo@espen.oysnet.lan To: stable@freebsd.org Subject: ipnat vs natd and ipf vs ipfw (fwd) 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 Ipfw and ipf to my eye (without glasses that is) seem to do pretty much the same thing. The same is true for ipnat and natd. Of course there are differences between the two (ritgh?). If so: What are they? An example of a scenario where it would be advantagous to use an ipfw/natd solution: An example of a scenario where it would be advantagous to use an ipf/ipnat solution: A wacky example where some different combination (or even all of them) should be used: Currently, I have ipfw and natd doing their job fairly well. Is there any point in switching (yeah,yeah, don't fix it if it ain't broken). Thanks alot! Espen Oyslebo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jan 27 17: 6:33 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 65E4237B404 for ; Sat, 27 Jan 2001 17:06:16 -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, 27 Jan 2001 17:04:26 -0800 Received: (from cjc@localhost) by rfx-216-196-73-168.users.reflexcom.com (8.11.1/8.11.1) id f0S16M881341; Sat, 27 Jan 2001 17:06:22 -0800 (PST) (envelope-from cjc) Date: Sat, 27 Jan 2001 17:06:21 -0800 From: "Crist J. Clark" To: Kal Torak Cc: FreeBSD-stable Subject: Re: ipfw forwarding (more info) Message-ID: <20010127170621.M10761@rfx-216-196-73-168.users.reflex> Reply-To: cjclark@alum.mit.edu References: <3A72CB47.7A5DD83@quake.com.au> <20010127220257.B28504@nevermind.kiev.ua> <3A732BE9.F559820D@quake.com.au> <3A732EFB.E7E743BA@quake.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <3A732EFB.E7E743BA@quake.com.au>; from kaltorak@quake.com.au on Sun, Jan 28, 2001 at 07:26:35AM +1100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jan 28, 2001 at 07:26:35AM +1100, Kal Torak wrote: > Kal Torak wrote: > > > > Nevermind wrote: > > > > > > Hello, Kal Torak! > > > > > > On Sun, Jan 28, 2001 at 12:21:11AM +1100, you wrote: > > > > > > > Ok, so I have another FreeBSD box running a server on port 27015/udp > > > > and I put a rule in my ipfw list saying "${fwcmd} 600 fwd 10.0.0.4 udp from > > > > any to any 27015" this seems like it should do the job, and when I connect > > > should this be: > > > ${fwcmd} 600 fwd 10.0.0.4,27015 udp from any to any 27015 > > > ? > > > > > > Correct me if I wrong... > > > > AFAIK you only need to specify the destination port if its different from the > > source... And the port would have no meaning when forwarding to another machine just like it says in the manpage. > > I just dont get this... it *should* work from what I know... yet it doesnt... > > > > I am considering recompiling with ipf and see if I can get that to do what I > > want.. but thats a bit of a pain since ipfw should be able to do this... > > After some more fiddling around, I have noticed that the ipfw rule is > hit, but nothing seems to happen... The data just continues on to the > local port instead of being forwarded to the remote one... Are you sure? Please try, # tcpdump -i -en port 27015 On each interface that would be involved. > Maybe I am missing something that needs to be loaded for this to work? No, forwarding is all in the kernel (or KLD module). But I suspect you really don't want to forward packets, but actually want to do NAT. -- 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 27 17:10: 7 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 94C1037B404 for ; Sat, 27 Jan 2001 17:09:50 -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, 27 Jan 2001 17:07:58 -0800 Received: (from cjc@localhost) by rfx-216-196-73-168.users.reflexcom.com (8.11.1/8.11.1) id f0S19xq81423; Sat, 27 Jan 2001 17:09:59 -0800 (PST) (envelope-from cjc) Date: Sat, 27 Jan 2001 17:09:59 -0800 From: "Crist J. Clark" To: "Thomas T. Veldhouse" Cc: Ben Jackson , Kal Torak , FreeBSD-stable Subject: Re: ipfw forwarding Message-ID: <20010127170959.N10761@rfx-216-196-73-168.users.reflex> Reply-To: cjclark@alum.mit.edu References: <200101272136.f0RLavv28020@saturn.home.ben.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from veldy@veldy.net on Sat, Jan 27, 2001 at 05:37:20PM -0600 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Jan 27, 2001 at 05:37:20PM -0600, Thomas T. Veldhouse wrote: > What if you don't run NAT? My network is bridged, so I don't run > NATD. Forwarding ports is a pain in the arse - since it does not appear > to work with ipfw. I have had to use "socket" with inetd. Something like 'bounce?' /usr/ports/net/bounce There are others in /usr/ports/net that do this kind of thing as well. -- 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 27 17:59:50 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 6135237B402 for ; Sat, 27 Jan 2001 17:59:31 -0800 (PST) Received: (from root@localhost) by cage.simianscience.com (8.11.2/8.11.1) id f0S1xUd76580; Sat, 27 Jan 2001 20:59:30 -0500 (EST) (envelope-from mike@sentex.net) Received: from chimp (fcage [192.168.0.2]) by cage.simianscience.com (8.11.2/8.11.1av) with ESMTP id f0S1xO776572; Sat, 27 Jan 2001 20:59:24 -0500 (EST) (envelope-from mike@sentex.net) Message-Id: <4.2.2.20010127204048.013addb0@marble.sentex.net> X-Sender: mdtancsa@marble.sentex.net X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Sat, 27 Jan 2001 20:59:23 -0500 To: "Mike Atkinson" , From: Mike Tancsa Subject: LAME domains, sendmail BIND and FreeBSD- its FreeBSD specific it seems (was more strange DNS issues in BIND and STABLE.)- In-Reply-To: <034601c08827$b8e08d80$1385f1d8@kconline.com> References: <4.2.2.20010127001841.03015358@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 01:09 AM 1/27/2001 -0500, Mike Atkinson wrote: >Just as a follow up on this thread, we are seeing the same behavior with the >moody.edu domain and currently have thousands of pieces of undeliverable OK, after trying out a few things, I think sendmail on FreeBSD is the actual culprit here. I downloaded sendmail 8.11.2 from sendmail.org, built and installed it, used the stock freebsd.mc file to generate a new .cf... Lo and behold, this version will deliver to LAME domains. I had tried the following combos: Using the totally LAME domain supercom.ca STABLE as of a few days ago (Jan 24) stock sendmail + stock BIND: no LAME delivery release BIND+ stock sendmail: No delivery release BIND+ sendmail .8.11.2: I can email LAME domains. STABLE stock BIND+ sendmail 8.11.2: I can email LAME domains... So in the end, this seems to be a sendmail issue, not a bind issue, but seems specific to FreeBSD, as the same versions of sendmail and BIND on a LINUX box, do not have this problem. Comments ? What is different about sendmail on FreeBSD that would account for this behaviour ? ---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 Sat Jan 27 19:18:50 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 4278137B400 for ; Sat, 27 Jan 2001 19:18:31 -0800 (PST) Received: (qmail 26081 invoked by uid 0); 28 Jan 2001 03:18:03 -0000 Received: from p3ee20abc.dip.t-dialin.net (HELO speedy.gsinet) (62.226.10.188) by mail.gmx.net (mp011-rz3) with SMTP; 28 Jan 2001 03:18:03 -0000 Received: (from sittig@localhost) by speedy.gsinet (8.8.8/8.8.8) id VAA05580 for freebsd-stable@FreeBSD.ORG; Sat, 27 Jan 2001 21:28:24 +0100 Date: Sat, 27 Jan 2001 21:28:24 +0100 From: Gerhard Sittig To: freebsd-stable@FreeBSD.ORG Subject: Re: Buildworld failure using two disks Message-ID: <20010127212824.R253@speedy.gsinet> Mail-Followup-To: freebsd-stable@FreeBSD.ORG References: <20010126232127.A294@dionysos.yi.org> <20010127120537.A420@dionysos.yi.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20010127120537.A420@dionysos.yi.org>; from dionysos@dionysos.yi.org on Sat, Jan 27, 2001 at 12:05:37PM -0700 Organization: System Defenestrators Inc. Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Jan 27, 2001 at 12:05 -0700, Dionysos wrote: > > Problem solved actually and I should have probably known > better. When I created my /usr/obj partition, I had done so > using partition magic and just created an msdos partition. > Apparently, though the man page for ln doesn't state this, you > can't make symbolic links across file systems of different type > (or at least involving msdosfs). Once I reformatted it to ufs, > it all worked fine. I'm not willing to follow you here. AFAIK symlinks only contain a *name* in their origin and neither do they care where they point to nor what type the destination is of nor if the destination is in existence at all. That's the actual point in symlinks -- they don't have an inode identification the hardlinks need and thus work across as many filesystem boundaries as you please whereas hardlinks only work within their own device (read: partition). There must have been something else. If I read your example right, you tried to combine all the problems that could arise: link across filesystems (no problem with -s) and thereby replace an existing dir entry (which _could_ be a problem). 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 Sat Jan 27 19:18:55 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 6C1CC37B402 for ; Sat, 27 Jan 2001 19:18:31 -0800 (PST) Received: (qmail 26091 invoked by uid 0); 28 Jan 2001 03:18:04 -0000 Received: from p3ee20abc.dip.t-dialin.net (HELO speedy.gsinet) (62.226.10.188) by mail.gmx.net (mp011-rz3) with SMTP; 28 Jan 2001 03:18:04 -0000 Received: (from sittig@localhost) by speedy.gsinet (8.8.8/8.8.8) id VAA05583 for freebsd-stable@freebsd.org; Sat, 27 Jan 2001 21:46:39 +0100 Date: Sat, 27 Jan 2001 21:46:39 +0100 From: Gerhard Sittig To: freebsd-stable@freebsd.org Subject: Re: IPFILTER 3.4.16 and FreeBSD-4.2 Message-ID: <20010127214639.S253@speedy.gsinet> Mail-Followup-To: freebsd-stable@freebsd.org References: <3A72DEA1.A31EC401@webcraft99.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <3A72DEA1.A31EC401@webcraft99.com>; from afu@webcraft99.com on Sat, Jan 27, 2001 at 10:43:45PM +0800 Organization: System Defenestrators Inc. Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Jan 27, 2001 at 22:43 +0800, Feisal Umar wrote: > > Are the startup scripts for FreeBSD-4.2 broken for > IPFILTER/IPNAT support? No. > I have a gateway machine configured with IPFILTER/IPNAT via the > rc.conf with the following entries: > ipfilter_enable="YES" > ipfilter_flags="" > ipnat_enable="YES" > ipmon_enable="YES" That's OK. And if you use the /etc/{ipf,ipnat}.rules filenames for your configuration -- these already are the defaults and work OOTB. > Hosts behind the GATEWAY can't traverse to outside via the NAT > after the GATEWAY is rebooted with a new Kernel Build > (yesterday). I had to manually specify "ipnat -CF -f > /etc/ipnat.rules" before everything works as normal. You don't use modules for your NIFs by chance? If so, have a look at the conf/22859 PR. A simple 'ipf -y' in your ppp.link{up,down} or late in rc.network should do. As well as you could make all the interfaces be there in time with some magic. But I would prefer to compile all essential NIC drivers into the kernel. > Ipmon behaviour has also changed, ie nothing is being passed to > syslog except an entry saying ipmon was started. I can't find > anything is the system logs to suggest anything is amiss. Dumb question: What exactly do you expect to find in the logs? Why are you scared by the absense of logged events? :) And then: Does your 'ipf -V' output allow logging? Do you have logging rules? Do they match? And while you're admitting to use a different ipfilter version: Where is it installed to? dougb tried to improve the rc scripts lately (you surely noticed while controling mergemaster(8)) to use pathnames and consistent output style. One basic thing to keep in mind when hunting bugs down: Don't look at your config files only -- these are just your intensions, they're easily misspelled and human readers tend to see what they _want_ to see ("I wrote 'blah', of course it reads 'blah'" when it actually reads 'blubb'). Query the system for status -- these are the facts! Look at the 'ipf -V', 'ipfstat -io -n', and 'ipnat -l' outputs as well as the 'which ipf ipfstat ipnat ipmon' output. It must be something simple. When in doubt put 'set -x' and 'set +x' around the ipfilter section in rc.network. 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 Sat Jan 27 19:23:56 2001 Delivered-To: freebsd-stable@freebsd.org Received: from ece.cmu.edu (ECE.CMU.EDU [128.2.236.200]) by hub.freebsd.org (Postfix) with ESMTP id 1E3D237B699 for ; Sat, 27 Jan 2001 19:23:39 -0800 (PST) Received: from pyanfar.ece.cmu.edu (uavxxl@PYANFAR.REM.CMU.EDU [128.2.87.225]) by ece.cmu.edu (8.11.0/8.10.2) with ESMTP id f0S3N7Z28633; Sat, 27 Jan 2001 22:23:07 -0500 (EST) Date: Sat, 27 Jan 2001 22:23:06 -0500 From: "Brandon S. Allbery KF8NH" To: Gerhard Sittig , freebsd-stable@FreeBSD.ORG Subject: Re: Buildworld failure using two disks Message-ID: <139420000.980652186@pyanfar.ece.cmu.edu> In-Reply-To: <20010127212824.R253@speedy.gsinet> X-Mailer: Mulberry/2.0.6b3 (Linux/x86) 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 Saturday, January 27, 2001 21:28:24 +0100, Gerhard Sittig wrote: +----- | I'm not willing to follow you here. AFAIK symlinks only contain | a *name* in their origin and neither do they care where they | point to nor what type the destination is of nor if the +--->8 ...but they cannot be created *on* msdos filesystems because the filesystem doesn't know about them. Which, if I've been following this correctly, is what was happening. -- brandon s. allbery [os/2][linux][solaris][japh] allbery@kf8nh.apk.net system administrator [WAY too many hats] allbery@ece.cmu.edu electrical and computer engineering KF8NH carnegie mellon university ["better check the oblivious first" -ke6sls] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jan 27 19:54: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 003D937B400 for ; Sat, 27 Jan 2001 19:54:36 -0800 (PST) Received: (from root@localhost) by cage.simianscience.com (8.11.2/8.11.1) id f0S3saU77293; Sat, 27 Jan 2001 22:54:36 -0500 (EST) (envelope-from mike@sentex.net) Received: from chimp (fcage [192.168.0.2]) by cage.simianscience.com (8.11.2/8.11.1av) with ESMTP id f0S3sK777285; Sat, 27 Jan 2001 22:54:21 -0500 (EST) (envelope-from mike@sentex.net) Message-Id: <4.2.2.20010127225302.01e75660@marble.sentex.net> X-Sender: mdtancsa@marble.sentex.net X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Sat, 27 Jan 2001 22:54:20 -0500 To: Espen Oyslebo , stable@freebsd.org From: Mike Tancsa Subject: Re: ipnat vs natd and ipf vs ipfw (fwd) 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 07:20 PM 1/27/2001 -0500, Espen Oyslebo wrote: >Currently, I have ipfw and natd doing their job fairly well. Is there any >point in switching (yeah,yeah, don't fix it if it ain't broken). Actually, I have found ipnat to be *much* faster for my home DSL connection. My gateway is a lowly Pentium 133 and I can only get full rate net throughput use ipnat. natd is about 33% slower than ipnat for my setup on PPPoE. ---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 Sat Jan 27 20:27:46 2001 Delivered-To: freebsd-stable@freebsd.org Received: from rshb.com.ru (unknown [212.164.116.242]) by hub.freebsd.org (Postfix) with ESMTP id 5B99137B698 for ; Sat, 27 Jan 2001 20:27:28 -0800 (PST) Received: from rshb.com.ru (vampiro.rsb.local [192.168.1.111]) by rshb.com.ru (8.11.1/8.11.1) with ESMTP id f0S4RPS82639 for ; Sun, 28 Jan 2001 10:27:26 +0600 (OMST) (envelope-from admin@rshb.com.ru) Message-ID: <3A739F7A.CF03E750@rshb.com.ru> Date: Sun, 28 Jan 2001 10:26:34 +0600 From: "Evgueni V. Gavrilov" X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.2-STABLE i386) X-Accept-Language: ru, en MIME-Version: 1.0 To: freebsd-stable@FreeBSD.ORG Subject: Re: IPFilter will not allow traceroute anymore References: <200101271624.f0RGO0c57680@cwsys.cwsent.com> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Cy Schubert - ITSD Open Systems Group wrote: > You're probably better of installing IPF 3.4.16. There have been many > bugfixes and improvements since 3.4.8 (version of IPF packaged with > FreeBSD-STABLE). I tried to install IPF 3.4.16 yesterday on fresh -STABLE, but after this my kernel couldn't be made. whilte making depend I got In file included from ../../netinet/ip_fil.c:100: ../../netinet/ip_compat.h:270: osreldate.h: No such file or directory In file included from ../../netinet/fil.c:78: ../../netinet/ip_compat.h:270: osreldate.h: No such file or directory In file included from ../../netinet/ip_nat.c:98: ../../netinet/ip_compat.h:270: osreldate.h: No such file or directory In file included from ../../netinet/ip_frag.c:70: ../../netinet/ip_compat.h:270: osreldate.h: No such file or directory In file included from ../../netinet/ip_state.c:82: ../../netinet/ip_compat.h:270: osreldate.h: No such file or directory In file included from ../../netinet/ip_auth.c:92: ../../netinet/ip_compat.h:270: osreldate.h: No such file or directory In file included from ../../netinet/ip_proxy.c:71: ../../netinet/ip_compat.h:270: osreldate.h: No such file or directory In file included from ../../netinet/mlfk_ipl.c:43: ../../netinet/ip_compat.h:270: osreldate.h: No such file or directory mkdep: compile failed *** Error code 1 Stop in /usr/src/sys/compile/VAMPIRO. any suggestions ? -- Yours truly, Evgueni www.treasury.ru/~gev When did my wild oats turn to shredded wheat? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jan 27 21: 5:31 2001 Delivered-To: freebsd-stable@freebsd.org Received: from kestrel.prod.itd.earthlink.net (kestrel.prod.itd.earthlink.net [207.217.121.155]) by hub.freebsd.org (Postfix) with ESMTP id 1126337B400 for ; Sat, 27 Jan 2001 21:05:13 -0800 (PST) Received: from dionysos.yi.org (1Cust85.tnt11.phoenix.az.da.uu.net [63.14.204.85]) by kestrel.prod.itd.earthlink.net (8.9.3-EL_1_3/8.9.3) with ESMTP id VAA29306; Sat, 27 Jan 2001 21:05:02 -0800 (PST) Received: by dionysos.yi.org (Postfix, from userid 1001) id 7A0B91C56; Sat, 27 Jan 2001 22:03:40 -0700 (MST) Date: Sat, 27 Jan 2001 22:03:40 -0700 From: Dionysos To: "Brandon S. Allbery KF8NH" Cc: Gerhard Sittig , freebsd-stable@FreeBSD.ORG Subject: Re: Buildworld failure using two disks Message-ID: <20010127220340.A294@dionysos.yi.org> Reply-To: james@m-a.net References: <20010127212824.R253@speedy.gsinet> <139420000.980652186@pyanfar.ece.cmu.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <139420000.980652186@pyanfar.ece.cmu.edu>; from allbery@ece.cmu.edu on Sat, Jan 27, 2001 at 10:23:06PM -0500 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Jan 27, 2001 at 10:23:06PM -0500, Brandon S. Allbery KF8NH wrote: > On Saturday, January 27, 2001 21:28:24 +0100, Gerhard Sittig > wrote: > +----- > | I'm not willing to follow you here. AFAIK symlinks only contain > | a *name* in their origin and neither do they care where they > | point to nor what type the destination is of nor if the > +--->8 > > ....but they cannot be created *on* msdos filesystems because the filesystem > doesn't know about them. Which, if I've been following this correctly, is > what was happening. > You would definitely be following correctly. Granted I didn't do any kind of scientific analysis of this to be sure that this was exactly what was tripping me up, but it makes a bit more sense that one can't write symbolic links across differently formatted file systems. One thing that crossed my mind was how far this carries. Can you symlink between an ext2fs and ufs filesystem, or do they have to be matching types in order for a symlink to be created? James To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jan 27 21:12:55 2001 Delivered-To: freebsd-stable@freebsd.org Received: from c007.snv.cp.net (c007-h000.c007.snv.cp.net [209.228.33.206]) by hub.freebsd.org (Postfix) with SMTP id 7156F37B400 for ; Sat, 27 Jan 2001 21:12:38 -0800 (PST) Received: (cpmta 5115 invoked from network); 27 Jan 2001 21:12:37 -0800 Received: from dsl-64-34-45-85.telocity.com (HELO BRIAN) (64.34.45.85) by smtp.telocity.com (209.228.33.206) with SMTP; 27 Jan 2001 21:12:37 -0800 X-Sent: 28 Jan 2001 05:12:37 GMT From: "Brian" To: "Freebsd-Stable" Subject: nlist failed Date: Sat, 27 Jan 2001 23:12:37 -0600 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 I have one machine that gives me this error when I run(attempt) top. I have cvsup'd the latest sources as of about 5PM 1/27. I have tried doing this a few different ways. I have done a make world, also a make buildworld installworld(from single user) then reboot and build a kernel. I have also tried the make buildkernel etc. I have it setup on a "dangerously" dedicated drive. I don't do anything other than the default install for the boot loader portion. Is there something that I am missing. BTW...I have been able to cvsup and build sucessfully on this machine. It was installed on 4.0 and updated regularly with no problems before. Thanks in Advance Brian Ellefson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jan 27 21:15: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 7415A37B400 for ; Sat, 27 Jan 2001 21:15:16 -0800 (PST) Received: (from root@localhost) by cage.simianscience.com (8.11.2/8.11.1) id f0S5FF177835; Sun, 28 Jan 2001 00:15:15 -0500 (EST) (envelope-from mike@sentex.net) Received: from chimp (fcage [192.168.0.2]) by cage.simianscience.com (8.11.2/8.11.1av) with ESMTP id f0S5F8777826; Sun, 28 Jan 2001 00:15:09 -0500 (EST) (envelope-from mike@sentex.net) Message-Id: <4.2.2.20010128001428.01a68b88@marble.sentex.net> X-Sender: mdtancsa@marble.sentex.net X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Sun, 28 Jan 2001 00:15:07 -0500 To: "Brian" , "Freebsd-Stable" From: Mike Tancsa Subject: Re: nlist failed 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 How are you booting the machine ? It sounds like the /boot/loader portion is messed up. ---Mike At 11:12 PM 1/27/2001 -0600, Brian wrote: >I have one machine that gives me this error when I run(attempt) top. I >have cvsup'd the latest sources as of about 5PM 1/27. I have tried >doing this a few different ways. I have done a make world, also a make >buildworld installworld(from single user) then reboot and build a >kernel. I have also tried the make buildkernel etc. I have it setup on >a "dangerously" dedicated drive. I don't do anything other than the >default install for the boot loader portion. Is there something that I >am missing. BTW...I have been able to cvsup and build sucessfully on >this machine. It was installed on 4.0 and updated regularly with no >problems before. > >Thanks in Advance > >Brian Ellefson > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-stable" in the body of the message -------------------------------------------------------------------- Mike Tancsa, tel +1 519 651 3400 Network Administration, mike@sentex.net Sentex Communications www.sentex.net Cambridge, Ontario Canada www.sentex.net/mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jan 27 21:18:53 2001 Delivered-To: freebsd-stable@freebsd.org Received: from arianna.webcraft99.alt (unknown [202.151.192.90]) by hub.freebsd.org (Postfix) with ESMTP id 8086C37B400 for ; Sat, 27 Jan 2001 21:18:33 -0800 (PST) Received: from jenna.webcraft99.alt (jenna.webcraft99.alt [192.168.1.22]) by arianna.webcraft99.alt (AriAnnA) with ESMTP id 76BF17C12; Sun, 28 Jan 2001 13:43:30 +0800 (MYT) Received: from webcraft99.com (lexus.webcraft99.alt [192.168.1.31]) by jenna.webcraft99.alt (JEnnA) with ESMTP id 039AB3DB2; Sun, 28 Jan 2001 13:23:09 +0800 (MYT) Message-ID: <3A73ACBC.FEBE8FCF@webcraft99.com> Date: Sun, 28 Jan 2001 13:23:08 +0800 From: Feisal Umar Organization: Webcraft Sdn Bhd (http://www.webcraft99.com) X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Gerhard Sittig Cc: freebsd-stable@freebsd.org Subject: Re: IPFILTER 3.4.16 and FreeBSD-4.2 References: <3A72DEA1.A31EC401@webcraft99.com> <20010127214639.S253@speedy.gsinet> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Gerhard Thanks for your extensive guide. It was indeed something simple. Disgusting unthorough, unlike dougb, I didnt synchronise my custom rc files for services that requires the firewall/ipfilter. One such script still was calling my old "initialise the firewall" script which I have deleted. I do concur now the rc scripts FreeBSD-4.2 is NOT broken. Apologies. Thank you. Gerhard Sittig wrote: > > On Sat, Jan 27, 2001 at 22:43 +0800, Feisal Umar wrote: > > > > Are the startup scripts for FreeBSD-4.2 broken for > > IPFILTER/IPNAT support? > > No. > > > I have a gateway machine configured with IPFILTER/IPNAT via the > > rc.conf with the following entries: > > ipfilter_enable="YES" > > ipfilter_flags="" > > ipnat_enable="YES" > > ipmon_enable="YES" > > That's OK. And if you use the /etc/{ipf,ipnat}.rules filenames > for your configuration -- these already are the defaults and work > OOTB. > > > Hosts behind the GATEWAY can't traverse to outside via the NAT > > after the GATEWAY is rebooted with a new Kernel Build > > (yesterday). I had to manually specify "ipnat -CF -f > > /etc/ipnat.rules" before everything works as normal. > > You don't use modules for your NIFs by chance? If so, have a > look at the conf/22859 PR. A simple 'ipf -y' in your > ppp.link{up,down} or late in rc.network should do. As well as > you could make all the interfaces be there in time with some > magic. But I would prefer to compile all essential NIC drivers > into the kernel. > > > Ipmon behaviour has also changed, ie nothing is being passed to > > syslog except an entry saying ipmon was started. I can't find > > anything is the system logs to suggest anything is amiss. > > Dumb question: What exactly do you expect to find in the logs? > Why are you scared by the absense of logged events? :) And then: > Does your 'ipf -V' output allow logging? Do you have logging > rules? Do they match? > > And while you're admitting to use a different ipfilter version: > Where is it installed to? dougb tried to improve the rc scripts > lately (you surely noticed while controling mergemaster(8)) to > use pathnames and consistent output style. > > One basic thing to keep in mind when hunting bugs down: Don't > look at your config files only -- these are just your intensions, > they're easily misspelled and human readers tend to see what they > _want_ to see ("I wrote 'blah', of course it reads 'blah'" when > it actually reads 'blubb'). Query the system for status -- these > are the facts! Look at the 'ipf -V', 'ipfstat -io -n', and > 'ipnat -l' outputs as well as the 'which ipf ipfstat ipnat ipmon' > output. It must be something simple. When in doubt put 'set -x' > and 'set +x' around the ipfilter section in rc.network. > > 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 -- Feisal Umar Webcraft Sdn Bhd - http://www.webcraft99.com If you think the United States has stood still, who built the largest shopping center in the world? -- Richard M. Nixon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jan 27 21:20: 1 2001 Delivered-To: freebsd-stable@freebsd.org Received: from ece.cmu.edu (ECE.CMU.EDU [128.2.236.200]) by hub.freebsd.org (Postfix) with ESMTP id 9B84C37B400 for ; Sat, 27 Jan 2001 21:19:42 -0800 (PST) Received: from pyanfar.ece.cmu.edu (53541n@PYANFAR.REM.CMU.EDU [128.2.87.225]) by ece.cmu.edu (8.11.0/8.10.2) with ESMTP id f0S5JAZ00768; Sun, 28 Jan 2001 00:19:11 -0500 (EST) Date: Sun, 28 Jan 2001 00:19:09 -0500 From: "Brandon S. Allbery KF8NH" To: james@m-a.net Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Buildworld failure using two disks Message-ID: <181490000.980659149@pyanfar.ece.cmu.edu> In-Reply-To: <20010127220340.A294@dionysos.yi.org> X-Mailer: Mulberry/2.0.6b3 (Linux/x86) 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 Saturday, January 27, 2001 22:03:40 -0700, Dionysos wrote: +----- | > ....but they cannot be created *on* msdos filesystems because the | filesystem > doesn't know about them. Which, if I've been following | this correctly, is > what was happening. | > | You would definitely be following correctly. Granted I didn't do any | kind of scientific analysis of this to be sure that this was exactly what | was tripping me up, but it makes a bit more sense that one can't write | symbolic links across differently formatted file systems. +---->8 You're not quite understanding. Symlinks can point to anything; as far as the VFS is concerned, it's just a new filesystem path to follow. The problem is that the msdos filesystem itself doesn't know how to store a filesystem object of type "symlink". In fact, the semantics of the msdos filesystem are so different from those of Unix-style filesystems (ufs, ext2, etc.) that I would have expected more things to fail than just symlinking: filenames which differ only in case will collide with each other, and it can't store any kind of filesystem object other than a regular file or a directory (i.e. not only do symlinks lose, so do fifos, sockets, and character and block devices... not that any of those would be put into /usr/obj.) The lesson of this is: don't put /usr/obj on a non-unix-like filesystem. ufs and ext2fs are the safe ones to use. -- brandon s. allbery [os/2][linux][solaris][japh] allbery@kf8nh.apk.net system administrator [WAY too many hats] allbery@ece.cmu.edu electrical and computer engineering KF8NH carnegie mellon university ["better check the oblivious first" -ke6sls] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jan 27 22:15:42 2001 Delivered-To: freebsd-stable@freebsd.org Received: from net2.dinoex.sub.org (net2.dinoex.de [212.184.201.182]) by hub.freebsd.org (Postfix) with ESMTP id 02AA037B402 for ; Sat, 27 Jan 2001 22:15:22 -0800 (PST) Received: from gate.dinoex.sub.org (dinoex@localhost) by net2.dinoex.sub.org (8.11.2/8.11.2) with BSMTP id f0S6F3d01896 for ; Sun, 28 Jan 2001 07:15:03 +0100 (CET) (envelope-from dirk.meyer@dinoex.sub.org) X-MDaemon-Deliver-To: To: freebsd-stable@FreeBSD.ORG Message-ID: From: dirk.meyer@dinoex.sub.org (Dirk Meyer) Organization: privat Subject: Re: LAME domains, sendmail BIND and FreeBSD- its FreeBSD specific it seems (was more strange DNS issues in BIND and STABLE.)- Date: Sun, 28 Jan 2001 07:14:00 +0100 X-Mailer: Dinoex 1.77 References: <034601c08827$b8e08d80$1385f1d8@kconline.com> <4.2.2.20010127001841.03015358@marble.sentex.net> <4.2.2.20010127204048.013addb0@marble.sentex.net> X-Gateway: ZCONNECT gate.dinoex.sub.org [UNIX/Connect 0.90] X-Accept-Language: de,en X-PGP-Fingerprint: 44 16 EC 0A D3 3A 4F 28 8A 8A 47 93 F1 CF 2F 12 X-Noad: Please don't send me ad's by mail. I'm bored by this type of mail. X-Copyright: (C) Copyright 1999 by Dirk Meyer -- All rights reserved. X-Note: sending SPAM is a violation of both german and US law and will at least trigger a complaint at your provider's postmaster. X-PGP-Key-Avail: mailto:pgp-public-keys@keys.de.pgp.net Subject:GET 0x331CDA5D X-ZC-VIA: 20010128000000W+1@dinoex.sub.org Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Tancsa wrote:, > OK, after trying out a few things, I think sendmail on FreeBSD is the > actual culprit here. I downloaded sendmail 8.11.2 from sendmail.org, built > and installed it, used the stock freebsd.mc file to generate a new .cf... > Lo and behold, this version will deliver to LAME domains. could you try and build Sendmail from ports? > Comments ? What is different about sendmail on FreeBSD that would account > for this behaviour ? There are no functiuonla patches to sendmail in the Release, but the Build enviroment is diffrent. The port keeps the original enviroment of the build. So this might show a diffrence here. build from STABLE/RELEASE: cc -O -pipe -I/usr/src/usr.sbin/sendmail/../../contrib/sendmail/src -I/usr/src/usr.sbin/sendmail/../../contrib/sendmail/include -DNEWDB -DNIS -DNETINET6 -DTCPWRAPPERS -DMAP_REGEX -DSTARTTLS -D_FFR_TLS_O_T -D_FFR_TLS_1 -D_FFR_TLS_TOREK -I/usr/obj/usr/src/i386/usr/include -c /usr/src/usr.sbin/sendmail/../../contrib/sendmail/src/main.c build from ports: (SENDMAIL_WITH_TSL=yes) cc -O -I. -I../../include -DNEWDB -DNIS -DMAP_REGEX -DTCPWRAPPERS -DNETINET6 -DSTARTTLS -D_FFR_TLS_O_T -D_FFR_TLS_1 -D_FFR_TLS_TOREK -c main.c If you build sendmail from scratch it does behave diffrent: - you won't have TSL support - it won't uses the TCPWRAPPERS - you don't have support for NETINET6 I would guess one of the 3 functions cause the problem. Please tweak the lines in the sendmail port: files/site.config.m4 to build without NETINET6 or without TCPWRAPPERS. I would like to know the results. kind regards Dirk - Dirk Meyer, Im Grund 4, 34317 Habichtswald, Germany - Tel. +49-5606-6512 - Tel. +49-177-6923813 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jan 27 23: 5:33 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail.kconline.com (kconline.com [216.241.132.2]) by hub.freebsd.org (Postfix) with ESMTP id 7A2B137B402 for ; Sat, 27 Jan 2001 23:05:16 -0800 (PST) Received: from barsoom (barsoom.kconline.com [216.241.133.19]) by mail.kconline.com (8.9.3/8.9.3) with SMTP id CAA18322; Sun, 28 Jan 2001 02:05:15 -0500 (EST) Message-ID: <03fc01c088f8$aafabd40$1385f1d8@kconline.com> From: "Mike Atkinson" To: , "Mike Tancsa" References: <4.2.2.20010127001841.03015358@marble.sentex.net> <4.2.2.20010127204048.013addb0@marble.sentex.net> Subject: Re: LAME domains, sendmail BIND and FreeBSD- its FreeBSD specific it seems (was more strange DNS issues in BIND and STABLE.)- Date: Sun, 28 Jan 2001 02:05:14 -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 ----- Original Message ----- From: "Mike Tancsa" . > STABLE stock BIND+ sendmail 8.11.2: I can email LAME domains... This combination did not resolve the problem in our case but we built 8.11.2 from the ports tree. We did find that running Sendmail 8.9.3 (out of desperation) seems to have corrected the problem for now. We are still having intermittent problems with nslookups up on some domains (don't have the exact error message in debug mode, but it as an "NX" problem.) Sendmail 8.11.1 (or 8.11.2) does work fine if we set resolv.conf to use our competitors NT nameserver.. I am now getting ready to try what Dirk Meyer has suggested and will report back. ----- Mike Atkinson - mikea@kconline.com KC Online, Inc. - System Administration ----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 28 0: 5:42 2001 Delivered-To: freebsd-stable@freebsd.org Received: from netcabo.pt (unknown [212.113.161.137]) by hub.freebsd.org (Postfix) with ESMTP id 8C9F737B400 for ; Sun, 28 Jan 2001 00:05:25 -0800 (PST) Received: from OpsyDopsy.net.dhis.org ([213.22.2.137]) by netcabo.pt with Microsoft SMTPSVC(5.5.1877.537.53); Sun, 28 Jan 2001 08:03:54 +0000 From: =?iso-8859-1?q?Jo=E3o=20Fernandes?= To: stable@freebsd.org Subject: IPF vs ipfw? Date: Sun, 28 Jan 2001 08:07:16 +0000 X-Mailer: KMail [version 1.1.99] Content-Type: text/plain; charset="iso-8859-1" MIME-Version: 1.0 Message-Id: <01012808071600.15005@OpsyDopsy.net.dhis.org> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Could some one please enlighten me on the subject IPFilter Versus ipfw? What the pros and cons may be? Or if this topic has already been way discussed, could I be given an URL to go and read the discussions? Thanks in advance. Joao Fernandes To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message