From owner-freebsd-stable Sun Dec 26 2:50:46 1999 Delivered-To: freebsd-stable@freebsd.org Received: from tarvalon.net (tarvalon.net [216.145.165.65]) by hub.freebsd.org (Postfix) with SMTP id 559B115033 for ; Sun, 26 Dec 1999 02:50:43 -0800 (PST) (envelope-from kevin@tarvalon.net) Received: (qmail 22711 invoked by uid 1000); 26 Dec 1999 10:50:38 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 26 Dec 1999 10:50:38 -0000 Date: Sun, 26 Dec 1999 04:50:38 -0600 (CST) From: Kevin Entringer To: questions@freebsd.org Cc: stable@freebsd.org Subject: X11 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just did a make world to 3.4-STABLE. Now I'm having problems with X11, version 3.3.5. Whenever I try to start it I get the following: kevin@discord:/home/kevin# startx Authentication failed - cannot start X server. Perhaps you do not have console ownership? xinit: unexpected signal 2 In /var/log/messages it says the following: Dec 26 04:45:53 discord Xwrapper: no modules loaded for `xserver' service Dec 26 04:46:08 discord Xwrapper: no modules loaded for `xserver' service Dec 26 04:46:16 discord su: kevin to root on /dev/ttyv4 Dec 26 04:46:18 discord Xwrapper: no modules loaded for `xserver' service I've got no idea how to fix this. Any suggestions would be appreciated. Please cc any replies directly to me. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 26 6: 6:56 1999 Delivered-To: freebsd-stable@freebsd.org Received: from megaweapon.zigg.com (megaweapon.zigg.com [206.114.60.8]) by hub.freebsd.org (Postfix) with ESMTP id B253314D7D for ; Sun, 26 Dec 1999 06:06:38 -0800 (PST) (envelope-from matt@zigg.com) Received: from localhost (matt@localhost) by megaweapon.zigg.com (8.9.3/8.9.3) with ESMTP id JAA28112; Sun, 26 Dec 1999 09:05:38 -0500 (EST) (envelope-from matt@zigg.com) Date: Sun, 26 Dec 1999 09:05:21 -0500 (EST) From: Matt Behrens To: Kevin Entringer Cc: stable@FreeBSD.ORG Subject: Re: X11 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 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sun, 26 Dec 1999, Kevin Entringer wrote: > I just did a make world to 3.4-STABLE. Now I'm having problems with > X11, version 3.3.5. Whenever I try to start it I get the following: > > kevin@discord:/home/kevin# startx > > Authentication failed - cannot start X server. > Perhaps you do not have console ownership? > xinit: unexpected signal 2 > > In /var/log/messages it says the following: > > Dec 26 04:45:53 discord Xwrapper: no modules loaded for `xserver' service > Dec 26 04:46:08 discord Xwrapper: no modules loaded for `xserver' service > Dec 26 04:46:16 discord su: kevin to root on /dev/ttyv4 > Dec 26 04:46:18 discord Xwrapper: no modules loaded for `xserver' service > > I've got no idea how to fix this. Any suggestions would be appreciated. My best guess is that you're missing options UCONSOLE in your kernel config. Look for it and see... Matt Behrens Owner/Administrator, zigg.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.0 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE4ZiCk+xq4JbgNGlMRArwsAJ9+pd/yXT61O2WO6NqDbnerSzwk6ACeKOyv 2bAa0FRDcTnYmUwThBIytK8= =Sn6I -----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 Dec 26 8:19:55 1999 Delivered-To: freebsd-stable@freebsd.org Received: from lepton.nuc.net (lepton.nuc.net [204.49.61.5]) by hub.freebsd.org (Postfix) with ESMTP id 96CE91501F for ; Sun, 26 Dec 1999 08:19:47 -0800 (PST) (envelope-from bjohnson@gainesville.usda.ufl.edu) Received: from gainesville.usda.ufl.edu (pm3-2-21.nuc.net [204.49.61.227]) by lepton.nuc.net (8.8.8/8.8.8) with ESMTP id KAA02381; Sun, 26 Dec 1999 10:19:40 -0600 (CST) (envelope-from bjohnson@gainesville.usda.ufl.edu) Message-ID: <384955F4.DDD4FCD7@gainesville.usda.ufl.edu> Date: Sat, 04 Dec 1999 12:57:09 -0500 From: Bob Johnson X-Mailer: Mozilla 4.61 [en] (Win95; U) X-Accept-Language: en MIME-Version: 1.0 To: "stable@FreeBSD.ORG" Cc: god@yahoo.com, bjohnson@gainesville.usda.ufl.edu Subject: Re: bugs in the handbook. (FreeBSD Portal) References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG stable-digest V4 #592 contained the following: > Date: Sat, 25 Dec 1999 01:21:21 -0800 (PST) > From: Mike s > Subject: Re: bugs in the handbook. (FreeBSD Portal) > > well yes i agree that the linux Documentation project > is along the lines of what i am talking about, but > again take linux.com for example. IF we had volunteers > who had knowledge of the latest web development > resources/languages such as sPHP we can start a site > that is based mostly on volunteers as is linux.com > > Awhile back, there was a discussion on this questions > and this mailing list about not nearly enough newbie > documentation. So i guess we are a lacking in a few > areas. > > but, its planting the seed that counts. > > again, not to compete at all with freebsd.org a > separate entity entirely. > > besides, a lot of people who would commit to -docs > don't have the knowledge or patience to learn the SGML > structure if the site itself. > This isn't the obstacle that many think it is, because there are people who are willing to take text contributions and add the necessary SGML. By far the hardest part of producing documentation is coming up with the text in the first place. Once someone has figured out what to say and how to say it, the formatting details can be worked out by someone else who specializes in that. Since the -doc group is working on cleaning up the Handbook so it can be published in print in the (near?) future, right now would be a good time to write any documentation you are capable of and submit it. > > I'd like to see a site going up utilizing php/mysql > for fast and convenient site development. I think it makes more sense to put the effort directly into improving the Handbook, but if an alternate approach gives us better documentation, that's what really counts, so I think your "experiment" is well worth the effort. > [...] > > - --- Colin wrote: > > I don't think we don't care about the > > documentation, that strikes me as > > something of an oversimplification. There are 2 > > distinct problems here: > > 1) The peole who know enough about the system to > > document it properly > > generally don't have the time (or > > inclination...gotta love those programmers ;)) > > to spend on documentation. They're too busy fixing Most non-programmers (or, more accurately, non-documenters) don't understand that it takes roughly as long to properly document a program as it does to write it in the first place. It isn't usually the most effective use of resources to have the original programmers producing the documentation, because the skills required are not the same. I mention this as a means of encouraging anyone who is able to submit additions to the FreeBSD Handbook. If you know how to do something that isn't documented, write it up and submit it. Someone will pick it up and add the necessary SGML to integrate it into the Handbook. > [...] > > 2) The peole who are most willing to spend time on > > the documentation don't have > > the specific knowledge to do it. They are the one's > > who would like to be > > reading the docs. That is, of course, the tough part. I've found that most programmers are happy to answer specific questions if it reduces the overall effort they have to devote to documenation. If you can read the code, or other docs, and figure out most of it, there's nothing wrong with asking the code maintainer to explain the remaining details so you can get it documented. > [...] Of course, all of this is my personal opinion and I don't speak for the code maintainers or the -doc group. -- Bob Johnson bjohnson@gainesville.usda.ufl.edu bobj@atlantic.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 26 9:32:41 1999 Delivered-To: freebsd-stable@freebsd.org Received: from jade.chc-chimes.com (jade.chc-chimes.com [216.28.46.6]) by hub.freebsd.org (Postfix) with ESMTP id 5E2F314DF8 for ; Sun, 26 Dec 1999 09:32:39 -0800 (PST) (envelope-from billf@chc-chimes.com) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id 632721C57; Sun, 26 Dec 1999 12:31:55 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by jade.chc-chimes.com (Postfix) with ESMTP id 537B9381B; Sun, 26 Dec 1999 12:31:55 -0500 (EST) Date: Sun, 26 Dec 1999 12:31:55 -0500 (EST) From: Bill Fumerola To: Mike s Cc: Colin , stable@freebsd.org Subject: Re: bugs in the handbook. (FreeBSD Portal) In-Reply-To: <19991225092121.14043.qmail@web505.mail.yahoo.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 Sat, 25 Dec 1999, Mike s wrote: > but, its planting the seed that counts. > [.. a lot of other stuff ..] No. It's the actual work that counts. Everyone and their brother is willing to make waves and say what is wrong, but no-one is willing to do the work. We've played this game before and it always ends the same. Just make submissions to the existing web pages, handbook, etc and we'll do just fine. -- - bill fumerola - billf@chc-chimes.com - BF1560 - computer horizons corp - - ph:(800) 252-2421 - bfumerol@computerhorizons.com - billf@FreeBSD.org - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 26 9:45: 2 1999 Delivered-To: freebsd-stable@freebsd.org Received: from green.excel.net (excel.net [156.46.156.2]) by hub.freebsd.org (Postfix) with ESMTP id BACBB15063; Sun, 26 Dec 1999 09:44:56 -0800 (PST) (envelope-from kevin@tarvalon.net) Received: from fdl0042.excel.net (kevin@fdl0042.excel.net [156.46.102.170]) by green.excel.net (8.9.3/8.9.3) with ESMTP id LAA16112; Sun, 26 Dec 1999 11:44:50 -0600 (CST) Date: Sun, 26 Dec 1999 11:44:48 -0600 (CST) From: Kevin Entringer To: questions@freebsd.org Cc: stable@freebsd.org Subject: Re: X11 (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 Thanks for the suggestion. I suspect that this was the problem, however X is still not working. The following no happens: Dec 26 11:29:13 discord login: ROOT LOGIN (root) ON ttyv3 Dec 26 11:29:14 discord Xwrapper: unable to dlopen(/usr/lib/pam_unix.so) Dec 26 11:29:14 discord Xwrapper: [dlerror: /usr/lib/pam_unix.so: Undefined symb ol "crypt"] Dec 26 11:29:14 discord Xwrapper: adding faulty module: /usr/lib/pam_unix.so Regards, Kevin On Sun, 26 Dec 1999, Cy Schubert - ITSD Open Systems Group wrote: > In message , Kevi > n Entringer writes: > > I just did a make world to 3.4-STABLE. Now I'm having problems with > > X11, version 3.3.5. Whenever I try to start it I get the following: > > > > kevin@discord:/home/kevin# startx > > > > Authentication failed - cannot start X server. > > Perhaps you do not have console ownership? > > xinit: unexpected signal 2 > > > > In /var/log/messages it says the following: > > > > Dec 26 04:45:53 discord Xwrapper: no modules loaded for `xserver' service > > Dec 26 04:46:08 discord Xwrapper: no modules loaded for `xserver' service > > Dec 26 04:46:16 discord su: kevin to root on /dev/ttyv4 > > Dec 26 04:46:18 discord Xwrapper: no modules loaded for `xserver' service > > > > I've got no idea how to fix this. Any suggestions would be appreciated. > > > > Please cc any replies directly to me. > > I did not see this problem when I was testing 3.3-STABLE and nor did I > see it when I upgraded to 3.4-RELEASE. I did however see this problem > when I upgraded from the previous port of XF86 3.3.5 to the current > port of XF86 3.3.5 which now supports PAM. > > What you are seeing are PAM messages for modules that have not been > loaded. To have PAM load the required modules, add the following to > your pam.conf: > > # If we don't match anything else, default to using getpwnam(). > other auth required pam_unix.so try_first_pass > other account required pam_unix.so try_first_pass > > > Regards, Phone: (250)387-8437 > Cy Schubert Fax: (250)387-5766 > Sun/DEC Team, UNIX Group Internet: Cy.Schubert@uumail.gov.bc.ca > ITSD > Province of BC > "e**(i*pi)+1=0" > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 26 12:26:13 1999 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 5F56614CF4 for ; Sun, 26 Dec 1999 12:26:10 -0800 (PST) (envelope-from cy@cschuber.net.gov.bc.ca) Received: (from daemon@localhost) by point.osg.gov.bc.ca (8.8.7/8.8.8) id MAA09881; Sun, 26 Dec 1999 12:25:58 -0800 Received: from passer.osg.gov.bc.ca(142.32.110.29) via SMTP by point.osg.gov.bc.ca, id smtpda09879; Sun Dec 26 12:25:38 1999 Received: (from uucp@localhost) by passer.osg.gov.bc.ca (8.9.3/8.9.1) id MAA64773; Sun, 26 Dec 1999 12:25:37 -0800 (PST) Received: from cwsys.cwsent.com(10.2.2.1) via SMTP by cwtest.cwsent.com, id smtpdt64768; Sun Dec 26 12:24:53 1999 Received: (from uucp@localhost) by cwsys.cwsent.com (8.9.3/8.9.1) id MAA37276; Sun, 26 Dec 1999 12:24:52 -0800 (PST) Message-Id: <199912262024.MAA37276@cwsys.cwsent.com> Received: from localhost.cwsent.com(127.0.0.1), claiming to be "cwsys" via SMTP by localhost.cwsent.com, id smtpda37257; Sun Dec 26 12:24:10 1999 X-Mailer: exmh version 2.1.1 10/15/1999 Reply-To: Cy Schubert - ITSD Open Systems Group From: Cy Schubert - ITSD Open Systems Group X-OS: FreeBSD 3.4-RELEASE X-Sender: cy To: Kevin Entringer Cc: freebsd-stable@freebsd.org Subject: Re: X11 In-reply-to: Your message of "Sun, 26 Dec 1999 11:30:23 CST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 26 Dec 1999 12:24:10 -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Kev in Entringer writes: > Thanks for the suggestion. I suspect that this was the problem, however X > is still not working. The following no happens: > > Dec 26 11:29:13 discord login: ROOT LOGIN (root) ON ttyv3 > Dec 26 11:29:14 discord Xwrapper: unable to dlopen(/usr/lib/pam_unix.so) > Dec 26 11:29:14 discord > Xwrapper: [dlerror: /usr/lib/pam_unix.so: Undefined symb > ol "crypt"] > Dec 26 11:29:14 discord Xwrapper: adding faulty > module: /usr/lib/pam_unix.so It appears that the problem was fixed in -current and not in -stable: markm 1999/09/30 11:53:34 PDT Modified files: lib/libpam/modules/pam_unix Makefile Log: Add libcrypt. This previously/coincidentally worked for login, because login was already linked against it, but others have a problem. Revision Changes Path 1.4 +3 -3 src/lib/libpam/modules/pam_unix/Makefile Even though the patch is for -current, it applies cleanly to -stable. Would someone please MFC this. Kevin, apply the following patch to and rebuild pam_unix. I've modified the "old" $FreeBSD$ to allow the patch to apply cleanly. =================================================================== RCS file: /home/ncvs/src/lib/libpam/modules/pam_unix/Makefile,v retrieving revision 1.3 retrieving revision 1.4 diff -p -u -r1.3 -r1.4 --- src/lib/libpam/modules/pam_unix/Makefile 1999/05/08 01:59:27 1.3 +++ /home/ncvs/src/lib/libpam/modules/pam_unix/Makefile 1999/09/30 18:53:34 1.4 @@ -22,7 +22,7 @@ # OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF # SUCH DAMAGE. # -# $FreeBSD: src/lib/libpam/modules/pam_unix/Makefile,v 1.2.2.1 1999/05/08 21:32:00 jdp Exp $ +# $FreeBSD: src/lib/libpam/modules/pam_unix/Makefile,v 1.3 1999/05/08 01:59:27 jdp Exp $ PAMDIR= ${.CURDIR}/../../../../contrib/libpam @@ -32,8 +32,8 @@ SRCS= pam_unix.c CFLAGS+= -Wall CFLAGS+= -I${PAMDIR}/libpam/include CFLAGS+= -I${.CURDIR}/../../libpam -DPADD+= ${LIBUTIL} ${LIBGCC_PIC} -LDADD+= -lutil -lgcc_pic +DPADD+= ${LIBUTIL} ${LIBGCC_PIC} ${LIBCRYPT} +LDADD+= -lutil -lgcc_pic -lcrypt INTERNALLIB= yes INTERNALSTATICLIB=yes Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 Sun/DEC Team, UNIX Group Internet: Cy.Schubert@uumail.gov.bc.ca ITSD Province of BC "e**(i*pi)+1=0" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 26 14:51:27 1999 Delivered-To: freebsd-stable@freebsd.org Received: from kci.kciLink.com (kci.kciLink.com [204.117.82.1]) by hub.freebsd.org (Postfix) with ESMTP id B49A51525F for ; Sun, 26 Dec 1999 14:51:16 -0800 (PST) (envelope-from khera@kciLink.com) Received: by kci.kciLink.com (Postfix, from userid 100) id D6FC6E8A5; Sun, 26 Dec 1999 17:51:14 -0500 (EST) From: Vivek Khera MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14438.39906.805120.393675@kci.kciLink.com> Date: Sun, 26 Dec 1999 17:51:14 -0500 (EST) To: jack Cc: Kris Kennaway , freebsd-stable@FreeBSD.ORG Subject: Re: three files in /usr/sbin not updated by make world In-Reply-To: References: X-Mailer: VM 6.72 under 21.1 (patch 7) "Biscayne" XEmacs Lucid Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "j" == jack writes: j> They're leftovers from the isdn4bsd upgrade from version 0.71 to j> 0.81 back in May. You'll find the source, and man pages, in the j> src/usr.sbin/i4b/alawulaw directory in the Attic. so can I assume they are safe to delete now? especially if I don't use isdn on this machine? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 26 15:11:19 1999 Delivered-To: freebsd-stable@freebsd.org Received: from germanium.xtalwind.net (germanium.xtalwind.net [205.160.242.5]) by hub.freebsd.org (Postfix) with ESMTP id 278E714FD9 for ; Sun, 26 Dec 1999 15:11:15 -0800 (PST) (envelope-from jack@germanium.xtalwind.net) Received: from localhost (jack@localhost) by germanium.xtalwind.net (8.10.0.Beta10/8.10.0.Beta10) with ESMTP id dBQNBA041010; Sun, 26 Dec 1999 18:11:10 -0500 (EST) Date: Sun, 26 Dec 1999 18:11:10 -0500 (EST) From: jack To: Vivek Khera Cc: freebsd-stable@FreeBSD.ORG Subject: Re: three files in /usr/sbin not updated by make world In-Reply-To: <14438.39906.805120.393675@kci.kciLink.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 Today Vivek Khera wrote: > >>>>> "j" == jack writes: > > j> They're leftovers from the isdn4bsd upgrade from version 0.71 to > j> 0.81 back in May. You'll find the source, and man pages, in the > j> src/usr.sbin/i4b/alawulaw directory in the Attic. > > so can I assume they are safe to delete now? I did, so I sure hope so. :) > especially if I don't use isdn on this machine? Nor do I. -------------------------------------------------------------------------- Jack O'Neill Systems Administrator / Systems Analyst jack@germanium.xtalwind.net Crystal Wind Communications, Inc. Finger jack@germanium.xtalwind.net for my PGP key. PGP Key fingerprint = F6 C4 E6 D4 2F 15 A7 67 FD 09 E9 3C 5F CC EB CD enriched, vcard, HTML messages > /dev/null -------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 26 16:22:39 1999 Delivered-To: freebsd-stable@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id 6955914D15; Sun, 26 Dec 1999 16:22:34 -0800 (PST) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40321>; Mon, 27 Dec 1999 11:13:07 +1100 Content-return: prohibited Date: Mon, 27 Dec 1999 11:22:14 +1100 From: Peter Jeremy Subject: Re: /bin/test broken ? In-reply-to: <19991226013551.A43483@ulstu.ru>; from vss@ulstu.ru on Sun, Dec 26, 1999 at 09:35:52AM +1100 To: Vlad Skvortsov Cc: freebsd-stable@FreeBSD.ORG, sheldonh@FreeBSD.ORG Message-Id: <99Dec27.111307est.40321@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0i Content-type: text/plain; charset=us-ascii References: <99Dec23.123516est.40332@border.alcanet.com.au> <199912232030.MAA65714@pau-amma.whistle.com> <99Dec24.105638est.40325@border.alcanet.com.au> <19991226013551.A43483@ulstu.ru> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 1999-Dec-26 09:35:52 +1100, Vlad Skvortsov wrote: >Subject: Cron /bin/[ -f /var/run/INET ] && /usr/local/bin/fetchmail >[: ]: unexpected operator > >It _did_ work before. Note that your original post was: > $ /bin/test 1 -ne 0 ] > [: ]: unexpected operator Although it seems your real problem is: > $ /bin/[ 1 -ne 0 ] > [: ]: unexpected operator This does make a lot more sense, and would have saved a lot of fruitless searching for a non-existent problem. (It is also why I enquired exactly what you thought was wrong, since your posted output didn't make sense). > I put your attention that you'd try using /bin/[, Note that this is the first time that you've mentioned that your problem is in /bin/[, not /bin/test (yes, they are hard-links, but they have different syntaxes). Given that piece of information, the problem is more obvious: The following code was changed near the top of main() in test.c between 1.20.2.3 and 1.20.2.4 (the tabs have been expanded): - if ((p = argv[0]) == NULL) - errx(2, "test: argc is zero"); - - if (*p != '\0' && p[strlen(p) - 1] == '[') { + if (strcmp(argv[0], "[") == 0) { if (strcmp(argv[--argc], "]")) The new code is incorrect because argv[0] is a pathname, not just a filename. The same problem exists in -current (so I'm surprised no-one else has been bitten). I believe the correst test is something like: char *p; if ((p = strrchr(argv[0], '/')) != NULL) p++; else p = argv[0]; if (strcmp(p, "[") == 0) { if (strcmp(argv[--argc], "]")) > Judjed by my logs the last change to /bin/test was on Dec, 16 or >somewhere about. By Sheldon, so I've copied him. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 26 16:40:10 1999 Delivered-To: freebsd-stable@freebsd.org Received: from web503.mail.yahoo.com (web503.mail.yahoo.com [128.11.68.70]) by hub.freebsd.org (Postfix) with SMTP id C3E6F14F27 for ; Sun, 26 Dec 1999 16:40:05 -0800 (PST) (envelope-from god@yahoo.com) Received: (qmail 25909 invoked by uid 60001); 27 Dec 1999 00:40:05 -0000 Message-ID: <19991227004005.25908.qmail@web503.mail.yahoo.com> Received: from [63.22.81.26] by web503.mail.yahoo.com; Sun, 26 Dec 1999 16:40:05 PST Date: Sun, 26 Dec 1999 16:40:05 -0800 (PST) From: Mike s Subject: FreeBSD Portal To: freebsd-stable@freebsd.org Cc: freebsd-doc@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I changed the subject of this thread from "bugs in the handbook" to " FreeBSd portal to avoid any further confusion of my intentions. Well, i have already taking the iniative in starting what it is i have been talking about. I have a lot of documentation that is done already, ( alot being 35% ) the site is very appealing for those that use netscape and the like and is also lynx friendly. I have already coded alot of user/interactive parts of the site in php. i know there are already several other sites such as freebsddiary.org, freebsdzine.com ( org? ) freebsdrocks.com, that have some useful information. Probably freebsddiary the most useful in my opinion. which again i emphasize , my goal is to create a FreeBSD portal similar to linux.com, not design a whole new site for freebsd.org. If I am solo on this and will have no support from the -doc team ( which i never really intended on having ) I am OK, with that. If i have to develop this site in my own free time it might take me awhile to do but it is a commitment i have made to myself to accomplish. the layout is close to being finished already and about 60% of the php coding is done. once i have enough basic documentation written i will launch the alpha version of the site and announce it in the announce mailing list. before launching the alpha site it will include: -a step by step installation process focused on the novice. -troubleshooting -basic networking support -getting Connected to the internet -all man pages marked outdated/up to date -using CVSup and make world -security related support -what services need to be running for specific server purposes -performance optimization -understanding log files -understanding /etc/*.conf files for the novice -most common asked questions with simple solutions ( Not FAQ's ) -FreeBSD command reference. -UID's and GID's file permissions -introduction to firewalls. -mailing list archives which users will be able to send and recieve via the web the beauty of the site is that user can submit comments to the documentation also add documentation to the subject in mind that will be pre-formatted to the site once submitted and at the bottom of the page will be links to all the comments and addition documentation. I have alot more in mind but this is what i have started to design, i am welcome to any suggestions. so please don't hesitate to let me know of any idea's you may have. On another note: who would i need to speak to about pointing something like portal.freebsd.org to one of my IP's. Or would that be innapropriate? mike god@yahoo.com _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 26 17:42: 8 1999 Delivered-To: freebsd-stable@freebsd.org Received: from green.excel.net (excel.net [156.46.156.2]) by hub.freebsd.org (Postfix) with ESMTP id 05F0915154 for ; Sun, 26 Dec 1999 17:42:04 -0800 (PST) (envelope-from kevin@tarvalon.net) Received: from fdl0047.excel.net (kevin@fdl0047.excel.net [156.46.102.175]) by green.excel.net (8.9.3/8.9.3) with ESMTP id TAA27739; Sun, 26 Dec 1999 19:41:59 -0600 (CST) Date: Sun, 26 Dec 1999 19:41:58 -0600 (CST) From: Kevin Entringer To: Cy Schubert - ITSD Open Systems Group Cc: freebsd-stable@FreeBSD.ORG Subject: Re: X11 In-Reply-To: <199912262024.MAA37276@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 Thanks again for taking the time to help, I applied the patch, it compiled cleanly. Nothing appears now in /var/log/messages when I attempt to startx. However all that happens now is my screen being flooded with: Password: Password: It doesn't stop unless I hit ctrl+c Regards, Kevin On Sun, 26 Dec 1999, Cy Schubert - ITSD Open Systems Group wrote: > In message , Kev > in Entringer writes: > > Thanks for the suggestion. I suspect that this was the problem, however X > > is still not working. The following no happens: > > > > Dec 26 11:29:13 discord login: ROOT LOGIN (root) ON ttyv3 > > Dec 26 11:29:14 discord Xwrapper: unable to dlopen(/usr/lib/pam_unix.so) > > Dec 26 11:29:14 discord > > Xwrapper: [dlerror: /usr/lib/pam_unix.so: Undefined symb > > ol "crypt"] > > Dec 26 11:29:14 discord Xwrapper: adding faulty > > module: /usr/lib/pam_unix.so > > It appears that the problem was fixed in -current and not in -stable: > > markm 1999/09/30 11:53:34 PDT > > Modified files: > lib/libpam/modules/pam_unix Makefile > Log: > Add libcrypt. This previously/coincidentally worked for login, > because login was already linked against it, but others have a > problem. > > Revision Changes Path > 1.4 +3 -3 src/lib/libpam/modules/pam_unix/Makefile > > Even though the patch is for -current, it applies cleanly to -stable. > Would someone please MFC this. > > Kevin, apply the following patch to and rebuild pam_unix. I've > modified the "old" $FreeBSD$ to allow the patch to apply cleanly. > > =================================================================== > RCS file: /home/ncvs/src/lib/libpam/modules/pam_unix/Makefile,v > retrieving revision 1.3 > retrieving revision 1.4 > diff -p -u -r1.3 -r1.4 > --- src/lib/libpam/modules/pam_unix/Makefile 1999/05/08 01:59:27 1.3 > +++ /home/ncvs/src/lib/libpam/modules/pam_unix/Makefile 1999/09/30 18:53:34 1.4 > @@ -22,7 +22,7 @@ > # OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF > # SUCH DAMAGE. > # > -# $FreeBSD: src/lib/libpam/modules/pam_unix/Makefile,v 1.2.2.1 1999/05/08 21:32:00 jdp Exp $ > +# $FreeBSD: src/lib/libpam/modules/pam_unix/Makefile,v 1.3 1999/05/08 01:59:27 jdp Exp $ > > PAMDIR= ${.CURDIR}/../../../../contrib/libpam > > @@ -32,8 +32,8 @@ SRCS= pam_unix.c > CFLAGS+= -Wall > CFLAGS+= -I${PAMDIR}/libpam/include > CFLAGS+= -I${.CURDIR}/../../libpam > -DPADD+= ${LIBUTIL} ${LIBGCC_PIC} > -LDADD+= -lutil -lgcc_pic > +DPADD+= ${LIBUTIL} ${LIBGCC_PIC} ${LIBCRYPT} > +LDADD+= -lutil -lgcc_pic -lcrypt > INTERNALLIB= yes > INTERNALSTATICLIB=yes > > > > Regards, Phone: (250)387-8437 > Cy Schubert Fax: (250)387-5766 > Sun/DEC Team, UNIX Group Internet: Cy.Schubert@uumail.gov.bc.ca > ITSD > Province of BC > "e**(i*pi)+1=0" > > > > > > 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 Dec 26 18:33:58 1999 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 6ADF114E08 for ; Sun, 26 Dec 1999 18:33:55 -0800 (PST) (envelope-from cy@cschuber.net.gov.bc.ca) Received: (from daemon@localhost) by point.osg.gov.bc.ca (8.8.7/8.8.8) id SAA10379; Sun, 26 Dec 1999 18:33:48 -0800 Received: from passer.osg.gov.bc.ca(142.32.110.29) via SMTP by point.osg.gov.bc.ca, id smtpda10377; Sun Dec 26 18:33:44 1999 Received: (from uucp@localhost) by passer.osg.gov.bc.ca (8.9.3/8.9.1) id SAA65543; Sun, 26 Dec 1999 18:33:44 -0800 (PST) Received: from cwsys.cwsent.com(10.2.2.1) via SMTP by cwtest.cwsent.com, id smtpdQ65541; Sun Dec 26 18:32:51 1999 Received: (from uucp@localhost) by cwsys.cwsent.com (8.9.3/8.9.1) id SAA01945; Sun, 26 Dec 1999 18:32:50 -0800 (PST) Message-Id: <199912270232.SAA01945@cwsys.cwsent.com> Received: from localhost.cwsent.com(127.0.0.1), claiming to be "cwsys" via SMTP by localhost.cwsent.com, id smtpdxn1941; Sun Dec 26 18:32:26 1999 X-Mailer: exmh version 2.1.1 10/15/1999 Reply-To: Cy Schubert - ITSD Open Systems Group From: Cy Schubert - ITSD Open Systems Group X-OS: FreeBSD 3.4-RELEASE X-Sender: cy To: Kevin Entringer Cc: Cy Schubert - ITSD Open Systems Group , freebsd-stable@FreeBSD.ORG Subject: Re: X11 In-reply-to: Your message of "Sun, 26 Dec 1999 19:41:58 CST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 26 Dec 1999 18:32:26 -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Interesting. Try ldconfig -R -elf and restart all apps using the shared library or reboot. As I've been debugging my dhclient-script, I did perform a number of reboots since applying the patch. I suppose a reboot may be the reason it works for me. Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 Sun/DEC Team, UNIX Group Internet: Cy.Schubert@uumail.gov.bc.ca ITSD Province of BC "e**(i*pi)+1=0" In message , Kevin Entringer writes: > Thanks again for taking the time to help, I applied the patch, it compiled > cleanly. Nothing appears now in /var/log/messages when I attempt to > startx. However all that happens now is my screen being flooded with: > > Password: > Password: > > It doesn't stop unless I hit ctrl+c > > Regards, Kevin > > On Sun, 26 Dec 1999, Cy Schubert - ITSD Open Systems Group wrote: > > > In message , > Kev > > in Entringer writes: > > > Thanks for the suggestion. I suspect that this was the problem, however > X > > > is still not working. The following no happens: > > > > > > Dec 26 11:29:13 discord login: ROOT LOGIN (root) ON ttyv3 > > > Dec 26 11:29:14 discord Xwrapper: unable to dlopen(/usr/lib/pam_unix.so) > > > Dec 26 11:29:14 discord > > > Xwrapper: [dlerror: /usr/lib/pam_unix.so: Undefined symb > > > ol "crypt"] > > > Dec 26 11:29:14 discord Xwrapper: adding faulty > > > module: /usr/lib/pam_unix.so > > > > It appears that the problem was fixed in -current and not in -stable: > > > > markm 1999/09/30 11:53:34 PDT > > > > Modified files: > > lib/libpam/modules/pam_unix Makefile > > Log: > > Add libcrypt. This previously/coincidentally worked for login, > > because login was already linked against it, but others have a > > problem. > > > > Revision Changes Path > > 1.4 +3 -3 src/lib/libpam/modules/pam_unix/Makefile > > > > Even though the patch is for -current, it applies cleanly to -stable. > > Would someone please MFC this. > > > > Kevin, apply the following patch to and rebuild pam_unix. I've > > modified the "old" $FreeBSD$ to allow the patch to apply cleanly. > > > > =================================================================== > > RCS file: /home/ncvs/src/lib/libpam/modules/pam_unix/Makefile,v > > retrieving revision 1.3 > > retrieving revision 1.4 > > diff -p -u -r1.3 -r1.4 > > --- src/lib/libpam/modules/pam_unix/Makefile 1999/05/08 01:59:27 > 1.3 > > +++ /home/ncvs/src/lib/libpam/modules/pam_unix/Makefile 1999/09/30 18:5 > 3:34 1.4 > > @@ -22,7 +22,7 @@ > > # OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF > > # SUCH DAMAGE. > > # > > -# $FreeBSD: src/lib/libpam/modules/pam_unix/Makefile,v 1.2.2.1 1999/05/08 > 21:32:00 jdp Exp $ > > +# $FreeBSD: src/lib/libpam/modules/pam_unix/Makefile,v 1.3 1999/05/08 01: > 59:27 jdp Exp $ > > > > PAMDIR= ${.CURDIR}/../../../../contrib/libpam > > > > @@ -32,8 +32,8 @@ SRCS= pam_unix.c > > CFLAGS+= -Wall > > CFLAGS+= -I${PAMDIR}/libpam/include > > CFLAGS+= -I${.CURDIR}/../../libpam > > -DPADD+= ${LIBUTIL} ${LIBGCC_PIC} > > -LDADD+= -lutil -lgcc_pic > > +DPADD+= ${LIBUTIL} ${LIBGCC_PIC} ${LIBCRYPT} > > +LDADD+= -lutil -lgcc_pic -lcrypt > > INTERNALLIB= yes > > INTERNALSTATICLIB=yes > > > > > > > > Regards, Phone: (250)387-8437 > > Cy Schubert Fax: (250)387-5766 > > Sun/DEC Team, UNIX Group Internet: Cy.Schubert@uumail.gov.bc.ca > > ITSD > > Province of BC > > "e**(i*pi)+1=0" > > > > > > > > > > > > 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 Sun Dec 26 20:50:10 1999 Delivered-To: freebsd-stable@freebsd.org Received: from sanson.reyes.somos.net (freyes.static.inch.com [207.240.212.43]) by hub.freebsd.org (Postfix) with ESMTP id 885B514ED5; Sun, 26 Dec 1999 20:50:04 -0800 (PST) (envelope-from fran@reyes.somos.net) Received: from tomasa (tomasa.reyes.somos.net [10.0.0.11]) by sanson.reyes.somos.net (8.9.3/8.9.3) with SMTP id XAA63199; Sun, 26 Dec 1999 23:47:58 -0500 (EST) (envelope-from fran@reyes.somos.net) Message-Id: <199912270447.XAA63199@sanson.reyes.somos.net> From: "Francisco Reyes" To: "Colin" , "Mike s" Cc: "freebsd-doc@freebsd.org" , "stable@FreeBSD.ORG" Date: Sun, 26 Dec 1999 23:47:52 -0500 Reply-To: "Francisco Reyes" X-Mailer: PMMail 98 Professional (2.01.1600) For Windows 98 (4.10.1998) MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Subject: Re: bugs in the handbook. (FreeBSD Portal) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 25 Dec 1999 01:21:21 -0800 (PST), Mike s wrote: >again take linux.com for example. IF we had volunteers >who had knowledge of the latest web development >resources/languages such as sPHP we can start a site >that is based mostly on volunteers as is linux.com FreeBSD.org IS based on volunteers. Why not try to improve that site before adding yet another site? >again, not to compete at all with freebsd.org a >separate entity entirely. If you make a separate site, not only YOU ARE competing, but you are not helping on getting the problems you think that site has. >besides, a lot of people who would commit to -docs >don't have the knowledge or patience to learn the SGML >structure if the site itself. Have you looked at the Doc primer? >I'd like to see a site going up utilizing php/mysql >for fast and convenient site development. This has been discussed in the past.. There are problems with this approach. The biggest one is that this makes the site much more harder to mirror. >I guess i will start by saying that I am willing to >donate a considerable ammount of time to working on >this project. So why not take 2 to 4 hours to go over the Doc primer and learn how to submit work to the Doc project. Then submit new docs or improvements to existing docs. >If anyone else is interested in helping out send me an >email with subject "FreeBSD Portal Volunteer" and once >we reach a sufficient ammount of volunteers. ( say 5 >or 6 ) well, we can get things under way. The effort that it would take to start yet another site could be much better spent improving the existing FreeBSD.org site. Have you ever attempted to help the Doc group? Have you contacted them with any issues thoughts you may have about the existing site? Can we move this discussion to the Doc list? It really does not belong in stable. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 26 22: 5:18 1999 Delivered-To: freebsd-stable@freebsd.org Received: from jade.chc-chimes.com (jade.chc-chimes.com [216.28.46.6]) by hub.freebsd.org (Postfix) with ESMTP id 55C4114C4B; Sun, 26 Dec 1999 22:05:13 -0800 (PST) (envelope-from billf@chc-chimes.com) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id C8C811C57; Mon, 27 Dec 1999 01:04:26 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by jade.chc-chimes.com (Postfix) with ESMTP id BA0EB381B; Mon, 27 Dec 1999 01:04:26 -0500 (EST) Date: Mon, 27 Dec 1999 01:04:26 -0500 (EST) From: Bill Fumerola To: Mike s Cc: freebsd-stable@freebsd.org, freebsd-doc@freebsd.org Subject: Re: FreeBSD Portal In-Reply-To: <19991227004005.25908.qmail@web503.mail.yahoo.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 26 Dec 1999, Mike s wrote: > before launching the alpha site it will include: > > -a step by step installation process focused on the > novice. > -troubleshooting > -basic networking support > -getting Connected to the internet > -all man pages marked outdated/up to date > -using CVSup and make world > -security related support > -what services need to be running for specific server > purposes > -performance optimization > -understanding log files > -understanding /etc/*.conf files for the novice > -most common asked questions with simple solutions ( > Not FAQ's ) > -FreeBSD command reference. > -UID's and GID's file permissions > -introduction to firewalls. > -mailing list archives which users will be able to > send and recieve via the web These all look like current FAQ/handbook headings/chapters/whatever. Wouldn't it (again) just be easier to send in updates to those existing pages? -- - bill fumerola - billf@chc-chimes.com - BF1560 - computer horizons corp - - ph:(800) 252-2421 - bfumerol@computerhorizons.com - billf@FreeBSD.org - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 26 22:44:39 1999 Delivered-To: freebsd-stable@freebsd.org Received: from pooh.elsevier.nl (p198.as1.naas1.eircom.net [159.134.254.198]) by hub.freebsd.org (Postfix) with ESMTP id E325315067; Sun, 26 Dec 1999 22:44:25 -0800 (PST) (envelope-from steve@pooh.elsevier.nl) Received: (from steve@localhost) by pooh.elsevier.nl (8.9.3/8.9.3) id GAA11676; Mon, 27 Dec 1999 06:44:30 GMT (envelope-from steve) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Mon, 27 Dec 1999 06:44:09 -0000 (GMT) From: "Steve O'Hara-Smith" To: Bill Fumerola Subject: Re: FreeBSD Portal Cc: freebsd-doc@freebsd.org, freebsd-stable@freebsd.org, Mike s Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > These all look like current FAQ/handbook headings/chapters/whatever. > > Wouldn't it (again) just be easier to send in updates to those existing > pages? Speaking as a user that is what I would prefer to see (personally I've always found the documentation adequate and the freebsd.org site useful). I do not see it as helpful to have fragmented documentation sites. Perhaps what would be helpful would be to make this user commenting technology available in links from freebsd.org. However it is a free world (ish) do as you will (of course). It may well be useful to somebody. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 27 1:28:26 1999 Delivered-To: freebsd-stable@freebsd.org Received: from pikachu.bsp.bc.niigata-u.ac.jp (pikachu.bsp.bc.niigata-u.ac.jp [133.35.85.2]) by hub.freebsd.org (Postfix) with SMTP id 597D714D66 for ; Mon, 27 Dec 1999 01:28:17 -0800 (PST) (envelope-from iwaki@bc.niigata-u.ac.jp) Received: (qmail 1371 invoked by alias); 27 Dec 1999 18:27:59 +0900 Message-ID: <19991227092759.1369.qmail@pikachu.bsp.bc.niigata-u.ac.jp> To: freebsd-stable@FreeBSD.ORG Subject: linux emulation on 3.4-stable X-Mailer: Mew version 1.94 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Mon, 27 Dec 1999 18:27:58 +0900 From: Mamoru Iwaki X-Dispatcher: imput version 990905(IM130) Lines: 19 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I met warnings like LINUX: 'ioctl' fd=9, typ=0x44d(M), num=0x76 not implemented LINUX: 'ioctl' fd=7, typ=0x44d(M), num=0x76 not implemented when realplay was running. The program is an alpha 2 release of RealPlayer G2 for Linux 2.0/2.2 and we can get from http://www.real.com/products/player/linux.html Please implement these ioctl's. --- ----- Mamoru IWAKI (iwaki@bc.niigata-u.ac.jp) Graduate School of Science and Technology, Niigata University ----- $B?73cBg3X(B $BBg3X1!<+A32J3X8&5f2J(B $B4d>k(B $B8n(B (iwaki@bc.niigata-u.ac.jp) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 27 2: 6:47 1999 Delivered-To: freebsd-stable@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id AE57E14C88; Mon, 27 Dec 1999 02:06:45 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 9774D1CD820; Mon, 27 Dec 1999 02:06:45 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Mon, 27 Dec 1999 02:06:45 -0800 (PST) From: Kris Kennaway To: Vivek Khera Cc: jack , freebsd-stable@FreeBSD.ORG Subject: Re: three files in /usr/sbin not updated by make world In-Reply-To: <14438.39906.805120.393675@kci.kciLink.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 26 Dec 1999, Vivek Khera wrote: > j> They're leftovers from the isdn4bsd upgrade from version 0.71 to > j> 0.81 back in May. You'll find the source, and man pages, in the > j> src/usr.sbin/i4b/alawulaw directory in the Attic. > > so can I assume they are safe to delete now? especially if I don't > use isdn on this machine? Yes. Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 27 2:41:27 1999 Delivered-To: freebsd-stable@freebsd.org Received: from me.ru (shell.me.ru [194.247.134.140]) by hub.freebsd.org (Postfix) with ESMTP id 8990C14FAD for ; Mon, 27 Dec 1999 02:41:05 -0800 (PST) (envelope-from ilya@zhurnal.ru) Received: from [194.247.147.206] (HELO webmaster.zhurnal.ru) by me.ru (CommuniGate Pro SMTP 3.1) with ESMTP id 266839 for stable@freebsd.org; Mon, 27 Dec 1999 13:41:03 +0300 Date: Mon, 27 Dec 1999 13:43:30 +0300 From: Ilya Obshadko X-Mailer: The Bat! (v1.36) S/N FE0A Reply-To: Ilya Obshadko Organization: Zhurnal.RU X-Priority: 3 (Normal) Message-ID: <10571.991227@zhurnal.ru> To: stable@freebsd.org Subject: IPFILTER: problem with denied ACK packets 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 Hello, Here's a strange problem with IPFILTER. Rulefile looks like this: block in log on de0 all pass in quick on de0 proto icmp from any to any pass out quick on de0 proto icmp from any to any pass out quick on de0 proto tcp from OUR_NET to any keep state keep frags pass out quick on de0 proto udp from OUR_NET to any keep state keep frags As far as I know, this set of rules allows all outbound traffic without any restrictions. But, when I'm trying to send a large amount of data (i.e. file attach) via SMTP, sending stops after about 10 kbytes. Both tcpdump and ipmon shows denied ACK tcp packets that SMTP server sends back to my machine. Seems like those ACK packets are not counted as a part of "keep state" rule by IPFILTER. The problem can be solved by explicit rule: pass in quick on de0 proto tcp from MY_SMTP_SERVER port = smtp to MY_MACHINE But this doesn't seem to be a secure and reliable way. Even more, if I enable, by the way, inbound ftp on any of machines in our net and try to download any file from outside, the sympthoms are exactly the same: transfer stops after ~10 kbytes, tcpdump & ipmon says about denied ACK packets etc... Best regards, Ilya mailto:ilya@zhurnal.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 27 2:42: 0 1999 Delivered-To: freebsd-stable@freebsd.org Received: from pooh.elsevier.nl (p91.as1.naas1.eircom.net [159.134.254.91]) by hub.freebsd.org (Postfix) with ESMTP id 20AB214F03 for ; Mon, 27 Dec 1999 02:41:55 -0800 (PST) (envelope-from steve@pooh.elsevier.nl) Received: (from steve@localhost) by pooh.elsevier.nl (8.9.3/8.9.3) id KAA15598; Mon, 27 Dec 1999 10:41:54 GMT (envelope-from steve) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <19991227092759.1369.qmail@pikachu.bsp.bc.niigata-u.ac.jp> Date: Mon, 27 Dec 1999 10:41:33 -0000 (GMT) From: "Steve O'Hara-Smith" To: Mamoru Iwaki Subject: RE: linux emulation on 3.4-stable Cc: freebsd-stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 27-Dec-99 Mamoru Iwaki wrote: > Hi, > > I met warnings like > > LINUX: 'ioctl' fd=9, typ=0x44d(M), num=0x76 not implemented > LINUX: 'ioctl' fd=7, typ=0x44d(M), num=0x76 not implemented > > when realplay was running. The program is an alpha 2 release of > RealPlayer G2 for Linux 2.0/2.2 and we can get from > http://www.real.com/products/player/linux.html Did the RealPlayer G2 work ? A few unimplemented messages do not necessarily prevent linux apps from running (I have no idea what these ones do BTW). Nor are they necessarily a bug or problem sometimes they simply reflect things required in Linux and not in FreeBSD. > Please implement these ioctl's. I suspect that this will only happen if/when i) They are needed (to make something work). ii) Somebody implements them. BTW: I am just a user (who has run the Linux G2 alpha without problems). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 27 5:36:32 1999 Delivered-To: freebsd-stable@freebsd.org Received: from netcom.com (netcom5.netcom.com [199.183.9.105]) by hub.freebsd.org (Postfix) with ESMTP id 53D4315018 for ; Mon, 27 Dec 1999 05:36:14 -0800 (PST) (envelope-from stanb@netcom.com) Received: (from stanb@localhost) by netcom.com (8.9.3/8.9.3) id FAA14584 for freebsd-stable@freebsd.org; Mon, 27 Dec 1999 05:36:12 -0800 (PST) From: Stan Brown Message-Id: <199912271336.FAA14584@netcom.com> Subject: Huge differences in suid programs ? To: freebsd-stable@freebsd.org (FreeBSD Stable List) Date: Mon, 27 Dec 1999 08:36:11 -0500 (EST) X-Mailer: ELM [version 2.4 PL25] 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 I cvsuped 3 machines and did a make worlds on the yesterday. I got HUGE differences on the suid files in the security report this morning: polar.fas.com setuid diffs: 1,12c1,12 < -r-xr-sr-x 1 root operator 51196 Dec 5 22:22:13 1999 /bin/df < -r-xr-sr-x 1 root kmem 189664 Dec 5 22:22:26 1999 /bin/ps < -r-sr-xr-x 1 root wheel 208408 Dec 5 22:22:29 1999 /bin/rcp < -r-xr-sr-x 1 root kmem 100148 Dec 5 22:33:20 1999 /sbin/ccdconfig < -r-xr-sr-x 1 root kmem 103696 Dec 5 22:33:27 1999 /sbin/dmesg < -r-xr-sr-x 2 root tty 221736 Dec 5 22:33:28 1999 /sbin/dump < -r-sr-xr-x 1 root wheel 145528 Dec 5 22:34:11 1999 /sbin/ping < -r-xr-sr-x 2 root tty 221736 Dec 5 22:33:28 1999 /sbin/rdump < -r-xr-sr-x 2 root tty 244920 Dec 5 22:34:16 1999 /sbin/restore < -r-sr-xr-x 1 root wheel 153760 Dec 5 22:34:18 1999 /sbin/route < -r-xr-sr-x 2 root tty 244920 Dec 5 22:34:16 1999 /sbin/rrestore < -r-sr-x--- 1 root operator 151712 Dec 5 22:34:22 1999 /sbin/shutdown --- > -r-xr-sr-x 1 root operator 51204 Dec 26 15:01:26 1999 /bin/df > -r-xr-sr-x 1 root kmem 190016 Dec 26 15:01:40 1999 /bin/ps > -r-sr-xr-x 1 root wheel 208408 Dec 26 15:01:43 1999 /bin/rcp > -r-xr-sr-x 1 root kmem 100156 Dec 26 15:12:33 1999 /sbin/ccdconfig > -r-xr-sr-x 1 root kmem 103872 Dec 26 15:12:39 1999 /sbin/dmesg > -r-xr-sr-x 2 root tty 221768 Dec 26 15:12:40 1999 /sbin/dump > -r-sr-xr-x 1 root wheel 145544 Dec 26 15:13:24 1999 /sbin/ping > -r-xr-sr-x 2 root tty 221768 Dec 26 15:12:40 1999 /sbin/rdump > -r-xr-sr-x 2 root tty 244920 Dec 26 15:13:28 1999 /sbin/restore > -r-sr-xr-x 1 root wheel 153760 Dec 26 15:13:30 1999 /sbin/route > -r-xr-sr-x 2 root tty 244920 Dec 26 15:13:28 1999 /sbin/rrestore > -r-sr-x--- 1 root operator 151712 Dec 26 15:13:36 1999 /sbin/shutdown 23,50c23,50 < -r-sr-xr-x 4 root wheel 17448 Dec 5 22:39:01 1999 /usr/bin/at < -r-sr-xr-x 4 root wheel 17448 Dec 5 22:39:01 1999 /usr/bin/atq < -r-sr-xr-x 4 root wheel 17448 Dec 5 22:39:01 1999 /usr/bin/atrm < -r-sr-xr-x 4 root wheel 17448 Dec 5 22:39:01 1999 /usr/bin/batch < -r-sr-xr-x 6 root wheel 28932 Dec 5 22:39:15 1999 /usr/bin/chfn < -r-sr-xr-x 6 root wheel 28932 Dec 5 22:39:15 1999 /usr/bin/chpass < -r-sr-xr-x 6 root wheel 28932 Dec 5 22:39:15 1999 /usr/bin/chsh < -r-sr-xr-x 1 root wheel 21028 Dec 5 22:42:54 1999 /usr/bin/crontab < -r-sr-sr-x 1 uucp dialer 110760 Dec 5 22:24:40 1999 /usr/bin/cu < -r-xr-sr-x 1 root kmem 10160 Dec 5 22:39:53 1999 /usr/bin/fstat < -r-sr-xr-x 5 root wheel 290448 Dec 5 22:44:46 1999 /usr/bin/hoststat < -r-xr-sr-x 1 root kmem 8728 Dec 5 22:40:07 1999 /usr/bin/ipcs < -r-sr-xr-x 1 root wheel 514 Dec 5 22:40:11 1999 /usr/bin/keyinfo < -r-sr-xr-x 1 root wheel 6556 Dec 5 22:40:12 1999 /usr/bin/keyinit < -r-sr-xr-x 1 root wheel 5656 Dec 5 22:40:26 1999 /usr/bin/lock < -r-sr-xr-x 1 root wheel 17624 Dec 5 22:40:29 1999 /usr/bin/login < -r-sr-sr-x 1 root daemon 18064 Dec 5 22:43:18 1999 /usr/bin/lpq < -r-sr-sr-x 1 root daemon 20864 Dec 5 22:43:19 1999 /usr/bin/lpr < -r-sr-sr-x 1 root daemon 17624 Dec 5 22:43:20 1999 /usr/bin/lprm < -r-sr-xr-x 5 root wheel 290448 Dec 5 22:44:46 1999 /usr/bin/mailq < -r-sr-xr-x 1 man wheel 23948 Dec 5 22:27:28 1999 /usr/bin/man < -r-xr-sr-x 1 root kmem 44536 Dec 5 22:40:52 1999 /usr/bin/netstat < -r-sr-xr-x 5 root wheel 290448 Dec 5 22:44:46 1999 /usr/bin/newaliases < -r-xr-sr-x 1 root kmem 7380 Dec 5 22:40:54 1999 /usr/bin/nfsstat < -r-sr-xr-x 2 root wheel 23984 Dec 5 22:41:02 1999 /usr/bin/passwd < -r-sr-xr-x 1 root wheel 10036 Dec 5 22:41:06 1999 /usr/bin/quota < -r-sr-xr-x 1 root wheel 8888 Dec 5 22:41:08 1999 /usr/bin/rlogin < -r-sr-xr-x 1 root wheel 6768 Dec 5 22:41:11 1999 /usr/bin/rsh --- > -r-sr-xr-x 4 root wheel 17448 Dec 26 15:18:22 1999 /usr/bin/at > -r-sr-xr-x 4 root wheel 17448 Dec 26 15:18:22 1999 /usr/bin/atq > -r-sr-xr-x 4 root wheel 17448 Dec 26 15:18:22 1999 /usr/bin/atrm > -r-sr-xr-x 4 root wheel 17448 Dec 26 15:18:22 1999 /usr/bin/batch > -r-sr-xr-x 6 root wheel 28932 Dec 26 15:18:36 1999 /usr/bin/chfn > -r-sr-xr-x 6 root wheel 28932 Dec 26 15:18:36 1999 /usr/bin/chpass > -r-sr-xr-x 6 root wheel 28932 Dec 26 15:18:36 1999 /usr/bin/chsh > -r-sr-xr-x 1 root wheel 21028 Dec 26 15:22:19 1999 /usr/bin/crontab > -r-sr-sr-x 1 uucp dialer 110760 Dec 26 15:03:55 1999 /usr/bin/cu > -r-xr-sr-x 1 root kmem 10160 Dec 26 15:19:12 1999 /usr/bin/fstat > -r-sr-xr-x 5 root wheel 290448 Dec 26 15:24:16 1999 /usr/bin/hoststat > -r-xr-sr-x 1 root kmem 8728 Dec 26 15:19:26 1999 /usr/bin/ipcs > -r-sr-xr-x 1 root wheel 514 Dec 26 15:19:31 1999 /usr/bin/keyinfo > -r-sr-xr-x 1 root wheel 6556 Dec 26 15:19:31 1999 /usr/bin/keyinit > -r-sr-xr-x 1 root wheel 5656 Dec 26 15:19:46 1999 /usr/bin/lock > -r-sr-xr-x 1 root wheel 17624 Dec 26 15:19:48 1999 /usr/bin/login > -r-sr-sr-x 1 root daemon 18064 Dec 26 15:22:44 1999 /usr/bin/lpq > -r-sr-sr-x 1 root daemon 20864 Dec 26 15:22:45 1999 /usr/bin/lpr > -r-sr-sr-x 1 root daemon 17624 Dec 26 15:22:46 1999 /usr/bin/lprm > -r-sr-xr-x 5 root wheel 290448 Dec 26 15:24:16 1999 /usr/bin/mailq > -r-sr-xr-x 1 man wheel 23948 Dec 26 15:06:43 1999 /usr/bin/man > -r-xr-sr-x 1 root kmem 44536 Dec 26 15:20:12 1999 /usr/bin/netstat > -r-sr-xr-x 5 root wheel 290448 Dec 26 15:24:16 1999 /usr/bin/newaliases > -r-xr-sr-x 1 root kmem 7380 Dec 26 15:20:14 1999 /usr/bin/nfsstat > -r-sr-xr-x 2 root wheel 23984 Dec 26 15:20:22 1999 /usr/bin/passwd > -r-sr-xr-x 1 root wheel 10036 Dec 26 15:20:25 1999 /usr/bin/quota > -r-sr-xr-x 1 root wheel 8888 Dec 26 15:20:28 1999 /usr/bin/rlogin > -r-sr-xr-x 1 root wheel 6768 Dec 26 15:20:30 1999 /usr/bin/rsh 52,73c52,73 < -r-s--x--x 2 root wheel 47472 Dec 5 22:30:18 1999 /usr/bin/sperl5.00503 < -r-sr-xr-x 1 root wheel 7404 Dec 5 22:41:21 1999 /usr/bin/su < -r-s--x--x 2 root wheel 47472 Dec 5 22:30:18 1999 /usr/bin/suidperl < -r-xr-sr-x 1 root kmem 52424 Dec 5 22:41:23 1999 /usr/bin/systat < -r-xr-sr-x 1 root kmem 30376 Dec 5 22:41:34 1999 /usr/bin/top < -r-xr-sr-x 2 root kmem 10576 Dec 5 22:41:59 1999 /usr/bin/uptime < -r-sr-xr-x 1 uucp wheel 79112 Dec 5 22:24:45 1999 /usr/bin/uucp < -r-sr-xr-x 1 uucp wheel 33480 Dec 5 22:24:46 1999 /usr/bin/uuname < -r-sr-sr-x 1 uucp dialer 86556 Dec 5 22:24:50 1999 /usr/bin/uustat < -r-sr-xr-x 1 uucp wheel 79936 Dec 5 22:24:51 1999 /usr/bin/uux < -r-xr-sr-x 1 root kmem 14536 Dec 5 22:41:58 1999 /usr/bin/vmstat < -r-xr-sr-x 2 root kmem 10576 Dec 5 22:41:59 1999 /usr/bin/w < -r-xr-sr-x 1 root tty 8108 Dec 5 22:42:01 1999 /usr/bin/wall < -r-xr-sr-x 1 root tty 6692 Dec 5 22:42:07 1999 /usr/bin/write < -r-sr-xr-x 6 root wheel 28932 Dec 5 22:39:15 1999 /usr/bin/ypchfn < -r-sr-xr-x 6 root wheel 28932 Dec 5 22:39:15 1999 /usr/bin/ypchpass < -r-sr-xr-x 6 root wheel 28932 Dec 5 22:39:15 1999 /usr/bin/ypchsh < -r-sr-xr-x 2 root wheel 23984 Dec 5 22:41:02 1999 /usr/bin/yppasswd < -r-xr-sr-x 1 root games 6188 Dec 5 22:22:52 1999 /usr/games/dm < -r-sr-xr-x 1 root wheel 15040 Dec 5 22:33:10 1999 /usr/libexec/mail.local < -r-sr-sr-x 1 uucp dialer 197552 Dec 5 22:24:43 1999 /usr/libexec/uucp/uucico < -r-sr-s--- 1 uucp uucp 89160 Dec 5 22:24:53 1999 /usr/libexec/uucp/uuxqt --- > -r-s--x--x 2 root wheel 47472 Dec 26 15:09:31 1999 /usr/bin/sperl5.00503 > -r-sr-xr-x 1 root wheel 7404 Dec 26 15:20:40 1999 /usr/bin/su > -r-s--x--x 2 root wheel 47472 Dec 26 15:09:31 1999 /usr/bin/suidperl > -r-xr-sr-x 1 root kmem 52424 Dec 26 15:20:42 1999 /usr/bin/systat > -r-xr-sr-x 1 root kmem 30376 Dec 26 15:20:53 1999 /usr/bin/top > -r-xr-sr-x 2 root kmem 10576 Dec 26 15:21:19 1999 /usr/bin/uptime > -r-sr-xr-x 1 uucp wheel 79112 Dec 26 15:03:59 1999 /usr/bin/uucp > -r-sr-xr-x 1 uucp wheel 33480 Dec 26 15:04:01 1999 /usr/bin/uuname > -r-sr-sr-x 1 uucp dialer 86556 Dec 26 15:04:04 1999 /usr/bin/uustat > -r-sr-xr-x 1 uucp wheel 79936 Dec 26 15:04:06 1999 /usr/bin/uux > -r-xr-sr-x 1 root kmem 14536 Dec 26 15:21:17 1999 /usr/bin/vmstat > -r-xr-sr-x 2 root kmem 10576 Dec 26 15:21:19 1999 /usr/bin/w > -r-xr-sr-x 1 root tty 8108 Dec 26 15:21:20 1999 /usr/bin/wall > -r-xr-sr-x 1 root tty 6692 Dec 26 15:21:26 1999 /usr/bin/write > -r-sr-xr-x 6 root wheel 28932 Dec 26 15:18:36 1999 /usr/bin/ypchfn > -r-sr-xr-x 6 root wheel 28932 Dec 26 15:18:36 1999 /usr/bin/ypchpass > -r-sr-xr-x 6 root wheel 28932 Dec 26 15:18:36 1999 /usr/bin/ypchsh > -r-sr-xr-x 2 root wheel 23984 Dec 26 15:20:22 1999 /usr/bin/yppasswd > -r-xr-sr-x 1 root games 6188 Dec 26 15:02:07 1999 /usr/games/dm > -r-sr-xr-x 1 root wheel 15040 Dec 26 15:12:21 1999 /usr/libexec/mail.local > -r-sr-sr-x 1 uucp dialer 197552 Dec 26 15:03:58 1999 /usr/libexec/uucp/uucico > -r-sr-s--- 1 uucp uucp 89160 Dec 26 15:04:07 1999 /usr/libexec/uucp/uuxqt 80,93c80,93 < -r-xr-sr-x 1 root kmem 9472 Dec 5 22:43:02 1999 /usr/sbin/iostat < -r-xr-sr-x 1 root daemon 23968 Dec 5 22:43:16 1999 /usr/sbin/lpc < -r-sr-xr-x 1 root wheel 14528 Dec 5 22:43:29 1999 /usr/sbin/mrinfo < -r-sr-xr-x 1 root wheel 27528 Dec 5 22:43:30 1999 /usr/sbin/mtrace < -r-sr-xr-- 1 root network 237236 Dec 5 22:43:52 1999 /usr/sbin/ppp < -r-sr-xr-x 1 root wheel 86632 Dec 5 22:43:54 1999 /usr/sbin/pppd < -r-xr-sr-x 2 root kmem 13184 Dec 5 22:43:56 1999 /usr/sbin/pstat < -r-sr-xr-x 5 root wheel 290448 Dec 5 22:44:46 1999 /usr/sbin/purgestat < -r-sr-xr-x 5 root wheel 290448 Dec 5 22:44:46 1999 /usr/sbin/sendmail < -r-sr-x--- 1 root network 9768 Dec 5 22:44:10 1999 /usr/sbin/sliplogin < -r-xr-sr-x 2 root kmem 13184 Dec 5 22:43:56 1999 /usr/sbin/swapinfo < -r-sr-xr-x 1 root wheel 13440 Dec 5 22:44:19 1999 /usr/sbin/timedc < -r-sr-xr-x 1 root wheel 11232 Dec 5 22:44:20 1999 /usr/sbin/traceroute < -r-xr-sr-x 1 root kmem 7036 Dec 5 22:44:21 1999 /usr/sbin/trpt --- > -r-xr-sr-x 1 root kmem 9472 Dec 26 15:22:29 1999 /usr/sbin/iostat > -r-xr-sr-x 1 root daemon 23968 Dec 26 15:22:42 1999 /usr/sbin/lpc > -r-sr-xr-x 1 root wheel 14528 Dec 26 15:22:54 1999 /usr/sbin/mrinfo > -r-sr-xr-x 1 root wheel 27528 Dec 26 15:22:55 1999 /usr/sbin/mtrace > -r-sr-xr-- 1 root network 237240 Dec 26 15:23:15 1999 /usr/sbin/ppp > -r-sr-xr-x 1 root wheel 86632 Dec 26 15:23:18 1999 /usr/sbin/pppd > -r-xr-sr-x 2 root kmem 13184 Dec 26 15:23:20 1999 /usr/sbin/pstat > -r-sr-xr-x 5 root wheel 290448 Dec 26 15:24:16 1999 /usr/sbin/purgestat > -r-sr-xr-x 5 root wheel 290448 Dec 26 15:24:16 1999 /usr/sbin/sendmail > -r-sr-x--- 1 root network 9768 Dec 26 15:23:33 1999 /usr/sbin/sliplogin > -r-xr-sr-x 2 root kmem 13184 Dec 26 15:23:20 1999 /usr/sbin/swapinfo > -r-sr-xr-x 1 root wheel 13440 Dec 26 15:23:42 1999 /usr/sbin/timedc > -r-sr-xr-x 1 root wheel 11232 Dec 26 15:23:42 1999 /usr/sbin/traceroute > -r-xr-sr-x 1 root kmem 7036 Dec 26 15:23:43 1999 /usr/sbin/trpt Whats going on here? -- Stan Brown stanb@netcom.com 404-996-6955 Factory Automation Systems Atlanta Ga. -- Look, look, see Windows 95. Buy, lemmings, buy! Pay no attention to that cliff ahead... Henry Spencer (c) 1998 Stan Brown. Redistribution via the Microsoft Network is prohibited. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 27 5:36:41 1999 Delivered-To: freebsd-stable@freebsd.org Received: from ktpk.dp.ua (ktpk.dp.ua [195.24.130.245]) by hub.freebsd.org (Postfix) with ESMTP id A2F6014F07; Mon, 27 Dec 1999 05:34:57 -0800 (PST) (envelope-from os@ktpk.dp.ua) Received: from admin (admin.dnepr.com [192.168.0.4]) by ktpk.dp.ua (8.8.8/8.8.8) with SMTP id PAA10167; Mon, 27 Dec 1999 15:34:12 +0200 (EET) (envelope-from os@ktpk.dp.ua) Message-ID: <011801bf506f$16aa1360$0400a8c0@admin.dnepr.com> From: "Oleg Semyonov" To: , , Subject: patches for pppd-2.3.10-radius are here Date: Mon, 27 Dec 1999 15:34:12 +0200 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_0115_01BF507F.D3A5F280" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0115_01BF507F.D3A5F280 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit Hi all! I'am receiving many questions about pppd patch for RADIUS support. So, I decide to make it available via ftp. Briefly, it is patch to pppd-2.3.10 for using this version with FreeBSD system (based on currently bundled version) plus optional ability to use RADIUS authentication and accounting (based on standard FreeBSD RADIUS library by John Polstra). readme.txt . . . . . . . . . . . Dec 24 10:43 1k README.RADIUS. . . . . . . . . . Dec 24 10:29 10k libradius.tar.gz . . . . . . . . Dec 24 10:19 14k ppp-2.3.10-radius.diff.gz. . . . Dec 24 10:19 20k ppp-2.3.10.tar.gz. . . . . . . . Sep 17 06:16 766k Main ftp site is ftp://ftp.energodar.dp.ua/pub/FreeBSD/RADIUS/ Mirror for patches is at ftp://ftp.slashnet.org/users/shonson/ README.RADIUS is attached to the message. Try it out! OS (os@altavista.net), ICQ:31256452 ------=_NextPart_000_0115_01BF507F.D3A5F280 Content-Type: application/octet-stream; name="README.RADIUS" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="README.RADIUS" UkFESVVTIHN1cHBvcnQgZm9yIFBQUAkgICAgT2xlZyBTZW15b25vdiA8b3NAYWx0YXZpc3RhLm5l dD4JMyBOb3ZlbWJlciAxOTk5Cj09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT0KCjEuIElOVFJPRFVDVElP TgoKTG9uZyB0aW1lIHRoZSBwcHBkIGV4aXN0cyBpbiBGcmVlQlNEIGFzIHBhdGNoZWQgMi4zLjUg dmVyc2lvbiB3aGljaCBoYXMKc29tZSBidWdzIChlLmcuICIqIiBvbmx5IGluIGFsbG93ZWQgYWRk cmVzcyBsaXN0IHdpdGggbm8gRE5TIGF2YWlsYWJsZQpsZWFkcyB0byBsb25nIGRlbGF5cyBmb3Ig Z2V0aG9zdGJ5bmFtZSgiKiIpIHdoYXQgcHJldmVudHMgdGhlIGxvZ2luIHdpdGgKdGltZW91dCBo YW5ndXAsIGFuZCBzbyBvbi4pLgoKSnVzdCBub3cgSSd2ZSBhbG1vc3QgZG9uZSBteSB3b3JrIHdp dGggcHBwZC0yLjMuMTAgcGF0Y2hlcy4gVGhleSBhcmUgYmFzZWQKb24gcHBwZC0yLjMuNSBpbiBG cmVlQlNEIDIuMi44IGRpc3RyaWJ1dGlvbiB3aXRoIG1pbm9yIGNoYW5nZXMgZm9yIG5ldyBwcHBk CmZlYXR1cmVzIChvcHRpb25hbCBvcHRpb24gbGlzdCBpbiBzZWNyZXRzIGZpbGUsIGV0Yy4pLiAg RnV0dXJlbW9yZSwgSSd2ZQppbXBsZW1lbnRlZCB0aGUgUkFESVVTIHN1cHBvcnQgZm9yIGF1dGhl bnRpY2F0aW9uIGFuZCBhY2NvdW50aW5nLiBUaGUgc3VwcG9ydAppcyBiYXNlZCBvbiBzdGFuZGFy ZCBGcmVlQlNEIHJhZGl1cyBsaWJyYXJ5IGJ5IEpvaG4gUG9sc3RyYSwgaXQgbWF5IGJlCmNvbXBp bGVkLWluIGJ5IHJlcXVlc3QgKFVTRV9SQURJVVM9eWVzIGluIE1ha2VmaWxlIG9yIGFzIG1ha2Ug YXJndW1lbnQpIHdpdGgKb3B0aW9uYWwgYmFzZSBwcHBkIGNvbmZpZ3VyYXRpb24gcGF0aCAoZS5n IC9ldGMvcHBwIG9yIC9ldGMvcHBwLXJhZGl1cyksCmFuZCBpdCBpbmNsdWRlcyBzdXBwb3J0IGZv cjoKCi0gbmV3IFJBRElVUy1vcmllbnRlZCBwcHBkIG9wdGlvbnM6CiAgICAtIHJhZGl1cwkJCSAg ICAodXNlIFJBRElVUykKICAgIC0gcmFkaXVzLWNvbmYgL3BhdGgvcmFkaXVzLmNvbmYgKGNvbmZp Z3VyYXRpb24gZmlsZSBmb3IgUkFESVVTIGxpYnJhcnkpCiAgICAtIHJhZGl1cy1vbmx5CQkgICAg KGRvbid0IHRyeSB0byBhdXRoIHdpdGggc2VjcmV0cyBvciBsb2dpbgoJCQkJICAgICBtZXRob2Rz IGlmIHJhZGl1cyByZXR1cm5zIEFjY2Vzcy1SZWplY3QpCiAgICAtIHJhZGl1cy1ub2FjY3QJCSAg ICAoZG9uJ3Qgc2VuZCBhY2NvdW50aW5nIHJlcXVlc3RzKQogICAgLSByYWRpdXMtcG9ydAkJICAg IChkZXZpY2UgbmFtZSB0byBwb3J0IG51bWJlciB0cmFuc2xhdGlvbikKCi0gc3VwcG9ydCBmb3Ig UEFQIGF1dGhlbnRpY2F0aW9uIChubyBDSEFQIG9yIENBTExCQUNLIHN1cHBvcnQsIHNvcnJ5KTsK Ci0gbmV3IHNjcmlwdCBlbnZpcm9ubWVudCB2YXJpYWJsZXMgKENBTExFRF9TVEFUSU9OX0lELCBD QUxMSU5HX1NUQVRJT05fSUQsCiAgICBDT05ORUNUX0lORk8sIFBBQ0tFVFNfU0VOVCwgUEFDS0VU U19SQ1ZELCBhbmQgb3RoZXIgcmVjZWl2ZWQgZnJvbQogICAgUkFESVVTIHNlcnZlciAtIHNlZSBi ZWxvdyB0aGUgUFBQRC1TY3JpcHQtRW52IFZlbmRvci1TcGVjaWZpYyBhdHRyaWJ1dGUpOwoKLSBh YmlsaXR5IHRvIHNwZWNpZnkgYW55IG51bWJlciBvZiBhZGRpdGlvbmFsIHBwcGQgb3B0aW9ucyBp biBSQURJVVMKICAgIEFjY2Vzcy1BY2NlcHQgcGFja2V0IChzZWUgYmVsb3cgdGhlIFBQUEQtT3B0 aW9uIFZlbmRvci1TcGVjaWZpYyBhdHRyaWJ1dGUpOwoKLSBzdXBwb3J0ZWQgUkFESVVTIGF0dHJp YnV0ZXMgYXJlOgoKICAgIC0gaW4gQWNjZXNzLVJlcXVlc3Q6CiAgICAgICAgVXNlci1OYW1lCiAg ICAgICAgVXNlci1QYXNzd29yZAogICAgICAgIE5BUy1JUC1BZGRyZXNzIChnZXRob3N0bmFtZSgp KQogICAgICAgIE5BUy1JZGVudGlmaWVyIChnZXRob3N0YnluYW1lKCkpCiAgICAgICAgTkFTLVBv cnQgKGZyb20gZGV2aWNlIHRvIHBvcnQgdHJhbnNsYXRpb24pCiAgICAgICAgTkFTLVBvcnQtVHlw ZSAoQXN5bmMgb25seSkKICAgICAgICBTZXJ2aWNlLVR5cGUgKEZyYW1lZCBvbmx5KQogICAgICAg IEZyYW1lZC1Qcm90b2NvbCAoUFBQIG9ubHkpCiAgICAgICAgRnJhbWVkLUlQLUFkZHJlc3MKICAg ICAgICBGcmFtZWQtQ29tcHJlc3Npb24gKFZKLVRDUElQIG9ubHksIG5vIElQWCBzdXBwb3J0ZWQp CiAgICAgICAgQ2FsbGVkLVN0YXRpb24tSWQgKGZyb20gcHBwZCdzIGVudmlyb25tZW50KQogICAg ICAgIENhbGxpbmctU3RhdGlvbi1JZCAoZnJvbSBwcHBkJ3MgZW52aXJvbm1lbnQsIHBhc3NlZCBi eSBtZ2V0dHksIGUuZy4pCiAgICAgICAgQ29ubmVjdC1JbmZvIChmcm9tIHBwcGQncyBlbnZpcm9u bWVudCwgcGFzc2VkIGJ5IG1nZXR0eSwgZS5nLikKICAgICAgICBQUFBELVNjcmlwdC1FbnYgKHBw cGQgc2NyaXB0IGVudiB2YXJzLCB2ZW5kb3Itc3BlY2lmaWMgYXR0cmlidXRlKQoKICAgIC0gaW4g QWNjZXNzLUFjY2VwdC9SZWplY3QgYWxzbyByZWNvZ25pc2VkICh3aXRoIG1lbnRpb25lZCBhYm92 ZSk6CiAgICAgICAgRnJhbWVkLUlQLU5ldG1hc2sKICAgICAgICBGcmFtZWQtUm91dGluZyAobm90 IHVzZWQgeWV0KQogICAgICAgIEZpbHRlci1JZCAobm90IHVzZWQgeWV0KQogICAgICAgIEZyYW1l ZC1NVFUKICAgICAgICBSZXBseS1NZXNzYWdlIChmaXJzdCBtZXNzYWdlIGlzIHVzZWQgb25seSkK ICAgICAgICBGcmFtZWQtUm91dGUgKG5vdCB1c2VkIHlldCkKICAgICAgICBDbGFzcyAocGFzc2Vk IHRocm91Z2ggaW4gYWNjb3VudGluZyByZXF1ZXN0cykKICAgICAgICBTZXNzaW9uLVRpbWVvdXQK ICAgICAgICBJZGxlLVRpbWVvdXQKICAgICAgICBQUFBELU9wdGlvbiAoYWRkaXRpb25hbCBwcHBk IG9wdGlvbnMsIHZlbmRvci1zcGVjaWZpYyBhdHRyaWJ1dGUpCiAgICAgICAgUFBQRC1TY3JpcHQt RW52IChhZGRpdGlvbmFsIHNjcmlwdCBlbnYgdmFycywgdmVuZG9yLXNwZWNpZmljCgkgICAgYXR0 cmlidXRlKQoKICAgIC0gaW4gQWNjb3VudGluZy1SZXF1ZXN0IFNUQVJUIHBhY2tldCBhbHNvIHBh c3NlZCAod2l0aCBtZW50aW9uZWQgYWJvdmUpOgogICAgICAgIEFjY3QtU3RhdHVzLVR5cGUgKFN0 YXJ0LCBTdG9wKQogICAgICAgIEFjY3QtU2Vzc2lvbi1JZCAoMTYgY2hhcnMgQVNDSUkgc3RyaW5n KQogICAgICAgIEFjY3QtQXV0aGVudGljIChSQURJVVMgb25seSkKCiAgICAtIGluIEFjY291bnRp bmctUmVxdWVzdCBTVE9QIHBhY2tldCBhbHNvIHBhc3NlZCAod2l0aCBtZW50aW9uZWQgYWJvdmUp OgogICAgICAgIEFjY3QtSW5wdXQtT2N0ZXRzCiAgICAgICAgQWNjdC1PdXRwdXQtT2N0ZXRzCiAg ICAgICAgQWNjdC1JbnB1dC1QYWNrZXRzCiAgICAgICAgQWNjdC1PdXRwdXQtUGFja2V0cwogICAg ICAgIEFjY3QtU2Vzc2lvbi1UaW1lCiAgICAgICAgQWNjdC1UZXJtaW5hdGUtQ2F1c2UgKG5vdCBz byBnb29kIGJ1dCBzb21ldGhpbmcgdXNlZnVsKQoKLSBubyBjaGFuZ2VzIG1hZGUgaW4gbWFudWFs IHBhZ2VzIGZvciBwcHBkLCBzb3JyeSAoYW55IHZvbHVudGVlcnM/KS4KCk1vc3Qgb2YgUkFESVVT IGF0dHJpYnV0ZXMgYXJlIHBhc3NlZCBiYWNrIGluIGFjY291bnRpbmcgcmVxdWVzdHMgKGUuZy4g YWxsCnNjcmlwdCBlbnZpcm9ubWVudCB2YXJpYWJsZXMgYW5kIFJBRElVUy1zcGVjaWZpZWQgYWRk aXRpb25hbCBwcHBkIG9wdGlvbnMpLgoKUkFESVVTIHN1cHBvcnQgaXNuJ3QgZG9uZSBhcyBsb2Fk YWJsZSBwcHBkIHBsdWdpbiBhcyBpbnRyb2R1Y2VkIGluIDIuMy4xMC4KRmlyc3QgcmVhc29uIHdh cyB0aGUgcHBwZCBtdXN0IHdvcmsgKGZvciBtZSkgb24gMi4yLjggc3lzdGVtIHdoaWNoIGRvZXMK bm90IHN1cHBvcnQgc29tZSBmZWF0dXJlcyByZXF1aXJlZCBmb3IgZHluYW1pYyBsaW5raW5nICgt RSBzd2l0Y2ggZm9yIGxkLApmb3IgZXhhbXBsZSkuIFNlY29uZGx5LCB0aGVyZSBpcyBubyBzb21l IGhvb2tzIGFuZCBnbG9iYWwgdmFyaWFibGVzIHJlcXVpcmVkCmZvciBpbXBsZW1lbnRpbmcgYWxs IHRoZSBmZWF0dXJlcyBsaXN0ZWQuCgpUaGUgY29kZSBhdCB0aW1lIG9mIHdyaXRpbmcgdGhpcyBS RUFETUUgaXMgc2xpZ2h0bHkgdGVzdGVkIHdpdGggU3RlZWwtQmVsdGVkClJBRElVUyBmb3IgV2lu TlQgYW5kIHdpdGggQ2lzdHJvbiByYWRpdXNkLTEuNi4xIGFuZCBzZWVtcyB0byB3b3JrIGZpbmUg Zm9yIG1lLgpBbnkgZmVlZGJhY2sgaXMgYXBwcmVjaWF0ZWQuCgoKMi4gSU5TVEFMTEFUSU9OIEFO RCBDT05GSUdVUkFUSU9OCgpJZiB5b3Ugd2FudCB0byBjb21waWxlIGl0IGFzIHBwcGQtMi4zLjEw IHdpdGhvdXQgUkFESVVTIHN1cHBvcnQgdGhlbgp1c2UgY29uZmlndXJlL21ha2UvbWFrZSBpbnN0 YWxsIGFzIHVzdWFsLiBEb24ndCBmb3JnZXQgdG8gYmFja3VwIEZyZWVCU0QncwpwcHBkIG1hbnVh bHMgYmVjYXVzZSBzb21lIG9mIEZyZWVCU0Qtc3BlY2lmaWMgZmVhdHVyZXMgYXJlbid0IGRlc2Ny aWJlZCBpbgpvcmlnaW5hbCBwcHBkIGRvY3VtZW50YXRpb24gd2hpY2ggaXNuJ3QgcGF0Y2hlZCBi eSBtZSAoc29ycnkgZm9yIG15IEVuZ2xpc2gsCmJ1dCBJIGRvbid0IHdhbm5hIHRvIHdyaXRlIG1h bnMgd2l0aG91dCBnb29kIGxhbmd1YWdlIHByYWN0aWNlIDopCgpBbGwgdGhlIGZlYXR1cmVzIGRl c2NyaWJlZCBpbiBGcmVlQlNEIHBwcGQgbWFuIHBhZ2UgYXJlIHByZXNlbnQuIEFkZGl0aW9uYWwK c2NyaXB0IHZhcmlhYmxlcyBDQUxMRURfU1RBVElPTl9JRCwgQ0FMTElOR19TVEFUSU9OX0lEIGFu ZCBDT05ORUNUX0lORk8Kd2lsbCBiZSBzZWFyY2hlZCBpbiBwcHBkIGVudmlyb25tZW50IGFuZCwg aWYgZm91bmQsIHdpbGwgYmUgcGxhY2VkIGluCmNoaWxkIHNjcmlwdHMgZW52aXJvbm1lbnQgdW50 b3VjaGVkLiBUd28gbGF0ZXN0IHZhcmlhYmxlcyBtYXkgYmUgZm91bmQsCmZvciBleGFtcGxlLCBp biBtZ2V0dHkncyBlbnZpcm9ubWVudCBhcyBDQUxMRVJfSUQgYW5kIENPTk5FQ1QsIHJlc3BlY3Rp dmVseS4KVmFyaWFibGVzIFBBQ0tFVFNfU0VOVCwgUEFDS0VUU19SQ1ZEIHdpbGwgYmUgcGFzc2Vk IHRvICotZG93biBzY3JpcHRzIG9uCnNlc3Npb24gdGVybWluYXRpb24gYW5kIG1heSBiZSB1c2Vk IGZvciBleHRlcm5hbCBhY2NvdW50aW5nLgoKRm9yIFJBRElVUyBzdXBwb3J0IGlzIHJlcXVpcmVk IHRvIGluc3RhbGwgbGF0ZXN0IEZyZWVCU0QgUkFESVVTIGNsaWVudApsaWJyYXJ5LCB0aGUgbGli cmFkaXVzLCB3aGljaCBzdXBwb3J0cyB0aGUgUkFESVVTIGFjY291bnRpbmcuIEN1cnJlbnRseQp0 aGUgbGlicmFyeSBpcyBpbmNsdWRlZCBpbiBGcmVlQlNEIDQuMC1DVVJSRU5ULCBidXQgdGhlcmUg YXJlIGNoYW5jZXMgdGhlCnVwZGF0ZWQgZm9yIGFjY291bnRpbmcgbGlicmFyeSB3aWxsIGJlIHBs YWNlZCBpbiAzLjMtU1RBQkxFIHNvb24uCgpCZWZvcmUgY29tcGlsaW5nIHNlZSB0aGUgcHBwZC9N YWtlZmlsZS5ic2QgZm9yIG5ldyBSQURJVVMtcmVsYXRlZCBvcHRpb25zLgpSQURJVVMgc3VwcG9y dCB3YXMgdGVzdGVkIG9uIEZyZWVCU0Qgc3lzdGVtIG9ubHkuIE90aGVyIHN5c3RlbSBNYWtlZmls ZXMgd2VyZQpub3QgdG91Y2hlZC4gQWRqdXN0IHNldHRpbmdzIGFzIHlvdSB3YW50IG9yIGRvbid0 IGZvcmdldCB0byBzcGVjaWZ5IHRoZXNlIG9uCm1ha2UgY29tbWFuZCBsaW5lLiBBZnRlciBjb21w aWxpbmcgdXNlIG1ha2UgaW5zdGFsbCBhcyB1c3VhbC4KClNlZSByYWRpdXMuc2FtcGxlcy9vcHRp b25zLnJhZGl1cyBzYW1wbGUgY29uZmlndXJhdGlvbiBmaWxlIGZvciBuZXcgb3B0aW9ucy4KCnJh ZGl1cwkJCVVzZSBSQURJVVMuIFdpdGhvdXQgdGhlIG9wdGlvbiBwcHBkIGRvZXNuJ3Qgc3VwcG9y dHMKCQkJUkFESVVTIGF0IGFsbC4KCnJhZGl1cy1jb25mIC9wYXRoL2ZpbGUJVXNlIC9wYXRoL2Zp bGUgYXMgUkFESVVTIGxpYnJhcnkgY29uZmlndXJhdGlvbiBmaWxlLgoJCQlXaXRob3V0IHRoZSBv cHRpb24gZGVmYXVsdCBsaWJyYWRpdXMgY29uZmlndXJhdGlvbgoJCQlmaWxlIHdpbGwgYmUgdXNl ZCAoL2V0Yy9yYWRpdXMuY29uZiBhcyBkb2N1bWVudGVkKS4KCnJhZGl1cy1vbmx5CQlJZiB0aGlz IG9wdGlvbiBpcyBzcGVjaWZpZWQsIHBwcGQgd2lsbCByZWplY3QgYW55CgkJCXVzZXIgaWYgUkFE SVVTIHJldHVybnMgQWNjZXNzLVJlamVjdC4gQnkgZGVmYXVsdAoJCQlwcHBkIHdpbGwgdHJ5IHRv IHVzZSBzZWNyZXRzIGZpbGUgb3IgVU5JWCBwYXNzd29yZAoJCQlkYXRhYmFzZSAob3IgUEFNLCBp ZiBjb21waWxlZCBpbikgaW4gY2FzZSBvZiBSQURJVVMKCQkJZmFpbHVyZS4KCnJhZGl1cy1ub2Fj Y3QJCUJ5IGRlZmF1bHQgcHBwZCB3aWxsIHNlbmQgdGhlIGFjY291bnRpbmcgcmVxdWVzdHMKCQkJ YWZ0ZXIgQWNjZXNzLUFjY2VwdCByZWNlaXZlZCBhbmQgb24gY29ubmVjdGlvbgoJCQl0ZXJtaW5h dGlvbi4gRmFpbHVyZSB0byByZWNlaXZlIHRoZSBBY2NvdW50aW5nLVJlc3BvbnNlCgkJCWZvciBT VEFSVCBwYWNrZXQgbGVhZHMgdG8gcmVqZWN0cyB0aGUgdXNlciBhcyBpbiBjYXNlCgkJCW9mIEFj Y2Vzcy1SZWplY3Qgd2l0aCBwb3NzaWJsZSBmYWxsYmFjayB0byBvdGhlcgoJCQlhdXRoZW50aWNh dGlvbiBtZXRob2RzIChzZWUgYWJvdmUpLiBXaXRoIHRoaXMgb3B0aW9uCgkJCW5vIGFjY291bnRp bmcgcGFja2V0cyB3aWxsIGJlIHNlbnQuCgpyYWRpdXMtcG9ydCBkZXY9cG9ydAlUaGlzIG9wdGlv biBkZWZpbmVzIGRldmljZSBuYW1lIHRvIHBvcnQgbnVtYmVyCgkJCXRyYW5zbGF0aW9uLiBkZXYg aXMgZGV2aWNlIG5hbWUgKGUuZy4gdHR5ZDUgb3IKCQkJL2Rldi90dHlkNSAtIHRoZSAvZGV2LyBw cmVmaXggaXMgc3RyaXBwZWQgaW50ZXJuYWxseSkuCgkJCXBvcnQgaXMgcG9ydCBudW1iZXIgZm9y IG5hbWVkIGRldmljZS4gUmVzZXJ2ZWQgd29yZAoJCQknZGVmYXVsdCcgZm9yIGRldmljZSBuYW1l IGlzIHVzZWQgYXMgZGVmYXVsdCBwb3J0IG51bWJlcgoJCQlmb3IgdW5zcGVjaWZpZWQgZGV2aWNl cy4gRGVmYXVsdCB2YWx1ZSBmb3IgZGVmYXVsdAoJCQlkZXZpY2UgaXMgMC4gV2hlbiByYWRpdXMt cG9ydCBvcHRpb24gaXNuJ3QgdXNlZCBhdAoJCQlhbGwgcHBwZCB3aWxsIHRyeSB0byBtYWtlIGRp ZmZlcmVudCBwb3J0IG51bWJlcnMKCQkJZm9yIGRpZmZlcmVudCBkZXZpY2VzIGJ1dCBkaXJlY3Qg dHJhbnNsYXRpb24gaXMKCQkJcHJlZmVycmVkLgoKZGVidWcJCQlXaXRoIHRoaXMgb3B0aW9uIHRo ZXJlIGFyZSBsb3RzIG9mIGRlYnVnZ2luZwoJCQlvdXRwdXQgaW4gbG9nIGZpbGUuIFVzZSBpdCBm b3IgbG9va2luZyBpbnRvIFJBRElVUwoJCQlyZXF1ZXN0cy9yZXNwb25zZXMgYW5kIHBwcGQgb3B0 aW9ucyBwYXNzZWQgYnkKCQkJUkFESVVTLiBWZXJ5IHVzZWZ1bCBmb3IgaW5pdGlhbCBzZXR0aW5n cy4KCkFmdGVyIHN1Y2Nlc3NmdWwgaW5zdGFsbGF0aW9uIG9mIGJpbmFyaWVzIGFuZCB1cGRhdGlu ZyB0aGUgb3B0aW9ucyBmaWxlCnRha2UgYSBsb29rIGludG8gcmFkaXVzLnNhbXBsZXMvZGljdGlv bmFyeS5wcHBkIGZpbGUuIFRoaXMgb25lIGRlZmluZXMKdHdvIGFkZGl0aW9uYWwgVmVuZG9yLVNw ZWNpZmljIFJBRElVUyBhdHRyaWJ1dGUgZm9yIFJBRElVUyBzZXJ2ZXIuIFlvdQptdXN0IHVwZGF0 ZSB5b3VyIFJBRElVUyBzZXJ2ZXIgY29uZmlndXJhdGlvbiBpbiBvcmRlciB0byBzdXBwb3J0IHRo ZXNlCmF0dHJpYnV0ZXMuIFNlZSB5b3VyIFJBRElVUyBzZXJ2ZXIgbWFudWFscyBmb3IgZGV0YWls cy4KClBQUEQtT3B0aW9uIG1heSBiZSB1c2VkIGZvciBzcGVjaWZ5aW5nIGFkZGl0aW9uYWwgcHBw ZCBvcHRpb25zIGluIFJBRElVUwpyZXBseSAodXN1YWxseSBpbiBBY2Nlc3MtQWNjZXB0IHBhY2tl dCksIGUuZy4gZm9yIGxvY2FsIElQIGFkZHJlc3MsCmNjcCBjb250cm9sIGFuZCBtb3JlLiBBbGwg b3B0aW9ucyBwYXNzZWQgd2lsbCBiZSBwcm9jZXNzZWQgYWZ0ZXIgYW55Cm90aGVyIG9wdGlvbnMg YW5kIG1heSBvdmVycmlkZSBpdC4gU3Vic2VxdWVudGx5LCBhbGwgUFBQRC1PcHRpb24gc3RyaW5n cwp3aWxsIGJlIHBhc3NlZCBiYWNrIGluIFJBRElVUyBhY2NvdW50aW5nIHJlcXVlc3RzLgoKUFBQ LVNjcmlwdC1FbnYgbWF5IGJlIHVzZWQgZm9yIHNwZWNpZnlpbmcgYW55IGV4dGVybmFsIHNjcmlw dCBlbnZpcm9ubWVudAp2YXJpYWJsZXMgb3IgZm9yIGNoYW5naW5nIHZhbHVlIG9mIGFscmVhZHkg ZGVmaW5lZCBvbmUuIEFsbCBzY3JpcHQgdmFyaWFibGVzCmFyZSBhbHNvIHBhc3NlZCB0byBSQURJ VVMgaW4gYWNjb3VudGluZyByZXF1ZXN0cyBhcyBQUFAtU2NyaXB0LUVudiBhdHRyaWJ1dGVzLgoK Tm90ZSB0aGUgcGFyc2luZyBvZiB0aGVzZSBhdHRyaWJ1dGVzIGlzbid0IGRvbmUgdG9vIHdlbGw6 IG9uZSBvbmx5IHN0cmluZyBpbgpvbmUgVmVuZG9yLVNwZWNpZmljIGF0dHJpYnV0ZSBtdXN0IGV4 aXN0LiBJZiB5b3Ugd2FudCBmb3IgbW9yZSB5b3UgYXJlIGZvcmNlZAp0byBwYXNzIHNvbWUgbnVt YmVyIG9mIFZlbmRvci1TcGVjaWZpYyBhdHRyaWJ1dGVzIHdpdGggb25lIHN0cmluZyBwZXIKYXR0 cmlidXRlLgoKQW5kIG5vdyBpcyB0aW1lIHRvIGNoZWNrIHlvdXIgL2V0Yy9yYWRpdXMuY29uZiAo Y2hlY2sgZm9yIG5ldyBzeW50YXggd2l0aAphY2NvdW50aW5nIHN1cHBvcnQpIGFuZCB0byBjb25m aWd1cmUgeW91ciBSQURJVVMgc2VydmVyIGZvciBwcHBkLiBVc2UKZGVidWcgb3B0aW9uIGZvciBm aXJzdCB0aW1lIC0gYWxsIFJBRElVUy1yZWxhdGVkIGluZm8gaW4gZGV0YWlscyB3aWxsCmJlIGxv Z2dlZCBhbmQgeW91IHdpbGwgc2VlIHdoYXQgaGFwcGVucy4KCgozLiBBQ0tOT1dMRURHRU1FTlRT CgpQYXVsIE1hY2tlcnJhcyA8UGF1bC5NYWNrZXJyYXNAY3MuYW51LmVkdS5hdT4gaXMgdGhlIGF1 dGhvciBvZiBwcHBkLTIuMy4xMC4KcGV0ZXJAZnJlZWJzZC5vcmcgaXMgdGhlIG1haW50YWluZXIg b2YgcHBwZCB2ZXJzaW9uIHVzZWQgaW4gRnJlZUJTRC4KSm9obiBQb2xzdHJhIDxqZHBAcG9sc3Ry YS5jb20+IGlzIHRoZSBhdXRob3Igb2YgRnJlZUJTRCBSQURJVVMgbGlicmFyeS4KT2xlZyBTZW15 b25vdiA8b3NAYWx0YXZpc3RhLm5ldD4gaXMgdGhlIGF1dGhvciBvZiBSQURJVVMgc3VwcG9ydCBm b3IgcHBwZC4KClRoaXMgaXMgdGhlIGFscGhhIHRlc3QgdmVyc2lvbiBvZiBwcHBkLTIuMy4xMC1y YWRpdXMgZm9yIEZyZWVCU0QuIEl0IHdhcwpkb25lIGZvciBteSBvd24gaW50ZXJuYWwgdXNlIGFu ZCBzZWVtcyB0byB3b3JrIGZvciBtZS4gSXQgbWF5IGJlIHVzZWZ1bApmb3Igb3RoZXJzIHNvIEkg d2FudCB0byByZWxlYXNlIGl0IHRvIHB1YmxpYy4gSWYgeW91IGhhdmUgYSBzdWdnZXNzdGlvbnMs CmJ1ZyByZXBvcnRzIG9yIGFueSBvdGhlciBpbmZvIC0gZmVlbCBmcmVlIHRvIGNvbnRhY3QgbWUu IFRoYW5rIHlvdSBmb3IKcmVhZGluZyB0aGlzIFJFQURNRSA7LSkKClJlZ2FyZHMsCiAgICBPbGVn IFNlbXlvbm92IDxvc0BhbHRhdmlzdGEubmV0PgogICAgMDMtTm92LTE5OTkuCgo= ------=_NextPart_000_0115_01BF507F.D3A5F280-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 27 5:45:28 1999 Delivered-To: freebsd-stable@freebsd.org Received: from typhoon.mail.pipex.net (typhoon.mail.pipex.net [158.43.128.27]) by hub.freebsd.org (Postfix) with SMTP id 89FCA1507B for ; Mon, 27 Dec 1999 05:45:22 -0800 (PST) (envelope-from mark@dogma.freebsd-uk.eu.org) Received: (qmail 12584 invoked from network); 27 Dec 1999 13:45:19 -0000 Received: from usercb09.uk.uudial.com (HELO marder-1.) (62.188.150.176) by smtp.dial.pipex.com with SMTP; 27 Dec 1999 13:45:19 -0000 Received: (from mark@localhost) by marder-1. (8.9.3/8.9.3) id NAA86270; Mon, 27 Dec 1999 13:45:29 GMT (envelope-from mark) Date: Mon, 27 Dec 1999 13:45:29 +0000 From: Mark Ovens To: Stan Brown Cc: FreeBSD Stable List Subject: Re: Huge differences in suid programs ? Message-ID: <19991227134529.D1290@marder-1> References: <199912271336.FAA14584@netcom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <199912271336.FAA14584@netcom.com> Organization: Total lack of Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Dec 27, 1999 at 08:36:11AM -0500, Stan Brown wrote: > I cvsuped 3 machines and did a make worlds on the yesterday. I got HUGE > differences on the suid files in the security report this morning: > [snipped report] > Whats going on here? > The timestamp has changed on the files because make world replaced them so they're different. > -- > Stan Brown stanb@netcom.com 404-996-6955 > Factory Automation Systems > Atlanta Ga. > -- > Look, look, see Windows 95. Buy, lemmings, buy! > Pay no attention to that cliff ahead... Henry Spencer > (c) 1998 Stan Brown. Redistribution via the Microsoft Network is prohibited. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- "there's a long-standing bug relating to the x86 architecture that allows you to install Windows too" -Matthew D. Fuller ________________________________________________________________ FreeBSD - The Power To Serve http://www.freebsd.org My Webpage http://ukug.uk.freebsd.org/~mark/ mailto:mark@ukug.uk.freebsd.org http://www.radan.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 27 5:49:38 1999 Delivered-To: freebsd-stable@freebsd.org Received: from sand2.sentex.ca (sand2.sentex.ca [209.167.248.3]) by hub.freebsd.org (Postfix) with ESMTP id 2F9B5151DB for ; Mon, 27 Dec 1999 05:49:32 -0800 (PST) (envelope-from mike@sentex.net) Received: from gravel (ospf-mdt.sentex.net [205.211.164.81]) by sand2.sentex.ca (8.9.3/8.9.3) with SMTP id IAA09234; Mon, 27 Dec 1999 08:49:17 -0500 (EST) (envelope-from mike@sentex.net) Message-Id: <4.1.19991227084847.03d6dc50@granite.sentex.ca> X-Sender: mdtancsa@granite.sentex.ca X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Mon, 27 Dec 1999 08:49:15 -0500 To: Stan Brown , freebsd-stable@FreeBSD.ORG (FreeBSD Stable List) From: Mike Tancsa Subject: Re: Huge differences in suid programs ? In-Reply-To: <199912271336.FAA14584@netcom.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 08:36 AM 12/27/99 , Stan Brown wrote: > I cvsuped 3 machines and did a make worlds on the yesterday. I got HUGE > differences on the suid files in the security report this morning: Thats because the files have changed when you installed the new binaries. Its normal. ---Mike ********************************************************************** Mike Tancsa * mike@sentex.net Sentex Communications Corp, * http://www.sentex.net/mike Cambridge, Ontario * 519 651 3400 Canada * To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 27 5:52:10 1999 Delivered-To: freebsd-stable@freebsd.org Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (Postfix) with ESMTP id 4AC3D152DE for ; Mon, 27 Dec 1999 05:52:06 -0800 (PST) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.8.8/8.8.8) id OAA21293 for freebsd-stable@FreeBSD.ORG; Mon, 27 Dec 1999 14:52:05 +0100 (CET) (envelope-from olli) Date: Mon, 27 Dec 1999 14:52:05 +0100 (CET) From: Oliver Fromme Message-Id: <199912271352.OAA21293@dorifer.heim3.tu-clausthal.de> To: freebsd-stable@FreeBSD.ORG Subject: Re: Huge differences in suid programs ? Organization: Administration TU Clausthal Reply-To: freebsd-stable@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: TIN [version 1.2 RZTUC(3) PL2] Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In list.freebsd-stable you wrote (27 Dec 1999 14:38:00 +0100): > I cvsuped 3 machines and did a make worlds on the yesterday. I got HUGE > differences on the suid files in the security report this morning: > [...] > Whats going on here? Well, a "make world" will also replace all s{u,g}id binaries in {/usr,}/{s,}bin, i.e. the time stamps and (possibly) the sizes of the files change, so the daily security script will report about all of them. That's normal. If you're paranoid, you should run /etc/security right after a "make world" (or "make installworld") to update the system's information about s{u,g}id binaries. If the daily security script still reports changes the next time, then you have a _real_ reason to worry. ;-) (Maybe this should be added to the "make world" chapter in the handbook...) Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 27 5:58:51 1999 Delivered-To: freebsd-stable@freebsd.org Received: from zgia.zp.ua (Eagle.ZGIA.zp.ua [194.183.182.2]) by hub.freebsd.org (Postfix) with ESMTP id 08D9114E78 for ; Mon, 27 Dec 1999 05:54:56 -0800 (PST) (envelope-from laa@zgia.zp.ua) Received: from localhost (laa@localhost) by zgia.zp.ua (8.9.3/8.9.3) with ESMTP id PAA84114; Mon, 27 Dec 1999 15:48:40 +0200 (EET) Date: Mon, 27 Dec 1999 15:48:40 +0200 (EET) From: Alexandr Listopad To: Stan Brown Cc: FreeBSD Stable List Subject: Re: Huge differences in suid programs ? In-Reply-To: <199912271336.FAA14584@netcom.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 don't worry. all right. during releases there is some changes in sources. this way - many binares will be changed (size). Good Luck! stanb> I cvsuped 3 machines and did a make worlds on the yesterday. I got HUGE stanb> differences on the suid files in the security report this morning: stanb> stanb> stanb> stanb>polar.fas.com setuid diffs: stanb>1,12c1,12 stanb>< -r-xr-sr-x 1 root operator 51196 Dec 5 22:22:13 1999 /bin/df stanb>< -r-xr-sr-x 1 root kmem 189664 Dec 5 22:22:26 1999 /bin/ps stanb>< -r-sr-xr-x 1 root wheel 208408 Dec 5 22:22:29 1999 /bin/rcp stanb>< -r-xr-sr-x 1 root kmem 100148 Dec 5 22:33:20 1999 /sbin/ccdconfig stanb>< -r-xr-sr-x 1 root kmem 103696 Dec 5 22:33:27 1999 /sbin/dmesg stanb>< -r-xr-sr-x 2 root tty 221736 Dec 5 22:33:28 1999 /sbin/dump stanb>< -r-sr-xr-x 1 root wheel 145528 Dec 5 22:34:11 1999 /sbin/ping stanb>< -r-xr-sr-x 2 root tty 221736 Dec 5 22:33:28 1999 /sbin/rdump stanb>< -r-xr-sr-x 2 root tty 244920 Dec 5 22:34:16 1999 /sbin/restore stanb>< -r-sr-xr-x 1 root wheel 153760 Dec 5 22:34:18 1999 /sbin/route stanb>< -r-xr-sr-x 2 root tty 244920 Dec 5 22:34:16 1999 /sbin/rrestore stanb>< -r-sr-x--- 1 root operator 151712 Dec 5 22:34:22 1999 /sbin/shutdown stanb>--- stanb>> -r-xr-sr-x 1 root operator 51204 Dec 26 15:01:26 1999 /bin/df stanb>> -r-xr-sr-x 1 root kmem 190016 Dec 26 15:01:40 1999 /bin/ps stanb>> -r-sr-xr-x 1 root wheel 208408 Dec 26 15:01:43 1999 /bin/rcp stanb>> -r-xr-sr-x 1 root kmem 100156 Dec 26 15:12:33 1999 /sbin/ccdconfig stanb>> -r-xr-sr-x 1 root kmem 103872 Dec 26 15:12:39 1999 /sbin/dmesg stanb>> -r-xr-sr-x 2 root tty 221768 Dec 26 15:12:40 1999 /sbin/dump stanb>> -r-sr-xr-x 1 root wheel 145544 Dec 26 15:13:24 1999 /sbin/ping stanb>> -r-xr-sr-x 2 root tty 221768 Dec 26 15:12:40 1999 /sbin/rdump stanb>> -r-xr-sr-x 2 root tty 244920 Dec 26 15:13:28 1999 /sbin/restore stanb>> -r-sr-xr-x 1 root wheel 153760 Dec 26 15:13:30 1999 /sbin/route stanb>> -r-xr-sr-x 2 root tty 244920 Dec 26 15:13:28 1999 /sbin/rrestore stanb>> -r-sr-x--- 1 root operator 151712 Dec 26 15:13:36 1999 /sbin/shutdown stanb>23,50c23,50 stanb>< -r-sr-xr-x 4 root wheel 17448 Dec 5 22:39:01 1999 /usr/bin/at stanb>< -r-sr-xr-x 4 root wheel 17448 Dec 5 22:39:01 1999 /usr/bin/atq stanb>< -r-sr-xr-x 4 root wheel 17448 Dec 5 22:39:01 1999 /usr/bin/atrm stanb>< -r-sr-xr-x 4 root wheel 17448 Dec 5 22:39:01 1999 /usr/bin/batch stanb>< -r-sr-xr-x 6 root wheel 28932 Dec 5 22:39:15 1999 /usr/bin/chfn stanb>< -r-sr-xr-x 6 root wheel 28932 Dec 5 22:39:15 1999 /usr/bin/chpass stanb>< -r-sr-xr-x 6 root wheel 28932 Dec 5 22:39:15 1999 /usr/bin/chsh stanb>< -r-sr-xr-x 1 root wheel 21028 Dec 5 22:42:54 1999 /usr/bin/crontab stanb>< -r-sr-sr-x 1 uucp dialer 110760 Dec 5 22:24:40 1999 /usr/bin/cu stanb>< -r-xr-sr-x 1 root kmem 10160 Dec 5 22:39:53 1999 /usr/bin/fstat stanb>< -r-sr-xr-x 5 root wheel 290448 Dec 5 22:44:46 1999 /usr/bin/hoststat stanb>< -r-xr-sr-x 1 root kmem 8728 Dec 5 22:40:07 1999 /usr/bin/ipcs stanb>< -r-sr-xr-x 1 root wheel 514 Dec 5 22:40:11 1999 /usr/bin/keyinfo stanb>< -r-sr-xr-x 1 root wheel 6556 Dec 5 22:40:12 1999 /usr/bin/keyinit stanb>< -r-sr-xr-x 1 root wheel 5656 Dec 5 22:40:26 1999 /usr/bin/lock stanb>< -r-sr-xr-x 1 root wheel 17624 Dec 5 22:40:29 1999 /usr/bin/login stanb>< -r-sr-sr-x 1 root daemon 18064 Dec 5 22:43:18 1999 /usr/bin/lpq stanb>< -r-sr-sr-x 1 root daemon 20864 Dec 5 22:43:19 1999 /usr/bin/lpr stanb>< -r-sr-sr-x 1 root daemon 17624 Dec 5 22:43:20 1999 /usr/bin/lprm stanb>< -r-sr-xr-x 5 root wheel 290448 Dec 5 22:44:46 1999 /usr/bin/mailq stanb>< -r-sr-xr-x 1 man wheel 23948 Dec 5 22:27:28 1999 /usr/bin/man stanb>< -r-xr-sr-x 1 root kmem 44536 Dec 5 22:40:52 1999 /usr/bin/netstat stanb>< -r-sr-xr-x 5 root wheel 290448 Dec 5 22:44:46 1999 /usr/bin/newaliases stanb>< -r-xr-sr-x 1 root kmem 7380 Dec 5 22:40:54 1999 /usr/bin/nfsstat stanb>< -r-sr-xr-x 2 root wheel 23984 Dec 5 22:41:02 1999 /usr/bin/passwd stanb>< -r-sr-xr-x 1 root wheel 10036 Dec 5 22:41:06 1999 /usr/bin/quota stanb>< -r-sr-xr-x 1 root wheel 8888 Dec 5 22:41:08 1999 /usr/bin/rlogin stanb>< -r-sr-xr-x 1 root wheel 6768 Dec 5 22:41:11 1999 /usr/bin/rsh stanb>--- stanb>> -r-sr-xr-x 4 root wheel 17448 Dec 26 15:18:22 1999 /usr/bin/at stanb>> -r-sr-xr-x 4 root wheel 17448 Dec 26 15:18:22 1999 /usr/bin/atq stanb>> -r-sr-xr-x 4 root wheel 17448 Dec 26 15:18:22 1999 /usr/bin/atrm stanb>> -r-sr-xr-x 4 root wheel 17448 Dec 26 15:18:22 1999 /usr/bin/batch stanb>> -r-sr-xr-x 6 root wheel 28932 Dec 26 15:18:36 1999 /usr/bin/chfn stanb>> -r-sr-xr-x 6 root wheel 28932 Dec 26 15:18:36 1999 /usr/bin/chpass stanb>> -r-sr-xr-x 6 root wheel 28932 Dec 26 15:18:36 1999 /usr/bin/chsh stanb>> -r-sr-xr-x 1 root wheel 21028 Dec 26 15:22:19 1999 /usr/bin/crontab stanb>> -r-sr-sr-x 1 uucp dialer 110760 Dec 26 15:03:55 1999 /usr/bin/cu stanb>> -r-xr-sr-x 1 root kmem 10160 Dec 26 15:19:12 1999 /usr/bin/fstat stanb>> -r-sr-xr-x 5 root wheel 290448 Dec 26 15:24:16 1999 /usr/bin/hoststat stanb>> -r-xr-sr-x 1 root kmem 8728 Dec 26 15:19:26 1999 /usr/bin/ipcs stanb>> -r-sr-xr-x 1 root wheel 514 Dec 26 15:19:31 1999 /usr/bin/keyinfo stanb>> -r-sr-xr-x 1 root wheel 6556 Dec 26 15:19:31 1999 /usr/bin/keyinit stanb>> -r-sr-xr-x 1 root wheel 5656 Dec 26 15:19:46 1999 /usr/bin/lock stanb>> -r-sr-xr-x 1 root wheel 17624 Dec 26 15:19:48 1999 /usr/bin/login stanb>> -r-sr-sr-x 1 root daemon 18064 Dec 26 15:22:44 1999 /usr/bin/lpq stanb>> -r-sr-sr-x 1 root daemon 20864 Dec 26 15:22:45 1999 /usr/bin/lpr stanb>> -r-sr-sr-x 1 root daemon 17624 Dec 26 15:22:46 1999 /usr/bin/lprm stanb>> -r-sr-xr-x 5 root wheel 290448 Dec 26 15:24:16 1999 /usr/bin/mailq stanb>> -r-sr-xr-x 1 man wheel 23948 Dec 26 15:06:43 1999 /usr/bin/man stanb>> -r-xr-sr-x 1 root kmem 44536 Dec 26 15:20:12 1999 /usr/bin/netstat stanb>> -r-sr-xr-x 5 root wheel 290448 Dec 26 15:24:16 1999 /usr/bin/newaliases stanb>> -r-xr-sr-x 1 root kmem 7380 Dec 26 15:20:14 1999 /usr/bin/nfsstat stanb>> -r-sr-xr-x 2 root wheel 23984 Dec 26 15:20:22 1999 /usr/bin/passwd stanb>> -r-sr-xr-x 1 root wheel 10036 Dec 26 15:20:25 1999 /usr/bin/quota stanb>> -r-sr-xr-x 1 root wheel 8888 Dec 26 15:20:28 1999 /usr/bin/rlogin stanb>> -r-sr-xr-x 1 root wheel 6768 Dec 26 15:20:30 1999 /usr/bin/rsh stanb>52,73c52,73 stanb>< -r-s--x--x 2 root wheel 47472 Dec 5 22:30:18 1999 /usr/bin/sperl5.00503 stanb>< -r-sr-xr-x 1 root wheel 7404 Dec 5 22:41:21 1999 /usr/bin/su stanb>< -r-s--x--x 2 root wheel 47472 Dec 5 22:30:18 1999 /usr/bin/suidperl stanb>< -r-xr-sr-x 1 root kmem 52424 Dec 5 22:41:23 1999 /usr/bin/systat stanb>< -r-xr-sr-x 1 root kmem 30376 Dec 5 22:41:34 1999 /usr/bin/top stanb>< -r-xr-sr-x 2 root kmem 10576 Dec 5 22:41:59 1999 /usr/bin/uptime stanb>< -r-sr-xr-x 1 uucp wheel 79112 Dec 5 22:24:45 1999 /usr/bin/uucp stanb>< -r-sr-xr-x 1 uucp wheel 33480 Dec 5 22:24:46 1999 /usr/bin/uuname stanb>< -r-sr-sr-x 1 uucp dialer 86556 Dec 5 22:24:50 1999 /usr/bin/uustat stanb>< -r-sr-xr-x 1 uucp wheel 79936 Dec 5 22:24:51 1999 /usr/bin/uux stanb>< -r-xr-sr-x 1 root kmem 14536 Dec 5 22:41:58 1999 /usr/bin/vmstat stanb>< -r-xr-sr-x 2 root kmem 10576 Dec 5 22:41:59 1999 /usr/bin/w stanb>< -r-xr-sr-x 1 root tty 8108 Dec 5 22:42:01 1999 /usr/bin/wall stanb>< -r-xr-sr-x 1 root tty 6692 Dec 5 22:42:07 1999 /usr/bin/write stanb>< -r-sr-xr-x 6 root wheel 28932 Dec 5 22:39:15 1999 /usr/bin/ypchfn stanb>< -r-sr-xr-x 6 root wheel 28932 Dec 5 22:39:15 1999 /usr/bin/ypchpass stanb>< -r-sr-xr-x 6 root wheel 28932 Dec 5 22:39:15 1999 /usr/bin/ypchsh stanb>< -r-sr-xr-x 2 root wheel 23984 Dec 5 22:41:02 1999 /usr/bin/yppasswd stanb>< -r-xr-sr-x 1 root games 6188 Dec 5 22:22:52 1999 /usr/games/dm stanb>< -r-sr-xr-x 1 root wheel 15040 Dec 5 22:33:10 1999 /usr/libexec/mail.local stanb>< -r-sr-sr-x 1 uucp dialer 197552 Dec 5 22:24:43 1999 /usr/libexec/uucp/uucico stanb>< -r-sr-s--- 1 uucp uucp 89160 Dec 5 22:24:53 1999 /usr/libexec/uucp/uuxqt stanb>--- stanb>> -r-s--x--x 2 root wheel 47472 Dec 26 15:09:31 1999 /usr/bin/sperl5.00503 stanb>> -r-sr-xr-x 1 root wheel 7404 Dec 26 15:20:40 1999 /usr/bin/su stanb>> -r-s--x--x 2 root wheel 47472 Dec 26 15:09:31 1999 /usr/bin/suidperl stanb>> -r-xr-sr-x 1 root kmem 52424 Dec 26 15:20:42 1999 /usr/bin/systat stanb>> -r-xr-sr-x 1 root kmem 30376 Dec 26 15:20:53 1999 /usr/bin/top stanb>> -r-xr-sr-x 2 root kmem 10576 Dec 26 15:21:19 1999 /usr/bin/uptime stanb>> -r-sr-xr-x 1 uucp wheel 79112 Dec 26 15:03:59 1999 /usr/bin/uucp stanb>> -r-sr-xr-x 1 uucp wheel 33480 Dec 26 15:04:01 1999 /usr/bin/uuname stanb>> -r-sr-sr-x 1 uucp dialer 86556 Dec 26 15:04:04 1999 /usr/bin/uustat stanb>> -r-sr-xr-x 1 uucp wheel 79936 Dec 26 15:04:06 1999 /usr/bin/uux stanb>> -r-xr-sr-x 1 root kmem 14536 Dec 26 15:21:17 1999 /usr/bin/vmstat stanb>> -r-xr-sr-x 2 root kmem 10576 Dec 26 15:21:19 1999 /usr/bin/w stanb>> -r-xr-sr-x 1 root tty 8108 Dec 26 15:21:20 1999 /usr/bin/wall stanb>> -r-xr-sr-x 1 root tty 6692 Dec 26 15:21:26 1999 /usr/bin/write stanb>> -r-sr-xr-x 6 root wheel 28932 Dec 26 15:18:36 1999 /usr/bin/ypchfn stanb>> -r-sr-xr-x 6 root wheel 28932 Dec 26 15:18:36 1999 /usr/bin/ypchpass stanb>> -r-sr-xr-x 6 root wheel 28932 Dec 26 15:18:36 1999 /usr/bin/ypchsh stanb>> -r-sr-xr-x 2 root wheel 23984 Dec 26 15:20:22 1999 /usr/bin/yppasswd stanb>> -r-xr-sr-x 1 root games 6188 Dec 26 15:02:07 1999 /usr/games/dm stanb>> -r-sr-xr-x 1 root wheel 15040 Dec 26 15:12:21 1999 /usr/libexec/mail.local stanb>> -r-sr-sr-x 1 uucp dialer 197552 Dec 26 15:03:58 1999 /usr/libexec/uucp/uucico stanb>> -r-sr-s--- 1 uucp uucp 89160 Dec 26 15:04:07 1999 /usr/libexec/uucp/uuxqt stanb>80,93c80,93 stanb>< -r-xr-sr-x 1 root kmem 9472 Dec 5 22:43:02 1999 /usr/sbin/iostat stanb>< -r-xr-sr-x 1 root daemon 23968 Dec 5 22:43:16 1999 /usr/sbin/lpc stanb>< -r-sr-xr-x 1 root wheel 14528 Dec 5 22:43:29 1999 /usr/sbin/mrinfo stanb>< -r-sr-xr-x 1 root wheel 27528 Dec 5 22:43:30 1999 /usr/sbin/mtrace stanb>< -r-sr-xr-- 1 root network 237236 Dec 5 22:43:52 1999 /usr/sbin/ppp stanb>< -r-sr-xr-x 1 root wheel 86632 Dec 5 22:43:54 1999 /usr/sbin/pppd stanb>< -r-xr-sr-x 2 root kmem 13184 Dec 5 22:43:56 1999 /usr/sbin/pstat stanb>< -r-sr-xr-x 5 root wheel 290448 Dec 5 22:44:46 1999 /usr/sbin/purgestat stanb>< -r-sr-xr-x 5 root wheel 290448 Dec 5 22:44:46 1999 /usr/sbin/sendmail stanb>< -r-sr-x--- 1 root network 9768 Dec 5 22:44:10 1999 /usr/sbin/sliplogin stanb>< -r-xr-sr-x 2 root kmem 13184 Dec 5 22:43:56 1999 /usr/sbin/swapinfo stanb>< -r-sr-xr-x 1 root wheel 13440 Dec 5 22:44:19 1999 /usr/sbin/timedc stanb>< -r-sr-xr-x 1 root wheel 11232 Dec 5 22:44:20 1999 /usr/sbin/traceroute stanb>< -r-xr-sr-x 1 root kmem 7036 Dec 5 22:44:21 1999 /usr/sbin/trpt stanb>--- stanb>> -r-xr-sr-x 1 root kmem 9472 Dec 26 15:22:29 1999 /usr/sbin/iostat stanb>> -r-xr-sr-x 1 root daemon 23968 Dec 26 15:22:42 1999 /usr/sbin/lpc stanb>> -r-sr-xr-x 1 root wheel 14528 Dec 26 15:22:54 1999 /usr/sbin/mrinfo stanb>> -r-sr-xr-x 1 root wheel 27528 Dec 26 15:22:55 1999 /usr/sbin/mtrace stanb>> -r-sr-xr-- 1 root network 237240 Dec 26 15:23:15 1999 /usr/sbin/ppp stanb>> -r-sr-xr-x 1 root wheel 86632 Dec 26 15:23:18 1999 /usr/sbin/pppd stanb>> -r-xr-sr-x 2 root kmem 13184 Dec 26 15:23:20 1999 /usr/sbin/pstat stanb>> -r-sr-xr-x 5 root wheel 290448 Dec 26 15:24:16 1999 /usr/sbin/purgestat stanb>> -r-sr-xr-x 5 root wheel 290448 Dec 26 15:24:16 1999 /usr/sbin/sendmail stanb>> -r-sr-x--- 1 root network 9768 Dec 26 15:23:33 1999 /usr/sbin/sliplogin stanb>> -r-xr-sr-x 2 root kmem 13184 Dec 26 15:23:20 1999 /usr/sbin/swapinfo stanb>> -r-sr-xr-x 1 root wheel 13440 Dec 26 15:23:42 1999 /usr/sbin/timedc stanb>> -r-sr-xr-x 1 root wheel 11232 Dec 26 15:23:42 1999 /usr/sbin/traceroute stanb>> -r-xr-sr-x 1 root kmem 7036 Dec 26 15:23:43 1999 /usr/sbin/trpt stanb> stanb> stanb> Whats going on here? stanb> stanb>-- stanb>Stan Brown stanb@netcom.com 404-996-6955 stanb>Factory Automation Systems stanb>Atlanta Ga. stanb>-- stanb>Look, look, see Windows 95. Buy, lemmings, buy! stanb>Pay no attention to that cliff ahead... Henry Spencer stanb>(c) 1998 Stan Brown. Redistribution via the Microsoft Network is prohibited. stanb> stanb> stanb>To Unsubscribe: send mail to majordomo@FreeBSD.org stanb>with "unsubscribe freebsd-stable" in the body of the message stanb> Regards, Listopad Alexandr (laa@zgia.zp.ua), LAA7-RIPE ZGIA, Zaporozhye, Ukraine. http://www.zgia.zp.ua. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 27 6:14: 0 1999 Delivered-To: freebsd-stable@freebsd.org Received: from foobar.franken.de (foobar.franken.de [194.94.249.81]) by hub.freebsd.org (Postfix) with ESMTP id 6EF1C150F0 for ; Mon, 27 Dec 1999 06:13:54 -0800 (PST) (envelope-from logix@foobar.franken.de) Received: (from logix@localhost) by foobar.franken.de (8.8.8/8.8.5) id PAA18262; Mon, 27 Dec 1999 15:13:22 +0100 (CET) Message-ID: <19991227151321.A18099@foobar.franken.de> Date: Mon, 27 Dec 1999 15:13:21 +0100 From: Harold Gutch To: Stan Brown , FreeBSD Stable List Subject: Re: Huge differences in suid programs ? References: <199912271336.FAA14584@netcom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199912271336.FAA14584@netcom.com>; from Stan Brown on Mon, Dec 27, 1999 at 08:36:11AM -0500 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Dec 27, 1999 at 08:36:11AM -0500, Stan Brown wrote: > I cvsuped 3 machines and did a make worlds on the yesterday. I got HUGE > differences on the suid files in the security report this morning: > > > > polar.fas.com setuid diffs: > 1,12c1,12 > < -r-xr-sr-x 1 root operator 51196 Dec 5 22:22:13 1999 /bin/df > < -r-xr-sr-x 1 root kmem 189664 Dec 5 22:22:26 1999 /bin/ps > < -r-sr-xr-x 1 root wheel 208408 Dec 5 22:22:29 1999 /bin/rcp > < -r-xr-sr-x 1 root kmem 100148 Dec 5 22:33:20 1999 /sbin/ccdconfig > < -r-xr-sr-x 1 root kmem 103696 Dec 5 22:33:27 1999 /sbin/dmesg > < -r-xr-sr-x 2 root tty 221736 Dec 5 22:33:28 1999 /sbin/dump > < -r-sr-xr-x 1 root wheel 145528 Dec 5 22:34:11 1999 /sbin/ping > < -r-xr-sr-x 2 root tty 221736 Dec 5 22:33:28 1999 /sbin/rdump > < -r-xr-sr-x 2 root tty 244920 Dec 5 22:34:16 1999 /sbin/restore > < -r-sr-xr-x 1 root wheel 153760 Dec 5 22:34:18 1999 /sbin/route > < -r-xr-sr-x 2 root tty 244920 Dec 5 22:34:16 1999 /sbin/rrestore > < -r-sr-x--- 1 root operator 151712 Dec 5 22:34:22 1999 /sbin/shutdown > --- > > -r-xr-sr-x 1 root operator 51204 Dec 26 15:01:26 1999 /bin/df > > -r-xr-sr-x 1 root kmem 190016 Dec 26 15:01:40 1999 /bin/ps > > -r-sr-xr-x 1 root wheel 208408 Dec 26 15:01:43 1999 /bin/rcp > > -r-xr-sr-x 1 root kmem 100156 Dec 26 15:12:33 1999 /sbin/ccdconfig > > -r-xr-sr-x 1 root kmem 103872 Dec 26 15:12:39 1999 /sbin/dmesg > > -r-xr-sr-x 2 root tty 221768 Dec 26 15:12:40 1999 /sbin/dump > > -r-sr-xr-x 1 root wheel 145544 Dec 26 15:13:24 1999 /sbin/ping > > -r-xr-sr-x 2 root tty 221768 Dec 26 15:12:40 1999 /sbin/rdump > > -r-xr-sr-x 2 root tty 244920 Dec 26 15:13:28 1999 /sbin/restore > > -r-sr-xr-x 1 root wheel 153760 Dec 26 15:13:30 1999 /sbin/route > > -r-xr-sr-x 2 root tty 244920 Dec 26 15:13:28 1999 /sbin/rrestore > > -r-sr-x--- 1 root operator 151712 Dec 26 15:13:36 1999 /sbin/shutdown [...] > > > Whats going on here? The suid binaries got built and installed during your "make world" and thus have new timestamps as you can see. As the new output of "ls -l" is different to the old one, /etc/security will complain about exactly these differences that you see above. The end line is that this behaviour is perfectly normal after having done "make world" or "make installworld". bye, Harold -- Someone should do a study to find out how many human life spans have been lost waiting for NT to reboot. Ken Deboy on Dec 24 1999 in comp.unix.bsd.freebsd.misc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 27 6:50:52 1999 Delivered-To: freebsd-stable@freebsd.org Received: from carlton.innotts.co.uk (carlton.innotts.co.uk [212.56.32.2]) by hub.freebsd.org (Postfix) with ESMTP id 3DF0D14ECC for ; Mon, 27 Dec 1999 06:50:49 -0800 (PST) (envelope-from robmel@nadt.org.uk) Received: from muffin.highwire.local (pool-1-p16.innotts.co.uk [212.56.33.16]) by carlton.innotts.co.uk (8.9.3/8.9.3) with ESMTP id OAA05530 for ; Mon, 27 Dec 1999 14:50:47 GMT Received: from [172.16.17.20] (robsmac.highwire.local [172.16.17.20]) by muffin.highwire.local (8.9.3/8.9.3) with ESMTP id OAA01085 for ; Mon, 27 Dec 1999 14:50:05 GMT (envelope-from robmel@nadt.org.uk) Mime-Version: 1.0 X-Sender: robmel@mailhost Message-Id: Date: Mon, 27 Dec 1999 14:50:19 +0000 To: freebsd-stable@freebsd.org From: Robin Melville Subject: CVSup woes Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi All, Am I alone in having a hell of a time cvsup-ing 3.4? I'm using the exact same supfile as ever, but it crawls (on whatever server I try) then finally dies with "TreeList failed: Network write failure: Connection timed out" at anything up to one hour after starting. This is cvsup client REL_16_0 over userland ppp on a 56k modem line with: *default host=cvsup.uk.FreeBSD.org *default base=/usr *default prefix=/usr *default release=cvs tag=RELENG_3 *default delete use-rel-suffix *default compress src-all I'm hoping that it's because the entire world has abandoned their seasonal holidays in order to download FreeBSD. However, it's possible something is going wrong. Best wishes for the new year! Robin. ---------------------------------------------------------------------- Robin Melville, Addiction Information Service Nottingham Alcohol & Drug Team Tel: +44 (0)115 952 9478 Fax: +44 (0)115 952 9421 work: robmel@nadt.org.uk Pages: http://www.nadt.org.uk/ ---------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 27 7:18:46 1999 Delivered-To: freebsd-stable@freebsd.org Received: from techpower.net (techpower.net [205.133.231.1]) by hub.freebsd.org (Postfix) with ESMTP id D331714D1F; Mon, 27 Dec 1999 07:18:39 -0800 (PST) (envelope-from hometeam@techpower.net) Received: from localhost (hometeam@localhost) by techpower.net (8.9.3/8.9.3) with ESMTP id KAA00386; Mon, 27 Dec 1999 10:20:07 GMT (envelope-from hometeam@techpower.net) Date: Mon, 27 Dec 1999 10:20:07 +0000 (GMT) From: hometeam To: Oleg Semyonov Cc: freebsd-questions@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: patches for pppd-2.3.10-radius are here In-Reply-To: <011801bf506f$16aa1360$0400a8c0@admin.dnepr.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 2.3.10 will not compile on 3.4 stable . On Mon, 27 Dec 1999, Oleg Semyonov wrote: > Hi all! > > I'am receiving many questions about pppd patch for RADIUS > support. So, I decide to make it available via ftp. Briefly, > it is patch to pppd-2.3.10 for using this version with FreeBSD > system (based on currently bundled version) plus optional ability > to use RADIUS authentication and accounting (based on standard > FreeBSD RADIUS library by John Polstra). > > readme.txt . . . . . . . . . . . Dec 24 10:43 1k > README.RADIUS. . . . . . . . . . Dec 24 10:29 10k > libradius.tar.gz . . . . . . . . Dec 24 10:19 14k > ppp-2.3.10-radius.diff.gz. . . . Dec 24 10:19 20k > ppp-2.3.10.tar.gz. . . . . . . . Sep 17 06:16 766k > > Main ftp site is ftp://ftp.energodar.dp.ua/pub/FreeBSD/RADIUS/ > Mirror for patches is at ftp://ftp.slashnet.org/users/shonson/ > > README.RADIUS is attached to the message. > > Try it out! > > OS (os@altavista.net), ICQ:31256452 > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 27 8:19: 7 1999 Delivered-To: freebsd-stable@freebsd.org Received: from dozer.skynet.be (dozer.skynet.be [195.238.2.36]) by hub.freebsd.org (Postfix) with ESMTP id 378BD1517B for ; Mon, 27 Dec 1999 08:19:04 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by dozer.skynet.be (8.9.3/odie-relay-v1.0) with ESMTP id RAA22635; Mon, 27 Dec 1999 17:18:13 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@foxbert.skynet.be Message-Id: In-Reply-To: <19991227134529.D1290@marder-1> References: <199912271336.FAA14584@netcom.com> <19991227134529.D1290@marder-1> Date: Mon, 27 Dec 1999 17:17:46 +0100 To: Mark Ovens , Stan Brown From: Brad Knowles Subject: Re: Huge differences in suid programs ? Cc: FreeBSD Stable List Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 1:45 PM +0000 1999/12/27, Mark Ovens wrote: > The timestamp has changed on the files because make world replaced > them so they're different. Right, but *why* are they so different? Was it perhaps a change in a library, a change in the compiler, or was it that the source code for these programs itself actually changed so much? I understand their being replaced (and why the security report would flag them all), but I don't understand why they were all so different to begin with. -- These are my opinions -- not to be taken as official Skynet policy ____________________________________________________________________ |o| Brad Knowles, Belgacom Skynet NV/SA |o| |o| Systems Architect, News & FTP Admin Rue Col. Bourg, 124 |o| |o| Phone/Fax: +32-2-706.11.11/12.49 B-1140 Brussels |o| |o| http://www.skynet.be Belgium |o| \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. Unix is very user-friendly. It's just picky who its friends are. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 27 8:24:22 1999 Delivered-To: freebsd-stable@freebsd.org Received: from kci.kciLink.com (kci.kciLink.com [204.117.82.1]) by hub.freebsd.org (Postfix) with ESMTP id 8432B14D1A for ; Mon, 27 Dec 1999 08:24:20 -0800 (PST) (envelope-from khera@kciLink.com) Received: from onceler.kcilink.com (onceler.kciLink.com [204.117.82.2]) by kci.kciLink.com (Postfix) with ESMTP id 02817E8A5; Mon, 27 Dec 1999 11:24:18 -0500 (EST) Received: (from khera@localhost) by onceler.kcilink.com (8.9.3/8.9.3) id LAA06151; Mon, 27 Dec 1999 11:24:18 -0500 (EST) (envelope-from khera@kci.kcilink.com) From: Vivek Khera MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14439.37554.879785.902295@onceler.kcilink.com> Date: Mon, 27 Dec 1999 11:24:18 -0500 (EST) To: Kris Kennaway Cc: jack , freebsd-stable@FreeBSD.ORG Subject: Re: three files in /usr/sbin not updated by make world In-Reply-To: References: <14438.39906.805120.393675@kci.kciLink.com> X-Mailer: VM 6.72 under 21.1 (patch 8) "Bryce Canyon" XEmacs Lucid Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "KK" == Kris Kennaway writes: KK> On Sun, 26 Dec 1999, Vivek Khera wrote: j> They're leftovers from the isdn4bsd upgrade from version 0.71 to j> 0.81 back in May. You'll find the source, and man pages, in the j> src/usr.sbin/i4b/alawulaw directory in the Attic. >> >> so can I assume they are safe to delete now? especially if I don't >> use isdn on this machine? KK> Yes. Thanks to all to clear this up! -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Vivek Khera, Ph.D. Khera Communications, Inc. Internet: khera@kciLink.com Rockville, MD +1-301-545-6996 PGP & MIME spoken here http://www.kciLink.com/home/khera/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 27 8:25:27 1999 Delivered-To: freebsd-stable@freebsd.org Received: from kot.ne.mediaone.net (kot.ne.mediaone.net [24.218.15.190]) by hub.freebsd.org (Postfix) with ESMTP id E932615283; Mon, 27 Dec 1999 08:25:15 -0800 (PST) (envelope-from mi@kot.ne.mediaone.net) Received: from rtfm.newton (rtfm.newton [10.10.0.1]) by kot.ne.mediaone.net (8.9.3/8.9.1) with ESMTP id LAA53903; Mon, 27 Dec 1999 11:25:14 -0500 (EST) From: Mikhail Teterin X-Relay-IP: 10.10.0.1 Received: (from mi@localhost) by rtfm.newton (8.9.3/8.9.3) id LAA74751; Mon, 27 Dec 1999 11:25:14 -0500 (EST) (envelope-from mi@kot.ne.mediaone.net) Message-Id: <199912271625.LAA74751@rtfm.newton> Subject: -lc vs. -lc_r (building Apache-PHP) To: stable@freebsd.org, ports@freebsd.org Date: Mon, 27 Dec 1999 11:25:14 -0500 (EST) X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli" /usr/local/lib/libpng.so.3 (0x181a2000) libz.so.2 => /usr/lib/libz.so.2 (0x181bc000) libttf.so.4 => /usr/local/lib/libttf.so.4 (0x181c9000) libmysqlclient.so.6 => /usr/local/lib/mysql/libmysqlclient.so.6 (0x181ec000) libmcrypt.so.2 => /usr/local/lib/libmcrypt.so.2 (0x181fe000) libmhash.so.1 => /usr/local/lib/libmhash.so.1 (0x18214000) libpam.so.1 => /usr/lib/libpam.so.1 (0x18225000) libm.so.2 => /usr/lib/libm.so.2 (0x1822d000) libcrypt.so.2 => /usr/lib/libcrypt.so.2 (0x18248000) libgdbm.so.2 => /usr/local/lib/libgdbm.so.2 (0x1824b000) libmm.so.10 => /usr/local/lib/libmm.so.10 (0x18251000) libc.so.3 => /usr/lib/libc.so.3 (0x18255000) libc_r.so.3 => /usr/lib/libc_r.so.3 (0x182d7000) # gdb apache [...] Program received signal SIGSEGV, Segmentation fault. 0x182bb240 in __swhatbuf () from /usr/lib/libc.so.3 Now, if I relink the executable manually, adding the -pthread at the end: cc -DHARD_SERVER_LIMIT=512 \ -DDEFAULT_PATH=\"/usr/local/bin:/bin:/usr/bin\" -funsigned-char \ -DTARGET=\"apache\" -DMOD_SSL=204109 -DEAPI -DEAPI_MM \ -DUSE_EXPAT -I./lib/expat-lite -O2 -fexpensive-optimizations \ -pipe `./apaci` -L/usr/local/lib -Wl,-E -o apache \ buildmark.o modules.o modules/standard/libstandard.a \ modules/php3/libphp3.a main/libmain.a ./os/unix/libos.a \ ap/libap.a lib/expat-lite/libexpat.a -L/usr/local/lib \ -R/usr/local/lib/mysql /usr/local/lib/libc-client4.a -lgd -lpng \ -lz -lttf -L/usr/local/lib/mysql -lmysqlclient -lexpat -lmcrypt \ -lmhash -Lmodules/php3 -L../modules/php3 -L../../modules/php3 \ -lmodphp3 -lz -lpam -lm -lcrypt -lcrypt -lgdbm -lmm -pthread /usr/lib/libc.so.3: warning: mktemp() possibly used unsafely; consider using mkstemp() /usr/lib/libc.so.3: warning: this program uses gets(), which is unsafe. /usr/lib/libc.so.3: WARNING! setkey(3) not present in the system! /usr/lib/libc.so.3: WARNING! des_setkey(3) not present in the system! /usr/lib/libc.so.3: WARNING! encrypt(3) not present in the system! /usr/lib/libc.so.3: WARNING! des_cipher(3) not present in the system! /usr/lib/libc.so.3: warning: this program uses f_prealloc(), which is stupid. The libraries are arranged differently: apache: libpng.so.3 => /usr/local/lib/libpng.so.3 (0x181a2000) libz.so.2 => /usr/lib/libz.so.2 (0x181bc000) libttf.so.4 => /usr/local/lib/libttf.so.4 (0x181c9000) libmysqlclient.so.6 => /usr/local/lib/mysql/libmysqlclient.so.6 (0x181ec000) libmcrypt.so.2 => /usr/local/lib/libmcrypt.so.2 (0x181fe000) libmhash.so.1 => /usr/local/lib/libmhash.so.1 (0x18214000) libpam.so.1 => /usr/lib/libpam.so.1 (0x18225000) libm.so.2 => /usr/lib/libm.so.2 (0x1822d000) libcrypt.so.2 => /usr/lib/libcrypt.so.2 (0x18248000) libgdbm.so.2 => /usr/local/lib/libgdbm.so.2 (0x1824b000) libmm.so.10 => /usr/local/lib/libmm.so.10 (0x18251000) libc_r.so.3 => /usr/lib/libc_r.so.3 (0x18255000) libc.so.3 => /usr/lib/libc.so.3 (0x182e9000) and the server starts and appears to work. What's the magic and why doesn't the port know it? Why is -lc even in play if some of the components (-lmysqlclient) require -lc_r? Yours, -mi FreeBSD rtfm.newton 3.4-STABLE FreeBSD 3.4-STABLE #0: Fri Dec 17 08:49:51 EST 1999 --ELM946311914-74626-0_ Content-Type: text/plain; charset=KOI8-R Content-Disposition: attachment; filename=Makefile.inc Content-Description: Automaticly generated by the port Content-Transfer-Encoding: 7bit PKGNAME= apache+php+mod_ssl-${VERSION_APACHE}+${VERSION_PHP}+${VERSION_MODSSL} DISTFILES+= mod_ssl-${VERSION_MODSSL}-${VERSION_APACHE}${EXTRACT_SUFX} BUILD_DEPENDS+= openssl:${PORTSDIR}/security/openssl \ mm-config:${PORTSDIR}/devel/mm \ ${PREFIX}/lib/libmm.a:${PORTSDIR}/devel/mm LIB_DEPENDS+= crypto.1:${PORTSDIR}/security/openssl \ ssl.1:${PORTSDIR}/security/openssl RUN_DEPENDS+= openssl:${PORTSDIR}/security/openssl VERSION_MODSSL= 2.4.9 RESTRICTED= "Contains cryptography" CONFIGURE_ARGS+=--enable-module=ssl \ --enable-module=define CONFIGURE_ENV+= SSL_BASE='SYSTEM' EAPI_MM='SYSTEM' PATH="${PREFIX}/bin:${PATH}" PLIST= ${PKGDIR}/PLIST.modssl SSL= ssl TYPE= test CRT= KEY= pre-patch: @cd ${WRKDIR}/mod_ssl-${VERSION_MODSSL}-${VERSION_APACHE} \ && ${ECHO_MSG} "===> Applying mod_ssl-${VERSION_MODSSL} extension" \ && ./configure --with-apache=../${DISTNAME} --expert post-patch: @cd ${WRKSRC} \ && find . -type f -name "*.orig" -print | xargs ${RM} -f post-build: @cd ${WRKSRC} \ && ${ECHO_MSG} "===> Creating Dummy Certificate for Server (SnakeOil)" \ && ${ECHO_MSG} " [use 'make certificate' to create a real one]" \ && ${MAKE} certificate TYPE=dummy >/dev/null 2>&1 certificate: @cd ${WRKSRC} \ && ${ECHO_MSG} "===> Creating Test Certificate for Server" \ && ${MAKE} certificate TYPE=$(TYPE) CRT=$(CRT) KEY=$(KEY) BUILD_DEPENDS+= ${PREFIX}/lib/libgd.a:${PORTSDIR}/graphics/gd PHP_CONF_ARGS+= --with-gd=${PREFIX} LIB_DEPENDS+= ttf.4:${PORTSDIR}/print/freetype PHP_CONF_ARGS+= --with-ttf=${PREFIX} PHP_CONF_ARGS+= --with-zlib LIB_DEPENDS+= mcrypt.2:${PORTSDIR}/security/libmcrypt PHP_CONF_ARGS+= --with-mcrypt=${PREFIX} LIB_DEPENDS+= mhash.1:${PORTSDIR}/security/mhash PHP_CONF_ARGS+= --with-mhash=${PREFIX} BUILD_DEPENDS+= ${PREFIX}/lib/libc-client4.a:${PORTSDIR}/mail/imap-uw PHP_CONF_ARGS+= --with-imap=${PREFIX} LIB_DEPENDS+= mysqlclient.6:${PORTSDIR}/databases/mysql322-client PHP_CONF_ARGS+= --with-mysql=${PREFIX} BUILD_DEPENDS+= ${PREFIX}/lib/libexpat.a:${PORTSDIR}/textproc/expat BUILD_DEPENDS+= ${PREFIX}/include/xml/xmlparse.h:${PORTSDIR}/textproc/expat BUILD_DEPENDS+= ${PREFIX}/include/xml/xmltok.h:${PORTSDIR}/textproc/expat PHP_CONF_ARGS+= --with-xml=${PREFIX} --ELM946311914-74626-0_-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 27 8:28:23 1999 Delivered-To: freebsd-stable@freebsd.org Received: from kci.kciLink.com (kci.kciLink.com [204.117.82.1]) by hub.freebsd.org (Postfix) with ESMTP id 63242152C2 for ; Mon, 27 Dec 1999 08:28:21 -0800 (PST) (envelope-from khera@kciLink.com) Received: from onceler.kcilink.com (onceler.kciLink.com [204.117.82.2]) by kci.kciLink.com (Postfix) with ESMTP id 87AA4E8A5; Mon, 27 Dec 1999 11:28:20 -0500 (EST) Received: (from khera@localhost) by onceler.kcilink.com (8.9.3/8.9.3) id LAA06181; Mon, 27 Dec 1999 11:28:20 -0500 (EST) (envelope-from khera@kci.kcilink.com) From: Vivek Khera MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14439.37796.454219.5788@onceler.kcilink.com> Date: Mon, 27 Dec 1999 11:28:20 -0500 (EST) To: Stan Brown Cc: freebsd-stable@freebsd.org (FreeBSD Stable List) Subject: Re: Huge differences in suid programs ? In-Reply-To: <199912271336.FAA14584@netcom.com> References: <199912271336.FAA14584@netcom.com> X-Mailer: VM 6.72 under 21.1 (patch 8) "Bryce Canyon" XEmacs Lucid Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "SB" == Stan Brown writes: SB> I cvsuped 3 machines and did a make worlds on the yesterday. I got HUGE SB> differences on the suid files in the security report this morning: [ ... ] SB> Whats going on here? You updated each and every one of your SUID programs in /usr/bin, /bin, /usr/sbin, and /sbin when you did "make world". You should expect to have the nightly security script notice these changes. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 27 8:29:53 1999 Delivered-To: freebsd-stable@freebsd.org Received: from freesbee.wheel.dk (freesbee.wheel.dk [193.162.159.97]) by hub.freebsd.org (Postfix) with ESMTP id 6A98015288 for ; Mon, 27 Dec 1999 08:29:51 -0800 (PST) (envelope-from jesper@skriver.dk) Received: by freesbee.wheel.dk (Postfix, from userid 1001) id 0D3F73E35; Mon, 27 Dec 1999 17:29:50 +0100 (CET) Date: Mon, 27 Dec 1999 17:29:49 +0100 From: Jesper Skriver To: Brad Knowles Cc: Mark Ovens , Stan Brown , FreeBSD Stable List Subject: Re: Huge differences in suid programs ? Message-ID: <19991227172949.A9209@skriver.dk> References: <199912271336.FAA14584@netcom.com> <19991227134529.D1290@marder-1> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from blk@skynet.be on Mon, Dec 27, 1999 at 05:17:46PM +0100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Dec 27, 1999 at 05:17:46PM +0100, Brad Knowles wrote: > At 1:45 PM +0000 1999/12/27, Mark Ovens wrote: > > > The timestamp has changed on the files because make world replaced > > them so they're different. > > Right, but *why* are they so different? Was it perhaps a change > in a library, a change in the compiler, or was it that the source > code for these programs itself actually changed so much? What do you mean by different ? Most of them had only the date changed ... /Jesper -- Jesper Skriver, jesper(at)skriver(dot)dk Work: Network manager @ AS3292 (Tele Danmark DataNetworks) Private: Geek @ AS2109 (A much smaller network ;-) One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone to bind them. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 27 8:56:40 1999 Delivered-To: freebsd-stable@freebsd.org Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (Postfix) with ESMTP id B017914BCE for ; Mon, 27 Dec 1999 08:56:34 -0800 (PST) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.8.8/8.8.8) id RAA28357 for freebsd-stable@FreeBSD.ORG; Mon, 27 Dec 1999 17:56:33 +0100 (CET) (envelope-from olli) Date: Mon, 27 Dec 1999 17:56:33 +0100 (CET) From: Oliver Fromme Message-Id: <199912271656.RAA28357@dorifer.heim3.tu-clausthal.de> To: freebsd-stable@FreeBSD.ORG Subject: Re: Huge differences in suid programs ? Organization: Administration TU Clausthal Reply-To: freebsd-stable@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: TIN [version 1.2 RZTUC(3) PL2] Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brad Knowles wrote in list.freebsd-stable: > At 1:45 PM +0000 1999/12/27, Mark Ovens wrote: > > > The timestamp has changed on the files because make world replaced > > them so they're different. > > Right, but *why* are they so different? Was it perhaps a change > in a library, a change in the compiler, or was it that the source > code for these programs itself actually changed so much? > > I understand their being replaced (and why the security report > would flag them all), but I don't understand why they were all so > different to begin with. Well, the daily security script just does an "ls -l" on all suid/sgid binaries and diffs them with the previous listing. Therefore it will regard all differences in the ls -l output as "differences". This can be the ownership, time stamps, and sizes of the files. Even if the actual contents of the files are the same, the time stamps are not the same (because they indicate the time at which the files where created), so the daily security script will regard them as "different". It's a feature. ;) Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 27 9: 0:51 1999 Delivered-To: freebsd-stable@freebsd.org Received: from freeway.dcfinc.com (cx74889-a.phnx3.az.home.com [24.1.193.157]) by hub.freebsd.org (Postfix) with ESMTP id 1121E14CE8 for ; Mon, 27 Dec 1999 09:00:49 -0800 (PST) (envelope-from chad@freeway.dcfinc.com) Received: (from chad@localhost) by freeway.dcfinc.com (8.8.8/8.8.8) id JAA09409; Mon, 27 Dec 1999 09:59:20 -0700 (MST) (envelope-from chad) Date: Mon, 27 Dec 1999 09:59:20 -0700 From: "Chad R. Larson" To: Brad Knowles Cc: Mark Ovens , Stan Brown , FreeBSD Stable List Subject: Re: Huge differences in suid programs ? Message-ID: <19991227095920.A9365@freeway.dcfinc.com> References: <199912271336.FAA14584@netcom.com> <19991227134529.D1290@marder-1> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from blk@skynet.be on Mon, Dec 27, 1999 at 05:17:46PM +0100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Dec 27, 1999 at 05:17:46PM +0100, Brad Knowles wrote: > At 1:45 PM +0000 1999/12/27, Mark Ovens wrote: > > > The timestamp has changed on the files because make world replaced > > them so they're different. > > Right, but *why* are they so different? Was it perhaps a change > in a library, a change in the compiler, or was it that the source > code for these programs itself actually changed so much? The "make world" regenerates every binary on the machine, unless you set the "no clean" option. It does so without regard to whether the source for any particular program has changed. I believe this to generally be a Good Thing. Think of it as the ultimate anti-virus, if nothing else. -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org larson1@home.net DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 27 9: 6:43 1999 Delivered-To: freebsd-stable@freebsd.org Received: from pawn.primelocation.net (pawn.primelocation.net [205.161.238.235]) by hub.freebsd.org (Postfix) with ESMTP id 3618D14CE8 for ; Mon, 27 Dec 1999 09:06:41 -0800 (PST) (envelope-from cdf.lists@fxp.org) Received: by pawn.primelocation.net (Postfix, from userid 1016) id E014A9B52; Mon, 27 Dec 1999 12:06:39 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by pawn.primelocation.net (Postfix) with ESMTP id D737BBA0C; Mon, 27 Dec 1999 12:06:39 -0500 (EST) Date: Mon, 27 Dec 1999 12:06:39 -0500 (EST) From: "Chris D. Faulhaber" X-Sender: cdf.lists@pawn.primelocation.net To: "Chad R. Larson" Cc: Brad Knowles , Mark Ovens , Stan Brown , FreeBSD Stable List Subject: Re: Huge differences in suid programs ? In-Reply-To: <19991227095920.A9365@freeway.dcfinc.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, 27 Dec 1999, Chad R. Larson wrote: > On Mon, Dec 27, 1999 at 05:17:46PM +0100, Brad Knowles wrote: > > At 1:45 PM +0000 1999/12/27, Mark Ovens wrote: > > > > > The timestamp has changed on the files because make world replaced > > > them so they're different. > > > > Right, but *why* are they so different? Was it perhaps a change > > in a library, a change in the compiler, or was it that the source > > code for these programs itself actually changed so much? > > The "make world" regenerates every binary on the machine, unless you > set the "no clean" option. It does so without regard to whether the > source for any particular program has changed. > OTOH, if you set: INSTALL=install -C in /etc/make.conf, unchanged files will not have their modification time changed. ----- 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 Dec 27 9:31:33 1999 Delivered-To: freebsd-stable@freebsd.org Received: from rs.ksl.co.il (rs.ksl.co.il [199.203.44.20]) by hub.freebsd.org (Postfix) with ESMTP id 559B515056 for ; Mon, 27 Dec 1999 09:31:26 -0800 (PST) (envelope-from roman@xpert.com) Received: from localhost (roman@localhost) by rs.ksl.co.il (8.9.3/8.9.3) with ESMTP id TAA58770 for ; Mon, 27 Dec 1999 19:35:22 +0200 (IST) X-Authentication-Warning: rs.ksl.co.il: roman owned process doing -bs Date: Mon, 27 Dec 1999 19:35:22 +0200 (IST) From: Roman Shterenzon To: freebsd-stable@FreeBSD.ORG Subject: some more files left from prev. install Message-ID: Organization: Xpert UNIX Systems Ltd. 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 also noted /usr/bin/bdes and /usr/sbin/named-bootconf which are left from previous cvsups. Was it replaced with something? --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 Dec 27 9:39:13 1999 Delivered-To: freebsd-stable@freebsd.org Received: from kci.kciLink.com (kci.kciLink.com [204.117.82.1]) by hub.freebsd.org (Postfix) with ESMTP id 01E9014DF2 for ; Mon, 27 Dec 1999 09:39:12 -0800 (PST) (envelope-from khera@kciLink.com) Received: from onceler.kcilink.com (onceler.kciLink.com [204.117.82.2]) by kci.kciLink.com (Postfix) with ESMTP id 02584E8A5; Mon, 27 Dec 1999 12:39:11 -0500 (EST) Received: (from khera@localhost) by onceler.kcilink.com (8.9.3/8.9.3) id MAA06825; Mon, 27 Dec 1999 12:39:10 -0500 (EST) (envelope-from khera@kci.kcilink.com) From: Vivek Khera MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14439.42046.843833.513339@onceler.kcilink.com> Date: Mon, 27 Dec 1999 12:39:10 -0500 (EST) To: Roman Shterenzon Cc: freebsd-stable@FreeBSD.ORG Subject: Re: some more files left from prev. install In-Reply-To: References: X-Mailer: VM 6.72 under 21.1 (patch 8) "Bryce Canyon" XEmacs Lucid Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "RS" == Roman Shterenzon writes: RS> Hello, RS> I also noted /usr/bin/bdes and /usr/sbin/named-bootconf which are left /usr/bin/bdes was updated for me, however /usr/sbin/named-bootconf was not updated for me, as well. -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Vivek Khera, Ph.D. Khera Communications, Inc. Internet: khera@kciLink.com Rockville, MD +1-301-545-6996 PGP & MIME spoken here http://www.kciLink.com/home/khera/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 27 10: 2:20 1999 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 7CBC814DF5 for ; Mon, 27 Dec 1999 10:02:18 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id KAA08977; Mon, 27 Dec 1999 10:02:16 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id KAA02871; Mon, 27 Dec 1999 10:02:15 -0800 (PST) (envelope-from jdp@polstra.com) Date: Mon, 27 Dec 1999 10:02:15 -0800 (PST) Message-Id: <199912271802.KAA02871@vashon.polstra.com> To: robmel@nadt.org.uk Subject: Re: CVSup woes In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Cc: stable@freebsd.org Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Robin Melville wrote: > Hi All, > > Am I alone in having a hell of a time cvsup-ing 3.4? I'm using the > exact same supfile as ever, but it crawls (on whatever server I try) > then finally dies with "TreeList failed: Network write failure: > Connection timed out" at anything up to one hour after starting. I haven't seen any problems like this under 3.4. Have you tried some other mirror sites? There are only about 50 of them to choose from. :-) John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "No matter how cynical I get, I just can't keep up." -- Nora Ephron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 27 10: 8:19 1999 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 9BED5150E1 for ; Mon, 27 Dec 1999 10:08:17 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id KAA09008; Mon, 27 Dec 1999 10:08:16 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id KAA02918; Mon, 27 Dec 1999 10:08:15 -0800 (PST) (envelope-from jdp@polstra.com) Date: Mon, 27 Dec 1999 10:08:15 -0800 (PST) Message-Id: <199912271808.KAA02918@vashon.polstra.com> To: jedgar@fxp.org Subject: Re: Huge differences in suid programs ? In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Cc: stable@freebsd.org Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Chris D. Faulhaber wrote: > > OTOH, if you set: > > INSTALL=install -C > > in /etc/make.conf, unchanged files will not have their modification time > changed. That's right, but it's more in the spirit of the make infrastructure to set COPY = -C and leave INSTALL alone. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "No matter how cynical I get, I just can't keep up." -- Nora Ephron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 27 10:15:24 1999 Delivered-To: freebsd-stable@freebsd.org Received: from pawn.primelocation.net (pawn.primelocation.net [205.161.238.235]) by hub.freebsd.org (Postfix) with ESMTP id AD9CE14D1D for ; Mon, 27 Dec 1999 10:15:22 -0800 (PST) (envelope-from jedgar@fxp.org) Received: by pawn.primelocation.net (Postfix, from userid 1003) id 83A5A9B52; Mon, 27 Dec 1999 13:13:49 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by pawn.primelocation.net (Postfix) with ESMTP id 7A150BA0C; Mon, 27 Dec 1999 13:13:49 -0500 (EST) Date: Mon, 27 Dec 1999 13:13:49 -0500 (EST) From: "Chris D. Faulhaber" X-Sender: jedgar@pawn.primelocation.net To: John Polstra Cc: stable@freebsd.org Subject: Re: Huge differences in suid programs ? In-Reply-To: <199912271808.KAA02918@vashon.polstra.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, 27 Dec 1999, John Polstra wrote: > In article , > Chris D. Faulhaber wrote: > > > > OTOH, if you set: > > > > INSTALL=install -C > > > > in /etc/make.conf, unchanged files will not have their modification time > > changed. > > That's right, but it's more in the spirit of the make infrastructure > to set COPY = -C and leave INSTALL alone. > Makes sense. I was just going by the examples in /etc{/defaults}/make.conf. If COPY is more correct, should /etc{/defaults}/make.conf be changed? ----- 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 Dec 27 10:32: 4 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail2.uniserve.com (mail2.uniserve.com [204.244.156.7]) by hub.freebsd.org (Postfix) with ESMTP id 16C6914F01; Mon, 27 Dec 1999 10:31:51 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca ([204.244.186.218]) by mail2.uniserve.com with smtp (Exim 3.03 #4) id 122evr-000AYC-00; Mon, 27 Dec 1999 10:31:47 -0800 Date: Mon, 27 Dec 1999 10:31:44 -0800 (PST) From: Tom X-Sender: tom@shell.uniserve.ca To: Mikhail Teterin Cc: stable@freebsd.org, ports@freebsd.org Subject: Re: -lc vs. -lc_r (building Apache-PHP) In-Reply-To: <199912271625.LAA74751@rtfm.newton> Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY=ELM946311914-74626-0_ Content-ID: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --ELM946311914-74626-0_ Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-ID: On Mon, 27 Dec 1999, Mikhail Teterin wrote: ... > What's the magic and why doesn't the port know it? Why is -lc even in > play if some of the components (-lmysqlclient) require -lc_r? Yours, libmysqlclient does not require -lc_r, because the library does not use threads. Only mysqld is threaded. > -mi > > FreeBSD rtfm.newton 3.4-STABLE FreeBSD 3.4-STABLE #0: Fri Dec 17 08:49:51 EST 1999 > Tom --ELM946311914-74626-0_ Content-Type: TEXT/PLAIN; CHARSET=KOI8-R Content-ID: Content-Description: Automaticly generated by the port Content-Disposition: ATTACHMENT; FILENAME="Makefile.inc" PKGNAME= apache+php+mod_ssl-${VERSION_APACHE}+${VERSION_PHP}+${VERSION_MODSSL} DISTFILES+= mod_ssl-${VERSION_MODSSL}-${VERSION_APACHE}${EXTRACT_SUFX} BUILD_DEPENDS+= openssl:${PORTSDIR}/security/openssl \ mm-config:${PORTSDIR}/devel/mm \ ${PREFIX}/lib/libmm.a:${PORTSDIR}/devel/mm LIB_DEPENDS+= crypto.1:${PORTSDIR}/security/openssl \ ssl.1:${PORTSDIR}/security/openssl RUN_DEPENDS+= openssl:${PORTSDIR}/security/openssl VERSION_MODSSL= 2.4.9 RESTRICTED= "Contains cryptography" CONFIGURE_ARGS+=--enable-module=ssl \ --enable-module=define CONFIGURE_ENV+= SSL_BASE='SYSTEM' EAPI_MM='SYSTEM' PATH="${PREFIX}/bin:${PATH}" PLIST= ${PKGDIR}/PLIST.modssl SSL= ssl TYPE= test CRT= KEY= pre-patch: @cd ${WRKDIR}/mod_ssl-${VERSION_MODSSL}-${VERSION_APACHE} \ && ${ECHO_MSG} "===> Applying mod_ssl-${VERSION_MODSSL} extension" \ && ./configure --with-apache=../${DISTNAME} --expert post-patch: @cd ${WRKSRC} \ && find . -type f -name "*.orig" -print | xargs ${RM} -f post-build: @cd ${WRKSRC} \ && ${ECHO_MSG} "===> Creating Dummy Certificate for Server (SnakeOil)" \ && ${ECHO_MSG} " [use 'make certificate' to create a real one]" \ && ${MAKE} certificate TYPE=dummy >/dev/null 2>&1 certificate: @cd ${WRKSRC} \ && ${ECHO_MSG} "===> Creating Test Certificate for Server" \ && ${MAKE} certificate TYPE=$(TYPE) CRT=$(CRT) KEY=$(KEY) BUILD_DEPENDS+= ${PREFIX}/lib/libgd.a:${PORTSDIR}/graphics/gd PHP_CONF_ARGS+= --with-gd=${PREFIX} LIB_DEPENDS+= ttf.4:${PORTSDIR}/print/freetype PHP_CONF_ARGS+= --with-ttf=${PREFIX} PHP_CONF_ARGS+= --with-zlib LIB_DEPENDS+= mcrypt.2:${PORTSDIR}/security/libmcrypt PHP_CONF_ARGS+= --with-mcrypt=${PREFIX} LIB_DEPENDS+= mhash.1:${PORTSDIR}/security/mhash PHP_CONF_ARGS+= --with-mhash=${PREFIX} BUILD_DEPENDS+= ${PREFIX}/lib/libc-client4.a:${PORTSDIR}/mail/imap-uw PHP_CONF_ARGS+= --with-imap=${PREFIX} LIB_DEPENDS+= mysqlclient.6:${PORTSDIR}/databases/mysql322-client PHP_CONF_ARGS+= --with-mysql=${PREFIX} BUILD_DEPENDS+= ${PREFIX}/lib/libexpat.a:${PORTSDIR}/textproc/expat BUILD_DEPENDS+= ${PREFIX}/include/xml/xmlparse.h:${PORTSDIR}/textproc/expat BUILD_DEPENDS+= ${PREFIX}/include/xml/xmltok.h:${PORTSDIR}/textproc/expat PHP_CONF_ARGS+= --with-xml=${PREFIX} --ELM946311914-74626-0_-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 27 10:32:17 1999 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 E7B361505F; Mon, 27 Dec 1999 10:31:54 -0800 (PST) (envelope-from pfeifer@dbai.tuwien.ac.at) Received: from [128.130.111.10] (nunki [128.130.111.10]) by vexpert.dbai.tuwien.ac.at (8.9.1/8.9.1) with ESMTP id TAA21590; Mon, 27 Dec 1999 19:31:40 +0100 (MET) Date: Mon, 27 Dec 1999 19:31:40 +0100 (MET) From: Gerald Pfeifer To: Mike s Cc: freebsd-stable@freebsd.org, freebsd-doc@freebsd.org Subject: Re: FreeBSD Portal In-Reply-To: <19991227004005.25908.qmail@web503.mail.yahoo.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 26 Dec 1999, Mike s wrote: > I have a lot of documentation that is done already, ( alot being 35% ) > the site is very appealing for those that use netscape and the like > and is also lynx friendly. Great! > before launching the alpha site it will include: > > [long list] Mike, this is very cool and useful stuff, but I am really worried that this will bring us two sites with a lot of duplicate information on the one hand and incomplete information on each of these sites on the other hand. As a FreeBSD user/admin, I'd really prefer to have *one* site with technical information of that kind. That is, if the question is "Doing nothing for FreeBSD versus building a site of your one" my answer is "Go ahead!", but I'd really, really prefer seeing your work merged with www.freebsd.org. 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 Dec 27 10:49:35 1999 Delivered-To: freebsd-stable@freebsd.org Received: from typhoon.mail.pipex.net (typhoon.mail.pipex.net [158.43.128.27]) by hub.freebsd.org (Postfix) with SMTP id C75DD15016 for ; Mon, 27 Dec 1999 10:49:11 -0800 (PST) (envelope-from mark@dogma.freebsd-uk.eu.org) Received: (qmail 28472 invoked from network); 27 Dec 1999 18:40:42 -0000 Received: from userao19.uk.uudial.com (HELO marder-1.) (62.188.135.135) by smtp.dial.pipex.com with SMTP; 27 Dec 1999 18:40:42 -0000 Received: (from mark@localhost) by marder-1. (8.9.3/8.9.3) id SAA87264; Mon, 27 Dec 1999 18:41:00 GMT (envelope-from mark) Date: Mon, 27 Dec 1999 18:41:00 +0000 From: Mark Ovens To: robmel@nadt.org.uk, stable@freebsd.org Subject: Re: CVSup woes Message-ID: <19991227184100.H1290@marder-1> References: <199912271802.KAA02871@vashon.polstra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <199912271802.KAA02871@vashon.polstra.com> Organization: Total lack of Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Dec 27, 1999 at 10:02:15AM -0800, John Polstra wrote: > In article , > Robin Melville wrote: > > Hi All, > > > > Am I alone in having a hell of a time cvsup-ing 3.4? I'm using the > > exact same supfile as ever, but it crawls (on whatever server I try) > > then finally dies with "TreeList failed: Network write failure: > > Connection timed out" at anything up to one hour after starting. > > I haven't seen any problems like this under 3.4. Have you tried > some other mirror sites? There are only about 50 of them to choose > from. :-) > Since you're in the UK try *default host=cvsup.uk.FreeBSD.org in your sup-file I get excellent d/l speeds from there (some of the US servers are painfully slow from the UK, unless you pick a time when everyone's asleep over The Pond). > John > -- > John Polstra jdp@polstra.com > John D. Polstra & Co., Inc. Seattle, Washington USA > "No matter how cynical I get, I just can't keep up." -- Nora Ephron > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- "there's a long-standing bug relating to the x86 architecture that allows you to install Windows too" -Matthew D. Fuller ________________________________________________________________ FreeBSD - The Power To Serve http://www.freebsd.org My Webpage http://ukug.uk.freebsd.org/~mark/ mailto:mark@ukug.uk.freebsd.org http://www.radan.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 27 10:53: 6 1999 Delivered-To: freebsd-stable@freebsd.org Received: from kot.ne.mediaone.net (kot.ne.mediaone.net [24.218.15.190]) by hub.freebsd.org (Postfix) with ESMTP id A22831529B; Mon, 27 Dec 1999 10:53:00 -0800 (PST) (envelope-from mi@kot.ne.mediaone.net) Received: from rtfm.newton (rtfm.newton [10.10.0.1]) by kot.ne.mediaone.net (8.9.3/8.9.1) with ESMTP id NAA54304; Mon, 27 Dec 1999 13:52:59 -0500 (EST) From: Mikhail Teterin X-Relay-IP: 10.10.0.1 Received: (from mi@localhost) by rtfm.newton (8.9.3/8.9.3) id NAA75978; Mon, 27 Dec 1999 13:52:59 -0500 (EST) (envelope-from mi@kot.ne.mediaone.net) Message-Id: <199912271852.NAA75978@rtfm.newton> Subject: Re: -lc vs. -lc_r (building Apache-PHP) In-Reply-To: from Tom at "Dec 27, 1999 10:31:44 am" To: stable@freebsd.org, ports@freebsd.org Date: Mon, 27 Dec 1999 13:52:59 -0500 (EST) X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli" What's the magic and why doesn't the port know it? Why is -lc even in => play if some of the components (-lmysqlclient) require -lc_r? Yours, = = libmysqlclient does not require -lc_r, because the library does not =use threads. Only mysqld is threaded. Thank you, Tom, for this correction. However, this does not change much. Some other extension wants threads then... The two different problems are: . it is possible to mix the -lc_r and -lc without specifying either one explicitly . the Apache port may still fail to build a usable executable because of this Yours, -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 27 11: 1:14 1999 Delivered-To: freebsd-stable@freebsd.org Received: from corinth.bossig.com (corinth.bossig.com [208.26.239.66]) by hub.freebsd.org (Postfix) with ESMTP id A33DC154DF for ; Mon, 27 Dec 1999 11:01:10 -0800 (PST) (envelope-from kstewart@3-cities.com) Received: from 3-cities.com (kenn2192.bossig.com [208.26.242.192]) by corinth.bossig.com (Rockliffe SMTPRA 3.4.5) with ESMTP id ; Mon, 27 Dec 1999 11:08:09 -0800 Message-ID: <3867B764.23A59226@3-cities.com> Date: Mon, 27 Dec 1999 11:00:52 -0800 From: Kent Stewart Organization: Columbia Basin Virtual Community Project X-Mailer: Mozilla 4.7 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: Robin Melville Cc: freebsd-stable@freebsd.org Subject: Re: CVSup woes References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Robin Melville wrote: > > Hi All, > > Am I alone in having a hell of a time cvsup-ing 3.4? I'm using the > exact same supfile as ever, but it crawls (on whatever server I try) > then finally dies with "TreeList failed: Network write failure: > Connection timed out" at anything up to one hour after starting. > > This is cvsup client REL_16_0 over userland ppp on a 56k modem line with: > > *default host=cvsup.uk.FreeBSD.org > *default base=/usr > *default prefix=/usr > *default release=cvs tag=RELENG_3 > *default delete use-rel-suffix > *default compress > src-all > > I'm hoping that it's because the entire world has abandoned their > seasonal holidays in order to download FreeBSD. However, it's > possible something is going wrong. I'm running 3.4-Stable and cvsup ran in 3.5 minutes on a 56kb line. Only a dozen files or so were updated. Kent > > Best wishes for the new year! > > Robin. > > ---------------------------------------------------------------------- > Robin Melville, Addiction Information Service > Nottingham Alcohol & Drug Team > Tel: +44 (0)115 952 9478 Fax: +44 (0)115 952 9421 > work: robmel@nadt.org.uk > Pages: http://www.nadt.org.uk/ > ---------------------------------------------------------------------- > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- Kent Stewart Richland, WA mailto:kstewart@3-cities.com http://www.3-cities.com/~kstewart/index.html FreeBSD News http://daily.daemonnews.org/ SETI(Search for Extraterrestrial Intelligence) @ HOME http://setiathome.ssl.berkeley.edu/ Hunting Archibald Stewart, b 1802 in Ballymena, Antrim Co., NIR http://www.3-cities.com/~kstewart/genealogy/archibald_stewart.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 27 11:10:45 1999 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 1F91615304 for ; Mon, 27 Dec 1999 11:10:38 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id KAA09126; Mon, 27 Dec 1999 10:42:38 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id KAA03105; Mon, 27 Dec 1999 10:42:38 -0800 (PST) (envelope-from jdp@polstra.com) Date: Mon, 27 Dec 1999 10:42:38 -0800 (PST) Message-Id: <199912271842.KAA03105@vashon.polstra.com> To: jedgar@fxp.org Subject: Re: Huge differences in suid programs ? In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Cc: stable@freebsd.org Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > That's right, but it's more in the spirit of the make infrastructure > > to set COPY = -C and leave INSTALL alone. > > > > Makes sense. I was just going by the examples in > /etc{/defaults}/make.conf. If COPY is more correct, should > /etc{/defaults}/make.conf be changed? Yes, I think so. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "No matter how cynical I get, I just can't keep up." -- Nora Ephron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 27 11:17:13 1999 Delivered-To: freebsd-stable@freebsd.org Received: from ktpk.dp.ua (ktpk.dp.ua [195.24.130.245]) by hub.freebsd.org (Postfix) with ESMTP id 31659152A6; Mon, 27 Dec 1999 11:16:10 -0800 (PST) (envelope-from os@altavista.net) Received: from os (os.en.zp.ua [195.24.151.18]) by ktpk.dp.ua (8.8.8/8.8.8) with SMTP id VAA26722; Mon, 27 Dec 1999 21:09:41 +0200 (EET) (envelope-from os@altavista.net) Message-ID: <001b01bf509e$020685e0$129718c3@en.zp.ua> From: "Oleg Semyonov" To: "hometeam" Cc: , , References: Subject: Re: patches for pppd-2.3.10-radius are here Date: Mon, 27 Dec 1999 21:09:44 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Have the patches fixed the config file for ppp-2.3.10 ? It is still only > looking for 3.0 or 3.1 version of freebsd. Or 3.2 or 3.3 after the patch. At the time I wrote that latest FreeBSD 3.x was 3.3. > 2.3.10 will not compile on 3.4 stable . I just compiled pppd on 3.4 system after the change: $ diff configure.33 configure 56c56 < 3.[0-3]*) state="known"; ksrc="freebsd-3.0";; --- > 3.[0-4]*) state="known"; ksrc="freebsd-3.0";; Can't test but I think it may be compiled also on 4.x if you add another line here for 4.* (ksrc still must point to freebsd-3.0). OS PS. Confirm or reject it. If you have another problem - write me, please. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 27 11:37:59 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail2.uniserve.com (mail2.uniserve.com [204.244.156.7]) by hub.freebsd.org (Postfix) with ESMTP id 76DE3152EF; Mon, 27 Dec 1999 11:37:48 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca ([204.244.186.218]) by mail2.uniserve.com with smtp (Exim 3.03 #4) id 122fxg-000CGE-00; Mon, 27 Dec 1999 11:37:44 -0800 Date: Mon, 27 Dec 1999 11:37:41 -0800 (PST) From: Tom X-Sender: tom@shell.uniserve.ca To: Mikhail Teterin Cc: stable@freebsd.org, ports@freebsd.org Subject: Re: -lc vs. -lc_r (building Apache-PHP) In-Reply-To: <199912271852.NAA75978@rtfm.newton> 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, 27 Dec 1999, Mikhail Teterin wrote: > Tom once stated: > > =On Mon, 27 Dec 1999, Mikhail Teterin wrote: > = > =... > => What's the magic and why doesn't the port know it? Why is -lc even in > => play if some of the components (-lmysqlclient) require -lc_r? Yours, > = > = libmysqlclient does not require -lc_r, because the library does not > =use threads. Only mysqld is threaded. > > Thank you, Tom, for this correction. However, this does not change much. > Some other extension wants threads then... Uhh.. highly unlikely. Almost none of PHP3 is thread-safe, and only a bit of Apache is thread-safe. I doubt that anything in the Apache-PHP port wants or needs threads. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 27 11:42:22 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mailgw1.netvision.net.il (mailgw1.netvision.net.il [194.90.1.14]) by hub.freebsd.org (Postfix) with ESMTP id 249CF15444 for ; Mon, 27 Dec 1999 11:42:12 -0800 (PST) (envelope-from ak@freenet.co.uk) Received: from freenet.co.uk (RAS1-p58.rlz.netvision.net.il [62.0.168.60]) by mailgw1.netvision.net.il (8.9.3/8.9.3) with ESMTP id VAA24104; Mon, 27 Dec 1999 21:38:03 +0200 (IST) Message-ID: <3867C05F.60E5AAD1@freenet.co.uk> Date: Mon, 27 Dec 1999 19:39:11 +0000 From: Alex X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Mark Ovens Cc: robmel@nadt.org.uk, stable@freebsd.org Subject: Re: CVSup woes References: <199912271802.KAA02871@vashon.polstra.com> <19991227184100.H1290@marder-1> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mark Ovens wrote: > > > I haven't seen any problems like this under 3.4. Have you tried > > some other mirror sites? There are only about 50 of them to choose > > from. :-) > > > > Since you're in the UK try > > *default host=cvsup.uk.FreeBSD.org Yeah, it used to be Imperial College London, but now Easynet seems to be taking over the world... (running FreeBSD mostly BTW). They have a pretty damn fast link to NY, so I wouldn't be surprised if it was faster even for some people in the US. Alex > > in your sup-file > > I get excellent d/l speeds from there (some of the US servers are > painfully slow from the UK, unless you pick a time when everyone's > asleep over The Pond). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 27 11:43:15 1999 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 2EF8514CF1; Mon, 27 Dec 1999 11:42:55 -0800 (PST) (envelope-from nik@nothing-going-on.demon.co.uk) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.9.3/8.9.3) id TAA85139; Mon, 27 Dec 1999 19:40:03 GMT (envelope-from nik) Date: Mon, 27 Dec 1999 19:40:03 +0000 From: Nik Clayton To: Mike s Cc: freebsd-stable@freebsd.org, freebsd-doc@freebsd.org Subject: Re: FreeBSD Portal Message-ID: <19991227194003.D80910@catkin.nothing-going-on.org> References: <19991227004005.25908.qmail@web503.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <19991227004005.25908.qmail@web503.mail.yahoo.com>; from Mike s on Sun, Dec 26, 1999 at 04:40:05PM -0800 Organization: FreeBSD Project Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike, On Sun, Dec 26, 1999 at 04:40:05PM -0800, Mike s wrote: > Well, i have already taking the iniative in starting > what it is i have been talking about. That's great. It gives people a chance to see what you have in mind. Actions speak a lot louder than words. > I have a lot of documentation that is done already, ( > alot being 35% ) > the site is very appealing for those that use netscape > and the like and is also > lynx friendly. Also good. I'd be interested in you collaborating with the rest of the doc team to try and get this in to the 'mainstream' site as well. > I have already coded alot of user/interactive parts of > the site in php. This is (sort of) the problem. PHP (or Zope, or Zend, or lots complicated CGI scripts) are great when you only have one site. And one language. And only a few people working on it. As soon as you start using something less mainstream, you start to reduce the number of people who can work on it, and, more importantly, you increase the effort required to mirror it (and, quite possibly, to translate it). If you look at the FreeBSD site as it is at the moment, you'll see it's mirrored in sixty countries, and translated in to five languages. That's possible because the site's infrastructure is relatively basic. The mirrors don't need to worry about setting up a complex webserver, all they need is basic CGI functionality, and the translation teams just need to be familiar with HTML, there's nothing extra they need to learn. This keeps the effort requirement down, and increases the chance that people will participate. Looking at your list of proposed content; > before launching the alpha site it will include: > > -a step by step installation process focused on the > novice. > -troubleshooting > -basic networking support > -getting Connected to the internet > -all man pages marked outdated/up to date > -using CVSup and make world > -security related support > -what services need to be running for specific server > purposes > -performance optimization > -understanding log files > -understanding /etc/*.conf files for the novice > -most common asked questions with simple solutions ( > Not FAQ's ) > -FreeBSD command reference. > -UID's and GID's file permissions > -introduction to firewalls. > -mailing list archives which users will be able to > send and recieve via the web With the exception of the mailing list archives, there's nothing there that can't be done with the FreeBSD site as it is, and; > the beauty of the site is that user can submit > comments to the documentation > also add documentation to the subject in mind that > will be pre-formatted > to the site once submitted and at the bottom of the > page will be links to all > the comments and addition documentation. That's a nice idea. I'd be interested in something like this for the FreeBSD site that automatically included a link to the outstanding PRs for a piece of documentation. However, your approach won't scale to new languages, or to mirror sites, without a lot of effort, and it's issues like these that we have to consider for the main FreeBSD site. Also, consider how the user will be able to get their documentation. Will it only be available from your site? A lot of people have dial up connections, and won't want to recheck a new site each week on the off chance that some comments have been added to a document. How will they be able to keep local copies of your documentation? Will they be able to download Postscript or PDF versions for pretty printing. Or even suitable for installing in to a Palm Pilot[1]. I'm not trying to be negative -- I deeply appreciate that you want to help, and that you're prepared to put the time in to doing some work on what you see as being problems. N [1] OK, I only got this working a few weeks ago, but it's still a very nice feature :-) -- If you want to imagine the future, imagine a tennis shoe stamping on a penguin's face forever. --- with apologies to George Orwell To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 27 11:48:49 1999 Delivered-To: freebsd-stable@freebsd.org Received: from alpha.netvision.net.il (alpha.netvision.net.il [194.90.1.13]) by hub.freebsd.org (Postfix) with ESMTP id 6C8F8152FF for ; Mon, 27 Dec 1999 11:48:35 -0800 (PST) (envelope-from ak@freenet.co.uk) Received: from freenet.co.uk (RAS1-p58.rlz.netvision.net.il [62.0.168.60]) by alpha.netvision.net.il (8.9.3/8.8.6) with ESMTP id VAA07327; Mon, 27 Dec 1999 21:48:20 +0200 (IST) Message-ID: <3867C2C8.994BDE98@freenet.co.uk> Date: Mon, 27 Dec 1999 19:49:28 +0000 From: Alex X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: "Steve O'Hara-Smith" Cc: Mamoru Iwaki , freebsd-stable@FreeBSD.ORG Subject: Re: linux emulation on 3.4-stable References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Steve O'Hara-Smith wrote: > > On 27-Dec-99 Mamoru Iwaki wrote: > > Hi, > > > > I met warnings like > > > > LINUX: 'ioctl' fd=9, typ=0x44d(M), num=0x76 not implemented > > LINUX: 'ioctl' fd=7, typ=0x44d(M), num=0x76 not implemented > > > > when realplay was running. The program is an alpha 2 release of > > RealPlayer G2 for Linux 2.0/2.2 and we can get from > > http://www.real.com/products/player/linux.html > > Did the RealPlayer G2 work ? > > A few unimplemented messages do not necessarily prevent linux apps from > running (I have no idea what these ones do BTW). Nor are they necessarily a bug > or problem sometimes they simply reflect things required in Linux and not in > FreeBSD. > > > Please implement these ioctl's. > > I suspect that this will only happen if/when > > i) They are needed (to make something work). > > ii) Somebody implements them. It's the OSS_GETVERSION ioctl, and it was implemented in -current 6 months ago. The version can now be changed through the sysctl variable compat.linux.oss_version. See PR/12917. Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 27 11:51:23 1999 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 64C0714F5B for ; Mon, 27 Dec 1999 11:51:15 -0800 (PST) (envelope-from voland@plab.ku.dk) Received: from eagle.plab.ku.dk (voland@eagle.plab.ku.dk [130.225.105.63]) by plab.ku.dk (8.9.3/8.9.3) with ESMTP id UAA06504; Mon, 27 Dec 1999 20:52:23 +0100 (CET) (envelope-from voland@plab.ku.dk) Received: (from voland@localhost) by eagle.plab.ku.dk (8.9.3/8.9.3) id UAA59372; Mon, 27 Dec 1999 20:50:52 +0100 (CET) (envelope-from voland) Mime-version: 1.0 Content-type: text/plain; charset="koi8-r" Content-transfer-encoding: 8bit X-Comment-To: John Polstra To: John Polstra Cc: jedgar@fxp.org, stable@FreeBSD.ORG Subject: Re: Huge differences in suid programs ? References: <199912271842.KAA03105@vashon.polstra.com> From: Vadim Belman In-Reply-To: John Polstra's message of "Mon, 27 Dec 1999 10:42:38 -0800 (PST)" Date: 27 Dec 1999 20:50:52 +0100 Message-ID: <857li0go2r.fsf@eagle.plab.ku.dk> Lines: 14 X-Mailer: Gnus v5.7/Emacs 20.4 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi John! On 27 Dec 99 at 19:42, "John" (John Polstra) wrote: >> Makes sense. I was just going by the examples in >> /etc{/defaults}/make.conf. If COPY is more correct, should >> /etc{/defaults}/make.conf be changed? John> Yes, I think so. Wouldn't it slow down the installworld? -- /Voland Vadim Belman E-mail: voland@plab.ku.dk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 27 11:52:41 1999 Delivered-To: freebsd-stable@freebsd.org Received: from techpower.net (techpower.net [205.133.231.1]) by hub.freebsd.org (Postfix) with ESMTP id 6886515511; Mon, 27 Dec 1999 11:52:28 -0800 (PST) (envelope-from hometeam@techpower.net) Received: from localhost (hometeam@localhost) by techpower.net (8.9.3/8.9.3) with ESMTP id OAA01985; Mon, 27 Dec 1999 14:56:13 GMT (envelope-from hometeam@techpower.net) Date: Mon, 27 Dec 1999 14:56:13 +0000 (GMT) From: hometeam To: Oleg Semyonov Cc: freebsd-questions@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: patches for pppd-2.3.10-radius are here In-Reply-To: <001b01bf509e$020685e0$129718c3@en.zp.ua> 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 Yes I still had to manual change the config for 3.4, though it fixed the unbalanced #endif in sys-bsd.c . Before your patch 2.3.10 wouldn't compile on 3.4 by removing the #endif it compiled and manual change on configure then it worked just didn't log users on the server.. I guess we could just add this to 2.3.11 and be upto date with pppd finally... Been hoping for this ....:) On Mon, 27 Dec 1999, Oleg Semyonov wrote: > > Have the patches fixed the config file for ppp-2.3.10 ? It is still only > > looking for 3.0 or 3.1 version of freebsd. > > Or 3.2 or 3.3 after the patch. > At the time I wrote that latest FreeBSD 3.x was 3.3. > > > 2.3.10 will not compile on 3.4 stable . > > I just compiled pppd on 3.4 system after the change: > > $ diff configure.33 configure > 56c56 > < 3.[0-3]*) state="known"; ksrc="freebsd-3.0";; > --- > > 3.[0-4]*) state="known"; ksrc="freebsd-3.0";; > > Can't test but I think it may be compiled also on 4.x if you > add another line here for 4.* (ksrc still must point to freebsd-3.0). > > OS > > PS. Confirm or reject it. If you have another problem - write me, please. > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 27 11:54:32 1999 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 1C9971550E for ; Mon, 27 Dec 1999 11:54:25 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id LAA09418; Mon, 27 Dec 1999 11:54:21 -0800 (PST) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id LAA03436; Mon, 27 Dec 1999 11:54:20 -0800 (PST) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <857li0go2r.fsf@eagle.plab.ku.dk> Date: Mon, 27 Dec 1999 11:54:20 -0800 (PST) Organization: Polstra & Co., Inc. From: John Polstra To: Vadim Belman Subject: Re: Huge differences in suid programs ? Cc: stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Vadim Belman wrote: > >> Makes sense. I was just going by the examples in > >> /etc{/defaults}/make.conf. If COPY is more correct, should > >> /etc{/defaults}/make.conf be changed? > > John> Yes, I think so. > > Wouldn't it slow down the installworld? No, it wouldn't change anything because the line in make.conf is just a comment. :-) John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 27 12:30:29 1999 Delivered-To: freebsd-stable@freebsd.org Received: from kot.ne.mediaone.net (kot.ne.mediaone.net [24.218.15.190]) by hub.freebsd.org (Postfix) with ESMTP id A1A6F14CF4; Mon, 27 Dec 1999 12:30:14 -0800 (PST) (envelope-from mi@kot.ne.mediaone.net) Received: from rtfm.newton (rtfm.newton [10.10.0.1]) by kot.ne.mediaone.net (8.9.3/8.9.1) with ESMTP id PAA54625; Mon, 27 Dec 1999 15:30:09 -0500 (EST) From: Mikhail Teterin X-Relay-IP: 10.10.0.1 Received: (from mi@localhost) by rtfm.newton (8.9.3/8.9.3) id PAA76727; Mon, 27 Dec 1999 15:30:08 -0500 (EST) (envelope-from mi@kot.ne.mediaone.net) Message-Id: <199912272030.PAA76727@rtfm.newton> Subject: Re: -lc vs. -lc_r (building Apache-PHP) In-Reply-To: from Tom at "Dec 27, 1999 11:37:41 am" To: stable@freebsd.org, ports@freebsd.org Date: Mon, 27 Dec 1999 15:30:08 -0500 (EST) X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli" => What's the magic and why doesn't the port know it? Why is -lc even => => in play if some of the components (-lmysqlclient) require -lc_r? => => Yours, => = => = libmysqlclient does not require -lc_r, because the library does => =not use threads. Only mysqld is threaded. => => Thank you, Tom, for this correction. However, this does not change => much. Some other extension wants threads then... = = Uhh.. highly unlikely. Almost none of PHP3 is thread-safe, and only a =bit of Apache is thread-safe. I doubt that anything in the Apache-PHP =port wants or needs threads. I did not put it in there myself :) At least one of the many extensions selected (I included the Makefile.inc with my original report) dragged the c_r with it... -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 27 12:52:56 1999 Delivered-To: freebsd-stable@freebsd.org Received: from tantivy.stanford.edu (tantivy.Stanford.EDU [171.64.234.70]) by hub.freebsd.org (Postfix) with ESMTP id B6496152DC for ; Mon, 27 Dec 1999 12:52:48 -0800 (PST) (envelope-from techie@tantivy.stanford.edu) Received: (from techie@localhost) by tantivy.stanford.edu (8.9.3/8.9.1) id MAA19956; Mon, 27 Dec 1999 12:50:31 -0800 (PST) Date: Mon, 27 Dec 1999 12:50:31 -0800 (PST) From: Bob Vaughan Message-Id: <199912272050.MAA19956@tantivy.stanford.edu> To: mark@dogma.freebsd-uk.eu.org Subject: Re: CVSup woes Cc: freebsd-stable@freebsd.org In-Reply-To: <19991227184100.H1290@marder-1> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Err.. did you read the original message? You wrote: > > Since you're in the UK try > > *default host=cvsup.uk.FreeBSD.org > > in your sup-file > > I get excellent d/l speeds from there (some of the US servers are > painfully slow from the UK, unless you pick a time when everyone's > asleep over The Pond). > Robin Melville wrote: > > Hi All, > > Am I alone in having a hell of a time cvsup-ing 3.4? I'm using the > exact same supfile as ever, but it crawls (on whatever server I try) > then finally dies with "TreeList failed: Network write failure: > Connection timed out" at anything up to one hour after starting. > > This is cvsup client REL_16_0 over userland ppp on a 56k modem line with: > > *default host=cvsup.uk.FreeBSD.org > *default base=/usr > *default prefix=/usr > *default release=cvs tag=RELENG_3 > *default delete use-rel-suffix > *default compress > src-all > > I'm hoping that it's because the entire world has abandoned their > seasonal holidays in order to download FreeBSD. However, it's > possible something is going wrong. -- Welcome My Son, Welcome To The Machine -- Bob Vaughan | techie@{w6yx|tantivy}.stanford.edu | kc6sxc@w6yx.ampr.org | P.O. Box 19792, Stanford, Ca 94309 -- I am Me, I am only Me, And no one else is Me, What could be simpler? -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 27 13:27:46 1999 Delivered-To: freebsd-stable@freebsd.org Received: from saturn.terahertz.net (saturn.terahertz.net [209.83.5.170]) by hub.freebsd.org (Postfix) with ESMTP id 4978514D7F for ; Mon, 27 Dec 1999 13:27:40 -0800 (PST) (envelope-from mustang@TeraHertz.Net) Received: from localhost (mustang@localhost) by saturn.terahertz.net (8.9.3/8.9.3) with ESMTP id PAA80041 for ; Mon, 27 Dec 1999 15:27:07 -0600 (CST) Date: Mon, 27 Dec 1999 15:27:07 -0600 (CST) From: Chris Malayter To: stable@FreeBSD.ORG Subject: Re: -lc vs. -lc_r (building Apache-PHP) In-Reply-To: <199912272030.PAA76727@rtfm.newton> 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 Along this line of problems, I am having serious problems compileing a usable apache binary when compileing modphp with IMAP support. It works fine for me when I just compile any other service or combination of services. Here's the error: Configuring for Apache, Version 1.3.9 + using installation path layout: Apache (config.layout) + activated php3 module (modules/php3/libphp3.a) Creating Makefile Creating Configuration.apaci in src Creating Makefile in src + configured for FreeBSD 3.4 platform + setting C compiler to gcc + setting C pre-processor to gcc -E + checking for system header files + adding selected modules o php3_module uses ConfigStart/End + checking sizeof various data types + doing sanity check on compiler and options ** A test compilation with your Makefile configuration ** failed. This is most likely because your C compiler ** is not ANSI. Apache requires an ANSI C Compiler, such ** as gcc. The above error message from your compiler ** will also provide a clue. Aborting! venus# Here's my uname: FreeBSD venus.terahertz.net 3.4-STABLE FreeBSD 3.4-STABLE #3: Mon Dec 27 08:34:56 CST 1999 mustang@venus.terahertz.net:/usr/src/sys/compile/VENUS i386 I tried doing this under 3.3-RELEASE and had the same error from apache. I have tried upgrading my IMAP libs, with no luck. I have tried downgrading apache, and php, and get the same result. Has anyone else experienced this? Chris Malayter Mustang@TeraHertz.Net Administrator, TeraHertz Communications To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 27 13:49:28 1999 Delivered-To: freebsd-stable@freebsd.org Received: from paprika.michvhf.com (paprika.michvhf.com [209.57.60.12]) by hub.freebsd.org (Postfix) with SMTP id C7B8B153D2 for ; Mon, 27 Dec 1999 13:49:15 -0800 (PST) (envelope-from vev@michvhf.com) Received: (qmail 11189 invoked by uid 1001); 27 Dec 1999 21:49:17 -0000 Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Mon, 27 Dec 1999 16:49:17 -0500 (EST) X-Face: *0^4Iw) To: Chris Malayter Subject: Re: -lc vs. -lc_r (building Apache-PHP) Cc: stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 27-Dec-99 Chris Malayter wrote: > Along this line of problems, > > I am having serious problems compileing a usable apache binary when > compileing modphp with IMAP support. It works fine for me when I just > compile any other service or combination of services. > > Here's the error: > > Configuring for Apache, Version 1.3.9 > + using installation path layout: Apache (config.layout) > + activated php3 module (modules/php3/libphp3.a) Creating Makefile > Creating Configuration.apaci in src Creating Makefile in src > + configured for FreeBSD 3.4 platform > + setting C compiler to gcc > + setting C pre-processor to gcc -E > + checking for system header files > + adding selected modules > o php3_module uses ConfigStart/End > + checking sizeof various data types > + doing sanity check on compiler and options ** A test compilation with > your Makefile configuration ** failed. This is most likely because your C > compiler ** is not ANSI. Apache requires an ANSI C Compiler, such ** as > gcc. The above error message from your compiler ** will also provide a > clue. > Aborting! > venus# Trying this again, hopefully that last one didn't go out (it was content free). I've seen this many times. Part of the problem is that apache's configure script won't pass --verbose to it's helper scripts which only leaves you clueless as to what's happening. If you go into the src directory and and run the following: $ ./helpers/TestCompile -v sanity you'll see the reason why it won't compile. 9 times out of 10 it's caused by a header file in the wrong place - or apache not knowing where it is. I don't recall what I did to fix it, but it was probably something like copying the file to a standard directory or creating a symlink. Vince. -- ========================================================================== Vince Vielhaber -- KA8CSH email: vev@michvhf.com http://www.pop4.net 128K ISDN: $24.95/mo or less - 56K Dialup: $17.95/mo or less at Pop4 Online Campground Directory http://www.camping-usa.com Online Giftshop Superstore http://www.cloudninegifts.com ========================================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 27 13:49:34 1999 Delivered-To: freebsd-stable@freebsd.org Received: from typhoon.mail.pipex.net (typhoon.mail.pipex.net [158.43.128.27]) by hub.freebsd.org (Postfix) with SMTP id DD9E8154D4 for ; Mon, 27 Dec 1999 13:49:29 -0800 (PST) (envelope-from mark@dogma.freebsd-uk.eu.org) Received: (qmail 8477 invoked from network); 27 Dec 1999 21:49:24 -0000 Received: from useran59.uk.uudial.com (HELO marder-1.) (62.188.135.76) by smtp.dial.pipex.com with SMTP; 27 Dec 1999 21:49:24 -0000 Received: (from mark@localhost) by marder-1. (8.9.3/8.9.3) id VAA88061; Mon, 27 Dec 1999 21:49:47 GMT (envelope-from mark) Date: Mon, 27 Dec 1999 21:49:47 +0000 From: Mark Ovens To: Bob Vaughan Cc: freebsd-stable@freebsd.org Subject: Re: CVSup woes Message-ID: <19991227214946.L1290@marder-1> References: <19991227184100.H1290@marder-1> <199912272050.MAA19956@tantivy.stanford.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <199912272050.MAA19956@tantivy.stanford.edu> Organization: Total lack of Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Dec 27, 1999 at 12:50:31PM -0800, Bob Vaughan wrote: > Err.. did you read the original message? > No, I didn't, but after posting my reply I saw the original quoted in another reply and realized my mistake. -- "there's a long-standing bug relating to the x86 architecture that allows you to install Windows too" -Matthew D. Fuller ________________________________________________________________ FreeBSD - The Power To Serve http://www.freebsd.org My Webpage http://ukug.uk.freebsd.org/~mark/ mailto:mark@ukug.uk.freebsd.org http://www.radan.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 27 13:54:31 1999 Delivered-To: freebsd-stable@freebsd.org Received: from kusanagi.boing.com (adsl-gte-la-216-86-200-115.mminternet.com [216.86.200.115]) by hub.freebsd.org (Postfix) with ESMTP id 82A7515442 for ; Mon, 27 Dec 1999 13:54:28 -0800 (PST) (envelope-from boing@boing.com) Received: from boing.com (localhost [127.0.0.1]) by kusanagi.boing.com (8.9.3/8.9.3) with ESMTP id NAA30879; Mon, 27 Dec 1999 13:54:30 -0800 (PST) (envelope-from boing@boing.com) Message-Id: <199912272154.NAA30879@kusanagi.boing.com> Date: Mon, 27 Dec 1999 13:54:29 -0800 (PST) From: Geff Hanoian Subject: Re: -lc vs. -lc_r (building Apache-PHP) To: vev@michvhf.com Cc: mustang@TeraHertz.Net, stable@FreeBSD.ORG, mustang@TeraHertz.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 I experienced this as well (just now in fact). Make sure that when you include imap that it's getting the archive library, not the shared library. For some reason there are symbols that are referenced by libc-client4.so that exist in libphp4.a (in my case I was installing 4). And the compiler doesn't seem to "like" to link them that way, I guess. But I'm sure I'll get flammed for being wrong real soon now. I'm just starting my stop watch. I don't completely understand the sitch, perhaps I needed an extra option on the compiler that I'm not aware of. Either way I fixed it temporarly and quickly by using the archive library. Geff On 27 Dec, Vince Vielhaber wrote: > > On 27-Dec-99 Chris Malayter wrote: >> Along this line of problems, >> >> I am having serious problems compileing a usable apache binary when >> compileing modphp with IMAP support. It works fine for me when I just >> compile any other service or combination of services. >> >> Here's the error: >> >> Configuring for Apache, Version 1.3.9 >> + using installation path layout: Apache (config.layout) >> + activated php3 module (modules/php3/libphp3.a) Creating Makefile >> Creating Configuration.apaci in src Creating Makefile in src >> + configured for FreeBSD 3.4 platform >> + setting C compiler to gcc >> + setting C pre-processor to gcc -E >> + checking for system header files >> + adding selected modules >> o php3_module uses ConfigStart/End >> + checking sizeof various data types >> + doing sanity check on compiler and options ** A test compilation with >> your Makefile configuration ** failed. This is most likely because your C >> compiler ** is not ANSI. Apache requires an ANSI C Compiler, such ** as >> gcc. The above error message from your compiler ** will also provide a >> clue. >> Aborting! >> venus# > > Trying this again, hopefully that last one didn't go out (it was content > free). > > I've seen this many times. Part of the problem is that apache's configure > script won't pass --verbose to it's helper scripts which only leaves you > clueless as to what's happening. > > If you go into the src directory and and run the following: > > $ ./helpers/TestCompile -v sanity > > you'll see the reason why it won't compile. 9 times out of 10 it's caused > by a header file in the wrong place - or apache not knowing where it is. > I don't recall what I did to fix it, but it was probably something like > copying the file to a standard directory or creating a symlink. > > Vince. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 27 14:16:24 1999 Delivered-To: freebsd-stable@freebsd.org Received: from devsys.jaguNET.com (devsys.jaguNET.com [206.156.208.6]) by hub.freebsd.org (Postfix) with ESMTP id 8B51A14A00 for ; Mon, 27 Dec 1999 14:16:18 -0800 (PST) (envelope-from jim@jaguNET.com) Received: (from jim@localhost) by devsys.jaguNET.com (8.9.3/jag-2.6) id RAA03398; Mon, 27 Dec 1999 17:16:08 -0500 (EST) From: Jim Jagielski Message-Id: <199912272216.RAA03398@devsys.jaguNET.com> Subject: Re: -lc vs. -lc_r (building Apache-PHP) To: mustang@TeraHertz.Net (Chris Malayter) Date: Mon, 27 Dec 1999 17:16:07 -0500 (EST) Cc: stable@FreeBSD.ORG Reply-To: jim@jaguNET.com In-Reply-To: from "Chris Malayter" at Dec 27, 1999 03:27:07 PM X-Mailer: ELM [version 2.5 PL2] 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 Chris Malayter wrote: > > Along this line of problems, > > I am having serious problems compileing a usable apache binary when > compileing modphp with IMAP support. It works fine for me when I just > compile any other service or combination of services. > > Here's the error: > > Configuring for Apache, Version 1.3.9 > + using installation path layout: Apache (config.layout) > + activated php3 module (modules/php3/libphp3.a) Creating Makefile > Creating Configuration.apaci in src Creating Makefile in src > + configured for FreeBSD 3.4 platform > + setting C compiler to gcc > + setting C pre-processor to gcc -E > + checking for system header files > + adding selected modules > o php3_module uses ConfigStart/End > + checking sizeof various data types > + doing sanity check on compiler and options ** A test compilation with > your Makefile configuration ** failed. This is most likely because your C > compiler ** is not ANSI. Apache requires an ANSI C Compiler, such ** as > gcc. The above error message from your compiler ** will also provide a > clue. > Aborting! > venus# > Just a FYI that I've "fixed" the latest CVS version of Apache (and it'll be in 1.3.10 when we release that around the first week of 2000) so that if the "test compile" fails, Configure no longer prints such a bogus message, but actually prints the error output of the compile :) -- =========================================================================== Jim Jagielski [|] jim@jaguNET.com [|] http://www.jaguNET.com/ "Are you suggesting coconuts migrate??" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 27 14:31:32 1999 Delivered-To: freebsd-stable@freebsd.org Received: from ktpk.dp.ua (ktpk.dp.ua [195.24.130.245]) by hub.freebsd.org (Postfix) with ESMTP id 6C05D14DB6; Mon, 27 Dec 1999 14:31:01 -0800 (PST) (envelope-from os@altavista.net) Received: from os (os.en.zp.ua [195.24.151.18]) by ktpk.dp.ua (8.8.8/8.8.8) with SMTP id AAA07496; Tue, 28 Dec 1999 00:30:31 +0200 (EET) (envelope-from os@altavista.net) Message-ID: <003d01bf50b9$fd8fe120$129718c3@en.zp.ua> From: "Oleg Semyonov" To: "hometeam" Cc: , , References: Subject: Re: patches for pppd-2.3.10-radius are here Date: Tue, 28 Dec 1999 00:30:31 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ----- Original Message ----- From: hometeam Sent: Monday, December 27, 1999 4:56 PM > Before your patch 2.3.10 wouldn't compile on 3.4 by removing the #endif > it compiled and manual change on configure then it worked just > didn't log users on the server.. Didn't make a records in utmp/wtmp. This and some number of other issues are fixed by patch. E.g. added check for account expiration, check for /etc/ppp/ppp.deny and ppp.shells, and other FreeBSD-specific stuff which is not required but useful. It all was merged from FreeBSD's pppd-2.3.5 into 2.3.10-radius. Particularly, some IPX stuff. I was not able to test all the magic, so simply move it from one version to another. Main goal was RADIUS for tcp/ip, PAP, dial-in, no callback. > I guess we could just add this to 2.3.11 and be upto date with > pppd finally... I have no time for this now. May be in 2.3.12? :-) AFAIK, there is no significant changes in 2.3.11 from 2.3.10. And I didn't received any feedback about the patches. All I've got was first impressions and not more. So there is no driving motive for me to do it now: 2.3.10 works fine. OS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 27 15:18:20 1999 Delivered-To: freebsd-stable@freebsd.org Received: from visionaire.ping.de (visionaire.ping.de [195.37.123.61]) by hub.freebsd.org (Postfix) with ESMTP id 3BFD814E56 for ; Mon, 27 Dec 1999 15:18:11 -0800 (PST) (envelope-from thomas@visionaire.ping.de) Received: from dante.visionaire.net (mail@dante.visionaire.net [192.168.208.42]) by visionaire.ping.de (8.9.3/8.9.3) with ESMTP id XAA32828; Mon, 27 Dec 1999 23:30:46 +0100 (CET) (envelope-from thomas@dante.visionaire.net) Received: from thomas by dante.visionaire.net with local (Exim 2.05 #1 (Debian)) id 122if8-00031q-00; Mon, 27 Dec 1999 23:30:46 +0100 Date: Mon, 27 Dec 1999 23:30:46 +0100 From: Thomas Keusch To: Vivek Khera Cc: US FreeBSD Stable Mailing List Subject: Re: some more files left from prev. install Message-ID: <19991227233045.A11598@dante.visionaire.net> References: <14439.42046.843833.513339@onceler.kcilink.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.0i In-Reply-To: <14439.42046.843833.513339@onceler.kcilink.com>; from khera@kciLink.com on Mon, Dec 27, 1999 at 12:39:10PM -0500 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Dec 27, 1999 at 12:39:10PM -0500, Vivek Khera wrote: > >>>>> "RS" == Roman Shterenzon writes: > > RS> Hello, > RS> I also noted /usr/bin/bdes and /usr/sbin/named-bootconf which are left > > /usr/bin/bdes was updated for me, however /usr/sbin/named-bootconf was > not updated for me, as well. Hmmm, I cvsupped on Xmas and build world tonight, and I've got a dozen or so files that did not get updated: darkstar:~ $ find {/usr,}/{s,}bin -mtime +2 -print0 | xargs -0 ls -l -r-xr-xr-x 1 root wheel 16912 May 18 1999 /usr/bin/kadmin -r-xr-xr-x 1 root wheel 13032 May 18 1999 /usr/bin/kauth -r-xr-xr-x 1 root wheel 3828 May 18 1999 /usr/bin/kdestroy -r-xr-xr-x 1 root wheel 6340 May 18 1999 /usr/bin/kinit -r-xr-xr-x 1 root wheel 7680 May 18 1999 /usr/bin/klist -r-xr-xr-x 1 root wheel 292 May 18 1999 /usr/bin/ksrvtgt lrwxr-xr-x 1 root wheel 23 Sep 4 13:05 /usr/bin/rnews -> ../local/news/bin/rnews -r-xr-xr-x 2 root wheel 3148 May 18 1999 /usr/sbin/alaw2ulaw -r-xr-xr-x 1 root wheel 5704 May 18 1999 /usr/sbin/ext_srvtab -r-xr-xr-x 1 root wheel 18392 May 18 1999 /usr/sbin/kadmind -r-xr-xr-x 1 root wheel 3924 May 18 1999 /usr/sbin/kdb_destroy -r-xr-xr-x 1 root wheel 8876 May 18 1999 /usr/sbin/kdb_edit -r-xr-xr-x 1 root wheel 6180 May 18 1999 /usr/sbin/kdb_init -r-xr-xr-x 1 root wheel 9860 May 18 1999 /usr/sbin/kdb_util -r-xr-xr-x 1 root wheel 14548 May 18 1999 /usr/sbin/kerberos -r-xr-xr-x 1 root wheel 6672 May 18 1999 /usr/sbin/kip -r-xr-xr-x 1 root wheel 10320 May 18 1999 /usr/sbin/kprop -r-xr-xr-x 1 root wheel 16504 May 18 1999 /usr/sbin/ksrvutil -r-xr-xr-x 1 root wheel 3952 May 18 1999 /usr/sbin/kstash -r-xr-xr-x 1 root wheel 8703 May 18 1999 /usr/sbin/named-bootconf -r-xr-xr-x 2 root wheel 3148 May 18 1999 /usr/sbin/ulaw2alaw darkstar:~ $ A lot of these files are named k*, is this all kerberos stuff? If it is all encryption/security stuff, why didn't it get updated? I did get the secure-collection stuff via cvsup, might it be because of "USA_RESIDENT=NO" in /etc/make.conf? -- thomas. .powered.by.debian/linux. .served.by.FreeBSD. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 27 16: 7: 4 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.nyct.net (bsd4.nyct.net [204.141.86.6]) by hub.freebsd.org (Postfix) with ESMTP id 7DE23152F3 for ; Mon, 27 Dec 1999 16:07:01 -0800 (PST) (envelope-from efutch@nyct.net) Received: from bsd1.nyct.net (efutch@bsd1.nyct.net [204.141.86.3]) by mail.nyct.net (8.8.8/8.8.7) with ESMTP id TAA27248 for ; Mon, 27 Dec 1999 19:07:00 -0500 (EST) (envelope-from efutch@nyct.net) Date: Mon, 27 Dec 1999 19:07:00 -0500 (EST) From: "Eric D. Futch" To: freebsd-stable@freebsd.org Subject: if_fxp.c 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 This is from -stable as of Wed Dec 22 01:48:17 EST 1999 ../../pci/if_fxp.c: In function `fxp_intr': ../../pci/if_fxp.c:1069: warning: label `getit' defined but not used ../../pci/if_fxp.c:1064: warning: label `dropit' defined but not used -- Eric Futch New York Connect.Net, Ltd. efutch@nyct.net Technical Support Staff http://www.nyct.net (212) 293-2620 "Bringing New York The Internet Access It Deserves" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 27 19:28:32 1999 Delivered-To: freebsd-stable@freebsd.org Received: from waltz.rahul.net (waltz.rahul.net [192.160.13.9]) by hub.freebsd.org (Postfix) with ESMTP id 648821537D for ; Mon, 27 Dec 1999 19:28:30 -0800 (PST) (envelope-from dhesi@rahul.net) Received: by waltz.rahul.net (Postfix, from userid 104) id 4006D24E; Mon, 27 Dec 1999 19:28:29 -0800 (PST) To: freebsd-stable@freebsd.org Subject: Re: bugs in the handbook. (FreeBSD Portal) Newsgroups: a2i.lists.freebsd-stable References: X-Newsreader: NN version 6.5.1 (NOV) Message-Id: <19991228032829.4006D24E@waltz.rahul.net> Date: Mon, 27 Dec 1999 19:28:29 -0800 (PST) From: dhesi@rahul.net (Rahul Dhesi) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Colin writes: >1) The peole who know enough about the system to document it properly >generally don't have the time (or inclination...gotta love those >programmers ;)) to spend on documentation. They're too busy fixing the >problems that turn up regularly or adding enhancements (which is where >most of the problems start ;)). It doesn't take very long to write quick documentation. It's polishing it that takes time. The developers have the time to write quick documentation, if they will embed in the source code in the form of structured comments. This can be then taken and polished by others. >2) The peole who are most willing to spend time on the documentation >don't have the specific knowledge to do it. They are the one's who >would like to be reading the docs. This is true. Notice how perl modules seem to be quite well documented? It's partly because the documentation is embedded in the source. When the maintainer updates the source, it's relatively easy to udpate the documentation at the same time...it's in the same file and the maintainer has (by embedding the documentation in the same file) implicitly accepted responsibility for keeping it updated. FreeBSD separates the documentation from the code. Thus somebody writing code has no explicit or implicit responsiblity for keeping the documentation updated. -- Rahul Dhesi See my UUNET spam mini-faq at: http://www.rahul.net/dhesi/uunet.faq.txt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 27 19:34:34 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.nyct.net (bsd4.nyct.net [204.141.86.6]) by hub.freebsd.org (Postfix) with ESMTP id 034C015325 for ; Mon, 27 Dec 1999 19:34:32 -0800 (PST) (envelope-from efutch@nyct.net) Received: from bsd1.nyct.net (efutch@bsd1.nyct.net [204.141.86.3]) by mail.nyct.net (8.8.8/8.8.7) with ESMTP id WAA24935 for ; Mon, 27 Dec 1999 22:34:32 -0500 (EST) (envelope-from efutch@nyct.net) Date: Mon, 27 Dec 1999 22:34:31 -0500 (EST) From: "Eric D. Futch" To: freebsd-stable@FreeBSD.ORG Subject: Re: if_fxp.c In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nevermind this... It was related to FreeBSD PAO which I can't get to compile. Please ignore :) I'll stop posting stuff and stick to listening :) -- Eric Futch New York Connect.Net, Ltd. efutch@nyct.net Technical Support Staff http://www.nyct.net (212) 293-2620 "Bringing New York The Internet Access It Deserves" On Mon, 27 Dec 1999, Eric D. Futch wrote: This is from -stable as of Wed Dec 22 01:48:17 EST 1999 ../../pci/if_fxp.c: In function `fxp_intr': ../../pci/if_fxp.c:1069: warning: label `getit' defined but not used ../../pci/if_fxp.c:1064: warning: label `dropit' defined but not used To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 27 20:15:22 1999 Delivered-To: freebsd-stable@freebsd.org Received: from web506.mail.yahoo.com (web506.mail.yahoo.com [128.11.68.73]) by hub.freebsd.org (Postfix) with SMTP id 9CA09153B3 for ; Mon, 27 Dec 1999 20:15:17 -0800 (PST) (envelope-from god@yahoo.com) Received: (qmail 23424 invoked by uid 60001); 28 Dec 1999 04:15:17 -0000 Message-ID: <19991228041517.23423.qmail@web506.mail.yahoo.com> Received: from [63.20.23.95] by web506.mail.yahoo.com; Mon, 27 Dec 1999 20:15:17 PST Date: Mon, 27 Dec 1999 20:15:17 -0800 (PST) From: Mike s Subject: re:freebsd.org To: stable@freebsd.org Cc: freebsd-docs@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 27 Dec 1999, Nik Clayton wrote: > Mike, > > On Sun, Dec 26, 1999 at 04:40:05PM -0800, Mike s >wrote: > > Well, i have already taking the iniative in >starting > > what it is i have been talking about. > > That's great. It gives people a chance to see what >you have in mind. > Actions speak a lot louder than words. I will have something to show within the next few weeks, i have something up already but i want to finish a bit more. > > > I have a lot of documentation that is done already, ( > > alot being 35% ) > > the site is very appealing for those that use netscape > > and the like and is also > > lynx friendly. > > Also good. I'd be interested in you collaborating >with the rest of > the doc team to try and get this in to the 'mainstream' site as well. well the freebsd.org site is not what i want to replace. I would be willing to contribute to it as well. maybe another part of the site ( e.g. newbies.freebsd.org ) > > I have already coded alot of user/interactive parts >of > > the site in php. > > This is (sort of) the problem. > > PHP (or Zope, or Zend, or lots complicated CGI >scripts) are great when > you only have one site. And one language. And only a few people working > on it. like i said earlier, planting he seed is what counts. I'm sure others that are fluent in foreign languages that i am not would eventually make the conversion. I would hope. > > As soon as you start using something less mainstream, you start to reduce > the number of people who can work on it, and, more importantly, you increase > the effort required to mirror it (and, quite possibly, to translate it). the different languages would be a problem being that i only speak English however, mirroring the site will not be difficult if it was or was not incorporated with freebsd.org, i have mirrored the php.net site awhile back when i first started to learn php and the way they had set it up was rather simple using rsync to mirror the site and a cron job to keep the mirror's up to date. however, there were a few bugs that would need some sort of work around. so in short i agree with you. There are pro's and con's in the way php.net mirrors their site. > > If you look at the FreeBSD site as it is at the moment, you'll see it's > mirrored in sixty countries, and translated in to five languages. I never said i wanted to replace freebsd.org. I have consistantly said it would be a seperate entity entirely. Now you guys are opening my mind up to a much larger project then i had in mind. Which was initially not my intentions. > > That's possible because the site's infrastructure is relatively basic. > The mirrors don't need to worry about setting up a complex webserver, > all they need is basic CGI functionality, and the translation teams just > need to be familiar with HTML, there's nothing extra they need to learn. > This keeps the effort requirement down, and increases the chance that > people will participate. Documentation for mirroring the freebsd.org site is lacking majorily. i attempted to do it once and was unsuccesful. > > Looking at your list of proposed content; > > > before launching the alpha site it will include: > > > > -a step by step installation process focused on the > > novice. > > -troubleshooting > > -basic networking support > > -getting Connected to the internet > > -all man pages marked outdated/up to date > > -using CVSup and make world > > -security related support > > -what services need to be running for specific server > > purposes > > -performance optimization > > -understanding log files > > -understanding /etc/*.conf files for the novice > > -most common asked questions with simple solutions ( > > Not FAQ's ) > > -FreeBSD command reference. > > -UID's and GID's file permissions > > -introduction to firewalls. > > -mailing list archives which users will be able to > > send and recieve via the web > > With the exception of the mailing list archives, there's nothing there > that can't be done with the FreeBSD site as it is, and; again, the documentation on Freebsd.org is not very simple to navigate around or understand for the novice/newbie. that is what i want to focus on ( the newbie ), rather than an overwheming description with alot of info that newbies would only be able to understand 10% if even. It would be easier im my opinion to redo the whole site then it would to pick through what is outdated and what is not. > > > the beauty of the site is that user can submit > > comments to the documentation > > also add documentation to the subject in mind that > > will be pre-formatted > > to the site once submitted and at the bottom of the > > page will be links to all > > the comments and additional documentation. > > That's a nice idea. I'd be interested in something like this for the > FreeBSD site that automatically included a link to the outstanding PRs > for a piece of documentation. This part i have almost fully completed the code for. Making it work with freebsd.org would need a lot of tweaking. > However, your approach won't scale to new languages, or to mirror sites, > without a lot of effort, and it's issues like these that we have to > consider for the main FreeBSD site. > > Also, consider how the user will be able to get their documentation. Will > it only be available from your site? A lot of people have dial up > connections, and won't want to recheck a new site each week on the off > chance that some comments have been added to a document. well the code already has an option that would email a notification of new comments to users that have submitted comments to the documentation at hand, along with a newsletter with updates to the site ( which is undetermined how often it will be sent ). > How will they be > able to keep local copies of your documentation? Will they be able to > download Postscript or PDF versions for pretty printing. like i said this would be alpha, these things would fit more into the beta release. I have pondered this already and have ideas on how to implement this. but nothing set in stone thus far. > Or even suitable > for installing in to a Palm Pilot[1]. Palm pilots, well quite honestly i have never owned one and do not know how they work. > > I'm not trying to be negative -- I deeply appreciate that you want to help, > and that you're prepared to put the time in to doing some work on what you > see as being problems. > I think it is time for me to write another email to recapitulate everythng that has been discussed and also clearify some key points of interest both on my part and what others have suggested to me. Which i will do tomorrow sometime. mike god@yahoo.com __________________________________________________ Do You Yahoo!? Talk to your friends online with Yahoo! Messenger. http://messenger.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 27 20:20:13 1999 Delivered-To: freebsd-stable@freebsd.org Received: from inbox.org (inbox.org [216.22.145.8]) by hub.freebsd.org (Postfix) with ESMTP id 1CEE1153A6 for ; Mon, 27 Dec 1999 20:20:07 -0800 (PST) (envelope-from bsd@inbox.org) Received: from localhost (bsd@localhost) by inbox.org (8.9.3/8.9.3) with SMTP id XAA22548 for ; Mon, 27 Dec 1999 23:20:14 -0500 (EST) Date: Mon, 27 Dec 1999 23:20:14 -0500 (EST) From: "Mr. K." To: stable@freebsd.org Subject: panic 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 received the following messages in /var/log/messages, followed by a kernel panic (I assume that's why it rebooted, anyway)... Dec 27 23:08:36 freebsd50 /kernel: r rx list -- packet dropped! Dec 27 23:08:36 freebsd50 /kernel: xl0: no memory for rx list -- packet dropped! Dec 27 23:08:36 freebsd50 last message repeated 177 times Dec 27 23:13:50 freebsd50 /kernel: Copyright (c) 1992-1999 FreeBSD Inc. What I was doing was making 500 connections from this box to a linux box and sending 1 million messages (10 bytes) back and forth. This box was the client, the linux box was the server. Unfortunately, it looks like the linux box won :(. Totally untweaked kernel. I didn't get to tweaking yet. I shouldn't have to tweak anything to make the kernel not panic, though... Not complaining, just pre-empting possible flames. Is this a known problem? Yes, I should enable crash dumps, I'm going to go look for documentation on that now... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 27 20:23:47 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mass.cdrom.com (castles542.castles.com [208.214.165.106]) by hub.freebsd.org (Postfix) with ESMTP id A9403153AE for ; Mon, 27 Dec 1999 20:23:27 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id UAA00870; Mon, 27 Dec 1999 20:28:16 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912280428.UAA00870@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Mr. K." Cc: stable@freebsd.org Subject: Re: panic In-reply-to: Your message of "Mon, 27 Dec 1999 23:20:14 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 27 Dec 1999 20:28:16 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > received the following messages in /var/log/messages, followed by a kernel > panic (I assume that's why it rebooted, anyway)... > > Dec 27 23:08:36 freebsd50 /kernel: r rx list -- packet dropped! > Dec 27 23:08:36 freebsd50 /kernel: xl0: no memory for rx list -- packet > dropped! > Dec 27 23:08:36 freebsd50 last message repeated 177 times > Dec 27 23:13:50 freebsd50 /kernel: Copyright (c) 1992-1999 FreeBSD Inc. > > What I was doing was making 500 connections from this box to a linux box > and sending 1 million messages (10 bytes) back and forth. This box was > the client, the linux box was the server. Unfortunately, it looks like > the linux box won :(. > > Totally untweaked kernel. I didn't get to tweaking yet. I shouldn't have > to tweak anything to make the kernel not panic, though... Not > complaining, just pre-empting possible flames. That's completely incorrect. > Is this a known problem? Yes, I should enable crash dumps, I'm going to > go look for documentation on that now... You might just try watching the console when the system goes over. GENERIC is tuned to work well on a wide range of configurations, not to be pounded to death. Try setting NMBCLUSTERS to something around 10000. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 27 20:32:12 1999 Delivered-To: freebsd-stable@freebsd.org Received: from inbox.org (inbox.org [216.22.145.8]) by hub.freebsd.org (Postfix) with ESMTP id 0188C14D09; Mon, 27 Dec 1999 20:32:11 -0800 (PST) (envelope-from bsd@inbox.org) Received: from localhost (bsd@localhost) by inbox.org (8.9.3/8.9.3) with SMTP id XAA22968; Mon, 27 Dec 1999 23:32:18 -0500 (EST) Date: Mon, 27 Dec 1999 23:32:18 -0500 (EST) From: "Mr. K." To: Mike Smith Cc: stable@freebsd.org Subject: Re: panic In-Reply-To: <199912280428.UAA00870@mass.cdrom.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 > > Totally untweaked kernel. I didn't get to tweaking yet. I shouldn't have > > to tweak anything to make the kernel not panic, though... Not > > complaining, just pre-empting possible flames. > > That's completely incorrect. > > > Is this a known problem? Yes, I should enable crash dumps, I'm going to > > go look for documentation on that now... > > You might just try watching the console when the system goes over. > GENERIC is tuned to work well on a wide range of configurations, not to > be pounded to death. Try setting NMBCLUSTERS to something around 10000. > Ran to the machine as soon as I realized what happened, but unfortunately, too late. I was not root when this happened, so, basically, you're saying that freebsd is not meant for a production environment where untrusted users have telnet access? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 27 21:32:43 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail2.uniserve.com (mail2.uniserve.com [204.244.156.7]) by hub.freebsd.org (Postfix) with ESMTP id E4E6914C2F for ; Mon, 27 Dec 1999 21:32:39 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca ([204.244.186.218]) by mail2.uniserve.com with smtp (Exim 3.03 #4) id 122pF8-000LVe-00; Mon, 27 Dec 1999 21:32:22 -0800 Date: Mon, 27 Dec 1999 21:32:16 -0800 (PST) From: Tom X-Sender: tom@shell.uniserve.ca To: "Mr. K." Cc: stable@freebsd.org Subject: Re: panic 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, 27 Dec 1999, Mr. K. wrote: > received the following messages in /var/log/messages, followed by a kernel > panic (I assume that's why it rebooted, anyway)... > > Dec 27 23:08:36 freebsd50 /kernel: r rx list -- packet dropped! > Dec 27 23:08:36 freebsd50 /kernel: xl0: no memory for rx list -- packet > dropped! > Dec 27 23:08:36 freebsd50 last message repeated 177 times > Dec 27 23:13:50 freebsd50 /kernel: Copyright (c) 1992-1999 FreeBSD Inc. > > What I was doing was making 500 connections from this box to a linux box > and sending 1 million messages (10 bytes) back and forth. This box was > the client, the linux box was the server. Unfortunately, it looks like > the linux box won :(. > > Totally untweaked kernel. I didn't get to tweaking yet. I shouldn't have > to tweak anything to make the kernel not panic, though... Not > complaining, just pre-empting possible flames. > > Is this a known problem? Yes, I should enable crash dumps, I'm going to > go look for documentation on that now... Easy fix: increase NMBCLUSTERS to 6000 or so. Less easy fix: don't use the xl driver, it has a tendency to freak out. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 27 21:35:33 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail2.uniserve.com (mail2.uniserve.com [204.244.156.7]) by hub.freebsd.org (Postfix) with ESMTP id AD1B314A1A; Mon, 27 Dec 1999 21:35:30 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca ([204.244.186.218]) by mail2.uniserve.com with smtp (Exim 3.03 #4) id 122pI5-000LZV-00; Mon, 27 Dec 1999 21:35:25 -0800 Date: Mon, 27 Dec 1999 21:35:20 -0800 (PST) From: Tom X-Sender: tom@shell.uniserve.ca To: Mike Smith Cc: "Mr. K." , stable@freebsd.org Subject: Re: panic In-Reply-To: <199912280428.UAA00870@mass.cdrom.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, 27 Dec 1999, Mike Smith wrote: > > received the following messages in /var/log/messages, followed by a kernel > > panic (I assume that's why it rebooted, anyway)... > > > > Dec 27 23:08:36 freebsd50 /kernel: r rx list -- packet dropped! > > Dec 27 23:08:36 freebsd50 /kernel: xl0: no memory for rx list -- packet > > dropped! > > Dec 27 23:08:36 freebsd50 last message repeated 177 times > > Dec 27 23:13:50 freebsd50 /kernel: Copyright (c) 1992-1999 FreeBSD Inc. > > > > What I was doing was making 500 connections from this box to a linux box > > and sending 1 million messages (10 bytes) back and forth. This box was > > the client, the linux box was the server. Unfortunately, it looks like > > the linux box won :(. > > > > Totally untweaked kernel. I didn't get to tweaking yet. I shouldn't have > > to tweak anything to make the kernel not panic, though... Not > > complaining, just pre-empting possible flames. > > That's completely incorrect. I don't know what part of the above you say is incorrect. FreeBSD has a tendency to panic in out of mbuf situations. That shouldn't happen. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 27 22: 2:33 1999 Delivered-To: freebsd-stable@freebsd.org Received: from pooh.elsevier.nl (p138.as1.naas1.eircom.net [159.134.254.138]) by hub.freebsd.org (Postfix) with ESMTP id E355E14FEE; Mon, 27 Dec 1999 22:02:28 -0800 (PST) (envelope-from steve@pooh.elsevier.nl) Received: (from steve@localhost) by pooh.elsevier.nl (8.9.3/8.9.3) id GAA17244; Tue, 28 Dec 1999 06:02:21 GMT (envelope-from steve) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Tue, 28 Dec 1999 06:02:00 -0000 (GMT) From: "Steve O'Hara-Smith" To: "Mr. K." Subject: Re: panic Cc: stable@freebsd.org, Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 28-Dec-99 Mr. K. wrote: > I was not root when this happened, so, basically, you're saying that > freebsd is not meant for a production environment where untrusted users > have telnet access? AFAIK there is nothing that is suitable for such an environment without first preparing it carefully. It is a matter of tuning and configuration, out of the box FreeBSD is not tuned for pounding but for general use. It can be tuned for pounding but it pays to tune for the specific type of pounding you expect to give it. Most systems can be made to panic with no root users, as a long term system developer and admin I would never give untrusted users telnet to production systems (on anything). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 27 22: 7:34 1999 Delivered-To: freebsd-stable@freebsd.org Received: from luna.lyris.net (luna.shelby.com [207.90.155.6]) by hub.freebsd.org (Postfix) with ESMTP id 82486152FE for ; Mon, 27 Dec 1999 22:07:30 -0800 (PST) (envelope-from kip@lyris.com) Received: from luna.shelby.com by luna.lyris.net (8.9.1b+Sun/SMI-SVR4) id WAA29228; Mon, 27 Dec 1999 22:06:34 -0800 (PST) Received: from (luna.shelby.com [207.90.155.6]) by luna.shelby.com with SMTP (MailShield v1.50); Mon, 27 Dec 1999 22:06:34 -0800 Date: Mon, 27 Dec 1999 22:06:17 -0800 (PST) From: Kip Macy To: "Mr. K." Cc: stable@freebsd.org Subject: Re: panic In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SMTP-HELO: luna X-SMTP-MAIL-FROM: kip@lyris.com X-SMTP-RCPT-TO: bsd@inbox.org,stable@freebsd.org X-SMTP-PEER-INFO: luna.shelby.com [207.90.155.6] Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I was not root when this happened, so, basically, you're saying that > freebsd is not meant for a production environment where untrusted users > have telnet access? As far as I can tell, yes. Until default per user mbuf limitations or some such thing is in place no amount of mbufs will prevent intentionally bad code from downing the machine. My understanding is that this was not a problem in 2.x. -Kip To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 27 22:17:42 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mass.cdrom.com (castles542.castles.com [208.214.165.106]) by hub.freebsd.org (Postfix) with ESMTP id 1F977153BF; Mon, 27 Dec 1999 22:17:37 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id WAA01190; Mon, 27 Dec 1999 22:22:26 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912280622.WAA01190@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Mr. K." Cc: Mike Smith , stable@freebsd.org Subject: Re: panic In-reply-to: Your message of "Mon, 27 Dec 1999 23:32:18 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 27 Dec 1999 22:22:26 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > Totally untweaked kernel. I didn't get to tweaking yet. I shouldn't have > > > to tweak anything to make the kernel not panic, though... Not > > > complaining, just pre-empting possible flames. > > > > That's completely incorrect. > > > > > Is this a known problem? Yes, I should enable crash dumps, I'm going to > > > go look for documentation on that now... > > > > You might just try watching the console when the system goes over. > > GENERIC is tuned to work well on a wide range of configurations, not to > > be pounded to death. Try setting NMBCLUSTERS to something around 10000. > > > > Ran to the machine as soon as I realized what happened, but unfortunately, > too late. > > I was not root when this happened, so, basically, you're saying that > freebsd is not meant for a production environment where untrusted users > have telnet access? No. As I specifically said, the GENERIC kernel configuration is tuned for 'generic' operations. There are a small number of well-known and well-documented tuning options that need to be adjusted to accommodate the sort of extreme load situations you're encountering. You might want to think, just for a moment, why FreeBSD is in such wide use if the assumptions you're making are true. And since it is, perhaps you should re-evaluate them? -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 27 22:19:34 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mass.cdrom.com (castles542.castles.com [208.214.165.106]) by hub.freebsd.org (Postfix) with ESMTP id 78BC415117 for ; Mon, 27 Dec 1999 22:19:31 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id WAA01209; Mon, 27 Dec 1999 22:24:20 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912280624.WAA01209@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Tom Cc: "Mr. K." , stable@freebsd.org Subject: Re: panic In-reply-to: Your message of "Mon, 27 Dec 1999 21:32:16 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 27 Dec 1999 22:24:20 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Less easy fix: don't use the xl driver, it has a tendency to freak out. This is actually untrue; it's just verbose when it freaks out, while most other drivers just fail silently. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 27 22:21:18 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mass.cdrom.com (castles542.castles.com [208.214.165.106]) by hub.freebsd.org (Postfix) with ESMTP id B7A8E153DD; Mon, 27 Dec 1999 22:21:14 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id WAA01224; Mon, 27 Dec 1999 22:26:02 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912280626.WAA01224@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Tom Cc: Mike Smith , "Mr. K." , stable@freebsd.org Subject: Re: panic In-reply-to: Your message of "Mon, 27 Dec 1999 21:35:20 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 27 Dec 1999 22:26:01 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > Totally untweaked kernel. I didn't get to tweaking yet. I shouldn't have > > > to tweak anything to make the kernel not panic, though... Not > > > complaining, just pre-empting possible flames. > > > > That's completely incorrect. > > I don't know what part of the above you say is incorrect. > > FreeBSD has a tendency to panic in out of mbuf situations. That > shouldn't happen. The semantics of "should" and "shouldn't" are debatable. In this case, the panic is a simple indicator that the administrator hasn't correctly tuned the system. Many would argue that this is a much better outcome than a system that performs poorly for no immediately perceptible reason, and it certainly encourages the prompt application of a correct adjustment. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 27 22:25:50 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mass.cdrom.com (castles542.castles.com [208.214.165.106]) by hub.freebsd.org (Postfix) with ESMTP id 00B9D14DD8 for ; Mon, 27 Dec 1999 22:25:48 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id WAA01257; Mon, 27 Dec 1999 22:30:23 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912280630.WAA01257@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Kip Macy Cc: "Mr. K." , stable@freebsd.org Subject: Re: panic In-reply-to: Your message of "Mon, 27 Dec 1999 22:06:17 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 27 Dec 1999 22:30:23 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > I was not root when this happened, so, basically, you're saying that > > freebsd is not meant for a production environment where untrusted users > > have telnet access? > > As far as I can tell, yes. Until default per user mbuf limitations or some > such thing is in place no amount of mbufs will prevent intentionally bad > code from downing the machine. My understanding is that this was not a > problem in 2.x. It's a fundamental problem with the BSD mbuf architecture. It's not something that as many people were seeing with 2.2 simply because people weren't pushing systems as hard back then. There's a conscious tradeoff between raw performance and tuning requirement in the BSD mbuf allocator. You can't add more buffering once the system has started, so you need to tune at kernel build or load time. The upside from this is that certain critical network buffer operations are extremely efficient. Work is underway (and in fact mostly complete) to reduce the fataility of mbuf starvation to the system, but the fact remains that correct tuning of the BSD kernel is and always has been critical to performance and robustness. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 27 23:32: 0 1999 Delivered-To: freebsd-stable@freebsd.org Received: from oracle.dsuper.net (oracle.dsuper.net [205.205.255.1]) by hub.freebsd.org (Postfix) with ESMTP id EEE6F14D7D; Mon, 27 Dec 1999 23:31:56 -0800 (PST) (envelope-from bmilekic@dsuper.net) Received: from oracle.dsuper.net (oracle.dsuper.net [205.205.255.1]) by oracle.dsuper.net (8.9.3/8.9.3) with ESMTP id CAA14399; Tue, 28 Dec 1999 02:31:51 -0500 (EST) Date: Tue, 28 Dec 1999 02:31:51 -0500 (EST) From: Bosko Milekic To: Mike Smith Cc: Kip Macy , "Mr. K." , stable@FreeBSD.ORG Subject: Re: panic In-Reply-To: <199912280630.WAA01257@mass.cdrom.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, 27 Dec 1999, Mike Smith wrote: !>> As far as I can tell, yes. Until default per user mbuf limitations or some !>> such thing is in place no amount of mbufs will prevent intentionally bad !>> code from downing the machine. My understanding is that this was not a !>> problem in 2.x. Already implemented in -CURRENT (the ulimit on sockbuf space, that is). Anybody want to help MFCing? !> !>It's a fundamental problem with the BSD mbuf architecture. It's not !>something that as many people were seeing with 2.2 simply because people !>weren't pushing systems as hard back then. !> !>There's a conscious tradeoff between raw performance and tuning !>requirement in the BSD mbuf allocator. You can't add more buffering once !>the system has started, so you need to tune at kernel build or load time. !>The upside from this is that certain critical network buffer operations !>are extremely efficient. !> !>Work is underway (and in fact mostly complete) to reduce the fataility of !>mbuf starvation to the system, but the fact remains that correct tuning !>of the BSD kernel is and always has been critical to performance and !>robustness. "Work" has been implemented in -CURRENT, actually. In fact, "more work" is being done on filtering out bad guys (before somebody decides to MFC, that is). The problem here is not that directly related to an mbuf starvation, or so it seems. Then again, one of the [easy] ways of checking if it is would be to of course verify complaints in /var/log/messages. In any case, -CURRENT should no longer panic on a lack of mbufs, well, at least not in the mbuf code. However, problems may remain here and there mainly for one reason: mbuf allocations not being checked for failure and resulting in either a NULL mbuf pointer, or an explicit panic from the code using the allocation routines. The solution would be to handle the shortage in other parts of the code differently. If whoever posted the original message could of course provide more detailed information regarding the crash, so that one can actually know for a fact what and where the problem is, we wouldn't be stuck here guessing. Bosko. ...... . . . . . . . . . . . . . Bosko Milekic -- bmilekic@dsuper.net . . . . . . . . . . . ...... . . WWW: http://pages.infinit.net/bmilekic/ . ................................................ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 27 23:50:25 1999 Delivered-To: freebsd-stable@freebsd.org Received: from ccssu.crimea.ua (ccssu.ccssu.crimea.ua [62.244.13.130]) by hub.freebsd.org (Postfix) with ESMTP id 854BB14D7D; Mon, 27 Dec 1999 23:50:02 -0800 (PST) (envelope-from phantom@scorpion.crimea.ua) Received: (from uucp@localhost) by ccssu.crimea.ua (8.9.3/8.9.0) with UUCP id JAA25152; Tue, 28 Dec 1999 09:41:56 +0200 Received: (from phantom@localhost) by scorpion.crimea.ua (8.8.8/8.8.5+ssl+keepalive) id JAA00635; Tue, 28 Dec 1999 09:22:11 +0300 (MSK) Date: Tue, 28 Dec 1999 09:22:11 +0300 From: Alexey Zelkin To: Mike s Cc: stable@FreeBSD.ORG, doc@FreeBSD.ORG Subject: Re: freebsd.org Message-ID: <19991228092211.A387@scorpion.crimea.ua> Reply-To: doc@FreeBSD.ORG References: <19991228041517.23423.qmail@web506.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.7i In-Reply-To: <19991228041517.23423.qmail@web506.mail.yahoo.com> X-Operating-System: FreeBSD 2.2.7-RELEASE i386 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi, [Follow up replies to -doc. Discussion does not belongs -stable anymore] Mike please send you next letter to doc@FreeBSD.org only! Thanks! On Mon, Dec 27, 1999 at 08:15:17PM -0800, Mike s wrote: > well the freebsd.org site is not what i want to > replace. I would be willing to > contribute to it as well. maybe another part of the > site ( e.g. newbies.freebsd.org ) Please check http://www.FreeBSD.org/projects/newbies.html. Maybe you can contribute something there. > the different languages would be a problem being that > i only speak English > however, Nobody asks you to translate site. Your task - create very useful site (like FreeBSD.org) and volonters will translate it anyway. > mirroring the site will not be difficult if > it was or was > not incorporated with freebsd.org, Sure :) > i have mirrored the > php.net site awhile back > when i first started to learn php and the way they had > set it up was rather > simple using rsync to mirror the site and a cron job > to keep the mirror's up to > date. Me too :) As well as FreeBSD.org and apache.org and many others. > > If you look at the FreeBSD site as it is at the > moment, you'll see it's > > mirrored in sixty countries, and translated in to > five languages. > > I never said i wanted to replace freebsd.org. I have > consistantly said it would > be a seperate entity entirely. Now you guys are > opening my mind up to a much > larger project then i had in mind. Which was initially > not my intentions. Try to split this "larger project" for smaller and try to complete them sequently. If people find your site usefull then they'll help you. > Documentation for mirroring the freebsd.org site is > lacking majorily. > i attempted to do it once and was unsuccesful. Hmmm... What kind of problem ? I tried to rebuild www site from the scratch and download complete site -- it worked fine every time. > > That's a nice idea. I'd be interested in something > like this for the > > FreeBSD site that automatically included a link to > the outstanding PRs > > for a piece of documentation. > > This part i have almost fully completed the code for. > Making it work with > freebsd.org would need a lot of tweaking. Good example of not well planed work. > I think it is time for me to write another email to > recapitulate everythng that > has been discussed and also clearify some key points > of interest both on my > part and what others have suggested to me. Which i > will do tomorrow sometime. Yes. It would be nice. -- /* Alexey Zelkin && phantom@cris.net */ /* Tavric National University && phantom@crimea.edu */ /* http://www.ccssu.crimea.ua/~phantom && phantom@FreeBSD.org */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 28 0:56:23 1999 Delivered-To: freebsd-stable@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 72D0C14F2B for ; Tue, 28 Dec 1999 00:56:17 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.11 #1) id 122sSN-0000UY-00; Tue, 28 Dec 1999 10:58:15 +0200 From: Sheldon Hearn To: Peter Jeremy Cc: Vlad Skvortsov , freebsd-stable@FreeBSD.ORG Subject: Re: /bin/test broken ? In-reply-to: Your message of "Mon, 27 Dec 1999 11:22:14 +1100." <99Dec27.111307est.40321@border.alcanet.com.au> Date: Tue, 28 Dec 1999 10:58:15 +0200 Message-ID: <1893.946371495@axl.noc.iafrica.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 27 Dec 1999 11:22:14 +1100, Peter Jeremy wrote: > Although it seems your real problem is: > > $ /bin/[ 1 -ne 0 ] > > [: ]: unexpected operator Ah, Peter, you are the man. :-) What an obscure problem report. I'm quite happy to leave things the way they are, but as the person responsible for the newly imported test(1), I'll fix it if someone can convince me that /bin/[ is part of a reasonable syntax to support. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 28 1:13:54 1999 Delivered-To: freebsd-stable@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id A814C14D0F for ; Tue, 28 Dec 1999 01:13:50 -0800 (PST) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id BAA69692; Tue, 28 Dec 1999 01:08:21 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <199912280908.BAA69692@gndrsh.dnsmgr.net> Subject: Re: /bin/test broken ? In-Reply-To: <1893.946371495@axl.noc.iafrica.com> from Sheldon Hearn at "Dec 28, 1999 10:58:15 am" To: sheldonh@uunet.co.za (Sheldon Hearn) Date: Tue, 28 Dec 1999 01:08:21 -0800 (PST) Cc: peter.jeremy@alcatel.com.au (Peter Jeremy), vss@ulstu.ru (Vlad Skvortsov), freebsd-stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > On Mon, 27 Dec 1999 11:22:14 +1100, Peter Jeremy wrote: > > > Although it seems your real problem is: > > > $ /bin/[ 1 -ne 0 ] > > > [: ]: unexpected operator > > Ah, Peter, you are the man. :-) > > What an obscure problem report. I'm quite happy to leave things the > way they are, but as the person responsible for the newly imported > test(1), I'll fix it if someone can convince me that /bin/[ is part of a > reasonable syntax to support. The syntax is reasonable, as /bin/[ or /bin/test is about the only way one would overide a builtin [, should some shell implement test as a builtin. (The builtin man page and my recolection of history say that [ or test have never been sh or csh builtins, but I have no idea about bash, tcsh, ksh or the million other shells out there.) -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 28 1:23:53 1999 Delivered-To: freebsd-stable@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id DF2DB14CC1 for ; Tue, 28 Dec 1999 01:23:49 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.11 #1) id 122sv9-0000ea-00; Tue, 28 Dec 1999 11:27:59 +0200 From: Sheldon Hearn To: "Rodney W. Grimes" Cc: freebsd-stable@FreeBSD.ORG Subject: Re: /bin/test broken ? In-reply-to: Your message of "Tue, 28 Dec 1999 01:08:21 PST." <199912280908.BAA69692@gndrsh.dnsmgr.net> Date: Tue, 28 Dec 1999 11:27:59 +0200 Message-ID: <2515.946373279@axl.noc.iafrica.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 28 Dec 1999 01:08:21 PST, "Rodney W. Grimes" wrote: > The syntax is reasonable, as /bin/[ or /bin/test is about the only way > one would overide a builtin [, should some shell implement test as > a builtin. Sold, to the old guy in the Christmas hat! *bang* I'll sort 'em out. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 28 1:29:52 1999 Delivered-To: freebsd-stable@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id 3E38E153EE for ; Tue, 28 Dec 1999 01:29:49 -0800 (PST) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id BAA69765; Tue, 28 Dec 1999 01:29:35 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <199912280929.BAA69765@gndrsh.dnsmgr.net> Subject: Re: /bin/test broken ? In-Reply-To: <2515.946373279@axl.noc.iafrica.com> from Sheldon Hearn at "Dec 28, 1999 11:27:59 am" To: sheldonh@uunet.co.za (Sheldon Hearn) Date: Tue, 28 Dec 1999 01:29:35 -0800 (PST) Cc: freebsd-stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > On Tue, 28 Dec 1999 01:08:21 PST, "Rodney W. Grimes" wrote: > > > The syntax is reasonable, as /bin/[ or /bin/test is about the only way > > one would overide a builtin [, should some shell implement test as > > a builtin. > > Sold, to the old guy in the Christmas hat! *bang* Hey, where did this hole in my hat come from???? :-) :-) :-) -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 28 2:20:44 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mirage.nlink.com.br (mirage.nlink.com.br [200.249.195.3]) by hub.freebsd.org (Postfix) with SMTP id A411514D19 for ; Tue, 28 Dec 1999 02:20:40 -0800 (PST) (envelope-from paulo@nlink.com.br) Received: (qmail 23918 invoked by uid 501); 28 Dec 1999 10:20:34 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 28 Dec 1999 10:20:34 -0000 Date: Tue, 28 Dec 1999 08:20:34 -0200 (EDT) From: Paulo Fragoso To: freebsd-stable@FreeBSD.ORG Subject: 3.4 ISO Images Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I've installed FreeBSD 3.4-RELEASE using iso image from ftp. It's working fine but boot floppy emulation (boot from cdrom) was build with 3.2-STABLE kernel. Is it ok? Thanks, Paulo. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 28 2:27:20 1999 Delivered-To: freebsd-stable@freebsd.org Received: from emmi.physik.TU-Berlin.DE (emmi.physik.TU-Berlin.DE [130.149.160.103]) by hub.freebsd.org (Postfix) with ESMTP id C84441545A; Tue, 28 Dec 1999 02:27:16 -0800 (PST) (envelope-from ibex@emmi.physik.TU-Berlin.DE) Received: (from ibex@localhost) by emmi.physik.TU-Berlin.DE (8.9.3/8.9.3) id LAA10339; Tue, 28 Dec 1999 11:27:13 +0100 (CET) (envelope-from ibex) Date: Tue, 28 Dec 1999 11:27:12 +0100 From: Dirk Froemberg To: Mikhail Teterin Cc: stable@freebsd.org, ports@freebsd.org, nsayer@freebsd.org Subject: Re: -lc vs. -lc_r (building Apache-PHP) Message-ID: <19991228112712.A9934@physik.TU-Berlin.DE> References: <199912272030.PAA76727@rtfm.newton> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <199912272030.PAA76727@rtfm.newton>; from mi@kot.ne.mediaone.net on Mon, Dec 27, 1999 at 03:30:08PM -0500 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Mikhail! On Mon, Dec 27, 1999 at 03:30:08PM -0500, Mikhail Teterin wrote: > Tom once stated: > => => What's the magic and why doesn't the port know it? Why is -lc even > => => in play if some of the components (-lmysqlclient) require -lc_r? > => => Yours, > => = > => = libmysqlclient does not require -lc_r, because the library does > => =not use threads. Only mysqld is threaded. > => > => Thank you, Tom, for this correction. However, this does not change > => much. Some other extension wants threads then... > = > = Uhh.. highly unlikely. Almost none of PHP3 is thread-safe, and only a > =bit of Apache is thread-safe. I doubt that anything in the Apache-PHP > =port wants or needs threads. > > I did not put it in there myself :) At least one of the many extensions > selected (I included the Makefile.inc with my original report) dragged > the c_r with it... It's the mhash option causing the problem. I disabled it for now. Basically the mhash port doesn't seem to be able to deal with FreeBSD's -pthread. I'll look at it to see whether the problem can be easily be solved. Regards Dirk [Cc'ed to mhash's maintainer] -- Dirk Froemberg 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 Tue Dec 28 2:51: 6 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mirage.nlink.com.br (mirage.nlink.com.br [200.249.195.3]) by hub.freebsd.org (Postfix) with SMTP id 72B6815008 for ; Tue, 28 Dec 1999 02:51:03 -0800 (PST) (envelope-from paulo@nlink.com.br) Received: (qmail 25671 invoked by uid 501); 28 Dec 1999 10:51:01 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 28 Dec 1999 10:51:01 -0000 Date: Tue, 28 Dec 1999 08:51:01 -0200 (EDT) From: Paulo Fragoso To: freebsd-stable@freebsd.org Subject: kernel.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 Hi, When I do upgrades (booting from cdrom and chosing UPGRADE option) always the file /boot/kernel.conf are removed. Now before I start new upgrade I make a copy for that file. I think upgrade script should move /boot/kernel.conf to /boot/kernel.conf.old instead remove it. Thanks, Paulo. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 28 3:35:20 1999 Delivered-To: freebsd-stable@freebsd.org Received: from grisu.bik-gmbh.de (grisu.bik-gmbh.de [194.233.237.82]) by hub.freebsd.org (Postfix) with ESMTP id 6E96D14FBC for ; Tue, 28 Dec 1999 03:35:16 -0800 (PST) (envelope-from cracauer@counter.bik-gmbh.de) Received: from counter.bik-gmbh.de (counter.bik-gmbh.de [194.233.237.131]) by grisu.bik-gmbh.de (8.9.3/8.9.3) with ESMTP id MAA21088; Tue, 28 Dec 1999 12:35:11 +0100 (MET) Received: (from cracauer@localhost) by counter.bik-gmbh.de (8.9.3/8.8.8) id MAA38223; Tue, 28 Dec 1999 12:34:35 +0100 (CET) (envelope-from cracauer) Date: Tue, 28 Dec 1999 12:34:35 +0100 From: Martin Cracauer To: Marcin Cieslak Cc: freebsd-stable@FreeBSD.ORG Subject: Re: /bin/test broken ? Message-ID: <19991228123435.A37738@cons.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Marcin Cieslak on Thu, Dec 23, 1999 at 02:30:19PM +0100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In , Marcin Cieslak wrote: > On Thu, 23 Dec 1999, Eric D. Futch wrote: > > > -stable as of Wed Dec 22 01:48:17 EST 1999 dosen't seem to have this > > problem. > > > > % /bin/test 1 -ne 0 ] > > test: ]: unexpected operator > > Recent -stable: > > $ /bin/test 1 -ne 0 ] > test: syntax error > $ [ 1 -ne 0 ] > $ > > but on Solaris 2.5 in both sh and ksh: > > $ /bin/test 1 -ne 0 ] > $ [ 1 -ne 0 ] Posix makes it clear that `test -n` without further arguments should be interpreted as "yes, there is a string with length > 0, and it is a dash and an n". Solaris violates this rule, amoung other problems. Also, try this on Solaris: sh -c 'test -n ; echo This must appear no matter what the former did' ksh -c 'test -n ; echo This must appear no matter what the former did' Probably caused by a shared source for standalone test(1) and sh's test(1). Someone calls exit() on error in test(1), and doesn't take into account that it may be builtin in sh. See also http://www3.cons.org/cracauer/bourneshell.html under "Fun with test -n". This is a beta-test page, feedback welcome. Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.bik-gmbh.de/~cracauer/ "Where do you want to do today?" Hard to tell running your calendar program on a junk operating system, eh? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 28 3:42:32 1999 Delivered-To: freebsd-stable@freebsd.org Received: from tank.skynet.be (tank.skynet.be [195.238.2.35]) by hub.freebsd.org (Postfix) with ESMTP id 6E009150BA for ; Tue, 28 Dec 1999 03:42:26 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by tank.skynet.be (8.9.3/odie-relay-v1.0) with ESMTP id MAA24100 for ; Tue, 28 Dec 1999 12:42:25 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@foxbert.skynet.be Message-Id: In-Reply-To: <199912271656.RAA28357@dorifer.heim3.tu-clausthal.de> References: <199912271656.RAA28357@dorifer.heim3.tu-clausthal.de> Date: Tue, 28 Dec 1999 11:19:45 +0100 To: freebsd-stable@FreeBSD.ORG From: Brad Knowles Subject: Re: Huge differences in suid programs ? Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 5:56 PM +0100 1999/12/27, Oliver Fromme wrote: > Well, the daily security script just does an "ls -l" on all > suid/sgid binaries and diffs them with the previous listing. I understand that part. > Therefore it will regard all differences in the ls -l output > as "differences". This can be the ownership, time stamps, and > sizes of the files. I understand that part, too. > Even if the actual contents of the files > are the same, the time stamps are not the same (because they > indicate the time at which the files where created), so the > daily security script will regard them as "different". My question has nothing to do with the daily security script noticing that things are different. It has everything to do with why the binaries were replaced to begin with, if the contents of the binaries haven't changed. -- These are my opinions -- not to be taken as official Skynet policy ____________________________________________________________________ |o| Brad Knowles, Belgacom Skynet NV/SA |o| |o| Systems Architect, News & FTP Admin Rue Col. Bourg, 124 |o| |o| Phone/Fax: +32-2-706.11.11/12.49 B-1140 Brussels |o| |o| http://www.skynet.be Belgium |o| \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. Unix is very user-friendly. It's just picky who its friends are. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 28 3:42:54 1999 Delivered-To: freebsd-stable@freebsd.org Received: from tank.skynet.be (tank.skynet.be [195.238.2.35]) by hub.freebsd.org (Postfix) with ESMTP id F347A15551 for ; Tue, 28 Dec 1999 03:42:45 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by tank.skynet.be (8.9.3/odie-relay-v1.0) with ESMTP id MAA24105; Tue, 28 Dec 1999 12:42:26 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@foxbert.skynet.be Message-Id: In-Reply-To: <19991227095920.A9365@freeway.dcfinc.com> References: <199912271336.FAA14584@netcom.com> <19991227134529.D1290@marder-1> <19991227095920.A9365@freeway.dcfinc.com> Date: Tue, 28 Dec 1999 11:20:13 +0100 To: "Chad R. Larson" From: Brad Knowles Subject: Re: Huge differences in suid programs ? Cc: Mark Ovens , Stan Brown , FreeBSD Stable List Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 9:59 AM -0700 1999/12/27, Chad R. Larson wrote: > The "make world" regenerates every binary on the machine, unless you > set the "no clean" option. It does so without regard to whether the > source for any particular program has changed. Ahh, okay. Now I understand. Nevermind.... -- These are my opinions -- not to be taken as official Skynet policy ____________________________________________________________________ |o| Brad Knowles, Belgacom Skynet NV/SA |o| |o| Systems Architect, News & FTP Admin Rue Col. Bourg, 124 |o| |o| Phone/Fax: +32-2-706.11.11/12.49 B-1140 Brussels |o| |o| http://www.skynet.be Belgium |o| \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. Unix is very user-friendly. It's just picky who its friends are. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 28 3:42:54 1999 Delivered-To: freebsd-stable@freebsd.org Received: from tank.skynet.be (tank.skynet.be [195.238.2.35]) by hub.freebsd.org (Postfix) with ESMTP id 87144154EB for ; Tue, 28 Dec 1999 03:42:40 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by tank.skynet.be (8.9.3/odie-relay-v1.0) with ESMTP id MAA24066; Tue, 28 Dec 1999 12:42:14 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@foxbert.skynet.be Message-Id: In-Reply-To: <19991227172949.A9209@skriver.dk> References: <199912271336.FAA14584@netcom.com> <19991227134529.D1290@marder-1> <19991227172949.A9209@skriver.dk> Date: Tue, 28 Dec 1999 11:17:46 +0100 To: Jesper Skriver From: Brad Knowles Subject: Re: Huge differences in suid programs ? Cc: Mark Ovens , Stan Brown , FreeBSD Stable List Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 5:29 PM +0100 1999/12/27, Jesper Skriver wrote: > What do you mean by different ? It looked to me like the file sizes had changed on most of them, but perhaps I'm misremembering things. > Most of them had only the date changed ... Then why where they replaced to begin with? -- These are my opinions -- not to be taken as official Skynet policy ____________________________________________________________________ |o| Brad Knowles, Belgacom Skynet NV/SA |o| |o| Systems Architect, News & FTP Admin Rue Col. Bourg, 124 |o| |o| Phone/Fax: +32-2-706.11.11/12.49 B-1140 Brussels |o| |o| http://www.skynet.be Belgium |o| \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. Unix is very user-friendly. It's just picky who its friends are. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 28 3:43: 7 1999 Delivered-To: freebsd-stable@freebsd.org Received: from tank.skynet.be (tank.skynet.be [195.238.2.35]) by hub.freebsd.org (Postfix) with ESMTP id 4D0B5155B4 for ; Tue, 28 Dec 1999 03:43:01 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by tank.skynet.be (8.9.3/odie-relay-v1.0) with ESMTP id MAA24110; Tue, 28 Dec 1999 12:42:28 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@foxbert.skynet.be Message-Id: In-Reply-To: References: Date: Tue, 28 Dec 1999 11:20:52 +0100 To: "Chris D. Faulhaber" , "Chad R. Larson" From: Brad Knowles Subject: Re: Huge differences in suid programs ? Cc: Mark Ovens , Stan Brown , FreeBSD Stable List Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 12:06 PM -0500 1999/12/27, Chris D. Faulhaber wrote: > OTOH, if you set: > > INSTALL=install -C > > in /etc/make.conf, unchanged files will not have their modification time > changed. I like this option! Thank you for telling me about it! I'm going to have to change that on my systems.... -- These are my opinions -- not to be taken as official Skynet policy ____________________________________________________________________ |o| Brad Knowles, Belgacom Skynet NV/SA |o| |o| Systems Architect, News & FTP Admin Rue Col. Bourg, 124 |o| |o| Phone/Fax: +32-2-706.11.11/12.49 B-1140 Brussels |o| |o| http://www.skynet.be Belgium |o| \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. Unix is very user-friendly. It's just picky who its friends are. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 28 5: 0:11 1999 Delivered-To: freebsd-stable@freebsd.org Received: from florence.pavilion.net (florence.pavilion.net [212.74.0.25]) by hub.freebsd.org (Postfix) with ESMTP id 1B58014FDD for ; Tue, 28 Dec 1999 05:00:08 -0800 (PST) (envelope-from joe@florence.pavilion.net) Received: (from joe@localhost) by florence.pavilion.net (8.9.3/8.8.8) id MAA09635; Tue, 28 Dec 1999 12:58:45 GMT (envelope-from joe) Date: Tue, 28 Dec 1999 12:58:45 +0000 From: Josef Karthauser To: Alex Cc: Mark Ovens , robmel@nadt.org.uk, stable@FreeBSD.ORG Subject: Re: CVSup woes Message-ID: <19991228125845.C7468@florence.pavilion.net> References: <199912271802.KAA02871@vashon.polstra.com> <19991227184100.H1290@marder-1> <3867C05F.60E5AAD1@freenet.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <3867C05F.60E5AAD1@freenet.co.uk> X-NCC-RegID: uk.pavilion Organisation: Pavilion Internet plc, Lees House, 21-23 Dyke Road, Brighton, England Phone: +44-845-333-5000 Fax: +44-845-333-5001 Mobile: +44-403-596893 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Dec 27, 1999 at 07:39:11PM +0000, Alex wrote: > > Yeah, it used to be Imperial College London, but now Easynet seems to be > taking over the world... (running FreeBSD mostly BTW). They have a > pretty damn fast link to NY, so I wouldn't be surprised if it was faster > even for some people in the US. > Hiya, not quite true. The cvsup.uk.freebsd.org server has always been run my me at Pavilion. The uk.freebsd.org domain was always running here at Pavilion, and when Easynet purchased us a few years ago they were mostly BSDI and NetBSD. We introduced them to FreeBSD, a model that's been followed since. John Polstra reminded me at FreeBSDCon that we were maybe the second or third cvsup server in the world :) Now in the UK cvsup.uk.freebsd.org is located in Telehouse on the Pavilion backbone (with Easynet routes, and an STM1 to New York), and cvsup2.uk.freebsd.org is running on Brian Somers (of user-ppp fame) machine in my office in Brighton. With respect to the FTP servers, when I inherited the running of the uk.freebsd.org name space we already had three FTP mirrors, at Imperial College (sunsite.doc.ic.ac.uk), the Hensa File Archive (Lancaster university) and Demon Internet. Since then we've acquired a further three FTP servers across the country. FTP4 was on the Easynet backbone in Easynet UK HQ, FTP5 is run by the UK User Group, and FTP6 is on Brian's machine. A little while ago I swapped FTP with FTP4 for two reasons, firstly due to the tightening of restrictions on the JANET (Join Academic Network) Imperial College had to reduce the number of concurrent connections to their FTP archive which serious caused UK FreeBSD people problems. Later the Imperial College machine suffered a major hardware failure that took it out of service for a couple of weeks. The new premier server is run by Easynet and so it is very easy for me to poke them if anything goes wrong, which to this day I've not had to do. Joe -- Josef Karthauser FreeBSD: Take the red pill and we'll show you just how Technical Manager deep the rabbit hole goes. (http://www.uk.freebsd.org) Pavilion Internet plc. [joe@pavilion.net, joe@freebsd.org, joe@tao.org.uk] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 28 5:48:33 1999 Delivered-To: freebsd-stable@freebsd.org Received: from ns1.aktrad.ru (ns1.aktrad.ru [195.218.140.4]) by hub.freebsd.org (Postfix) with ESMTP id 7A26B14A20 for ; Tue, 28 Dec 1999 05:48:28 -0800 (PST) (envelope-from hook@aktrad.ru) Received: from sloth (sloth.aktrad.ru [195.218.140.13]) by ns1.aktrad.ru (8.9.3/8.9.3) with SMTP id QAA70444 for ; Tue, 28 Dec 1999 16:48:26 +0300 (MSK) Message-ID: <0b1901bf513a$5c8c8810$0d8cdac3@aktrad.ru> From: "Gene Sokolov" To: Subject: Re: -lc vs. -lc_r (building Apache-PHP) Date: Tue, 28 Dec 1999 16:49:28 +0300 MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From: Dirk Froemberg > > Tom once stated: > > => => What's the magic and why doesn't the port know it? Why is -lc even > > => => in play if some of the components (-lmysqlclient) require -lc_r? > > => => Yours, > > => = > > => = libmysqlclient does not require -lc_r, because the library does > > => =not use threads. Only mysqld is threaded. > > => > > => Thank you, Tom, for this correction. However, this does not change > > => much. Some other extension wants threads then... > > = > > = Uhh.. highly unlikely. Almost none of PHP3 is thread-safe, and only a > > =bit of Apache is thread-safe. I doubt that anything in the Apache-PHP > > =port wants or needs threads. > > > > I did not put it in there myself :) At least one of the many extensions > > selected (I included the Makefile.inc with my original report) dragged > > the c_r with it... > > It's the mhash option causing the problem. I disabled it for now. > > Basically the mhash port doesn't seem to be able to deal with > FreeBSD's -pthread. I'll look at it to see whether the problem can > be easily be solved. By the way, is there a particular reason why the PHP port does not support Sybase/FreeTDS option? The PHP itself supports it. Gene Sokolov. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 28 6:47:36 1999 Delivered-To: freebsd-stable@freebsd.org Received: from kci.kciLink.com (kci.kciLink.com [204.117.82.1]) by hub.freebsd.org (Postfix) with ESMTP id 8B80D14D7E; Tue, 28 Dec 1999 06:47:33 -0800 (PST) (envelope-from khera@kciLink.com) Received: from onceler.kcilink.com (onceler.kciLink.com [204.117.82.2]) by kci.kciLink.com (Postfix) with ESMTP id 22D6BE89D; Tue, 28 Dec 1999 09:47:29 -0500 (EST) Received: (from khera@localhost) by onceler.kcilink.com (8.9.3/8.9.3) id JAA28247; Tue, 28 Dec 1999 09:47:29 -0500 (EST) (envelope-from khera@kci.kcilink.com) From: Vivek Khera MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14440.52608.752256.799982@onceler.kcilink.com> Date: Tue, 28 Dec 1999 09:47:28 -0500 (EST) To: Mike Smith Cc: stable@freebsd.org Subject: Re: panic In-Reply-To: <199912280626.WAA01224@mass.cdrom.com> References: <199912280626.WAA01224@mass.cdrom.com> X-Mailer: VM 6.72 under 21.1 (patch 8) "Bryce Canyon" XEmacs Lucid Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "MS" == Mike Smith writes: >> FreeBSD has a tendency to panic in out of mbuf situations. That >> shouldn't happen. MS> The semantics of "should" and "shouldn't" are debatable. In this case, MS> the panic is a simple indicator that the administrator hasn't correctly MS> tuned the system. Many would argue that this is a much better outcome MS> than a system that performs poorly for no immediately perceptible reason, MS> and it certainly encourages the prompt application of a correct MS> adjustment. I come from the school of thought that nothing should make the system crash. It should try its hardest to handle the workload thrown at it. Under no circumstances is a panic acceptable. The system should at worst drop some connections and issue a warning, or plod through and issue a warning. Kernel panic is *never* the right thing to do, and should be considered an error in the kernel. It is this kind of cavalier attitude towards system problems that makes people scared of using open source systems. -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Vivek Khera, Ph.D. Khera Communications, Inc. Internet: khera@kciLink.com Rockville, MD +1-301-545-6996 PGP & MIME spoken here http://www.kciLink.com/home/khera/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 28 7:56:40 1999 Delivered-To: freebsd-stable@freebsd.org Received: from inbox.org (inbox.org [216.22.145.8]) by hub.freebsd.org (Postfix) with ESMTP id 1227915174; Tue, 28 Dec 1999 07:56:36 -0800 (PST) (envelope-from bsd@inbox.org) Received: from localhost (bsd@localhost) by inbox.org (8.9.3/8.9.3) with SMTP id KAA14263; Tue, 28 Dec 1999 10:56:35 -0500 (EST) Date: Tue, 28 Dec 1999 10:56:35 -0500 (EST) From: "Mr. K." To: Bosko Milekic Cc: Mike Smith , Kip Macy , stable@FreeBSD.ORG Subject: Re: panic 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 > The solution would be to handle the shortage in other parts of the > code differently. If whoever posted the original message could of course > provide more detailed information regarding the crash, so that one can > actually know for a fact what and where the problem is, we wouldn't be > stuck here guessing. > I can reproduce at will (for the next hour or so until I recompile my kernel. Unfortunately, I get the message: savecore: /dev/rwd0s1b: Invalid Argument when the kernel reboots. I did verify that the panic message is out of mbufs though. Basically, if anyone thinks they could gain any useful information from a dump, I'll be happy to reproduce. All I need is info on how to obtain the dump. If it's going to just wind up as a duplicate of a known problem, or one that's never going to be solved, I'd just as well modify my tunables and forget about it. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 28 8: 8:41 1999 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 ABAB4153B6 for ; Tue, 28 Dec 1999 08:08:38 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (dcs@p19-dn02kiryunisiki.gunma.ocn.ne.jp [210.163.200.116]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id BAA14950; Wed, 29 Dec 1999 01:08:23 +0900 (JST) Message-ID: <3868DFBF.2DDA4D05@newsguy.com> Date: Wed, 29 Dec 1999 01:05:19 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Paulo Fragoso Cc: freebsd-stable@FreeBSD.ORG Subject: Re: kernel.conf References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Paulo Fragoso wrote: > > When I do upgrades (booting from cdrom and chosing UPGRADE option) always > the file /boot/kernel.conf are removed. Now before I start new upgrade I > make a copy for that file. > > I think upgrade script should move /boot/kernel.conf to > /boot/kernel.conf.old instead remove it. Good idea. Open a PR, and try to mention "sysinstall" in the subject line for it. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "Nice try, Lao Che." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 28 8:31: 2 1999 Delivered-To: freebsd-stable@freebsd.org Received: from hemorrhage.mindcrash.com (hemorrhage.mindcrash.com [209.51.189.194]) by hub.freebsd.org (Postfix) with ESMTP id A22AC14F86 for ; Tue, 28 Dec 1999 08:30:59 -0800 (PST) (envelope-from sheepman@mindcrash.com) Received: from localhost (sheepman@localhost) by hemorrhage.mindcrash.com (8.9.3/MindCrash-Custom-v2.4) with ESMTP id LAA00377 for ; Tue, 28 Dec 1999 11:31:08 -0500 (EST) Date: Tue, 28 Dec 1999 11:31:08 -0500 (EST) From: Sheepman To: stable@freebsd.org Subject: Kernel Options 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 am not sure if this is within the scope of this list, but.. Is there any documentation on all the kernel options that are present in /usr/src/sys/i386/conf/options.386? Thanks! Al --------------------------------------- "The world is headed for mutiny, when all we want is unity" -Creed --------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 28 8:36:53 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mass.cdrom.com (castles508.castles.com [208.214.165.72]) by hub.freebsd.org (Postfix) with ESMTP id 2C2A514DA0 for ; Tue, 28 Dec 1999 08:36:51 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id IAA03113; Tue, 28 Dec 1999 08:41:04 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912281641.IAA03113@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Paulo Fragoso Cc: freebsd-stable@FreeBSD.ORG Subject: Re: 3.4 ISO Images In-reply-to: Your message of "Tue, 28 Dec 1999 08:20:34 -0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 28 Dec 1999 08:41:04 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi, > > I've installed FreeBSD 3.4-RELEASE using iso image from ftp. It's working > fine but boot floppy emulation (boot from cdrom) was build with 3.2-STABLE > kernel. Is it ok? I think you'll find it's a 3.4 kernel; there was a mistake made at one point when sysinstall was rebuilt such that it thinks it's a 3.2-stable snapshot. This is just a cosmetic error for the most part. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 28 8:52:57 1999 Delivered-To: freebsd-stable@freebsd.org Received: from tricord.system.pl (tricord.system.pl [195.205.185.10]) by hub.freebsd.org (Postfix) with ESMTP id 426C714ECA for ; Tue, 28 Dec 1999 08:51:42 -0800 (PST) (envelope-from saper@system.pl) Received: from localhost (saper@localhost [127.0.0.1]) by tricord.system.pl (SYSTEM Internet) with ESMTP id RAA02595; Tue, 28 Dec 1999 17:50:35 +0100 (MET) Date: Tue, 28 Dec 1999 17:50:31 +0100 (MET) From: Marcin Cieslak To: "Mr. K." Cc: stable@FreeBSD.ORG Subject: Re: panic (savecore: Invalid Argument) 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, 28 Dec 1999, Mr. K. wrote: > kernel. Unfortunately, I get the message: > savecore: /dev/rwd0s1b: Invalid Argument > when the kernel reboots. > mbufs though. From BUGS section of dumpon(1): Dumpon currently allows only devices with minor number 1 to be used as dump devices. % ls -l /dev/*wd0b crw-r----- 1 root operator 3, 1 30 Mar 1999 /dev/rwd0b brw-r----- 1 root operator 0, 1 30 Mar 1999 /dev/wd0b % ls -l /dev/*wd0s1b crw-r----- 1 root wheel 3, 0x00020001 2 Wrz 11:36 /dev/rwd0s1b brw-r----- 1 root wheel 0, 0x00020001 2 Wrz 11:36 /dev/wd0s1b Shouldn't be /dev/wd0b used as a dump device? Also, try using serial console to catch panic messages. -- << Marcin Cieslak // saper@system.pl >> ----------------------------------------------------------------- SYSTEM Internet Provider http://www.system.pl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 28 9:23:11 1999 Delivered-To: freebsd-stable@freebsd.org Received: from freeway.dcfinc.com (cx74889-a.phnx3.az.home.com [24.1.193.157]) by hub.freebsd.org (Postfix) with ESMTP id AC70B154ED for ; Tue, 28 Dec 1999 09:22:55 -0800 (PST) (envelope-from chad@freeway.dcfinc.com) Received: (from chad@localhost) by freeway.dcfinc.com (8.8.8/8.8.8) id KAA12868; Tue, 28 Dec 1999 10:21:25 -0700 (MST) (envelope-from chad) From: "Chad R. Larson" Message-Id: <199912281721.KAA12868@freeway.dcfinc.com> Subject: Re: Huge differences in suid programs ? In-Reply-To: from Brad Knowles at "Dec 28, 99 11:20:52 am" To: blk@skynet.be (Brad Knowles) Date: Tue, 28 Dec 1999 10:21:25 -0700 (MST) Cc: jedgar@fxp.org, mark@dogma.freebsd-uk.eu.org, stanb@netcom.com, freebsd-stable@FreeBSD.ORG Reply-To: chad@DCFinc.com X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > in /etc/make.conf, unchanged files will not have their modification time > > changed. > > I like this option! Thank you for telling me about it! I'm > going to have to change that on my systems.... Just so you know... The -C option to install causes install to make a temporary copy of the "new" file in the target directory, and then does a byte-by-byte compare with the "old" one. If they're different, it deletes the old and renames the new. It will be noticably slower. -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org larson1@home.net DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 28 9:26:36 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail2.uniserve.com (mail2.uniserve.com [204.244.156.7]) by hub.freebsd.org (Postfix) with ESMTP id BD90E14D67; Tue, 28 Dec 1999 09:26:26 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca ([204.244.186.218]) by mail2.uniserve.com with smtp (Exim 3.03 #4) id 1230O9-0007BF-00; Tue, 28 Dec 1999 09:26:25 -0800 Date: Tue, 28 Dec 1999 09:26:23 -0800 (PST) From: Tom X-Sender: tom@shell.uniserve.ca To: Mike Smith Cc: "Mr. K." , stable@freebsd.org Subject: Re: panic In-Reply-To: <199912280626.WAA01224@mass.cdrom.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, 27 Dec 1999, Mike Smith wrote: > > > > Totally untweaked kernel. I didn't get to tweaking yet. I shouldn't have > > > > to tweak anything to make the kernel not panic, though... Not > > > > complaining, just pre-empting possible flames. > > > > > > That's completely incorrect. > > > > I don't know what part of the above you say is incorrect. > > > > FreeBSD has a tendency to panic in out of mbuf situations. That > > shouldn't happen. > > The semantics of "should" and "shouldn't" are debatable. In this case, > the panic is a simple indicator that the administrator hasn't correctly > tuned the system. Many would argue that this is a much better outcome > than a system that performs poorly for no immediately perceptible reason, > and it certainly encourages the prompt application of a correct > adjustment. Well, in FreeBSD 2.2.x, an "Out of mbufs!" message was printed on the console, and there was no panic. > -- > \\ Give a man a fish, and you feed him for a day. \\ Mike Smith > \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org > \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 28 9:28:29 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail2.uniserve.com (mail2.uniserve.com [204.244.156.7]) by hub.freebsd.org (Postfix) with ESMTP id 7114F14C3E; Tue, 28 Dec 1999 09:28:27 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca ([204.244.186.218]) by mail2.uniserve.com with smtp (Exim 3.03 #4) id 1230Q3-0007FT-00; Tue, 28 Dec 1999 09:28:23 -0800 Date: Tue, 28 Dec 1999 09:28:21 -0800 (PST) From: Tom X-Sender: tom@shell.uniserve.ca To: Mike Smith Cc: Kip Macy , "Mr. K." , stable@freebsd.org Subject: Re: panic In-Reply-To: <199912280630.WAA01257@mass.cdrom.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, 27 Dec 1999, Mike Smith wrote: > > > I was not root when this happened, so, basically, you're saying that > > > freebsd is not meant for a production environment where untrusted users > > > have telnet access? > > > > As far as I can tell, yes. Until default per user mbuf limitations or some > > such thing is in place no amount of mbufs will prevent intentionally bad > > code from downing the machine. My understanding is that this was not a > > problem in 2.x. > > It's a fundamental problem with the BSD mbuf architecture. It's not > something that as many people were seeing with 2.2 simply because people > weren't pushing systems as hard back then. Back then? People were running the same junk back then as they are now. In fact, I still have a _lot_ of 2.2 systems around, some that are woefully overloaded, but they never panic. Tom Uniserve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 28 9:39:35 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mass.cdrom.com (castles508.castles.com [208.214.165.72]) by hub.freebsd.org (Postfix) with ESMTP id D78E514D5B for ; Tue, 28 Dec 1999 09:39:31 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id JAA03338; Tue, 28 Dec 1999 09:44:10 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912281744.JAA03338@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Tom Cc: "Mr. K." , stable@freebsd.org Subject: Re: panic In-reply-to: Your message of "Tue, 28 Dec 1999 09:26:23 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 28 Dec 1999 09:44:10 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Mon, 27 Dec 1999, Mike Smith wrote: > > > > > > Totally untweaked kernel. I didn't get to tweaking yet. I shouldn't have > > > > > to tweak anything to make the kernel not panic, though... Not > > > > > complaining, just pre-empting possible flames. > > > > > > > > That's completely incorrect. > > > > > > I don't know what part of the above you say is incorrect. > > > > > > FreeBSD has a tendency to panic in out of mbuf situations. That > > > shouldn't happen. > > > > The semantics of "should" and "shouldn't" are debatable. In this case, > > the panic is a simple indicator that the administrator hasn't correctly > > tuned the system. Many would argue that this is a much better outcome > > than a system that performs poorly for no immediately perceptible reason, > > and it certainly encourages the prompt application of a correct > > adjustment. > > Well, in FreeBSD 2.2.x, an "Out of mbufs!" message was printed on the > console, and there was no panic. That's not correct. In a number of cases, all families will print "out of mbufs" messages. However most families also have code paths which will fail catastrophically in case of mbuf shortage. (This has, for the first time, been substantially reduced in 4.0). You're welcome to go look at the code; I've been over large parts of it three times now with other people working on this issue under 2.x, 3.x and now under 4.x (where Bosko has finally started getting bits committed). -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 28 9:52:36 1999 Delivered-To: freebsd-stable@freebsd.org Received: from dozer.skynet.be (dozer.skynet.be [195.238.2.36]) by hub.freebsd.org (Postfix) with ESMTP id 582CE14C3E for ; Tue, 28 Dec 1999 09:52:33 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by dozer.skynet.be (8.9.3/odie-relay-v1.0) with ESMTP id SAA22889; Tue, 28 Dec 1999 18:51:29 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@foxbert.skynet.be Message-Id: In-Reply-To: <199912281721.KAA12868@freeway.dcfinc.com> References: <199912281721.KAA12868@freeway.dcfinc.com> Date: Tue, 28 Dec 1999 18:37:54 +0100 To: chad@DCFinc.com From: Brad Knowles Subject: Re: Huge differences in suid programs ? Cc: jedgar@fxp.org, mark@dogma.freebsd-uk.eu.org, stanb@netcom.com, freebsd-stable@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 10:21 AM -0700 1999/12/28, Chad R. Larson wrote: > The -C option to install causes install to make a temporary copy of the > "new" file in the target directory, and then does a byte-by-byte compare > with the "old" one. If they're different, it deletes the old and > renames the new. Sigh. It can't do the comparison with the new file in it's current location, then do the copy if they're different? That would seem to be the intelligent thing to do. > It will be noticably slower. Double sigh. Thanks for the warning. Although it would keep my security notices from being too huge, it otherwise seems to be an option I'm unlikely to use. -- These are my opinions -- not to be taken as official Skynet policy ____________________________________________________________________ |o| Brad Knowles, Belgacom Skynet NV/SA |o| |o| Systems Architect, News & FTP Admin Rue Col. Bourg, 124 |o| |o| Phone/Fax: +32-2-706.11.11/12.49 B-1140 Brussels |o| |o| http://www.skynet.be Belgium |o| \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. Unix is very user-friendly. It's just picky who its friends are. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 28 10: 1: 7 1999 Delivered-To: freebsd-stable@freebsd.org Received: from oracle.dsuper.net (oracle.dsuper.net [205.205.255.1]) by hub.freebsd.org (Postfix) with ESMTP id 5B5B214EBB; Tue, 28 Dec 1999 10:01:02 -0800 (PST) (envelope-from bmilekic@dsuper.net) Received: from oracle.dsuper.net (oracle.dsuper.net [205.205.255.1]) by oracle.dsuper.net (8.9.3/8.9.3) with ESMTP id NAA19577; Tue, 28 Dec 1999 13:00:58 -0500 (EST) Date: Tue, 28 Dec 1999 13:00:58 -0500 (EST) From: Bosko Milekic To: Tom Cc: Mike Smith , "Mr. K." , stable@FreeBSD.ORG Subject: Re: panic 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, 28 Dec 1999, Tom wrote: !>> The semantics of "should" and "shouldn't" are debatable. In this case, !>> the panic is a simple indicator that the administrator hasn't correctly !>> tuned the system. Many would argue that this is a much better outcome !>> than a system that performs poorly for no immediately perceptible reason, !>> and it certainly encourages the prompt application of a correct !>> adjustment. !> !> Well, in FreeBSD 2.2.x, an "Out of mbufs!" message was printed on the !>console, and there was no panic. Right, and then do you know what happen? Most likely, you would page fault "somewhere" else in the code, because of that calling code would again not end up being able to handle the NULL pointer or, worse yet, not even check for it. Personally, I don't believe that "solving" the problem originally by inserting an explicit panic() on failure was a good solution. In fact, it basically transported the problem over to the mbuf code, which can't predict the context of the caller, in the sense that it's difficult to decide *how* to fail when it has to. Thus, the "wait" code was written to modify the behavior of the code in the event that a shortage occurs. This, as I mentionned in my previous post, does _not_ excuse any of the calling code from properly checking for failure. You'll find many such kludges around the NFS code, for example. What's important to understand is that allocation of an mbuf even with M_WAIT does *not* guarantee success because if we're short, it's frankly rather useless to wait forever. With that said, since you're running -STABLE as opposed to -CURRENT, the wait code, nor the ulimit on sockbuf space code for that matter, have been MFCed at this time. "To MFC or not to MFC" is not a decision that I am to make, since I don't represent the project `officially.' Therefore, you can either merge them over yourself (it's not that difficult) -- that is, if you're somewhat familiar with the code -- or wait and tune your system while waiting accordingly. If whoever would like to offer further complaints about something not being the way it should, I have to mention again that "whoever" should equally provide detailed information on the crash, which in this case has not yet been done; therefore, all that I've mentionned above is assuming of course that the crash is the _direct_ result of the explicit panic() in m_retry. Bosko. ...... . . . . . . . . . . . . . Bosko Milekic -- bmilekic@dsuper.net . . . . . . . . . . . ...... . . WWW: http://pages.infinit.net/bmilekic/ . ................................................ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 28 10: 2:50 1999 Delivered-To: freebsd-stable@freebsd.org Received: from inbox.org (inbox.org [216.22.145.8]) by hub.freebsd.org (Postfix) with ESMTP id 744C014D5B for ; Tue, 28 Dec 1999 10:02:47 -0800 (PST) (envelope-from bsd@inbox.org) Received: from localhost (bsd@localhost) by inbox.org (8.9.3/8.9.3) with SMTP id NAA18145; Tue, 28 Dec 1999 13:02:28 -0500 (EST) Date: Tue, 28 Dec 1999 13:02:28 -0500 (EST) From: "Mr. K." To: Marcin Cieslak Cc: stable@FreeBSD.ORG Subject: Re: panic (savecore: Invalid Argument) 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, 28 Dec 1999, Marcin Cieslak wrote: > On Tue, 28 Dec 1999, Mr. K. wrote: > > > kernel. Unfortunately, I get the message: > > savecore: /dev/rwd0s1b: Invalid Argument > > when the kernel reboots. > > From BUGS section of dumpon(1): > > Dumpon currently allows only devices with minor number 1 to be used as > dump devices. > > % ls -l /dev/*wd0b > crw-r----- 1 root operator 3, 1 30 Mar 1999 /dev/rwd0b > brw-r----- 1 root operator 0, 1 30 Mar 1999 /dev/wd0b > % ls -l /dev/*wd0s1b > crw-r----- 1 root wheel 3, 0x00020001 2 Wrz 11:36 /dev/rwd0s1b > brw-r----- 1 root wheel 0, 0x00020001 2 Wrz 11:36 /dev/wd0s1b > > Shouldn't be /dev/wd0b used as a dump device? > :) now I get savecore: /dev/rwd0b: Invalid Argument Ohwell, I don't have any more time to spend on this. It seems like it's a well enough known problem though... > Also, try using serial console to catch panic messages. > The null modem cable is in the mail :) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 28 10:40:37 1999 Delivered-To: freebsd-stable@freebsd.org Received: from smtp10.atl.mindspring.net (smtp10.atl.mindspring.net [207.69.200.246]) by hub.freebsd.org (Postfix) with ESMTP id 52DAB14DAB for ; Tue, 28 Dec 1999 10:40:26 -0800 (PST) (envelope-from mvh@ix.netcom.com) Received: from netcom1.netcom.com (lai-ca3b-129.ix.netcom.com [209.110.241.129]) by smtp10.atl.mindspring.net (8.9.3/8.8.5) with ESMTP id NAA26134; Tue, 28 Dec 1999 13:40:02 -0500 (EST) Received: by netcom1.netcom.com (Postfix, from userid 1000) id C5FDCA5FF3; Tue, 28 Dec 1999 10:39:28 -0800 (PST) From: Mike Harding To: Cy.Schubert@uumail.gov.bc.ca Cc: kevin@tarvalon.net, freebsd-stable@freebsd.org In-reply-to: <199912262024.MAA37276@cwsys.cwsent.com> (message from Cy Schubert - ITSD Open Systems Group on Sun, 26 Dec 1999 12:24:10 -0800) Subject: Re: X11 References: <199912262024.MAA37276@cwsys.cwsent.com> Message-Id: <19991228183928.C5FDCA5FF3@netcom1.netcom.com> Date: Tue, 28 Dec 1999 10:39:28 -0800 (PST) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I was just bit by this as well - I rebuilt my X server and was unable to log in... - Mike Harding Reply-To: Cy Schubert - ITSD Open Systems Group From: Cy Schubert - ITSD Open Systems Group X-OS: FreeBSD 3.4-RELEASE X-Sender: cy Cc: freebsd-stable@freebsd.org Content-Type: text/plain; charset=us-ascii Date: Sun, 26 Dec 1999 12:24:10 -0800 Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.ORG Precedence: bulk X-RULES: lists In message , Kev in Entringer writes: > Thanks for the suggestion. I suspect that this was the problem, however X > is still not working. The following no happens: > > Dec 26 11:29:13 discord login: ROOT LOGIN (root) ON ttyv3 > Dec 26 11:29:14 discord Xwrapper: unable to dlopen(/usr/lib/pam_unix.so) > Dec 26 11:29:14 discord > Xwrapper: [dlerror: /usr/lib/pam_unix.so: Undefined symb > ol "crypt"] > Dec 26 11:29:14 discord Xwrapper: adding faulty > module: /usr/lib/pam_unix.so It appears that the problem was fixed in -current and not in -stable: markm 1999/09/30 11:53:34 PDT Modified files: lib/libpam/modules/pam_unix Makefile Log: Add libcrypt. This previously/coincidentally worked for login, because login was already linked against it, but others have a problem. Revision Changes Path 1.4 +3 -3 src/lib/libpam/modules/pam_unix/Makefile Even though the patch is for -current, it applies cleanly to -stable. Would someone please MFC this. Kevin, apply the following patch to and rebuild pam_unix. I've modified the "old" $FreeBSD$ to allow the patch to apply cleanly. =================================================================== RCS file: /home/ncvs/src/lib/libpam/modules/pam_unix/Makefile,v retrieving revision 1.3 retrieving revision 1.4 diff -p -u -r1.3 -r1.4 --- src/lib/libpam/modules/pam_unix/Makefile 1999/05/08 01:59:27 1.3 +++ /home/ncvs/src/lib/libpam/modules/pam_unix/Makefile 1999/09/30 18:53:34 1.4 @@ -22,7 +22,7 @@ # OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF # SUCH DAMAGE. # -# $FreeBSD: src/lib/libpam/modules/pam_unix/Makefile,v 1.2.2.1 1999/05/08 21:32:00 jdp Exp $ +# $FreeBSD: src/lib/libpam/modules/pam_unix/Makefile,v 1.3 1999/05/08 01:59:27 jdp Exp $ PAMDIR= ${.CURDIR}/../../../../contrib/libpam @@ -32,8 +32,8 @@ SRCS= pam_unix.c CFLAGS+= -Wall CFLAGS+= -I${PAMDIR}/libpam/include CFLAGS+= -I${.CURDIR}/../../libpam -DPADD+= ${LIBUTIL} ${LIBGCC_PIC} -LDADD+= -lutil -lgcc_pic +DPADD+= ${LIBUTIL} ${LIBGCC_PIC} ${LIBCRYPT} +LDADD+= -lutil -lgcc_pic -lcrypt INTERNALLIB= yes INTERNALSTATICLIB=yes Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 Sun/DEC Team, UNIX Group Internet: Cy.Schubert@uumail.gov.bc.ca ITSD Province of BC "e**(i*pi)+1=0" 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 Dec 28 10:43:54 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.rdc1.ct.home.com (ha1.rdc1.ct.home.com [24.2.0.66]) by hub.freebsd.org (Postfix) with ESMTP id EF5F515008 for ; Tue, 28 Dec 1999 10:43:46 -0800 (PST) (envelope-from tsikora@home.com) Received: from home.com ([24.2.168.186]) by mail.rdc1.ct.home.com (InterMail v4.01.01.07 201-229-111-110) with ESMTP id <19991228184345.QOCU9446.mail.rdc1.ct.home.com@home.com> for ; Tue, 28 Dec 1999 10:43:45 -0800 Message-ID: <386904D7.11DDA425@home.com> Date: Tue, 28 Dec 1999 13:43:35 -0500 From: Ted Sikora Reply-To: tsikora@powerusersbbs.com Organization: Jtl Development X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.4-STABLE i386) X-Accept-Language: en-US,en-GB MIME-Version: 1.0 To: "freebsd-stable@FreeBSD.ORG" Subject: linux_clone(465) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG /kernel: linux_clone(465): does not work with SMP yet Has this been addressed in current with the other Linux ioctls? This prevents me from installing Staroffice 5.1a. I was able to install a tarred installation from a Linux machine however the messages persist. How can I turn the messages off. Will # soffice >dev/null work? -- Ted Sikora Jtl Development Group tsikora@powerusersbbs.com http://powerusersbbs.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 28 12:29:34 1999 Delivered-To: freebsd-stable@freebsd.org Received: from deimos.ldc.net (deimos.ldc.net [195.230.141.3]) by hub.freebsd.org (Postfix) with ESMTP id 21E0415515 for ; Tue, 28 Dec 1999 12:29:26 -0800 (PST) (envelope-from sasha@deimos.ldc.net) Received: (from sasha@localhost) by deimos.ldc.net (8.9.3/8.9.3) id WAA11100 for FreeBSD-stable@FreeBSD.ORG; Tue, 28 Dec 1999 22:29:06 +0200 (EET) Date: Tue, 28 Dec 1999 22:29:06 +0200 (EET) From: Sasha Nazarenko Message-Id: <199912282029.WAA11100@deimos.ldc.net> To: FreeBSD-stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG help To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 28 14:29:18 1999 Delivered-To: freebsd-stable@freebsd.org Received: from luna.lyris.net (luna.shelby.com [207.90.155.6]) by hub.freebsd.org (Postfix) with ESMTP id CF24A1555B; Tue, 28 Dec 1999 14:29:15 -0800 (PST) (envelope-from kip@lyris.com) Received: from luna.shelby.com by luna.lyris.net (8.9.1b+Sun/SMI-SVR4) id OAA04014; Tue, 28 Dec 1999 14:28:54 -0800 (PST) Received: from (luna.shelby.com [207.90.155.6]) by luna.shelby.com with SMTP (MailShield v1.50); Tue, 28 Dec 1999 14:28:54 -0800 Date: Tue, 28 Dec 1999 14:28:54 -0800 (PST) From: Kip Macy To: Vivek Khera Cc: Mike Smith , stable@freebsd.org Subject: Re: panic In-Reply-To: <14440.52608.752256.799982@onceler.kcilink.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SMTP-HELO: luna X-SMTP-MAIL-FROM: kip@lyris.com X-SMTP-RCPT-TO: khera@kciLink.com,msmith@freebsd.org,stable@freebsd.org X-SMTP-PEER-INFO: luna.shelby.com [207.90.155.6] Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 28 Dec 1999, Vivek Khera wrote: > >>>>> "MS" == Mike Smith writes: > > >> FreeBSD has a tendency to panic in out of mbuf situations. That > >> shouldn't happen. > > MS> The semantics of "should" and "shouldn't" are debatable. In this case, > MS> the panic is a simple indicator that the administrator hasn't correctly > MS> tuned the system. Many would argue that this is a much better outcome > MS> than a system that performs poorly for no immediately perceptible reason, > MS> and it certainly encourages the prompt application of a correct > MS> adjustment. > > I come from the school of thought that nothing should make the system > crash. It should try its hardest to handle the workload thrown at it. > Under no circumstances is a panic acceptable. The system should at > worst drop some connections and issue a warning, or plod through and > issue a warning. Kernel panic is *never* the right thing to do, and > should be considered an error in the kernel. > > It is this kind of cavalier attitude towards system problems that > makes people scared of using open source systems. > I think it is ultimately a religious issue and not a customer issue which is why FreeBSD has the strengths that it does and the weaknesses that it does. David Greenman backed me up when I said the same thing. However, there are numerous others in the FreeBSD group who believe that it is the users' responsibility. -Kip To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 28 14:42:20 1999 Delivered-To: freebsd-stable@freebsd.org Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (Postfix) with ESMTP id D6A1F14EB9 for ; Tue, 28 Dec 1999 14:42:10 -0800 (PST) (envelope-from ben@scientia.demon.co.uk) Received: from strontium.scientia.demon.co.uk ([192.168.91.36] ident=ben) by scientia.demon.co.uk with smtp (Exim 3.092 #1) id 1234gt-000C9n-00; Tue, 28 Dec 1999 22:02:03 +0000 Date: Tue, 28 Dec 1999 22:02:02 +0000 From: Ben Smithurst To: Brad Knowles Cc: chad@DCFinc.com, jedgar@fxp.org, mark@dogma.freebsd-uk.eu.org, stanb@netcom.com, freebsd-stable@FreeBSD.ORG Subject: Re: Huge differences in suid programs ? Message-ID: <19991228220202.C46546@strontium.scientia.demon.co.uk> References: <199912281721.KAA12868@freeway.dcfinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brad Knowles wrote: > At 10:21 AM -0700 1999/12/28, Chad R. Larson wrote: > >> The -C option to install causes install to make a temporary copy of the >> "new" file in the target directory, and then does a byte-by-byte compare >> with the "old" one. If they're different, it deletes the old and >> renames the new. > > Sigh. It can't do the comparison with the new file in it's > current location, then do the copy if they're different? That would > seem to be the intelligent thing to do. You mean compare /usr/obj/usr/src/bin/sh with /bin/sh (or whatever the path is)? I don't think that would work, since /usr/obj/... files aren't stripped, and the installed versions are. -- Ben Smithurst | PGP: 0x99392F7D ben@scientia.demon.co.uk | key available from keyservers and | ben+pgp@scientia.demon.co.uk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 28 15:54:11 1999 Delivered-To: freebsd-stable@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id 28B4E15500 for ; Tue, 28 Dec 1999 15:53:58 -0800 (PST) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40322>; Wed, 29 Dec 1999 10:44:30 +1100 Content-return: prohibited Date: Wed, 29 Dec 1999 10:53:46 +1100 From: Peter Jeremy Subject: Re: /bin/test broken ? In-reply-to: <199912280908.BAA69692@gndrsh.dnsmgr.net>; from freebsd@gndrsh.dnsmgr.net on Tue, Dec 28, 1999 at 08:08:21PM +1100 To: freebsd-stable@freebsd.org Message-Id: <99Dec29.104430est.40322@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0i Content-type: text/plain; charset=us-ascii References: <1893.946371495@axl.noc.iafrica.com> <199912280908.BAA69692@gndrsh.dnsmgr.net> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 1999-Dec-28 20:08:21 +1100, "Rodney W. Grimes" wrote: >The syntax is reasonable, as /bin/[ or /bin/test is about the only way >one would overide a builtin [, should some shell implement test as >a builtin. Of course, that assumes that the shell doesn't have other problems with its parsing: $ zsh -c '[ 1 -ne 0 ] && echo correct' correct $ zsh -c '/bin/[ 1 -ne 0 ] && echo correct' zsh: bad pattern: /bin/[ $ (Found by accident whilst looking into the original problem - I haven't, but probably should, report it as a bug in zsh 3.0.5). Peter -- Peter Jeremy (VK2PJ) peter.jeremy@alcatel.com.au Alcatel Australia Limited 41 Mandible St Phone: +61 2 9690 5019 ALEXANDRIA NSW 2015 Fax: +61 2 9690 5982 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 28 17: 6:18 1999 Delivered-To: freebsd-stable@freebsd.org Received: from pluto.psn.net (pluto.psn.net [207.211.58.12]) by hub.freebsd.org (Postfix) with ESMTP id 7B8A314E26 for ; Tue, 28 Dec 1999 17:06:16 -0800 (PST) (envelope-from will@shadow.blackdawn.com) Received: from 14-078.008.popsite.net ([209.69.195.78] helo=shadow.blackdawn.com) by pluto.psn.net with esmtp (PSN Internet Service 3.12 #1) id 1237Yy-0005Yz-00; Tue, 28 Dec 1999 18:06:05 -0700 Received: (from will@localhost) by shadow.blackdawn.com (8.9.3/8.9.3) id UAA37095; Tue, 28 Dec 1999 20:06:01 -0500 (EST) (envelope-from will) Message-ID: X-Mailer: XFMail 1.3.1 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <99Dec29.104430est.40322@border.alcanet.com.au> Date: Tue, 28 Dec 1999 20:06:01 -0500 (EST) Reply-To: Will Andrews From: Will Andrews To: Peter Jeremy Subject: Re: /bin/test broken ? Cc: freebsd-stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 28-Dec-99 Peter Jeremy wrote: > $ zsh -c '[ 1 -ne 0 ] && echo correct' > correct > $ zsh -c '/bin/[ 1 -ne 0 ] && echo correct' > zsh: bad pattern: /bin/[ > $ > > (Found by accident whilst looking into the original problem - I haven't, > but probably should, report it as a bug in zsh 3.0.5). I don't think so. It's a regex thing - you're supposed to escape the [ since it's parsed by the shell as a regex.. (just like parentheses, semicolons, stars, tildes, and so on). <2 5011-0> (99-12-28 20:02:04) [will@shadow ~]% /bin/\[ 1 -ne 0 && echo correct correct <2 5012-0> (99-12-28 20:02:11) [will@shadow ~]% [ 1 -ne 0 ] && echo correct correct FWIW: <2 5002-0> (99-12-28 20:03:38) [will@shadow ~]% pkg_info -Ia | grep zsh zsh-3.1.6 The Z shell (development version) <2 5003-0> (99-12-28 20:03:39) [will@shadow ~]% grep will /etc/passwd will:*:1000:1000:Will Andrews:/home/will:/usr/local/bin/zsh ..although I'm not sure why /bin/[ behaves like this: <2 5004-0> (99-12-28 20:03:47) [will@shadow ~]% /bin/\[ 1 -ne 0 ] && echo correct [: ]: unexpected operator *shrug* could be some weird kink. :-) -- Will Andrews GCS/E/S @d- s+:+>+:- a--->+++ C++ UB++++ P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP+>+++ t++ 5 X++ R+ tv+ b++>++++ DI+++ D+ G++>+++ e->++++ h! r-->+++ y? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 28 17:21: 0 1999 Delivered-To: freebsd-stable@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id 420E115580 for ; Tue, 28 Dec 1999 17:20:57 -0800 (PST) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id RAA71526; Tue, 28 Dec 1999 17:15:00 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <199912290115.RAA71526@gndrsh.dnsmgr.net> Subject: Re: /bin/test broken ? In-Reply-To: from Will Andrews at "Dec 28, 1999 08:06:01 pm" To: andrews@TECHNOLOGIST.COM (Will Andrews) Date: Tue, 28 Dec 1999 17:14:59 -0800 (PST) Cc: peter.jeremy@alcatel.com.au (Peter Jeremy), freebsd-stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On 28-Dec-99 Peter Jeremy wrote: > > $ zsh -c '[ 1 -ne 0 ] && echo correct' > > correct > > $ zsh -c '/bin/[ 1 -ne 0 ] && echo correct' > > zsh: bad pattern: /bin/[ > > $ > > > > (Found by accident whilst looking into the original problem - I haven't, > > but probably should, report it as a bug in zsh 3.0.5). > > I don't think so. It's a regex thing - you're supposed to escape the [ since > it's parsed by the shell as a regex.. (just like parentheses, semicolons, > stars, tildes, and so on). Things inside single quotes (') are not subject to regex unless the shell is broken. From sh(1): Single Quotes Enclosing characters in single quotes preserves the literal mean- ing of all the characters (except single quotes, making it impos- sible to put single-quotes in a single-quoted string). Thus, zsh is broken :-(. Here is a working /bin/csh on FreeBSD 3.3 with a working /bin/[ doing this thing correctly: gndrsh:root {1134}# sh -c '/bin/[ 1 -ne 0 ] && echo correct' correct And a working /bin/sh FreeBSD 3.3 with a working /bin/[ doing this correctly: # sh -c '/bin/[ 1 -ne 0 ] && echo correct' correct -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 28 17:33:15 1999 Delivered-To: freebsd-stable@freebsd.org Received: from jade.chc-chimes.com (jade.chc-chimes.com [216.28.46.6]) by hub.freebsd.org (Postfix) with ESMTP id CF5BC14F3C for ; Tue, 28 Dec 1999 17:33:13 -0800 (PST) (envelope-from billf@chc-chimes.com) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id 8F5921C5D; Tue, 28 Dec 1999 20:32:24 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by jade.chc-chimes.com (Postfix) with ESMTP id 7F9033847; Tue, 28 Dec 1999 20:32:24 -0500 (EST) Date: Tue, 28 Dec 1999 20:32:24 -0500 (EST) From: Bill Fumerola To: "Rodney W. Grimes" Cc: Will Andrews , Peter Jeremy , freebsd-stable@FreeBSD.ORG Subject: Re: /bin/test broken ? In-Reply-To: <199912290115.RAA71526@gndrsh.dnsmgr.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 Tue, 28 Dec 1999, Rodney W. Grimes wrote: > Things inside single quotes (') are not subject to regex unless the > shell is broken. From sh(1): > Single Quotes > Enclosing characters in single quotes preserves the literal mean- > ing of all the characters (except single quotes, making it impos- > sible to put single-quotes in a single-quoted string). Rod, Had you actually read his original post you would have seen that the [ wasn't in single quotes in the example he provided. I have no idea what relevence the above section is. -- - bill fumerola - billf@chc-chimes.com - BF1560 - computer horizons corp - - ph:(800) 252-2421 - bfumerol@computerhorizons.com - billf@FreeBSD.org - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 28 22:35: 3 1999 Delivered-To: freebsd-stable@freebsd.org Received: from pooh.elsevier.nl (p105.as1.naas1.eircom.net [159.134.254.105]) by hub.freebsd.org (Postfix) with ESMTP id 6EC721511E for ; Tue, 28 Dec 1999 22:34:57 -0800 (PST) (envelope-from steve@pooh.elsevier.nl) Received: (from steve@localhost) by pooh.elsevier.nl (8.9.3/8.9.3) id GAA21225; Wed, 29 Dec 1999 06:34:55 GMT (envelope-from steve) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Wed, 29 Dec 1999 06:34:34 -0000 (GMT) From: "Steve O'Hara-Smith" To: freebsd-stable@freebsd.org Subject: /dev/pcaudio unusable Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Is anyone else seeing this effect ? su-2.03# cat bork.au > /dev/pcaudio cat: stdout: Device busy No matter what I do I get this (even in single user mode just after a cold boot -s). This has been happening for a while now (at least beack to 3.3-RELEASE). Is it me, is it a bug ? I wind up here because I haven't yet succeeded in getting the ESS-SOLO1 in this laptop to work (OSS did for a while then it got terribly unstable - anyway it is bigger than my kernel :(). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 29 0:48:11 1999 Delivered-To: freebsd-stable@freebsd.org Received: from sonet.crimea.ua (OTC-sl3-FLY.CRIS.NET [212.110.136.71]) by hub.freebsd.org (Postfix) with ESMTP id C43BD14D58 for ; Wed, 29 Dec 1999 00:47:54 -0800 (PST) (envelope-from phantom@scorpion.crimea.ua) Received: (from uucp@localhost) by sonet.crimea.ua (8.9.3/8.9.3) with UUCP id KAA12603; Wed, 29 Dec 1999 10:54:05 +0300 (MSK) Received: (from phantom@localhost) by scorpion.crimea.ua (8.8.8/8.8.5+ssl+keepalive) id KAA27393; Wed, 29 Dec 1999 10:35:11 +0300 (MSK) Date: Wed, 29 Dec 1999 10:35:11 +0300 From: Alexey Zelkin To: Sheepman Cc: stable@FreeBSD.ORG Subject: Re: Kernel Options Message-ID: <19991229103511.A27292@scorpion.crimea.ua> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.7i In-Reply-To: X-Operating-System: FreeBSD 2.2.7-RELEASE i386 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi, On Tue, Dec 28, 1999 at 11:31:08AM -0500, Sheepman wrote: > I am not sure if this is within the scope of this list, but.. > Is there any documentation on all the kernel options that are present in > /usr/src/sys/i386/conf/options.386? 1. Comments in /sys/i386/conf/LINT 2. handbook 3. FAQ -- /* Alexey Zelkin && phantom@cris.net */ /* Tavric National University && phantom@crimea.edu */ /* http://www.ccssu.crimea.ua/~phantom && phantom@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 Dec 29 4:22:47 1999 Delivered-To: freebsd-stable@freebsd.org Received: from netcom.com (netcom3.netcom.com [199.183.9.103]) by hub.freebsd.org (Postfix) with ESMTP id 5087814E21 for ; Wed, 29 Dec 1999 04:22:44 -0800 (PST) (envelope-from stanb@netcom.com) Received: (from stanb@localhost) by netcom.com (8.9.3/8.9.3) id EAA22783 for freebsd-stable@freebsd.org; Wed, 29 Dec 1999 04:22:42 -0800 (PST) From: Stan Brown Message-Id: <199912291222.EAA22783@netcom.com> Subject: Dump problem (soft updates?) To: freebsd-stable@freebsd.org (FreeBSD Stable List) Date: Wed, 29 Dec 1999 07:22:42 -0500 (EST) X-Mailer: ELM [version 2.4 PL25] 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 I have a machine with 3.4 STABLE (cvsuped this weekend). I have enable softupdates. Last night my amanda dump failed with the following: /-- koala wd0s1f lev 2 FAILED [/sbin/dump returned 3] sendbackup: start [koala:wd0s1f level 2] sendbackup: info BACKUP=/sbin/dump sendbackup: info RECOVER_CMD=/sbin/restore -f... - sendbackup: info end | DUMP: Date of this level 2 dump: Wed Dec 29 05:22:53 1999 | DUMP: Date of last level 1 dump: Mon Dec 27 01:17:25 1999 | DUMP: Dumping /dev/rwd0s1f (/usr) to standard output | DUMP: mapping (Pass I) [regular files] | DUMP: mapping (Pass II) [directories] | DUMP: estimated 1481869 tape blocks. | DUMP: dumping (Pass III) [directories] | DUMP: dumping (Pass IV) [regular files] | DUMP: 2.51% done, finished in 3:14 | DUMP: 5.66% done, finished in 2:46 | DUMP: 8.84% done, finished in 2:34 | DUMP: 12.01% done, finished in 2:26 ? DUMP: read error from /dev/rwd0s1f: Invalid argument: [block -1637719248]: count=8192 ? DUMP: read error from /dev/rwd0s1f: Invalid argument: [sector -1637719248]: count=512 ? DUMP: read error from /dev/rwd0s1f: Invalid argument: [sector -1637719247]: count=512 ? DUMP: read error from /dev/rwd0s1f: Invalid argument: [sector -1637719246]: count=512 ? DUMP: read error from /dev/rwd0s1f: Invalid argument: [sector -1637719245]: count=512 ? DUMP: read error from /dev/rwd0s1f: Invalid argument: [sector -1637719244]: count=512 ? DUMP: read error from /dev/rwd0s1f: Invalid argument: [sector -1637719243]: count=512 ? DUMP: read error from /dev/rwd0s1f: Invalid argument: [sector -1637719242]: count=512 ? DUMP: read error from /dev/rwd0s1f: Invalid argument: [sector -1637719241]: count=512 ? DUMP: read error from /dev/rwd0s1f: Invalid argument: [sector -1637719240]: count=512 ? DUMP: read error from /dev/rwd0s1f: Invalid argument: [sector -1637719239]: count=512 ? DUMP: read error from /dev/rwd0s1f: Invalid argument: [sector -1637719238]: count=512 ? DUMP: read error from /dev/rwd0s1f: Invalid argument: [sector -1637719237]: count=512 . . . . ? DUMP: read error from /dev/rwd0s1f: Invalid argument: [sector -2078257879]: count=512 ? DUMP: read error from /dev/rwd0s1f: Invalid argument: [sector -2078257878]: count=512 ? DUMP: read error from /dev/rwd0s1f: Invalid argument: [sector -2078257877]: count=512 ? DUMP: read error from /dev/rwd0s1f: Invalid argument: [sector -2078257876]: count=512 ? DUMP: read error from /dev/rwd0s1f: Invalid argument: [sector -2078257875]: count=512 ? DUMP: read error from /dev/rwd0s1f: Invalid argument: [sector -2078257874]: count=512 ? DUMP: read error from /dev/rwd0s1f: Invalid argument: [sector -2078257873]: count=512 | DUMP: The ENTIRE dump is aborted. sendbackup: error [/sbin/dump returned 3] \-------- Anyone got any ideas whats going on here? Should I turn softupdates off? If so, should I run fsck on this partition? I don't think I have a good backup of this partiton :-( -- Stan Brown stanb@netcom.com 404-996-6955 Factory Automation Systems Atlanta Ga. -- Look, look, see Windows 95. Buy, lemmings, buy! Pay no attention to that cliff ahead... Henry Spencer (c) 1998 Stan Brown. Redistribution via the Microsoft Network is prohibited. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 29 4:52:40 1999 Delivered-To: freebsd-stable@freebsd.org Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (Postfix) with ESMTP id 8D61914BC4 for ; Wed, 29 Dec 1999 04:52:36 -0800 (PST) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.8.8/8.8.8) id NAA25219 for freebsd-stable@FreeBSD.ORG; Wed, 29 Dec 1999 13:51:53 +0100 (CET) (envelope-from olli) Date: Wed, 29 Dec 1999 13:51:53 +0100 (CET) From: Oliver Fromme Message-Id: <199912291251.NAA25219@dorifer.heim3.tu-clausthal.de> To: freebsd-stable@FreeBSD.ORG Subject: Re: /bin/test broken ? Organization: Administration TU Clausthal Reply-To: freebsd-stable@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: TIN [version 1.2 RZTUC(3) PL2] Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Peter Jeremy wrote in list.freebsd-stable: > Of course, that assumes that the shell doesn't have other > problems with its parsing: > > $ zsh -c '[ 1 -ne 0 ] && echo correct' > correct > $ zsh -c '/bin/[ 1 -ne 0 ] && echo correct' > zsh: bad pattern: /bin/[ > $ > > (Found by accident whilst looking into the original problem - I haven't, > but probably should, report it as a bug in zsh 3.0.5). It's not a bug, it's a feature. :) By default, zsh handles ``['' as part of a glob expression. And according to that behaviour, ``/bin/['' _is_ a broken glob expression, whether you like it or not (I happen to like it, because it's more consistent and causes less surprises). It's (intentionlly) not compatible with the bourne shell. Look at the third example, please: $ zsh -c '[ 1 -ne 0 ] && echo correct' correct $ zsh -c '/bin/[ 1 -ne 0 ] && echo correct' zsh: bad pattern: /bin/[ $ zsh -c 'emulate sh ; /bin/[ 1 -ne 0 ] && echo correct' [: ]: unexpected operator The behaviour in the last example is the default when zsh is invoked as ``sh''. (I'm using zsh 3.0.7, but it works the same in 3.0.5.) For what it's worth, GNU test behaves similarly to ours: $ /usr/local/bin/[ 1 -ne 0 ] && echo correct /usr/local/bin/[: too many arguments Regards Oliver PS: Instead of ``emulate sh'' or invoking it as ``sh'', you can also modify the behaviour by zsh options (``setopt foo''), see ``man zshoptions''. In fact, ``emulate sh'' does nothing more than performing a whole bunch of setopts to make zsh behave like sh. By default, zsh is not supposed to be 100% sh-compatible. -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 29 5:25:12 1999 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 DC6A015048 for ; Wed, 29 Dec 1999 05:25:06 -0800 (PST) (envelope-from Cy.Schubert@uumail.gov.bc.ca) Received: (from daemon@localhost) by point.osg.gov.bc.ca (8.8.7/8.8.8) id FAA17841; Wed, 29 Dec 1999 05:24:39 -0800 Received: from passer.osg.gov.bc.ca(142.32.110.29) via SMTP by point.osg.gov.bc.ca, id smtpda17839; Wed Dec 29 05:24:36 1999 Received: (from uucp@localhost) by passer.osg.gov.bc.ca (8.9.3/8.9.1) id FAA60923; Wed, 29 Dec 1999 05:24:35 -0800 (PST) Received: from cwsys9.cwsent.com(10.2.2.1), claiming to be "cwsys.cwsent.com" via SMTP by passer9.cwsent.com, id smtpdL60902; Wed Dec 29 05:23:42 1999 Received: (from uucp@localhost) by cwsys.cwsent.com (8.9.3/8.9.1) id FAA06712; Wed, 29 Dec 1999 05:23:41 -0800 (PST) Message-Id: <199912291323.FAA06712@cwsys.cwsent.com> Received: from localhost.cwsent.com(127.0.0.1), claiming to be "cwsys" via SMTP by localhost.cwsent.com, id smtpdKw6707; Wed Dec 29 05:23:19 1999 X-Mailer: exmh version 2.1.1 10/15/1999 Reply-To: Cy Schubert - ITSD Open Systems Group From: Cy Schubert - ITSD Open Systems Group X-OS: FreeBSD 3.4-RELEASE X-Sender: cy To: Stan Brown Cc: freebsd-stable@FreeBSD.ORG (FreeBSD Stable List) Subject: Re: Dump problem (soft updates?) In-reply-to: Your message of "Wed, 29 Dec 1999 07:22:42 EST." <199912291222.EAA22783@netcom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 29 Dec 1999 05:23:17 -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199912291222.EAA22783@netcom.com>, Stan Brown writes: > I have a machine with 3.4 STABLE (cvsuped this weekend). I have enable > softupdates. Last night my amanda dump failed with the following: > > > /-- koala wd0s1f lev 2 FAILED [/sbin/dump returned 3] > sendbackup: start [koala:wd0s1f level 2] > sendbackup: info BACKUP=/sbin/dump > sendbackup: info RECOVER_CMD=/sbin/restore -f... - > sendbackup: info end > | DUMP: Date of this level 2 dump: Wed Dec 29 05:22:53 1999 > | DUMP: Date of last level 1 dump: Mon Dec 27 01:17:25 1999 > | DUMP: Dumping /dev/rwd0s1f (/usr) to standard output > | DUMP: mapping (Pass I) [regular files] > | DUMP: mapping (Pass II) [directories] > | DUMP: estimated 1481869 tape blocks. > | DUMP: dumping (Pass III) [directories] > | DUMP: dumping (Pass IV) [regular files] > | DUMP: 2.51% done, finished in 3:14 > | DUMP: 5.66% done, finished in 2:46 > | DUMP: 8.84% done, finished in 2:34 > | DUMP: 12.01% done, finished in 2:26 > ? DUMP: read error from /dev/rwd0s1f: Invalid argument: [block -1637719248] > : count=8192 > ? DUMP: read error from /dev/rwd0s1f: Invalid argument: [sector -1637719248 > ]: count=512 > ? DUMP: read error from /dev/rwd0s1f: Invalid argument: [sector -1637719247 > ]: count=512 > ? DUMP: read error from /dev/rwd0s1f: Invalid argument: [sector -1637719246 > ]: count=512 > ? DUMP: read error from /dev/rwd0s1f: Invalid argument: [sector -1637719245 > ]: count=512 > ? DUMP: read error from /dev/rwd0s1f: Invalid argument: [sector -1637719244 > ]: count=512 > ? DUMP: read error from /dev/rwd0s1f: Invalid argument: [sector -1637719243 > ]: count=512 > ? DUMP: read error from /dev/rwd0s1f: Invalid argument: [sector -1637719242 > ]: count=512 > ? DUMP: read error from /dev/rwd0s1f: Invalid argument: [sector -1637719241 > ]: count=512 > ? DUMP: read error from /dev/rwd0s1f: Invalid argument: [sector -1637719240 > ]: count=512 > ? DUMP: read error from /dev/rwd0s1f: Invalid argument: [sector -1637719239 > ]: count=512 > ? DUMP: read error from /dev/rwd0s1f: Invalid argument: [sector -1637719238 > ]: count=512 > ? DUMP: read error from /dev/rwd0s1f: Invalid argument: [sector -1637719237 > ]: count=512 I had an fsck that produced messages with the same sector numbers last night, just after a panic. As it turned out /var and /opt3, which is normally empty and was used for the first time, were overlapping, causing filesystem corruption. Could it be that your filesystem is corrupted as mine was last night? The other possibility is that the filesystem was actively being written to while the dump was taken (very bad idea). I think you need to perform an fsck on that filesystem to at least verify that it is O.K. Good thing my filesystem corruption occurred at home and not at work. Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 Sun/DEC Team, UNIX Group Internet: Cy.Schubert@uumail.gov.bc.ca ITSD Province of BC "e**(i*pi)+1=0" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 29 6:22: 5 1999 Delivered-To: freebsd-stable@freebsd.org Received: from pluto.psn.net (pluto.psn.net [207.211.58.12]) by hub.freebsd.org (Postfix) with ESMTP id 043B415642 for ; Wed, 29 Dec 1999 06:22:02 -0800 (PST) (envelope-from will@shadow.blackdawn.com) Received: from 14-100.008.popsite.net ([209.69.195.100] helo=shadow.blackdawn.com) by pluto.psn.net with esmtp (PSN Internet Service 3.12 #1) id 123Jxr-0001q0-00; Wed, 29 Dec 1999 07:20:36 -0700 Received: (from will@localhost) by shadow.blackdawn.com (8.9.3/8.9.3) id JAA75013; Wed, 29 Dec 1999 09:20:33 -0500 (EST) (envelope-from will) Message-ID: X-Mailer: XFMail 1.3.1 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199912290115.RAA71526@gndrsh.dnsmgr.net> Date: Wed, 29 Dec 1999 09:20:33 -0500 (EST) Reply-To: Will Andrews From: Will Andrews To: "Rodney W. Grimes" Subject: Re: /bin/test broken ? Cc: freebsd-stable@FreeBSD.ORG, (Peter Jeremy) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 29-Dec-99 Rodney W. Grimes wrote: > Thus, zsh is broken :-(. Here is a working /bin/csh on FreeBSD 3.3 with > a working /bin/[ doing this thing correctly: > gndrsh:root {1134}# sh -c '/bin/[ 1 -ne 0 ] && echo correct' > correct zsh isn't really meant to be 100% sh compatible.. :) It's said that every derivative deviates from its origin.. this is just another example. :) > And a working /bin/sh FreeBSD 3.3 with a working /bin/[ doing this correctly: ># sh -c '/bin/[ 1 -ne 0 ] && echo correct' > correct It's still possible to use zsh to do this kind of check. Although why anyone would want to use zsh for something as simple as this eludes me. I only write scripts using sh, for anything that needs more complex code that is not supported by sh, I use Perl. zsh is intended as an environment shell, not a scripting shell. -- Will Andrews GCS/E/S @d- s+:+>+:- a--->+++ C++ UB++++ P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP+>+++ t++ 5 X++ R+ tv+ b++>++++ DI+++ D+ G++>+++ e->++++ h! r-->+++ y? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 29 10: 3:25 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.rdc1.ct.home.com (ha1.rdc1.ct.home.com [24.2.0.66]) by hub.freebsd.org (Postfix) with ESMTP id 5DD90151F8; Wed, 29 Dec 1999 10:03:20 -0800 (PST) (envelope-from tsikora@home.com) Received: from home.com ([24.2.168.186]) by mail.rdc1.ct.home.com (InterMail v4.01.01.07 201-229-111-110) with ESMTP id <19991229180316.RCR9446.mail.rdc1.ct.home.com@home.com>; Wed, 29 Dec 1999 10:03:16 -0800 Message-ID: <386A4CEC.EB948EE8@home.com> Date: Wed, 29 Dec 1999 13:03:24 -0500 From: Ted Sikora Reply-To: tsikora@powerusersbbs.com Organization: Jtl Development X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.14pre17 i686) X-Accept-Language: en-US,en-GB MIME-Version: 1.0 To: "freebsd-stable@FreeBSD.ORG" Cc: "freebsd-hackers@FreeBSD.ORG" Subject: Temperature Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Here's a strange problem. I run Linux stable/development kernels and FreeBSD-3-STABLE on a SMP dual-boot workstation. The machines temperatures have always been in this range with either system: 87F CPU #0 87F CPU #1 95F Case Temp Sometime last week or early this week the temperature under FreeBSD only has changed to: 113F CPU #0 113F CPU #1 109F Case Temp This is right after boot and varies 3-4 Degrees + while running. During the night periodically my temp warning has been going off. I have it set to 118F. This happens only under FreeBSD. Linux continues to run cool at the old temperatures. Apparantly some code change has caused this. Does anyone know exactly where I should look? Regards, -- Ted Sikora Jtl Development Group tsikora@powerusersbbs.com http://powerusersbbs.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 29 10:12:30 1999 Delivered-To: freebsd-stable@freebsd.org Received: from medulla.hippocampus.net (medulla.hippocampus.net [204.138.241.6]) by hub.freebsd.org (Postfix) with ESMTP id 24D4F1519E; Wed, 29 Dec 1999 10:12:21 -0800 (PST) (envelope-from marc@netstor.com) Received: from localhost (marc@localhost) by medulla.hippocampus.net (8.9.3/8.9.2) with ESMTP id NAA11517; Wed, 29 Dec 1999 13:12:12 -0500 (EST) Date: Wed, 29 Dec 1999 13:12:12 -0500 (EST) From: Marc Nicholas X-Sender: marc@medulla.hippocampus.net To: tsikora@powerusersbbs.com Cc: "freebsd-stable@FreeBSD.ORG" , "freebsd-hackers@FreeBSD.ORG" Subject: Re: Temperature In-Reply-To: <386A4CEC.EB948EE8@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 You're referring to the temps reported via an LM78 or similar, yes? And not reporting that the machine is actually getting HOTTER under FreeBSD? -marc ------------------------------------------------------------------- Marc Nicholas netSTOR Technologies, Inc. http://www.netstor.com "Fast, Expandable and Affordable Internet Caching Products" 1.877.464.4776 416.979.9000x11 fax: 416.979.8223 cell: 416.346.9255 On Wed, 29 Dec 1999, Ted Sikora wrote: > Here's a strange problem. I run Linux stable/development kernels > and FreeBSD-3-STABLE on a SMP dual-boot workstation. The machines > temperatures have always been in this range with either system: > > 87F CPU #0 > 87F CPU #1 > 95F Case Temp > > Sometime last week or early this week the temperature under FreeBSD only > has changed to: > > 113F CPU #0 > 113F CPU #1 > 109F Case Temp > This is right after boot and varies 3-4 Degrees + while running. > > During the night periodically my temp warning has been going off. > I have it set to 118F. This happens only under FreeBSD. Linux continues > to run cool at the old temperatures. Apparantly some code change has > caused this. Does anyone know exactly where I should look? > > Regards, > -- > Ted Sikora > Jtl Development Group > tsikora@powerusersbbs.com > http://powerusersbbs.com > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" 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 Dec 29 11:12: 6 1999 Delivered-To: freebsd-stable@freebsd.org Received: from math.uic.edu (galois.math.uic.edu [131.193.178.114]) by hub.freebsd.org (Postfix) with SMTP id 50B0414D7B for ; Wed, 29 Dec 1999 11:12:04 -0800 (PST) (envelope-from vladimir-bsd-stable@math.uic.edu) Received: (qmail 5656 invoked by uid 31415); 29 Dec 1999 19:11:59 -0000 Date: 29 Dec 1999 19:11:59 -0000 Message-ID: <19991229191159.5655.qmail@math.uic.edu> From: vladimir-bsd-stable@math.uic.edu To: freebsd-stable@FreeBSD.ORG Subject: Re: Temperature Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Speaking of which, is there any way to obtain the temperature and fan RPM from the bios on a FBSD-3.4-stable? Thanks! Vladimir >You're referring to the temps reported via an LM78 or similar, yes? And >not reporting that the machine is actually getting HOTTER under FreeBSD? > > >-marc > >------------------------------------------------------------------- >Marc Nicholas netSTOR Technologies, Inc. http://www.netstor.com >"Fast, Expandable and Affordable Internet Caching Products" >1.877.464.4776 416.979.9000x11 fax: 416.979.8223 cell: 416.346.9255 > >On Wed, 29 Dec 1999, Ted Sikora wrote: > >> Here's a strange problem. I run Linux stable/development kernels >> and FreeBSD-3-STABLE on a SMP dual-boot workstation. The machines >> temperatures have always been in this range with either system: >> >> 87F CPU #0 >> 87F CPU #1 >> 95F Case Temp >> >> Sometime last week or early this week the temperature under FreeBSD only >> has changed to: >> >> 113F CPU #0 >> 113F CPU #1 >> 109F Case Temp >> This is right after boot and varies 3-4 Degrees + while running. >> >> During the night periodically my temp warning has been going off. >> I have it set to 118F. This happens only under FreeBSD. Linux continues >> to run cool at the old temperatures. Apparantly some code change has >> caused this. Does anyone know exactly where I should look? >> >> Regards, >> -- >> Ted Sikora >> Jtl Development Group >> tsikora@powerusersbbs.com >> http://powerusersbbs.com >> >> >> To Unsubscribe: send mail to majordomo@FreeBSD.org >> with "unsubscribe freebsd-hackers" 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 Wed Dec 29 11:15:27 1999 Delivered-To: freebsd-stable@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 0D37114F14; Wed, 29 Dec 1999 11:15:23 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 17D671CA0; Thu, 30 Dec 1999 03:15:16 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: tsikora@powerusersbbs.com Cc: "freebsd-stable@FreeBSD.ORG" , "freebsd-hackers@FreeBSD.ORG" Subject: Re: Temperature In-Reply-To: Message from Ted Sikora of "Wed, 29 Dec 1999 13:03:24 EST." <386A4CEC.EB948EE8@home.com> Date: Thu, 30 Dec 1999 03:15:16 +0800 From: Peter Wemm Message-Id: <19991229191516.17D671CA0@overcee.netplex.com.au> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ted Sikora wrote: > During the night periodically my temp warning has been going off. > I have it set to 118F. This happens only under FreeBSD. Linux continues > to run cool at the old temperatures. Apparantly some code change has > caused this. Does anyone know exactly where I should look? The main difference is that Linux halts the cpu in the idle loop, we don't. As a result the cpu is in a tight spin waiting for a process to become scheduleable. I have some patches half-done that I've been working on for 4.0 that should probably be able to be adapted to the 3.x series. Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 29 11:39: 7 1999 Delivered-To: freebsd-stable@freebsd.org Received: from anarcat.dyndns.org (phobos.IRO.UMontreal.CA [132.204.20.20]) by hub.freebsd.org (Postfix) with ESMTP id EA797150DC for ; Wed, 29 Dec 1999 11:39:01 -0800 (PST) (envelope-from spidey@anarcat.dyndns.org) Received: by anarcat.dyndns.org (Postfix, from userid 1000) id 3A7A41BD4; Wed, 29 Dec 1999 12:00:53 -0500 (EST) From: Spidey MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14442.15940.371472.189793@anarcat.dyndns.org> Date: Wed, 29 Dec 1999 12:00:52 -0500 (EST) To: John Reynolds~ Cc: stable@FreeBSD.ORG Subject: Re: Seeing log messages associated with CVSup updates References: <13641.991004@McFlySr.Kurgan.Ru> <199910071621.JAA47057@vashon.polstra.com> <37FDC033.F3B549A6@newsguy.com> <14334.5160.352292.773239@hip186.ch.intel.com> X-Mailer: VM 6.72 under 21.1 (patch 8) "Bryce Canyon" XEmacs Lucid Reply-To: beaupran@iro.umontreal.ca Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ok... I know this has been __a while ago__ but I am still interested. First, is this in the ports? It should be. :) Second, I can't run it. :) $ ./cvsup.check.pl /root/cvsup/logs/ports-19991228 /ports/audio/timidity++-emacs/pkg/COMMENT/: nested *?+ in regexp at ./cvsup.check.pl line 71, chunk 147. $ I don't understand. Thanks a lot! --- Big Brother told John Reynolds~ to write, at 08:56 of October 8: > > [ On Friday, October 8, Daniel C. Sobral wrote: ] > > > > This script is really cool, but it is still a little bit lacking. If > > we could have a link to the diff between the version you have and > > the latest version, that would be much better. It seems feasible, > > isn't it? > > > > Yes, most of the above seems feasible. There would be a little guesswork and > heuristics on the "linking to the diff" part, but the rest is pretty much done > by the following. The idea for this script, of course, was gleaned from the > original awk script posted by John Polstra yesterday. > > Use at will, modify to suit your needs :) > > #!/usr/bin/perl > # > # Copyright (c) 1999 John C. Reynolds > # All rights reserved. > # > # Redistribution and use in source and binary forms, with or without > # modification, are permitted provided that the following conditions > # are met: > # 1. Redistributions of source code must retain the above copyright > # notice, this list of conditions, and the following disclaimer, > # without modification, immediately at the beginning of the file. > # 2. The name of the author may not be used to endorse or promote products > # derived from this software without specific prior written permission. > # > # THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND > # ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE > # IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE > # ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR > # ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL > # DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS > # OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) > # HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT > # LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY > # OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF > # SUCH DAMAGE. > # > # > # Quickie script to reformat CVSup (16) log files into HTML. Links > # references to files, deltas, and committers to the CVS web CGI program > # and the FreeBSD web site. > # > # The idea for this program originated from an 'awk' script created by > # , with other ideas and patches submitted > # by Marcel Moolenaar . > # > require 'ctime.pl'; > > $url = 'http://www.freebsd.org/cgi/cvsweb.cgi'; > > if ($ARGV[0] eq '') { > print "Usage: $0 cvsup-log-file > cvsup-log-file.html\n"; > exit 1; > } > > # Grab date from file if not coming in from stdin > # > $date = ''; > unless ($ARGV[0] eq '-') { > ($dev, $ino, $mode, $nlink, $uid, $gid, > $rdev, $size, $atime, $mtime, @junk) = stat ($ARGV[0]); > > $date = ctime ($mtime); > chomp ($date); > $date = '(' . $date . ')'; > } > > if (! open (IN, $ARGV[0])) { > print (STDERR "Could not open '$ARGV[0]' for reading - $!\n"); > exit 2; > } > > while () { > if (/Parsing\s+supfile\s+"(.*?)"/) { > $file = $1; > s#$file#$file#; > } > > if (/(Edit|Checkout)\s+(\S+)/) { > $file = $2; > ($realfile = $file) =~ s/,v$//; > s#$file#$file#; > } > > if (/Add\s+delta\s+(\S+).*?(\S+)\s*$/) { > $rev = $1; > $committer = $2; > > s#$rev#$rev#; > s#$committer#$committer#; > } > > if (/Updating\s+collection\s+(\S+)/) { > $collection = $1; > } > > push (@lines, $_); > > } > > close (IN); > > print "\n\n"; > print "CVSup log for '$collection' ${date}\n\n"; > print "\n
\n\n";
> foreach (@lines) {
>     print;
> }
> print "
\n\n\n\n"; > > > > -- > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > | John Reynolds CEG, CCE, Next Generation Flows, HLA | > | Intel Corporation MS: CH6-210 Phone: 480-554-9092 pgr: 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 -- Si l'image donne l'illusion de savoir C'est que l'adage pretend que pour croire, L'important ne serait que de voir Lofofora To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 29 11:49:39 1999 Delivered-To: freebsd-stable@freebsd.org Received: from browni.hq.palmreach.com (browni.hq.palmreach.com [195.198.168.195]) by hub.freebsd.org (Postfix) with ESMTP id 3274815020 for ; Wed, 29 Dec 1999 11:49:36 -0800 (PST) (envelope-from kaj@ns.Raditex.se) Received: from Raditex.se (r9.se.palmreach.com [172.16.0.19]) by browni.hq.palmreach.com (8.9.3/8.9.3/Debian/GNU) with ESMTP id UAA30099; Wed, 29 Dec 1999 20:49:06 +0100 Message-ID: <386A65C2.B2BFF596@Raditex.se> Date: Wed, 29 Dec 1999 20:49:22 +0100 From: Rasmus Kaj Organization: Raditex AB - http://Raditex.se/ X-Mailer: Mozilla 4.51 [en] (X11; I; FreeBSD 3.2-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Peter Wemm Cc: tsikora@powerusersbbs.com, "freebsd-stable@FreeBSD.ORG" , kaj@ns.Raditex.se Subject: Re: Temperature References: <19991229191516.17D671CA0@overcee.netplex.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 Peter Wemm wrote, about processor temp, etc: > The main difference is that Linux halts the cpu in the idle loop, we don't. > As a result the cpu is in a tight spin waiting for a process to become > scheduleable. I have some patches half-done that I've been working on for > 4.0 that should probably be able to be adapted to the 3.x series. The FAQ says that FreeBSD does use the HLT instruction when idle, is this wrong? http://www.se.FreeBSD.org/FAQ/misc.html#AEN3561 // Rasmus To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 29 12: 7:40 1999 Delivered-To: freebsd-stable@freebsd.org Received: from megaweapon.zigg.com (megaweapon.zigg.com [206.114.60.8]) by hub.freebsd.org (Postfix) with ESMTP id 4C23114DA2 for ; Wed, 29 Dec 1999 12:07:37 -0800 (PST) (envelope-from matt@zigg.com) Received: from localhost (matt@localhost) by megaweapon.zigg.com (8.9.3/8.9.3) with ESMTP id PAA09036; Wed, 29 Dec 1999 15:07:35 -0500 (EST) (envelope-from matt@zigg.com) Date: Wed, 29 Dec 1999 15:07:32 -0500 (EST) From: Matt Behrens To: Peter Wemm Cc: tsikora@powerusersbbs.com, "freebsd-stable@FreeBSD.ORG" Subject: Re: Temperature In-Reply-To: <19991229191516.17D671CA0@overcee.netplex.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 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 [Taking out the -hackers crosspost] On Thu, 30 Dec 1999, Peter Wemm wrote: > The main difference is that Linux halts the cpu in the idle loop, we don't. > As a result the cpu is in a tight spin waiting for a process to become > scheduleable. I have some patches half-done that I've been working on for > 4.0 that should probably be able to be adapted to the 3.x series. Huh?! So the FAQ is wrong? (See .) Also, when the did this (apparently) change? The original poster referred to this being a new problem. - -- Matt Behrens Owner/Administrator, zigg.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.1 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE4amoG+xq4JbgNGlMRAhhjAKCSKGQxp5vFuB7qYU1RZuqwJwMANACfTxop fNrl6jam9rJpmKIDBnOvgu8= =KFHE -----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 Wed Dec 29 12:16:20 1999 Delivered-To: freebsd-stable@freebsd.org Received: from finland.ispro.net.tr (finland.ispro.net.tr [212.174.120.1]) by hub.freebsd.org (Postfix) with ESMTP id B8EC814CFD for ; Wed, 29 Dec 1999 12:15:57 -0800 (PST) (envelope-from yurtesen@ispro.net.tr) Received: from localhost (yurtesen@localhost) by finland.ispro.net.tr (8.9.3/8.9.3) with ESMTP id WAA69879; Wed, 29 Dec 1999 22:14:48 +0200 (EET) (envelope-from yurtesen@ispro.net.tr) Date: Wed, 29 Dec 1999 22:14:48 +0200 (EET) From: Evren Yurtesen To: vladimir-bsd-stable@math.uic.edu Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Temperature In-Reply-To: <19991229191159.5655.qmail@math.uic.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 There is a program in ports but I never used it... http://www.freebsd.org/ports/sysutils.html#consolehm-1.2 I think this is the program you need... Evren On 29 Dec 1999 vladimir-bsd-stable@math.uic.edu wrote: > > Speaking of which, is there any way to obtain the temperature > and fan RPM from the bios on a FBSD-3.4-stable? Thanks! > > Vladimir > > >You're referring to the temps reported via an LM78 or similar, yes? And > >not reporting that the machine is actually getting HOTTER under FreeBSD? > > > > > >-marc > > > >------------------------------------------------------------------- > >Marc Nicholas netSTOR Technologies, Inc. http://www.netstor.com > >"Fast, Expandable and Affordable Internet Caching Products" > >1.877.464.4776 416.979.9000x11 fax: 416.979.8223 cell: 416.346.9255 > > > >On Wed, 29 Dec 1999, Ted Sikora wrote: > > > >> Here's a strange problem. I run Linux stable/development kernels > >> and FreeBSD-3-STABLE on a SMP dual-boot workstation. The machines > >> temperatures have always been in this range with either system: > >> > >> 87F CPU #0 > >> 87F CPU #1 > >> 95F Case Temp > >> > >> Sometime last week or early this week the temperature under FreeBSD only > >> has changed to: > >> > >> 113F CPU #0 > >> 113F CPU #1 > >> 109F Case Temp > >> This is right after boot and varies 3-4 Degrees + while running. > >> > >> During the night periodically my temp warning has been going off. > >> I have it set to 118F. This happens only under FreeBSD. Linux continues > >> to run cool at the old temperatures. Apparantly some code change has > >> caused this. Does anyone know exactly where I should look? > >> > >> Regards, > >> -- > >> Ted Sikora > >> Jtl Development Group > >> tsikora@powerusersbbs.com > >> http://powerusersbbs.com > >> > >> > >> To Unsubscribe: send mail to majordomo@FreeBSD.org > >> with "unsubscribe freebsd-hackers" 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 Wed Dec 29 12:31:14 1999 Delivered-To: freebsd-stable@freebsd.org Received: from news-ma.rhein-neckar.de (news-ma.rhein-neckar.de [193.197.90.3]) by hub.freebsd.org (Postfix) with ESMTP id ECD0E15262 for ; Wed, 29 Dec 1999 12:31:11 -0800 (PST) (envelope-from daemon@bigeye.rhein-neckar.de) Received: from bigeye.rhein-neckar.de (uucp@localhost) by news-ma.rhein-neckar.de (8.8.8/8.8.8) with bsmtp id VAA12605 for freebsd-stable@freebsd.org; Wed, 29 Dec 1999 21:31:06 +0100 (CET) (envelope-from daemon@bigeye.rhein-neckar.de) Received: (from daemon@localhost) by bigeye.rhein-neckar.de (8.9.3/8.9.3) id VAA36735 for freebsd-stable@freebsd.org; Wed, 29 Dec 1999 21:07:10 +0100 (CET) (envelope-from daemon) From: naddy@mips.rhein-neckar.de (Christian Weisgerber) Subject: Re: Dump problem (soft updates?) Date: 29 Dec 1999 21:07:10 +0100 Message-ID: <84dple$13rm$1@bigeye.rhein-neckar.de> References: <199912291222.EAA22783@netcom.com> To: freebsd-stable@freebsd.org Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Stan Brown wrote: > | DUMP: 12.01% done, finished in 2:26 > ? DUMP: read error from /dev/rwd0s1f: Invalid argument: [block > -1637719248]: count=8192 Never seen anything like this, but in your place, the first thing I'd do is unmount that partition and fsck it. > Anyone got any ideas whats going on here? Should I turn softupdates > off? Softupdates don't interfere with dump. Your problem has a different cause. -- Christian "naddy" Weisgerber naddy@mips.rhein-neckar.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 29 12:31:24 1999 Delivered-To: freebsd-stable@freebsd.org Received: from news-ma.rhein-neckar.de (news-ma.rhein-neckar.de [193.197.90.3]) by hub.freebsd.org (Postfix) with ESMTP id DB8DE156C4 for ; Wed, 29 Dec 1999 12:31:17 -0800 (PST) (envelope-from daemon@bigeye.rhein-neckar.de) Received: from bigeye.rhein-neckar.de (uucp@localhost) by news-ma.rhein-neckar.de (8.8.8/8.8.8) with bsmtp id VAA12607 for freebsd-stable@freebsd.org; Wed, 29 Dec 1999 21:31:13 +0100 (CET) (envelope-from daemon@bigeye.rhein-neckar.de) Received: (from daemon@localhost) by bigeye.rhein-neckar.de (8.9.3/8.9.3) id VAA36791 for freebsd-stable@freebsd.org; Wed, 29 Dec 1999 21:11:11 +0100 (CET) (envelope-from daemon) From: naddy@mips.rhein-neckar.de (Christian Weisgerber) Subject: Re: Dump problem (soft updates?) Date: 29 Dec 1999 21:11:10 +0100 Message-ID: <84dpsu$13te$1@bigeye.rhein-neckar.de> References: <199912291222.EAA22783@netcom.com> <199912291323.FAA06712@cwsys.cwsent.com> To: freebsd-stable@freebsd.org Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Cy Schubert - ITSD Open Systems Group wrote: > The other possibility is that the filesystem was actively being written to > while the dump was taken (very bad idea). Supposedly dump handles this quite well. I haven't stress-tested this yet, but I keep my machines in multiuser mode when running dump. No problems encountered so far. > "e**(i*pi)+1=0" ;-) -- Christian "naddy" Weisgerber naddy@mips.rhein-neckar.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 29 13:29:59 1999 Delivered-To: freebsd-stable@freebsd.org Received: from crcst347.netaddress.usa.net (crcst347.netaddress.usa.net [204.68.23.92]) by hub.freebsd.org (Postfix) with SMTP id 41AC61505E for ; Wed, 29 Dec 1999 13:29:55 -0800 (PST) (envelope-from _novocaer_@usa.net) Received: (qmail 23483 invoked from network); 29 Dec 1999 21:08:43 -0000 Received: from nw171.netaddress.usa.net (204.68.24.71) by outbound.netaddress.usa.net with SMTP; 29 Dec 1999 21:08:43 -0000 Received: (qmail 6809 invoked by uid 60001); 29 Dec 1999 21:29:51 -0000 Message-ID: <19991229212951.6807.qmail@nw171.netaddress.usa.net> Received: from 204.68.24.71 by nw171 for [212.116.171.52] via web-mailer(M3.4.0.33) on Wed Dec 29 21:29:51 GMT 1999 Date: 29 Dec 99 14:29:51 MST From: Novocaer <_novocaer_@usa.net> To: stable@FreeBSD.org Subject: 3.2 executables won't run X-Mailer: USANET web-mailer (M3.4.0.33) 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 Dear sirs, as it happens my first experience with FreeBSD is with 3.2-Stable, and i've yet to see this sort of problem ever. When i run a file, that should run, i get error message as if it didn't exist. So i check permissions- they're OK. I check it with "file"- = the output seems reasonable (executable, stripped etc.). So i go hmmm. Maybe that's a shell problem. I change the shell- nothing. So i go hmmm. Maybe i loaded one or more modules that are somehow defective. Unloading-= Nothing. So i go hmmm. Maybe i should try something else: #cat >asd <a.c <; Wed, 29 Dec 1999 13:38:55 -0800 (PST) (envelope-from mark@dogma.freebsd-uk.eu.org) Received: (qmail 20708 invoked from network); 29 Dec 1999 21:38:51 -0000 Received: from userat13.uk.uudial.com (HELO marder-1.) (62.188.137.116) by smtp.dial.pipex.com with SMTP; 29 Dec 1999 21:38:51 -0000 Received: (from mark@localhost) by marder-1. (8.9.3/8.9.3) id VAA93470; Wed, 29 Dec 1999 21:40:31 GMT (envelope-from mark) Date: Wed, 29 Dec 1999 21:40:31 +0000 From: Mark Ovens To: Novocaer <_novocaer_@usa.net> Cc: stable@freebsd.org Subject: Re: 3.2 executables won't run Message-ID: <19991229214031.V1290@marder-1> References: <19991229212951.6807.qmail@nw171.netaddress.usa.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <19991229212951.6807.qmail@nw171.netaddress.usa.net> Organization: Total lack of Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Dec 29, 1999 at 02:29:51PM -0700, Novocaer wrote: > Dear sirs, > as it happens my first experience with FreeBSD is with 3.2-Stable, > and i've yet to see this sort of problem ever. > When i run a file, that should run, i get error message as if it didn't > exist. So i check permissions- they're OK. I check it with "file"- > the output seems reasonable (executable, stripped etc.). So i go hmmm. > Maybe that's a shell problem. I change the shell- nothing. So i go hmmm. > Maybe i loaded one or more modules that are somehow defective. Unloading- > Nothing. So i go hmmm. Maybe i should try something else: > #cat >asd < echo qwerty > EOF > #chmod a+x asd > "file" on "asd" says "text file", but when i run it- you guessed- nothing. > So i go hmmm. Maybe pleading to the CPU would help? So i type: Ah, did you type ``./asd'' to run it (unless the current directory is in your path): marder-1# cat >asd < #cat >a.c < main(){ > printf('qwerty'); > } > EOF > #gcc a.c > and get executable "a.out" that won't run either. So i go hmmm. > #gdb a.out > looking through the main() procedure reveals nothing strange. > I got a feeling i'm missing something big here... > Additional (Maybe) important data to analyse: > A. I was unable to diferentiate the files that run from those that don't. > It's not owner dependant, size dependant, shell dependant, in or out > of X, loadable modules or not, made for Linux or not, not user > dependant- i tried real hard. > B. I used the same set of CD's to install on a different station (200mhz, > 64mb, 6.4GB pentium) and the same problem appeared there. > C. I tried it on different installs, expert/novice, w/ developer or w/o- > again- nothing. > D. Yes, i do hummm a-lot. > > Thank you. > > > ---------------------------------------------------------------- > TagLine Thieves Guild Official Member # 31415926535 > ---------------------------------------------------------------- > > ____________________________________________________________________ > Get free email and a permanent address at http://www.netaddress.com/?N=1 > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- "there's a long-standing bug relating to the x86 architecture that allows you to install Windows too" -Matthew D. Fuller ________________________________________________________________ FreeBSD - The Power To Serve http://www.freebsd.org My Webpage http://ukug.uk.freebsd.org/~mark/ mailto:mark@ukug.uk.freebsd.org http://www.radan.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 29 13:47:59 1999 Delivered-To: freebsd-stable@freebsd.org Received: from pinhead.parag.codegen.com (207-44-235-154.CodeGen.COM [207.44.235.154]) by hub.freebsd.org (Postfix) with ESMTP id 9C0B115734 for ; Wed, 29 Dec 1999 13:47:47 -0800 (PST) (envelope-from parag@pinhead.parag.codegen.com) Received: from pinhead.parag.codegen.com (parag@localhost.parag.codegen.com [127.0.0.1]) by pinhead.parag.codegen.com (8.9.3/8.9.3) with ESMTP id NAA60081 for ; Wed, 29 Dec 1999 13:47:43 -0800 (PST) (envelope-from parag@pinhead.parag.codegen.com) To: freebsd-stable@FreeBSD.ORG Subject: Re: Temperature In-Reply-To: Message from vladimir-bsd-stable@math.uic.edu of "29 Dec 1999 19:11:59 GMT." <19991229191159.5655.qmail@math.uic.edu> X-Image-URL: http://www.codegen.com/images/CG-logo-only.gif X-URL: http://www.codegen.com X-Face: =O'Kj74icvU|oS*<7gS/8'\Pbpm}okVj*@UC!IgkmZQAO!W[|iBiMs*|)n*`X ]pW%m>Oz_mK^Gdazsr.Z0/JsFS1uF8gBVIoChGwOy{EK=<6g?aHE`[\S]C]T0Wm Date: Wed, 29 Dec 1999 13:47:43 -0800 Message-ID: <60078.946504063@pinhead.parag.codegen.com> From: Parag Patel Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 29 Dec 1999 19:11:59 GMT, vladimir-bsd-stable@math.uic.edu wrote: > > >Speaking of which, is there any way to obtain the temperature >and fan RPM from the bios on a FBSD-3.4-stable? Thanks! I'm using the sysutils/lmmon port with the "-i" option. Works great! -- Parag To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 29 13:51:51 1999 Delivered-To: freebsd-stable@freebsd.org Received: from smtp6.jps.net (smtp6.jps.net [209.63.224.103]) by hub.freebsd.org (Postfix) with ESMTP id 369A21505E for ; Wed, 29 Dec 1999 13:51:44 -0800 (PST) (envelope-from onemo@jps.net) Received: from jps.net (216-224-146-33.stk.jps.net [216.224.146.33]) by smtp6.jps.net (8.9.3/8.9.0) with ESMTP id NAA18096; Wed, 29 Dec 1999 13:48:59 -0800 (PST) Message-ID: <386A805F.1212E89E@jps.net> Date: Wed, 29 Dec 1999 13:42:55 -0800 From: Michael Oski X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: Novocaer <_novocaer_@usa.net> Cc: stable@FreeBSD.ORG Subject: Re: 3.2 executables won't run References: <19991229212951.6807.qmail@nw171.netaddress.usa.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Are you by chance saving these files on an NFS mounted file system? I've seen this exact behaviour when I was mounting a Solaris home dir with my ~/bin scripts without the execute flag enabled on the mount. Novocaer wrote: > Dear sirs, > as it happens my first experience with FreeBSD is with 3.2-Stable, > and i've yet to see this sort of problem ever. > When i run a file, that should run, i get error message as if it didn't > exist. So i check permissions- they're OK. I check it with "file"- > the output seems reasonable (executable, stripped etc.). So i go hmmm. > Maybe that's a shell problem. I change the shell- nothing. So i go hmmm. > Maybe i loaded one or more modules that are somehow defective. Unloading- > Nothing. So i go hmmm. Maybe i should try something else: > #cat >asd < echo qwerty > EOF > #chmod a+x asd > "file" on "asd" says "text file", but when i run it- you guessed- nothing. > So i go hmmm. Maybe pleading to the CPU would help? So i type: > #cat >a.c < main(){ > printf('qwerty'); > } > EOF > #gcc a.c > and get executable "a.out" that won't run either. So i go hmmm. > #gdb a.out > looking through the main() procedure reveals nothing strange. > I got a feeling i'm missing something big here... > Additional (Maybe) important data to analyse: > A. I was unable to diferentiate the files that run from those that don't. > It's not owner dependant, size dependant, shell dependant, in or out > of X, loadable modules or not, made for Linux or not, not user > dependant- i tried real hard. > B. I used the same set of CD's to install on a different station (200mhz, > 64mb, 6.4GB pentium) and the same problem appeared there. > C. I tried it on different installs, expert/novice, w/ developer or w/o- > again- nothing. > D. Yes, i do hummm a-lot. > > Thank you. > > ---------------------------------------------------------------- > TagLine Thieves Guild Official Member # 31415926535 > ---------------------------------------------------------------- > > ____________________________________________________________________ > Get free email and a permanent address at http://www.netaddress.com/?N=1 > > 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 Dec 29 13:55:26 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mechv.me.tuns.ca (mechv.me.TUNS.Ca [134.190.50.152]) by hub.freebsd.org (Postfix) with ESMTP id 2918714F14 for ; Wed, 29 Dec 1999 13:55:23 -0800 (PST) (envelope-from bbursey@mechv.me.tuns.ca) Received: from localhost (bbursey@localhost) by mechv.me.tuns.ca (8.8.8/8.8.5) with SMTP id RAA00697 for ; Wed, 29 Dec 1999 17:45:46 -0400 (AST) Date: Wed, 29 Dec 1999 17:45:46 -0400 (AST) From: Bryan Bursey To: freebsd-stable@FreeBSD.ORG Subject: Re: Temperature In-Reply-To: <60078.946504063@pinhead.parag.codegen.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 G'day folks... I've had both wmhm and consolehm wonking, but only with a single CPU. Does anyone know of a SMP-enabled version of these apps, or if one might be in the works? Cheers, Bryan On Wed, 29 Dec 1999, Parag Patel wrote: |On 29 Dec 1999 19:11:59 GMT, vladimir-bsd-stable@math.uic.edu wrote: |> |> |>Speaking of which, is there any way to obtain the temperature |>and fan RPM from the bios on a FBSD-3.4-stable? Thanks! | |I'm using the sysutils/lmmon port with the "-i" option. Works great! | | | -- Parag | | |To Unsubscribe: send mail to majordomo@FreeBSD.org |with "unsubscribe freebsd-stable" in the body of the message | ________________________________ Bryan Bursey, DEng Dept. of Mechanical Engineering DalTech (TUNS) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 29 14: 0:51 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mechv.me.tuns.ca (mechv.me.TUNS.Ca [134.190.50.152]) by hub.freebsd.org (Postfix) with ESMTP id 468FD151D4 for ; Wed, 29 Dec 1999 14:00:48 -0800 (PST) (envelope-from bbursey@mechv.me.tuns.ca) Received: from localhost (bbursey@localhost) by mechv.me.tuns.ca (8.8.8/8.8.5) with SMTP id RAA00724 for ; Wed, 29 Dec 1999 17:51:26 -0400 (AST) Date: Wed, 29 Dec 1999 17:51:26 -0400 (AST) From: Bryan Bursey To: freebsd-stable@FreeBSD.ORG Subject: Re: Temperature 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 Wed, 29 Dec 1999, Bryan Bursey wrote: |G'day folks... | |I've had both wmhm and consolehm wonking, but only with a single CPU. ^^^^^^^ working |Does anyone know of a SMP-enabled version of these apps, or if one might |be in the works? | |Cheers, |Bryan | Sorry... Bryan |On Wed, 29 Dec 1999, Parag Patel wrote: | ||On 29 Dec 1999 19:11:59 GMT, vladimir-bsd-stable@math.uic.edu wrote: ||> ||> ||>Speaking of which, is there any way to obtain the temperature ||>and fan RPM from the bios on a FBSD-3.4-stable? Thanks! || ||I'm using the sysutils/lmmon port with the "-i" option. Works great! || || || -- Parag || || ||To Unsubscribe: send mail to majordomo@FreeBSD.org ||with "unsubscribe freebsd-stable" in the body of the message || | |________________________________ |Bryan Bursey, DEng |Dept. of Mechanical Engineering |DalTech (TUNS) | | | | | | |To Unsubscribe: send mail to majordomo@FreeBSD.org |with "unsubscribe freebsd-stable" in the body of the message | ________________________________ Bryan Bursey, DEng Dept. of Mechanical Engineering DalTech (TUNS) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 29 15: 2:53 1999 Delivered-To: freebsd-stable@freebsd.org Received: from www.geocrawler.com (sourceforge.net [209.81.8.17]) by hub.freebsd.org (Postfix) with ESMTP id 378F915739 for ; Wed, 29 Dec 1999 15:02:51 -0800 (PST) (envelope-from nobody@www.geocrawler.com) Received: (from nobody@localhost) by www.geocrawler.com (8.9.3/8.9.3) id PAA02890; Wed, 29 Dec 1999 15:02:53 -0800 Date: Wed, 29 Dec 1999 15:02:53 -0800 Message-Id: <199912292302.PAA02890@www.geocrawler.com> To: freebsd-stable@freebsd.org Subject: modstat: modload: /dev/lkm From: "Juan Kuuse" Reply-To: "Juan Kuuse" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message was sent from Geocrawler.com by "Juan Kuuse" Be sure to reply to that address. I just upgraded from 3.0-RELEASE to 3.4-STABLE. Three things didn't work: 1. Invalid format at boot: Fixed with disklabel etc. 2. pam error at login: Missing /etc/pam.conf file, fixed by copying the file from another 3.4 box (that one was upgraded from 3.1-RELEASE). 3. modstat: /dev/lkm: Device not configured modload: /dev/lkm: Device not configured I searched the mailing list and figured out that I don't need the lkm modules anymore. But I didn't find *how* to get rid of the lkm modules (and the error messages). "options LKM" in the kernel config file doesn't seem to be an elegant solution. How do I? Any suggestions are appreciated. Thanks in advance, Juan Kuuse Geocrawler.com - The Knowledge Archive To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 29 15:20:22 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id 72164151E9; Wed, 29 Dec 1999 15:20:18 -0800 (PST) (envelope-from dkelly@nospam.hiwaay.net) Received: from nospam.hiwaay.net (tnt8-208-170-118-224.dialup.HiWAAY.net [208.170.118.224]) by mail.HiWAAY.net (8.9.3/8.9.0) with ESMTP id RAA19459; Wed, 29 Dec 1999 17:20:15 -0600 (CST) Received: from localhost (localhost [127.0.0.1]) by nospam.hiwaay.net (8.9.3/8.9.3) with ESMTP id RAA38266; Wed, 29 Dec 1999 17:20:12 -0600 (CST) (envelope-from dkelly@nospam.hiwaay.net) Message-Id: <199912292320.RAA38266@nospam.hiwaay.net> X-Mailer: exmh version 2.1.1 10/15/1999 To: Peter Wemm Cc: tsikora@powerusersbbs.com, "freebsd-stable@FreeBSD.ORG" , "freebsd-hackers@FreeBSD.ORG" From: David Kelly Subject: Re: Temperature In-reply-to: Message from Peter Wemm of "Thu, 30 Dec 1999 03:15:16 +0800." <19991229191516.17D671CA0@overcee.netplex.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 29 Dec 1999 17:20:12 -0600 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Peter Wemm writes: > Ted Sikora wrote: > > > During the night periodically my temp warning has been going off. > > I have it set to 118F. This happens only under FreeBSD. Linux continues > > to run cool at the old temperatures. Apparantly some code change has > > caused this. Does anyone know exactly where I should look? > > The main difference is that Linux halts the cpu in the idle loop, we don't. > As a result the cpu is in a tight spin waiting for a process to become > scheduleable. I have some patches half-done that I've been working on for > 4.0 that should probably be able to be adapted to the 3.x series. I'll let others debate whether or not FreeBSD halts the CPU when idle or not, or whether this has changed recently. OTOH Ted has a problem that is being ignored: that his CPU/Heatsink/Fan combination is apparently not up to a 100% duty cycle. DOS would cook it. As would most games. Or several "make buildworlds" in a row. -- David Kelly N4HHE, dkelly@hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 29 15:45:47 1999 Delivered-To: freebsd-stable@freebsd.org Received: from corinth.bossig.com (corinth.bossig.com [208.26.239.66]) by hub.freebsd.org (Postfix) with ESMTP id F08E514D7B; Wed, 29 Dec 1999 15:45:39 -0800 (PST) (envelope-from kstewart@3-cities.com) Received: from 3-cities.com (kenn2123.bossig.com [208.26.242.123]) by corinth.bossig.com (Rockliffe SMTPRA 3.4.5) with ESMTP id ; Wed, 29 Dec 1999 15:52:46 -0800 Message-ID: <386A9D29.C7F0390D@3-cities.com> Date: Wed, 29 Dec 1999 15:45:45 -0800 From: Kent Stewart Organization: Columbia Basin Virtual Community Project X-Mailer: Mozilla 4.7 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: David Kelly Cc: Peter Wemm , tsikora@powerusersbbs.com, "freebsd-stable@FreeBSD.ORG" , "freebsd-hackers@FreeBSD.ORG" Subject: Re: Temperature References: <199912292320.RAA38266@nospam.hiwaay.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David Kelly wrote: > > Peter Wemm writes: > > Ted Sikora wrote: > > > > > During the night periodically my temp warning has been going off. > > > I have it set to 118F. This happens only under FreeBSD. Linux continues > > > to run cool at the old temperatures. Apparantly some code change has > > > caused this. Does anyone know exactly where I should look? > > > > The main difference is that Linux halts the cpu in the idle loop, we don't. > > As a result the cpu is in a tight spin waiting for a process to become > > scheduleable. I have some patches half-done that I've been working on for > > 4.0 that should probably be able to be adapted to the 3.x series. > > I'll let others debate whether or not FreeBSD halts the CPU when idle > or not, or whether this has changed recently. > > OTOH Ted has a problem that is being ignored: that his CPU/Heatsink/Fan > combination is apparently not up to a 100% duty cycle. DOS would cook > it. As would most games. Or several "make buildworlds" in a row. Antec and Startech have some dual fans for P-II's. The old P-II style is hard to find but the K-7 Athalon apparently uses the same style of fan. One of the vendors has a monster fan for a P-III. I run setiathome in the background on all of my computers, which keeps the systems at 100% all of the time. I had a new 250W PS go out in three days. The fans that come on P-II OEM's is not that great. It also sounds like he isn't getting enough outside air. You can't cool if the inside air is hot. Kent > > -- > David Kelly N4HHE, dkelly@hiwaay.net > ===================================================================== > The human mind ordinarily operates at only ten percent of its > capacity -- the rest is overhead for the operating system. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- Kent Stewart Richland, WA mailto:kstewart@3-cities.com http://www.3-cities.com/~kstewart/index.html FreeBSD News http://daily.daemonnews.org/ SETI(Search for Extraterrestrial Intelligence) @ HOME http://setiathome.ssl.berkeley.edu/ Hunting Archibald Stewart, b 1802 in Ballymena, Antrim Co., NIR http://www.3-cities.com/~kstewart/genealogy/archibald_stewart.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 29 18:53:35 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail2.uniserve.com (mail2.uniserve.com [204.244.156.7]) by hub.freebsd.org (Postfix) with ESMTP id BC1DD1509C; Wed, 29 Dec 1999 18:53:29 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca ([204.244.186.218]) by mail2.uniserve.com with smtp (Exim 3.03 #4) id 123ViT-000AZ1-00; Wed, 29 Dec 1999 18:53:29 -0800 Date: Wed, 29 Dec 1999 18:53:24 -0800 (PST) From: Tom X-Sender: tom@shell.uniserve.ca To: freebsd-stable@freebsd.org, freebsd-hackers@freebsd.org Subject: softupdates and debug.max_softdeps 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'm trying to find some information on reasonable settings for debug.max_softdeps on a recent FreeBSD-stable system. It seems that if you have a machine that is able to generate disk IO much faster than can be handled, has a large amount of RAM (and therefore debug.max_softdeps is large), and the filesystem is very large (about 80GB), filesystem metadata updates can get _very_ far behind. For instance, on a test system running 4 instances of postmark continuously for 24 hours, "df" reports that 40 GB of disk space is being used, even though only about 5 GB is actually used. If I kill the postmark processes, the metadata is eventually dribbled out and "df" reports 5GB in use. It takes about 20 minutes for the metadata to be updated on a completely ideal system. On this particular system, it doesn't seem to stabilize either. If the 4 postmark instances are allowed to run, disk usage seems to climb indefinitely (at 40GB it was still climbing), until eventually the machine silently reboots. debug.max_softdeps is by default set to 523,712 (1 GB of RAM). Is that a resonable value? I see some tests in the docs with max_softdeps set to 4000 or so. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 29 19: 6:38 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.nyct.net (bsd4.nyct.net [204.141.86.6]) by hub.freebsd.org (Postfix) with ESMTP id B163A14D3F for ; Wed, 29 Dec 1999 19:06:35 -0800 (PST) (envelope-from efutch@nyct.net) Received: from bsd1.nyct.net (efutch@bsd1.nyct.net [204.141.86.3]) by mail.nyct.net (8.8.8/8.8.7) with ESMTP id WAA04003 for ; Wed, 29 Dec 1999 22:06:34 -0500 (EST) (envelope-from efutch@nyct.net) Date: Wed, 29 Dec 1999 22:06:34 -0500 (EST) From: "Eric D. Futch" To: freebsd-stable@FreeBSD.ORG Subject: Re: USB broken? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm running 3.4-stable with source cvsup'd about a week ago. I configed my kernel for USB support. After turning on the USB interface in BIOS kernel panics after it probes uchi0. Below is the panic message plus trace. % uname -a FreeBSD quake.nyct.net 3.4-STABLE FreeBSD 3.4-STABLE #3: Wed Dec 29 21:17:59 EST 1999 efutch@quake.nyct.net:/usr/src/sys/compile/QUAKE i386 --- uhci0: rev 0x01 int d irq 10 on pci0.7.2> kernel trap 12 with interrupts disabled Fatal trap 12: page fault while in kernel mode mp_lock = 00000002; cpuid = 0; lapic.id = 00000000 fault virtual address = 0x0 fault code = supervisor write, page not present instruction pointer = 0x8:0xc0216a74 stack pointer = 0x10:0xc0313e18 frame pointer = 0x10:0xc0313e38 code segment = base 0x0, limit 0xfffff, type 0x16 = DPL 0, pres 1, def32 1, gran 1 processor eflags = resume, IOPC = 0 current progess = 0 () interrupt mask = net tty bio cam <- SMP: XXX kernel: type 12 trap, code=0 Stopped at INTREN+0x2c: movl %ecx,0(%edx) db> trace INTREN(a,c01fd294,c0da1000,c028d14c,0) at INTREN+0x2c add_intrdesc(c0d93e20,400,c028a2f8,c0da1000,a) at add_intrdesc+0x29 intr_connect(c0d93e20,ffffffff,a,c01fd294,c0da1000,c028d14c,0) at intr_connect+0x2e pci_map_int_right(c0751608,c01fd294,c0da1000,c028d14c,0) at pci_map_int_right+0x31 pci_map_int(c0751608,c01fd294,c0da1000,c028d14c,c0751608,20) at pci_map_int+0x16 uhci_pci_attach(c0751608,0) at uhci_pci_attach+0x75 pci_drvattach(c0751600,c0751600,0,7,c0322f68) at pci_drvattach+0x5f pci_probebus(0,c02637b2,0) at pci_probebus+0x53 pci_probe(0,c0322f98,c0214d70,c0322fac,c014a1f7) at pci_probe+0x39 pci_configure(c0322fac,c014a1f7,0,320c00,326000) at pci_configure+0xa configure(0) at configure+0x20 main(c0322fb8,0,8000,c0161189,c0403000) at main+0x83 begin() at begin+0x55 --- -- Eric Futch New York Connect.Net, Ltd. efutch@nyct.net Technical Support Staff http://www.nyct.net (212) 293-2620 "Bringing New York The Internet Access It Deserves" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 29 20: 4:10 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.rdc1.ct.home.com (ha1.rdc1.ct.home.com [24.2.0.66]) by hub.freebsd.org (Postfix) with ESMTP id 5924F150D9; Wed, 29 Dec 1999 20:04:05 -0800 (PST) (envelope-from tsikora@home.com) Received: from home.com ([24.2.168.186]) by mail.rdc1.ct.home.com (InterMail v4.01.01.07 201-229-111-110) with ESMTP id <19991230040404.GDZR9446.mail.rdc1.ct.home.com@home.com>; Wed, 29 Dec 1999 20:04:04 -0800 Message-ID: <386AD9BC.37852615@home.com> Date: Wed, 29 Dec 1999 23:04:12 -0500 From: Ted Sikora Reply-To: tsikora@powerusersbbs.com Organization: Jtl Development X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.3.34 i686) X-Accept-Language: en-US,en-GB MIME-Version: 1.0 To: Kent Stewart Cc: "freebsd-stable@FreeBSD.ORG" , "freebsd-hackers@FreeBSD.ORG" Subject: Re: Temperature References: <199912292320.RAA38266@nospam.hiwaay.net> <386A9D29.C7F0390D@3-cities.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kent Stewart wrote: > > David Kelly wrote: > > > > Peter Wemm writes: > > > Ted Sikora wrote: > > > > > > > During the night periodically my temp warning has been going off. > > > > I have it set to 118F. This happens only under FreeBSD. Linux continues > > > > to run cool at the old temperatures. Apparantly some code change has > > > > caused this. Does anyone know exactly where I should look? > > > > > > The main difference is that Linux halts the cpu in the idle loop, we don't. > > > As a result the cpu is in a tight spin waiting for a process to become > > > scheduleable. I have some patches half-done that I've been working on for > > > 4.0 that should probably be able to be adapted to the 3.x series. > > > > I'll let others debate whether or not FreeBSD halts the CPU when idle > > or not, or whether this has changed recently. > > > > OTOH Ted has a problem that is being ignored: that his CPU/Heatsink/Fan > > combination is apparently not up to a 100% duty cycle. DOS would cook > > it. As would most games. Or several "make buildworlds" in a row. No this is right after bootup. It started right after I did a make world around Christmas or coinciding with 3.4-STABLE. It runs 26 degrees hotter right from the get go. Linux still runs cool like always. FreeBSD used to be exactly the same. I have a SMP board with 2 CPU's. > > Antec and Startech have some dual fans for P-II's. The old P-II style > is hard to find but the K-7 Athalon apparently uses the same style of > fan. One of the vendors has a monster fan for a P-III. > > I run setiathome in the background on all of my computers, which keeps > the systems at 100% all of the time. I had a new 250W PS go out in > three days. The fans that come on P-II OEM's is not that great. > > It also sounds like he isn't getting enough outside air. You can't > cool if the inside air is hot. It runs at 87F on both CPU's and a 95F case temp under Linux regardless of load maybe varies 3-4 degrees +-. It's extremely cool. FreeBSD was just like that till I did a makeworld right around or after Christmas then this started. FreeBSD runs 26F degrees hotter right after bootup with nothing. Booting back to Linux it reverts back to the old temps...cool. It's just FreeBSD. Regards, -- Ted Sikora Jtl Development Group tsikora@powerusersbbs.com http://powerusersbbs.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 29 20: 7:16 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.rdc1.ct.home.com (ha1.rdc1.ct.home.com [24.2.0.66]) by hub.freebsd.org (Postfix) with ESMTP id E303215185; Wed, 29 Dec 1999 20:07:12 -0800 (PST) (envelope-from tsikora@home.com) Received: from home.com ([24.2.168.186]) by mail.rdc1.ct.home.com (InterMail v4.01.01.07 201-229-111-110) with ESMTP id <19991230040700.GEOR9446.mail.rdc1.ct.home.com@home.com>; Wed, 29 Dec 1999 20:07:00 -0800 Message-ID: <386ADA6B.5D0CEAB2@home.com> Date: Wed, 29 Dec 1999 23:07:07 -0500 From: Ted Sikora Reply-To: tsikora@powerusersbbs.com Organization: Jtl Development X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.3.34 i686) X-Accept-Language: en-US,en-GB MIME-Version: 1.0 To: Marc Nicholas Cc: "freebsd-hackers@FreeBSD.ORG" , "freebsd-stable@FreeBSD.ORG" Subject: Re: Temperature References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Marc Nicholas wrote: > > You're referring to the temps reported via an LM78 or similar, yes? The machines bios with Winbond W83782d IC > not reporting that the machine is actually getting HOTTER under FreeBSD? It is HOTTER under FreeBSD. Immediatelly upon boot-up it's 26F hotter under FreeBSD than under Linux. Sometime after 3.4-RC and now this started. (I follow the stable branch via CVSup) Under 3.3-STABLE the temerature was always the same as Linux...cool averaging 89F for the CPU's. Now it's over 113F under FreeBSD only. I know it's wierd but the machine does not lie. Under Linux it's the same as before 87-89F. > > On Wed, 29 Dec 1999, Ted Sikora wrote: > > > Here's a strange problem. I run Linux stable/development kernels > > and FreeBSD-3-STABLE on a SMP dual-boot workstation. The machines > > temperatures have always been in this range with either system: > > > > 87F CPU #0 > > 87F CPU #1 > > 95F Case Temp > > > > Sometime last week or early this week the temperature under FreeBSD only > > has changed to: > > > > 113F CPU #0 > > 113F CPU #1 > > 109F Case Temp > > This is right after boot and varies 3-4 Degrees + while running. > > > > During the night periodically my temp warning has been going off. > > I have it set to 118F. This happens only under FreeBSD. Linux continues > > to run cool at the old temperatures. Apparantly some code change has > > caused this. Does anyone know exactly where I should look? -- Ted Sikora Jtl Development Group tsikora@powerusersbbs.com http://powerusersbbs.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 29 20: 8: 4 1999 Delivered-To: freebsd-stable@freebsd.org Received: from ns.itga.com.au (ns.itga.com.au [202.53.40.210]) by hub.freebsd.org (Postfix) with ESMTP id 85C171575F for ; Wed, 29 Dec 1999 20:07:58 -0800 (PST) (envelope-from gnb@itga.com.au) Received: from lightning.itga.com.au (lightning.itga.com.au [192.168.71.20]) by ns.itga.com.au (8.9.3/8.9.3) with ESMTP id PAA57290 for ; Thu, 30 Dec 1999 15:07:50 +1100 (EST) (envelope-from gnb@itga.com.au) Received: from lightning.itga.com.au (lightning.itga.com.au [192.168.71.20]) by lightning.itga.com.au (8.9.3/8.9.3) with ESMTP id PAA11522; Thu, 30 Dec 1999 15:07:50 +1100 (EST) Message-Id: <199912300407.PAA11522@lightning.itga.com.au> X-Mailer: exmh version 2.0.1 12/23/97 From: Gregory Bond To: stable@freebsd.org Subject: mfc request: linux emulator Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 30 Dec 1999 15:07:50 +1100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG There were a huge raft of updates to the linux emulator committed to -HEAD on 29/9/99 that fix a number of holes. In particular, they implement the rt_sigsuspend() and setresuid() syscalls that are required to get Railroad Tycoon II for linux up & running. Could these changes be MFC'd? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 29 20:12:28 1999 Delivered-To: freebsd-stable@freebsd.org Received: from pawn.primelocation.net (pawn.primelocation.net [205.161.238.235]) by hub.freebsd.org (Postfix) with ESMTP id E811014D45; Wed, 29 Dec 1999 20:12:25 -0800 (PST) (envelope-from cdf.lists@fxp.org) Received: by pawn.primelocation.net (Postfix, from userid 1016) id C11F39B4F; Wed, 29 Dec 1999 23:12:21 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by pawn.primelocation.net (Postfix) with ESMTP id B784ABA0C; Wed, 29 Dec 1999 23:12:21 -0500 (EST) Date: Wed, 29 Dec 1999 23:12:21 -0500 (EST) From: "Chris D. Faulhaber" X-Sender: cdf.lists@pawn.primelocation.net To: tsikora@powerusersbbs.com Cc: Marc Nicholas , "freebsd-hackers@FreeBSD.ORG" , "freebsd-stable@FreeBSD.ORG" Subject: Re: Temperature In-Reply-To: <386ADA6B.5D0CEAB2@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 Wed, 29 Dec 1999, Ted Sikora wrote: > Marc Nicholas wrote: > > > > You're referring to the temps reported via an LM78 or similar, yes? > The machines bios with Winbond W83782d IC > That may explain it, then. > > not reporting that the machine is actually getting HOTTER under FreeBSD? > > It is HOTTER under FreeBSD. Immediatelly upon boot-up it's 26F > hotter under FreeBSD than under Linux. Sometime after 3.4-RC and > now this started. (I follow the stable branch via CVSup) Under > 3.3-STABLE the temerature was always the same as Linux...cool averaging > 89F for the CPU's. Now it's over 113F under FreeBSD only. I know it's > wierd but the machine does not lie. Under Linux it's the same as before > 87-89F. > The Winbond chipsets seems to have different multipliers than the LM78 chipsets. As author of lmmon/wmlmmon, I have yet to get someone to test so I can verify what the correct multipliers are. ----- 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 Wed Dec 29 20:12:55 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.rdc1.ct.home.com (ha1.rdc1.ct.home.com [24.2.0.66]) by hub.freebsd.org (Postfix) with ESMTP id 5E9F91576D for ; Wed, 29 Dec 1999 20:12:53 -0800 (PST) (envelope-from tsikora@home.com) Received: from home.com ([24.2.168.186]) by mail.rdc1.ct.home.com (InterMail v4.01.01.07 201-229-111-110) with ESMTP id <19991230041252.GFSM9446.mail.rdc1.ct.home.com@home.com>; Wed, 29 Dec 1999 20:12:52 -0800 Message-ID: <386ADBCC.3B2334E9@home.com> Date: Wed, 29 Dec 1999 23:13:00 -0500 From: Ted Sikora Reply-To: tsikora@powerusersbbs.com Organization: Jtl Development X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.3.34 i686) X-Accept-Language: en-US,en-GB MIME-Version: 1.0 To: Peter Wemm , "freebsd-stable@FreeBSD.ORG" Subject: Re: Temperature References: <19991229191516.17D671CA0@overcee.netplex.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 Peter Wemm wrote: > > Ted Sikora wrote: > > > During the night periodically my temp warning has been going off. > > I have it set to 118F. This happens only under FreeBSD. Linux continues > > to run cool at the old temperatures. Apparantly some code change has > > caused this. Does anyone know exactly where I should look? > > The main difference is that Linux halts the cpu in the idle loop, we don't. > As a result the cpu is in a tight spin waiting for a process to become > scheduleable. I have some patches half-done that I've been working on for > 4.0 that should probably be able to be adapted to the 3.x series. Has FreeBSD changed since 3.3-STABLE? This all started shortly after STABLE went from 3.4-RC to -STABLE. Under 3.3 it was the same as Linux give or take a few degrees. I would have to say something has changed since it appeared only after a recent make world. > > Cheers, > -Peter > -- > Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- Ted Sikora Jtl Development Group tsikora@powerusersbbs.com http://powerusersbbs.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 29 20:22:12 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.rdc1.ct.home.com (ha1.rdc1.ct.home.com [24.2.0.66]) by hub.freebsd.org (Postfix) with ESMTP id 51F3914ED2 for ; Wed, 29 Dec 1999 20:22:05 -0800 (PST) (envelope-from tsikora@home.com) Received: from home.com ([24.2.168.186]) by mail.rdc1.ct.home.com (InterMail v4.01.01.07 201-229-111-110) with ESMTP id <19991230042204.GHPP9446.mail.rdc1.ct.home.com@home.com>; Wed, 29 Dec 1999 20:22:04 -0800 Message-ID: <386ADDF3.FE274878@home.com> Date: Wed, 29 Dec 1999 23:22:11 -0500 From: Ted Sikora Reply-To: tsikora@powerusersbbs.com Organization: Jtl Development X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.3.34 i686) X-Accept-Language: en-US,en-GB MIME-Version: 1.0 To: Kent Stewart Cc: "freebsd-stable@FreeBSD.ORG" Subject: Re: Temperature References: <199912292320.RAA38266@nospam.hiwaay.net> <386A9D29.C7F0390D@3-cities.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kent Stewart wrote: > > David Kelly wrote: > > > > Peter Wemm writes: > > > Ted Sikora wrote: > > > > > > > During the night periodically my temp warning has been going off. > > > > I have it set to 118F. This happens only under FreeBSD. Linux continues > > > > to run cool at the old temperatures. Apparantly some code change has > > > > caused this. Does anyone know exactly where I should look? > > > > > > The main difference is that Linux halts the cpu in the idle loop, we don't. > > > As a result the cpu is in a tight spin waiting for a process to become > > > scheduleable. I have some patches half-done that I've been working on for > > > 4.0 that should probably be able to be adapted to the 3.x series. > > > > I'll let others debate whether or not FreeBSD halts the CPU when idle > > or not, or whether this has changed recently. > > > > OTOH Ted has a problem that is being ignored: that his CPU/Heatsink/Fan > > combination is apparently not up to a 100% duty cycle. DOS would cook > > it. As would most games. Or several "make buildworlds" in a row. > > Antec and Startech have some dual fans for P-II's. The old P-II style > is hard to find but the K-7 Athalon apparently uses the same style of > fan. One of the vendors has a monster fan for a P-III. > > I run setiathome in the background on all of my computers, which keeps > the systems at 100% all of the time. I had a new 250W PS go out in > three days. The fans that come on P-II OEM's is not that great. > > It also sounds like he isn't getting enough outside air. You can't > cool if the inside air is hot. > I run (2) seti sessions nightly usually on this machine. I have an Inwin case with 2 fans besides the ps and CPU's. One front mounted pulling air in and one Xlarge rear mounted pulling out next to the ps level with the CPU's. Air flow is strong right out and across the case?? Who knows? I'm tempted to put 3.3 back but.. Regards, -- Ted Sikora Jtl Development Group tsikora@powerusersbbs.com http://powerusersbbs.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 29 20:27:46 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.rdc1.ct.home.com (ha1.rdc1.ct.home.com [24.2.0.66]) by hub.freebsd.org (Postfix) with ESMTP id 7324114D9A for ; Wed, 29 Dec 1999 20:27:35 -0800 (PST) (envelope-from tsikora@home.com) Received: from home.com ([24.2.168.186]) by mail.rdc1.ct.home.com (InterMail v4.01.01.07 201-229-111-110) with ESMTP id <19991230042732.GIWR9446.mail.rdc1.ct.home.com@home.com>; Wed, 29 Dec 1999 20:27:32 -0800 Message-ID: <386ADF3B.EF6E12FA@home.com> Date: Wed, 29 Dec 1999 23:27:39 -0500 From: Ted Sikora Reply-To: tsikora@powerusersbbs.com Organization: Jtl Development X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.3.34 i686) X-Accept-Language: en-US,en-GB MIME-Version: 1.0 To: "Chris D. Faulhaber" , "freebsd-stable@FreeBSD.ORG" Subject: Re: Temperature References: Content-Type: multipart/mixed; boundary="------------217E2D7A4A6085CE492980CC" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------217E2D7A4A6085CE492980CC Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit "Chris D. Faulhaber" wrote: > > On Wed, 29 Dec 1999, Ted Sikora wrote: > > > Marc Nicholas wrote: > > > > > > You're referring to the temps reported via an LM78 or similar, yes? > > The machines bios with Winbond W83782d IC > > > > That may explain it, then. > > > > not reporting that the machine is actually getting HOTTER under FreeBSD? > > > > It is HOTTER under FreeBSD. Immediatelly upon boot-up it's 26F > > hotter under FreeBSD than under Linux. Sometime after 3.4-RC and > > now this started. (I follow the stable branch via CVSup) Under > > 3.3-STABLE the temerature was always the same as Linux...cool averaging > > 89F for the CPU's. Now it's over 113F under FreeBSD only. I know it's > > wierd but the machine does not lie. Under Linux it's the same as before > > 87-89F. > > > > The Winbond chipsets seems to have different multipliers than the LM78 > chipsets. As author of lmmon/wmlmmon, I have yet to get someone to test > so I can verify what the correct multipliers are. > Check out this lm_sensor script from Linux. Maybe it can help? Why did they report identical ranges before and now FreeBSD is hotter? That I don't understand. The alarm went off twice now. -- Ted Sikora Jtl Development Group tsikora@powerusersbbs.com http://powerusersbbs.com --------------217E2D7A4A6085CE492980CC Content-Type: text/plain; charset=us-ascii; name="sensors.conf" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="sensors.conf" # Hardware sensors configuration file # This configuration file will be used by all applications linked to # libsensors. # This config file consists of two parts: the heavily commented LM78 # example, and the real parts. Search for '####' if you want to skip # to the real stuff. # Hash marks introduce comments, which continue until the end of a line # # Identifiers consisting of only digits and letters can be used # unquoted; other identifiers must be quoted. Escape characters within # quotes operate like those in C. # A 'chip' line specifies what the following 'label', 'compute', 'set' and # (not yet implemented) 'valid' lines refer to. In this case, until the # next 'chip' line, everything refers to all lm78, lm78-j and lm79 # chips. Other examples are *-isa-* for everything on the ISA bus, and # lm78-j-i2c-*-4e for all lm78-j chips on address 0x4e of any I2C bus. # # If more chip statements match a specific chip, they are all considered. # Later lines overrule earlier lines, so if you set the in0 label for # lm78-* to "This", and later on the in0 label for lm78-isa-* to "That", # "That" is used for LM78 chips on the ISA bus, and "This" for LM78 # chips on a non-ISA bus. #chip "lm78-*" "lm78-j-*" "lm79-*" # A label line describes what a certain feature stands for on your # mainboard. Programs can retrieve these names and display them. # If no label is specified for a certain feature, the default name # (ie. 'fan1' for fan1) is used. # If you specify a label for in1, this label is also used for in1_min and # in1_max, unless they have their own labels declared. There are several # of these logical groups. # These are as advised in the LM78 and LM79 data sheets, and used on almost # any mainboard we have seen. # label in0 "VCore 1" # label in1 "VCore 2" # label in2 "+3.3V" # label in3 "+5V" # label in4 "+12V" # label in5 "-12V" # label in6 "-5V" # A compute line describes how to scale a certain feature. There are # two expressions in it: the first describes how the /proc value must # be translated to a user value, the second how a user value must be # translated to a /proc value. '@' is the value to operate on. You may # refer to other readable features (like '2 * vid'). # Like for the label statement, there are logical groups here. They are # sometimes a bit different, though. For example, fan1_div is in the # logical label group of fan1 (it gets the same label if none is declared # for it), but it is not in the compute group of fan1 (as it uses a # completely different system of values). # For positive voltages (in0..in4), two resistors are used, with the following # formula (R1,R2: resistor values, Vs: read voltage, Vin: pin voltage) # R1 = R2 * (Vs/Vin - 1) # For negative voltages (in5, in6) two resistors are used, with the following # formula (Rin,Rf: resistor values, Vs: read voltage, Vin: pin voltage) # Rin = (Vs * Rf) / Vin # Here are the official LM78 and LM79 data sheet values. # Vs R1,Rin R2,Rf Vin # in3 +5.0 6.8 10 +2.98 # in4 +12.0 30 10 +3.00 # in5 -12.0 240 60 +3.00 # in6 -5.0 100 60 +3.00 # These would lead to these declarations: # compute in3 ((6.8/10)+1)*@ , @/((6.8/10)+1) # compute in4 ((30/10)+1)*@ , @/((30/10)+1) # compute in5 -(240/60)*@ , -@/(240/60) # compute in6 -(100/60)*@ , -@/(100/60) # On almost any mainboard we have seen, the Winbond compute values lead to # much better results, though. # Vs R1,Rin R2,Rf Vin # in4 +12.0 28 10 +3.00 # in5 -12.0 210 60.4 +3.00 # in6 -5.0 90.9 60.4 +3.00 # These leads to these declarations: # compute in3 ((6.8/10)+1)*@ , @/((6.8/10)+1) # compute in4 ((28/10)+1)*@ , @/((28/10)+1) # compute in5 -(210/60.4)*@ , -@/(210/60.4) # compute in6 -(90.9/60.4)*@ , -@/(90.9/60.4) # Set statements set things like limits. Complete expressions can be # used. Not everything can sensibly be set: setting 'in0', for example, # is impossible! These settings are put through the compute translations; # so if we specify '12.8' for in6, '3.2' will actually be written! #set in0_max vid*1.05 #set in0_min vid*0.95 # Invalid statements tell certain features are not wanted. User programs can # still read them if they really want, though; this is just an advisory # marking. 'in0' would also invalidate 'in0_max' and 'in0_min'. # The invalid keyword is not yet recognized by the parser. # There is one other feature: the 'bus' statement. An example is below. #bus "i2c-0" "SMBus PIIX4 adapter at e800" "Non-I2C SMBus adapter" # If we refer from now on to 'i2c-0' in 'chip' lines, this will run-time # be matched to this bus. So even if the PIIX4 is called 'i2c-5' at that # moment, because five other adapters were detected first, 'i2c-0' in # the config file would always only match this physical bus. In the above # config file, this feature is not needed; but the next lines would # only affect the LM75 chips on the PIIX4 adapter: #chip "lm75-i2c-0-*" # You should really use the output of /proc/bus/chips to generate bus lines, # because one mistyped characted will inhibit the match. Wildcards are not # yet supported; spaces at the end are ignored, though. #### Here begins the real configuration file chip "lm78-*" "lm78-j-*" "lm79-*" "w83781d-*" "sis5595-*" # These are as advised in the LM78 and LM79 data sheets, and used on almost # any mainboard we have seen. label in0 "VCore 1" label in1 "VCore 2" label in2 "+3.3V" label in3 "+5V" label in4 "+12V" label in5 "-12V" label in6 "-5V" # For positive voltages (in0..in4), two resistors are used, with the following # formula (R1,R2: resistor values, Vs: read voltage, Vin: pin voltage) # R1 = R2 * (Vs/Vin - 1) # For negative voltages (in5, in6) two resistors are used, with the following # formula (Rin,Rf: resistor values, Vs: read voltage, Vin: pin voltage) # Rin = (Vs * Rf) / Vin # Here are the official LM78 and LM79 data sheet values. # Vs R1,Rin R2,Rf Vin # in3 +5.0 6.8 10 +2.98 # in4 +12.0 30 10 +3.00 # in5 -12.0 240 60 +3.00 # in6 -5.0 100 60 +3.00 # These would lead to these declarations: # compute in3 ((6.8/10)+1)*@ , @/((6.8/10)+1) # compute in4 ((30/10)+1)*@ , @/((30/10)+1) # compute in5 -(240/60)*@ , -@/(240/60) # compute in6 -(100/60)*@ , -@/(100/60) # On almost any mainboard we have seen, the Winbond compute values lead to # much better results, though. # Vs R1,Rin R2,Rf Vin # in4 +12.0 28 10 +3.00 # in5 -12.0 210 60.4 +3.00 # in6 -5.0 90.9 60.4 +3.00 # These leads to these declarations: compute in3 ((6.8/10)+1)*@ , @/((6.8/10)+1) compute in4 ((28/10)+1)*@ , @/((28/10)+1) compute in5 -(210/60.4)*@ , -@/(210/60.4) compute in6 -(90.9/60.4)*@ , -@/(90.9/60.4) # Here, we assume the VID readings are valid, and we use a max. 5% deviation set in0_min vid*0.95 set in0_max vid*1.05 set in1_min vid*0.95 set in1_max vid*1.05 set in2_min 3.3 * 0.95 set in2_max 3.3 * 1.05 set in3_min 5.0 * 0.95 set in3_max 5.0 * 1.05 set in4_min 12 * 0.95 set in4_max 12 * 1.05 set in5_min -12 * 0.95 set in5_max -12 * 1.05 set in6_min -5 * 0.95 set in6_max -5 * 1.05 chip "w83782d-*" "w83783s-*" # Same as above for w83781d except that in5 and in6 are computed differently. # Rather than an internal inverting op amp, the 82d/83s use standard positive # inputs and the negative voltages are level shifted by a 3.6V reference. # The math is convoluted, so we hope that your motherboard # uses the recommended resistor values. label in0 "VCore 1" label in1 "VCore 2" label in2 "+3.3V" label in3 "+5V" label in4 "+12V" label in5 "-12V" label in6 "-5V" label in7 "V5SB" label in8 "VBat" compute in3 ((6.8/10)+1)*@ , @/((6.8/10)+1) compute in4 ((28/10)+1)*@ , @/((28/10)+1) compute in5 (5.14 * @) - 14.91 , (@ + 14.91) / 5.14 compute in6 (3.14 * @) - 7.71 , (@ + 7.71) / 3.14 compute in7 ((6.8/10)+1)*@ , @/((6.8/10)+1) # set limits to 5% for the critical voltages # set limits to 10% for the non-critical voltages # set limits to 20% for the battery voltage set in0_min vid*0.95 set in0_max vid*1.05 set in1_min vid*0.95 set in1_max vid*1.05 set in2_min 3.3 * 0.95 set in2_max 3.3 * 1.05 set in3_min 5.0 * 0.95 set in3_max 5.0 * 1.05 set in4_min 12 * 0.90 set in4_max 12 * 1.10 set in5_min -12 * 0.90 set in5_max -12 * 1.10 set in6_min -5 * 0.95 set in6_max -5 * 1.05 set in7_min 5 * 0.95 set in7_max 5 * 1.05 set in8_min 3.0 * 0.80 set in8_max 3.0 * 1.20 # set up sensor types (thermistor is default) # 1 = PII/Celeron Diode; 2 = 3904 transistor; # 3435 = thermistor with Beta = 3435 # If temperature changes very little, try 1 or 2. # set sensor1 1 # set sensor2 2 # set sensor3 3435 chip "gl518sm-r00-*" "gl518sm-r80-*" # Factors and labels taken from GL518SM datasheet, they seem to give # reasonable values with EISCA connected Fan78 label vdd "+5V" label vin1 "+3.3V" label vin2 "+12V" label vin3 "Vcore" # vin2 depends on external resistors (4,7k and 15k assumed here) # vin1 and vin3 require no scaling compute vin2 (197/47)*@ , @/(197/47) set vdd_min 4.8 set vdd_max 5.2 set vin1_min 3.20 set vin1_max 3.40 set vin2_min 11.0 set vin2_max 13.0 set vin3_min 2.10 set vin3_max 2.30 chip "lm80-*" # The values below should be correct if you own a qdi BX (brilliant1) # mainboard. If not, please contact us, so we can figure out better readings. # Many thanks go to Peter T. Breuer for helping us figure # out how to handle the LM80. # For positive voltages (in0..in4), two resistors are used, with the following # formula (R1,R2: resistor values, Vs: read voltage, Vin: pin voltage) # R1 = R2 * (Vs/Vin - 1) # For negative voltages (in5, in6) two resistors are used, with the following # formula (R3,R4: resistor values, Vs: read voltage, Vin: pin voltage, # V5: +5V) # R3 = R4 * (Vs - Vin) / (Vin - V5) # Here are the official LM78 and LM79 data sheet values. # Vs R1,R3 R2,R4 Vin # +2.5V 23.7 75 +1.9 # +3.3V 22.1 30 +1.9 # +5.0 24 14.7 +1.9 # +12.0 160 30.1 +1.9 # -12.0 160 35.7 +1.9 # -5.0 36 16.2 +1.9 # Now curiously enough, VCore is connected with (unknown) resistors, which # translate a +2.8V to +1.9V. So we use that in the computations below. label in0 "+5V" label in1 "VTT" label in2 "+3.3V" label in3 "+Vcore" label in4 "+12V" label in5 "-12V" label in6 "-5V" compute in0 (24/14.7 + 1) * @ , @ / (24/14.7 + 1) compute in2 (22.1/30 + 1) * @ , @ / (22.1/30 + 1) compute in3 (2.8/1.9) * @, @ * 1.9/2.8 compute in4 (160/35.7 + 1) * @, @ / (160/35.7 + 1) compute in5 (160/35.7)*(@ - in0) + @, (@ + in0 * 160/25.7)/ (1 + 160/25.7) compute in6 (36/16.2)*(@ - in0) + @, (@ + in0 * 36/16.2) / (1 + 36/16.2) set in0_min 5 * 0.95 set in0_max 5 * 0.95 # What is your VTT? It is probably not this value... set in1_min 2*0.95 set in1_max 2*1.05 set in2_min 3.3 * 0.95 set in2_max 3.3 * 1.05 # What is your VCore? It is probably not this value... set in3_min 1.9 * 0.95 set in3_max 1.9 * 1.05 set in4_min 12 * 0.95 set in4_max 12 * 1.05 set in5_min -12 * 0.95 set in5_max -12 * 1.05 set in6_min -5 * 0.95 set in6_max -5 * 1.05 chip "maxilife-cg-*" "maxilife-co-*" "maxilife-as-*" label fan1 "HDD Fan" label fan2 "PCI Fan" label fan3 "CPU Fan" label temp2 "PCI Temp" label temp4 "HDD Temp" label temp5 "CPU Temp" label vid1 "V+12" # vid1 need to be scaled by 6.337 other voltages # require no scaling compute vid1 6.337*@ , @/6.337 chip "maxilife-cg-*" # invalid temp1 label temp3 "BX Temp" label vid2 "Vcpu1" label vid3 "Vcpu2" # invalid vid4 chip "maxilife-co-*" label temp1 "CPU 1 Temp" label temp3 "CPU 2 Temp" label vid2 "Vcpu1" label vid3 "Vcpu2" label vid4 "VcacheL2" chip "maxilife-as-*" # invalid temp1 # invalid temp3 label vid2 "Vcpu" # invalid vid3 # invalid vid4 bus "i2c-0" "SMBus PIIX4 adapter at 5000" "Non-I2C SMBus adapter" --------------217E2D7A4A6085CE492980CC-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 29 20:50:54 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id 693F3151B7 for ; Wed, 29 Dec 1999 20:50:52 -0800 (PST) (envelope-from dkelly@nospam.hiwaay.net) Received: from nospam.hiwaay.net (tnt8-208-170-118-135.dialup.HiWAAY.net [208.170.118.135]) by mail.HiWAAY.net (8.9.3/8.9.0) with ESMTP id WAA04789; Wed, 29 Dec 1999 22:50:50 -0600 (CST) Received: from localhost (localhost [127.0.0.1]) by nospam.hiwaay.net (8.9.3/8.9.3) with ESMTP id WAA72948; Wed, 29 Dec 1999 22:50:47 -0600 (CST) (envelope-from dkelly@nospam.hiwaay.net) Message-Id: <199912300450.WAA72948@nospam.hiwaay.net> X-Mailer: exmh version 2.1.1 10/15/1999 To: tsikora@powerusersbbs.com Cc: Kent Stewart , "freebsd-stable@FreeBSD.ORG" From: David Kelly Subject: Re: Temperature In-reply-to: Message from Ted Sikora of "Wed, 29 Dec 1999 23:22:11 EST." <386ADDF3.FE274878@home.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 29 Dec 1999 22:50:41 -0600 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ted Sikora writes: > I run (2) seti sessions nightly usually on this machine. I have an Inwin > case with 2 fans besides the ps and CPU's. One front mounted pulling air > in and one Xlarge rear mounted pulling out next to the ps level with the > CPU's. Air flow is strong right out and across the case?? Who knows? I'm > tempted to put 3.3 back but.. Did you miss the other posts? "Chris D. Faulhaber" said: > The Winbond chipsets seems to have different multipliers than the LM78 > chipsets. As author of lmmon/wmlmmon, I have yet to get someone to > test so I can verify what the correct multipliers are. Another point to assert that your problem is simply one of calibration is when you observe instantly on boot the CPU temperature is 26F hotter. There is too much thermal mass in your CPU and heatsink for it to rise 26F as quickly as you seem to indicate. You need one of the digital indoor/outdoor thermometers available at Radio Shack, K-Mart, Wal-Mart, etc. Paid $15 last time. Forgot it that one had max/min memory or not. Anyhow, put the outdoor probe on your heatsink and get a 2nd opinion. When this thermometer doesn't read significantly different between Linux and FreeBSD you can be assured there is a only calibration problem. Those digital indoor/outdoor thermometers are great. Made a 1000 mile road trip this past week. Thru the outdoor probe out a window. Sure was nice to know when I entered freezing conditions. Sure was miserable to know when I bought gas Tuesday it was 21F out. Now I need a wind speed meter as I'm certain it was blowing 30 MPH but have no way of proving it. Would also be nice to know what the windspeed is over the car as I'm also pretty sure I drove into a headwind the 2nd 500 miles. BTW: I'd be interested in a CPU temerature monitoring program for my Asus P2B-S. Asus uses a termistor, not the LM part. -- David Kelly N4HHE, dkelly@hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 29 21:29:28 1999 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 B1D6014F8F for ; Wed, 29 Dec 1999 21:29:26 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p24-dn03kiryunisiki.gunma.ocn.ne.jp [210.232.224.153]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id OAA28444; Thu, 30 Dec 1999 14:29:07 +0900 (JST) Message-ID: <386AE7A5.8C02B7F7@newsguy.com> Date: Thu, 30 Dec 1999 14:03:33 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: tsikora@powerusersbbs.com Cc: "Chris D. Faulhaber" , "freebsd-stable@FreeBSD.ORG" Subject: Re: Temperature References: <386ADF3B.EF6E12FA@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 Ted Sikora wrote: > > Why did they report identical ranges before and now FreeBSD is hotter? Programs lie. Do you know for a FACT that it is hotter? I mean, do you used a REAL thermometer to measure it? If not, stop saying it is "hotter" and start saying it "says it is hotter". These are very different things. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "Nice try, Lao Che." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 29 21:29:36 1999 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 CAA2F14CB3 for ; Wed, 29 Dec 1999 21:29:33 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p24-dn03kiryunisiki.gunma.ocn.ne.jp [210.232.224.153]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id OAA28425; Thu, 30 Dec 1999 14:28:58 +0900 (JST) Message-ID: <386AE660.F74B4CB2@newsguy.com> Date: Thu, 30 Dec 1999 13:58:08 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: tsikora@powerusersbbs.com Cc: Peter Wemm , "freebsd-stable@FreeBSD.ORG" Subject: Re: Temperature References: <19991229191516.17D671CA0@overcee.netplex.com.au> <386ADBCC.3B2334E9@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 Ted Sikora wrote: > > Has FreeBSD changed since 3.3-STABLE? This all started shortly after > STABLE went from 3.4-RC to -STABLE. Under 3.3 it was the same as Linux > give or take a few degrees. I would have to say something has changed > since it appeared only after a recent make world. Wild guess... Bruce's scheduler fix. I think it dates from around that time, and it just might be related. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "Nice try, Lao Che." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 29 22: 1:23 1999 Delivered-To: freebsd-stable@freebsd.org Received: from freeway.dcfinc.com (cx74889-a.phnx3.az.home.com [24.1.193.157]) by hub.freebsd.org (Postfix) with ESMTP id C21E815091 for ; Wed, 29 Dec 1999 22:01:21 -0800 (PST) (envelope-from chad@freeway.dcfinc.com) Received: (from chad@localhost) by freeway.dcfinc.com (8.8.8/8.8.8) id XAA18333; Wed, 29 Dec 1999 23:01:14 -0700 (MST) (envelope-from chad) Date: Wed, 29 Dec 1999 23:01:14 -0700 From: "Chad R. Larson" To: David Kelly Cc: tsikora@powerusersbbs.com, Kent Stewart , "freebsd-stable@FreeBSD.ORG" Subject: Re: Temperature Message-ID: <19991229230114.A18295@freeway.dcfinc.com> References: <199912300450.WAA72948@nospam.hiwaay.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <199912300450.WAA72948@nospam.hiwaay.net>; from dkelly@hiwaay.net on Wed, Dec 29, 1999 at 10:50:41PM -0600 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Dec 29, 1999 at 10:50:41PM -0600, David Kelly wrote: > Those digital indoor/outdoor thermometers are great. Made a 1000 mile > road trip this past week. Thru the outdoor probe out a window. Sure > was nice to know when I entered freezing conditions. Sure was > miserable to know when I bought gas Tuesday it was 21F out. Now I > need a wind speed meter as I'm certain it was blowing 30 MPH but have > no way of proving it. Would also be nice to know what the windspeed > is over the car as I'm also pretty sure I drove into a headwind the > 2nd 500 miles. I'm very happy with my Kestrel from Nielsen-Kellerman instruments. Mine's the 3000, which has temperature, wind speed and humidity (and the computed values derived therefrom, like dewpoint, windchill and heat index). A weather station in the hand. The 2000 doesn't do humidity. The 1000 does wind speed only. Check http://www.kestrel-instruments.com/ -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org larson1@home.net DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 29 22:15:27 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.rdc1.ct.home.com (ha1.rdc1.ct.home.com [24.2.0.66]) by hub.freebsd.org (Postfix) with ESMTP id 38F2E15091 for ; Wed, 29 Dec 1999 22:15:25 -0800 (PST) (envelope-from tsikora@home.com) Received: from home.com ([24.2.168.186]) by mail.rdc1.ct.home.com (InterMail v4.01.01.07 201-229-111-110) with ESMTP id <19991230061524.GZMO9446.mail.rdc1.ct.home.com@home.com>; Wed, 29 Dec 1999 22:15:24 -0800 Message-ID: <386AF883.FB8E950A@home.com> Date: Thu, 30 Dec 1999 01:15:31 -0500 From: Ted Sikora Reply-To: tsikora@powerusersbbs.com Organization: Jtl Development X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.4-STABLE i386) X-Accept-Language: en-US,en-GB MIME-Version: 1.0 To: "Daniel C. Sobral" , "freebsd-stable@FreeBSD.ORG" Subject: Re: Temperature References: <386ADF3B.EF6E12FA@home.com> <386AE7A5.8C02B7F7@newsguy.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Daniel C. Sobral" wrote: > > Ted Sikora wrote: > > > > Why did they report identical ranges before and now FreeBSD is hotter? Beats me. It changed after I made world about a week ago. > > Programs lie. Do you know for a FACT that it is hotter? I mean, do you > used a REAL thermometer to measure it? If not, stop saying it is > "hotter" and start saying it "says it is hotter". These are very > different things. > Picky..picky it says it's hotter. I am asumming the Winbond IC and the bios readings are correct. I just installed lmmon/chm and lm_sensors in Linux they all confirm what I have been saying. After 3.3 went to 3.4-stable my machine now says it's hotter under freebsd by about 24-26 degrees. > -- > Daniel C. Sobral (8-DCS) > dcs@newsguy.com > dcs@freebsd.org > > "Nice try, Lao Che." > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- Ted Sikora Jtl Development Group tsikora@powerusersbbs.com http://powerusersbbs.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 29 23:17:26 1999 Delivered-To: freebsd-stable@freebsd.org Received: from jason.argos.org (a1-3b058.neo.rr.com [24.93.181.58]) by hub.freebsd.org (Postfix) with ESMTP id 350EB15141 for ; Wed, 29 Dec 1999 23:17:23 -0800 (PST) (envelope-from mike@argos.org) Received: from localhost (mike@localhost) by jason.argos.org (8.9.1/8.9.1) with ESMTP id CAA06386; Thu, 30 Dec 1999 02:17:06 -0500 Date: Thu, 30 Dec 1999 02:17:06 -0500 (EST) From: Mike Nowlin To: tsikora@powerusersbbs.com Cc: "Daniel C. Sobral" , "freebsd-stable@FreeBSD.ORG" Subject: Re: Temperature In-Reply-To: <386AF883.FB8E950A@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 > Picky..picky it says it's hotter. I am asumming the Winbond IC and the > bios readings are correct. I just installed lmmon/chm and lm_sensors in > Linux they all confirm what I have been saying. > After 3.3 went to 3.4-stable my machine now says it's hotter under > freebsd by about 24-26 degrees. Seems to me that if the temperature was actually that much higher, some basic rules of physics are being broken by your machine..... I could be wrong, but it seems to me that for the internal temp of the case (motherboard) to be raised by 24-26 degrees, the CPU itself would have to get a whole lot hotter than the same 24-26 degrees. (Assuming, of course, that the MB temp sensor isn't physically mounted directly beneath the CPU. If it is, you bought a motherboard designed by morons - get a different one.) I'd have to agree that you're seeing a software reporting error, not an actual temperature increase.... Try it with a real thermometer, and if you don't have one of those, use your thumb. You'll feel the difference if it's that much hotter. mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 30 0:58:38 1999 Delivered-To: freebsd-stable@freebsd.org Received: from pluto.psn.net (pluto.psn.net [207.211.58.12]) by hub.freebsd.org (Postfix) with ESMTP id C2B9814DBF; Thu, 30 Dec 1999 00:58:33 -0800 (PST) (envelope-from will@shadow.blackdawn.com) Received: from 15-155.008.popsite.net ([209.69.195.155] helo=shadow.blackdawn.com) by pluto.psn.net with esmtp (PSN Internet Service 3.12 #1) id 123bPk-0007Of-00; Thu, 30 Dec 1999 01:58:32 -0700 Received: (from will@localhost) by shadow.blackdawn.com (8.9.3/8.9.3) id DAA90605; Thu, 30 Dec 1999 03:58:29 -0500 (EST) (envelope-from will) Message-ID: X-Mailer: XFMail 1.3.1 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <386A4CEC.EB948EE8@home.com> Date: Thu, 30 Dec 1999 03:58:29 -0500 (EST) Reply-To: Will Andrews From: Will Andrews To: tsikora@powerusersbbs.com Subject: RE: Temperature Cc: "freebsd-hackers@FreeBSD.ORG" , "freebsd-stable@FreeBSD.ORG" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ not subscribed to -hackers, but -stable ] On 29-Dec-99 Ted Sikora wrote: > Here's a strange problem. I run Linux stable/development kernels > and FreeBSD-3-STABLE on a SMP dual-boot workstation. The machines > temperatures have always been in this range with either system: > > 87F CPU #0 > 87F CPU #1 > 95F Case Temp > > Sometime last week or early this week the temperature under FreeBSD only > has changed to: > > 113F CPU #0 > 113F CPU #1 > 109F Case Temp > This is right after boot and varies 3-4 Degrees + while running. > > During the night periodically my temp warning has been going off. > I have it set to 118F. This happens only under FreeBSD. Linux continues > to run cool at the old temperatures. Apparantly some code change has > caused this. Does anyone know exactly where I should look? I would first confirm this kind of anomaly by loading that overheating machine with Linux and then seeing where the temperatures go. I'm not convinced you've taken into account all environment variables (and I don't mean shell variables). My system under FreeBSD tends to stay around 32C, or a little under 90F. I run FreeBSD 3.4-STABLE here, with adequate fan power and ventilation. The box is a 25" full tower case loaded with scsi stuff, and so on.. Sometimes (after one day's power-off) it starts up with a minimum temperature of 19C (66F). I've never seen it go above 35C (95F), so I'm a little curious about your problem. I doubt it has anything to do with the OS. [ Note: These temperatures are obtained from the intpm device via wmhm. I had to calculate the F's by the formula F = (C)(9/5) + 32. ] I admit I haven't seen this machine above 60 days uptime in a long while.. -- Will Andrews GCS/E/S @d- s+:+>+:- a--->+++ C++ UB++++ P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP+>+++ t++ 5 X++ R+ tv+ b++>++++ DI+++ D+ G++>+++ e->++++ h! r-->+++ y? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 30 2:25:51 1999 Delivered-To: freebsd-stable@freebsd.org Received: from chuggalug.clues.com (chuggalug.clues.com [194.217.82.22]) by hub.freebsd.org (Postfix) with ESMTP id D05CC15212 for ; Thu, 30 Dec 1999 02:25:49 -0800 (PST) (envelope-from geoffb@chuggalug.clues.com) Received: (from geoffb@localhost) by chuggalug.clues.com (8.9.3/8.9.3) id KAA36228; Thu, 30 Dec 1999 10:25:39 GMT (envelope-from geoffb) Date: Thu, 30 Dec 1999 10:25:39 +0000 From: Geoff Buckingham To: tsikora@powerusersbbs.com Cc: "Chris D. Faulhaber" , "freebsd-stable@FreeBSD.ORG" Subject: Re: Temperature Message-ID: <19991230102539.A36187@chuggalug.clues.com> References: <386ADF3B.EF6E12FA@home.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <386ADF3B.EF6E12FA@home.com>; from Ted Sikora on Wed, Dec 29, 1999 at 11:27:39PM -0500 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Dec 29, 1999 at 11:27:39PM -0500, Ted Sikora wrote: > > Why did they report identical ranges before and now FreeBSD is hotter? > That I don't understand. The alarm went off twice now. > Is this a software alarm or a BIOS/firmware type thing? the later indicating really being hotter as opposed to claiming to be hotter. -- GeoffB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 30 3:42:26 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.scc.nl (node1374.a2000.nl [62.108.19.116]) by hub.freebsd.org (Postfix) with ESMTP id 70D09152D9 for ; Thu, 30 Dec 1999 03:42:21 -0800 (PST) (envelope-from freebsd-stable@scc.nl) Received: (from daemon@localhost) by mail.scc.nl (8.9.3/8.9.3) id MAA24772 for stable@FreeBSD.org; Thu, 30 Dec 1999 12:23:47 +0100 (CET) (envelope-from freebsd-stable@scc.nl) Received: from GATEWAY by dwarf.hq.scc.nl with netnews for stable@FreeBSD.org (stable@FreeBSD.org) To: stable@FreeBSD.org Date: Thu, 30 Dec 1999 12:23:43 +0100 From: Marcel Moolenaar Message-ID: <386B40BF.8C90B67D@scc.nl> Organization: SCC vof Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit References: <199912300407.PAA11522@lightning.itga.com.au> Subject: Re: mfc request: linux emulator Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Gregory Bond wrote: > > There were a huge raft of updates to the linux emulator committed to -HEAD on > 29/9/99 that fix a number of holes. In particular, they implement the > rt_sigsuspend() and setresuid() syscalls that are required to get Railroad > Tycoon II for linux up & running. > > Could these changes be MFC'd? rt_sigsuspend should not be implemented on -stable, because it breaks more than it fixes. setresuid is not implemented in -current (yet). Please send this to -emulation in the future. I just happened to see this, but normally skip -questions and -stable if I don't have the time. -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD project mailto:marcel@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 30 4: 7:24 1999 Delivered-To: freebsd-stable@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 9592F14FF9 for ; Thu, 30 Dec 1999 04:07:19 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 595DD1CA0; Thu, 30 Dec 1999 20:07:11 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: Rasmus Kaj Cc: tsikora@powerusersbbs.com, "freebsd-stable@FreeBSD.ORG" Subject: Re: Temperature In-Reply-To: Message from Rasmus Kaj of "Wed, 29 Dec 1999 20:49:22 +0100." <386A65C2.B2BFF596@Raditex.se> Date: Thu, 30 Dec 1999 20:07:11 +0800 From: Peter Wemm Message-Id: <19991230120711.595DD1CA0@overcee.netplex.com.au> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Rasmus Kaj wrote: > Peter Wemm wrote, about processor temp, etc: > > > The main difference is that Linux halts the cpu in the idle loop, we don't. > > As a result the cpu is in a tight spin waiting for a process to become > > scheduleable. I have some patches half-done that I've been working on for > > 4.0 that should probably be able to be adapted to the 3.x series. > > The FAQ says that FreeBSD does use the HLT instruction when idle, is > this wrong? In uniprocessor mode, yes it uses HLT (and always has). Under SMP it does not (and never has). Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 30 4:36:47 1999 Delivered-To: freebsd-stable@freebsd.org Received: from dozer.skynet.be (dozer.skynet.be [195.238.2.36]) by hub.freebsd.org (Postfix) with ESMTP id 6BE5314E49 for ; Thu, 30 Dec 1999 04:36:45 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by dozer.skynet.be (8.9.3/odie-relay-v1.0) with ESMTP id NAA18224; Thu, 30 Dec 1999 13:36:36 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@foxbert.skynet.be Message-Id: In-Reply-To: <10571.991227@zhurnal.ru> References: <10571.991227@zhurnal.ru> Date: Thu, 30 Dec 1999 13:36:03 +0100 To: Ilya Obshadko , stable@FreeBSD.ORG From: Brad Knowles Subject: Re: IPFILTER: problem with denied ACK packets Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 1:43 PM +0300 1999/12/27, Ilya Obshadko wrote: > Here's a strange problem with IPFILTER. Rulefile looks like this: This one has been sitting around for a few days, and I've been waiting with interest to hear if anyone has any thoughts. I haven't heard any yet, so I'm wondering if this has been fixed in private, or if there is something else going on. Anybody else heard anything? -- These are my opinions -- not to be taken as official Skynet policy ____________________________________________________________________ |o| Brad Knowles, Belgacom Skynet NV/SA |o| |o| Systems Architect, News & FTP Admin Rue Col. Bourg, 124 |o| |o| Phone/Fax: +32-2-706.11.11/12.49 B-1140 Brussels |o| |o| http://www.skynet.be Belgium |o| \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. Unix is very user-friendly. It's just picky who its friends are. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 30 6:34:51 1999 Delivered-To: freebsd-stable@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 93BD21515F for ; Thu, 30 Dec 1999 06:34:44 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id PAA25924; Thu, 30 Dec 1999 15:19:05 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id OAA62941; Thu, 30 Dec 1999 14:15:01 +0100 (CET) (envelope-from wilko) Date: Thu, 30 Dec 1999 14:15:01 +0100 From: Wilko Bulte To: Peter Wemm Cc: Rasmus Kaj , tsikora@powerusersbbs.com, "freebsd-stable@FreeBSD.ORG" Subject: Re: Temperature Message-ID: <19991230141501.C62691@yedi.iaf.nl> References: <19991230120711.595DD1CA0@overcee.netplex.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <19991230120711.595DD1CA0@overcee.netplex.com.au>; from peter@netplex.com.au on Thu, Dec 30, 1999 at 08:07:11PM +0800 X-OS: FreeBSD yedi.iaf.nl 3.4-STABLE FreeBSD 3.4-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Dec 30, 1999 at 08:07:11PM +0800, Peter Wemm wrote: > Rasmus Kaj wrote: > > Peter Wemm wrote, about processor temp, etc: > > > > > The main difference is that Linux halts the cpu in the idle loop, we don't. > > > As a result the cpu is in a tight spin waiting for a process to become > > > scheduleable. I have some patches half-done that I've been working on for > > > 4.0 that should probably be able to be adapted to the 3.x series. > > > > The FAQ says that FreeBSD does use the HLT instruction when idle, is > > this wrong? > > In uniprocessor mode, yes it uses HLT (and always has). Under SMP it does > not (and never has). Peter, please allow me a layman's question: is there an easy explanation for this difference? Thanks, -- Wilko Bulte Arnhem, The Netherlands - The FreeBSD Project WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 30 7:14:49 1999 Delivered-To: freebsd-stable@freebsd.org Received: from ssh.tepkom.ru (ssh.tepkom.ru [195.9.10.32]) by hub.freebsd.org (Postfix) with ESMTP id A431E15346 for ; Thu, 30 Dec 1999 07:14:40 -0800 (PST) (envelope-from ssh@tepkom.ru) Received: from tepkom.ru (localhost [127.0.0.1]) by ssh.tepkom.ru (8.9.3/8.9.1) with ESMTP id SAA38155 for ; Thu, 30 Dec 1999 18:12:52 +0300 (MSK) (envelope-from ssh@tepkom.ru) Message-ID: <386B7673.CDBB4B93@tepkom.ru> Date: Thu, 30 Dec 1999 18:12:51 +0300 From: "Serguei Y. Shilov" Organization: LANIT-Terkom, Inc. X-Mailer: Mozilla 4.6 [en] (X11; I; FreeBSD 3.4-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: PPP reconnect problem Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! Happy New Year at the 1st! Be lucky, happy at new year and of course stably! I've update my kernel and userland to 3.4-STABLE via CVS and find that I could not reconnect with my ISP after carrier lost. I use next strings in my /etc/ppp/ppp.conf file: set redial 3 50 ; it's work set reconnect 3 50 ; it's don't work Must I downgrade ppp to 3.3-RELEASE? It's a bad idea for me. Is there other suggestions? -- Serguei Shilov, M.Sc., C.U.S.E. Networked system administrator of LANIT-Terkom Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 30 8:17:49 1999 Delivered-To: freebsd-stable@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id F1AF614D65 for ; Thu, 30 Dec 1999 08:17:41 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 921061CC6; Fri, 31 Dec 1999 00:17:35 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: Wilko Bulte Cc: Rasmus Kaj , tsikora@powerusersbbs.com, "freebsd-stable@FreeBSD.ORG" Subject: Re: Temperature In-Reply-To: Message from Wilko Bulte of "Thu, 30 Dec 1999 14:15:01 +0100." <19991230141501.C62691@yedi.iaf.nl> Date: Fri, 31 Dec 1999 00:17:35 +0800 From: Peter Wemm Message-Id: <19991230161735.921061CC6@overcee.netplex.com.au> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Wilko Bulte wrote: > On Thu, Dec 30, 1999 at 08:07:11PM +0800, Peter Wemm wrote: > > Rasmus Kaj wrote: > > > Peter Wemm wrote, about processor temp, etc: > > > > > > > The main difference is that Linux halts the cpu in the idle loop, we do n't. > > > > As a result the cpu is in a tight spin waiting for a process to become > > > > scheduleable. I have some patches half-done that I've been working on for > > > > 4.0 that should probably be able to be adapted to the 3.x series. > > > > > > The FAQ says that FreeBSD does use the HLT instruction when idle, is > > > this wrong? > > > > In uniprocessor mode, yes it uses HLT (and always has). Under SMP it does > > not (and never has). > > Peter, > > please allow me a layman's question: is there an easy explanation for this > difference? Yes. Under UP, the cpu only goes to sleep if there is absolutely nothing else to do except wait for an interrupt (clock, etc). Under SMP, there is more than one cpu. If one cpu is asleep in a HLT, and the other one changes the run queues, there is nothing to wake up the sleeping CPU even though there is now a job in the queue. So.. we let the cpu spin looking at the "queue not empty" bits so it never gets caught sleeping on the job. Now we have a more flexible IPI system and have moved the runqueue manipulation out of assembler (in -current only) into specially tuned C code, we can easily add an IPI transmission call to the "add process to a run queue" routine. This isn't automatically a good idea though.. sending an IPI is relatively expensive so we don't want to do it unless it's needed. Defining "when needed" is the tricky part. Remember that the cpu doing the change to the run queue is holding the kernel lock, so the other cpu cannot enter the kernel to get a process while the first one is holding the lock. We also don't want to wake the other cpu if there is only one single process in the queues as the current cpu will take it and by the time the other cpu gets into the kernel at last, the queues will be empty again and we'll have wasted an IPI. Probably the best thing to do is have each cpu set a bit flag indicating it's halting, and each time a cpu is leaving the kernel to return to user mode it should check if there is still another process available and at least one cpu is sleeping, then do a targeted IPI to wake up the sleepers. The initial cpu will leave the kernel lock in a moment and one of the other cpus will grab the process. As I've said, I've half finished this (under -current), it shouldn't be too hard to finish the rest. On the subject of CPU heat etc, remember that halting a cpu doesn't do a thing if you're running seti@home or rc5des or something cpu intensive. There is always something to run and the halt never happens. One would assume that people with SMP machines actually intend to use the CPUs so that's the other reason it's never bothered anyone enough to finish it. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 30 10:37:17 1999 Delivered-To: freebsd-stable@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 3C16D153B8; Thu, 30 Dec 1999 10:37:14 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id KAA76049; Thu, 30 Dec 1999 10:37:12 -0800 (PST) (envelope-from dillon) Date: Thu, 30 Dec 1999 10:37:12 -0800 (PST) From: Matthew Dillon Message-Id: <199912301837.KAA76049@apollo.backplane.com> To: Tom Cc: freebsd-stable@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: softupdates and debug.max_softdeps References: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, in general I would not mess with max_softdeps - softupdates gets very inefficient if it hits its limits. I think you may have found a flaw in the code, though. Softupdates reschedules its vnode sync whenever it does something to the vnode. Postmark must be operating on the same set of files for very long periods of time, including truncating and extending them, for softupdates to get that far behind! Kirk may have to modify the vnode scheduling to not reschedule the vnode beyond a certain aggregate delay in order to ensure that things get synchronized in a reasonable period of time. Softupdates biggest problem are with overly-long delays in block reclamation - several people have commented on it. I think what you are seeing is a special case of this problem that causes it to be much worse then normal. In the mean time you have a couple of choices. You can try running 'sync' every so often, or you can write a small C program to fsync() the files postfix messes with every so often. -Matt Matthew Dillon : I'm trying to find some information on reasonable settings for :debug.max_softdeps on a recent FreeBSD-stable system. : : It seems that if you have a machine that is able to generate disk IO :much faster than can be handled, has a large amount of RAM (and therefore :debug.max_softdeps is large), and the filesystem is very large (about :80GB), filesystem metadata updates can get _very_ far behind. : : For instance, on a test system running 4 instances of postmark :continuously for 24 hours, "df" reports that 40 GB of disk space is being :used, even though only about 5 GB is actually used. If I kill the :postmark processes, the metadata is eventually dribbled out and "df" :reports 5GB in use. It takes about 20 minutes for the metadata to be :updated on a completely ideal system. : : On this particular system, it doesn't seem to stabilize either. If the :4 postmark instances are allowed to run, disk usage seems to climb :indefinitely (at 40GB it was still climbing), until eventually the machine :silently reboots. : : debug.max_softdeps is by default set to 523,712 (1 GB of RAM). Is that :a resonable value? I see some tests in the docs with max_softdeps set to :4000 or so. : : :Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 30 11:14:23 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail2.uniserve.com (mail2.uniserve.com [204.244.156.7]) by hub.freebsd.org (Postfix) with ESMTP id BDBF0153C0; Thu, 30 Dec 1999 11:14:16 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca ([204.244.186.218]) by mail2.uniserve.com with smtp (Exim 3.03 #4) id 123l1X-0004iR-00; Thu, 30 Dec 1999 11:14:11 -0800 Date: Thu, 30 Dec 1999 11:14:08 -0800 (PST) From: Tom X-Sender: tom@shell.uniserve.ca To: Matthew Dillon Cc: freebsd-stable@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: softupdates and debug.max_softdeps In-Reply-To: <199912301837.KAA76049@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yes, postmark operates on the same file set. I used the following postmark settings: set number 30000 set transactions 4000000 set size 1500 200000 which uses a set of 30,000 files, and does a 4,000,000 transactions them (random mix of various operations), and size between 1,500 and 200,000 bytes. BTW, I hacked my version of postmark to use unsigned ints in various places. I guess by having a very large filesystem (80GB), and mostly empty, the softupdate code is able to queue an enormous amount of metadata updates over time. I tried forcing max_softdeps down to 50,000, and within a couple of hours all processes accessing that filesystem hung! Also, postmark is filesytem benchmarking and stress tester utility. Adding fsync() would defeat the purpose a bit! So in summary, if max_softdeps is left at the default, the system will reboot in 24 to 36 hours. If max_softdeps is set down, filesystem access will eventually hang within 12 hours. On Thu, 30 Dec 1999, Matthew Dillon wrote: > Well, in general I would not mess with max_softdeps - softupdates gets > very inefficient if it hits its limits. I think you may have found a > flaw in the code, though. Softupdates reschedules its vnode sync whenever > it does something to the vnode. Postmark must be operating on the same > set of files for very long periods of time, including truncating and > extending them, for softupdates to get that far behind! Kirk may have > to modify the vnode scheduling to not reschedule the vnode beyond a > certain aggregate delay in order to ensure that things get synchronized > in a reasonable period of time. > > Softupdates biggest problem are with overly-long delays in block > reclamation - several people have commented on it. I think what you > are seeing is a special case of this problem that causes it to be much > worse then normal. > > In the mean time you have a couple of choices. You can try running > 'sync' every so often, or you can write a small C program to fsync() > the files postfix messes with every so often. > > -Matt > Matthew Dillon > > > : I'm trying to find some information on reasonable settings for > :debug.max_softdeps on a recent FreeBSD-stable system. > : > : It seems that if you have a machine that is able to generate disk IO > :much faster than can be handled, has a large amount of RAM (and therefore > :debug.max_softdeps is large), and the filesystem is very large (about > :80GB), filesystem metadata updates can get _very_ far behind. > : > : For instance, on a test system running 4 instances of postmark > :continuously for 24 hours, "df" reports that 40 GB of disk space is being > :used, even though only about 5 GB is actually used. If I kill the > :postmark processes, the metadata is eventually dribbled out and "df" > :reports 5GB in use. It takes about 20 minutes for the metadata to be > :updated on a completely ideal system. > : > : On this particular system, it doesn't seem to stabilize either. If the > :4 postmark instances are allowed to run, disk usage seems to climb > :indefinitely (at 40GB it was still climbing), until eventually the machine > :silently reboots. > : > : debug.max_softdeps is by default set to 523,712 (1 GB of RAM). Is that > :a resonable value? I see some tests in the docs with max_softdeps set to > :4000 or so. > : > : > :Tom > > > Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 30 12:35: 2 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 06AA6152B5; Thu, 30 Dec 1999 12:34:58 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id MAA01353; Thu, 30 Dec 1999 12:38:50 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912302038.MAA01353@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: tsikora@powerusersbbs.com Cc: Marc Nicholas , "freebsd-hackers@FreeBSD.ORG" , "freebsd-stable@FreeBSD.ORG" Subject: Re: Temperature In-reply-to: Your message of "Wed, 29 Dec 1999 23:07:07 EST." <386ADA6B.5D0CEAB2@home.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 30 Dec 1999 12:38:50 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Marc Nicholas wrote: > > > > You're referring to the temps reported via an LM78 or similar, yes? > The machines bios with Winbond W83782d IC > > > not reporting that the machine is actually getting HOTTER under FreeBSD? > > It is HOTTER under FreeBSD. Immediatelly upon boot-up it's 26F > hotter under FreeBSD than under Linux. That's fairly hard to believe, unless your system has zero thermal inertia. I'd have an easier time suggesting that your reporting software has been broken. I'm also curious as to how you're talking to the BIOS to obtain these temperature values. > Sometime after 3.4-RC and > now this started. (I follow the stable branch via CVSup) Under > 3.3-STABLE the temerature was always the same as Linux...cool averaging > 89F for the CPU's. Now it's over 113F under FreeBSD only. I know it's > wierd but the machine does not lie. Under Linux it's the same as before > 87-89F. You can't claim "the machine does not lie" without substantiating evidence. I'd want an external thermometer at the very least. However, since you're the only one reporting this, you could do us all a great service by taking a few minutes off to perform a binary search to narrow down the date at which this purported change might have occurred. You can trivially easily check out kernels and build them to see what effect running them has on your operating temperature. You haven't by some chance just recently started running eg. the SETI @home client, or one of the distributed.net clients by any chance? -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 30 12:57:56 1999 Delivered-To: freebsd-stable@freebsd.org Received: from gemini.inside.pathcom.com (chihuahua.pathcom.com [209.250.128.11]) by hub.freebsd.org (Postfix) with ESMTP id 676DE15212 for ; Thu, 30 Dec 1999 12:57:40 -0800 (PST) (envelope-from drkangel@gemini.inside.pathcom.com) Received: from localhost (drkangel@localhost) by gemini.inside.pathcom.com (8.9.1/8.9.1) with ESMTP id PAA20813 for ; Thu, 30 Dec 1999 15:57:43 -0500 Date: Thu, 30 Dec 1999 15:57:43 -0500 (EST) From: Marco Paulo Rodrigues To: stable@freebsd.org Subject: PPPOED 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 Does anyone know the reason for the pppoed daemon? I've read all the man files and the ones related to it and I can't seem to get it to work. I can get pppoe to work fine with ppp and I have a life connection. Anyways my problem is when I enable pppoed in the rc.conf file then when I boot I don't get an error message, but I notice it shows the pppoed command and the sytnax as if I typed an invalid switch. Anyone with any ideas? Marco Paulo Rodrigues Junior Unix Systems Operator Pathway Communications email: marco.rodrigues@pathcom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 30 12:58:47 1999 Delivered-To: freebsd-stable@freebsd.org Received: from gemini.inside.pathcom.com (chihuahua.pathcom.com [209.250.128.11]) by hub.freebsd.org (Postfix) with ESMTP id 9B3321540A for ; Thu, 30 Dec 1999 12:58:42 -0800 (PST) (envelope-from drkangel@gemini.inside.pathcom.com) Received: from localhost (drkangel@localhost) by gemini.inside.pathcom.com (8.9.1/8.9.1) with ESMTP id PAA20817 for ; Thu, 30 Dec 1999 15:58:54 -0500 Date: Thu, 30 Dec 1999 15:58:54 -0500 (EST) From: Marco Paulo Rodrigues To: freebsd-stable@freebsd.org Subject: PPPOED in rc.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 Does anyone know the reason for the pppoed daemon? I've read all the man files and the ones related to it and I can't seem to get it to work. I can get pppoe to work fine with ppp and I have a life connection. Anyways my problem is when I enable pppoed in the rc.conf file then when I boot I don't get an error message, but I notice it shows the pppoed command and the sytnax as if I typed an invalid switch. Anyone with any ideas? Marco Paulo Rodrigues Junior Unix Systems Operator Pathway Communications email: marco.rodrigues@pathcom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 30 13:18:53 1999 Delivered-To: freebsd-stable@freebsd.org Received: from florence.pavilion.net (florence.pavilion.net [212.74.0.25]) by hub.freebsd.org (Postfix) with ESMTP id 9752A152B5 for ; Thu, 30 Dec 1999 13:18:47 -0800 (PST) (envelope-from joe@florence.pavilion.net) Received: (from joe@localhost) by florence.pavilion.net (8.9.3/8.8.8) id VAA39375; Thu, 30 Dec 1999 21:18:39 GMT (envelope-from joe) Date: Thu, 30 Dec 1999 21:18:39 +0000 From: Josef Karthauser To: Marco Paulo Rodrigues Cc: freebsd-stable@FreeBSD.ORG Subject: Re: PPPOED in rc.conf Message-ID: <19991230211839.D35536@florence.pavilion.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: X-NCC-RegID: uk.pavilion Organisation: Pavilion Internet plc, Lees House, 21-23 Dyke Road, Brighton, England Phone: +44-845-333-5000 Fax: +44-845-333-5001 Mobile: +44-403-596893 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Dec 30, 1999 at 03:58:54PM -0500, Marco Paulo Rodrigues wrote: > Does anyone know the reason for the pppoed daemon? I've read all > the man files and the ones related to it and I can't seem to get it to > work. I can get pppoe to work fine with ppp and I have a life connection. > Anyways my problem is when I enable pppoed in the rc.conf file then when I > boot I don't get an error message, but I notice it shows the pppoed > command and the sytnax as if I typed an invalid switch. Anyone with any > ideas? Yes, if you want to run a server that other people can connect to using pppoe you need to run pppoed. If you're connecting to someone elses server (your ISPs, etc) then you don't need to play with pppoed. Joe -- Josef Karthauser FreeBSD: Take the red pill and we'll show you just how Technical Manager deep the rabbit hole goes. (http://www.uk.freebsd.org) Pavilion Internet plc. [joe@pavilion.net, joe@freebsd.org, joe@tao.org.uk] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 30 13:31:14 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.rdc1.ct.home.com (ha1.rdc1.ct.home.com [24.2.0.66]) by hub.freebsd.org (Postfix) with ESMTP id 21E2E1541E; Thu, 30 Dec 1999 13:31:06 -0800 (PST) (envelope-from tsikora@home.com) Received: from home.com ([24.2.168.186]) by mail.rdc1.ct.home.com (InterMail v4.01.01.07 201-229-111-110) with ESMTP id <19991230213059.NUJZ9446.mail.rdc1.ct.home.com@home.com>; Thu, 30 Dec 1999 13:30:59 -0800 Message-ID: <386BCF19.F259CD1B@home.com> Date: Thu, 30 Dec 1999 16:31:05 -0500 From: Ted Sikora Reply-To: tsikora@powerusersbbs.com Organization: Jtl Development X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.4-STABLE i386) X-Accept-Language: en-US,en-GB MIME-Version: 1.0 To: Mike Smith Cc: tsikora@powerusersbbs.com, Marc Nicholas , "freebsd-hackers@FreeBSD.ORG" , "freebsd-stable@FreeBSD.ORG" Subject: Re: Temperature References: <199912302038.MAA01353@mass.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > > > Marc Nicholas wrote: > > > > > > You're referring to the temps reported via an LM78 or similar, yes? > > The machines bios with Winbond W83782d IC > > > > > not reporting that the machine is actually getting HOTTER under FreeBSD? > > > > It is HOTTER under FreeBSD. Immediatelly upon boot-up it's 26F > > hotter under FreeBSD than under Linux. > > That's fairly hard to believe, unless your system has zero thermal > inertia. I'd have an easier time suggesting that your reporting software > has been broken. I'm also curious as to how you're talking to the BIOS > to obtain these temperature values. > I'm really starting to get irritaed with all these posts. I'm trying to report a potential problem and your treating me like I'm some yokel. I have been a computer engineer for 28 years so I think I have a little experience in this. Well here's some data: FreeBSD 3.3-RELEASE #0: Thu Sep 16 23:40:35 GMT 1999 jkh@highwing.cdrom.com:/usr/src/sys/compile/GENERIC (lmmon -i reports) Motherboard Temp Voltages 32C / 89F / 305K Vcore1: +2.016V Vcore2: +1.469V Fan Speeds + 3.3V: +3.234V + 5.0V: +4.932V 1: 0 rpm +12.0V: +12.625V 2: 0 rpm -12.0V: -2.438V 3: 0 rpm - 5.0V: -1.383V System Winbond chip in system bios reports: 87F CPU#0 87F CPU#1 89F CASE TEMP ------------------------------------------------------------- FreeBSD 3.4-STABLE #0: Tue Dec 28 19:28:10 EST 1999 root@telecast.htfds1.ct.home.com:/usr/src/sys/compile/TELECAST (lmmon -i reports) Motherboard Temp Voltages 41C / 105F / 314K Vcore1: +2.016V Vcore2: +1.484V Fan Speeds + 3.3V: +3.250V + 5.0V: +4.932V 1: 0 rpm +12.0V: +12.625V 2: 0 rpm -12.0V: -2.375V 3: 0 rpm - 5.0V: -1.383V System Winbond chip in system bios reports: 113F CPU#0 113F CPU#1 105F CASE TEMP These are both taken right after bootup with X started and WindowMaker running. No other apps running. Regards, -- Ted Sikora Jtl Development Group tsikora@powerusersbbs.com http://powerusersbbs.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 30 14: 5:56 1999 Delivered-To: freebsd-stable@freebsd.org Received: from marcy.nas.nasa.gov (marcy.nas.nasa.gov [129.99.113.17]) by hub.freebsd.org (Postfix) with ESMTP id 10A1B154D7; Thu, 30 Dec 1999 14:05:50 -0800 (PST) (envelope-from wrstuden@marcy.nas.nasa.gov) Received: from localhost (wrstuden@localhost) by marcy.nas.nasa.gov (8.9.3/NAS8.8.7n) with SMTP id OAA16103; Thu, 30 Dec 1999 14:05:07 -0800 (PST) Date: Thu, 30 Dec 1999 14:05:07 -0800 (PST) From: Bill Studenmund To: tsikora@powerusersbbs.com Cc: Marc Nicholas , "freebsd-hackers@FreeBSD.ORG" , "freebsd-stable@FreeBSD.ORG" Subject: Re: Temperature In-Reply-To: <386ADA6B.5D0CEAB2@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 Wed, 29 Dec 1999, Ted Sikora wrote: > It is HOTTER under FreeBSD. Immediatelly upon boot-up it's 26F > hotter under FreeBSD than under Linux. Sometime after 3.4-RC and > now this started. (I follow the stable branch via CVSup) Under > 3.3-STABLE the temerature was always the same as Linux...cool averaging > 89F for the CPU's. Now it's over 113F under FreeBSD only. I know it's > wierd but the machine does not lie. Under Linux it's the same as before > 87-89F. The big question of course is are you sure the machine's not lying? I agree with you that i't unlikely that it's a fundamental hardware problem (like you're getting no air flow) if Linux still reports sane temperatures. But it seems quite reasonable that somehow temperture reading broke for your hardware when you upgraded. Two easy ways to settle the issue would be either to get a thermocouple thermometer, put the thermocouple in the case, and see exactly what happens with the case temperature. Another easy way to settle it is to get the voltages being returned for the temperature sensors as opposed to the reported temperature. If the voltages are the same under the two OS's, then it's definitly a reporting error. :-) Take care, Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 30 14: 7: 9 1999 Delivered-To: freebsd-stable@freebsd.org Received: from smtp5.jps.net (smtp5.jps.net [209.63.224.55]) by hub.freebsd.org (Postfix) with ESMTP id 61E5A1525D; Thu, 30 Dec 1999 14:06:52 -0800 (PST) (envelope-from onemo@jps.net) Received: from jps.net (216-224-148-40.stk.jps.net [216.224.148.40]) by smtp5.jps.net (8.9.3/8.9.0) with ESMTP id OAA16548; Thu, 30 Dec 1999 14:06:26 -0800 (PST) Message-ID: <386BD5E2.F341E560@jps.net> Date: Thu, 30 Dec 1999 14:00:03 -0800 From: Michael Oski X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: tsikora@powerusersbbs.com Cc: "freebsd-hackers@FreeBSD.ORG" , "freebsd-stable@FreeBSD.ORG" Subject: Re: Temperature References: <199912302038.MAA01353@mass.cdrom.com> <386BCF19.F259CD1B@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 Ted Sikora wrote: > I'm really starting to get irritaed with all these posts. I'm trying to > report a potential problem and your treating me like I'm some yokel. I > have been a computer engineer for 28 years so I think I have a little > experience in this. Well here's some data: OK, I'll admit I'm merely an observer in all this, but I'd like to say that I too am starting to get irritated with this. To be honest, your apparent irritation, along with the point about not being 'some yokel' has finally nudged me into replying. I would have to say that the vast majority of posts regarding your problem report were targetted at identifying whether the system 'was HOTTER' or 'was SAYING it was hotter'. When this was first pointed out to you, your reply was 'picky, it SAYS it's hotter'. This is not a matter of being picky - this is a crucial factor in determining what the source of this problem is. I can say with most certainty, that I would have had far fewer messages in my inbox had you acurately described the problem. So, you see, it is YOU that is the cause of this irritation. I would think that a professional such as yourself, with 28 years of experience, would understand this and make every effort to post clear and concise reports. Please don't flame the developers of FreeBSD for taking so long to determine what it is you are reporting, when it was up to you to specify this originally. My last $0.02 from the 20th Century. Michael. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 30 14:11:48 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 3B4C4153A9; Thu, 30 Dec 1999 14:11:39 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id OAA02713; Thu, 30 Dec 1999 14:15:25 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912302215.OAA02713@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: tsikora@powerusersbbs.com Cc: Marc Nicholas , "freebsd-hackers@FreeBSD.ORG" , "freebsd-stable@FreeBSD.ORG" Subject: Re: Temperature In-reply-to: Your message of "Thu, 30 Dec 1999 16:31:05 EST." <386BCF19.F259CD1B@home.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 30 Dec 1999 14:15:25 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > not reporting that the machine is actually getting HOTTER under FreeBSD? > > > > > > It is HOTTER under FreeBSD. Immediatelly upon boot-up it's 26F > > > hotter under FreeBSD than under Linux. > > > > That's fairly hard to believe, unless your system has zero thermal > > inertia. I'd have an easier time suggesting that your reporting software > > has been broken. I'm also curious as to how you're talking to the BIOS > > to obtain these temperature values. > > > I'm really starting to get irritaed with all these posts. I'm trying to > report a potential problem and your treating me like I'm some yokel. I > have been a computer engineer for 28 years so I think I have a little > experience in this. Since we also have some experience in this, you might want to take our responses to indicate that your thinking may be in error. I'm certainly not trying to treat you like a yokel. I'm trying to get you to think and behave like a computer engineer with nearly 30 years of experience. So far this hasn't been very successful. > Well here's some data: > > FreeBSD 3.3-RELEASE #0: Thu Sep 16 23:40:35 GMT 1999 > jkh@highwing.cdrom.com:/usr/src/sys/compile/GENERIC > > (lmmon -i reports) > > Motherboard Temp Voltages > > 32C / 89F / 305K Vcore1: +2.016V ... > 41C / 105F / 314K Vcore1: +2.016V Is this the same lmmon binary in both cases? Have you confirmed these temperatures with an external thermometer? > These are both taken right after bootup with X started and WindowMaker > running. No other apps running. The first step in resolving this has simply been to try to narrow down the variables so that we have some idea what might actually be involved here. It's been a painful process, but we're almost there. Once you can confirm that the onboard temperature sensors are working and bear a good resemblance to reality we can eliminate them from the equation. I did ask for verification of this (which hasn't been forthcoming yet). I've also asked you to undertake the second phase, which is to perform a binary-search set of kernel builds to pin down the timeframe in which this change occurred. It's also been suggested that the scheduler changes made by Bruce Evans may have impacted your system; you might want to bracket those changes to quickly eliminate them as possibilities. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 30 14:48:14 1999 Delivered-To: freebsd-stable@freebsd.org Received: from inbox.org (inbox.org [216.22.145.8]) by hub.freebsd.org (Postfix) with ESMTP id 7978514E81 for ; Thu, 30 Dec 1999 14:48:09 -0800 (PST) (envelope-from bsd@inbox.org) Received: from localhost (bsd@localhost) by inbox.org (8.9.3/8.9.3) with SMTP id RAA18064 for ; Thu, 30 Dec 1999 17:48:14 -0500 (EST) Date: Thu, 30 Dec 1999 17:48:14 -0500 (EST) From: "Mr. K." To: stable@freebsd.org Subject: Panic: Out of mbuf clusters 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 OK, so I raised NMBCLUSTERS to 4096, and installed a second freebsd-stable box also with NMBCLUSTERS at 4096, and I managed to have them both panic at the same time (unfortunately, only one of them gave me a crash dump). But anyway, here is the stack trace, hopefully someone can tell me if this is the same as the known problem, and whether 4.0 would fix it. euclid# cd /var/crash euclid# ls bounds kernel.0 minfree vmcore.0 euclid# gdb -k kernel.0 vmcore.0 GNU gdb 4.18 Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-unknown-freebsd"... IdlePTD 2392064 initial pcb at 1e64a4 panicstr: Out of mbuf clusters panic messages: --- panic: Ouxl0: no memory for rx list -- packet dropped! t of mbuf clusters syncing disks... done xl0: no memory for rx list -- packet dropped! xl0: no memory for rx list -- packet dropped! xl0: no memory for rx list -- packet dropped! xl0: no memory for rx list -- packet dropped! xl0: no memory for rx list -- packet dropped! xl0: no memory for rx list -- packet dropped! xl0: no memory for rx list -- packet dropped! xl0: no memory for rx list -- packet dropped! xl0: no memory for rx list -- packet dropped! xl0: no memory for rx list -- packet dropped! xl0: no memory for rx list -- packet dropped! xl0: no memory for rx list -- packet dropped! xl0: no memory for rx list -- packet dropped! xl0: no memory for rx list -- packet dropped! xl0: no memory for rx list -- packet dropped! xl0: no memory for rx list -- packet dropped! xl0: no memory for rx list -- packet dropped! xl0: no memory for rx list -- packet dropped! xl0: no memory for rx list -- packet dropped! xl0: no memory for rx list -- packet dropped! xl0: no memory for rx list -- packet dropped! xl0: no memory for rx list -- packet dropped! xl0: no memory for rx list -- packet dropped! xl0: no memory for rx list -- packet dropped! xl0: no memory for rx list -- packet dropped! xl0: no memory for rx list -- packet dropped! xl0: no memory for rx list -- packet dropped! xl0: no memory for rx list -- packet dropped! xl0: no memory for rx list -- packet dropped! xl0: no memory for rx list -- packet dropped! xl0: no memory for rx list -- packet dropped! xl0: no memory for rx list -- packet dropped! xl0: no memory for rx list -- packet dropped! xl0: no memory for rx list -- packet dropped! xl0: no memory for rx list -- packet dropped! xl0: no memory for rx list -- packet dropped! xl0: no memory for rx list -- packet dropped! dumping to dev 1, offset 417552 dump 95 94 93 92 91 90 89 88 87 86 85 84 83 82 81 80 79 78 77 76 75 74 73 72 71 70 69 68 67 66 65 64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 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 --- #0 0xc01253bb in boot () (kgdb) where #0 0xc01253bb in boot () #1 0xc0125640 in at_shutdown () #2 0xc013b5ca in m_retryhdr () #3 0xc013d283 in sosend () #4 0xc01333e8 in soo_write () #5 0xc0130332 in dofilewrite () #6 0xc013023b in write () #7 0xc01ac6a7 in syscall () #8 0xc019fdcc in Xint0x80_syscall () #9 0x8048983 in ?? () #10 0x8048679 in ?? () (kgdb) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 30 14:48:22 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.rdc1.ct.home.com (ha1.rdc1.ct.home.com [24.2.0.66]) by hub.freebsd.org (Postfix) with ESMTP id 8AA3914E81; Thu, 30 Dec 1999 14:48:19 -0800 (PST) (envelope-from tsikora@home.com) Received: from home.com ([24.2.168.186]) by mail.rdc1.ct.home.com (InterMail v4.01.01.07 201-229-111-110) with ESMTP id <19991230224818.OPRX9446.mail.rdc1.ct.home.com@home.com>; Thu, 30 Dec 1999 14:48:18 -0800 Message-ID: <386BE138.E85A3DCB@home.com> Date: Thu, 30 Dec 1999 17:48:24 -0500 From: Ted Sikora Reply-To: tsikora@powerusersbbs.com Organization: Jtl Development X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.4-STABLE i386) X-Accept-Language: en-US,en-GB MIME-Version: 1.0 To: Mike Smith , "freebsd-stable@FreeBSD.ORG" Subject: Re: Temperature References: <199912302215.OAA02713@mass.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > > > > > > not reporting that the machine is actually getting HOTTER under FreeBSD? > > > > > > > > It is HOTTER under FreeBSD. Immediatelly upon boot-up it's 26F > > > > hotter under FreeBSD than under Linux. > > > > > > That's fairly hard to believe, unless your system has zero thermal > > > inertia. I'd have an easier time suggesting that your reporting software > > > has been broken. I'm also curious as to how you're talking to the BIOS > > > to obtain these temperature values. > > > > > I'm really starting to get irritaed with all these posts. I'm trying to > > report a potential problem and your treating me like I'm some yokel. I > > have been a computer engineer for 28 years so I think I have a little > > experience in this. > > Since we also have some experience in this, you might want to take our > responses to indicate that your thinking may be in error. > > I'm certainly not trying to treat you like a yokel. I'm trying to get > you to think and behave like a computer engineer with nearly 30 years of > experience. So far this hasn't been very successful. I know I apologize again. I did not think this post would generate so much feedback. Well I built another kernel without SMP and the temp dropped so I am beginning to see this may be SMP related possibly. Later tonight I am going to attach a mechanical gauge to the CPU's to verify the temperatures. I failed to mention we have another (identical) board and it reports the same thing so until I verify the temp the only other possibility is a bug in the temp IC *but* the bios reports the same thing as lmmon so that is doubtful. > -- Ted Sikora Jtl Development Group tsikora@powerusersbbs.com http://powerusersbbs.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 30 14:57:13 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail2.uniserve.com (mail2.uniserve.com [204.244.156.7]) by hub.freebsd.org (Postfix) with ESMTP id 82DD915480 for ; Thu, 30 Dec 1999 14:57:11 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca ([204.244.186.218]) by mail2.uniserve.com with smtp (Exim 3.03 #4) id 123oVJ-0009Jr-00; Thu, 30 Dec 1999 14:57:09 -0800 Date: Thu, 30 Dec 1999 14:57:05 -0800 (PST) From: Tom X-Sender: tom@shell.uniserve.ca To: "Mr. K." Cc: stable@freebsd.org Subject: Re: Panic: Out of mbuf clusters In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 30 Dec 1999, Mr. K. wrote: > OK, so I raised NMBCLUSTERS to 4096, and installed a second freebsd-stable > box also with NMBCLUSTERS at 4096, and I managed to have them both panic > at the same time (unfortunately, only one of them gave me a crash dump). > But anyway, here is the stack trace, hopefully someone can tell me if this > is the same as the known problem, and whether 4.0 would fix it. 4096 isn't very many. Set it to 6000 or so. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 30 15:28:10 1999 Delivered-To: freebsd-stable@freebsd.org Received: from inbox.org (inbox.org [216.22.145.8]) by hub.freebsd.org (Postfix) with ESMTP id 16F7115351 for ; Thu, 30 Dec 1999 15:28:08 -0800 (PST) (envelope-from bsd@inbox.org) Received: from localhost (bsd@localhost) by inbox.org (8.9.3/8.9.3) with SMTP id SAA19642; Thu, 30 Dec 1999 18:28:11 -0500 (EST) Date: Thu, 30 Dec 1999 18:28:11 -0500 (EST) From: "Mr. K." To: Tom Cc: stable@freebsd.org Subject: Re: Panic: Out of mbuf clusters In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 30 Dec 1999, Tom wrote: > On Thu, 30 Dec 1999, Mr. K. wrote: > > > OK, so I raised NMBCLUSTERS to 4096, and installed a second freebsd-stable > > box also with NMBCLUSTERS at 4096, and I managed to have them both panic > > at the same time (unfortunately, only one of them gave me a crash dump). > > But anyway, here is the stack trace, hopefully someone can tell me if this > > is the same as the known problem, and whether 4.0 would fix it. > > 4096 isn't very many. Set it to 6000 or so. > > Tom > > I just did, and it just happened again. The really odd thing is it manages to panic both freebsd boxes (client and server) simultaneously. Hopefully I got both dumps working this time. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 30 16: 0:54 1999 Delivered-To: freebsd-stable@freebsd.org Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (Postfix) with ESMTP id 251DE15310 for ; Thu, 30 Dec 1999 16:00:51 -0800 (PST) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.8.8/8.8.8) id BAA28584 for freebsd-stable@FreeBSD.ORG; Fri, 31 Dec 1999 01:00:49 +0100 (CET) (envelope-from olli) Date: Fri, 31 Dec 1999 01:00:49 +0100 (CET) From: Oliver Fromme Message-Id: <199912310000.BAA28584@dorifer.heim3.tu-clausthal.de> To: freebsd-stable@FreeBSD.ORG Subject: Re: Panic: Out of mbuf clusters Organization: Administration TU Clausthal Reply-To: freebsd-stable@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: TIN [version 1.2 RZTUC(3) PL2] Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mr. K. wrote in list.freebsd-stable: > OK, so I raised NMBCLUSTERS to 4096, and installed a second freebsd-stable > box also with NMBCLUSTERS at 4096, and I managed to have them both panic 4096 isn't that much. On our web proxy I had to raise it to 10240 (and that box doesn't get that much traffic either). I'd recommend that you use the ``netstat -m'' command to watch your mbuf cluster usage. It will print something like this: 584/4288 mbufs in use: 365 mbufs allocated to data 219 mbufs allocated to packet headers 299/3626/10240 mbuf clusters in use (current/peak/max) 7788 Kbytes allocated to network (8% in use) 366 requests for memory denied 0 requests for memory delayed 0 calls to protocol drain routines The important thing is the 4th line. It displays three values x/y/z. ``x'' is the current number of mbuf clusters in use (pretty low in the above example... well, it's night here, and holidays). ``y'' is the peak value, i.e. the largest number that has been in use at a time since reboot. ``z'' is the hard limit value that you specify in your kernel config file using the NMBCLUSTERS option. If your ``y'' ever reaches (or comes even close to) the ``z'' value during times of high network load, you _must_ increase your NMBCLUSTERS value. In the above example, the maximum use since reboot (which was 69 days ago) is 3626 out of 10240 (i.e. ~ 36%), which is OK. A sidenote: If you experience high mbuf usage without actually servicing many requests, it _might_ be an indication of a denial-of-service attack that someone is running against your machine. Might be something worth investigating. Finally, the fact that FreeBSD 3.x panics when it runs out of mbuf clusters is a well-known problem. The solution is to not let it run out of mbuf clusters by configuring a sufficient number for them. This should be in the Handbook or in the FAQ. Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 30 16: 7: 9 1999 Delivered-To: freebsd-stable@freebsd.org Received: from oracle.dsuper.net (oracle.dsuper.net [205.205.255.1]) by hub.freebsd.org (Postfix) with ESMTP id D5B5A1503D for ; Thu, 30 Dec 1999 16:07:02 -0800 (PST) (envelope-from bmilekic@dsuper.net) Received: from oracle.dsuper.net (oracle.dsuper.net [205.205.255.1]) by oracle.dsuper.net (8.9.3/8.9.3) with ESMTP id TAA11856; Thu, 30 Dec 1999 19:06:51 -0500 (EST) Date: Thu, 30 Dec 1999 19:06:50 -0500 (EST) From: Bosko Milekic To: "Mr. K." Cc: stable@FreeBSD.ORG Subject: Re: Panic: Out of mbuf clusters In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 30 Dec 1999, Mr. K. wrote: !>OK, so I raised NMBCLUSTERS to 4096, and installed a second freebsd-stable !>box also with NMBCLUSTERS at 4096, and I managed to have them both panic !>at the same time (unfortunately, only one of them gave me a crash dump). !>But anyway, here is the stack trace, hopefully someone can tell me if this !>is the same as the known problem, and whether 4.0 would fix it. !> !>euclid# cd /var/crash !>euclid# ls !>bounds kernel.0 minfree vmcore.0 !>euclid# gdb -k kernel.0 vmcore.0 !>GNU gdb 4.18 !>Copyright 1998 Free Software Foundation, Inc. !>GDB is free software, covered by the GNU General Public License, and you !>are !>welcome to change it and/or distribute copies of it under certain !>conditions. !>Type "show copying" to see the conditions. !>There is absolutely no warranty for GDB. Type "show warranty" for !>details. !>This GDB was configured as "i386-unknown-freebsd"... !>IdlePTD 2392064 !>initial pcb at 1e64a4 !>panicstr: Out of mbuf clusters !>panic messages: !>--- !>panic: Ouxl0: no memory for rx list -- packet dropped! !>t of mbuf clusters !> [snip] !>--- !>#0 0xc01253bb in boot () !>(kgdb) where !>#0 0xc01253bb in boot () !>#1 0xc0125640 in at_shutdown () !>#2 0xc013b5ca in m_retryhdr () !>#3 0xc013d283 in sosend () !>#4 0xc01333e8 in soo_write () !>#5 0xc0130332 in dofilewrite () !>#6 0xc013023b in write () !>#7 0xc01ac6a7 in syscall () !>#8 0xc019fdcc in Xint0x80_syscall () !>#9 0x8048983 in ?? () !>#10 0x8048679 in ?? () !>(kgdb) Well, now. We can see that the actual panic occurs during a send() syscall (and not as a result of anything in the driver). Since sosend() calls the allocation routines with M_WAIT, this confirms the origin of the panic. At the same time, you can observe that the `xl' driver is properly dropping packets when it runs out of memory. The panic problem is solved in -CURRENT. However, if you ever see such messages as "no memory for [...]" and it's coming from the `xl' driver, that's a good indication -- assuming that this occurs often -- that you should higher NMBCLUSTERS. Bosko. -- Bosko Milekic Email: bmilekic@dsuper.net WWW: http://pages.infinit.net/bmilekic/ -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 30 16:20:38 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.rdc1.ct.home.com (ha1.rdc1.ct.home.com [24.2.0.66]) by hub.freebsd.org (Postfix) with ESMTP id 61AEE14D6E for ; Thu, 30 Dec 1999 16:20:34 -0800 (PST) (envelope-from tsikora@home.com) Received: from home.com ([24.2.168.186]) by mail.rdc1.ct.home.com (InterMail v4.01.01.07 201-229-111-110) with ESMTP id <19991231002020.PJXF9446.mail.rdc1.ct.home.com@home.com> for ; Thu, 30 Dec 1999 16:20:20 -0800 Message-ID: <386BF6CA.EA00DF5C@home.com> Date: Thu, 30 Dec 1999 19:20:26 -0500 From: Ted Sikora Reply-To: tsikora@powerusersbbs.com Organization: Jtl Development X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.4-STABLE i386) X-Accept-Language: en-US,en-GB MIME-Version: 1.0 To: "freebsd-stable@FreeBSD.ORG" Subject: Temperature Findings References: <199912302215.OAA02713@mass.cdrom.com> <386BE138.E85A3DCB@home.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I had one my technicians set up a scope to test the voltage readings and a Cooper temperature gauge to check the case temp. We decided to abandon the CPU test since we had no accurate way to attach the gauge. Our findings: The voltage readings by the winbond IC in the bios are accurate. The case temperature was 5F cooler than reported. So I would conclude the readings from the bios are a fairly accurate representation of the machines current condition. Things I failed to mention. The CPU's were overclocked by 100MHz Core CPU Voltage was raised a 1/2 step to 2.05V o This still does not explain the differences between Linux and FreeBSD. o The standard 3.3-RELEASE UniProcessor kernel runs identical to Linux. o FreeBSD SMP kernels immediately run hotter than the standard kernel. I put Core voltage back to normal and set the CPU's to standard settings. The result was much better but it still runs about 14 degrees hotter.(acceptable) 26 degrees was not. Has anyone else checked this. Just checking the Generic versus a SMP kernel you should see this. Regards, -- Ted Sikora Jtl Development Group tsikora@powerusersbbs.com http://powerusersbbs.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 30 16:27:38 1999 Delivered-To: freebsd-stable@freebsd.org Received: from shell.webmaster.com (mail.webmaster.com [209.133.28.73]) by hub.freebsd.org (Postfix) with ESMTP id 5021E15244 for ; Thu, 30 Dec 1999 16:27:36 -0800 (PST) (envelope-from davids@webmaster.com) Received: from whenever ([209.133.29.2]) by shell.webmaster.com (Post.Office MTA v3.5.3 release 223 ID# 0-12345L500S10000V35) with SMTP id com; Thu, 30 Dec 1999 16:27:34 -0800 From: "David Schwartz" To: , Subject: RE: Temperature Findings Date: Thu, 30 Dec 1999 16:27:34 -0800 Message-ID: <000001bf5325$d5335630$021d85d1@youwant.to> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0 In-reply-to: <386BF6CA.EA00DF5C@home.com> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It's really simple, your machine was configured beyond recommended settings and as a result was unable to run at full speed for long periods of time. Returning the machine to recommended settings solved the problem. Case closed. Your machine was a ticking time bomb for any OS. DS > I had one my technicians set up a scope to test the voltage readings and > a Cooper temperature gauge to check the case temp. We decided to abandon > the CPU test since we had no accurate way to attach the gauge. Our > findings: > The voltage readings by the winbond IC in the bios are accurate. > The case temperature was 5F cooler than reported. > So I would conclude the readings from the bios are a fairly accurate > representation of the machines current condition. > > Things I failed to mention. > The CPU's were overclocked by 100MHz > Core CPU Voltage was raised a 1/2 step to 2.05V > > o This still does not explain the differences between Linux > and FreeBSD. > o The standard 3.3-RELEASE UniProcessor kernel runs identical to > Linux. > o FreeBSD SMP kernels immediately run hotter than the standard > kernel. > > I put Core voltage back to normal and set the CPU's to standard > settings. The result was much better but it still runs about 14 degrees > hotter.(acceptable) 26 degrees was not. > > Has anyone else checked this. Just checking the Generic versus a SMP > kernel you should see this. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 30 16:31:57 1999 Delivered-To: freebsd-stable@freebsd.org Received: from rs.ksl.co.il (rs.ksl.co.il [199.203.44.20]) by hub.freebsd.org (Postfix) with ESMTP id CDD4D14EBD for ; Thu, 30 Dec 1999 16:31:50 -0800 (PST) (envelope-from roman@xpert.com) Received: from localhost (roman@localhost) by rs.ksl.co.il (8.9.3/8.9.3) with ESMTP id CAA85229; Fri, 31 Dec 1999 02:35:33 +0200 (IST) X-Authentication-Warning: rs.ksl.co.il: roman owned process doing -bs Date: Fri, 31 Dec 1999 02:35:33 +0200 (IST) From: Roman Shterenzon To: Bosko Milekic Cc: "Mr. K." , stable@FreeBSD.ORG Subject: Re: Panic: Out of mbuf clusters In-Reply-To: Message-ID: Organization: Xpert UNIX Systems Ltd. MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Good day, That's very scary, that means that a individual or group of individuals having a decent intenet link could bring a FreeBSD-stable machine to it's knees. Please correct me if I'm wrong. Is there nmbcluster number which cannot be exploited using current (I don't mean freebsd-current :) technology? On Thu, 30 Dec 1999, Bosko Milekic wrote: > > On Thu, 30 Dec 1999, Mr. K. wrote: > > !>OK, so I raised NMBCLUSTERS to 4096, and installed a second freebsd-stable > !>box also with NMBCLUSTERS at 4096, and I managed to have them both panic > !>at the same time (unfortunately, only one of them gave me a crash dump). > !>But anyway, here is the stack trace, hopefully someone can tell me if this > !>is the same as the known problem, and whether 4.0 would fix it. > !> > !>euclid# cd /var/crash > !>euclid# ls > !>bounds kernel.0 minfree vmcore.0 > !>euclid# gdb -k kernel.0 vmcore.0 > !>GNU gdb 4.18 > !>Copyright 1998 Free Software Foundation, Inc. > !>GDB is free software, covered by the GNU General Public License, and you > !>are > !>welcome to change it and/or distribute copies of it under certain > !>conditions. > !>Type "show copying" to see the conditions. > !>There is absolutely no warranty for GDB. Type "show warranty" for > !>details. > !>This GDB was configured as "i386-unknown-freebsd"... > !>IdlePTD 2392064 > !>initial pcb at 1e64a4 > !>panicstr: Out of mbuf clusters > !>panic messages: > !>--- > !>panic: Ouxl0: no memory for rx list -- packet dropped! > !>t of mbuf clusters > !> > > [snip] > > !>--- > !>#0 0xc01253bb in boot () > !>(kgdb) where > !>#0 0xc01253bb in boot () > !>#1 0xc0125640 in at_shutdown () > !>#2 0xc013b5ca in m_retryhdr () > !>#3 0xc013d283 in sosend () > !>#4 0xc01333e8 in soo_write () > !>#5 0xc0130332 in dofilewrite () > !>#6 0xc013023b in write () > !>#7 0xc01ac6a7 in syscall () > !>#8 0xc019fdcc in Xint0x80_syscall () > !>#9 0x8048983 in ?? () > !>#10 0x8048679 in ?? () > !>(kgdb) > > > Well, now. We can see that the actual panic occurs during a send() > syscall (and not as a result of anything in the driver). Since sosend() > calls the allocation routines with M_WAIT, this confirms the origin of > the panic. > At the same time, you can observe that the `xl' driver is > properly dropping packets when it runs out of memory. The panic problem > is solved in -CURRENT. However, if you ever see such messages as "no > memory for [...]" and it's coming from the `xl' driver, that's a good > indication -- assuming that this occurs often -- that you should higher > NMBCLUSTERS. > > Bosko. > > -- > Bosko Milekic > Email: bmilekic@dsuper.net > WWW: http://pages.infinit.net/bmilekic/ > -- > > > > > 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 Thu Dec 30 16:37:26 1999 Delivered-To: freebsd-stable@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 8896614BE1; Thu, 30 Dec 1999 16:37:21 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 71BAE1CA0; Fri, 31 Dec 1999 08:37:18 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: tsikora@powerusersbbs.com Cc: Mike Smith , Marc Nicholas , "freebsd-hackers@FreeBSD.ORG" , "freebsd-stable@FreeBSD.ORG" Subject: Re: Temperature In-Reply-To: Message from Ted Sikora of "Thu, 30 Dec 1999 16:31:05 EST." <386BCF19.F259CD1B@home.com> Date: Fri, 31 Dec 1999 08:37:18 +0800 From: Peter Wemm Message-Id: <19991231003718.71BAE1CA0@overcee.netplex.com.au> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ted Sikora wrote: > These are both taken right after bootup with X started and WindowMaker > running. No other apps running. Can you please include: top -S -n 100 ps -axl vmstat -i sysctl kern sysctl vm And we can see if that gives some clues as to what the cpus are doing. It's a long shot but we have nothing else to go on. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 30 16:41:33 1999 Delivered-To: freebsd-stable@freebsd.org Received: from luna.lyris.net (luna.shelby.com [207.90.155.6]) by hub.freebsd.org (Postfix) with ESMTP id A13E215360 for ; Thu, 30 Dec 1999 16:41:29 -0800 (PST) (envelope-from kip@lyris.com) Received: from luna.shelby.com by luna.lyris.net (8.9.1b+Sun/SMI-SVR4) id QAA25687; Thu, 30 Dec 1999 16:40:42 -0800 (PST) Received: from (luna.shelby.com [207.90.155.6]) by luna.shelby.com with SMTP (MailShield v1.50); Thu, 30 Dec 1999 16:40:42 -0800 Date: Thu, 30 Dec 1999 16:40:42 -0800 (PST) From: Kip Macy To: David Schwartz Cc: tsikora@powerusersbbs.com, freebsd-stable@FreeBSD.ORG Subject: RE: Temperature Findings In-Reply-To: <000001bf5325$d5335630$021d85d1@youwant.to> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SMTP-HELO: luna X-SMTP-MAIL-FROM: kip@lyris.com X-SMTP-RCPT-TO: davids@webmaster.com,tsikora@powerusersbbs.com,freebsd-stable@FreeBSD.ORG X-SMTP-PEER-INFO: luna.shelby.com [207.90.155.6] Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 30 Dec 1999, David Schwartz wrote: > > It's really simple, your machine was configured beyond recommended settings > and as a result was unable to run at full speed for long periods of time. > Returning the machine to recommended settings solved the problem. Case > closed. Your machine was a ticking time bomb for any OS. > > DS I think everyone knows that. However, it does not answer his question about the temperature differences. -Kip To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 30 16:47:10 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id D72D714C34 for ; Thu, 30 Dec 1999 16:47:07 -0800 (PST) (envelope-from dkelly@nospam.hiwaay.net) Received: from nospam.hiwaay.net (tnt8-208-170-118-195.dialup.HiWAAY.net [208.170.118.195]) by mail.HiWAAY.net (8.9.3/8.9.0) with ESMTP id SAA01166; Thu, 30 Dec 1999 18:47:05 -0600 (CST) Received: from localhost (localhost [127.0.0.1]) by nospam.hiwaay.net (8.9.3/8.9.3) with ESMTP id SAA53665; Thu, 30 Dec 1999 18:47:03 -0600 (CST) (envelope-from dkelly@nospam.hiwaay.net) Message-Id: <199912310047.SAA53665@nospam.hiwaay.net> X-Mailer: exmh version 2.1.1 10/15/1999 To: tsikora@powerusersbbs.com Cc: "freebsd-stable@FreeBSD.ORG" From: David Kelly Subject: Re: Temperature In-reply-to: Message from Ted Sikora of "Thu, 30 Dec 1999 17:48:24 EST." <386BE138.E85A3DCB@home.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 30 Dec 1999 18:47:02 -0600 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ted Sikora writes: > Well I built another kernel without SMP and the temp dropped so I am > beginning to see this may be SMP related possibly. Later tonight I am > going to attach a mechanical gauge to the CPU's to verify the > temperatures. I failed to mention we have another (identical) board and > it reports the same thing so until I verify the temp the only other > possibility is a bug in the temp IC *but* the bios reports the same > thing as lmmon so that is doubtful. By education I'm a mechanical engineer. What I read that clicked that something was wrong was the observation Ted's temperatures were instantly off as quickly as he could read them after booting 3.4. It should take longer to rise 26F. Thermal inertia of the CPU mass. Rebooting to Linux should not take long enough for the CPU to cool 26F either. For an experiment, under Linux where is supposedly cooler, run someting CPU intensive such as the seti or dnetc client, see if the temperature rises. If not then we've bypassed the HLT command under Linux and demonstrated your system probably has sufficient cooling. For even more fun unplug your CPU fan during the above test and see how long it takes to rise 10F. Am expecting it to take about 10 minutes. If the readings are accurate, due to HLT being disabled or something, then there are other more serious problems with Ted's hardware. Airflow. Heatsink size. Fan. Something isn't up to 24/7 server standards. -- David Kelly N4HHE, dkelly@hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 30 16:49:15 1999 Delivered-To: freebsd-stable@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 7FC251525B; Thu, 30 Dec 1999 16:49:04 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 01D721CA0; Fri, 31 Dec 1999 08:49:02 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: Tom Cc: Matthew Dillon , freebsd-stable@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: softupdates and debug.max_softdeps In-Reply-To: Message from Tom of "Thu, 30 Dec 1999 11:14:08 PST." Date: Fri, 31 Dec 1999 08:49:01 +0800 From: Peter Wemm Message-Id: <19991231004902.01D721CA0@overcee.netplex.com.au> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG FYI: On hub.freebsd.org (the freebsd mailing list server), if we activate softupdates on the disk containing the postfix spool, the machine reboots (silently if I recall correctly) within 5 minutes of postfix starting up. This is a much smaller system of course, with smaller memory and filesystem working set. (postfix spool of ~50-80MB, 256MB ram). I thought I'd post this as a real-use datapoint. Tom wrote: > Yes, postmark operates on the same file set. I used the following > postmark settings: > > set number 30000 > set transactions 4000000 > set size 1500 200000 > > which uses a set of 30,000 files, and does a 4,000,000 transactions them > (random mix of various operations), and size between 1,500 and 200,000 > bytes. BTW, I hacked my version of postmark to use unsigned ints in > various places. > > I guess by having a very large filesystem (80GB), and mostly empty, the > softupdate code is able to queue an enormous amount of metadata updates > over time. > > I tried forcing max_softdeps down to 50,000, and within a couple of > hours all processes accessing that filesystem hung! > > Also, postmark is filesytem benchmarking and stress tester utility. > Adding fsync() would defeat the purpose a bit! > > So in summary, if max_softdeps is left at the default, the system will > reboot in 24 to 36 hours. If max_softdeps is set down, filesystem access > will eventually hang within 12 hours. > > > On Thu, 30 Dec 1999, Matthew Dillon wrote: > > > Well, in general I would not mess with max_softdeps - softupdates gets > > very inefficient if it hits its limits. I think you may have found a > > flaw in the code, though. Softupdates reschedules its vnode sync whene ver > > it does something to the vnode. Postmark must be operating on the same > > set of files for very long periods of time, including truncating and > > extending them, for softupdates to get that far behind! Kirk may have > > to modify the vnode scheduling to not reschedule the vnode beyond a > > certain aggregate delay in order to ensure that things get synchronized > > in a reasonable period of time. > > > > Softupdates biggest problem are with overly-long delays in block > > reclamation - several people have commented on it. I think what you > > are seeing is a special case of this problem that causes it to be much > > worse then normal. > > > > In the mean time you have a couple of choices. You can try running > > 'sync' every so often, or you can write a small C program to fsync() > > the files postfix messes with every so often. > > > > -Matt > > Matthew Dillon > > > > > > : I'm trying to find some information on reasonable settings for > > :debug.max_softdeps on a recent FreeBSD-stable system. > > : > > : It seems that if you have a machine that is able to generate disk IO > > :much faster than can be handled, has a large amount of RAM (and therefore > > :debug.max_softdeps is large), and the filesystem is very large (about > > :80GB), filesystem metadata updates can get _very_ far behind. > > : > > : For instance, on a test system running 4 instances of postmark > > :continuously for 24 hours, "df" reports that 40 GB of disk space is being > > :used, even though only about 5 GB is actually used. If I kill the > > :postmark processes, the metadata is eventually dribbled out and "df" > > :reports 5GB in use. It takes about 20 minutes for the metadata to be > > :updated on a completely ideal system. > > : > > : On this particular system, it doesn't seem to stabilize either. If the > > :4 postmark instances are allowed to run, disk usage seems to climb > > :indefinitely (at 40GB it was still climbing), until eventually the machine > > :silently reboots. > > : > > : debug.max_softdeps is by default set to 523,712 (1 GB of RAM). Is that > > :a resonable value? I see some tests in the docs with max_softdeps set to > > :4000 or so. > > : > > : > > :Tom > > > > > > > > > Tom > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 30 16:56:48 1999 Delivered-To: freebsd-stable@freebsd.org Received: from shell.webmaster.com (mail.webmaster.com [209.133.28.73]) by hub.freebsd.org (Postfix) with ESMTP id 7CF7D14C34 for ; Thu, 30 Dec 1999 16:56:46 -0800 (PST) (envelope-from davids@webmaster.com) Received: from whenever ([209.133.29.2]) by shell.webmaster.com (Post.Office MTA v3.5.3 release 223 ID# 0-12345L500S10000V35) with SMTP id com; Thu, 30 Dec 1999 16:56:44 -0800 From: "David Schwartz" To: "Kip Macy" Cc: , Subject: RE: Temperature Findings Date: Thu, 30 Dec 1999 16:56:44 -0800 Message-ID: <000101bf5329$e8080ef0$021d85d1@youwant.to> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0 In-Reply-To: Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Thu, 30 Dec 1999, David Schwartz wrote: > > > > > It's really simple, your machine was configured beyond > recommended settings > > and as a result was unable to run at full speed for long > periods of time. > > Returning the machine to recommended settings solved the problem. Case > > closed. Your machine was a ticking time bomb for any OS. > > > > DS > I think everyone knows that. However, it does not answer his question > about the temperature differences. > > -Kip His machine cannot run at full capacity. FreeBSD SMP runs the machine at full bore. He would probably see the same temperature results with Linux if he had two seti@home clients running or similar. DS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 30 17: 2:55 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail2.uniserve.com (mail2.uniserve.com [204.244.156.7]) by hub.freebsd.org (Postfix) with ESMTP id E039B15343; Thu, 30 Dec 1999 17:02:48 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca ([204.244.186.218]) by mail2.uniserve.com with smtp (Exim 3.03 #4) id 123qSj-000Bhp-00; Thu, 30 Dec 1999 17:02:37 -0800 Date: Thu, 30 Dec 1999 17:02:33 -0800 (PST) From: Tom X-Sender: tom@shell.uniserve.ca To: Peter Wemm Cc: Matthew Dillon , freebsd-stable@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: softupdates and debug.max_softdeps In-Reply-To: <19991231004902.01D721CA0@overcee.netplex.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, 31 Dec 1999, Peter Wemm wrote: > FYI: On hub.freebsd.org (the freebsd mailing list server), if we activate > softupdates on the disk containing the postfix spool, the machine reboots > (silently if I recall correctly) within 5 minutes of postfix starting up. > > This is a much smaller system of course, with smaller memory and filesystem > working set. (postfix spool of ~50-80MB, 256MB ram). I thought I'd post > this as a real-use datapoint. That is interesting. So I guess the conclusion to this is, softupdates is useful for bursty IO, but not sustained because it can get far behind until it eventually reaches the point where the machine reboots silently. I guess the delay until reboot is dependent on the size of max_softdeps. If it is big, it takes a while. I still think that the default value of max_softdeps might be too big for the kernel memory space. > -- > Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au > Tom Uniserve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 30 17:22:24 1999 Delivered-To: freebsd-stable@freebsd.org Received: from pluto.psn.net (pluto.psn.net [207.211.58.12]) by hub.freebsd.org (Postfix) with ESMTP id A829814E40; Thu, 30 Dec 1999 17:22:16 -0800 (PST) (envelope-from will@shadow.blackdawn.com) Received: from 20-172.008.popsite.net ([209.69.196.172] helo=shadow.blackdawn.com) by pluto.psn.net with esmtp (PSN Internet Service 3.12 #1) id 123qkr-0003ax-00; Thu, 30 Dec 1999 18:21:23 -0700 Received: (from will@localhost) by shadow.blackdawn.com (8.9.3/8.9.3) id UAA36875; Thu, 30 Dec 1999 20:21:16 -0500 (EST) (envelope-from will) Message-ID: X-Mailer: XFMail 1.3.1 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199912302038.MAA01353@mass.cdrom.com> Date: Thu, 30 Dec 1999 20:21:16 -0500 (EST) Reply-To: Will Andrews From: Will Andrews To: Mike Smith Subject: Re: Temperature Cc: "freebsd-stable@FreeBSD.ORG" , "freebsd-hackers@FreeBSD.ORG" , Marc Nicholas , tsikora@powerusersbbs.com Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 30-Dec-99 Mike Smith wrote: > You haven't by some chance just recently started running eg. the SETI > @home client, or one of the distributed.net clients by any chance? I forgot to mention that I run rc5des on my 3.4-STABLE machine here, and I rarely see the temperature higher than 32C (~90F). As I touch the grill where some of the air goes out, it feels quite cold. 32C as reported by wmhm through the intpm device. I might add this is a single PII-450 machine, with no overclocking or any stupid things like that. -- Will Andrews GCS/E/S @d- s+:+>+:- a--->+++ C++ UB++++ P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP+>+++ t++ 5 X++ R+ tv+ b++>++++ DI+++ D+ G++>+++ e->++++ h! r-->+++ y? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 30 17:29:43 1999 Delivered-To: freebsd-stable@freebsd.org Received: from celery.dragondata.com (celery.dragondata.com [205.253.12.6]) by hub.freebsd.org (Postfix) with ESMTP id 85F0B14D98; Thu, 30 Dec 1999 17:29:39 -0800 (PST) (envelope-from toasty@celery.dragondata.com) Received: (from toasty@localhost) by celery.dragondata.com (8.9.3/8.9.3) id TAA22448; Thu, 30 Dec 1999 19:29:55 -0600 (CST) (envelope-from toasty) From: Kevin Day Message-Id: <199912310129.TAA22448@celery.dragondata.com> Subject: Re: Temperature To: msmith@FreeBSD.ORG (Mike Smith) Date: Thu, 30 Dec 1999 19:29:55 -0600 (CST) Cc: tsikora@powerusersbbs.com, marc@netstor.com (Marc Nicholas), freebsd-hackers@FreeBSD.ORG (freebsd-hackers@FreeBSD.ORG), freebsd-stable@FreeBSD.ORG (freebsd-stable@FreeBSD.ORG) In-Reply-To: <199912302215.OAA02713@mass.cdrom.com> from "Mike Smith" at Dec 30, 1999 02:15:25 PM X-Mailer: ELM [version 2.5 PL1] 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 > I've also asked you to undertake the second phase, which is to perform a > binary-search set of kernel builds to pin down the timeframe in which > this change occurred. It's also been suggested that the scheduler > changes made by Bruce Evans may have impacted your system; you might want > to bracket those changes to quickly eliminate them as possibilities. In the very very very heat sensitve embedded product I'm working on, we have a system that has thermal probes all over the place that we use for testing. It's a Celeron 333(S370), 440ZX motherboard, and SDRAM DIMMs. In a very very unscientific test, using software that's not available anywhere outside my office, I can say that if anything, I see a 1 or 2 degree (C) *decrease* in CPU temperature between 3.2 and 3.4. (I do not have a 3.3 system to compare with to see if, in fact, 3.3 was very cool and 3.4 and 3.2 share the same brokenness). I'm also using external temperature probes, not using an LM78 or anything internal to measure the temperature. My honest guess is that something broke in 3.4 that's making it screw with the temperature readings, and the bios isn't setting it back right. :) Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 30 17:41:33 1999 Delivered-To: freebsd-stable@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 1FFB215386; Thu, 30 Dec 1999 17:41:30 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id RAA78648; Thu, 30 Dec 1999 17:41:26 -0800 (PST) (envelope-from dillon) Date: Thu, 30 Dec 1999 17:41:26 -0800 (PST) From: Matthew Dillon Message-Id: <199912310141.RAA78648@apollo.backplane.com> To: Tom Cc: Peter Wemm , freebsd-stable@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: softupdates and debug.max_softdeps References: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : That is interesting. So I guess the conclusion to this is, softupdates :is useful for bursty IO, but not sustained because it can get far behind :until it eventually reaches the point where the machine reboots silently. :I guess the delay until reboot is dependent on the size of max_softdeps. :If it is big, it takes a while. : : I still think that the default value of max_softdeps might be too big :for the kernel memory space. Well it sure isn't supposed to reboot silently! No panic message at all? No printf? Hopefully Kirk is around to help track down the problem but if not I'll take a crack at it after newyears if you create a PR for it and assign it to me. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 30 18:46: 6 1999 Delivered-To: freebsd-stable@freebsd.org Received: from workhorse.iMach.com (workhorse.iMach.com [206.127.77.89]) by hub.freebsd.org (Postfix) with ESMTP id 48E6414DBF for ; Thu, 30 Dec 1999 18:45:54 -0800 (PST) (envelope-from forrestc@workhorse.iMach.com) Received: from localhost (forrestc@localhost) by workhorse.iMach.com (8.9.3/8.9.3) with SMTP id TAA20661; Thu, 30 Dec 1999 19:41:03 -0700 (MST) Date: Thu, 30 Dec 1999 19:41:03 -0700 (MST) From: "Forrest W. Christian" To: Kip Macy Cc: David Schwartz , tsikora@powerusersbbs.com, freebsd-stable@FreeBSD.ORG Subject: RE: Temperature Findings In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 30 Dec 1999, Kip Macy wrote: > I think everyone knows that. However, it does not answer his question > about the temperature differences. I think the answer is ery simple. Single processor uses HLT. SMP does not. I suspect a 100% utilized box would be equal temp to the SMP. - Forrest W. Christian (forrestc@imach.com) KD7EHZ ---------------------------------------------------------------------- iMach, Ltd., P.O. Box 5749, Helena, MT 59604 http://www.imach.com Solutions for your high-tech problems. (406)-442-6648 ---------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 30 19:17:56 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail2.uniserve.com (mail2.uniserve.com [204.244.156.7]) by hub.freebsd.org (Postfix) with ESMTP id 75AB115467; Thu, 30 Dec 1999 19:17:37 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca ([204.244.186.218]) by mail2.uniserve.com with smtp (Exim 3.03 #4) id 123sZA-000EJ8-00; Thu, 30 Dec 1999 19:17:24 -0800 Date: Thu, 30 Dec 1999 19:17:19 -0800 (PST) From: Tom X-Sender: tom@shell.uniserve.ca To: Matthew Dillon Cc: Peter Wemm , freebsd-stable@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: softupdates and debug.max_softdeps In-Reply-To: <199912310141.RAA78648@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 30 Dec 1999, Matthew Dillon wrote: > : That is interesting. So I guess the conclusion to this is, softupdates > :is useful for bursty IO, but not sustained because it can get far behind > :until it eventually reaches the point where the machine reboots silently. > :I guess the delay until reboot is dependent on the size of max_softdeps. > :If it is big, it takes a while. > : > : I still think that the default value of max_softdeps might be too big > :for the kernel memory space. > > Well it sure isn't supposed to reboot silently! No panic message at > all? No printf? Well, a panic/printf should be recorded in the dmesg buffer, but I don't see anything. I'm using a serial terminal now, and I'm repeating my 4 x postmark test. > Hopefully Kirk is around to help track down the problem but if not I'll > take a crack at it after newyears if you create a PR for it and assign > it to me. I also don't think "sync" is a fix either. I expect "sync" to reclaim unused space. For instance, the file system currently shows 9 GB in use with "df", but there is only about 5 GB actually present on the disk. I ran "sync", and I expected "df" to report about 5GB used, but it doesn't seem to change anything. I'm going to try sync again tommorrow once the unreclaimed space is about 30GB or so, and see if it does anything. The only fix seems to be to halt IO before the mystery limit is hit, and let softupdates catch up on unreclaimed space. My 4 x postmark test completely maxes out the IO capacity of the system (ex. an ls of any empty directory taks 5 seconds). One thing that is interesting is that the following sysctl variables are always zero: debug.blk_limit_push: 0 debug.ino_limit_push: 0 debug.blk_limit_hit: 0 debug.ino_limit_hit: 0 debug.rush_requests: 0 So it doesn't look like softupdates is rushing things out. "vmstat -m" is showing that the storage for "inodedep" is steadily increasing. I _think_ I need to increase tick_delay, so when the max_softdeps limit is finally hit, syncer gets run for a while and clean things up. > -Matt Tom Uniserve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 30 19:37:32 1999 Delivered-To: freebsd-stable@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 1C6EE15372; Thu, 30 Dec 1999 19:37:28 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id TAA79239; Thu, 30 Dec 1999 19:37:26 -0800 (PST) (envelope-from dillon) Date: Thu, 30 Dec 1999 19:37:26 -0800 (PST) From: Matthew Dillon Message-Id: <199912310337.TAA79239@apollo.backplane.com> To: Tom Cc: Peter Wemm , freebsd-stable@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: softupdates and debug.max_softdeps References: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : : I also don't think "sync" is a fix either. I expect "sync" to reclaim :unused space. For instance, the file system currently shows 9 GB in use :with "df", but there is only about 5 GB actually present on the disk. I :ran "sync", and I expected "df" to report about 5GB used, but it doesn't :seem to change anything. I'm going to try sync again tommorrow once the :unreclaimed space is about 30GB or so, and see if it does anything. Try lots of sync's ... like one a second :-). One sync won't do it. But what we really want to do is make the thing crash and hopefully (with the serial console maybe) get a panic message. Conventionally what should be occuring is that the kernel should be running out of some memory pool. If this is what is occuring it should generate a panic message prior to rebooting. A couple of other things you can do: Compile up the kernel with DDB configured so the system drops into DDB instead of panicing (only do this if you have access to the console). Then you should be able to 'trace' and 'ps' prior to typing 'panic' manually (type as many s as necessary after that but be careful, you don't want to interrupt a kernel dump if the kernel has started one!). Using several local xterms with a large back buffer configured, ssh to the machine under test and setup a couple of csh while(1) loops to look at various kernel resources, e.g. while (1) vmstat -z; vmstat -m end end The reason you use a local xterm in which you ssh to the remote machine is so the xterm doesn't disappear on you when the remote machine crashes :-). A tail -f /var/log/messages will probably *NOT* spit out the panic message quickly enough, but a true serial console (not just a getty running on the port) should spit it out just fine. : One thing that is interesting is that the following sysctl variables are :always zero: : :debug.blk_limit_push: 0 :debug.ino_limit_push: 0 :debug.blk_limit_hit: 0 :debug.ino_limit_hit: 0 :debug.rush_requests: 0 : : So it doesn't look like softupdates is rushing things out. These aren't very useful unless you only have a tiny bit of main memory. for all practical purposes the limit is not usually ever reached (which is probably why its buggy when it *is* reached). : "vmstat -m" is showing that the storage for "inodedep" is steadily :increasing. : : I _think_ I need to increase tick_delay, so when the max_softdeps limit :is finally hit, syncer gets run for a while and clean things up. tick_delay will probably not have much of an effect. look at the vmstat -m output carefully as you run the test (as suggested above). Bad things happen if you run the kernel out of KVM, and that can happen even if you have plenty of normal ram. There are *TWO* limits involved. There is the limit for the memory pool you are observing, and there is a global limit on the grand total which is nominally 2x the per-pool limit. If either limit is reached the machine is hosed. :Tom :Uniserve -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 30 21:11: 8 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.rdc1.ct.home.com (ha1.rdc1.ct.home.com [24.2.0.66]) by hub.freebsd.org (Postfix) with ESMTP id 6D4C914DEA for ; Thu, 30 Dec 1999 21:11:05 -0800 (PST) (envelope-from tsikora@home.com) Received: from home.com ([24.2.168.186]) by mail.rdc1.ct.home.com (InterMail v4.01.01.07 201-229-111-110) with ESMTP id <19991231051101.RRVJ9446.mail.rdc1.ct.home.com@home.com>; Thu, 30 Dec 1999 21:11:01 -0800 Message-ID: <386C3AEB.1F0512E5@home.com> Date: Fri, 31 Dec 1999 00:11:07 -0500 From: Ted Sikora Reply-To: tsikora@powerusersbbs.com Organization: Jtl Development X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.4-STABLE i386) X-Accept-Language: en-US,en-GB MIME-Version: 1.0 To: David Schwartz , "freebsd-stable@FreeBSD.ORG" Subject: Re: Temperature Findings References: <000101bf5329$e8080ef0$021d85d1@youwant.to> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David Schwartz wrote: > > > On Thu, 30 Dec 1999, David Schwartz wrote: > > > > > > > > It's really simple, your machine was configured beyond > > recommended settings > > > and as a result was unable to run at full speed for long > > periods of time. > > > Returning the machine to recommended settings solved the problem. Case > > > closed. Your machine was a ticking time bomb for any OS. > > > > > > DS > > > I think everyone knows that. However, it does not answer his question > > about the temperature differences. > > > > -Kip > > His machine cannot run at full capacity. FreeBSD SMP runs the machine at > full bore. He would probably see the same temperature results with Linux if > he had two seti@home clients running or similar. That's exactly how the machine was run for many months. FreeBSD was added only recently to this machine. I usally start 2 seti sessions when I'm done for the day on this machine. Under Linux it never..ever reached even 100F.(still the same) That's whats so baffling about this.(I only overclocked it very recently out of curiosity) Tommorow I am going to run the programs Peter suggested. On the sessions between Linux and FreeBSD I usually shut it off for a moment the temperatures took a while to stabilize it was not immediately cool as someone questioned. I want to stress it again this is only with the SMP kernel. The standard kernels do indeed run cool. -- Ted Sikora Jtl Development Group tsikora@powerusersbbs.com http://powerusersbbs.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 30 21:56: 7 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.rdc1.ct.home.com (ha1.rdc1.ct.home.com [24.2.0.66]) by hub.freebsd.org (Postfix) with ESMTP id 6EB2D14CB2 for ; Thu, 30 Dec 1999 21:55:55 -0800 (PST) (envelope-from tsikora@home.com) Received: from home.com ([24.2.168.186]) by mail.rdc1.ct.home.com (InterMail v4.01.01.07 201-229-111-110) with ESMTP id <19991231055551.RYTG9446.mail.rdc1.ct.home.com@home.com>; Thu, 30 Dec 1999 21:55:51 -0800 Message-ID: <386C456E.3F90CE8A@home.com> Date: Fri, 31 Dec 1999 00:55:58 -0500 From: Ted Sikora Reply-To: tsikora@powerusersbbs.com Organization: Jtl Development X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.4-STABLE i386) X-Accept-Language: en-US,en-GB MIME-Version: 1.0 To: Peter Wemm , "freebsd-stable@FreeBSD.ORG" Subject: Re: Temperature References: <19991231003718.71BAE1CA0@overcee.netplex.com.au> Content-Type: multipart/mixed; boundary="------------494FA547AF4C3F09BEC1AD93" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------494FA547AF4C3F09BEC1AD93 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Peter Wemm wrote: > > Ted Sikora wrote: > > > These are both taken right after bootup with X started and WindowMaker > > running. No other apps running. > > Can you please include: > top -S -n 100 > ps -axl > vmstat -i > sysctl kern > sysctl vm > > And we can see if that gives some clues as to what the cpus are doing. It's > a long shot but we have nothing else to go on. > Here they are: Temp when taken: 109F CPU#0 109F CPU#1 107F CASE (room temp 64F) -- Ted Sikora Jtl Development Group tsikora@powerusersbbs.com http://powerusersbbs.com --------------494FA547AF4C3F09BEC1AD93 Content-Type: text/plain; charset=us-ascii; name="kern.txt" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="kern.txt" kern.ostype: FreeBSD kern.osrelease: 3.4-STABLE kern.osrevision: 199506 kern.version: FreeBSD 3.4-STABLE #0: Thu Dec 30 18:43:41 EST 1999 root@telecast.htfds1.ct.home.com:/usr/src/sys/compile/TELECAST kern.maxvnodes: 4416 kern.maxproc: 532 kern.maxfiles: 1064 kern.argmax: 65536 kern.securelevel: -1 kern.hostname: telecast.htfds1.ct.home.com kern.hostid: 0 kern.clockrate: { hz = 100, tick = 10000, tickadj = 5, profhz = 1024, stathz = 128 } kern.posix1version: 199309 kern.ngroups: 16 kern.job_control: 1 kern.saved_ids: 0 kern.boottime: { sec = 946615599, usec = 626699 } Thu Dec 30 23:46:39 1999 kern.domainname: kern.osreldate: 340001 kern.bootfile: /kernel kern.maxfilesperproc: 1064 kern.maxprocperuid: 531 kern.dumpdev: { major = 255, minor = -65281 } kern.ipc.maxsockbuf: 262144 kern.ipc.sockbuf_waste_factor: 8 kern.ipc.somaxconn: 128 kern.ipc.max_linkhdr: 16 kern.ipc.max_protohdr: 40 kern.ipc.max_hdr: 56 kern.ipc.max_datalen: 40 kern.ipc.nmbclusters: 1024 kern.ipc.maxsockets: 1064 kern.dummy: 0 kern.ps_strings: -1077944336 kern.usrstack: -1077944320 kern.logsigexit: 1 kern.init_path: /sbin/init:/sbin/oinit:/sbin/init.bak:/stand/sysinstall kern.module_path: /;/boot/;/modules/ kern.acct_suspend: 2 kern.acct_resume: 4 kern.acct_chkfreq: 15 kern.timecounter.method: 0 kern.fast_vfork: 0 kern.sugid_coredump: 0 kern.corefile: %N.core kern.quantum: 100000 kern.ccpu: 1948 kern.fscale: 2048 kern.devstat.numdevs: 2 kern.devstat.generation: 2 kern.devstat.version: 3 kern.consmute: 0 --------------494FA547AF4C3F09BEC1AD93 Content-Type: text/plain; charset=us-ascii; name="psaxl.txt" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="psaxl.txt" UID PID PPID CPU PRI NI VSZ RSS WCHAN STAT TT TIME COMMAND 0 0 0 0 -18 0 0 0 sched DLs ?? 0:00.00 (swapper) 0 1 0 0 10 0 496 248 wait Is ?? 0:00.02 /sbin/init 0 2 0 0 -18 0 0 0 psleep DL ?? 0:00.01 (pagedaemo 0 3 0 0 18 0 0 0 psleep DL ?? 0:00.00 (vmdaemon) 0 4 0 0 18 0 0 0 syncer DL ?? 0:00.09 (syncer) 0 35 1 32 18 0 204 80 pause Is ?? 0:00.00 adjkerntz - 0 112 1 0 2 0 824 516 select Is ?? 0:00.05 syslogd 1 121 1 32 2 0 824 376 select Is ?? 0:00.00 /usr/sbin/p 0 134 1 0 10 0 212 76 nfsidl I ?? 0:00.98 nfsiod -n 4 0 135 1 0 10 0 212 76 nfsidl I ?? 0:00.37 nfsiod -n 4 0 136 1 0 10 0 212 76 nfsidl I ?? 0:00.05 nfsiod -n 4 0 137 1 0 10 0 212 76 nfsidl I ?? 0:00.02 nfsiod -n 4 0 163 1 32 2 0 900 664 select Is ?? 0:00.02 inetd -wW 0 166 1 0 10 0 988 564 nanslp Is ?? 0:00.03 cron 0 170 1 0 2 0 1320 956 select Is ?? 0:00.02 sendmail: a 0 206 1 0 2 0 792 420 select Ss ?? 0:02.33 moused -p / 0 224 1 33 2 0 1744 1184 poll Is ?? 0:00.15 /usr/local/ 0 288 287 0 2 0 24420 23052 select S ?? 0:17.72 /usr/X11R6/ 0 358 357 0 10 0 1460 972 wait Ss p0 0:00.04 bash 0 364 358 0 28 0 400 244 - R+ p0 0:00.00 ps -axl 0 252 1 0 10 0 1472 944 wait Is v0 0:00.10 -bash (bash 0 275 252 23 10 0 504 276 wait I+ v0 0:00.02 /bin/sh /us 0 276 252 0 -6 0 772 336 piperd I+ v0 0:00.03 tee /root/. 0 287 275 0 10 0 1864 980 wait I+ v0 0:00.02 xinit /usr/ 0 289 287 0 2 0 3136 2320 select S v0 0:01.85 wmaker 0 307 289 0 2 0 4308 3880 select S v0 0:00.66 wish8.2 /us 0 312 289 1 2 0 22892 19056 select S v0 0:36.71 /usr/local/ 0 313 312 1 2 0 16088 5664 select I v0 0:00.07 (dns helper 0 357 289 0 2 0 3076 2132 select S v0 0:00.08 xterm 0 253 1 0 3 0 832 584 ttyin Is+ v1 0:00.02 /usr/libexe 0 254 1 0 3 0 832 584 ttyin Is+ v2 0:00.02 /usr/libexe 0 255 1 0 3 0 832 584 ttyin Is+ v3 0:00.01 /usr/libexe 0 256 1 0 3 0 832 584 ttyin Is+ v4 0:00.01 /usr/libexe 0 257 1 0 3 0 832 584 ttyin Is+ v5 0:00.01 /usr/libexe 0 258 1 0 3 0 832 584 ttyin Is+ v6 0:00.01 /usr/libexe 0 259 1 0 3 0 832 584 ttyin Is+ v7 0:00.01 /usr/libexe --------------494FA547AF4C3F09BEC1AD93 Content-Type: text/plain; charset=us-ascii; name="top.txt" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="top.txt" last pid: 403; load averages: 0.05, 0.12, 0.11 up 0+00:44:03 00:30:12 36 processes: 1 running, 35 sleeping Mem: 25M Active, 17M Inact, 11M Wired, 2252K Cache, 7531K Buf, 4984K Free Swap: 132M Total, 132M Free PID USERNAME PRI NICE SIZE RES STATE C TIME WCPU CPU COMMAND 312 root 2 0 22892K 19056K select 0 0:39 0.00% 0.00% communicator 288 root 2 0 24468K 23000K select 0 0:21 0.00% 0.00% XF86_SVGA 206 root 2 0 792K 380K select 1 0:03 0.00% 0.00% moused 289 root 2 0 3136K 2140K select 0 0:02 0.00% 0.00% wmaker 134 root 10 0 212K 28K nfsidl 1 0:01 0.00% 0.00% nfsiod 307 root 2 0 4308K 3780K select 1 0:01 0.00% 0.00% wish8.2 135 root 10 0 212K 28K nfsidl 0 0:00 0.00% 0.00% nfsiod 224 root 2 0 1744K 1028K poll 1 0:00 0.00% 0.00% sshd 357 root 2 0 3076K 2092K select 0 0:00 0.00% 0.00% xterm 4 root 18 0 0K 0K syncer 0 0:00 0.00% 0.00% syncer 252 root 10 0 1472K 860K wait 0 0:00 0.00% 0.00% bash 313 root 2 0 16088K 5664K select 1 0:00 0.00% 0.00% communicator 358 root 10 0 1464K 896K wait 0 0:00 0.00% 0.00% bash 112 root 2 0 824K 476K select 1 0:00 0.00% 0.00% syslogd 136 root 10 0 212K 28K nfsidl 0 0:00 0.00% 0.00% nfsiod 166 root 10 0 988K 488K nanslp 0 0:00 0.00% 0.00% cron 276 root -6 0 772K 304K piperd 1 0:00 0.00% 0.00% tee 170 root 2 0 1320K 780K select 1 0:00 0.00% 0.00% sendmail 163 root 2 0 900K 580K select 1 0:00 0.00% 0.00% inetd 137 root 10 0 212K 28K nfsidl 0 0:00 0.00% 0.00% nfsiod 253 root 3 0 832K 520K ttyin 1 0:00 0.00% 0.00% getty 275 root 10 0 504K 184K wait 1 0:00 0.00% 0.00% sh 287 root 10 0 1864K 924K wait 1 0:00 0.00% 0.00% xinit 254 root 3 0 832K 520K ttyin 0 0:00 0.00% 0.00% getty 1 root 10 0 496K 164K wait 0 0:00 0.00% 0.00% init 258 root 3 0 832K 520K ttyin 1 0:00 0.00% 0.00% getty 256 root 3 0 832K 520K ttyin 0 0:00 0.00% 0.00% getty 403 root 28 0 1560K 816K CPU1 1 0:00 0.00% 0.00% top 2 root -18 0 0K 0K psleep 0 0:00 0.00% 0.00% pagedaemon 257 root 3 0 832K 520K ttyin 1 0:00 0.00% 0.00% getty 259 root 3 0 832K 520K ttyin 0 0:00 0.00% 0.00% getty 255 root 3 0 832K 520K ttyin 1 0:00 0.00% 0.00% getty 121 daemon 2 0 824K 340K select 0 0:00 0.00% 0.00% portmap 0 root -18 0 0K 0K sched 0 0:00 0.00% 0.00% swapper 35 root 18 0 204K 56K pause 0 0:00 0.00% 0.00% adjkerntz 3 root 18 0 0K 0K psleep 1 0:00 0.00% 0.00% vmdaemon --------------494FA547AF4C3F09BEC1AD93 Content-Type: text/plain; charset=us-ascii; name="vm.txt" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="vm.txt" vm.loadavg: { 0.11 0.17 0.13 } vm.v_free_min: 210 vm.v_free_target: 764 vm.v_free_reserved: 134 vm.v_inactive_target: 1146 vm.v_cache_min: 764 vm.v_cache_max: 1528 vm.v_pageout_free_min: 34 vm.pageout_algorithm: 0 vm.swap_enabled: 1 vm.swap_idle_threshold1: 2 vm.swap_idle_threshold2: 10 vm.stats.sys.v_swtch: 204576 vm.stats.sys.v_trap: 75907 vm.stats.sys.v_syscall: 2734322 vm.stats.sys.v_intr: 627010 vm.stats.sys.v_soft: 119704 vm.stats.vm.v_vm_faults: 32784 vm.stats.vm.v_cow_faults: 7935 vm.stats.vm.v_cow_optim: 1473 vm.stats.vm.v_zfod: 17644 vm.stats.vm.v_ozfod: 16757 vm.stats.vm.v_swapin: 0 vm.stats.vm.v_swapout: 0 vm.stats.vm.v_swappgsin: 0 vm.stats.vm.v_swappgsout: 0 vm.stats.vm.v_vnodein: 644 vm.stats.vm.v_vnodeout: 0 vm.stats.vm.v_vnodepgsin: 5692 vm.stats.vm.v_vnodepgsout: 0 vm.stats.vm.v_intrans: 4 vm.stats.vm.v_reactivated: 20 vm.stats.vm.v_pdwakeups: 1 vm.stats.vm.v_pdpages: 765 vm.stats.vm.v_dfree: 0 vm.stats.vm.v_pfree: 13618 vm.stats.vm.v_tfree: 28721 vm.stats.vm.v_page_size: 4096 vm.stats.vm.v_page_count: 15539 vm.stats.vm.v_free_reserved: 134 vm.stats.vm.v_free_target: 764 vm.stats.vm.v_free_min: 210 vm.stats.vm.v_free_count: 1016 vm.stats.vm.v_wire_count: 2879 vm.stats.vm.v_active_count: 6661 vm.stats.vm.v_inactive_target: 1146 vm.stats.vm.v_inactive_count: 4361 vm.stats.vm.v_cache_count: 611 vm.stats.vm.v_cache_min: 764 vm.stats.vm.v_cache_max: 1528 vm.stats.vm.v_pageout_free_min: 34 vm.stats.vm.v_interrupt_free_min: 2 vm.stats.misc.zero_page_count: 949 vm.stats.misc.cnt_prezero: 28980 vm.pageout_stats_max: 764 vm.pageout_full_stats_interval: 20 vm.pageout_stats_interval: 5 vm.pageout_stats_free_max: 5 vm.swap_idle_enabled: 0 vm.defer_swapspace_pageouts: 0 vm.disable_swapspace_pageouts: 0 vm.max_page_launder: 32 vm.zone: ITEM SIZE LIMIT USED FREE REQUESTS PIPE: 160, 0, 18, 84, 157 unpcb: 64, 0, 16, 112, 30 ripcb: 96, 1064, 0, 42, 0 tcpcb: 288, 1064, 12, 30, 15 udpcb: 96, 1064, 6, 78, 33 unpcb: 64, 0, 0, 0, 0 socket: 160, 1064, 34, 41, 84 AIOLIO: 704, 0, 0, 0, 0 AIOL: 64, 0, 0, 0, 0 AIOCB: 128, 0, 0, 0, 0 AIOP: 32, 0, 0, 0, 0 AIO: 96, 0, 0, 0, 0 NFSNODE: 288, 0, 25, 31, 39 NFSMOUNT: 544, 0, 2, 12, 0 VNODE: 192, 0, 634, 108, 627 NAMEI: 1024, 0, 0, 16, 13631 VMSPACE: 192, 0, 37, 27, 379 PROC: 352, 0, 37, 21, 379 DP fakepg: 64, 0, 23, 105, 22 PV ENTRY: 28, 139162, 13837, 2544, 103799 MAP ENTRY: 40, 0, 643, 199, 11942 KMAP ENTRY: 40, 4012, 66, 164, 878 MAP: 100, 0, 7, 3, 7 VM OBJECT: 124, 0, 919, 63, 8168 vm.zone_kmem_pages: 10 vm.zone_kmem_kvaspace: 4280320 vm.zone_kern_pages: 90 --------------494FA547AF4C3F09BEC1AD93 Content-Type: text/plain; charset=us-ascii; name="vmstat.txt" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="vmstat.txt" interrupt total rate clk0 irq2 250647 99 rtc0 irq8 320823 127 wdc0 irq14 3311 1 atkbd0 irq1 2431 0 sio0 irq4 43471 17 ed0 irq10 21116 8 sb0 irq5 1 0 Total 641800 256 --------------494FA547AF4C3F09BEC1AD93-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 30 22:17: 9 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mass.cdrom.com (castles532.castles.com [208.214.165.96]) by hub.freebsd.org (Postfix) with ESMTP id 2AD2D14CF0 for ; Thu, 30 Dec 1999 22:17:05 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id WAA00554; Thu, 30 Dec 1999 22:22:17 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912310622.WAA00554@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Mr. K." Cc: stable@freebsd.org Subject: Re: Panic: Out of mbuf clusters In-reply-to: Your message of "Thu, 30 Dec 1999 17:48:14 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 30 Dec 1999 22:22:17 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > OK, so I raised NMBCLUSTERS to 4096, and installed a second freebsd-stable > box also with NMBCLUSTERS at 4096, and I managed to have them both panic > at the same time (unfortunately, only one of them gave me a crash dump). > But anyway, here is the stack trace, hopefully someone can tell me if this > is the same as the known problem, and whether 4.0 would fix it. Again, 4096 is (obviously) not high enough. No, upgrading to 4.x won't "fix" your problem. The panic is telling you that you _have_not_ tuned the system correctly. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 30 22:21:54 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mass.cdrom.com (castles532.castles.com [208.214.165.96]) by hub.freebsd.org (Postfix) with ESMTP id 2F92E154AC for ; Thu, 30 Dec 1999 22:21:51 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id WAA00576; Thu, 30 Dec 1999 22:27:02 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912310627.WAA00576@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: tsikora@powerusersbbs.com Cc: "freebsd-stable@FreeBSD.ORG" Subject: Re: Temperature Findings In-reply-to: Your message of "Thu, 30 Dec 1999 19:20:26 EST." <386BF6CA.EA00DF5C@home.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 30 Dec 1999 22:27:02 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I had one my technicians set up a scope to test the voltage readings and > a Cooper temperature gauge to check the case temp. We decided to abandon > the CPU test since we had no accurate way to attach the gauge. Our > findings: > The voltage readings by the winbond IC in the bios are accurate. > The case temperature was 5F cooler than reported. > So I would conclude the readings from the bios are a fairly accurate > representation of the machines current condition. > > Things I failed to mention. > The CPU's were overclocked by 100MHz > Core CPU Voltage was raised a 1/2 step to 2.05V > > o This still does not explain the differences between Linux > and FreeBSD. The difference has already been explained as a different instruction mix. This should be obvious to anyone that has been in the industry for as long as you have. > o The standard 3.3-RELEASE UniProcessor kernel runs identical to > Linux. This is because both systems use the HLT instruction, which has a low power consumption. You've already been told this. > o FreeBSD SMP kernels immediately run hotter than the standard > kernel. FreeBSD doesn't use HLT in the SMP implementation. You've been told this as well. > I put Core voltage back to normal and set the CPU's to standard > settings. The result was much better but it still runs about 14 degrees > hotter.(acceptable) 26 degrees was not. > > Has anyone else checked this. Just checking the Generic versus a SMP > kernel you should see this. This is commonly known behaviour. Your problem is simply that your cooling setup is not adequate to support your system running at 100% duty cycle. You've been told this already. You need to upgrade your cooling arrangements, and you've been told _that_ already too. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 30 23:49:54 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.cybcon.com (mail.cybcon.com [216.190.188.5]) by hub.freebsd.org (Postfix) with ESMTP id D5EFC14A1B; Thu, 30 Dec 1999 23:49:49 -0800 (PST) (envelope-from freebsd@cybcon.com) Received: from laptop.cybcon.com (william@usr1-23.cybcon.com [205.147.75.24]) by mail.cybcon.com (8.9.3/8.9.3) with ESMTP id XAA26664; Thu, 30 Dec 1999 23:49:47 -0800 (PST) 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 Date: Thu, 30 Dec 1999 23:51:30 -0800 (PST) From: William Woods To: freebsd-questions@freebsd.org, freebsd-stable@freebsd.org Subject: StarOffice5 problems.... Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am useing (trying to anyway) the StarOffice 5 port on a FreeBSD 3.4 system /usr/ports/editors/staroffice5 but its asking for a couple libs: Here is the makefile: DISTNAME= so51a_lnx_01 PKGNAME= staroffice-5.1a CATEGORIES= editors MASTER_SITES= ftp://ftp.hagenhomes.com/pub/ \ ftp://ftp.stat.duke.edu/pub/Users/sto/StarOffice51a/ \ ftp://ftp.stardivision.de/pub/support/so51a/nwspatch/unxlnxi/ \ ftp://ftp.stardivision.de/pub/support/so51a/db/unxlnxi/ EXTRACT_SUFX= .tar DISTFILES= applicat.rdb.gz libofa517li.so libsdb517li.s ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ As you can see, the ftp sites are looking fot ftp.stardivision.de, which no longer does staroffice. Anyone out there have the libs you can email me? I cant find them anywhere.... ---------------------------------- E-Mail: William Woods Date: 30-Dec-99 Time: 23:47:45 FreeBSD 3.4 On a Laptop......... ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Dec 31 1:32:50 1999 Delivered-To: freebsd-stable@freebsd.org Received: from dozer.skynet.be (dozer.skynet.be [195.238.2.36]) by hub.freebsd.org (Postfix) with ESMTP id BA04D15019; Fri, 31 Dec 1999 01:32:46 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by dozer.skynet.be (8.9.3/odie-relay-v1.0) with ESMTP id KAA26117; Fri, 31 Dec 1999 10:32:42 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@foxbert.skynet.be Message-Id: In-Reply-To: <199912310627.WAA00576@mass.cdrom.com> References: <199912310627.WAA00576@mass.cdrom.com> Date: Fri, 31 Dec 1999 09:50:52 +0100 To: Mike Smith , tsikora@powerusersbbs.com From: Brad Knowles Subject: Re: Temperature Findings Cc: "freebsd-stable@FreeBSD.ORG" Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 10:27 PM -0800 1999/12/30, Mike Smith wrote: > The difference has already been explained as a different instruction mix. > This should be obvious to anyone that has been in the industry for as > long as you have. It seems to me that you guys are all talking past each other: 1. He's mentioned that he runs the same instruction mix (i.e., two seti@home clients) under both Linux and FreeBSD 2. He's mentioned that he's run FreeBSD in both uniprocessor and SMP modes 3. He's mentioned that he's run FreeBSD SMP with 3.3 without problems 4. He's mentioned that the overclocking is a recent introduction to the issue and the system was overheating before then 5. He's also mentioned that this is a chipset which we now know is not directly supported by the measurement interface, and therefore the temperature multiples might (or might not) be off Now, I don't recall seeing which version of the Linux kernel he was talking about -- I'd be guessing that might have some effect. If it was a 2.0.x kernel, then obviously he's not getting more than one processor under Linux anyway. Depending on which 2.1.x or 2.2.x kernel he runs, he should be getting SMP under Linux (if he's built the kernel to support SMP), although he might not have very good SMP (2.2.13+, from all reports I've heard). I'd be real surprised if they found some way to HLT the processor under Linux in SMP, but I wouldn't rule it out as impossible. I do still find it suspicious that the temperature difference is 14 or 26 degrees, and that it rises much more quickly than would appear to be possible, given the thermal mass, etc.... I also find it suspicious that this works fine under FreeBSD in SMP in version 3.3 (even with all the overclocking, etc...) and that this only breaks in 3.4. Of course, the fact that everyone is talking past each other is not surprising, seeing as many of the correspondents are spread around the globe. If I might make a suggestion based on my own recent introduction to this mailing list -- it really helps if the new poster provides as much detail as possible and doesn't make any assumptions about how much they know about the problem based on their decade-plus (or more) experience, and it really helps if the other people involved give the guy at least half a break while he tries to explain what weirdo whacked out thing he's seeing. Myself, I think I've permanently pissed-off some of the important contributors to the FreeBSD project (and perhaps even some of the core members) by coming in too strong. I hope that one day I'll manage to be able to erase that deficit either by patching things up with the parties in question, or by making enough of my own positive contributions that the past can be forgiven, if not forgotten. Ghu help me if I'm actually the voice of reason in this case, but I felt like something needed to be said before this got too far out of hand. -- These are my opinions -- not to be taken as official Skynet policy ____________________________________________________________________ |o| Brad Knowles, Belgacom Skynet NV/SA |o| |o| Systems Architect, News & FTP Admin Rue Col. Bourg, 124 |o| |o| Phone/Fax: +32-2-706.11.11/12.49 B-1140 Brussels |o| |o| http://www.skynet.be Belgium |o| \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. Unix is very user-friendly. It's just picky who its friends are. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Dec 31 1:57:54 1999 Delivered-To: freebsd-stable@freebsd.org Received: from freeway.dcfinc.com (cx74889-a.phnx3.az.home.com [24.1.193.157]) by hub.freebsd.org (Postfix) with ESMTP id 3C0591550B; Fri, 31 Dec 1999 01:57:52 -0800 (PST) (envelope-from chad@freeway.dcfinc.com) Received: (from chad@localhost) by freeway.dcfinc.com (8.8.8/8.8.8) id CAA22452; Fri, 31 Dec 1999 02:57:51 -0700 (MST) (envelope-from chad) From: "Chad R. Larson" Message-Id: <199912310957.CAA22452@freeway.dcfinc.com> Subject: Re: Temperature Findings In-Reply-To: <199912310627.WAA00576@mass.cdrom.com> from Mike Smith at "Dec 30, 99 10:27:02 pm" To: msmith@FreeBSD.ORG (Mike Smith) Date: Fri, 31 Dec 1999 02:57:51 -0700 (MST) Cc: tsikora@powerusersbbs.com, freebsd-stable@FreeBSD.ORG Reply-To: chad@DCFinc.com X-Mailer: ELM [version 2.4ME+ PL40 (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 As I recall, Mike Smith wrote: >> o The standard 3.3-RELEASE UniProcessor kernel runs identical to >> Linux. > > This is because both systems use the HLT instruction, which has a low > power consumption. You've already been told this. > >> o FreeBSD SMP kernels immediately run hotter than the standard >> kernel. > > FreeBSD doesn't use HLT in the SMP implementation. You've been told > this as well. > >> Has anyone else checked this. Just checking the Generic versus a SMP >> kernel you should see this. > > This is commonly known behaviour. Your problem is simply that your > cooling setup is not adequate to support your system running at 100% duty > cycle. You've been told this already. You need to upgrade your cooling > arrangements, and you've been told _that_ already too. No wonder he feels like he's being called a yokel. So, how does the lack of HLTing explain why his system =doesn't= report itself as being hot when he runs two SETI@home processes under Linux? How come the difference is instantly apparent after the reboot--not subject to thermal inertia--if inadequate cooling were the culprit? -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org larson1@home.net DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Dec 31 2:19:53 1999 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 6D73715327 for ; Fri, 31 Dec 1999 02:19:51 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p16-dn01kiryunisiki.gunma.ocn.ne.jp [210.132.6.145]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id TAA04112; Fri, 31 Dec 1999 19:19:42 +0900 (JST) Message-ID: <386C79EE.23862BEA@newsguy.com> Date: Fri, 31 Dec 1999 18:39:58 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: tsikora@powerusersbbs.com Cc: "freebsd-stable@FreeBSD.ORG" Subject: Re: Temperature Findings References: <199912302215.OAA02713@mass.cdrom.com> <386BE138.E85A3DCB@home.com> <386BF6CA.EA00DF5C@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 Ted Sikora wrote: > > The voltage readings by the winbond IC in the bios are accurate. > The case temperature was 5F cooler than reported. > So I would conclude the readings from the bios are a fairly accurate > representation of the machines current condition. Was this tested with both Linux (or an UP kernel) *and* FreeBSD 3.4R? -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "Nice try, Lao Che." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Dec 31 4:26: 2 1999 Delivered-To: freebsd-stable@freebsd.org Received: from gov.mari.ru (GOVERNMENT-3-2LL-MARTELCOM.relinfo.ru [195.161.209.90]) by hub.freebsd.org (Postfix) with ESMTP id 5D48614DBF for ; Fri, 31 Dec 1999 04:25:59 -0800 (PST) (envelope-from kuks@gov.mari.ru) Received: from host3.gov.mari.ru (host3.gov.mari.ru [195.161.213.3]) by gov.mari.ru (8.9.3/X.X.X) with ESMTP id OAA00628 for ; Fri, 31 Dec 1999 14:54:39 +0300 (MSK) Date: Fri, 31 Dec 1999 14:49:47 +0300 From: kuks X-Mailer: The Bat! (v1.35) S/N 20E8 Reply-To: kuks Organization: Grey House X-Priority: 3 (Normal) Message-ID: <5617.991231@gov.mari.ru> To: freebsd-stable@FreeBSD.org Subject: subscribe freebsd-stable 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Dec 31 6:31:25 1999 Delivered-To: freebsd-stable@freebsd.org Received: from inbox.org (inbox.org [216.22.145.8]) by hub.freebsd.org (Postfix) with ESMTP id 7734214EF4 for ; Fri, 31 Dec 1999 06:31:20 -0800 (PST) (envelope-from bsd@inbox.org) Received: from localhost (bsd@localhost) by inbox.org (8.9.3/8.9.3) with SMTP id JAA02016 for ; Fri, 31 Dec 1999 09:31:22 -0500 (EST) Date: Fri, 31 Dec 1999 09:31:22 -0500 (EST) From: "Mr. K." To: stable@freebsd.org Subject: Re: Temperature In-Reply-To: <199912310047.SAA53665@nospam.hiwaay.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 Of course, the problem could be that linux is simply not reporting the right temperature (too low), and that your overclocked chips simply can't handle SMP. On Thu, 30 Dec 1999, David Kelly wrote: > Ted Sikora writes: > > Well I built another kernel without SMP and the temp dropped so I am > > beginning to see this may be SMP related possibly. Later tonight I am > > going to attach a mechanical gauge to the CPU's to verify the > > temperatures. I failed to mention we have another (identical) board and > > it reports the same thing so until I verify the temp the only other > > possibility is a bug in the temp IC *but* the bios reports the same > > thing as lmmon so that is doubtful. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Dec 31 6:38:45 1999 Delivered-To: freebsd-stable@freebsd.org Received: from luke.immure.com (cust-42-74.customer.jump.net [207.8.42.74]) by hub.freebsd.org (Postfix) with ESMTP id C042215031 for ; Fri, 31 Dec 1999 06:38:42 -0800 (PST) (envelope-from bob@luke.immure.com) Received: (from bob@localhost) by luke.immure.com (8.9.3/8.9.3) id IAA10879 for freebsd-stable@freebsd.org; Fri, 31 Dec 1999 08:38:42 -0600 (CST) (envelope-from bob) Date: Fri, 31 Dec 1999 08:38:42 -0600 From: Bob Willcox To: stable list Subject: Host command output changed in bind 8.2.2p5 Message-ID: <19991231083842.A10723@luke.immure.com> Reply-To: Bob Willcox Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have noticed that the host command no longer produces the same output as it did prior to the bind 8.2.2p5 import to 3.4. For machines with an MX record prior to bind 8.2.2p5 I used to get: bob@obiwan-p4 /home/bob> host umd1.umd.edu umd1.umd.edu is a nickname for haven.umd.edu haven.umd.edu has address 128.8.10.6 haven.umd.edu mail is handled (pri=4) by haven.umd.edu But now on a recently upgraded 3.4-stable system I get: bob@luke:p6 /home/bob> host umd1.umd.edu umd1.umd.edu is a nickname for haven.umd.edu haven.umd.edu has address 128.8.10.6 haven.umd.edu has address 128.8.10.6 The uname -a output from the first system is: FreeBSD obiwan.pmr.com 3.4-RC FreeBSD 3.4-RC #11: Sun Dec 12 17:14:35 CST 1999 bob@obiwan.pmr.com:/usr2/src/sys/compile/OBIWAN i386 and the second: FreeBSD luke.immure.com 3.4-STABLE FreeBSD 3.4-STABLE #19: Thu Dec 30 20:10:23 CST 1999 bob@luke.immure.com:/usr/src/sys/compile/LUKE i386 Anybody else noticed this? Thanks, Bob -- Bob Willcox Don't tell me that worry doesn't do any good. bob@pmr.com I know better. The things I worry about don't Austin, TX happen. -- Watchman Examiner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Dec 31 6:53:49 1999 Delivered-To: freebsd-stable@freebsd.org Received: from inbox.org (inbox.org [216.22.145.8]) by hub.freebsd.org (Postfix) with ESMTP id 3F33614FA1; Fri, 31 Dec 1999 06:53:47 -0800 (PST) (envelope-from bsd@inbox.org) Received: from localhost (bsd@localhost) by inbox.org (8.9.3/8.9.3) with SMTP id JAA02463; Fri, 31 Dec 1999 09:53:49 -0500 (EST) Date: Fri, 31 Dec 1999 09:53:49 -0500 (EST) From: "Mr. K." To: Mike Smith Cc: stable@freebsd.org Subject: Re: Panic: Out of mbuf clusters In-Reply-To: <199912310622.WAA00554@mass.cdrom.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, 30 Dec 1999, Mike Smith wrote: > > OK, so I raised NMBCLUSTERS to 4096, and installed a second freebsd-stable > > box also with NMBCLUSTERS at 4096, and I managed to have them both panic > > at the same time (unfortunately, only one of them gave me a crash dump). > > But anyway, here is the stack trace, hopefully someone can tell me if this > > is the same as the known problem, and whether 4.0 would fix it. > > Again, 4096 is (obviously) not high enough. No, upgrading to 4.x won't > "fix" your problem. The panic is telling you that you _have_not_ tuned > the system correctly. > 4096 _is_ high enough for what I want. Consider a web company who gets 5Mbps of transfer request 99.9% of the time and 1000Mbps of transfer request 0.1% of the time. Would you tell them that a 10Mbps internet connection is (obviously) not high enough? Would you consider it a bug if their machine rebooted every time they got more than 10Mbps in requests? Consider cdrom.com. Would you consider it a bug if freebsd rebooted every time they received 5001 simultaneous connection requests and tell them to tune their FTP server correctly? How am I supposed to test my system, both hardware and software, if I can't push them to their limits? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Dec 31 7:11:45 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.rdc1.ct.home.com (ha1.rdc1.ct.home.com [24.2.0.66]) by hub.freebsd.org (Postfix) with ESMTP id 565F815176 for ; Fri, 31 Dec 1999 07:11:44 -0800 (PST) (envelope-from tsikora@home.com) Received: from home.com ([24.2.168.186]) by mail.rdc1.ct.home.com (InterMail v4.01.01.07 201-229-111-110) with ESMTP id <19991231151143.UJYK9446.mail.rdc1.ct.home.com@home.com> for ; Fri, 31 Dec 1999 07:11:43 -0800 Message-ID: <386CC7B6.F99C1E2D@home.com> Date: Fri, 31 Dec 1999 10:11:50 -0500 From: Ted Sikora Reply-To: tsikora@powerusersbbs.com Organization: Jtl Development X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.3.34 i686) X-Accept-Language: en-US,en-GB MIME-Version: 1.0 To: "freebsd-stable@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 unsubscribe freebsd-ports To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Dec 31 7:45:24 1999 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 B9E0514DA1 for ; Fri, 31 Dec 1999 07:45:21 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id HAA29763; Fri, 31 Dec 1999 07:45:20 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id HAA40473; Fri, 31 Dec 1999 07:45:19 -0800 (PST) (envelope-from jdp@polstra.com) Date: Fri, 31 Dec 1999 07:45:19 -0800 (PST) Message-Id: <199912311545.HAA40473@vashon.polstra.com> To: bob@pmr.com Subject: Re: Host command output changed in bind 8.2.2p5 In-Reply-To: <19991231083842.A10723@luke.immure.com> References: <19991231083842.A10723@luke.immure.com> Organization: Polstra & Co., Seattle, WA Cc: stable@freebsd.org Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <19991231083842.A10723@luke.immure.com>, Bob Willcox wrote: > I have noticed that the host command no longer produces the same output > as it did prior to the bind 8.2.2p5 import to 3.4. > > For machines with an MX record prior to bind 8.2.2p5 I used to get: > > bob@obiwan-p4 /home/bob> host umd1.umd.edu > umd1.umd.edu is a nickname for haven.umd.edu > haven.umd.edu has address 128.8.10.6 > haven.umd.edu mail is handled (pri=4) by haven.umd.edu > > But now on a recently upgraded 3.4-stable system I get: > > bob@luke:p6 /home/bob> host umd1.umd.edu > umd1.umd.edu is a nickname for haven.umd.edu > haven.umd.edu has address 128.8.10.6 > haven.umd.edu has address 128.8.10.6 Yep, I just noticed the same thing yesterday. It's broken, I'd say. (Same story in -current). 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 Fri Dec 31 8:11:29 1999 Delivered-To: freebsd-stable@freebsd.org Received: from kci.kciLink.com (kci.kciLink.com [204.117.82.1]) by hub.freebsd.org (Postfix) with ESMTP id EA27714E52; Fri, 31 Dec 1999 08:11:25 -0800 (PST) (envelope-from khera@kciLink.com) Received: from onceler.kcilink.com (onceler.kciLink.com [204.117.82.2]) by kci.kciLink.com (Postfix) with ESMTP id B3417E8AF; Fri, 31 Dec 1999 11:11:22 -0500 (EST) Received: (from khera@localhost) by onceler.kcilink.com (8.9.3/8.9.3) id LAA39695; Fri, 31 Dec 1999 11:11:22 -0500 (EST) (envelope-from khera@kci.kcilink.com) From: Vivek Khera MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14444.54698.604479.105360@onceler.kcilink.com> Date: Fri, 31 Dec 1999 11:11:22 -0500 (EST) To: William Woods Cc: freebsd-questions@freebsd.org, freebsd-stable@freebsd.org Subject: Re: StarOffice5 problems.... In-Reply-To: References: X-Mailer: VM 6.72 under 21.1 (patch 8) "Bryce Canyon" XEmacs Lucid Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "WW" == William Woods writes: WW> I am useing (trying to anyway) the StarOffice 5 port on a FreeBSD WW> 3.4 system /usr/ports/editors/staroffice5 but its asking for a WW> couple libs: Here is the makefile: I installed without the using the port. It was quite trivial. Once you download and extract the so51a tar file, just do this: env PATH=/usr/compat/linux/bin ./setup when in the installation directory. The only other change I had to make was to put a similar env PATH=... command in the KDE menus for the Setup and SPAdmin thingies. The StarOffice menu item works fine. Also be sure to enable these in your kernel: # for StarOffice/Linux Compat: options "P1003_1B" options "_KPOSIX_PRIORITY_SCHEDULING" options "_KPOSIX_VERSION=199309L" options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Vivek Khera, Ph.D. Khera Communications, Inc. Internet: khera@kciLink.com Rockville, MD +1-301-545-6996 PGP & MIME spoken here http://www.kciLink.com/home/khera/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Dec 31 8:21:37 1999 Delivered-To: freebsd-stable@freebsd.org Received: from jasper.heartland.ab.ca (jasper.heartland.ab.ca [207.107.228.1]) by hub.freebsd.org (Postfix) with ESMTP id 92CC414A29; Fri, 31 Dec 1999 08:21:32 -0800 (PST) (envelope-from dkwiebe@hagenhomes.com) Received: from freebsd.hagens.ab.ca (dyn109.heartland.ab.ca [207.107.228.109]) by jasper.heartland.ab.ca (8.9.0/8.9.0) with ESMTP id JAA23959; Fri, 31 Dec 1999 09:06:37 -0700 (MST) Received: from hagenhomes.com (darren.hagens.ab.ca [10.0.1.3]) by freebsd.hagens.ab.ca (8.9.3/8.9.2) with ESMTP id IAA25808; Fri, 31 Dec 1999 08:31:39 GMT (envelope-from dkwiebe@hagenhomes.com) Message-ID: <386E2954.594D5804@hagenhomes.com> Date: Sat, 01 Jan 2000 09:20:36 -0700 From: Darren Wiebe Organization: Hagen Homes Ltd. X-Mailer: Mozilla 4.61 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: William Woods Cc: freebsd-questions@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: StarOffice5 problems.... References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I will be sending them to you in a seperate e-mail. I guess that those sites must have just died... Does anybody know if it is legal for me to host those replacement files on my own ftp server? I'm not really good at reading licenses... Darren Wiebe dkwiebe@hagenhomes.com William Woods wrote: > > I am useing (trying to anyway) the StarOffice 5 port on a FreeBSD 3.4 system > /usr/ports/editors/staroffice5 but its asking for a couple libs: Here is the > makefile: > > DISTNAME= so51a_lnx_01 > PKGNAME= staroffice-5.1a > CATEGORIES= editors > MASTER_SITES= ftp://ftp.hagenhomes.com/pub/ \ > ftp://ftp.stat.duke.edu/pub/Users/sto/StarOffice51a/ \ > ftp://ftp.stardivision.de/pub/support/so51a/nwspatch/unxlnxi/ \ > ftp://ftp.stardivision.de/pub/support/so51a/db/unxlnxi/ > EXTRACT_SUFX= .tar > DISTFILES= applicat.rdb.gz libofa517li.so libsdb517li.s > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > As you can see, the ftp sites are looking fot ftp.stardivision.de, which no > longer does staroffice. Anyone out there have the libs you can email me? > > I cant find them anywhere.... > > ---------------------------------- > E-Mail: William Woods > Date: 30-Dec-99 > Time: 23:47:45 > FreeBSD 3.4 > On a Laptop......... > ---------------------------------- > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Dec 31 10: 1:23 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.wzrd.com (mail.wzrd.com [206.99.165.3]) by hub.freebsd.org (Postfix) with ESMTP id 6F7D914C59 for ; Fri, 31 Dec 1999 10:01:21 -0800 (PST) (envelope-from danh@wzrd.com) Received: by mail.wzrd.com (Postfix, from userid 91) id B5EEE5D01A; Fri, 31 Dec 1999 13:01:20 -0500 (EST) Subject: Re: Host command output changed in bind 8.2.2p5 In-Reply-To: <199912311545.HAA40473@vashon.polstra.com> from John Polstra at "Dec 31, 1999 7:45:19 am" To: jdp@polstra.com (John Polstra) Date: Fri, 31 Dec 1999 13:01:20 -0500 (EST) Cc: freebsd-stable@freebsd.org X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 1294 Message-Id: <19991231180120.B5EEE5D01A@mail.wzrd.com> From: danh@wzrd.com (Dan Harnett) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG You can get the same output by using 'host -t any [hostname]'. > In article <19991231083842.A10723@luke.immure.com>, > Bob Willcox wrote: > > I have noticed that the host command no longer produces the same output > > as it did prior to the bind 8.2.2p5 import to 3.4. > > > > For machines with an MX record prior to bind 8.2.2p5 I used to get: > > > > bob@obiwan-p4 /home/bob> host umd1.umd.edu > > umd1.umd.edu is a nickname for haven.umd.edu > > haven.umd.edu has address 128.8.10.6 > > haven.umd.edu mail is handled (pri=4) by haven.umd.edu > > > > But now on a recently upgraded 3.4-stable system I get: > > > > bob@luke:p6 /home/bob> host umd1.umd.edu > > umd1.umd.edu is a nickname for haven.umd.edu > > haven.umd.edu has address 128.8.10.6 > > haven.umd.edu has address 128.8.10.6 > > Yep, I just noticed the same thing yesterday. It's broken, I'd say. > (Same story in -current). > > 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 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Dec 31 10: 4:50 1999 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 38EA314C59 for ; Fri, 31 Dec 1999 10:04:48 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id KAA29960; Fri, 31 Dec 1999 10:04:46 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id KAA40908; Fri, 31 Dec 1999 10:04:46 -0800 (PST) (envelope-from jdp@polstra.com) Date: Fri, 31 Dec 1999 10:04:46 -0800 (PST) Message-Id: <199912311804.KAA40908@vashon.polstra.com> To: danh@wzrd.com Subject: Re: Host command output changed in bind 8.2.2p5 In-Reply-To: <19991231180120.B5EEE5D01A@mail.wzrd.com> References: <19991231180120.B5EEE5D01A@mail.wzrd.com> Organization: Polstra & Co., Seattle, WA Cc: stable@freebsd.org Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <19991231180120.B5EEE5D01A@mail.wzrd.com>, Dan Harnett wrote: > You can get the same output by using 'host -t any [hostname]'. Yes, but it is supposed to print the A records and the MX records by default. That's what the man page says. 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 Fri Dec 31 10:55:23 1999 Delivered-To: freebsd-stable@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 7E12A15107; Fri, 31 Dec 1999 10:55:19 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id KAA84956; Fri, 31 Dec 1999 10:54:59 -0800 (PST) (envelope-from dillon) Date: Fri, 31 Dec 1999 10:54:59 -0800 (PST) From: Matthew Dillon Message-Id: <199912311854.KAA84956@apollo.backplane.com> To: Peter Wemm Cc: Tom , freebsd-stable@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: softupdates and debug.max_softdeps References: <19991231004902.01D721CA0@overcee.netplex.com.au> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :FYI: On hub.freebsd.org (the freebsd mailing list server), if we activate :softupdates on the disk containing the postfix spool, the machine reboots :(silently if I recall correctly) within 5 minutes of postfix starting up. : :This is a much smaller system of course, with smaller memory and filesystem :working set. (postfix spool of ~50-80MB, 256MB ram). I thought I'd post :this as a real-use datapoint. :Cheers, :-Peter :-- :Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au :... :Tom wrote: :> Yes, postmark operates on the same file set. I used the following :> postmark settings: :> :> set number 30000 :> set transactions 4000000 :> set size 1500 200000 :... I'm running the postmark test on my 3.x and 4.x test boxes now using a large softupdates partition (33G on each) and large memory (512M and 1G) configuration. The 4.x box seems to have stabilized at around 14MB of KVM, the 3.x box seems to have stabilized at around 9MB of KVM. I'll leave it running for a while to see if there are any memory leaks and then try reducing debug.max_softdeps to see what happens. We are still looking for panic messages. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Dec 31 11:20:48 1999 Delivered-To: freebsd-stable@freebsd.org Received: from shell.webmaster.com (mail.webmaster.com [209.133.28.73]) by hub.freebsd.org (Postfix) with ESMTP id EE8A21561B for ; Fri, 31 Dec 1999 11:20:36 -0800 (PST) (envelope-from davids@webmaster.com) Received: from whenever ([209.133.29.2]) by shell.webmaster.com (Post.Office MTA v3.5.3 release 223 ID# 0-12345L500S10000V35) with SMTP id com; Fri, 31 Dec 1999 11:20:35 -0800 From: "David Schwartz" To: "Brad Knowles" , Cc: Subject: RE: Temperature Findings Date: Fri, 31 Dec 1999 11:20:35 -0800 Message-ID: <000101bf53c4$1cf9c690$021d85d1@youwant.to> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0 Importance: Normal In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > At 10:27 PM -0800 1999/12/30, Mike Smith wrote: > > > The difference has already been explained as a different > instruction mix. > > This should be obvious to anyone that has been in the industry for as > > long as you have. > > It seems to me that you guys are all talking past each other: > > 1. He's mentioned that he runs the same instruction mix > (i.e., two seti@home clients) under both Linux and FreeBSD Yes, Linux before he overclocked and overvoltaged and FreeBSD before. > 2. He's mentioned that he's run FreeBSD in both > uniprocessor > and SMP modes Yes, UP uses HLT, SMP doesn't. With FreeBSD's SMP kernel, both processors are always running full bore. > 3. He's mentioned that he's run FreeBSD SMP with > 3.3 without problems Before he overclocked and overvoltaged. Possibly also before his fan's capacity decreased due to bearing failure or similar. > 4. He's mentioned that the overclocking is a recent > introduction to the issue and the system was overheating before then So he has cooling problems even at normal CPU voltages and frequencies. Obviously, he either has inadequate cooling or he has some defective component in his system that is creating too much heat. > 5. He's also mentioned that this is a chipset which we now > know is not directly supported by the measurement interface, and > therefore the temperature multiples might (or might not) be off Okay, so we can't even trust his data as correctly indicating a temperature problems. So, perhaps we know nothing at all. [snip] > Of course, the fact that everyone is talking past each other is > not surprising, seeing as many of the correspondents are spread > around the globe. There's nothing to explain or analyze. Much of his data comes from unsupported (and unsupportable) configurations. > If I might make a suggestion based on my own recent introduction > to this mailing list -- it really helps if the new poster provides as > much detail as possible and doesn't make any assumptions about how > much they know about the problem based on their decade-plus (or more) > experience, and it really helps if the other people involved give the > guy at least half a break while he tries to explain what weirdo > whacked out thing he's seeing. Seeing an overclocked, overvoltaged SMP system overheat is not exactly weird or whacked out. It's specifically the reason most people do not recommend overclocking or overvoltaging. DS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Dec 31 11:47:15 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail2.uniserve.com (mail2.uniserve.com [204.244.156.7]) by hub.freebsd.org (Postfix) with ESMTP id 7AA7214F3E; Fri, 31 Dec 1999 11:47:11 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca ([204.244.186.218]) by mail2.uniserve.com with smtp (Exim 3.03 #4) id 12480l-0004bV-00; Fri, 31 Dec 1999 11:46:55 -0800 Date: Fri, 31 Dec 1999 11:46:52 -0800 (PST) From: Tom X-Sender: tom@shell.uniserve.ca To: Matthew Dillon Cc: Peter Wemm , freebsd-stable@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: softupdates and debug.max_softdeps In-Reply-To: <199912311854.KAA84956@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 31 Dec 1999, Matthew Dillon wrote: > :FYI: On hub.freebsd.org (the freebsd mailing list server), if we activate > :softupdates on the disk containing the postfix spool, the machine reboots > :(silently if I recall correctly) within 5 minutes of postfix starting up. > : > :This is a much smaller system of course, with smaller memory and filesystem > :working set. (postfix spool of ~50-80MB, 256MB ram). I thought I'd post > :this as a real-use datapoint. > :Cheers, > :-Peter > :-- > :Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au > :... > :Tom wrote: > :> Yes, postmark operates on the same file set. I used the following > :> postmark settings: > :> > :> set number 30000 > :> set transactions 4000000 > :> set size 1500 200000 > :... > > I'm running the postmark test on my 3.x and 4.x test boxes now using > a large softupdates partition (33G on each) and large memory (512M and 1G) > configuration. How many instances of postmark are you running? I used 4 separate instances (you must run them in separate directories). How fast are your disks? I used an external RAID-5 array that appears as single disk to FreeBSD. It is RAID-5, so the performance isn't that great for writing. I think my virtual disk is quite slow. If your system has fast disks, run more instances of postmark. > The 4.x box seems to have stabilized at around 14MB of KVM, the 3.x box > seems to have stabilized at around 9MB of KVM. I'll leave it running > for a while to see if there are any memory leaks and then try reducing > debug.max_softdeps to see what happens. > > We are still looking for panic messages. Well, I lost last nights panic because of fsck complaining about several million unreferenced files. I'm going to log to disk next time. > -Matt > Matthew Dillon > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > > Tom Uniserve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Dec 31 11:50:44 1999 Delivered-To: freebsd-stable@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id A40491557A; Fri, 31 Dec 1999 11:50:40 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id LAA85337; Fri, 31 Dec 1999 11:50:39 -0800 (PST) (envelope-from dillon) Date: Fri, 31 Dec 1999 11:50:39 -0800 (PST) From: Matthew Dillon Message-Id: <199912311950.LAA85337@apollo.backplane.com> To: Tom Cc: Peter Wemm , freebsd-stable@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: softupdates and debug.max_softdeps References: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : How many instances of postmark are you running? I used 4 separate :instances (you must run them in separate directories). Well, you didn't say that! :-) I'm running one. I'll start up another couple to match your test. : How fast are your disks? I used an external RAID-5 array that appears :as single disk to FreeBSD. It is RAID-5, so the performance isn't that :great for writing. I think my virtual disk is quite slow. If your system :has fast disks, run more instances of postmark. Fast. Two striped 18G seacrates on each system 40 MB/sec SCSI bus on one system, 80 MB/sec SCSI bus on the other. : : Well, I lost last nights panic because of fsck complaining about several :million unreferenced files. I'm going to log to disk next time. : :Tom :Uniserve Ach. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Dec 31 12:38: 9 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mass.cdrom.com (castles511.castles.com [208.214.165.75]) by hub.freebsd.org (Postfix) with ESMTP id B525A14FCE; Fri, 31 Dec 1999 12:38:06 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id MAA02795; Fri, 31 Dec 1999 12:43:21 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912312043.MAA02795@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Mr. K." Cc: Mike Smith , stable@freebsd.org Subject: Re: Panic: Out of mbuf clusters In-reply-to: Your message of "Fri, 31 Dec 1999 09:53:49 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 31 Dec 1999 12:43:21 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Thu, 30 Dec 1999, Mike Smith wrote: > > > > OK, so I raised NMBCLUSTERS to 4096, and installed a second freebsd-stable > > > box also with NMBCLUSTERS at 4096, and I managed to have them both panic > > > at the same time (unfortunately, only one of them gave me a crash dump). > > > But anyway, here is the stack trace, hopefully someone can tell me if this > > > is the same as the known problem, and whether 4.0 would fix it. > > > > Again, 4096 is (obviously) not high enough. No, upgrading to 4.x won't > > "fix" your problem. The panic is telling you that you _have_not_ tuned > > the system correctly. > > 4096 _is_ high enough for what I want. Consider a web company who gets > 5Mbps of transfer request 99.9% of the time and 1000Mbps of transfer > request 0.1% of the time. Would you tell them that a 10Mbps internet > connection is (obviously) not high enough? Would you consider it a bug if > their machine rebooted every time they got more than 10Mbps in requests? That would depend on what happened to their business model if/when their bandwidth proved inadequate. If they were eg. serving streaming video, I'd say they needed a better link. > Consider cdrom.com. Would you consider it a bug if freebsd rebooted every > time they received 5001 simultaneous connection requests and tell them to > tune their FTP server correctly? Er, since we _have_ tuned our FTP server correctly, that's somewhat of a silly question to be asking. > How am I supposed to test my system, both hardware and software, if I > can't push them to their limits? You're welcome to push the system to its limit. All you're seeing is that the system is telling you that you've hit it, and how to move that limit further out. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Dec 31 12:38:18 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.rdc1.ct.home.com (ha1.rdc1.ct.home.com [24.2.0.66]) by hub.freebsd.org (Postfix) with ESMTP id 96CB114BC9 for ; Fri, 31 Dec 1999 12:38:12 -0800 (PST) (envelope-from tsikora@home.com) Received: from home.com ([24.2.168.186]) by mail.rdc1.ct.home.com (InterMail v4.01.01.07 201-229-111-110) with ESMTP id <19991231203811.WWGI9446.mail.rdc1.ct.home.com@home.com>; Fri, 31 Dec 1999 12:38:11 -0800 Message-ID: <386D1439.D9AC45BB@home.com> Date: Fri, 31 Dec 1999 15:38:17 -0500 From: Ted Sikora Reply-To: tsikora@powerusersbbs.com Organization: Jtl Development X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.3.34 i686) X-Accept-Language: en-US,en-GB MIME-Version: 1.0 To: "freebsd-stable@FreeBSD.ORG" , Brad Knowles , David Schwartz Subject: Re: Temperature Findings References: <000101bf53c4$1cf9c690$021d85d1@youwant.to> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David Schwartz wrote: > > > At 10:27 PM -0800 1999/12/30, Mike Smith wrote: > > > > > The difference has already been explained as a different > > instruction mix. > > > This should be obvious to anyone that has been in the industry for as > > > long as you have. I am not a kernel programmer and relatively new to FreeBSD (since 3.0-RC) and nobody explained this previously. > > > > It seems to me that you guys are all talking past each other: Giant understatement! > > > > 1. He's mentioned that he runs the same instruction mix > > (i.e., two seti@home clients) under both Linux and FreeBSD > > Yes, Linux before he overclocked and overvoltaged and FreeBSD before. > > > 2. He's mentioned that he's run FreeBSD in both > > uniprocessor > > and SMP modes > > Yes, UP uses HLT, SMP doesn't. With FreeBSD's SMP kernel, both processors > are always running full bore. > > > 3. He's mentioned that he's run FreeBSD SMP with > > 3.3 without problems YES 3.3 runs cool w/ or w/o a SMP kernel. > > Before he overclocked and overvoltaged. Possibly also before his fan's > capacity decreased due to bearing failure or similar. The fan's are fine. The case is a custom server design *with* a panel mounted digital display for the TEMP readings from the Winbond W83782D/W83783S IC mounted on the motherboard. The readings are taken right from the systems MB routed through the systems bios. It is independant of the OS installed. I had a technician verify the voltage readings and case temperature before I posted with this problem. I verified it again myself after being accused of presenting false or inaccurate data. > > > 4. He's mentioned that the overclocking is a recent > > introduction to the issue and the system was overheating before then I only overclocked it 3 days prior. The increase in temp was nominal only 3-5 degrees so really it had no bearing on this. > > So he has cooling problems even at normal CPU voltages and frequencies. No problems just much higher than before or compared to Linux SMP. The FreeBSD Uni kernel is fine. It is only with the SMP kernel in 3.4. > Obviously, he either has inadequate cooling or he has some defective > component in his system that is creating too much heat. > > > 5. He's also mentioned that this is a chipset which we now > > know is not directly supported by the measurement interface, and > > therefore the temperature multiples might (or might not) be off There are no multiples I was not using the OS measurement tools. I was using the MB/case display and the system bios for readings. I only used lmmon after I was told to. > > Okay, so we can't even trust his data as correctly indicating a temperature > problems. So, perhaps we know nothing at all. > > [snip] > > Of course, the fact that everyone is talking past each other is > > not surprising, seeing as many of the correspondents are spread > > around the globe. > > There's nothing to explain or analyze. Much of his data comes from > unsupported (and unsupportable) configurations. > > > If I might make a suggestion based on my own recent introduction > > to this mailing list -- it really helps if the new poster provides as > > much detail as possible and doesn't make any assumptions about how > > much they know about the problem based on their decade-plus (or more) > > experience, and it really helps if the other people involved give the > > guy at least half a break while he tries to explain what weirdo > > whacked out thing he's seeing. > > Seeing an overclocked, overvoltaged SMP system overheat is not exactly > weird or whacked out. It's specifically the reason most people do not > recommend overclocking or overvoltaging. > That had nothing to do with the issue at hand. (Whether overclocked or normal it's hotter.) I wanted to know if you (FreeBSD) was aware that the SMP kernel runs quite a bit hotter than normal and that the Linux SMP kernel is cooler(Why?). Is this normal or a problem? That's all I wanted to know.(and everyone went for the juggler.) Regards, -- Ted Sikora Jtl Development Group tsikora@powerusersbbs.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Dec 31 13: 7: 5 1999 Delivered-To: freebsd-stable@freebsd.org Received: from kot.ne.mediaone.net (kot.ne.mediaone.net [24.218.15.190]) by hub.freebsd.org (Postfix) with ESMTP id C908E14F46 for ; Fri, 31 Dec 1999 13:07:03 -0800 (PST) (envelope-from mi@kot.ne.mediaone.net) Received: from rtfm.newton (rtfm.newton [10.10.0.1]) by kot.ne.mediaone.net (8.9.3/8.9.1) with ESMTP id QAA70302 for ; Fri, 31 Dec 1999 16:07:02 -0500 (EST) From: Mikhail Teterin X-Relay-IP: 10.10.0.1 Received: (from mi@localhost) by rtfm.newton (8.9.3/8.9.3) id QAA09713 for stable@freebsd.org; Fri, 31 Dec 1999 16:07:02 -0500 (EST) (envelope-from mi@kot.ne.mediaone.net) Message-Id: <199912312107.QAA09713@rtfm.newton> Subject: Re: Panic: Out of mbuf clusters In-Reply-To: <199912312043.MAA02795@mass.cdrom.com> from Mike Smith at "Dec 31, 1999 12:43:21 pm" To: stable@freebsd.org Date: Fri, 31 Dec 1999 16:07:02 -0500 (EST) X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli" How am I supposed to test my system, both hardware and software, if I => can't push them to their limits? = =You're welcome to push the system to its limit. All you're seeing is =that the system is telling you that you've hit it, and how to move that =limit further out. With all due respect, it should not require a reboot for this... -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Dec 31 14: 6:15 1999 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 B6ED214D8A; Fri, 31 Dec 1999 14:06:08 -0800 (PST) (envelope-from Cy.Schubert@uumail.gov.bc.ca) Received: (from daemon@localhost) by point.osg.gov.bc.ca (8.8.7/8.8.8) id NAA25830; Fri, 31 Dec 1999 13:59:31 -0800 Received: from passer.osg.gov.bc.ca(142.32.110.29) via SMTP by point.osg.gov.bc.ca, id smtpda25828; Fri Dec 31 13:59:30 1999 Received: (from uucp@localhost) by passer.osg.gov.bc.ca (8.9.3/8.9.1) id NAA40759; Fri, 31 Dec 1999 13:59:29 -0800 (PST) Received: from cwsys9.cwsent.com(10.2.2.1), claiming to be "cwsys.cwsent.com" via SMTP by passer9.cwsent.com, id smtpdV40749; Fri Dec 31 13:58:52 1999 Received: (from uucp@localhost) by cwsys.cwsent.com (8.9.3/8.9.1) id NAA79182; Fri, 31 Dec 1999 13:58:51 -0800 (PST) Message-Id: <199912312158.NAA79182@cwsys.cwsent.com> Received: from localhost.cwsent.com(127.0.0.1), claiming to be "cwsys" via SMTP by localhost.cwsent.com, id smtpdd79178; Fri Dec 31 13:58:37 1999 X-Mailer: exmh version 2.1.1 10/15/1999 Reply-To: Cy Schubert - ITSD Open Systems Group From: Cy Schubert - ITSD Open Systems Group X-OS: FreeBSD 3.4-RELEASE X-Sender: cy To: Vivek Khera Cc: William Woods , freebsd-questions@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: StarOffice5 problems.... In-reply-to: Your message of "Fri, 31 Dec 1999 11:11:22 EST." <14444.54698.604479.105360@onceler.kcilink.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 31 Dec 1999 13:58:37 -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <14444.54698.604479.105360@onceler.kcilink.com>, Vivek Khera writes: > >>>>> "WW" == William Woods writes: > > WW> I am useing (trying to anyway) the StarOffice 5 port on a FreeBSD > WW> 3.4 system /usr/ports/editors/staroffice5 but its asking for a > WW> couple libs: Here is the makefile: > > I installed without the using the port. It was quite trivial. Once > you download and extract the so51a tar file, just do this: > > env PATH=/usr/compat/linux/bin ./setup Beter yet: # /compat/linux/bin/bash # ./setup > > when in the installation directory. The only other change I had to > make was to put a similar env PATH=... command in the KDE menus for > the Setup and SPAdmin thingies. The StarOffice menu item works fine. Or change the first line of the soffice script to: #!/compat/linux/bin/sh Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 Sun/DEC Team, UNIX Group Internet: Cy.Schubert@uumail.gov.bc.ca ITSD Province of BC "e**(i*pi)+1=0" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Dec 31 14:24:41 1999 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 796C115600 for ; Fri, 31 Dec 1999 14:24:39 -0800 (PST) (envelope-from bright@wintelcom.net) Received: from localhost (bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) with ESMTP id OAA19772; Fri, 31 Dec 1999 14:47:05 -0800 (PST) Date: Fri, 31 Dec 1999 14:47:05 -0800 (PST) From: Alfred Perlstein To: Mikhail Teterin Cc: stable@FreeBSD.ORG Subject: Re: Panic: Out of mbuf clusters In-Reply-To: <199912312107.QAA09713@rtfm.newton> 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, 31 Dec 1999, Mikhail Teterin wrote: > Mike Smith once stated: > > => How am I supposed to test my system, both hardware and software, if I > => can't push them to their limits? > = > =You're welcome to push the system to its limit. All you're seeing is > =that the system is telling you that you've hit it, and how to move that > =limit further out. > > With all due respect, it should not require a reboot for this... send-pr will allow you to attach diffs. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Dec 31 14:28:22 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mass.cdrom.com (castles511.castles.com [208.214.165.75]) by hub.freebsd.org (Postfix) with ESMTP id 043DD14F05 for ; Fri, 31 Dec 1999 14:28:20 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id OAA03103; Fri, 31 Dec 1999 14:33:36 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912312233.OAA03103@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Mikhail Teterin Cc: stable@freebsd.org Subject: Re: Panic: Out of mbuf clusters In-reply-to: Your message of "Fri, 31 Dec 1999 16:07:02 EST." <199912312107.QAA09713@rtfm.newton> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 31 Dec 1999 14:33:36 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Mike Smith once stated: > > => How am I supposed to test my system, both hardware and software, if I > => can't push them to their limits? > = > =You're welcome to push the system to its limit. All you're seeing is > =that the system is telling you that you've hit it, and how to move that > =limit further out. > > With all due respect, it should not require a reboot for this... You are invited to submit code fixes to work around this; it's a long-standing BSD limitation that we'd all love to be rid of. Until then, can we leave off the "it would be nice if", and just deal with the way things are? -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Dec 31 14:44:22 1999 Delivered-To: freebsd-stable@freebsd.org Received: from paradox.nexuslabs.com (cc718001-a.vron1.nj.home.com [24.11.70.21]) by hub.freebsd.org (Postfix) with ESMTP id 255FE14E95; Fri, 31 Dec 1999 14:44:20 -0800 (PST) (envelope-from cyouse@paradox.nexuslabs.com) Received: from localhost (cyouse@localhost) by paradox.nexuslabs.com (8.9.3/8.9.3) with ESMTP id XAA79514; Fri, 31 Dec 1999 23:06:42 -0500 (EST) (envelope-from cyouse@paradox.nexuslabs.com) Date: Fri, 31 Dec 1999 23:06:42 -0500 (EST) From: Charles Youse To: Mike Smith Cc: Mikhail Teterin , stable@FreeBSD.ORG Subject: Re: Panic: Out of mbuf clusters In-Reply-To: <199912312233.OAA03103@mass.cdrom.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 Why aren't they dynamically allocated using the kernel memory management routines? This is an honest question - I don't know enough about the kernel to complain. I was wondering what the pitfalls were. Chuck On Fri, 31 Dec 1999, Mike Smith wrote: > > Mike Smith once stated: > > > > => How am I supposed to test my system, both hardware and software, if I > > => can't push them to their limits? > > = > > =You're welcome to push the system to its limit. All you're seeing is > > =that the system is telling you that you've hit it, and how to move that > > =limit further out. > > > > With all due respect, it should not require a reboot for this... > > You are invited to submit code fixes to work around this; it's a > long-standing BSD limitation that we'd all love to be rid of. Until > then, can we leave off the "it would be nice if", and just deal with the > way things are? > > -- > \\ Give a man a fish, and you feed him for a day. \\ Mike Smith > \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org > \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Dec 31 15: 1:18 1999 Delivered-To: freebsd-stable@freebsd.org Received: from shell.webmaster.com (mail.webmaster.com [209.133.28.73]) by hub.freebsd.org (Postfix) with ESMTP id B79C61561E for ; Fri, 31 Dec 1999 15:01:16 -0800 (PST) (envelope-from davids@webmaster.com) Received: from whenever ([209.133.29.2]) by shell.webmaster.com (Post.Office MTA v3.5.3 release 223 ID# 0-12345L500S10000V35) with SMTP id com; Fri, 31 Dec 1999 15:01:15 -0800 From: "David Schwartz" To: , Subject: RE: Temperature Findings Date: Fri, 31 Dec 1999 15:01:15 -0800 Message-ID: <000201bf53e2$f09d7af0$021d85d1@youwant.to> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0 In-Reply-To: <386D1439.D9AC45BB@home.com> X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Importance: Normal Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I wanted to know if you (FreeBSD) was aware that the SMP kernel runs > quite a bit hotter than normal and that the Linux SMP kernel > is cooler(Why?). Is this normal or a problem? The FreeBSD SMP kernel runs all CPUs at full bore all the time, it does not use HLT. Your machine needs to have adequate cooling to tolerate that. DS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Dec 31 15:15:21 1999 Delivered-To: freebsd-stable@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 6C26614C5A; Fri, 31 Dec 1999 15:14:47 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id QAA52138; Fri, 31 Dec 1999 16:14:44 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id QAA18578; Fri, 31 Dec 1999 16:14:44 -0700 (MST) Message-Id: <199912312314.QAA18578@harmony.village.org> To: Charles Youse Subject: Re: Panic: Out of mbuf clusters Cc: Mike Smith , Mikhail Teterin , stable@FreeBSD.ORG In-reply-to: Your message of "Fri, 31 Dec 1999 23:06:42 EST." References: Date: Fri, 31 Dec 1999 16:14:44 -0700 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Charles Youse writes: : Why aren't they dynamically allocated using the kernel memory management : routines? Because it is hard to malloc in an interrupt context. It is expensive to do this and on older hardware it was felt that it would be better to have a large enough pool and not have to worry about the hair that doing things dynamically would require. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Dec 31 15:30:49 1999 Delivered-To: freebsd-stable@freebsd.org Received: from paradox.nexuslabs.com (cc718001-a.vron1.nj.home.com [24.11.70.21]) by hub.freebsd.org (Postfix) with ESMTP id 733F515674; Fri, 31 Dec 1999 15:30:46 -0800 (PST) (envelope-from cyouse@paradox.nexuslabs.com) Received: from localhost (cyouse@localhost) by paradox.nexuslabs.com (8.9.3/8.9.3) with ESMTP id XAA79594; Fri, 31 Dec 1999 23:53:05 -0500 (EST) (envelope-from cyouse@paradox.nexuslabs.com) Date: Fri, 31 Dec 1999 23:53:05 -0500 (EST) From: Charles Youse To: Warner Losh Cc: Mike Smith , Mikhail Teterin , stable@FreeBSD.ORG Subject: Re: Panic: Out of mbuf clusters In-Reply-To: <199912312314.QAA18578@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 Perhaps, then, it would be best to monitor the number of free clusters and when it hits a low watermark, to allocate more - perhaps by flagging an AST to obviate allocating clusters from within an interrupt context. Stated more specifically, the mbuf management routines, which can be called in an interrupt context, should be responsible for monitoring the levels and triggering the AST. The AST handler's job would be to stay ahead of the game to prevent interrupt handlers from digging the cluster-well dry (which would still result in a panic). A certain part of my instincts tell me that this is a dirty hack, I don't think it's possible to devise a scheme based on this idea that could be proven [mathematically] not to result in a panic under certain conditions. On the other hand, I think if the allocator is smart enough it can probably cover most of the real-world cases without being a memory hog. Comments? Chuck On Fri, 31 Dec 1999, Warner Losh wrote: > In message Charles Youse writes: > : Why aren't they dynamically allocated using the kernel memory management > : routines? > > Because it is hard to malloc in an interrupt context. It is expensive > to do this and on older hardware it was felt that it would be better > to have a large enough pool and not have to worry about the hair that > doing things dynamically would require. > > Warner > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Dec 31 16:22: 5 1999 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 16785156EF; Fri, 31 Dec 1999 16:22:02 -0800 (PST) (envelope-from bright@wintelcom.net) Received: from localhost (bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) with ESMTP id QAA22165; Fri, 31 Dec 1999 16:44:41 -0800 (PST) Date: Fri, 31 Dec 1999 16:44:41 -0800 (PST) From: Alfred Perlstein To: Charles Youse Cc: Warner Losh , Mike Smith , Mikhail Teterin , stable@FreeBSD.ORG Subject: Re: Panic: Out of mbuf clusters In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 31 Dec 1999, Charles Youse wrote: > > Perhaps, then, it would be best to monitor the number of free clusters > and when it hits a low watermark, to allocate more - perhaps by flagging > an AST to obviate allocating clusters from within an interrupt context. > > Stated more specifically, the mbuf management routines, which can be > called in an interrupt context, should be responsible for monitoring the > levels and triggering the AST. The AST handler's job would be to stay > ahead of the game to prevent interrupt handlers from digging the > cluster-well dry (which would still result in a panic). > > A certain part of my instincts tell me that this is a dirty hack, I don't > think it's possible to devise a scheme based on this idea that could be > proven [mathematically] not to result in a panic under certain conditions. > On the other hand, I think if the allocator is smart enough it can > probably cover most of the real-world cases without being a memory hog. > > Comments? One of the problems with all such schemes is that you then have a chance to wire down all the kernel memory with network buffers, It's a bit bogus, but at the same time better to impose a limit that specifically tells you what's hogging what and why. Also, mbufs are allocated from a special pool where a fixed size allows certain 'tricks' to work that the network stack depends on. Although new ideas are welcome it's really better for you to research the current system before giving suggestions that are unfortunatly not feasable. Grab a copy of 'design and implementation' and trod through the sources, people have and will improve the system, but it takes more research. -Alfred > > Chuck > > On Fri, 31 Dec 1999, Warner Losh wrote: > > > In message Charles Youse writes: > > : Why aren't they dynamically allocated using the kernel memory management > > : routines? > > > > Because it is hard to malloc in an interrupt context. It is expensive > > to do this and on older hardware it was felt that it would be better > > to have a large enough pool and not have to worry about the hair that > > doing things dynamically would require. > > > > Warner > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > -Alfred Perlstein - [bright@rush.net|alfred@freebsd.org] Wintelcom systems administrator and programmer - http://www.wintelcom.net/ [bright@wintelcom.net] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Dec 31 16:39:32 1999 Delivered-To: freebsd-stable@freebsd.org Received: from set.spradley.org (set.spradley.tmi.net [207.170.107.99]) by hub.freebsd.org (Postfix) with ESMTP id F02FC1567F for ; Fri, 31 Dec 1999 16:39:21 -0800 (PST) (envelope-from tsprad@set.spradley.org) Received: from set.spradley.org (localhost.spradley.tmi.net [127.0.0.1]) by set.spradley.org (8.9.3/8.9.2) with ESMTP id SAA08707; Fri, 31 Dec 1999 18:39:18 -0600 (CST) (envelope-from tsprad@set.spradley.org) Message-Id: <200001010039.SAA08707@set.spradley.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: tsikora@powerusersbbs.com Cc: "freebsd-stable@FreeBSD.ORG" Subject: Re: Temperature Findings In-reply-to: Your message of "Fri, 31 Dec 1999 15:38:17 EST." <386D1439.D9AC45BB@home.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 31 Dec 1999 18:39:17 -0600 From: Ted Spradley Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > The fan's are fine. The case is a custom server design *with* a panel > mounted digital display for the TEMP readings from the Winbond > W83782D/W83783S IC mounted on the motherboard. The readings are taken > right from the systems MB routed through the systems bios. It is > independant of the OS installed. I had a technician verify the voltage > readings and case temperature before I posted with this problem. I > verified it again myself after being accused of presenting false or > inaccurate data. I hope that you now realize that you could have saved us all a lot of confusion and wasted cycles by telling us this in the first place, and maybe mentioning that you could feel how much hotter it is when you put your hand near the exhaust fan. I don't have any SMP systems, but I'm anxiously waiting to find out where that difference is coming from. I just can't imagine what the software could possibly do that would make that much difference, unless it's somehow shorting two power supply voltages together inadvertently. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Dec 31 16:44: 1 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mass.cdrom.com (castles511.castles.com [208.214.165.75]) by hub.freebsd.org (Postfix) with ESMTP id 33AFC14E95; Fri, 31 Dec 1999 16:43:58 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id QAA03440; Fri, 31 Dec 1999 16:49:08 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200001010049.QAA03440@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Charles Youse Cc: Warner Losh , Mike Smith , Mikhail Teterin , stable@FreeBSD.ORG Subject: Re: Panic: Out of mbuf clusters In-reply-to: Your message of "Fri, 31 Dec 1999 23:53:05 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 31 Dec 1999 16:49:08 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Perhaps, then, it would be best to monitor the number of free clusters > and when it hits a low watermark, to allocate more - perhaps by flagging > an AST to obviate allocating clusters from within an interrupt context. This sounds nice until I ask you how you plan to deal with an interrupt storm. 8( At some point, you need to decide what to do when you run out of resources. Just "allocating from a larger pool" has other, massive shortcomings; it allows the networking stack to tie up resources that may be needed by other parts of the system (look at the current discussion inre: massive resource overconsumption by the softupdates code for a contrasting example). Right now, the mbuf management code simply bails out when things get too hard, and most of the code that calls it doesn't deal with that very well. Improving the state of play is a slow process that doesn't lend itself well to 10-minute back-of-the-envelope suggestions (no offence meant). -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Dec 31 17:20: 7 1999 Delivered-To: freebsd-stable@freebsd.org Received: from ns.itga.com.au (ns.itga.com.au [202.53.40.210]) by hub.freebsd.org (Postfix) with ESMTP id 72F8814D17 for ; Fri, 31 Dec 1999 17:20:00 -0800 (PST) (envelope-from gnb@itga.com.au) Received: from lightning.itga.com.au (lightning.itga.com.au [192.168.71.20]) by ns.itga.com.au (8.9.3/8.9.3) with ESMTP id MAA02458 for ; Sat, 1 Jan 2000 12:19:56 +1100 (EST) (envelope-from gnb@itga.com.au) Received: from lightning.itga.com.au (lightning.itga.com.au [192.168.71.20]) by lightning.itga.com.au (8.9.3/8.9.3) with ESMTP id MAA21570; Sat, 1 Jan 2000 12:19:55 +1100 (EST) Message-Id: <200001010119.MAA21570@lightning.itga.com.au> X-Mailer: exmh version 2.0.1 12/23/97 From: Gregory Bond To: stable@freebsd.org Subject: fwiw: I survived Y2k... Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 01 Jan 2000 12:19:55 +1100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG with a bunch of 3.x machines (from 3.2-RELEASE to -STABLE) with no problems. [Nor, I should add, did we have any strife with our Solaris machines] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Dec 31 17:57: 7 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.cybcon.com (mail.cybcon.com [216.190.188.5]) by hub.freebsd.org (Postfix) with ESMTP id DED6714C09; Fri, 31 Dec 1999 17:57:01 -0800 (PST) (envelope-from freebsd@cybcon.com) Received: from laptop.cybcon.com (william@usr1-38.cybcon.com [205.147.75.39]) by mail.cybcon.com (8.9.3/8.9.3) with ESMTP id NAA17576; Fri, 31 Dec 1999 13:36:04 -0800 (PST) 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: <386E2954.594D5804@hagenhomes.com> Date: Fri, 31 Dec 1999 13:37:47 -0800 (PST) From: William Woods To: Darren Wiebe Subject: Re: StarOffice5 problems.... Cc: freebsd-stable@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks, I should have searched the web before asking, but I found them pn an ftp site in russia !! Go figure. But thanks for sending them. On 01-Jan-00 Darren Wiebe wrote: > I will be sending them to you in a seperate e-mail. I guess that those > sites must have just died... Does anybody know if it is legal for me to > host those replacement files on my own ftp server? I'm not really good > at reading licenses... > > Darren Wiebe > dkwiebe@hagenhomes.com > > William Woods wrote: >> >> I am useing (trying to anyway) the StarOffice 5 port on a FreeBSD 3.4 system >> /usr/ports/editors/staroffice5 but its asking for a couple libs: Here is the >> makefile: >> >> DISTNAME= so51a_lnx_01 >> PKGNAME= staroffice-5.1a >> CATEGORIES= editors >> MASTER_SITES= ftp://ftp.hagenhomes.com/pub/ \ >> ftp://ftp.stat.duke.edu/pub/Users/sto/StarOffice51a/ \ >> ftp://ftp.stardivision.de/pub/support/so51a/nwspatch/unxlnxi/ >> \ >> ftp://ftp.stardivision.de/pub/support/so51a/db/unxlnxi/ >> EXTRACT_SUFX= .tar >> DISTFILES= applicat.rdb.gz libofa517li.so libsdb517li.s >> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ >> >> As you can see, the ftp sites are looking fot ftp.stardivision.de, which no >> longer does staroffice. Anyone out there have the libs you can email me? >> >> I cant find them anywhere.... >> >> ---------------------------------- >> E-Mail: William Woods >> Date: 30-Dec-99 >> Time: 23:47:45 >> FreeBSD 3.4 >> On a Laptop......... >> ---------------------------------- >> >> To Unsubscribe: send mail to majordomo@FreeBSD.org >> with "unsubscribe freebsd-questions" in the body of the message > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message ---------------------------------- E-Mail: William Woods Date: 31-Dec-99 Time: 13:09:01 FreeBSD 3.4 On a Laptop......... ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message