From owner-freebsd-stable Sun Mar 21 2:56:28 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mta2.iol.it (mta2.iol.it [195.210.91.152]) by hub.freebsd.org (Postfix) with ESMTP id 8067815148 for ; Sun, 21 Mar 1999 02:56:24 -0800 (PST) (envelope-from albertodegiorgi@iol.it) Received: from oemcomputer ([212.52.72.243]) by mta2.iol.it (Netscape Messaging Server 3.6) with SMTP id AAB150A for ; Sun, 21 Mar 1999 11:56:03 +0100 Message-ID: <002601be7389$aab428c0$f34834d4@oemcomputer> From: "Alberto De Giorgi" To: Subject: FreeBSD vs. kppp Date: Sun, 21 Mar 1999 11:54:05 +0100 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 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 Hallo list . Does anybody know if there is some sort of incompatibility between FreeBSD 2.2.8 and the kppp utility that comes with kde ? bye MDG To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Mar 21 3:31:20 1999 Delivered-To: freebsd-stable@freebsd.org Received: from freebie.dcfinc.com (freebie.dcfinc.com [138.113.5.128]) by hub.freebsd.org (Postfix) with ESMTP id 1922514BE2 for ; Sun, 21 Mar 1999 03:31:18 -0800 (PST) (envelope-from chad@freebie.dcfinc.com) Received: (from chad@localhost) by freebie.dcfinc.com (8.8.7/8.8.3a) id EAA04488 for stable@FreeBSD.org; Sun, 21 Mar 1999 04:30:59 -0700 (MST) From: "Chad R. Larson" Message-Id: <199903211130.EAA04488@freebie.dcfinc.com> Subject: make buildworld fails (fwd) To: stable@FreeBSD.org Date: Sun, 21 Mar 1999 04:30:59 -0700 (MST) Reply-To: chad@dcfinc.com X-unexpected: The Spanish Inquisition X-Mailer: ELM [version 2.4ME+ PL22 (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 Following up my own message. +--------------- | This is on a 2.2.8-RELEASE system, cvsup'd to RELENG_2_2 freshly | today. Make buildworld progresses to about 4/5ths done and then | errors with: | -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= | cc -nostdinc -O2 -pipe -I/usr/src/gnu/usr.bin/gdb/gdb -I/usr/obj/usr/src/tmp/usr/include/readline -I/usr/src/gnu/usr.bin/gdb/gdb/../bfd -DNO_MMALLOC -I/usr/src/gnu/usr.bin/gdb/gdb/../../../../contrib/gdb/include/. -I/usr/src/gnu/usr.bin/gdb/gdb/../../../../contrib/gdb/gdb/. -I/usr/src/gnu/usr.bin/gdb/gdb/../../../../contrib/gdb/bfd/. -I/usr/src/gnu/usr.bin/gdb/gdb/../../../../contrib/gdb/libiberty/. -I/usr/src/gnu/usr.bin/gdb/gdb/../../../../contrib/gdb/gdb/config/. -DHAVE_CONFIG_H -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/gnu/usr.bin/gdb/gdb/../../../../contrib/gdb/gdb/objfiles.c | /usr/src/gnu/usr.bin/gdb/gdb/../../../../contrib/gdb/gdb/objfiles.c: In function `add_to_objfile_sections': | /usr/src/gnu/usr.bin/gdb/gdb/../../../../contrib/gdb/gdb/objfiles.c:90: `kernel_debugging' undeclared (first use this function) | /usr/src/gnu/usr.bin/gdb/gdb/../../../../contrib/gdb/gdb/objfiles.c:90: (Each undeclared identifier is reported only once | /usr/src/gnu/usr.bin/gdb/gdb/../../../../contrib/gdb/gdb/objfiles.c:90: for each function it appears in.) | *** Error code 1 | | Stop. | *** Error code 1 | | Stop. | -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= | I removed all of /usr/obj and tried again with the same results. +--------------- Looking in the code, it seemed that "objfiles.c" needed to include "nm.h" to get the definition of "kernel_debugging". So I deleted it and re-cvsupped to see if the file had changed. It hadn't. That left me believing there had to be some cruft in my source tree. I removed all of /usr/src/contrib, and then cvsup'd again. Way too long later, I did another "make buildworld", which was successful. Anyone understand why/how the source tree could get broken in a way that cvsup didn't catch? -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org chad@anasazi.com 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 Sun Mar 21 3:57: 0 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 9C7C214F8E for ; Sun, 21 Mar 1999 03:56:58 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id UAA07993; Sun, 21 Mar 1999 20:56:54 +0900 (JST) Message-ID: <36F41F71.3F34D172@newsguy.com> Date: Sun, 21 Mar 1999 07:21:37 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Mike Meyer , stable@freebsd.org Subject: Re: Build of 3.1-STABLE failing? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Meyer wrote: > > Actually, I'm aware of all that. The goal is (was?) to upgrade the > utilities. Watching the stable list for hints as to when the kernel > needed to be updated as well - and doing that at that time. > > >From the above, it looks like I shouldn't be tracking -STABLE, but > should be running -RELEASE. Running stable is preferable than release. But the targets are buildworld and installworld. > Just one question - what are "make" and "make install" for, then? For those who know what they are doing. For instance, they can be very handy for developers who know what their modifications are doing or not to the source tree. At the very least, you should have tried "world" before asking the question. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "What happened?" "It moved, sir!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Mar 21 3:58:49 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 4516814D13 for ; Sun, 21 Mar 1999 03:58:40 -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 MAA26062 for freebsd-stable@FreeBSD.ORG; Sun, 21 Mar 1999 12:58:21 +0100 (CET) (envelope-from olli) Date: Sun, 21 Mar 1999 12:58:21 +0100 (CET) From: Oliver Fromme Message-Id: <199903211158.MAA26062@dorifer.heim3.tu-clausthal.de> To: freebsd-stable@FreeBSD.ORG Subject: Re: Problem with "make release" Newsgroups: list.freebsd-stable Organization: Administration Heim 3 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 Brian Somers wrote in list.freebsd-stable: > Have you got a couple of vn devices configured ? I have no idea > why miniperl is complaining, but vn's are required to build the boot > floppies etc. Yes, I have 16 (!) vn devices configured. This doesn't look like a problem with vn devices anyway, because it's not yet trying to build any floppies or CDs, as far as I can tell. It seems to be in the midst of building perl. The strange thing is that perl is also built during a "make buildworld", which works fine without any problems. Regards Oliver > > I tried to do a "make release" in mid February, I tried it a > > few days ago, and I tried it today. It always fails at exactly > > the same point, with the same error message -- it's 100% > > reproducible, so it's probably not a hardware problem. > > > > At first I thought that my CVS repository might be broken, > > so I newfs'ed it and cvsup'ed a fresh copy -- same thing. > > > > Interestingly, "make buildworld" works perfectly fine (takes > > about 1 hour), but "make release" fails after about 1.5 hours. > > I'm probably doing something wrong, because it seems to work > > for others, but WTF am I doing wrong?!? > > > > [...] > > ===> gnu/usr.bin/perl > > ===> gnu/usr.bin/perl/libperl > > ===> gnu/usr.bin/perl/miniperl > > sh config_h.sh > > Extracting config.h (with variable substitutions) > > cc -nostdinc -O -pipe -I/usr/src/gnu/usr.bin/perl/miniperl/../../../../contrib/perl5 -I/usr/obj/usr/src/gnu/usr.bin/perl/miniperl -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/gnu/usr.bin/perl/miniperl/../../../../contrib/perl5/miniperlmain.c > > cc -nostdinc -O -pipe -I/usr/src/gnu/usr.bin/perl/miniperl/../../../../contrib/perl5 -I/usr/obj/usr/src/gnu/usr.bin/perl/miniperl -I/usr/obj/usr/src/tmp/usr/include -static -o miniperl miniperlmain.o -lperl -lm -lcrypt > > ===> gnu/usr.bin/perl/perl > > find: build: No such file or directory > > find: build: No such file or directory > > sh config_h.sh > > Extracting config.h (with variable substitutions) > > sh writemain.sh > > Extracting writemain (with variable substitutions) > > sh writemain lib/auto/DynaLoader/DynaLoader.a > perlmain.c > > cc -nostdinc -O -pipe -I/usr/src/gnu/usr.bin/perl/perl/../../../../contrib/perl5 -I/usr/obj/usr/src/gnu/usr.bin/perl/perl -I/usr/obj/usr/src/tmp/usr/include -c perlmain.c > > miniperl /usr/src/gnu/usr.bin/perl/perl/../../../../contrib/perl5/configpm Config.pm Porting/Glossary myconfig config.sh > > cd lib ; ln -sf ../Config.pm > > miniperl -I/usr/obj/usr/src/gnu/usr.bin/perl/perl/lib -e 'use AutoSplit; autosplit_lib_modules(@ARGV)' lib/*.pm lib/*/*.pm > > Can't open perl script "-e": Device not configured > > *** Error code 6 > > > > Stop. > > *** Error code 1 > > > > Stop. > > [...] > > *** Error code 1 > > > > Stop. > > # -- 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 Sun Mar 21 10:39:57 1999 Delivered-To: freebsd-stable@freebsd.org Received: from rrnet.com (rrnet.com [206.11.160.5]) by hub.freebsd.org (Postfix) with ESMTP id 3C13A14EC9 for ; Sun, 21 Mar 1999 10:39:53 -0800 (PST) (envelope-from freebsdstable@rrnet.com) Received: (from freebsdstable@localhost) by rrnet.com (8.8.8/8.8.8) id MAA23000 for freebsd-stable@freebsd.org; Sun, 21 Mar 1999 12:39:32 -0600 (CST) From: Chad Dubuque Message-Id: <199903211839.MAA23000@rrnet.com> Subject: Re: syslogd "fixes" To: freebsd-stable@freebsd.org Date: Sun, 21 Mar 1999 12:39:31 -0600 (CST) In-Reply-To: <199903210058.SAA15530@rrnet.com> from "Chad Dubuque" at Mar 20, 99 06:58:32 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Chad Dubuque wrote: > run syslogd without any options and with "-a 10.1.1.8:*" Obviously, I had been staring at the screen too long. This should be "-a 10.0.0.0/8:*" and now it works fine. Thanks to James E. Housley for pointing out my foolishness. -- Chad Dubuque cdubuque@rrnet.com Fargo, N.D. (USA) Red River Net - Internet Communications http://www.rrnet.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Mar 21 11: 6:40 1999 Delivered-To: freebsd-stable@freebsd.org Received: from phyleus.interlinx.qc.ca (phyleus.interlinx.qc.ca [207.253.145.6]) by hub.freebsd.org (Postfix) with ESMTP id 0FCF014D8D for ; Sun, 21 Mar 1999 11:06:38 -0800 (PST) (envelope-from master@interlinx.qc.ca) Received: from thespider (thespider@023.utc-4.Sherbrooke.InterLinx.qc.ca [207.253.183.43]) by phyleus.interlinx.qc.ca (8.9.1a/8.9.1) with SMTP id OAA27397 for ; Sun, 21 Mar 1999 14:06:19 -0500 Message-ID: <000101be73cd$edde2080$2bb7fdcf@thespider> From: "thespider" To: Subject: I want join Date: Sun, 21 Mar 1999 14:06:28 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hello I want join the freebsd stable mailling list. I using FreebSD like about 1 years ago. It's the best UNIX o/s thx To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Mar 21 11:27:25 1999 Delivered-To: freebsd-stable@freebsd.org Received: from kiev.sovam.com (kiev.sovam.com [194.186.143.7]) by hub.freebsd.org (Postfix) with ESMTP id 12ED414D8D for ; Sun, 21 Mar 1999 11:27:23 -0800 (PST) (envelope-from doka@kiev.sovam.com) Received: from doka (helo=localhost) by kiev.sovam.com with local-esmtp (Exim 2.12 #1) id 10OnsD-0005dO-00; Sun, 21 Mar 1999 21:27:01 +0200 Date: Sun, 21 Mar 1999 21:27:00 +0200 (EET) From: Vladimir Litovka Reply-To: doka@triton.kiev.sovam.com To: thespider Cc: freebsd-stable@FreeBSD.ORG Subject: Re: I want join In-Reply-To: <000101be73cd$edde2080$2bb7fdcf@thespider> 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! On Sun, 21 Mar 1999, thespider wrote: > hello I want join the freebsd stable mailling list. I using FreebSD like > about 1 years ago. It's the best UNIX o/s thx It is OK. You need to send paper, singned by at least two your friends, to Jordan K. Hubbard and if he will confirm, that you really FreeBSD user, he will subscribe you to this mailing ;-) -- Yours sincerely, Vladimir Litovka, hostmaster of Sovam Teleport Kiev To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Mar 21 11:33:14 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mailbox2.ucsd.edu (mailbox2.ucsd.edu [132.239.1.54]) by hub.freebsd.org (Postfix) with ESMTP id D73FA14EA0 for ; Sun, 21 Mar 1999 11:33:13 -0800 (PST) (envelope-from rjdawes@physics.ucsd.edu) Received: from physics.ucsd.edu (physics.ucsd.edu [132.239.69.26]) by mailbox2.ucsd.edu (8.9.1a/8.9.1) with SMTP id LAA18346; Sun, 21 Mar 1999 11:32:24 -0800 (PST) Received: from localhost by physics.ucsd.edu (SMI-8.6/SMI-SVR4) id LAA01990; Sun, 21 Mar 1999 11:30:42 -0800 Date: Sun, 21 Mar 1999 11:30:42 -0800 (PST) From: "Richard J. Dawes" X-Sender: rjdawes@physics Reply-To: Richard Dawes To: Vladimir Litovka Cc: freebsd-stable@FreeBSD.ORG, Oliver Fromme , Vadim Chepkov Subject: Re: Problem with "make release" 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 too had this problem a month or so back. It turns out that setting the COPTS variable in make.conf or with the -D option to include a gcc optimization level no higher than "-O" (same as "-O1"), i.e. NOT "-O2" or "-O3", will allow the build to complete. (At least this is what worked for me...) Good luck! --Rich On Sat, 20 Mar 1999, Vladimir Litovka wrote: > Hello! > > On Sat, 20 Mar 1999, Oliver Fromme wrote: > > > Interestingly, "make buildworld" works perfectly fine (takes > > about 1 hour), > > Today's CVSUP make buildworld fails with this message: > > -------------------------------------------------------------------------- > ===> share/doc/psd/22.rpcgen > touch _stamp.extraobjs > (cd /usr/src/share/doc/psd/22.rpcgen/../../../../lib/libc/rpc/PSD.doc; > groff -mt > ty-char -Tascii -t -ms -o1- > /usr/src/share/doc/psd/22.rpcgen/../../../../lib/lib > c/rpc/PSD.doc/rpcgen.ms) | gzip -cn > paper.ascii.gz > groff: can't find `DESC' file > groff:fatal error: invalid device `ascii' > ===> share/doc/psd/23.rpc > touch _stamp.extraobjs > (cd /usr/src/share/doc/psd/23.rpc/../../../../lib/libc/rpc/PSD.doc; groff > -mtty- > char -Tascii -t -p -ms -o1- > /usr/src/share/doc/psd/23.rpc/../../../../lib/libc/r > pc/PSD.doc/rpc.prog.ms) | gzip -cn > paper.ascii.gz > groff: can't find `DESC' file > groff:fatal error: invalid device `ascii' > *** Error code 3 > > Stop. > *** Error code 1 > > Stop. > *** Error code 1 > -------------------------------------------------------------------------- > > What is this? > > -- > Yours sincerely, > Vladimir Litovka, hostmaster of Sovam Teleport Kiev > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > ======================================== Richard J. Dawes rdawes@ucsd.edu ======================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Mar 21 11:47:24 1999 Delivered-To: freebsd-stable@freebsd.org Received: from kiev.sovam.com (kiev.sovam.com [194.186.143.7]) by hub.freebsd.org (Postfix) with ESMTP id 4383914D6E for ; Sun, 21 Mar 1999 11:47:21 -0800 (PST) (envelope-from doka@kiev.sovam.com) Received: from doka (helo=localhost) by kiev.sovam.com with local-esmtp (Exim 2.12 #1) id 10OoBY-0005ft-00; Sun, 21 Mar 1999 21:47:00 +0200 Date: Sun, 21 Mar 1999 21:47:00 +0200 (EET) From: Vladimir Litovka Reply-To: doka@triton.kiev.sovam.com To: Richard Dawes Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Problem with "make release" 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 Hi! On Sun, 21 Mar 1999, Richard J. Dawes wrote: > I too had this problem a month or so back. It turns out that setting > the COPTS variable in make.conf or with the -D option to include a gcc > optimization level no higher than "-O" (same as "-O1"), i.e. NOT "-O2" > or "-O3", will allow the build to complete. (At least this is what > worked for me...) Good luck! You are right. After I've set everywhere '-O -pipe' buildworld finished without errors. Optimization.... BTW do FreeBSD's team have plans to use egcs as main compiler or no? Or gcc 2.8.x at least... -- Yours sincerely, Vladimir Litovka, hostmaster of Sovam Teleport Kiev To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Mar 21 12:12: 7 1999 Delivered-To: freebsd-stable@freebsd.org Received: from holly.dyndns.org (ip202.houston5.tx.pub-ip.psi.net [38.11.7.202]) by hub.freebsd.org (Postfix) with ESMTP id 870AE150C9 for ; Sun, 21 Mar 1999 12:12:04 -0800 (PST) (envelope-from chris@holly.dyndns.org) Received: (from chris@localhost) by holly.dyndns.org (8.9.3/8.9.2) id OAA04528; Sun, 21 Mar 1999 14:13:21 -0600 (CST) (envelope-from chris) Date: Sun, 21 Mar 1999 14:13:20 -0600 From: Chris Costello To: Vladimir Litovka Cc: freebsd-stable@freebsd.org Subject: Re: I want join Message-ID: <19990321141320.A4517@holly.dyndns.org> Reply-To: chris@calldei.com References: <000101be73cd$edde2080$2bb7fdcf@thespider> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4us In-Reply-To: ; from Vladimir Litovka on Sun, Mar 21, 1999 at 09:27:00PM +0200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Mar 21, 1999, Vladimir Litovka wrote: > Hi! > > On Sun, 21 Mar 1999, thespider wrote: > > > hello I want join the freebsd stable mailling list. I using FreebSD like > > about 1 years ago. It's the best UNIX o/s thx > > It is OK. You need to send paper, singned by at least two your friends, to > Jordan K. Hubbard and if he will confirm, that you really FreeBSD user, he > will subscribe you to this mailing ;-) Don't forget your house, your car, and all of your report cards from grade school! Or you could take the easy, cop-out way and send the following to Majordomo@FreeBSD.ORG: subscribe freebsd-stable with no subject line and no other data in the body. > > -- > Yours sincerely, > Vladimir Litovka, hostmaster of Sovam Teleport Kiev -Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Mar 21 15: 7:29 1999 Delivered-To: freebsd-stable@freebsd.org Received: from guru.phone.net (guru.phone.net [209.157.82.120]) by hub.freebsd.org (Postfix) with SMTP id 298CC14BE2 for ; Sun, 21 Mar 1999 15:07:27 -0800 (PST) (envelope-from mwm@phone.net) Received: (qmail 8514 invoked by uid 100); 21 Mar 1999 23:07:08 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 21 Mar 1999 23:07:08 -0000 Date: Sun, 21 Mar 1999 15:07:08 -0800 (PST) From: Mike Meyer To: stable@freebsd.org Subject: Re: Build of 3.1-STABLE failing? In-Reply-To: <36F41F71.3F34D172@newsguy.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, 21 Mar 1999, Daniel C. Sobral wrote: > Running stable is preferable than release. But the targets are > buildworld and installworld. If you make regular backups of userland, that represents quite a bit of work. Since it rebuilds everything in userland, you wind up dumping all of userland with every backup, so you need to do some kind of special backup after doing an installworld. Putting it all together, that's enough work that I wouldn't bother doing it except every 6-8 weeks. But -RELEASE happens about twice that often. What's the point of tracking -STABLE under those conditions? Of course, part of the reason for tracking -STABLE is I want up-to-date versions of various ports. After all, like most users, I have a computer so I can run the apps, not the OS. But here we're told that the ports tree and the OS are tied together - and you shouldn't try using newer versions of the ports without having the appropriate underlying OS. Given that /usr/ports was one of the reasons I chose FreeBSD, not being able to track that closely is a serious hit. This all points to one of the most serious problems with the current release system - that patches seem to be considered impossible. On commercial OS's, or Linux, you see small distributions that fix a few things in userland (a security hole in Sendmail being a typical example). Fixing that is a simple matter of installing that patch and restarting sendmail on the relevant systems (assuming the patch didn't do that for you). On the other hand, here I see a discussion of doing a "point release" instead of a patch. This means that fixing the problem requires reinstalling the OS for all those systems. Surely, anyone who runs more than a few systems doesn't do this? Unfortunately, I don't have a solution, even ignoring the problem of needing to find extra time to do that work. The main reason for doing this is to see if anyone else has ideas for a solution. > > Just one question - what are "make" and "make install" for, then? > > For those who know what they are doing. > For instance, they can be very handy for developers who know what > their modifications are doing or not to the source tree. You mean - people who go in and edit the userland sources? Nuts - that's one of the reasons I *started* tracking -STABLE. I kept hoping the patches I submitted with pr bin/9429 would show up, as well as some of the ports I've done and submitted. > At the very least, you should have tried "world" before asking the > question. True - it would have avoided a lot of flaming on the list. ; Sun, 21 Mar 1999 16:15:18 -0800 (PST) (envelope-from andrew@squiz.co.nz) Received: from aniwa.sky (localhost [127.0.0.1]) by aniwa.sky (8.9.1a/8.9.1) with ESMTP id DAA21908; Mon, 22 Mar 1999 03:06:27 +1200 (NZST) Message-Id: <199903211506.DAA21908@aniwa.sky> X-Mailer: exmh version 2.0.2 2/24/98 To: "Michael C. Vergallen" Cc: Eddie Irvine , Keith Woodman , freebsd-stable@FreeBSD.ORG Subject: Re: Confusion In-reply-to: Your message of "Sat, 20 Mar 1999 04:36:02 BST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 22 Mar 1999 03:06:27 +1200 From: Andrew McNaughton Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > That is what cvs was invented for .. and that I why I switched all my > machines to FreeBSD when 2.2.6. was released. However I don't just run > cvs on all those machines I have a dedicated box that cvs's all the code > and then builds all the code and runs a number off test scripts that test > all the code used in the production boxes and then sends me a report if > it fails if not I upgrade the production box by mounting it's hd and do a > automtic install then I log in to the production box check if any changes > are required in /etc and reboot the server. My maximum downtime is 5 > minutes per upgrade unless some hardware goes bad but that is not the > fault of FreeBSD. I wonder if this is generic enough that the script should be part of the distribution. Should FreeBSD be distributing scripts for maintaining build systems, testing those build systems, and upgrading production systems from them? Andrew McNaughton -- ----------- Andrew McNaughton andrew@squiz.co.nz http://www.newsroom.co.nz/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Mar 21 16:59:55 1999 Delivered-To: freebsd-stable@freebsd.org Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (Postfix) with SMTP id 40D5214CD1 for ; Sun, 21 Mar 1999 16:59:35 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 10Ot3H-0006Yu-00; Sun, 21 Mar 1999 16:58:47 -0800 Date: Sun, 21 Mar 1999 16:58:44 -0800 (PST) From: Tom X-Sender: tom@shell.uniserve.ca To: Andrew McNaughton Cc: "Michael C. Vergallen" , Eddie Irvine , Keith Woodman , freebsd-stable@FreeBSD.ORG Subject: Re: Confusion In-Reply-To: <199903211506.DAA21908@aniwa.sky> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 22 Mar 1999, Andrew McNaughton wrote: > > That is what cvs was invented for .. and that I why I switched all my > > machines to FreeBSD when 2.2.6. was released. However I don't just run > > cvs on all those machines I have a dedicated box that cvs's all the code > > and then builds all the code and runs a number off test scripts that test > > all the code used in the production boxes and then sends me a report if > > it fails if not I upgrade the production box by mounting it's hd and do a > > automtic install then I log in to the production box check if any changes > > are required in /etc and reboot the server. My maximum downtime is 5 > > minutes per upgrade unless some hardware goes bad but that is not the > > fault of FreeBSD. > > I wonder if this is generic enough that the script should be part of the > distribution. > > Should FreeBSD be distributing scripts for maintaining build systems, testing > those build systems, and upgrading production systems from them? Already done. "make buildworld" on your build system, and "make installworld" everywhere else. > Andrew McNaughton Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Mar 21 17:24:13 1999 Delivered-To: freebsd-stable@freebsd.org Received: from gooey.bunnynet.org (pm04-s17.donet.com [198.30.201.209]) by hub.freebsd.org (Postfix) with ESMTP id 7D68414BCD for ; Sun, 21 Mar 1999 17:24:07 -0800 (PST) (envelope-from mwhite@donet.com) Received: from yiff (yiff.bunnynet.org [10.3.2.4]) by gooey.bunnynet.org (8.9.2/8.8.7) with SMTP id UAA00370 for ; Sun, 21 Mar 1999 20:24:51 -0500 (EST) (envelope-from mwhite@donet.com) From: "Matt White" To: Subject: Strange Error Message Date: Sun, 21 Mar 1999 20:23:28 -0500 Message-ID: <000001be7402$9766b5c0$0402030a@yiff.bunnynet.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello... Today while copying a large number of files I started getting this error message: inetd in realloc(): warning: junk pointer, too low to make sense. inetd in free(): warning: junk pointer, too low to make sense. This is a -STABLE system, last cvsupped and built on the 20th of this month. Any idea what this means? It prevented me from logging in, whenever I'd try to start up a telnet session it would toss those two lines to me and close the session. (I was still able to ssh in, which is not started via inetd.) Thanks, Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 22 1:47:52 1999 Delivered-To: freebsd-stable@freebsd.org Received: from schuimpje.snt.utwente.nl (schuimpje.snt.utwente.nl [130.89.238.4]) by hub.freebsd.org (Postfix) with ESMTP id 7C8DD15097 for ; Mon, 22 Mar 1999 01:47:42 -0800 (PST) (envelope-from jeroen@vangelderen.org) Received: from wit395301.student.utwente.nl ([130.89.235.121]:60164 "EHLO vangelderen.org" ident: "NO-IDENT-SERVICE[2]") by schuimpje.snt.utwente.nl with ESMTP id <7977-3302>; Mon, 22 Mar 1999 10:47:14 +0100 Message-ID: <36F611BD.9156B708@vangelderen.org> Date: Mon, 22 Mar 1999 10:47:41 +0100 From: "Jeroen C. van Gelderen" X-Mailer: Mozilla 4.51 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: PIIX4 but no UDMA? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, The following machine: FreeBSD 3.1-STABLE #3: Tue Feb 16 19:37:24 AST 1999 gelderen@cypherpunks.ai:/usr/src/sys/compile/CYPHERPUNKS Calibrating clock(s) ... TSC clock: 224538038 Hz, i8254 clock: 1193197 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz CLK_USE_TSC_CALIBRATION not specified - using old calibration method Timecounter "TSC" frequency 224536147 Hz CPU: AMD-K6tm w/ multimedia extensions (224.54-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x562 Stepping=2 Features=0x8001bf Data TLB: 128 entries, 2-way associative Instruction TLB: 64 entries, 1-way associative L1 data cache: 32 kbytes, 32 bytes/line, 2 lines/tag, 2-way associative L1 instruction cache: 32 kbytes, 32 bytes/line, 2 lines/tag, 2-way associative Write Allocate Enable Limit: 128M bytes Write Allocate 15-16M bytes: Enable Hardware Write Allocate Control: Disable real memory = 134217728 (131072K bytes) Physical memory chunk(s): 0x00001000 - 0x0009ffff, 651264 bytes (159 pages) 0x00235000 - 0x07ff5fff, 131862528 bytes (32193 pages) avail memory = 128262144 (125256K bytes) Found BIOS32 Service Directory header at 0xf00fb020 Entry = 0xfb420 (0xf00fb420) Rev = 0 Len = 1 PCI BIOS entry at 0xb450 Other BIOS signatures found: ACPI: 00000000 $PnP: 000fc140 Preloaded elf kernel "kernel" at 0xf0228000. [...] appears to have a PIIX4 controller: [...] found-> vendor=0x8086, dev=0x7111, revid=0x01 class=01-01-80, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[0]: type 4, range 32, base 0000f000, size 4 ide_pci0: rev 0x01 on pci0.7.1 intel_piix_status: primary master/slave sample = 3, master/slave recovery = 1 intel_piix_status: primary master fastDMAonly disabled, pre/post enabled, intel_piix_status: IORDY sampling enabled, intel_piix_status: fast PIO enabled intel_piix_status: primary master/slave sample = 3, master/slave recovery = 1 intel_piix_status: primary slave fastDMAonly disabled, pre/post disabled, intel_piix_status: IORDY sampling disabled, intel_piix_status: fast PIO disabled ide_pci: busmaster 0 status: 04 from port: 0000f002 intel_piix_status: secondary master/slave sample = 5, master/slave recovery = 4 intel_piix_status: secondary master fastDMAonly disabled, pre/post disabled, intel_piix_status: IORDY sampling disabled, intel_piix_status: fast PIO disabled intel_piix_status: secondary master/slave sample = 5, master/slave recovery = 4 intel_piix_status: secondary slave fastDMAonly disabled, pre/post disabled, intel_piix_status: IORDY sampling disabled, intel_piix_status: fast PIO disabled ide_pci: busmaster 1 status: 04 from port: 0000f00a [...] which AFAIK should talk UDMA to the following drive: [...] wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): wd0: 8693MB (17803296 sectors), 17662 cyls, 16 heads, 63 S/T, 512 B/S wd0: ATA INQUIRE valid = 0007, dmamword = 0007, apio = 0003, udma = 0407 [...] The BIOS reports that this drive is UDMA capable and UDMA seems to be enabled in the BIOS. FreeBSD however, doesn't report UDMA functionality in the verbose boot. I tried to mess a bit with the source to find out why UDMA doesn't get enabled, but this is beyond me or my spare time :-( Anybody any clues? Cheers, Jeroen PS. [gelderen@cypherpunks gelderen]$ uptime 5:42AM up 33 days, 10:04, 2 users, load averages: 0.44, 0.53, 0.58 :-) -- Jeroen C. van Gelderen - jeroen@vangelderen.org - 0xC33EDFDE To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 22 4:52:37 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 4AC5414A09 for ; Mon, 22 Mar 1999 04:52:35 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id VAA19064; Mon, 22 Mar 1999 21:52:32 +0900 (JST) Message-ID: <36F63224.BC5A9F5A@newsguy.com> Date: Mon, 22 Mar 1999 21:05:56 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Mike Meyer Cc: stable@FreeBSD.ORG Subject: Re: Build of 3.1-STABLE failing? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Meyer wrote: > > If you make regular backups of userland, that represents quite a bit > of work. Since it rebuilds everything in userland, you wind up dumping > all of userland with every backup, so you need to do some kind of > special backup after doing an installworld. Putting it all together, > that's enough work that I wouldn't bother doing it except every 6-8 > weeks. But -RELEASE happens about twice that often. What's the point > of tracking -STABLE under those conditions? What does world installs? /bin /sbin /usr/bin /usr/sbin /usr/lib /usr/libexec /usr/share I might be missing a couple more directories, but that's beside the point. These things should be touched by world, and world alone. You'll notice that ports *don't* touch these directories. So, leave them out of the backup. Well, you might want to keep /usr/lib in. When you restore the backup, you go back to RELEASE (which you did back up), plus all other stuff you installed/modified, and the later libraries, just in case they are needed for the stuff you installed. All the same, next time you installworld you'll be -stable again. > Of course, part of the reason for tracking -STABLE is I want > up-to-date versions of various ports. After all, like most users, I > have a computer so I can run the apps, not the OS. But here we're told > that the ports tree and the OS are tied together - and you shouldn't > try using newer versions of the ports without having the appropriate > underlying OS. Given that /usr/ports was one of the reasons I chose > FreeBSD, not being able to track that closely is a serious hit. What was said is that you need to install the appropriate upgrade package. Sure, track ports only. But if something goes wrong, install the upgrade package *before* complaining. > This all points to one of the most serious problems with the current > release system - that patches seem to be considered impossible. On > commercial OS's, or Linux, you see small distributions that fix a few > things in userland (a security hole in Sendmail being a typical > example). Fixing that is a simple matter of installing that patch and > restarting sendmail on the relevant systems (assuming the patch didn't > do that for you). On the other hand, here I see a discussion of doing > a "point release" instead of a patch. This means that fixing the > problem requires reinstalling the OS for all those systems. Surely, > anyone who runs more than a few systems doesn't do this? Surely, there are a lot of them that do. The two most common methods being installworld over NFS and rdist or similar (Matthew Dillon has a very good utility, which he created for this precise purpose). > > > Just one question - what are "make" and "make install" for, then? > > > > For those who know what they are doing. > > For instance, they can be very handy for developers who know what > > their modifications are doing or not to the source tree. > > You mean - people who go in and edit the userland sources? Nuts - > that's one of the reasons I *started* tracking -STABLE. I kept hoping Why nuts? Why can't these people have their tools? It's not like you don't have *your* tools, it's just that you don't like them (buildworld & installworld). Make is a program for programmers, in first place. > the patches I submitted with pr bin/9429 would show up, as well as > some of the ports I've done and submitted. If you submitted the patches, you better just keep your own tree, with your patches. Whenever the patches reach the tree, the committer will, hopefully, close the PR. > > At the very least, you should have tried "world" before asking the > > question. > > True - it would have avoided a lot of flaming on the list. I might not have paid enough attention, but I saw no one flaming you. I saw a lot of people saying "you should have done make buildworld & make installworld", which could not have been stated in any other way that I can think of (and is the *documented* procedure). You then replied saying that using "make && make install" is what you have always done, to which I then replied that this is why it broke for you. Frankly, what else could we have answered? The source tree broke for you because you did not follow the correct procedure. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "What happened?" "It moved, sir!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 22 5: 9:39 1999 Delivered-To: freebsd-stable@freebsd.org Received: from st-lcremean.tidalwave.net (host-e186.tidalwave.net [208.213.203.186]) by hub.freebsd.org (Postfix) with ESMTP id EAFF2150B8 for ; Mon, 22 Mar 1999 05:09:35 -0800 (PST) (envelope-from lee@st-lcremean.tidalwave.net) Received: (from lee@localhost) by st-lcremean.tidalwave.net (8.9.2/8.9.2) id IAA37943; Mon, 22 Mar 1999 08:09:11 -0500 (EST) (envelope-from lee) Message-ID: <19990322080910.A37915@tidalwave.net> Date: Mon, 22 Mar 1999 08:09:10 -0500 From: Lee Cremeans To: "Jeroen C. van Gelderen" , freebsd-stable@FreeBSD.ORG Subject: Re: PIIX4 but no UDMA? Reply-To: lcremean@tidalwave.net References: <36F611BD.9156B708@vangelderen.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <36F611BD.9156B708@vangelderen.org>; from Jeroen C. van Gelderen on Mon, Mar 22, 1999 at 10:47:41AM +0100 X-OS: FreeBSD 3.0-STABLE Organization: My room? Are you crazy? :) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Mar 22, 1999 at 10:47:41AM +0100, Jeroen C. van Gelderen wrote: > Hi, > > The following machine: [snip] > > appears to have a PIIX4 controller: > > [...] > found-> vendor=0x8086, dev=0x7111, revid=0x01 > class=01-01-80, hdrtype=0x00, mfdev=0 > subordinatebus=0 secondarybus=0 > map[0]: type 4, range 32, base 0000f000, size 4 > ide_pci0: rev 0x01 on pci0.7.1 [snip] > which AFAIK should talk UDMA to the following drive: > > [...] > wdc0 at 0x1f0-0x1f7 irq 14 on isa > wdc0: unit 0 (wd0): > wd0: 8693MB (17803296 sectors), 17662 cyls, 16 heads, 63 S/T, 512 B/S > wd0: ATA INQUIRE valid = 0007, dmamword = 0007, apio = 0003, udma = 0407 > [...] > > The BIOS reports that this drive is UDMA capable and UDMA seems to be > enabled in the BIOS. FreeBSD however, doesn't report UDMA functionality > in the verbose boot. I tried to mess a bit with the source to find out > why UDMA doesn't get enabled, but this is beyond me or my spare time :-( > Anybody any clues? FreeBSD has DMA support turned off by default. Add "flags 0xa0ffa0ff" to the wdc0 line in your kernel config, or in user config with the flags command, and it should work. -- +--------------------------------------------------------------------+ | Lee Cremeans -- Manassas, VA, USA (WakkyMouse on WTnet) | | lcremean@tidalwave.net| http://st-lcremean.tidalwave.net/~lee | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 22 5:43:21 1999 Delivered-To: freebsd-stable@freebsd.org Received: from pi.yip.org (yip.org [142.154.6.140]) by hub.freebsd.org (Postfix) with ESMTP id AC9CB14F26 for ; Mon, 22 Mar 1999 05:43:07 -0800 (PST) (envelope-from melange@yip.org) Received: from localhost (melange@localhost) by pi.yip.org (8.9.2/8.9.2) with ESMTP id IAA15268 for ; Mon, 22 Mar 1999 08:43:56 -0500 (EST) (envelope-from melange@yip.org) Date: Mon, 22 Mar 1999 08:43:56 -0500 (EST) From: Bob K To: freebsd-stable@freebsd.org Subject: 24-character usernames? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I recently wanted to try out 24-character usernames on my system. So, following the man page for adduser, I changed UT_NAMESIZE in /usr/include/utmp.h to 24 from the default of 16. I then changed MAXLOGNAME in /usr/include/sys/param.h to 25, as per the comments in both utmp.h and param.h. I then made buildworld && make installworld (-j4 -O -pipe only) and a new kernel (-O -pipe), and then built the various ports that would need it. Well, adduser still would complain about usernames more than 16 characters. As an added bonus, I began seeing odd things with w and who, such as: 8:32AM up 21:32, 2 users, load averages: 1.40, 1.07, 0.63 USER TTY FROM LOGIN@ IDLE WHAT nistor p3 snickers:ttyp6:S 31Dec69 9:03 -tcsh (tcsh) melange p6 ttyp4 31Dec69 - screen -r (screen-3.7.6) pi# who nistor ttyp3 Dec 31 22:25 (snickers:ttyp6:S) melange ttyp6 Dec 31 19:00 (ttyp4) pi# Note a) the login date, and b) how user nistor is now logged in from snickers:ttyp6:S rather than snickers.org. I've also seen at the top of the output things such as w://ttyp4:S.0: no such file or directory (but this only happens once in a while). Sources were originally from March 12th. I cvsupped on March 18th and made world again to see if it was just a temporary bug. Same deal (although when I made installworld, it did clobber the changes to utmp.h and sys/param.h). Has anyone else seen this? Is this just pilot error? It's an SMP system, although I'd be extremely suprised if that made a difference with this. If anyone wants more info, just ask and ye shall receive... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 22 5:46: 8 1999 Delivered-To: freebsd-stable@freebsd.org Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.40.153]) by hub.freebsd.org (Postfix) with ESMTP id 58318151ED; Mon, 22 Mar 1999 05:29:15 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by phk.freebsd.dk (8.9.1/8.8.8) with ESMTP id OAA04282; Mon, 22 Mar 1999 14:28:55 +0100 (CET) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.2/8.9.2) with ESMTP id OAA14971; Mon, 22 Mar 1999 14:28:50 +0100 (CET) (envelope-from phk@critter.freebsd.dk) Date: Mon, 22 Mar 1999 14:28:50 +0100 Message-ID: <14969.922109330.1@critter.freebsd.dk> From: Poul-Henning Kamp Subject: NTP kernel support in FreeBSD, a few notes... MIME-Version: 1.0 Content-Type: multipart/digest; boundary="----- =_aaaaaaaaaa" Content-Description: Blind Carbon Copy Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ------- =_aaaaaaaaaa Content-Type: message/rfc822 Content-Description: Original Message Subject: NTP kernel support in FreeBSD, a few notes... Date: Mon, 22 Mar 1999 14:28:50 +0100 Message-ID: <14969.922109330@critter.freebsd.dk> From: Poul-Henning Kamp Bcc: Blind Distribution List: ; MIME-Version: 1.0 I have just merged the recent modifications to the kernel support for NTPD from -current to -stable. We now fully support both XNTPD version 3 (as in usr/src/usr.sbin) and NTPD version 4 in both -current & -stable. In fact, we not only support it, we define state of the art performance when using the pci/xrpu.c driver. We have only adopted the PLL/FLL section of Dave Mills "nanokernel", the rest of the stuff is still "timecounter" based. We have PPS-API support on the parallel port and on the pci/xrpu.c driver, John Hay has submitted patches to me for PPS-API support on sio.c (DCD) these will be committed to -current once I have them tested. I may experient a bit with hardpps() in -current if I can find the time, but these experiments will not be reflected in -stable until some kind of conclusion has been reached. The issue at hand is if a "normal" 2nd order PLL would do better for precise-phase hardpps() signals ("prefer peers") Anyone out there with hardpps() able refclocks are invited to join in on these experients. If you want to try out the pci/xrpu.c timestamping function, send me email, I have not committed the VHDL & stuff to the tree yet. Hope you like it... -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! ------- =_aaaaaaaaaa-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 22 6:23:32 1999 Delivered-To: freebsd-stable@freebsd.org Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (Postfix) with ESMTP id 448AE14EF9 for ; Mon, 22 Mar 1999 06:23:27 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from keep.lan.Awfulhak.org (keep.lan.Awfulhak.org [172.16.0.8]) by awfulhak.org (8.9.2/8.8.8) with ESMTP id OAA33694; Mon, 22 Mar 1999 14:22:57 GMT (envelope-from brian@Awfulhak.org) Received: from keep.lan.Awfulhak.org (localhost [127.0.0.1]) by keep.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id IAA00589; Mon, 22 Mar 1999 08:25:14 GMT (envelope-from brian@keep.lan.Awfulhak.org) Message-Id: <199903220825.IAA00589@keep.lan.Awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: Mike Meyer Cc: stable@FreeBSD.ORG Subject: Re: Build of 3.1-STABLE failing? In-reply-to: Your message of "Sun, 21 Mar 1999 15:07:08 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 22 Mar 1999 08:25:14 +0000 From: Brian Somers Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Sun, 21 Mar 1999, Daniel C. Sobral wrote: > > > Running stable is preferable than release. But the targets are > > buildworld and installworld. > > If you make regular backups of userland, that represents quite a bit > of work. Since it rebuilds everything in userland, you wind up dumping > all of userland with every backup, so you need to do some kind of > special backup after doing an installworld. Putting it all together, > that's enough work that I wouldn't bother doing it except every 6-8 > weeks. But -RELEASE happens about twice that often. What's the point > of tracking -STABLE under those conditions? Set COPY to -C in /etc/make.conf. > Of course, part of the reason for tracking -STABLE is I want > up-to-date versions of various ports. After all, like most users, I > have a computer so I can run the apps, not the OS. But here we're told > that the ports tree and the OS are tied together - and you shouldn't > try using newer versions of the ports without having the appropriate > underlying OS. Given that /usr/ports was one of the reasons I chose > FreeBSD, not being able to track that closely is a serious hit. > > This all points to one of the most serious problems with the current > release system - that patches seem to be considered impossible. On > commercial OS's, or Linux, you see small distributions that fix a few > things in userland (a security hole in Sendmail being a typical > example). Fixing that is a simple matter of installing that patch and > restarting sendmail on the relevant systems (assuming the patch didn't > do that for you). On the other hand, here I see a discussion of doing > a "point release" instead of a patch. This means that fixing the > problem requires reinstalling the OS for all those systems. Surely, > anyone who runs more than a few systems doesn't do this? AFAIK, FreeBSD is never going to start making these sort of patches. It only leads to the linux ``Sendmail doesn't work ? Ahh, you need to install patch 1.2.3 from some.domain, but I wouldn't do that unless you've first installed patch 1.1 from some.other.place'', or even worse, the Solaris scenario where you can install individual patches or you can install jumbo ``recommended'' or ``y2000'' patches where the patch set that these words represent changes monthly.... > Unfortunately, I don't have a solution, even ignoring the problem of > needing to find extra time to do that work. The main reason for doing > this is to see if anyone else has ideas for a solution. Either use the -C install option as mentioned above or subscribe to the commit lists and decide when you want to rebuild/install an individual program. You can then do a ``make world'' every six weeks or whatever. > > > Just one question - what are "make" and "make install" for, then? > > > > For those who know what they are doing. > > For instance, they can be very handy for developers who know what > > their modifications are doing or not to the source tree. > > You mean - people who go in and edit the userland sources? Nuts - > that's one of the reasons I *started* tracking -STABLE. I kept hoping > the patches I submitted with pr bin/9429 would show up, as well as > some of the ports I've done and submitted. Right - if you've submitted changes, you'll know exactly what knock-on effect they'll have on other parts of the system. You therefore already know where to go before doing the makes (I mean which directory ! ;) > > At the very least, you should have tried "world" before asking the > > question. > > True - it would have avoided a lot of flaming on the list. > > Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 22 7:39:40 1999 Delivered-To: freebsd-stable@freebsd.org Received: from pop01.globecomm.net (pop01.globecomm.net [206.253.129.185]) by hub.freebsd.org (Postfix) with ESMTP id 92E2614C18 for ; Mon, 22 Mar 1999 07:39:32 -0800 (PST) (envelope-from sandy@cyberservices.com) Received: from cyberservices.com (ip55.tpi.ru [195.151.116.55]) by pop01.globecomm.net (8.9.0/8.8.0) with ESMTP id KAA28627 for ; Mon, 22 Mar 1999 10:38:54 -0500 (EST) Message-ID: <36F664CF.A38D94B1@cyberservices.com> Date: Mon, 22 Mar 1999 18:42:08 +0300 From: Alex Kosorukoff Organization: MGK X-Mailer: Mozilla 4.05 [en] (X11; I; FreeBSD 2.2.5-RELEASE i386) MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: Re: SIO probe problem in TOSHIBA SATELLITE 4005 Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello! I have FBSD 2.2.5 and it can't find my sio0 serial port, that has standard address and interrupt. I've heard that this problem is fixed in 2.2.8 and later versions and there are patches to fix it in 2.2.5 and 2.2.6. Although I couldn't find such a patch for 2.2.5 on your site. Can you help me? Thanks for your attention, Alex --- www.3form.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 22 7:46:23 1999 Delivered-To: freebsd-stable@freebsd.org Received: from freed.libdns.qc.ca (derby.JSP.UMontreal.CA [132.204.45.26]) by hub.freebsd.org (Postfix) with ESMTP id 3D55514D6F; Mon, 22 Mar 1999 07:46:17 -0800 (PST) (envelope-from spidey@libdns.qc.ca) Received: from localhost (spidey@localhost) by freed.libdns.qc.ca (8.9.2/8.9.2) with SMTP id KAA00741; Mon, 22 Mar 1999 10:44:29 -0500 (EST) (envelope-from spidey@libdns.qc.ca) X-Authentication-Warning: freed.libdns.qc.ca: spidey owned process doing -bs Date: Mon, 22 Mar 1999 10:44:29 -0500 (EST) From: Spidey Reply-To: Spidey To: Munehiro Matsuda Cc: talon@lpthe.jussieu.fr, chad@freebie.dcfinc.com, kaj@raditex.se, freebsd-questions , freebsd-stable@FreeBSD.ORG Subject: SOLVED: Re: Problems with SB16 PnP and FBSD-stable (fwd) In-Reply-To: <19990319171536Q.haro@tk.kubota.co.jp> 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! Thanks to all the people who helped me through this... Your advices are what is making FreeOses like FreeBSD great! So, yes, i made it through. I don't really know what the problem was... guessing that since Windows could use the sound card correctly, I could get some answers there. What I discovered was that, surprisingly, windows had assigned the SB to the 2/9 IRQ channel!!! With drq0 at 3 and drq1 at 7... So I made the exact same setup in the -c pnp config in my kernel and.. it worked!!! However I am still worried that it (SB) uses the 2/9 irq... this is weird! I never saw this before. I would better like my modem to use this, but I don't know how to do it. (could someone know this? It's a Cirrus Logic PnP modem, and is now on COM2/irq5) Thanks a lot to all people who helped me, again... The only thing now is that I have a __lot__ of debugging messages issued from the kernel when I play sounds... Nothing a kernel rebuild won't fix... :) On Fri, 19 Mar 1999, Munehiro Matsuda wrote: > From: Spidey > Date: Thu, 18 Mar 1999 21:00:06 -0500 (EST) > ::No. That's not it either... > > How about enabling DEBUG mode in pcm? > > 1. Change following line in /usr/src/sys/i386/isa/snd/sound.h: > > from: > #define DEB(x) > > to: > #define DEB(x) x > > 2. Update source files in /usr/src/sys/i386/isa/snd > > # touch /usr/src/sys/i386/isa/snd/*.c > > 3. Recompile kernel and reboot > > Now what happens? > > Haro, > ------------------------------------------------------------------------------- > _ _ Munehiro (haro) Matsuda > -|- /_\ |_|_| Office of Business Planning & Developement, Kubota Corp. > /|\ |_| |_|_| 1-3 Nihonbashi-Muromachi 3-Chome > Chuo-ku Tokyo 103, Japan > Tel: +81-3-3245-3318 Fax: +81-3-32454-3315 > Email: haro@tk.kubota.co.jp > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > > > When a man lies he murders some part of the world These are the pale deaths which men miscall their lives All this I can witness any longer Cannot the kingdom of salvation take me home To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 22 10:45:50 1999 Delivered-To: freebsd-stable@freebsd.org Received: from rucus.ru.ac.za (rucus.ru.ac.za [146.231.29.2]) by hub.freebsd.org (Postfix) with SMTP id E9BE514FF2 for ; Mon, 22 Mar 1999 10:45:42 -0800 (PST) (envelope-from nbm@rucus.ru.ac.za) Received: (qmail 48044 invoked by uid 1003); 22 Mar 1999 20:48:04 -0000 Date: Mon, 22 Mar 1999 20:48:04 +0000 From: Neil Blakey-Milner To: Bob K Cc: freebsd-stable@FreeBSD.ORG Subject: Re: 24-character usernames? Message-ID: <19990322204803.A47001@rucus.ru.ac.za> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: ; from Bob K on Mon, Mar 22, 1999 at 08:43:56AM -0500 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon 1999-03-22 (08:43), Bob K wrote: > pi# who > nistor ttyp3 Dec 31 22:25 (snickers:ttyp6:S) > melange ttyp6 Dec 31 19:00 (ttyp4) > > Note a) the login date, and b) how user nistor is now logged in from > snickers:ttyp6:S rather than snickers.org. I've also seen at the top of > the output things such as w://ttyp4:S.0: no such file or directory (but > this only happens once in a while). Did you whack your old utmp/wtmp? The lack of doing this may cause problems like this. Neil -- Neil Blakey-Milner nbm@rucus.ru.ac.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 22 11:26:37 1999 Delivered-To: freebsd-stable@freebsd.org Received: from pi.yip.org (yip.org [142.154.6.140]) by hub.freebsd.org (Postfix) with ESMTP id 31E651510D for ; Mon, 22 Mar 1999 11:26:30 -0800 (PST) (envelope-from melange@yip.org) Received: from localhost (melange@localhost) by pi.yip.org (8.9.2/8.9.2) with ESMTP id OAA17801; Mon, 22 Mar 1999 14:27:18 -0500 (EST) (envelope-from melange@yip.org) Date: Mon, 22 Mar 1999 14:27:18 -0500 (EST) From: Bob K To: Neil Blakey-Milner Cc: freebsd-stable@FreeBSD.ORG Subject: Re: 24-character usernames? In-Reply-To: <19990322204803.A47001@rucus.ru.ac.za> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 22 Mar 1999, Neil Blakey-Milner wrote: > On Mon 1999-03-22 (08:43), Bob K wrote: > > pi# who > > nistor ttyp3 Dec 31 22:25 (snickers:ttyp6:S) > > melange ttyp6 Dec 31 19:00 (ttyp4) > > > > Note a) the login date, and b) how user nistor is now logged in from > > snickers:ttyp6:S rather than snickers.org. I've also seen at the top of > > the output things such as w://ttyp4:S.0: no such file or directory (but > > this only happens once in a while). > > Did you whack your old utmp/wtmp? The lack of doing this may cause problems > like this. Er, no. Are there any specific instructions to do this? Is it just a case of cat /dev/null>/var/run/utmp and cat /dev/null>/var/log/wtmp? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 22 11:43:24 1999 Delivered-To: freebsd-stable@freebsd.org Received: from guru.phone.net (guru.phone.net [209.157.82.120]) by hub.freebsd.org (Postfix) with SMTP id E9AF914A2F for ; Mon, 22 Mar 1999 11:43:11 -0800 (PST) (envelope-from mwm@phone.net) Received: (qmail 14284 invoked by uid 100); 22 Mar 1999 19:42:52 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 22 Mar 1999 19:42:52 -0000 Date: Mon, 22 Mar 1999 11:42:52 -0800 (PST) From: Mike Meyer To: stable@FreeBSD.ORG Subject: Re: Build of 3.1-STABLE failing? In-Reply-To: <36F63224.BC5A9F5A@newsguy.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 22 Mar 1999, Daniel C. Sobral wrote: > What does world installs? > > /bin > /sbin > /usr/bin > /usr/sbin > /usr/lib > /usr/libexec > /usr/share > > I might be missing a couple more directories, but that's beside the > point. These things should be touched by world, and world alone. > You'll notice that ports *don't* touch these directories. So, leave > them out of the backup. Well, you might want to keep /usr/lib in. You're missing /usr/games (ok, we can live without that...), /usr/include (which not working is why my make break), /usr/libdata parts of /usr/share, /boot and /modules (and again, maybe more). If you read the handbook on backups, you'll note that the recommended backup tool is dump - because it's the only thing that does the job right. Unfortunately, it doesn't have a way to exclude directories. That means your new step is to chflags over all those things. I've thought about pushing /usr/local off onto another file system, and then ont backing up /usr, other than level 0s. Roto (with /var on another file system already) is small enough not to be a problem. > > Of course, part of the reason for tracking -STABLE is I want > > up-to-date versions of various ports. After all, like most users, I > > have a computer so I can run the apps, not the OS. But here we're told > > that the ports tree and the OS are tied together - and you shouldn't > > try using newer versions of the ports without having the appropriate > > underlying OS. Given that /usr/ports was one of the reasons I chose > > FreeBSD, not being able to track that closely is a serious hit. > > What was said is that you need to install the appropriate upgrade > package. Sure, track ports only. But if something goes wrong, > install the upgrade package *before* complaining. I'm pretty sure that what was said was that you should only use the ports tree that came with the CD-ROM (i.e. - the -RELEASE ports tree) with that CD-ROM, and you should track -STABLE if you wanted to track the ports tree. However, even doing that can still lead to broken binaries with the recommended regimine. More in the next message. > > This all points to one of the most serious problems with the current > > release system - that patches seem to be considered impossible. On > > commercial OS's, or Linux, you see small distributions that fix a few > > things in userland (a security hole in Sendmail being a typical > > example). Fixing that is a simple matter of installing that patch and > > restarting sendmail on the relevant systems (assuming the patch didn't > > do that for you). On the other hand, here I see a discussion of doing > > a "point release" instead of a patch. This means that fixing the > > problem requires reinstalling the OS for all those systems. Surely, > > anyone who runs more than a few systems doesn't do this? > > Surely, there are a lot of them that do. The two most common methods > being installworld over NFS and rdist or similar (Matthew Dillon has > a very good utility, which he created for this precise purpose). Given that you set INSTALL to "install -C" in make.conf, that should work reasonably well. There's at least one other problem, though (again, see the next message). > > > > Just one question - what are "make" and "make install" for, then? > > > > > > For those who know what they are doing. > > > For instance, they can be very handy for developers who know what > > > their modifications are doing or not to the source tree. > > > > You mean - people who go in and edit the userland sources? Nuts - > > that's one of the reasons I *started* tracking -STABLE. I kept hoping > > Why nuts? Why can't these people have their tools? It's not like you > don't have *your* tools, it's just that you don't like them > (buildworld & installworld). "Nuts" because the reason stated was exactly what I *was* doing. I was using make & make install to build & install my changes to the source tree. > Make is a program for programmers, in first place. Right. Sounds like my kind of tool.... > > the patches I submitted with pr bin/9429 would show up, as well as > > some of the ports I've done and submitted. > > If you submitted the patches, you better just keep your own tree, > with your patches. Whenever the patches reach the tree, the > committer will, hopefully, close the PR. Which sounds like "don't bother tracking -STABLE, just track -RELEASE". After all, what I was doing was to make update, reinstall my patches, then do the build. > > > At the very least, you should have tried "world" before asking the > > > question. > > > > True - it would have avoided a lot of flaming on the list. > > I might not have paid enough attention, but I saw no one flaming > you. I saw a lot of people saying "you should have done make > buildworld & make installworld", which could not have been stated in > any other way that I can think of (and is the *documented* > procedure). You then replied saying that using "make && make > install" is what you have always done, to which I then replied that > this is why it broke for you. > > Frankly, what else could we have answered? The source tree broke for > you because you did not follow the correct procedure. Most people did just that. No problem. The rest was just par for this list - condescending and insulting. ; Mon, 22 Mar 1999 12:11:01 -0800 (PST) (envelope-from melange@yip.org) Received: from localhost (melange@localhost) by pi.yip.org (8.9.2/8.9.2) with ESMTP id PAA18249; Mon, 22 Mar 1999 15:10:47 -0500 (EST) (envelope-from melange@yip.org) Date: Mon, 22 Mar 1999 15:10:47 -0500 (EST) From: Bob K To: Neil Blakey-Milner , David Hawkins Cc: freebsd-stable@FreeBSD.ORG Subject: Re: 24-character usernames? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 22 Mar 1999, Bob K wrote: > On Mon, 22 Mar 1999, Neil Blakey-Milner wrote: > > > > nistor ttyp3 Dec 31 22:25 (snickers:ttyp6:S) > > > melange ttyp6 Dec 31 19:00 (ttyp4) > > > > > > Note a) the login date, and b) how user nistor is now logged in from > > > snickers:ttyp6:S rather than snickers.org. I've also seen at the top of > > > the output things such as w://ttyp4:S.0: no such file or directory (but > > > this only happens once in a while). > > > > Did you whack your old utmp/wtmp? The lack of doing this may cause problems > > like this. > > Er, no. Are there any specific instructions to do this? Is it just a > case of cat /dev/null>/var/run/utmp and cat /dev/null>/var/log/wtmp? Well, I gave this a try. No dice: 3:07PM up 1 day, 4:08, 3 users, load averages: 0.12, 0.18, 0.11 USER TTY FROM LOGIN@ IDLE WHAT melange p0 slam3.ican.net 3:06PM - screen (screen-3.7.6) melange p1 - 31Dec69 - (pine) ttyp2 - Fri12AM 13:07 - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 22 12:12: 0 1999 Delivered-To: freebsd-stable@freebsd.org Received: from guru.phone.net (guru.phone.net [209.157.82.120]) by hub.freebsd.org (Postfix) with SMTP id 60F1515211 for ; Mon, 22 Mar 1999 12:11:41 -0800 (PST) (envelope-from mwm@phone.net) Received: (qmail 14435 invoked by uid 100); 22 Mar 1999 20:11:22 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 22 Mar 1999 20:11:22 -0000 Date: Mon, 22 Mar 1999 12:11:22 -0800 (PST) From: Mike Meyer To: stable@FreeBSD.ORG Subject: Musings about tracking FreeBSD... In-Reply-To: <199903220825.IAA00589@keep.lan.Awfulhak.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 22 Mar 1999, Brian Somers wrote: > > > Running stable is preferable than release. But the targets are > > > buildworld and installworld. > > > > If you make regular backups of userland, that represents quite a bit > > of work. Since it rebuilds everything in userland, you wind up dumping > > all of userland with every backup, so you need to do some kind of > > special backup after doing an installworld. Putting it all together, > > that's enough work that I wouldn't bother doing it except every 6-8 > > weeks. But -RELEASE happens about twice that often. What's the point > > of tracking -STABLE under those conditions? > > Set COPY to -C in /etc/make.conf. From looking at make.conf and the various makefile bits in /usr/src, I think you mean set INSTALL to "install -C" (it's in the make.conf, but commented out). > > This all points to one of the most serious problems with the current > > release system - that patches seem to be considered impossible. On > > commercial OS's, or Linux, you see small distributions that fix a few > > things in userland (a security hole in Sendmail being a typical > > AFAIK, FreeBSD is never going to start making these sort of patches. > It only leads to the linux ``Sendmail doesn't work ? Ahh, you need > to install patch 1.2.3 from some.domain, but I wouldn't do that > unless you've first installed patch 1.1 from some.other.place'', or > even worse, the Solaris scenario where you can install individual > patches or you can install jumbo ``recommended'' or ``y2000'' patches > where the patch set that these words represent changes monthly.... First, just to make it clear - I'm not saying that FreeBSD *needs* a patch mechanism. Just that there seems to be a level of functionality I'm used to seeing that's missing. That said, your answer "the cure is worse than the disease" is perfectly valid. However, you chose the other extreme for your example of "the cure"; Sun works harder at not saying "That's fixed in the next release" than any other vendor I've dealt with. Which means you have things like patches to patches, and dozens of versions of a patch, and jumbo patches - which can make getting a patch installed harder than doing a system upgrade. Once you're willing to ask that people upgrade, the frequency of the FreeBSD releases means you will avoid the more extreme cases that Sun gets into. Further, all the sites I've dealt with dealt with this issue by 1) installing the patch on the systems that were being hit by the bug, then 2) adding the patch to the standard system install so new systems didn't get it. This isn't noticably worse than doing one system upgrade, and then just tracking the -STABLE tree for installing new systems. That said, the only real issue would be things that you want to install on most systems, even if they aren't obviously having problems that are cured by an upgrade. As far as I can tell, only security fixes meet that criteria. Possibly those are rare enough it's not a problem, and point releases do the trick? How common are point releases for such things? > > Unfortunately, I don't have a solution, even ignoring the problem of > > needing to find extra time to do that work. The main reason for doing > > this is to see if anyone else has ideas for a solution. > > Either use the -C install option as mentioned above or subscribe to > the commit lists and decide when you want to rebuild/install an > individual program. > > You can then do a ``make world'' every six weeks or whatever. Part of my point was that updating to -STABLE every six weeks or so - when -RELEASE is updated every 12-16 weeks - seems pretty pointless. However, I noticed another problem. If your syslog is sending log messages to a machine that you've shut down (for example, to do a "make installworld" on it), it stops logging until you restart it. Is this a bug? If so, I'll look into fixing it. If not, I can switch to the daemontools port. However, that brings up yet *another* level of problem. Even if you follow the correct procedures completely (or at least as completely as they have been specified here), you can still wind up with broken binaries from the /ports tree. In fact, the first time I did a system update, I did exactly that: update the source tree, build the world, install the world, build a new kernel, install the new kernel, run mergemaster, and reboot. Everything worked fine. Then I dumped / & /usr to disk and tried to burn a CD-ROM of those dumps for archival purposes - only to have cdrecord die in the middle with an illegal system call. Rebuilding cdrecord solved the problem, but this illustrates that the recommended procedure is incomplete - you need to reinstall all ports/packages as well, right? Is there a tool that inspects /var/db/pkg to automate that process? Of course, that leaves things that weren't install from /usr/ports out in the cold. Does anyone actually update all such things? Or do they do the more realistic thing, and just rebuild things that aren't from /usr/ports - or are, for that matter - when they break? Which would also be a perfectly reasonable attitude for /usr/src & make/make install vs. buildworkd/installworld, and which at least one person recommended to me in private mail. ; Mon, 22 Mar 1999 12:16:13 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id FAA07643; Tue, 23 Mar 1999 05:16:00 +0900 (JST) Message-ID: <36F6A49C.68CB8201@newsguy.com> Date: Tue, 23 Mar 1999 05:14:20 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Mike Meyer Cc: stable@freebsd.org Subject: Re: Build of 3.1-STABLE failing? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Meyer wrote: > > > > > > Just one question - what are "make" and "make install" for, then? > > > > > > > > For those who know what they are doing. > > > > For instance, they can be very handy for developers who know what > > > > their modifications are doing or not to the source tree. > > "Nuts" because the reason stated was exactly what I *was* doing. I was > using make & make install to build & install my changes to the source > tree. You said you was cvsupping. What error did you came up with? An undefined "define". Why is that? Because the include file in which it was defined was not installed in the obj tree before the program that required it was compiled. Why not? Because you made "all", instead of making "buildworld". The later makes sure all the programs/libs/includes required to build world are recompiled/installed (in the obj tree) *before* actually doing so, so that modifications to any of these will take effect. If this was *your* modification, you would instantly spot the error, it's causes and figure out what need to be done to solve it. > > If you submitted the patches, you better just keep your own tree, > > with your patches. Whenever the patches reach the tree, the > > committer will, hopefully, close the PR. > > Which sounds like "don't bother tracking -STABLE, just track > -RELEASE". After all, what I was doing was to make update, reinstall > my patches, then do the build. This was left a bit out of context. If what you wanted was "just see when your patches got in", all you have to do is wait for the PR to close, or read cvs-all. No need to keep cvsupping. If you *do* want to track -stable, which, *imho*, is a good idea, but ommv, the correct procedure is buildworld&installworld (or just world). -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "Someone's trying to hack into our server." "Wow... How flattering!" "I know. There must be some mistake." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 22 12:24:50 1999 Delivered-To: freebsd-stable@freebsd.org Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (Postfix) with SMTP id 70DF214D04 for ; Mon, 22 Mar 1999 12:24:49 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 10PBEf-0003Sv-00; Mon, 22 Mar 1999 12:23:45 -0800 Date: Mon, 22 Mar 1999 12:23:43 -0800 (PST) From: Tom X-Sender: tom@shell.uniserve.ca To: Bob K Cc: Neil Blakey-Milner , David Hawkins , freebsd-stable@FreeBSD.ORG Subject: Re: 24-character usernames? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 22 Mar 1999, Bob K wrote: > > case of cat /dev/null>/var/run/utmp and cat /dev/null>/var/log/wtmp? > > Well, I gave this a try. No dice: You need to get lastlog too, and everyone needs to logout after you do it. If you do it right, w will show nothing right after you do it. After you log in, everything should be normal. > 3:07PM up 1 day, 4:08, 3 users, load averages: 0.12, 0.18, 0.11 > USER TTY FROM LOGIN@ IDLE WHAT > melange p0 slam3.ican.net 3:06PM - screen > (screen-3.7.6) > melange p1 - 31Dec69 - (pine) > ttyp2 - Fri12AM 13:07 - > > Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 22 12:38:49 1999 Delivered-To: freebsd-stable@freebsd.org Received: from pi.yip.org (yip.org [142.154.6.140]) by hub.freebsd.org (Postfix) with ESMTP id 52E9E14CAD for ; Mon, 22 Mar 1999 12:38:26 -0800 (PST) (envelope-from melange@yip.org) Received: from localhost (melange@localhost) by pi.yip.org (8.9.2/8.9.2) with ESMTP id PAA18457; Mon, 22 Mar 1999 15:39:07 -0500 (EST) (envelope-from melange@yip.org) Date: Mon, 22 Mar 1999 15:39:07 -0500 (EST) From: Bob K To: Tom Cc: Neil Blakey-Milner , David Hawkins , freebsd-stable@FreeBSD.ORG Subject: Re: 24-character usernames? 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 > > > case of cat /dev/null>/var/run/utmp and cat /dev/null>/var/log/wtmp? > > > > Well, I gave this a try. No dice: > > You need to get lastlog too, and everyone needs to logout after you do > it. If you do it right, w will show nothing right after you do it. After > you log in, everything should be normal. I'm going to try rebuilding screen. But here's a note about adduser: pi# pwd /cudgel/src/usr.sbin/adduser pi# make clean rm -f adduser.8.gz rmuser.8.gz adduser.8.cat.gz rmuser.8.cat.gz pi# make gzip -cn /cudgel/src/usr.sbin/adduser/adduser.8 > adduser.8.gz gzip -cn /cudgel/src/usr.sbin/adduser/rmuser.8 > rmuser.8.gz pi# make install install -c -o root -g wheel -m 555 /cudgel/src/usr.sbin/adduser/adduser.perl /usr/sbin/adduser install -c -o root -g wheel -m 555 /cudgel/src/usr.sbin/adduser/rmuser.perl /usr/sbin/rmuser install -c -o root -g wheel -m 444 adduser.8.gz rmuser.8.gz /usr/share/man/man8 pi# adduser Use option ``-verbose'' if you want see more warnings & questions or try to repair bugs. Enter username [a-z0-9_-]: test5678901234567890123 Username is longer than 16 chars Enter username [a-z0-9_-]: ^C Which kind of strikes me as being a slightly larger problem. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 22 12:42:56 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 6CEDA14E84 for ; Mon, 22 Mar 1999 12:42:55 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id FAA08542; Tue, 23 Mar 1999 05:42:52 +0900 (JST) Message-ID: <36F6AAEC.2BBCA159@newsguy.com> Date: Tue, 23 Mar 1999 05:41:16 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Mike Meyer Cc: stable@FreeBSD.ORG Subject: Re: Musings about tracking FreeBSD... References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Meyer wrote: > ... > system call. Rebuilding cdrecord solved the problem, but this > illustrates that the recommended procedure is incomplete - you need to > reinstall all ports/packages as well, right? Is there a tool that Hardly ever, actually. A few ones might need reinstalling in some cases, but most ports should continue to work just fine. And the only reason I don't say that this particular instance of cdrecord not working for you anymore probably won't ever happen again is that saying this would automatically break cdrecord again. ;-> Was this, by any chance, a 2.2.x -> 3.x upgrade? This is a far greater upgrade than a normal point release. In this case, cdrecord could have been broken because we completely changed our SCSI architecture. That is not something we do very often, I garantee. :-) > Of course, that leaves things that weren't install from /usr/ports out > in the cold. > > Does anyone actually update all such things? Or do they do the more > realistic thing, and just rebuild things that aren't from /usr/ports - > or are, for that matter - when they break? Which would also be a > perfectly reasonable attitude for /usr/src & make/make install > vs. buildworkd/installworld, and which at least one person recommended > to me in private mail. Whatever it works for you. :-) The reason "world" is necessary is that the interdependencies of the build process are too complex for a simple "all" target. It *could* be made to work, at the price making working in the source tree a PITA. But most working programs should *continue* to work, new world or not. That's one reason for using shared libraries, even: so they can get the newer version (with bug fixes) without needing recompilation. The particular case of cdrecord is unfortunate, because there isn't a *standard* interface for it to use. If it used a *standard* interface, it wouldn't get broken. And if it did even then, it would be a bug in FreeBSD. So, it comes down to one getting used enough to know your way around. I think we are still way ahead than anyone else when it comes down to building the whole system (or even parts of it :). -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "Someone's trying to hack into our server." "Wow... How flattering!" "I know. There must be some mistake." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 22 12:59:58 1999 Delivered-To: freebsd-stable@freebsd.org Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (Postfix) with SMTP id 1595214BD3 for ; Mon, 22 Mar 1999 12:59:56 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 10PBn3-0001Qo-00; Mon, 22 Mar 1999 12:59:18 -0800 Date: Mon, 22 Mar 1999 12:59:15 -0800 (PST) From: Tom X-Sender: tom@shell.uniserve.ca To: Bob K Cc: Neil Blakey-Milner , David Hawkins , freebsd-stable@FreeBSD.ORG Subject: Re: 24-character usernames? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 22 Mar 1999, Bob K wrote: > > > > case of cat /dev/null>/var/run/utmp and cat /dev/null>/var/log/wtmp? > > > > > > Well, I gave this a try. No dice: > > > > You need to get lastlog too, and everyone needs to logout after you do > > it. If you do it right, w will show nothing right after you do it. After > > you log in, everything should be normal. > > I'm going to try rebuilding screen. But here's a note about adduser: Of course. Anything that touches wtmp/utmp needs to be rebuilt. > Which kind of strikes me as being a slightly larger problem. Tiny probably actually. Just edit adduser and change it. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 22 13: 3:26 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 F1A2414A2F for ; Mon, 22 Mar 1999 13:03:04 -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 WAA18723 for freebsd-stable@freebsd.org; Mon, 22 Mar 1999 22:02:45 +0100 (CET) (envelope-from olli) Date: Mon, 22 Mar 1999 22:02:45 +0100 (CET) From: Oliver Fromme Message-Id: <199903222102.WAA18723@dorifer.heim3.tu-clausthal.de> To: freebsd-stable@freebsd.org Subject: Re: Problem with "make release" Newsgroups: list.freebsd-stable Organization: Administration Heim 3 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 Vladimir Litovka wrote in list.freebsd-stable: > On Sun, 21 Mar 1999, Richard J. Dawes wrote: > > I too had this problem a month or so back. It turns out that setting > > the COPTS variable in make.conf or with the -D option to include a gcc > > optimization level no higher than "-O" (same as "-O1"), i.e. NOT "-O2" > > or "-O3", will allow the build to complete. (At least this is what > > worked for me...) Good luck! > > You are right. After I've set everywhere '-O -pipe' buildworld finished > without errors. That's nice, but it doesn't fix my problem that I described in the initial posting in this thread. :-( > Optimization.... BTW do FreeBSD's team have plans to use > egcs as main compiler or no? Or gcc 2.8.x at least... 2.8.x is even more buggy then our current gcc. I don't know about egcs, though. 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 Mar 22 13: 8:30 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 326DD14A2F for ; Mon, 22 Mar 1999 13:08:21 -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 WAA18769 for freebsd-stable@FreeBSD.ORG; Mon, 22 Mar 1999 22:08:02 +0100 (CET) (envelope-from olli) Date: Mon, 22 Mar 1999 22:08:02 +0100 (CET) From: Oliver Fromme Message-Id: <199903222108.WAA18769@dorifer.heim3.tu-clausthal.de> To: freebsd-stable@FreeBSD.ORG Subject: Re: 24-character usernames? Newsgroups: list.freebsd-stable Organization: Administration Heim 3 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 Bob K wrote in list.freebsd-stable: > I recently wanted to try out 24-character usernames on my system. So, > following the man page for adduser, I changed UT_NAMESIZE in > /usr/include/utmp.h to 24 from the default of 16. I then changed > MAXLOGNAME in /usr/include/sys/param.h to 25, as per the comments in both > utmp.h and param.h. I then made buildworld && make installworld (-j4 -O > -pipe only) and a new kernel (-O -pipe), and then built the various ports > that would need it. Did you change it in /usr/include only? If I'm not mistaken, you have to change it in /usr/src/include before doing a make world (otherwise it doesn't really take effect). 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 Mar 22 13: 9:45 1999 Delivered-To: freebsd-stable@freebsd.org Received: from rucus.ru.ac.za (rucus.ru.ac.za [146.231.29.2]) by hub.freebsd.org (Postfix) with SMTP id DE2861500B for ; Mon, 22 Mar 1999 13:09:36 -0800 (PST) (envelope-from nbm@rucus.ru.ac.za) Received: (qmail 81837 invoked by uid 1003); 22 Mar 1999 23:11:58 -0000 Date: Mon, 22 Mar 1999 23:11:58 +0000 From: Neil Blakey-Milner To: Mike Meyer Cc: stable@FreeBSD.ORG Subject: Re: Musings about tracking FreeBSD... Message-ID: <19990322231158.A68035@rucus.ru.ac.za> References: <199903220825.IAA00589@keep.lan.Awfulhak.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: ; from Mike Meyer on Mon, Mar 22, 1999 at 12:11:22PM -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon 1999-03-22 (12:11), Mike Meyer wrote: > > > This all points to one of the most serious problems with the current > > > release system - that patches seem to be considered impossible. On > > > commercial OS's, or Linux, you see small distributions that fix a few > > > things in userland (a security hole in Sendmail being a typical If you have a local copy of /usr/src, simply use anoncvs, and cvs diff the pertinent bit of the system if you're really in need of the patch. The point in running -STABLE is that you're getting these little patches all the time, and you don't have to worry about applying them yourself. > First, just to make it clear - I'm not saying that FreeBSD *needs* a > patch mechanism. Just that there seems to be a level of functionality > I'm used to seeing that's missing. I must say the same thing about other operating systems that don't use CVS. I just don't understand how people survive without it, and I imagine CVS is much more of a functional gain than the ability to apply patches you get from a whole bunch of different people all around the world.. > That said, your answer "the cure is worse than the disease" is > perfectly valid. However, you chose the other extreme for your example > of "the cure"; Sun works harder at not saying "That's fixed in the > next release" than any other vendor I've dealt with. Which means you > have things like patches to patches, and dozens of versions of a > patch, and jumbo patches - which can make getting a patch installed > harder than doing a system upgrade. Once you're willing to ask that > people upgrade, the frequency of the FreeBSD releases means you will > avoid the more extreme cases that Sun gets into. Depending on the level of changes, again, all these patches are available using CVS, and I think the cvsweb scripts are pretty friendly (or I may be comparing another project) in this regard. So, if you have a problem with sendmail in 3.0-RELEASE, and you need to fix it up, just run a diff, or just update that small section you're interested in. > Part of my point was that updating to -STABLE every six weeks or so - > when -RELEASE is updated every 12-16 weeks - seems pretty pointless. Possibly, but it all depends on what you're trying to do. I don't think -STABLE is all that geared towards people who couldn't be bothered to follow it. It's point in life is to allow changes to get integrated between releases, and thus people who are keen to get the cutting edge of the blunt edge should be following it. If you don't want the hassles, and the releases are doing it for you, great, just use the releases. Noone is trying to force you to use -STABLE, I'm sure. > However, I noticed another problem. If your syslog is sending log > messages to a machine that you've shut down (for example, to do a > "make installworld" on it), it stops logging until you restart it. Is > this a bug? If so, I'll look into fixing it. If not, I can switch to > the daemontools port. You might want to take this up in another email, as many people who might be interested in this as a problem might not have been interested in your Subject line, or initial content. > However, that brings up yet *another* level of problem. Even if you > follow the correct procedures completely (or at least as completely as > they have been specified here), you can still wind up with broken > binaries from the /ports tree. In fact, the first time I did a system > update, I did exactly that: update the source tree, build the world, > install the world, build a new kernel, install the new kernel, run > mergemaster, and reboot. Everything worked fine. Then I dumped / & > /usr to disk and tried to burn a CD-ROM of those dumps for archival > purposes - only to have cdrecord die in the middle with an illegal > system call. Rebuilding cdrecord solved the problem, but this > illustrates that the recommended procedure is incomplete - you need to > reinstall all ports/packages as well, right? Is there a tool that > inspects /var/db/pkg to automate that process? Obviously reinstalling ports to make sure they know what they're talking to on the other end of a function call is an idea, but doesn't apply in most cases. As a general rule, anything that talks to hardware or memory a lot should be rebuilt. As for tools, it should be relatively trivial to write a script that takes a look at what's installed and then tries to install them again (using make reinstall). (Not that it's likely to be required) > Of course, that leaves things that weren't install from /usr/ports out > in the cold. Unfortunately that's a sad fact of life if you're not using some form of package management. > Does anyone actually update all such things? Or do they do the more > realistic thing, and just rebuild things that aren't from /usr/ports - > or are, for that matter - when they break? Which would also be a > perfectly reasonable attitude for /usr/src & make/make install > vs. buildworkd/installworld, and which at least one person recommended > to me in private mail. On quite a few machines recently I went through and made sure we weren't running any old non-ELF ports, and upgraded as necessary. Since some of these ports had been installed since before I even came to this university two-and-a-half years ago, there doesn't seem to be anything that says that you should go through and update your ports every time you rebuild world. I'm not an expert on the matter, but I'm more impressed with the "assuredness" the world process gives me, compared to the other methods where I've managed to make a few mistakes before. Again, whatever _you_ feel comfortable with - it's your machine, and noone is going to tell you what you _must_ do, but evaluate their advice, and don't come crying if things explode violently. Neil -- Neil Blakey-Milner nbm@rucus.ru.ac.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 22 13:13:16 1999 Delivered-To: freebsd-stable@freebsd.org Received: from pi.yip.org (yip.org [142.154.6.140]) by hub.freebsd.org (Postfix) with ESMTP id 41A621500B for ; Mon, 22 Mar 1999 13:13:13 -0800 (PST) (envelope-from melange@yip.org) Received: from localhost (melange@localhost) by pi.yip.org (8.9.2/8.9.2) with ESMTP id QAA22382; Mon, 22 Mar 1999 16:14:26 -0500 (EST) (envelope-from melange@yip.org) Date: Mon, 22 Mar 1999 16:14:26 -0500 (EST) From: Bob K To: Tom Cc: freebsd-stable@FreeBSD.ORG Subject: Re: 24-character usernames? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 22 Mar 1999, Tom wrote: > > I'm going to try rebuilding screen. But here's a note about adduser: > > Of course. Anything that touches wtmp/utmp needs to be rebuilt. Well, I had already rebuilt it after the first time I made world with the altered utmp.h & params.h files. Rebuilding it now has continued to make no difference. (It's 3.07.06 from the ports collection) > > Which kind of strikes me as being a slightly larger problem. > > Tiny probably actually. Just edit adduser and change it. Ah; didn't realize it was a perl script. So due to trying to work on this along with my regular job, my brain is little more than a large-sized bowl of rice pudding at the moment. I'll continue this once I get home and clear my head a bit. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 22 13:28:23 1999 Delivered-To: freebsd-stable@freebsd.org Received: from guru.phone.net (guru.phone.net [209.157.82.120]) by hub.freebsd.org (Postfix) with SMTP id 7CC4814CF1 for ; Mon, 22 Mar 1999 13:28:21 -0800 (PST) (envelope-from mwm@phone.net) Received: (qmail 14893 invoked by uid 100); 22 Mar 1999 21:28:01 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 22 Mar 1999 21:28:01 -0000 Date: Mon, 22 Mar 1999 13:28:01 -0800 (PST) From: Mike Meyer To: stable@FreeBSD.ORG Subject: Re: Musings about tracking FreeBSD... In-Reply-To: <36F6AAEC.2BBCA159@newsguy.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 Tue, 23 Mar 1999, Daniel C. Sobral wrote: > > system call. Rebuilding cdrecord solved the problem, but this > > illustrates that the recommended procedure is incomplete - you need to > > reinstall all ports/packages as well, right? Is there a tool that > > Hardly ever, actually. A few ones might need reinstalling in some > cases, but most ports should continue to work just fine. That's actually what I expect. > Was this, by any chance, a 2.2.x -> 3.x upgrade? This is a far Nope. 3.0-RELEASE->3.1-STABLE (at the time of the 3.1-RELEASE release). > > Does anyone actually update all such things? Or do they do the more > > realistic thing, and just rebuild things that aren't from /usr/ports - > > or are, for that matter - when they break? Which would also be a > > perfectly reasonable attitude for /usr/src & make/make install > > vs. buildworkd/installworld, and which at least one person recommended > > to me in private mail. > > Whatever it works for you. :-) Yeah - I'm still considering it. I had been working on the (incorrect, obviously) that "make/make install" on the tree or parts of it the equivalent for patches in other platforms. > The reason "world" is necessary is that the interdependencies of the > build process are too complex for a simple "all" target. It *could* > be made to work, at the price making working in the source tree a > PITA. Well, it could be done with a new branch between -STABLE & -RELEASE, that had to build against the -RELEASE headers & libraries. But in general, yeah - having a branch that would build properly against *any* old version of the branch is a PITA, and something you don't run into in commercial build environments. > But most working programs should *continue* to work, new world or > not. That's one reason for using shared libraries, even: so they can > get the newer version (with bug fixes) without needing > recompilation. That has, in general, been my experience. *Including* programs that are built from /usr/src via make & make install. Sure, it's not guaranteed to work. But it sounds like neither is anything else that was on the system before the world got built. > So, it comes down to one getting used enough to know your way > around. I think we are still way ahead than anyone else when it > comes down to building the whole system (or even parts of it :). Certainly ahead of the BSD releases I dealt with before. NetBSD seems close, though. ; Mon, 22 Mar 1999 13:47:29 -0800 (PST) (envelope-from mwm@phone.net) Received: (qmail 15000 invoked by uid 100); 22 Mar 1999 21:47:10 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 22 Mar 1999 21:47:10 -0000 Date: Mon, 22 Mar 1999 13:47:09 -0800 (PST) From: Mike Meyer To: stable@FreeBSD.ORG Subject: Possible bug in syslog? In-Reply-To: <19990322231158.A68035@rucus.ru.ac.za> 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 noticed what I think is a problem. If your syslog is sending log messages to a machine that you've shut down (for example, to do a "make installworld" on it), it stops logging until you restart it. Is this a bug? If so, I'll look into fixing it. If not, I can switch to the daemontools port. Thanx, ; Mon, 22 Mar 1999 13:47:43 -0800 (PST) (envelope-from rjdawes@physics.ucsd.edu) Received: from physics.ucsd.edu (huntington.ucsd.edu [132.239.73.96]) by mailbox1.ucsd.edu (8.9.1a/8.9.1) with SMTP id NAA27783; Mon, 22 Mar 1999 13:47:24 -0800 (PST) Received: from localhost by physics.ucsd.edu (SMI-8.6/SMI-SVR4) id NAA18929; Mon, 22 Mar 1999 13:45:44 -0800 Date: Mon, 22 Mar 1999 13:45:43 -0800 (PST) From: "Richard J. Dawes" X-Sender: rjdawes@huntington Reply-To: Richard Dawes To: Mike Meyer Cc: stable@FreeBSD.ORG Subject: Re: Musings about tracking FreeBSD... 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 Hi! How about if you write a script that gets a list of ports you've installed (or just ones you worry about). Then it goes through your mail from the "cvs-all" mailing-list, and adds those regarding your list of ports to a file (sorted to taste), discarding the rest. Run nightly, or whenever you make world. A quick scan of the output should indicate the ports you might wish to upgrade. Might not be too hard in PERL. Just an idea... Good luck! --Rich On Mon, 22 Mar 1999, Mike Meyer wrote: > [...] > However, that brings up yet *another* level of problem. Even if you > follow the correct procedures completely (or at least as completely as > they have been specified here), you can still wind up with broken > binaries from the /ports tree. In fact, the first time I did a system > update, I did exactly that: update the source tree, build the world, > install the world, build a new kernel, install the new kernel, run > mergemaster, and reboot. Everything worked fine. Then I dumped / & > /usr to disk and tried to burn a CD-ROM of those dumps for archival > purposes - only to have cdrecord die in the middle with an illegal > system call. Rebuilding cdrecord solved the problem, but this > illustrates that the recommended procedure is incomplete - you need to > reinstall all ports/packages as well, right? Is there a tool that > inspects /var/db/pkg to automate that process? > [...] ======================================== Richard J. Dawes rdawes@ucsd.edu ======================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 22 13:47:55 1999 Delivered-To: freebsd-stable@freebsd.org Received: from guru.phone.net (guru.phone.net [209.157.82.120]) by hub.freebsd.org (Postfix) with SMTP id 2B89515033 for ; Mon, 22 Mar 1999 13:46:43 -0800 (PST) (envelope-from mwm@phone.net) Received: (qmail 14993 invoked by uid 100); 22 Mar 1999 21:46:24 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 22 Mar 1999 21:46:24 -0000 Date: Mon, 22 Mar 1999 13:46:24 -0800 (PST) From: Mike Meyer To: stable@FreeBSD.ORG Subject: Re: Musings about tracking FreeBSD... In-Reply-To: <19990322231158.A68035@rucus.ru.ac.za> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 22 Mar 1999, Neil Blakey-Milner wrote: > Date: Mon, 22 Mar 1999 23:11:58 +0000 > From: Neil Blakey-Milner > To: Mike Meyer > Cc: stable@FreeBSD.ORG > Subject: Re: Musings about tracking FreeBSD... > > On Mon 1999-03-22 (12:11), Mike Meyer wrote: > > > > This all points to one of the most serious problems with the current > > > > release system - that patches seem to be considered impossible. On > > > > commercial OS's, or Linux, you see small distributions that fix a few > > > > things in userland (a security hole in Sendmail being a typical > > If you have a local copy of /usr/src, simply use anoncvs, and cvs diff the > pertinent bit of the system if you're really in need of the patch. The point > in running -STABLE is that you're getting these little patches all the time, > and you don't have to worry about applying them yourself. Except - as I've just had explained a number of times in a variety of ways - you can't just install the patches. You're supposed to reinstall the whole system. > > First, just to make it clear - I'm not saying that FreeBSD *needs* a > > patch mechanism. Just that there seems to be a level of functionality > > I'm used to seeing that's missing. > > I must say the same thing about other operating systems that don't use CVS. > I just don't understand how people survive without it, and I imagine CVS is > much more of a functional gain than the ability to apply patches you get from > a whole bunch of different people all around the world.. Normally, you get patches from the vendor of the distribution. The vendor takes care of integrating patches from lots of different people for you. Which is exactly what CVS is doing for you. The difference is that they are set up to provide patches against a fixed release, whereas FreeBSD provides a constantly updated release. > > Part of my point was that updating to -STABLE every six weeks or so - > > when -RELEASE is updated every 12-16 weeks - seems pretty pointless. > > Possibly, but it all depends on what you're trying to do. I don't think > -STABLE is all that geared towards people who couldn't be bothered to follow > it. It's point in life is to allow changes to get integrated between > releases, and thus people who are keen to get the cutting edge of the blunt > edge should be following it. If you don't want the hassles, and the releases > are doing it for you, great, just use the releases. Noone is trying to force > you to use -STABLE, I'm sure. You're right, no one is - and I'm not trying to get the behavior of the -STABLE branch changed to match my expectations, either. I got burnt by starting to track -STABLE without properly understanding it. I'm trying to get a better understanding before I decide if I want to stay with -STABLE, or go back to -RELEASE. My problem is, I want cutting edge on critical parts of /usr/ports. But /usr/ports sometimes breaks against -RELEASE, as it gets updated to use new features of tools in -STABLE (fetch adding a new argument, for instance). I've already run into cases where some tools can't be run from the ports tree, because I need access to the source tree for configuration purposes, or to add modules, or whatever. Just dropping back to -RELEASE, and building things I need cutting-edge access to myself is a real possibility. > > However, I noticed another problem. If your syslog is sending log > > messages to a machine that you've shut down (for example, to do a > > "make installworld" on it), it stops logging until you restart it. Is > > this a bug? If so, I'll look into fixing it. If not, I can switch to > > the daemontools port. > > You might want to take this up in another email, as many people who might be > interested in this as a problem might not have been interested in your > Subject line, or initial content. ok... > > Does anyone actually update all such things? Or do they do the more > > realistic thing, and just rebuild things that aren't from /usr/ports - > > or are, for that matter - when they break? Which would also be a > > perfectly reasonable attitude for /usr/src & make/make install > > vs. buildworkd/installworld, and which at least one person recommended > > to me in private mail. > > On quite a few machines recently I went through and made sure we weren't > running any old non-ELF ports, and upgraded as necessary. Since some of > these ports had been installed since before I even came to this university > two-and-a-half years ago, there doesn't seem to be anything that says that > you should go through and update your ports every time you rebuild world. Yeah - a change of binary format sounds like a good time to do a search-and-update on old binaries. I agree about "make world" giving you a nice, warm fuzzy feeling. It would be nice if there were an extended version "make completeworld" that did the groveling through /usr/ports so you could extend that feeling to those things. Of course, in a perfect world, there'd be a hook for getting to the user-built things as well. But that's where things start getting very difficult. Message-Id: <199903222151.OAA68634@panzer.plutotech.com> Subject: quintuple softupdates panic in -stable To: stable@FreeBSD.ORG Date: Mon, 22 Mar 1999 14:51:10 -0700 (MST) Cc: mckusick@mckusick.com, dillon@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just got this panic on a very heavily loaded -stable server. It is RELENG_3 as of about March 10th. I noticed that Kirk checked in some softupdates bug fixes on March 1st/2nd, but they didn't go into RELENG_3. I'm not sure if this panic would be fixed by those changes. I wasn't able to compile a kernel with debugging symbols that would correspond to the one that was running on the machine in question, so there are no symbols. Sorry. Ken -- Kenneth Merry ken@plutotech.com # gdb -k kernel.4 vmcore.4 GDB is free software and you are welcome to 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. GDB 4.16 (i386-unknown-freebsd), Copyright 1996 Free Software Foundation, Inc...(no debugging symbols found)... IdlePTD 2813952 initial pcb at 241958 panicstr: softdep_disk_write_complete: lock is held panic messages: --- panic: allocdirect_check: old 0 != new 397448 || lbn 12 >= 12 syncing disks... panic: softdep_lock: locking against myself panic: softdep_disk_write_complete: lock is held panic: softdep_disk_write_complete: lock is held panic: softdep_disk_write_complete: lock is held dumping to dev 20401, offset 327680 dump 128 127 126 125 124 123 122 121 120 119 118 117 116 115 114 113 112 111 110 109 108 107 106 105 104 103 102 101 100 99 98 97 96 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 0xf01462c7 in boot () (kgdb) where #0 0xf01462c7 in boot () #1 0xf0146548 in at_shutdown () #2 0xf01d414b in softdep_disk_write_complete () #3 0xf01658c5 in biodone () #4 0xf0120f79 in dadone () #5 0xf011cca3 in camisr () #6 0xf011ca99 in swi_cambio () #7 0xf011a194 in xpt_polled_action () #8 0xf0121445 in dashutdown () #9 0xf0146297 in boot () #10 0xf0146548 in at_shutdown () #11 0xf01d414b in softdep_disk_write_complete () #12 0xf01658c5 in biodone () #13 0xf0120f79 in dadone () #14 0xf011cca3 in camisr () #15 0xf011ca99 in swi_cambio () #16 0xf011a194 in xpt_polled_action () #17 0xf0121445 in dashutdown () #18 0xf0146297 in boot () #19 0xf0146548 in at_shutdown () #20 0xf01d414b in softdep_disk_write_complete () #21 0xf01658c5 in biodone () #22 0xf0120f79 in dadone () #23 0xf011cca3 in camisr () #24 0xf011ca99 in swi_cambio () #25 0xf011a194 in xpt_polled_action () #26 0xf0121445 in dashutdown () #27 0xf0146297 in boot () #28 0xf0146548 in at_shutdown () #29 0xf01d112f in acquire_lock () #30 0xf01d3f4f in initiate_write_inodeblock () #31 0xf01d3cd3 in softdep_disk_io_initiation () #32 0xf01766b9 in spec_strategy () #33 0xf0175e81 in spec_vnoperate () #34 0xf01df489 in ufs_vnoperatespec () #35 0xf0163aff in bwrite () #36 0xf016814e in vop_stdbwrite () #37 0xf0167f99 in vop_defaultop () #38 0xf0175e81 in spec_vnoperate () #39 0xf01df489 in ufs_vnoperatespec () #40 0xf016453c in vfs_bio_awrite () #41 0xf01d909a in ffs_fsync () #42 0xf01d7544 in ffs_sync () #43 0xf016ca43 in sync () #44 0xf0146119 in boot () #45 0xf0146548 in at_shutdown () #46 0xf01d216b in allocdirect_merge () #47 0xf01d4d15 in merge_inode_lists () #48 0xf01d4bdc in softdep_update_inodeblock () #49 0xf01d01e4 in ffs_update () #50 0xf01d9f25 in ufs_inactive () #51 0xf01df459 in ufs_vnoperate () #52 0xf016abab in vput () #53 0xf019dbc6 in nfsrv_write () #54 0xf01b3a88 in nfssvc_nfsd () #55 0xf01b3385 in nfssvc () #56 0xf0203a88 in syscall () #57 0xf01fa41c in Xint0x80_syscall () #58 0x80480e9 in ?? () To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 22 13:59: 3 1999 Delivered-To: freebsd-stable@freebsd.org Received: from guru.phone.net (guru.phone.net [209.157.82.120]) by hub.freebsd.org (Postfix) with SMTP id A8D321535B for ; Mon, 22 Mar 1999 13:59:02 -0800 (PST) (envelope-from mwm@phone.net) Received: (qmail 15127 invoked by uid 100); 22 Mar 1999 21:58:22 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 22 Mar 1999 21:58:22 -0000 Date: Mon, 22 Mar 1999 13:58:22 -0800 (PST) From: Mike Meyer To: stable@FreeBSD.ORG Subject: Re: Musings about tracking FreeBSD... 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 While it's good idea, it's not the way I'd tackle it. How about grovelling over the output of "make update", and if a change in a port shows up, check /usr/ports//Makefile for the package name, and then /var/db/pkg for that name. If it's there, add a note about it to that file. Of course this misses changes in the libraries/includes/etc. that might cause you to want to rebuild a port. Date: Mon, 22 Mar 1999 13:45:43 -0800 (PST) > From: Richard J. Dawes > Reply-To: Richard Dawes > To: Mike Meyer > Cc: stable@FreeBSD.ORG > Subject: Re: Musings about tracking FreeBSD... > > Hi! > How about if you write a script that gets a list of ports you've > installed (or just ones you worry about). Then it goes through your > mail from the "cvs-all" mailing-list, and adds those regarding your list > of ports to a file (sorted to taste), discarding the rest. Run nightly, > or whenever you make world. > A quick scan of the output should indicate the ports you might > wish to upgrade. Might not be too hard in PERL. Just an idea... Good > luck! > > --Rich > > > On Mon, 22 Mar 1999, Mike Meyer wrote: > > [...] > > However, that brings up yet *another* level of problem. Even if you > > follow the correct procedures completely (or at least as completely as > > they have been specified here), you can still wind up with broken > > binaries from the /ports tree. In fact, the first time I did a system > > update, I did exactly that: update the source tree, build the world, > > install the world, build a new kernel, install the new kernel, run > > mergemaster, and reboot. Everything worked fine. Then I dumped / & > > /usr to disk and tried to burn a CD-ROM of those dumps for archival > > purposes - only to have cdrecord die in the middle with an illegal > > system call. Rebuilding cdrecord solved the problem, but this > > illustrates that the recommended procedure is incomplete - you need to > > reinstall all ports/packages as well, right? Is there a tool that > > inspects /var/db/pkg to automate that process? > > [...] > > > > > ======================================== > Richard J. Dawes rdawes@ucsd.edu > ======================================== > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 22 14:42:25 1999 Delivered-To: freebsd-stable@freebsd.org Received: from ns.raditex.se (raditex.thorsen.se [193.14.93.200]) by hub.freebsd.org (Postfix) with ESMTP id 16D8A15545 for ; Mon, 22 Mar 1999 14:42:17 -0800 (PST) (envelope-from kaj@raditex.se) Received: from localhost (dialup163-1-50.swipnet.se [130.244.163.50]) by ns.raditex.se (8.8.8/8.8.8) with ESMTP id XAA00585; Mon, 22 Mar 1999 23:41:53 +0100 (CET) (envelope-from kaj@raditex.se) To: mwm@phone.net Cc: stable@FreeBSD.ORG Cc: Rasmus Kaj Subject: Re: Musings about tracking FreeBSD... From: Rasmus Kaj In-Reply-To: Your message of "Mon, 22 Mar 1999 13:46:24 -0800 (PST)" References: X-Mailer: Mew version 1.93 on XEmacs 20.4 (Emerald) X-URL: http://www.e.kth.se/~kaj/ X-Phone: +46 (0)8 - 692 35 09 X-Attribution: Kaj X-Face: M9cR~WYav<"fu%MaslX0`43PAYY?uIsM8[#E(0\Xuy9rj>4gE\h3jm.7DD?]R8*^7T\o&vT U@[53Dwkuup4[0@gw#~kyu>`unH?kVj9CJa02(h>Ki\+i=%rn%sDf^KC.!?IHkKjMAbkd\jgmphp^' d|Q;OeXEAhq?ybGqOs1CHb6TJT42'C`Krnk61//AOfXtNjj/t'`5>Vw0QX!dKfOL$.f+S"LIuwR<;I Z0Qnnx(F^F]o@*V%TUtEV'1Z[TkOl^FFV9Z~A[b19%}uP*,huCU Mime-Version: 1.0 Content-Type: Text/Plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Message-Id: <19990322234320S.kaj@raditex.se> Date: Mon, 22 Mar 1999 23:43:20 +0100 X-Dispatcher: imput version 980905(IM100) Lines: 43 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This thread begins to seem more religious than technical, but I'll run = the risk and throw in a few words anyway ... I'll quote rather briefly, since I will only reply to one of the points made. >>>>> "MM" =3D=3D Mike Meyer writes: MM> On Mon, 22 Mar 1999, Neil Blakey-Milner wrote: >> If you have a local copy of /usr/src, simply use anoncvs, and cvs >> diff the pertinent bit of the system if you're really in need of >> the patch. The point in running -STABLE is that you're getting >> these little patches all the time, and you don't have to worry >> about applying them yourself. MM> Except - as I've just had explained a number of times in a variety = of MM> ways - you can't just install the patches. You're supposed to MM> reinstall the whole system. But you can! Just cvsup or get the patch from its author (which might be found randomly on the net), cd to the directories affected by the change you are interested in and make && make install. This will probably work and all is well. Just remember that IF it fails (to make or to produce a stable working system) the most probable reason for its failure is that the change were depending on some other change in a directory where you didn't make. Now you can either try to track down the dependencies or simply go to /usr/src (or wherever you keep it) and make buildworld && make installworld. So the only problem remaining is that if you choose to 'just install the patches' you might get into trouble by dependencies, but that is certainly true for other systems as well ... -- = Rasmus Kaj ---------------- rasmus@kaj.a.se - http://www.e.kth.se/~kaj/ \ Var glad! Det v=E4rsta har =E4nnu inte intr=E4ffat -Ph. Joh= nnson \--------------------------------------------- http://www.Raditex.se/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 22 17:38:31 1999 Delivered-To: freebsd-stable@freebsd.org Received: from nefertiti.lightningweb.com (nefertiti.lightningweb.com [198.68.191.157]) by hub.freebsd.org (Postfix) with ESMTP id 7CD3514FB2; Mon, 22 Mar 1999 17:38:28 -0800 (PST) (envelope-from keith@lightningweb.com) Received: from localhost (keith@localhost) by nefertiti.lightningweb.com (8.8.7/8.8.5) with SMTP id RAA13463; Mon, 22 Mar 1999 17:40:22 -0800 (PST) Date: Mon, 22 Mar 1999 17:40:22 -0800 (PST) From: Keith Woodman To: freebsd-stable@freebsd.org Cc: freebsd-chat@freebsd.org Subject: fixit.flp NOW 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 HELP. In dire need of a way to boot my system for repair. The last I read, the fixit disk process for 3.0 was broken so I couldn't make one. Is there a way to get this sytem up and rolling with another fixit floppy? Could realy use some advise here. Seems that while preparing to update to -stable, and running mergemaster. I messed up the passwd stuff. Can't seem to get into the system after a logout. :-( I'll be accepting laughs and outright gut busters between the hours of 6pm and 9pm pacific time. And now for my next trick.............. :-) Thanks. ---------------------------------------------------------------------- Keith Woodman Technical Coordinator Keith@lightningweb.com Lightningweb LLC pid 7962 (sniffit), uid 0: exited on signal 10 (core dumped) ---------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 22 17:42:11 1999 Delivered-To: freebsd-stable@freebsd.org Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (Postfix) with SMTP id E47D5152E7; Mon, 22 Mar 1999 17:42:08 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 10PGCR-0005Q5-00; Mon, 22 Mar 1999 17:41:47 -0800 Date: Mon, 22 Mar 1999 17:41:44 -0800 (PST) From: Tom X-Sender: tom@shell.uniserve.ca To: Keith Woodman Cc: freebsd-stable@freebsd.org, freebsd-chat@freebsd.org Subject: Re: fixit.flp NOW In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 22 Mar 1999, Keith Woodman wrote: > HELP. In dire need of a way to boot my system for repair. The > last I read, the fixit disk process for 3.0 was broken so I couldn't make > one. Is there a way to get this sytem up and rolling with another fixit > floppy? Could realy use some advise here. Seems that while preparing to > update to -stable, and running mergemaster. I messed up the passwd stuff. > Can't seem to get into the system after a logout. :-( That shouldn't require an emergency boot disk. You only need an emergency boot disk if you can't boot. Just boot single user, and change the password (or rebuild the password database). Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 22 17:42:33 1999 Delivered-To: freebsd-stable@freebsd.org Received: from shell.futuresouth.com (shell.futuresouth.com [198.78.58.28]) by hub.freebsd.org (Postfix) with ESMTP id 7E0A4152F3; Mon, 22 Mar 1999 17:42:11 -0800 (PST) (envelope-from fullermd@futuresouth.com) Received: (from fullermd@localhost) by shell.futuresouth.com (8.9.3/8.9.3) id TAA18265; Mon, 22 Mar 1999 19:41:43 -0600 (CST) Date: Mon, 22 Mar 1999 19:41:43 -0600 From: "Matthew D. Fuller" To: Keith Woodman Cc: freebsd-chat@FreeBSD.ORG Subject: Re: fixit.flp NOW Message-ID: <19990322194143.D17547@futuresouth.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: ; from Keith Woodman on Mon, Mar 22, 1999 at 05:40:22PM -0800 X-OS: FreeBSD Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ Bad crosspost. BAD! ;-] On Mon, Mar 22, 1999 at 05:40:22PM -0800, a little birdie told me that Keith Woodman remarked > HELP. In dire need of a way to boot my system for repair. The > last I read, the fixit disk process for 3.0 was broken so I couldn't make > one. Is there a way to get this sytem up and rolling with another fixit > floppy? Could realy use some advise here. Seems that while preparing to > update to -stable, and running mergemaster. I messed up the passwd stuff. > Can't seem to get into the system after a logout. :-( > I'll be accepting laughs and outright gut busters between the hours of 6pm > and 9pm pacific time. And now for my next trick.............. :-) If you used mergemaster to merge the password file over, it should have created root with no password. So can't you just boot single user and handle passwords/etc? --- *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* | Matthew Fuller http://www.over-yonder.net/ | * fullermd@futuresouth.com fullermd@over-yonder.net * | UNIX Systems Administrator Specializing in FreeBSD | * FutureSouth Communications ISPHelp ISP Consulting * | "The only reason I'm burning my candle at both ends, | * is because I haven't figured out how to light the * | middle yet" | *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 22 18: 1:53 1999 Delivered-To: freebsd-stable@freebsd.org Received: from quackerjack.cc.vt.edu (quackerjack.cc.vt.edu [198.82.160.250]) by hub.freebsd.org (Postfix) with ESMTP id 4A6A914F59 for ; Mon, 22 Mar 1999 18:01:49 -0800 (PST) (envelope-from jobaldwi@vt.edu) Received: from sable.cc.vt.edu (sable.cc.vt.edu [128.173.16.30]) by quackerjack.cc.vt.edu (8.8.8/8.8.8) with ESMTP id VAA28142; Mon, 22 Mar 1999 21:01:24 -0500 (EST) Received: from john.baldwin.cx (jobaldwi.campus.vt.edu [198.82.67.63]) by sable.cc.vt.edu (8.8.8/8.8.8) with ESMTP id VAA14156; Mon, 22 Mar 1999 21:01:20 -0500 (EST) 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: Date: Mon, 22 Mar 1999 21:01:23 -0500 (EST) From: John Baldwin To: Mike Meyer Subject: Re: Musings about tracking FreeBSD... Cc: stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a very simple shell script that greps /usr/ports/INDEX to find ports that need updating. It does have the rare false alarm (namely pgp-2.6.2). Also, I find that /usr/ports/INDEX isn't always up to date with the rest of the ports tree, occasionally producing another false alarm, but these are easy to find by just checking the version in the respective ports Makefile. If anyones interested, e-mail me and I'll send it to you. On 22-Mar-99 Mike Meyer wrote: > While it's good idea, it's not the way I'd tackle it. How about > grovelling over the output of "make update", and if a change in a port > shows up, check /usr/ports//Makefile for the package name, > and then /var/db/pkg for that name. If it's there, add a note about it > to that file. > > Of course this misses changes in the libraries/includes/etc. that > might cause you to want to rebuild a port. > > > On Mon, 22 Mar 1999, Richard J. Dawes wrote: > >> Date: Mon, 22 Mar 1999 13:45:43 -0800 (PST) >> From: Richard J. Dawes >> Reply-To: Richard Dawes >> To: Mike Meyer >> Cc: stable@FreeBSD.ORG >> Subject: Re: Musings about tracking FreeBSD... >> >> Hi! >> How about if you write a script that gets a list of ports you've >> installed (or just ones you worry about). Then it goes through your >> mail from the "cvs-all" mailing-list, and adds those regarding your list >> of ports to a file (sorted to taste), discarding the rest. Run nightly, >> or whenever you make world. >> A quick scan of the output should indicate the ports you might >> wish to upgrade. Might not be too hard in PERL. Just an idea... Good >> luck! >> >> --Rich >> >> >> On Mon, 22 Mar 1999, Mike Meyer wrote: >> > [...] >> > However, that brings up yet *another* level of problem. Even if you >> > follow the correct procedures completely (or at least as completely as >> > they have been specified here), you can still wind up with broken >> > binaries from the /ports tree. In fact, the first time I did a system >> > update, I did exactly that: update the source tree, build the world, >> > install the world, build a new kernel, install the new kernel, run >> > mergemaster, and reboot. Everything worked fine. Then I dumped / & >> > /usr to disk and tried to burn a CD-ROM of those dumps for archival >> > purposes - only to have cdrecord die in the middle with an illegal >> > system call. Rebuilding cdrecord solved the problem, but this >> > illustrates that the recommended procedure is incomplete - you need to >> > reinstall all ports/packages as well, right? Is there a tool that >> > inspects /var/db/pkg to automate that process? >> > [...] --- John Baldwin -- http://members.freedomnet.com/~jbaldwin/ PGP Key: http://members.freedomnet.com/~jbaldwin/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 22 18:11: 2 1999 Delivered-To: freebsd-stable@freebsd.org Received: from falcon.lonetree.com (falcon.lonetree.com [207.141.55.4]) by hub.freebsd.org (Postfix) with ESMTP id 18442151F8 for ; Mon, 22 Mar 1999 18:10:58 -0800 (PST) (envelope-from wolfnet@wolfnet-irc.org) Received: from wolfnet-irc.org (users.wolfnet-irc.org [209.64.46.42]) by falcon.lonetree.com (8.8.7/8.8.7) with ESMTP id TAA19908 for ; Mon, 22 Mar 1999 19:10:37 -0700 Message-ID: <36F6F936.2ED009F9@wolfnet-irc.org> Date: Mon, 22 Mar 1999 19:15:18 -0700 From: Jonathan Frazier Organization: The WolfNet-IRC Organization X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 3.1-STABLE i386) MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: Packages Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I started out on FreeBSD 2.2.5-RELEASE, then upgraded via CD to 2.2.6-RELEASE, then to 2.2.7-RELEASE. Then I learned about cvsup, a dream come true! I upgraded to 2.2.8-STABLE. Now after a month or so of running 2.2.8-STABLE I decided to take my chances and be brave and upgrade to 3.1-STABLE (scared me to death to be honest). Now I have done that and everything seems to be going ok, mostly. My main problems are dealing with all the hundreds of old packages that I still have from 2.2.5 and 2.2.6. I have never been able to figure out ports, half of them fail building on me. I couldn't build the newest TK and TCL for instance, so I am still using the old 2.2.6 packages for them. That would be ok, I can live with that....but half of the packages don't even work on 3.1-STABLE for me now. Is there any possible way to upgrade packages? Or even download all the newer ones blocked instead of having to buy a new CD and try to sort through them? Thanks for your help. -- Jonathan C. Frazier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 22 19:23:40 1999 Delivered-To: freebsd-stable@freebsd.org Received: from knecht.sendmail.org (knecht.sendmail.org [209.31.233.160]) by hub.freebsd.org (Postfix) with ESMTP id 4A2BD151C1; Mon, 22 Mar 1999 19:23:35 -0800 (PST) (envelope-from mckusick@flamingo.McKusick.COM) Received: from flamingo.McKusick.COM (root@flamingo.mckusick.com [209.31.233.178]) by knecht.sendmail.org (8.9.3/8.9.3) with ESMTP id TAA23624; Mon, 22 Mar 1999 19:23:16 -0800 (PST) Received: from flamingo.McKusick.COM (mckusick@localhost [127.0.0.1]) by flamingo.McKusick.COM (8.8.5/8.8.5) with ESMTP id SAA10662; Mon, 22 Mar 1999 18:29:11 -0800 (PST) Message-Id: <199903230229.SAA10662@flamingo.McKusick.COM> To: "Kenneth D. Merry" Subject: Re: quintuple softupdates panic in -stable Cc: stable@freebsd.org, dillon@freebsd.org In-reply-to: Your message of "Mon, 22 Mar 1999 14:51:10 MST." <199903222151.OAA68634@panzer.plutotech.com> Date: Mon, 22 Mar 1999 18:29:11 -0800 From: Kirk McKusick Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From: "Kenneth D. Merry" Subject: quintuple softupdates panic in -stable To: stable@FreeBSD.ORG Date: Mon, 22 Mar 1999 14:51:10 -0700 (MST) Cc: mckusick@mckusick.com, dillon@FreeBSD.ORG I just got this panic on a very heavily loaded -stable server. It is RELENG_3 as of about March 10th. I noticed that Kirk checked in some softupdates bug fixes on March 1st/2nd, but they didn't go into RELENG_3. I'm not sure if this panic would be fixed by those changes. I wasn't able to compile a kernel with debugging symbols that would correspond to the one that was running on the machine in question, so there are no symbols. Sorry. Ken -- Kenneth Merry ken@plutotech.com ... panic: allocdirect_check: old 0 != new 397448 || lbn 12 >= 12 I have never gotten this panic before. The fixes that I put in in early March would probably not have prevented it (though unless I knew what did cause this panic, I can't say that with complete assurance). At any rate, it would be very useful if you could reproducce this panic with a symbolled kernel. For starters, I would like to know the contents of oldadp and newadp (the second and third parameters to allocdirect_merge). It would also be useful to see the elments on the list headed by adphead (the first parameter to allocdirect_merge). The follow-on panics are the usual trash that crops up when trying to sync the filesystem while in the middle of a soft updates panic. Kirk McKusick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 22 19:32:57 1999 Delivered-To: freebsd-stable@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 455E814DA7 for ; Mon, 22 Mar 1999 19:32:56 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id TAA44885; Mon, 22 Mar 1999 19:32:14 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Mike Meyer Cc: stable@FreeBSD.ORG Subject: Re: Musings about tracking FreeBSD... In-reply-to: Your message of "Mon, 22 Mar 1999 12:11:22 PST." Date: Mon, 22 Mar 1999 19:32:14 -0800 Message-ID: <44883.922159934@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG OK, not to be overly presumptuous or anything, but I think I can sum up this whole thread by simply stating what my wish list has always been in this regard: In my ideal FreeBSD, each and every software component installed anywhere on a permanently mounted hard disk has been installed through a common interface which treats the whole collection of bits, regardless of where it resides, as fundmentally under its [the package system's] control. Even when bits come in via some back way (a 3rd party's errant installer, perhaps), there is an option to tell the system to go "own" them after the fact which is easy to use and fairly intelligent (e.g. it can even be done automatically via a nightly/weekly/... inventory scan). This central accounting mechanism buys the user various CVS-like operations on binary filesets including occlusion detection and "push-down", dependency checking and auto-loading, history (roll-back) information going as far back as free space permits, etc. The average user never upgrades a specific software component so much as they "subscribe" to a given branch for some period of time of their own choosing, and during which time the "upgrade" command simply runs out and grabs whatever new components the user needs by comparing remote and local inventory lists of what is installed and what is available on some given mirror site. Since full history information is kept, the user can even do "crazy" things like jump from 3.1 to 4.0-current, ride that for awhile, and then decide to jump back to 3.1-stable. Since upgrading a package like "bin" (which is now also itself composed of many smaller binary package sets) stores push-back information for the version being upgraded from, moving to 4.0-current never destroys the 3.1 binaries which were there before. Getting back is a simple matter of requesting an Undo on the 4.0-current binary upgrade package, bringing you back to 3.1. Then one could install the latest 3.1-stable bin upgrade from the 3.1-stable snapshot package building machine and voila, now up to the very latest 3.1-stable. For the more fastidious at heart, it is also possible to prune the 4.0-current experience completely from the history mechanism so that it appears as if a direct 3.1 to 3.1-stable upgrade occurred. Since everything is a package in my ideal FreeBSD, bin is also no different from bash as far as the package system is concerned, except perhaps that bash happens to depend on (some subcomponent of) bin and not vice-versa. Since storage prices have fallen into the $10/GB range and the history mechanism allows dynamic allocation of the "history buffer", that is to say it prunes old history information when more space is desired by new package or upgrade than currently exists, most users are willing to keep a lot of history around and that means that upgrades can now become fully automatic. Not only are they fully automatic, but they change the way users fundamentally regard upgrades. If one finds that one's "fvwm" has suddenly stopped working, for example, but this wasn't noticed for several weeks and many nightly upgrades, all is not lost, you just ask the package system to push fvwm back to whatever state it was in a week ago and then you add it to the auto-upgrade exception list using the package manager. Voila, one working fvwm that won't just stop working again on your next auto-upgrade. If at some later time you decide to test the waters again, you can also just ask for fvwm specifically to be upgraded and see if it works. If not, you just back up again and wait a little longer. Being the single gate through which all software gets on a FreeBSD system, the new package system allows for a very flexible number of styles and has abstracted the concept of "user input" enough that it can be gotten in a wide variety of ways, including being driven via non-interactive scripts. For the power-user, everything is handled by the hyperkinetic GUI-front-ended package handling system from hell which lets you inspect your current inventory at a glance, (potentially) upgrade all or some of it from FTP/NFS/UFS/CD/DOS/carrier pigeon media, view dependency trees, clone one system from another, you name it. For the hacker, there's an extensive API of functions for frobbing the package system via one's own front-end interfaces or writing TCL/PERL scripts that use packages in clever ways, etc. There are also extensive hooks for setting security policy, a package being potentially confined to installing things only under certain sub-trees or supporting only a restricted number of setup options - everything the package does in talking to the user or modifying the system is done via secure TCL (it's my dream, I get to choose the scripting language, OK? :-) so that built-ins can be disabled or redirected depending on the outer "security environment" that the package add routines are excuting in. For the beginning user, there's basically just one command which does a big Q&A session once with the user and then remembers it all in order to be as fire-and-forget from there on out as possible. To configure a system they type setup, a command which presents some basic menus created by calling the configuration hooks directly inside the various registered packages. This makes the configuration menu structure something which is highly tailored to the user's exact installation - what they don't have, they don't see configuration information for (and vice-versa). The package tools also helps the tech support people considerably in that they're able to get a comprehensive inventory of everything on a system as well as anything potentially not listed in that inventory or modified from the last time an inventory was taken. It's essentially tripwire, CVS, pkg_info and emacs (just checking to see if you're paying attention) all rolled into one and, of course, it rocks because, well, it's the ideal FreeBSD we're talkin' about here. :-) Waking up and coming back to the real world for a moment here, I can say that some of this packaging technology exists now but is still in a very green state and requires egcs to compile due to its more advanced use of C++ than 2.7.2.x can handle. It also requires Turbovision and/or Qt as interface back-end libraries and both need to be egcs compiled to work properly. All of this makes it a bit hard to release it for general play-time and it's really also not quite to the state of being ready for peer-review yet in any case, so that's why it's not been more widely released. Even with the work that's been done to date and the work we're immediately contemplating, however, it's still a pale fraction of the "wish list reality" I depict above. That's where I'd really like to *get* to, not where I expect to get to right away (unless a lot of people become suddenly infected with the idea and start coding like possessed maniacs, I guess). :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 22 19:51:42 1999 Delivered-To: freebsd-stable@freebsd.org Received: from nefertiti.lightningweb.com (nefertiti.lightningweb.com [198.68.191.157]) by hub.freebsd.org (Postfix) with ESMTP id 297AD1529D; Mon, 22 Mar 1999 19:51:39 -0800 (PST) (envelope-from keith@lightningweb.com) Received: from localhost (keith@localhost) by nefertiti.lightningweb.com (8.8.7/8.8.5) with SMTP id TAA19541; Mon, 22 Mar 1999 19:53:42 -0800 (PST) Date: Mon, 22 Mar 1999 19:53:42 -0800 (PST) From: Keith Woodman To: freebsd-chat@freebsd.org Cc: freebsd-stable@freebsd.org Subject: Re: fixit.flp NOW 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 Well. To follow up, It wasn't the passwd at all. Went up single user after just doing a flip of the switch to turn the machine off. Came up single user. fsck and mount the devices. Did a vipw. checked for oddeties. All looks fine. Made sure that /etc/login.access wasn't all screwy and disallowing console logins or some stupid thing. I rebooted properly this time. Came up ok. loged in as root. Did a cd /etc and got an error saying. cd: RESTRICTED and didn't allow me to change directories. As if I were running bash -r or something. The last little ouch is that none of the other system users are noticed by the system at all. Even as root trying to do a passwd fails telling me there is no such user. This is very telling. I'm not entirely sure how at the moment as I am getting a nice radiation tan from sitting in front of this monitor so dang long today. Oh well, geuss I can be glad it was a test machine. Any pointers out there are appreciated. Keith ---------------------------------------------------------------------- Keith Woodman Technical Coordinator Keith@lightningweb.com Lightningweb LLC pid 7962 (sniffit), uid 0: exited on signal 10 (core dumped) ---------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 22 20:45:16 1999 Delivered-To: freebsd-stable@freebsd.org Received: from tick.ssec.wisc.edu (tick.ssec.wisc.edu [144.92.108.121]) by hub.freebsd.org (Postfix) with ESMTP id B063E14D31 for ; Mon, 22 Mar 1999 20:45:13 -0800 (PST) (envelope-from dglo@tick.ssec.wisc.edu) Received: from tick.ssec.wisc.edu (localhost [127.0.0.1]) by tick.ssec.wisc.edu (8.8.7/8.8.7) with ESMTP id WAA17794; Mon, 22 Mar 1999 22:44:44 -0600 (CST) From: Dave Glowacki Message-Id: <199903230444.WAA17794@tick.ssec.wisc.edu> To: John Baldwin Cc: Mike Meyer , stable@freebsd.org Subject: Re: Musings about tracking FreeBSD... In-reply-to: Your message of "Mon, 22 Mar 1999 21:01:23 EST." Date: Mon, 22 Mar 1999 22:44:38 -0600 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I have a very simple shell script that greps /usr/ports/INDEX to find ports > that need updating. It does have the rare false alarm (namely pgp-2.6.2). Bruce Mah's Perl script in /usr/ports/sysutils/pkg_version does this, too. > Also, I find that /usr/ports/INDEX isn't always up to date with the rest of the > ports tree, occasionally producing another false alarm, but these are easy to > find by just checking the version in the respective ports Makefile. You can also fix the out-of-date /usr/ports/INDEX problem by doing a "make index" in /usr/ports, but this gives your disk a MAJOR workout and takes a while to complete, so the fix might be worse than the problem. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 22 22:39: 1 1999 Delivered-To: freebsd-stable@freebsd.org Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (Postfix) with ESMTP id 637551536E; Mon, 22 Mar 1999 22:38:57 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.3/8.8.5) id XAA71643; Mon, 22 Mar 1999 23:38:34 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199903230638.XAA71643@panzer.plutotech.com> Subject: Re: quintuple softupdates panic in -stable In-Reply-To: <199903230229.SAA10662@flamingo.McKusick.COM> from Kirk McKusick at "Mar 22, 1999 6:29:11 pm" To: mckusick@McKusick.COM (Kirk McKusick) Date: Mon, 22 Mar 1999 23:38:33 -0700 (MST) Cc: stable@freebsd.org, dillon@freebsd.org X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kirk McKusick wrote... > From: "Kenneth D. Merry" > Subject: quintuple softupdates panic in -stable > To: stable@FreeBSD.ORG > Date: Mon, 22 Mar 1999 14:51:10 -0700 (MST) > Cc: mckusick@mckusick.com, dillon@FreeBSD.ORG > > I just got this panic on a very heavily loaded -stable > server. It is RELENG_3 as of about March 10th. > > I noticed that Kirk checked in some softupdates bug fixes > on March 1st/2nd, but they didn't go into RELENG_3. I'm > not sure if this panic would be fixed by those changes. > > I wasn't able to compile a kernel with debugging symbols > that would correspond to the one that was running on the > machine in question, so there are no symbols. Sorry. > > Ken > -- > Kenneth Merry > ken@plutotech.com > > ... > > panic: allocdirect_check: old 0 != new 397448 || lbn 12 >= 12 > > I have never gotten this panic before. The fixes that I put in in > early March would probably not have prevented it (though unless I > knew what did cause this panic, I can't say that with complete > assurance). At any rate, it would be very useful if you could > reproducce this panic with a symbolled kernel. For starters, I > would like to know the contents of oldadp and newadp (the second > and third parameters to allocdirect_merge). It would also be > useful to see the elments on the list headed by adphead (the > first parameter to allocdirect_merge). The follow-on panics are > the usual trash that crops up when trying to sync the filesystem > while in the middle of a soft updates panic. Okay, I believe I have managed to recompile a debugging kernel using the same sources and from the same path. It seems like the symbols are more or less okay. I think I should also mention that at the time the panic occurred, one of the partitions (out of 5) with softupdates enabled had filled up under primarily NFS write activity. I suppose that could make a difference. If you want more information from this core dump, just let me know. If you'd like me to install another kernel and see if I get another panic, let me know as well. I'll need to schedule downtime for the server ahead of time to install the kernel. Thanks, Ken -- Kenneth Merry ken@plutotech.com ============================================================================= gdb -k kernel.debug /var/crash/vmcore.4 GDB is free software and you are welcome to 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. GDB 4.16 (i386-unknown-freebsd), Copyright 1996 Free Software Foundation, Inc... IdlePTD 2813952 initial pcb at 241958 panicstr: softdep_disk_write_complete: lock is held panic messages: --- panic: allocdirect_check: old 0 != new 397448 || lbn 12 >= 12 syncing disks... panic: softdep_lock: locking against myself panic: softdep_disk_write_complete: lock is held panic: softdep_disk_write_complete: lock is held panic: softdep_disk_write_complete: lock is held dumping to dev 20401, offset 327680 dump 128 127 126 125 124 123 122 121 120 119 118 117 116 115 114 113 112 111 110 109 108 107 106 105 104 103 102 101 100 99 98 97 96 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 boot (howto=260) at ../../kern/kern_shutdown.c:285 285 dumppcb.pcb_cr3 = rcr3(); (kgdb) where #0 boot (howto=260) at ../../kern/kern_shutdown.c:285 #1 0xf0146548 in at_shutdown ( function=0xf02255f8 <__set_sysctl__debug_sym_sysctl___debug_rush_requests+2020>, arg=0xf5a6db20, queue=-173614304) at ../../kern/kern_shutdown.c:446 #2 0xf01d414b in softdep_disk_write_complete (bp=0xf5a6db20) at ../../ufs/ffs/ffs_softdep.c:2931 #3 0xf01658c5 in biodone (bp=0xf5a6db20) at ../../kern/vfs_bio.c:1911 #4 0xf0120f79 in dadone (periph=0xf3113180, done_ccb=0xf31c1600) at ../../cam/scsi/scsi_da.c:1313 #5 0xf011cca3 in camisr (queue=0xf0240cc4) at ../../cam/cam_xpt.c:6001 #6 0xf011ca99 in swi_cambio () at ../../cam/cam_xpt.c:5905 #7 0xf011a194 in xpt_polled_action (start_ccb=0xf9d10da8) at ../../cam/cam_xpt.c:3217 #8 0xf0121445 in dashutdown (howto=260, arg=0x0) at ../../cam/scsi/scsi_da.c:1603 #9 0xf0146297 in boot (howto=260) at ../../kern/kern_shutdown.c:280 #10 0xf0146548 in at_shutdown ( function=0xf02255f8 <__set_sysctl__debug_sym_sysctl___debug_rush_requests+2020>, arg=0xf5a886f0, queue=-173504784) at ../../kern/kern_shutdown.c:446 #11 0xf01d414b in softdep_disk_write_complete (bp=0xf5a886f0) at ../../ufs/ffs/ffs_softdep.c:2931 #12 0xf01658c5 in biodone (bp=0xf5a886f0) at ../../kern/vfs_bio.c:1911 #13 0xf0120f79 in dadone (periph=0xf3113180, done_ccb=0xf3394200) at ../../cam/scsi/scsi_da.c:1313 #14 0xf011cca3 in camisr (queue=0xf0240cc4) at ../../cam/cam_xpt.c:6001 #15 0xf011ca99 in swi_cambio () at ../../cam/cam_xpt.c:5905 #16 0xf011a194 in xpt_polled_action (start_ccb=0xf9d11284) at ../../cam/cam_xpt.c:3217 #17 0xf0121445 in dashutdown (howto=260, arg=0x0) at ../../cam/scsi/scsi_da.c:1603 #18 0xf0146297 in boot (howto=260) at ../../kern/kern_shutdown.c:280 #19 0xf0146548 in at_shutdown ( function=0xf02255f8 <__set_sysctl__debug_sym_sysctl___debug_rush_requests+2020>, arg=0xf5a31358, queue=-173862056) at ../../kern/kern_shutdown.c:446 #20 0xf01d414b in softdep_disk_write_complete (bp=0xf5a31358) at ../../ufs/ffs/ffs_softdep.c:2931 #21 0xf01658c5 in biodone (bp=0xf5a31358) at ../../kern/vfs_bio.c:1911 #22 0xf0120f79 in dadone (periph=0xf3113180, done_ccb=0xf3397800) at ../../cam/scsi/scsi_da.c:1313 #23 0xf011cca3 in camisr (queue=0xf0240cc4) at ../../cam/cam_xpt.c:6001 #24 0xf011ca99 in swi_cambio () at ../../cam/cam_xpt.c:5905 #25 0xf011a194 in xpt_polled_action (start_ccb=0xf9d11760) at ../../cam/cam_xpt.c:3217 #26 0xf0121445 in dashutdown (howto=260, arg=0x0) at ../../cam/scsi/scsi_da.c:1603 #27 0xf0146297 in boot (howto=260) at ../../kern/kern_shutdown.c:280 #28 0xf0146548 in at_shutdown ( function=0xf0224c1c <__set_sysuninit_set_sym_M_DIRREM_uninit_sys_uninit+4>, arg=0xf6555900, queue=-103736980) at ../../kern/kern_shutdown.c:446 #29 0xf01d112f in acquire_lock (lk=0xf02399e0) at ../../ufs/ffs/ffs_softdep.c:264 #30 0xf01d3f4f in initiate_write_inodeblock (inodedep=0xf3a99b80, bp=0xf5a2e518) at ../../ufs/ffs/ffs_softdep.c:2821 #31 0xf01d3cd3 in softdep_disk_io_initiation (bp=0xf5a2e518) at ../../ufs/ffs/ffs_softdep.c:2680 #32 0xf01766b9 in spec_strategy (ap=0xf9d119c8) at ../../miscfs/specfs/spec_vnops.c:539 #33 0xf0175e81 in spec_vnoperate (ap=0xf9d119c8) at ../../miscfs/specfs/spec_vnops.c:129 #34 0xf01df489 in ufs_vnoperatespec (ap=0xf9d119c8) at ../../ufs/ufs/ufs_vnops.c:2312 #35 0xf0163aff in bwrite (bp=0xf5a2e518) at vnode_if.h:891 #36 0xf016814e in vop_stdbwrite (ap=0xf9d11a30) at ../../kern/vfs_default.c:296 #37 0xf0167f99 in vop_defaultop (ap=0xf9d11a30) at ../../kern/vfs_default.c:130 #38 0xf0175e81 in spec_vnoperate (ap=0xf9d11a30) at ../../miscfs/specfs/spec_vnops.c:129 #39 0xf01df489 in ufs_vnoperatespec (ap=0xf9d11a30) at ../../ufs/ufs/ufs_vnops.c:2312 #40 0xf016453c in vfs_bio_awrite (bp=0xf5a2e518) at vnode_if.h:1145 #41 0xf01d909a in ffs_fsync (ap=0xf9d11a94) at ../../ufs/ffs/ffs_vnops.c:205 #42 0xf01d7544 in ffs_sync (mp=0xf311c000, waitfor=2, cred=0xf075b000, p=0xf025f118) at vnode_if.h:499 #43 0xf016ca43 in sync (p=0xf025f118, uap=0x0) at ../../kern/vfs_syscalls.c:549 #44 0xf0146119 in boot (howto=256) at ../../kern/kern_shutdown.c:203 #45 0xf0146548 in at_shutdown ( function=0xf022500b <__set_sysctl__debug_sym_sysctl___debug_rush_requests+503>, arg=0x0, queue=397448) at ../../kern/kern_shutdown.c:446 #46 0xf01d216b in allocdirect_merge (adphead=0xf35eecc4, newadp=0xf32d1ec0, oldadp=0xf3691bc0) at ../../ufs/ffs/ffs_softdep.c:1264 #47 0xf01d4d15 in merge_inode_lists (inodedep=0xf35eec80) at ../../ufs/ffs/ffs_softdep.c:3555 #48 0xf01d4bdc in softdep_update_inodeblock (ip=0xf33d2600, bp=0xf5a946e0, waitfor=0) at ../../ufs/ffs/ffs_softdep.c:3503 #49 0xf01d01e4 in ffs_update (vp=0xfa1d0e40, waitfor=0) at ../../ufs/ffs/ffs_inode.c:105 #50 0xf01d9f25 in ufs_inactive (ap=0xf9d11c00) at ../../ufs/ufs/ufs_inode.c:92 #51 0xf01df459 in ufs_vnoperate (ap=0xf9d11c00) at ../../ufs/ufs/ufs_vnops.c:2294 #52 0xf016abab in vput (vp=0xfa1d0e40) at vnode_if.h:767 #53 0xf019dbc6 in nfsrv_write (nfsd=0xf38d0700, slp=0xf30da300, procp=0xf9cd0c80, mrq=0xf9d11e1c) at ../../nfs/nfs_serv.c:906 #54 0xf01b3a88 in nfssvc_nfsd (nsd=0xf9d11e7c, argp=0x8071d9c
, p=0xf9cd0c80) at ../../nfs/nfs_syscalls.c:656 #55 0xf01b3385 in nfssvc (p=0xf9cd0c80, uap=0xf9d11f84) at ../../nfs/nfs_syscalls.c:342 #56 0xf0203a88 in syscall (frame={tf_es = 39, tf_ds = 39, tf_edi = 20, tf_esi = 0, tf_ebp = -272638524, tf_isp = -103735340, tf_ebx = 0, tf_edx = -272638920, tf_ecx = 0, tf_eax = 155, tf_trapno = 12, tf_err = 2, tf_eip = 134519060, tf_cs = 31, tf_eflags = 642, tf_esp = -272638912, tf_ss = 39}) at ../../i386/i386/trap.c:1118 #57 0xf01fa41c in Xint0x80_syscall () #58 0x80480e9 in ?? () (kgdb) up 46 #46 0xf01d216b in allocdirect_merge (adphead=0xf35eecc4, newadp=0xf32d1ec0, oldadp=0xf3691bc0) at ../../ufs/ffs/ffs_softdep.c:1264 1264 panic("allocdirect_check: old %d != new %d || lbn %ld >= %d", (kgdb) list 1259 panic("allocdirect_merge: lock not held"); 1260 #endif 1261 if (newadp->ad_oldblkno != oldadp->ad_newblkno || 1262 newadp->ad_oldsize != oldadp->ad_newsize || 1263 newadp->ad_lbn >= NDADDR) 1264 panic("allocdirect_check: old %d != new %d || lbn %ld >= %d", 1265 newadp->ad_oldblkno, oldadp->ad_newblkno, newadp->ad_lbn, 1266 NDADDR); 1267 newadp->ad_oldblkno = oldadp->ad_oldblkno; 1268 newadp->ad_oldsize = oldadp->ad_oldsize; (kgdb) print oldadp $1 = (struct allocdirect *) 0x0 (kgdb) print newadp $2 = (struct allocdirect *) 0x0 (kgdb) print (struct allocdirect *)0xf32d1ec0 $3 = (struct allocdirect *) 0xf32d1ec0 (kgdb) print *((struct allocdirect *)0xf32d1ec0) $4 = {ad_list = {wk_list = {le_next = 0xf3691bc0, le_prev = 0xf5aaba04}, wk_type = 4, wk_state = 32769}, ad_next = {tqe_next = 0xf3691bc0, tqe_prev = 0xf35eecc4}, ad_lbn = 12, ad_newblkno = 397448, ad_oldblkno = 0, ad_newsize = 8192, ad_oldsize = 0, ad_deps = { le_next = 0xf3691bc0, le_prev = 0xf31c8310}, ad_buf = 0xf5ab1438, ad_inodedep = 0xf35eec80, ad_freefrag = 0x0} (kgdb) print *((struct allocdirect *)0xf3691bc0) $5 = {ad_list = {wk_list = {le_next = 0x0, le_prev = 0xf32d1ec0}, wk_type = 4, wk_state = 32769}, ad_next = {tqe_next = 0x0, tqe_prev = 0xf32d1ecc}, ad_lbn = 12, ad_newblkno = 397448, ad_oldblkno = 0, ad_newsize = 8192, ad_oldsize = 0, ad_deps = {le_next = 0x0, le_prev = 0xf32d1ee8}, ad_buf = 0xf5ab1438, ad_inodedep = 0xf35eec80, ad_freefrag = 0x0} (kgdb) print adphead $6 = (struct allocdirectlst *) 0xf35eecc4 (kgdb) print *adphead $7 = {tqh_first = 0xf32d1ec0, tqh_last = 0xf3691bcc} (kgdb) print *adphead->tqh_first $8 = {ad_list = {wk_list = {le_next = 0xf3691bc0, le_prev = 0xf5aaba04}, wk_type = 4, wk_state = 32769}, ad_next = {tqe_next = 0xf3691bc0, tqe_prev = 0xf35eecc4}, ad_lbn = 12, ad_newblkno = 397448, ad_oldblkno = 0, ad_newsize = 8192, ad_oldsize = 0, ad_deps = { le_next = 0xf3691bc0, le_prev = 0xf31c8310}, ad_buf = 0xf5ab1438, ad_inodedep = 0xf35eec80, ad_freefrag = 0x0} (kgdb) print *adphead->tqh_first.ad_next->tqe_next $9 = {ad_list = {wk_list = {le_next = 0x0, le_prev = 0xf32d1ec0}, wk_type = 4, wk_state = 32769}, ad_next = {tqe_next = 0x0, tqe_prev = 0xf32d1ecc}, ad_lbn = 12, ad_newblkno = 397448, ad_oldblkno = 0, ad_newsize = 8192, ad_oldsize = 0, ad_deps = {le_next = 0x0, le_prev = 0xf32d1ee8}, ad_buf = 0xf5ab1438, ad_inodedep = 0xf35eec80, ad_freefrag = 0x0} To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 22 23:13:19 1999 Delivered-To: freebsd-stable@freebsd.org Received: from freebie.dcfinc.com (freebie.dcfinc.com [138.113.5.128]) by hub.freebsd.org (Postfix) with ESMTP id 9E2BC1532C for ; Mon, 22 Mar 1999 23:13:16 -0800 (PST) (envelope-from chad@freebie.dcfinc.com) Received: (from chad@localhost) by freebie.dcfinc.com (8.8.7/8.8.3a) id AAA08064; Tue, 23 Mar 1999 00:12:04 -0700 (MST) From: "Chad R. Larson" Message-Id: <199903230712.AAA08064@freebie.dcfinc.com> Subject: Re: Musings about tracking FreeBSD... To: dglo@SSEC.WISC.EDU (Dave Glowacki) Date: Tue, 23 Mar 1999 00:12:04 -0700 (MST) Cc: jobaldwi@vt.edu, mwm@phone.net, stable@FreeBSD.ORG In-Reply-To: <199903230444.WAA17794@tick.ssec.wisc.edu> from Dave Glowacki at "Mar 22, 99 10:44:38 pm" Reply-To: chad@dcfinc.com X-unexpected: The Spanish Inquisition X-Mailer: ELM [version 2.4ME+ PL22 (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 > You can also fix the out-of-date /usr/ports/INDEX problem by doing a > "make index" in /usr/ports, but this gives your disk a MAJOR workout > and takes a while to complete, so the fix might be worse than the problem. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Generating INDEX - please wait..syntax error in file /usr/ports/Tools/make_index at line 16, next 2 tokens "my $name " syntax error in file /usr/ports/Tools/make_index at line 26, next 2 tokens "my @f" syntax error in file /usr/ports/Tools/make_index at line 34, next 2 tokens "my $pkg " syntax error in file /usr/ports/Tools/make_index at line 35, next 2 tokens "->" syntax error in file /usr/ports/Tools/make_index at line 39, next 2 tokens "my @deps" syntax error in file /usr/ports/Tools/make_index at line 40, next 2 tokens "@$pkg" Execution of /usr/ports/Tools/make_index aborted due to compilation errors. *** Error code 255 Stop. *** Error code 1 Stop. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org chad@anasazi.com 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 Mar 22 23:17:39 1999 Delivered-To: freebsd-stable@freebsd.org Received: from stampede.cs.berkeley.edu (stampede.CS.Berkeley.EDU [128.32.45.124]) by hub.freebsd.org (Postfix) with ESMTP id 27EED14C4E for ; Mon, 22 Mar 1999 23:17:37 -0800 (PST) (envelope-from asami@cs.berkeley.edu) Received: from silvia.hip.berkeley.edu (sji-ca41-149.ix.netcom.com [209.111.208.149]) by stampede.cs.berkeley.edu (8.8.7/8.7.3) with ESMTP id XAA29947; Mon, 22 Mar 1999 23:17:10 -0800 (PST) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.9.2/8.6.9) id XAA34661; Mon, 22 Mar 1999 23:16:59 -0800 (PST) Date: Mon, 22 Mar 1999 23:16:59 -0800 (PST) Message-Id: <199903230716.XAA34661@silvia.hip.berkeley.edu> X-Authentication-Warning: silvia.hip.berkeley.edu: asami set sender to asami@cs.berkeley.edu using -f To: chad@dcfinc.com Cc: dglo@SSEC.WISC.EDU, jobaldwi@vt.edu, mwm@phone.net, stable@FreeBSD.ORG In-reply-to: <199903230712.AAA08064@freebie.dcfinc.com> (chad@freebie.dcfinc.com) Subject: Re: Musings about tracking FreeBSD... From: asami@FreeBSD.ORG (Satoshi Asami) References: <199903230712.AAA08064@freebie.dcfinc.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * From: "Chad R. Larson" * Generating INDEX - please wait..syntax error in file /usr/ports/Tools/make_index at line 16, next 2 tokens "my $name " You need perl5 to regenerate the index. Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Mar 22 23:25:57 1999 Delivered-To: freebsd-stable@freebsd.org Received: from login-2.eunet.no (login-2.eunet.no [193.71.71.239]) by hub.freebsd.org (Postfix) with ESMTP id 2845A1536C; Mon, 22 Mar 1999 23:25:20 -0800 (PST) (envelope-from mbendiks@eunet.no) Received: from login-1.eunet.no (mbendiks@login-1.eunet.no [193.71.71.238]) by login-2.eunet.no (8.9.3/8.9.0/GN) with ESMTP id IAA19932; Tue, 23 Mar 1999 08:24:59 +0100 (CET) Received: from localhost (mbendiks@localhost) by login-1.eunet.no (8.8.8/8.8.8) with ESMTP id IAA28338; Tue, 23 Mar 1999 08:24:59 +0100 (CET) (envelope-from mbendiks@eunet.no) X-Authentication-Warning: login-1.eunet.no: mbendiks owned process doing -bs Date: Tue, 23 Mar 1999 08:24:59 +0100 (CET) From: Marius Bendiksen To: Keith Woodman Cc: freebsd-chat@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: fixit.flp NOW 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 > other system users are noticed by the system at all. Even as root trying > to do a passwd fails telling me there is no such user. This is Are you sure you've rebuilt the password-database? IIRC, passwd is just a text-frontend to it, which doesn't represent the real data. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 23 0:42:50 1999 Delivered-To: freebsd-stable@freebsd.org Received: from luke.cpl.net (luke.cpl.net [209.150.92.68]) by hub.freebsd.org (Postfix) with ESMTP id 5924D14CE7 for ; Tue, 23 Mar 1999 00:42:48 -0800 (PST) (envelope-from shawn@luke.cpl.net) Received: (from shawn@localhost) by luke.cpl.net (8.8.8/8.8.8) id AAA17778 for stable@freebsd.org; Tue, 23 Mar 1999 00:44:11 -0800 (PST) Message-ID: <19990323004411.A6977@cpl.net> Date: Tue, 23 Mar 1999 00:44:11 -0800 From: Shawn Ramsey To: stable@freebsd.org Subject: compile error Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Mailer: Mutt 0.93i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -L/usr/X11R6/lib -lX11 tty.o: In function =16ideo_setborder': tty.o(.text+0x274): undefined reference to etWindowBackground' tty.o: In function =13etgc': tty.o(.text+0x319): undefined reference to angeGC' tty.o: In function =16ideo_update': tty.o(.text+0x52d): undefined reference to awImageString' tty.o(.text+0x5b5): undefined reference to awImageString' tty.o(.text+0x6a2): undefined reference to angeGC' tty.o(.text+0x719): undefined reference to llRectangle' tty.o(.text+0x7d2): undefined reference to angeGC' tty.o(.text+0x804): undefined reference to llRectangle' tty.o(.text+0x812): undefined reference to ush' tty.o: In function =04ebug_event': tty.o(.text+0xcbe): undefined reference to =BEll' tty.o(.text+0xcc9): undefined reference to ush' tty.o: In function =16ideo_async_event': tty.o(.text+0x13ab): undefined reference to ush' tty.o(.text+0x13c3): undefined reference to extEvent' tty.o(.text+0x1437): undefined reference to ush' tty.o(.text+0x1470): undefined reference to extEvent' tty.o: In function =16ideo_event': tty.o(.text+0x1a29): undefined reference to ookupString' tty.o(.text+0x1c09): undefined reference to ookupString' tty.o: In function =14ty_write': tty.o(.text+0x2b92): undefined reference to =BEll' tty.o: In function =0BbdWrite': tty.o(.text+0x3548): undefined reference to =BEll' tty.o: In function =16ideo_init': tty.o(.text+0x38c8): undefined reference to penDisplay' tty.o(.text+0x38fd): undefined reference to splayName' tty.o(.text+0x39d9): undefined reference to locNamedColor' tty.o(.text+0x3a30): undefined reference to oadQueryFont' tty.o(.text+0x3a4c): undefined reference to oadQueryFont' tty.o(.text+0x3b1a): undefined reference to eateSimpleWindow' tty.o(.text+0x3b7d): undefined reference to eateGC' tty.o(.text+0x3bb4): undefined reference to eateGC' tty.o(.text+0x3bd1): undefined reference to etNormalHints' tty.o(.text+0x3c02): undefined reference to electInput' tty.o(.text+0x3c16): undefined reference to apWindow' tty.o(.text+0x3c21): undefined reference to ush' *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Trying to do "make upgrade" .... cvsup'd as of about 4pm today, RELENG_3.= =20 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 23 0:47:59 1999 Delivered-To: freebsd-stable@freebsd.org Received: from bamboo.verinet.com (bamboo.verinet.com [204.144.246.5]) by hub.freebsd.org (Postfix) with ESMTP id 9C30D15305 for ; Tue, 23 Mar 1999 00:47:49 -0800 (PST) (envelope-from allenc@verinet.com) Received: from struct. (allenc.verinet.com [199.45.180.181]) by bamboo.verinet.com (8.8.8/8.7.1) with ESMTP id BAA04294; Tue, 23 Mar 1999 01:47:28 -0700 Received: from verinet.com (localhost [127.0.0.1]) by struct. (8.9.2/8.9.2) with ESMTP id BAA00689; Tue, 23 Mar 1999 01:47:12 -0700 (MST) (envelope-from allenc@verinet.com) Message-ID: <36F75510.10809BA8@verinet.com> Date: Tue, 23 Mar 1999 01:47:12 -0700 From: Allen Campbell X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 3.1-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: "Jordan K. Hubbard" Cc: stable@FreeBSD.ORG Subject: Re: Musings about tracking FreeBSD... References: <44883.922159934@zippy.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 > Waking up and coming back to the real world for a moment here, I can > say that some of this packaging technology exists now but is still in > a very green state and requires egcs to compile due to its more > advanced use of C++ than 2.7.2.x can handle. It also requires > Turbovision and/or Qt as interface back-end libraries and both need to > be egcs compiled to work properly. All of this makes it a bit hard to > release it for general play-time and it's really also not quite to the > state of being ready for peer-review yet in any case, so that's why > it's not been more widely released. Even with the work that's been > done to date and the work we're immediately contemplating, however, > it's still a pale fraction of the "wish list reality" I depict above. > That's where I'd really like to *get* to, not where I expect to get to > right away (unless a lot of people become suddenly infected with the > idea and start coding like possessed maniacs, I guess). :) Release it and let's see. I am really pleased to see these tools (EGCS, QT and TV) being used despite the difficulty it poses for distribution. A little risk in the form of a break with convention is warranted and a great deal could be achieved. I would guess you have endured some criticism on this point although I have no way to know. I think the payoff will be worth it; contemporary tools will make a difference, if only to inspire those who would care to put them to use. There are several dozen rather productive 'possessed maniacs' over at kde.org. I often wonder how much of this is due to QT. I know this; QT and EGCS (w/STL) are what keep me up late. I can see TurboVision doing that too :) Release it and let's see. What thought has gone into the next 'official' compiler? I would like to think the GCC-2.8.x branch could be skipped. By all accounts, EGCS-1.1.x is at least as stable, and considerably farther along the standards track. -- Allen Campbell | Lurking at the bottom of the allenc@verinet.com | gravity well, getting old. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 23 2:14:10 1999 Delivered-To: freebsd-stable@freebsd.org Received: from wins0.win.org (WinS0.win.org [204.184.50.200]) by hub.freebsd.org (Postfix) with ESMTP id 25E3F152C2 for ; Tue, 23 Mar 1999 02:13:38 -0800 (PST) (envelope-from jase@clearsail.net) Received: from clearsail.net (win-pd-cs1-14.win.org [204.184.50.62]) by wins0.win.org (8.9.1a/8.9.1) with ESMTP id EAA02349 for ; Tue, 23 Mar 1999 04:13:10 -0600 (CST) Message-ID: <36F76950.9681B350@clearsail.net> Date: Tue, 23 Mar 1999 04:13:37 -0600 From: Jason McNew X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 3.1-STABLE i386) X-Accept-Language: ja MIME-Version: 1.0 To: stable@freebsd.org Subject: Perl File::Find problem Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm trying to use the File::Find module in Perl 5 and for some reason it refuses to search through my fat32 mouted dirs. Observe the folowing code: use File::Find; &find(\&ismp3, '/d','/c','/usr/home'); sub ismp3 { if(/mp3/i) { push @mp3list, $File:Find:name; } } It works exactly as expect but only under /usr/home. It quietly skips over /c and /d which are both fat32 partitions. After removing the '/usr/home' for testing, I found that it claims to have searched /c and /d in under .2 seconds, when using `find /c` as I used to do usually takes a full 80 seconds. I checked to make sure that they are in fact mounted; they are. I'm not sure if it's aproblem with the module it's self or in the way it interacts with the os. I'm running FreeBSD 3.0-stable CVSup'ed about 3 days ago and using the version of perl compiled with it (5.002_02). Any ideas? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 23 2:52:52 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.palmerharvey.co.uk (mail.palmerharvey.co.uk [62.172.109.58]) by hub.freebsd.org (Postfix) with ESMTP id DA44E14E10 for ; Tue, 23 Mar 1999 02:52:47 -0800 (PST) (envelope-from Dom.Mitchell@palmerharvey.co.uk) Received: from ho-nt-01.pandhm.co.uk (unverified) by mail.palmerharvey.co.uk (Content Technologies SMTPRS 2.0.15) with ESMTP id ; Tue, 23 Mar 1999 10:52:36 +0000 Received: from voodoo.pandhm.co.uk ([10.100.35.12]) by ho-nt-01.pandhm.co.uk with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2448.0) id GZL8KC85; Tue, 23 Mar 1999 10:46:02 -0000 Received: from dom by voodoo.pandhm.co.uk with local (Exim 2.10 #1) id 10POqH-00008J-00; Tue, 23 Mar 1999 10:55:29 +0000 To: Jason McNew Cc: stable@freebsd.org Subject: Re: Perl File::Find problem X-Mailer: nmh-1.0 X-Colour: Green Organization: Palmer & Harvey McLane In-Reply-To: Jason McNew's message of "Tue, 23 Mar 1999 04:13:37 CST" <36F76950.9681B350@clearsail.net> Date: Tue, 23 Mar 1999 10:55:29 +0000 From: Dom Mitchell Message-Id: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 23 March 1999, Jason McNew proclaimed: > I'm trying to use the File::Find module in Perl 5 and for some reason it > refuses to search through my fat32 mouted dirs. Observe the folowing > code: > > use File::Find; > &find(\&ismp3, '/d','/c','/usr/home'); > > sub ismp3 { > if(/mp3/i) { push @mp3list, $File:Find:name; } > } > > It works exactly as expect but only under /usr/home. It quietly skips > over /c and /d which are both fat32 partitions. After removing the > '/usr/home' for testing, I found that it claims to have searched /c and > /d in under .2 seconds, when using `find /c` as I used to do usually > takes a full 80 seconds. > I checked to make sure that they are in fact mounted; they are. I'm not > sure if it's aproblem with the module it's self or in the way it > interacts with the os. I'm running FreeBSD 3.0-stable CVSup'ed about 3 > days ago and using the version of perl compiled with it (5.002_02). Any > ideas? Try running the whole thing under ktrace(1) to see what's really going on. Off the top of my head, it may be the same problem that find used to have on older Unix systems, where it didn't like cd9660 filesystems, because the link count on the directory was wrong. It's been such a long time since I've looked inside a FAT filesystem, that I have no ideas whether or not this would be the case. -- Dom Mitchell -- Palmer & Harvey McLane -- Unix Systems Administrator "Anybody who can paint a fence Tinky-Winky purple is alright in my book." -- LLB -- ********************************************************************** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. ********************************************************************** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 23 3:55:18 1999 Delivered-To: freebsd-stable@freebsd.org Received: from ns.raditex.se (raditex.thorsen.se [193.14.93.200]) by hub.freebsd.org (Postfix) with ESMTP id 217C114D61 for ; Tue, 23 Mar 1999 03:55:10 -0800 (PST) (envelope-from kaj@raditex.se) Received: from localhost (dialup204-4-43.swipnet.se [130.244.204.235]) by ns.raditex.se (8.8.8/8.8.8) with ESMTP id MAA01358; Tue, 23 Mar 1999 12:54:44 +0100 (CET) (envelope-from kaj@raditex.se) To: jase@clearsail.net Cc: stable@FreeBSD.ORG Cc: Rasmus Kaj Subject: Re: Perl File::Find problem From: Rasmus Kaj In-Reply-To: Your message of "Tue, 23 Mar 1999 04:13:37 -0600" <36F76950.9681B350@clearsail.net> References: <36F76950.9681B350@clearsail.net> X-Mailer: Mew version 1.93 on XEmacs 20.4 (Emerald) X-URL: http://www.e.kth.se/~kaj/ X-Phone: +46 (0)8 - 692 35 09 X-Attribution: Kaj X-Face: M9cR~WYav<"fu%MaslX0`43PAYY?uIsM8[#E(0\Xuy9rj>4gE\h3jm.7DD?]R8*^7T\o&vT U@[53Dwkuup4[0@gw#~kyu>`unH?kVj9CJa02(h>Ki\+i=%rn%sDf^KC.!?IHkKjMAbkd\jgmphp^' d|Q;OeXEAhq?ybGqOs1CHb6TJT42'C`Krnk61//AOfXtNjj/t'`5>Vw0QX!dKfOL$.f+S"LIuwR<;I Z0Qnnx(F^F]o@*V%TUtEV'1Z[TkOl^FFV9Z~A[b19%}uP*,huCU Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19990323125613D.kaj@raditex.se> Date: Tue, 23 Mar 1999 12:56:13 +0100 X-Dispatcher: imput version 980905(IM100) Lines: 27 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "JM" == Jason McNew writes: JM> I'm trying to use the File::Find module in Perl 5 and for some reason it JM> refuses to search through my fat32 mouted dirs. Observe the folowing JM> code: JM> use File::Find; JM> &find(\&ismp3, '/d','/c','/usr/home'); JM> sub ismp3 { JM> if(/mp3/i) { push @mp3list, $File:Find:name; } JM> } JM> It works exactly as expect but only under /usr/home. Maybe the perl find won't descend mountpoints by default? I guess /d and /c are mountpoints, but /usr/home is a common directory? If so, try to use "&find(\&ismp3, '/d/.','/c/.','/usr/home');". I've seen another suggestion from Dom Mitchell in another mail, that might be it also ... -- Rasmus Kaj ---------------- rasmus@kaj.a.se - http://www.e.kth.se/~kaj/ \ If you think I'm talking about the future you're living in the past \--------------------------------------------- http://www.Raditex.se/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 23 4:58: 0 1999 Delivered-To: freebsd-stable@freebsd.org Received: from wins0.win.org (WinS0.win.org [204.184.50.200]) by hub.freebsd.org (Postfix) with ESMTP id 480D214C32 for ; Tue, 23 Mar 1999 04:57:58 -0800 (PST) (envelope-from jase@clearsail.net) Received: from clearsail.net (win-pd-cs1-13.win.org [204.184.50.61]) by wins0.win.org (8.9.1a/8.9.1) with ESMTP id GAA15814; Tue, 23 Mar 1999 06:57:31 -0600 (CST) Message-ID: <36F78FD9.9143B702@clearsail.net> Date: Tue, 23 Mar 1999 06:58:01 -0600 From: Jason McNew X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 3.1-STABLE i386) X-Accept-Language: ja MIME-Version: 1.0 To: Dom Mitchell Cc: stable@freebsd.org Subject: Re: Perl File::Find problem References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dom Mitchell wrote: > On 23 March 1999, Jason McNew proclaimed: > > I'm trying to use the File::Find module in Perl 5 and for some reason it > > refuses to search through my fat32 mouted dirs. Observe the folowing > > code: > > > > use File::Find; > > &find(\&ismp3, '/d','/c','/usr/home'); > > > > sub ismp3 { > > if(/mp3/i) { push @mp3list, $File:Find:name; } > > } > > > > It works exactly as expect but only under /usr/home. It quietly skips > > over /c and /d which are both fat32 partitions. After removing the > > '/usr/home' for testing, I found that it claims to have searched /c and > > /d in under .2 seconds, when using `find /c` as I used to do usually > > takes a full 80 seconds. > > I checked to make sure that they are in fact mounted; they are. I'm not > > sure if it's aproblem with the module it's self or in the way it > > interacts with the os. I'm running FreeBSD 3.0-stable CVSup'ed about 3 > > days ago and using the version of perl compiled with it (5.002_02). Any > > ideas? > > Try running the whole thing under ktrace(1) to see what's really going > on. Off the top of my head, it may be the same problem that find used > to have on older Unix systems, where it didn't like cd9660 filesystems, > because the link count on the directory was wrong. It's been such a > long time since I've looked inside a FAT filesystem, that I have no > ideas whether or not this would be the case. > -- Yes, that's it. lstat is returing 1 as the nlink count any directory, and the module uses $subdirs = $nlink - 2 then thinks there are no subdirs because $subdirs = -1. The fix is to define $File::Find::dont_use_nlink as the pod suggests if your using AFS. I have no idea what AFS is, but defining that works. I should probably notify the perl people though. Thanks for the tip. :) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 23 5:10:33 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 2032C1530B for ; Tue, 23 Mar 1999 05:10:28 -0800 (PST) (envelope-from spud@i.am) Received: from john (RAS1-p19.hfa.netvision.net.il [62.0.145.19]) by alpha.netvision.net.il (8.8.6/8.8.6) with SMTP id PAA04163 for ; Tue, 23 Mar 1999 15:06:10 +0200 (IST) Message-ID: <001901be752d$0bc6ab20$1391003e@john> From: "Tomer Weller" To: Subject: weird terminal/modem problem ? Date: Tue, 23 Mar 1999 14:59:52 +0200 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0016_01BE753D.CE39C560" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.37 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.37 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0016_01BE753D.CE39C560 Content-Type: text/plain; charset="iso-8859-8" Content-Transfer-Encoding: quoted-printable here's my problem, whenever i enter a terminal connected to my modem i = have a strange problem, when i write a char i can't see it being written, i = can only see it when i enter another char, and so on and so on, to see the = char i just put i have to put another char, though the char performs it's = duty without being seen and that leads to many problems with ppp ("expect" in scripts doesn't work), i dont know what to do, maybe u can help me ? BTW, works fine in win98. and worked fine in 2.2.7.=20 ------=_NextPart_000_0016_01BE753D.CE39C560 Content-Type: text/html; charset="iso-8859-8" Content-Transfer-Encoding: quoted-printable
here's my problem, whenever i enter a terminal connected to my = modem i=20 have
a strange problem, when i write a char i can't see it being = written, i=20 can
only see it when i enter another char, and so on and so on, to = see the=20 char
i just put i have to put another char, though the char performs = it's=20 duty
without being seen and that leads to many problems with ppp=20 ("expect" in
scripts doesn't work), i dont know what to do, = maybe u=20 can help me ?

BTW, works fine in win98. and worked fine in 2.2.7. =
------=_NextPart_000_0016_01BE753D.CE39C560-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 23 5:56: 7 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.palmerharvey.co.uk (mail.palmerharvey.co.uk [62.172.109.58]) by hub.freebsd.org (Postfix) with ESMTP id 25D6514D41 for ; Tue, 23 Mar 1999 05:55:39 -0800 (PST) (envelope-from Dom.Mitchell@palmerharvey.co.uk) Received: from ho-nt-01.pandhm.co.uk (unverified) by mail.palmerharvey.co.uk (Content Technologies SMTPRS 2.0.15) with ESMTP id ; Tue, 23 Mar 1999 13:55:28 +0000 Received: from voodoo.pandhm.co.uk ([10.100.35.12]) by ho-nt-01.pandhm.co.uk with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2448.0) id GZL8KDAM; Tue, 23 Mar 1999 13:48:54 -0000 Received: from dom by voodoo.pandhm.co.uk with local (Exim 2.10 #1) id 10PRhF-0000JY-00; Tue, 23 Mar 1999 13:58:21 +0000 To: Jason McNew Cc: stable@freebsd.org Subject: Re: Perl File::Find problem X-Mailer: nmh-1.0 X-Colour: Green Organization: Palmer & Harvey McLane In-Reply-To: Jason McNew's message of "Tue, 23 Mar 1999 06:58:01 CST" <36F78FD9.9143B702@clearsail.net> Date: Tue, 23 Mar 1999 13:58:21 +0000 From: Dom Mitchell Message-Id: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 23 March 1999, Jason McNew proclaimed: > Yes, that's it. lstat is returing 1 as the nlink count any directory, and the > module uses $subdirs = $nlink - 2 then thinks there are no subdirs because > $subdirs = -1. > The fix is to define $File::Find::dont_use_nlink as the pod suggests if your > using AFS. I have no idea what AFS is, but defining that works. > I should probably notify the perl people though. Thanks for the tip. :) AFS is the Andrew File System. Originally developed at CMU, it's now being sold by TransArc. It was designed as a wide-area filesystem with much better performance than NFS. Coda is a free follow-on, which is available for modern FreeBSD systems. Have a look at http://www.coda.cs.cmu.edu/ (I think). -- Dom Mitchell -- Palmer & Harvey McLane -- Unix Systems Administrator "Anybody who can paint a fence Tinky-Winky purple is alright in my book." -- LLB -- ********************************************************************** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. ********************************************************************** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 23 6:40:31 1999 Delivered-To: freebsd-stable@freebsd.org Received: from harmony.williams.edu (harmony.williams.edu [137.165.4.25]) by hub.freebsd.org (Postfix) with ESMTP id 6E2EF153B4 for ; Tue, 23 Mar 1999 06:40:27 -0800 (PST) (envelope-from sachs@cs.williams.edu) Received: from bull.cs.williams.edu by williams.edu (PMDF V5.1-10 #24595) with ESMTP id <0F910020TY2WFZ@williams.edu> for freebsd-stable@freebsd.org; Tue, 23 Mar 1999 09:40:08 -0500 (EST) Received: from hamburger.cs.williams.edu (hamburger [137.165.8.59]) by bull.cs.williams.edu (8.9.0/8.9.0) with ESMTP id JAA22050 for ; Tue, 23 Mar 1999 09:40:07 -0500 (EST) Received: (from sachs@localhost) by hamburger.cs.williams.edu (8.8.8/8.8.8) id JAA28674; Tue, 23 Mar 1999 09:40:10 -0500 Date: Tue, 23 Mar 1999 09:40:10 -0500 From: Jay Sachs Subject: error making aout-to-elf-buildworld To: freebsd-stable@freebsd.org Message-id: MIME-version: 1.0 (generated by tm-edit 7.108) X-Mailer: Gnus v5.6.45/XEmacs 20.4 - "Emerald" Content-type: text/plain; charset=US-ASCII X-Face: 6!-I&o^[[HP+0~O~}d2Zf@Pbof:|>j5^*W$QOR"&)JYcHT.@-"AhAXLg3vioV79Ri3JMp/a e3QD@Z$1Ot@'j1/A Lines: 54 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is on a 2.2.8-stable box, and occurred during the build of the elfworld using the aout tools. It appears that doscmd is requiring either 1) a more recent XFree86 or 2) an ELF XFree86. But the real question is why is X required at all to build world? Sources were 'supped 3 days ago. -Jay cc -O -pipe -I. -I/usr/X11R6/include -DDISASSEMBLER -I/usr/obj/elf/base/src/tmp/usr/include -o doscmd AsyncIO.o ParseBuffer.o bios.o callback.o cpu.o dos.o cmos.o config.o cwd.o debug.o disktab.o doscmd.o ems.o emuint.o exe.o i386-pinsn.o int.o int10.o int13.o int14.o int16.o int17.o int1a.o int2f.o intff.o mem.o mouse.o net.o port.o setver.o signal.o timer.o trace.o trap.o tty.o xms.o -L/usr/X11R6/lib -lX11 tty.o: In function `video_setborder': tty.o(.text+0x25f): undefined reference to `XSetWindowBackground' tty.o: In function `setgc': tty.o(.text+0x2f5): undefined reference to `XChangeGC' tty.o: In function `video_update': tty.o(.text+0x50e): undefined reference to `XDrawImageString' tty.o(.text+0x597): undefined reference to `XDrawImageString' tty.o(.text+0x68a): undefined reference to `XChangeGC' tty.o(.text+0x712): undefined reference to `XFillRectangle' tty.o(.text+0x7be): undefined reference to `XChangeGC' tty.o(.text+0x7fb): undefined reference to `XFillRectangle' tty.o(.text+0x809): undefined reference to `XFlush' tty.o: In function `debug_event': tty.o(.text+0xc48): undefined reference to `XBell' tty.o(.text+0xc53): undefined reference to `XFlush' tty.o: In function `video_async_event': tty.o(.text+0x1233): undefined reference to `XFlush' tty.o(.text+0x124b): undefined reference to `XNextEvent' tty.o(.text+0x12c7): undefined reference to `XFlush' tty.o(.text+0x12fc): undefined reference to `XNextEvent' tty.o: In function `video_event': tty.o(.text+0x17f4): undefined reference to `XLookupString' tty.o(.text+0x1978): undefined reference to `XLookupString' tty.o: In function `tty_write': tty.o(.text+0x27fe): undefined reference to `XBell' tty.o: In function `KbdWrite': tty.o(.text+0x3083): undefined reference to `XBell' tty.o: In function `video_init': tty.o(.text+0x33e1): undefined reference to `XOpenDisplay' tty.o(.text+0x3408): undefined reference to `XDisplayName' tty.o(.text+0x34df): undefined reference to `XAllocNamedColor' tty.o(.text+0x3532): undefined reference to `XLoadQueryFont' tty.o(.text+0x354e): undefined reference to `XLoadQueryFont' tty.o(.text+0x3629): undefined reference to `XCreateSimpleWindow' tty.o(.text+0x368c): undefined reference to `XCreateGC' tty.o(.text+0x36c3): undefined reference to `XCreateGC' tty.o(.text+0x36e0): undefined reference to `XSetNormalHints' tty.o(.text+0x370a): undefined reference to `XSelectInput' tty.o(.text+0x371e): undefined reference to `XMapWindow' tty.o(.text+0x3729): undefined reference to `XFlush' *** Error code 1 Stop. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 23 6:44:19 1999 Delivered-To: freebsd-stable@freebsd.org Received: from pi.yip.org (yip.org [142.154.6.140]) by hub.freebsd.org (Postfix) with ESMTP id 0F5EE14FA7 for ; Tue, 23 Mar 1999 06:44:12 -0800 (PST) (envelope-from melange@yip.org) Received: from localhost (melange@localhost) by pi.yip.org (8.9.2/8.9.2) with ESMTP id JAA30322 for ; Tue, 23 Mar 1999 09:46:26 -0500 (EST) (envelope-from melange@yip.org) Date: Tue, 23 Mar 1999 09:46:26 -0500 (EST) From: Bob K To: freebsd-stable@FreeBSD.ORG Subject: Re: 24-character usernames? In-Reply-To: <199903222108.WAA18769@dorifer.heim3.tu-clausthal.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 22 Mar 1999, Oliver Fromme wrote: > Bob K wrote in list.freebsd-stable: > > I recently wanted to try out 24-character usernames on my system. So, > > following the man page for adduser, I changed UT_NAMESIZE in > > /usr/include/utmp.h to 24 from the default of 16. I then changed > > MAXLOGNAME in /usr/include/sys/param.h to 25, as per the comments in both > > utmp.h and param.h. I then made buildworld && make installworld (-j4 -O > > -pipe only) and a new kernel (-O -pipe), and then built the various ports > > that would need it. > > Did you change it in /usr/include only? If I'm not mistaken, > you have to change it in /usr/src/include before doing a make > world (otherwise it doesn't really take effect). Ah. I think I did after the 2nd cvsup. One thing to note is that changing it in /usr/src/include is mentioned in the handbook, but not in the manpages for adduser (which only mentions making the world). I'll cvsup today and make world again after making totally sure I have that in there before starting. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 23 7:30:59 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 2DD9614E89 for ; Tue, 23 Mar 1999 07:30:57 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id AAA06919; Wed, 24 Mar 1999 00:30:52 +0900 (JST) Message-ID: <36F79807.898E95D0@newsguy.com> Date: Tue, 23 Mar 1999 22:32:55 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: "Jordan K. Hubbard" Cc: Mike Meyer , stable@FreeBSD.ORG Subject: Re: Musings about tracking FreeBSD... References: <44883.922159934@zippy.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jordan K. Hubbard" wrote: > > Waking up and coming back to the real world for a moment here, I can > say that some of this packaging technology exists now but is still in > a very green state and requires egcs to compile due to its more > advanced use of C++ than 2.7.2.x can handle. It also requires > Turbovision and/or Qt as interface back-end libraries and both need to > be egcs compiled to work properly. All of this makes it a bit hard to > release it for general play-time and it's really also not quite to the > state of being ready for peer-review yet in any case, so that's why > it's not been more widely released. Even with the work that's been > done to date and the work we're immediately contemplating, however, > it's still a pale fraction of the "wish list reality" I depict above. > That's where I'd really like to *get* to, not where I expect to get to > right away (unless a lot of people become suddenly infected with the > idea and start coding like possessed maniacs, I guess). :) It's a lack of soul, really. We just don't have the amount of souls the Devil would ask for that. :-) -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "Someone's trying to hack into our server." "Wow... How flattering!" "I know. There must be some mistake." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 23 7:42: 9 1999 Delivered-To: freebsd-stable@freebsd.org Received: from abe.hymarc.com (homer.hymarc.com [206.191.28.71]) by hub.freebsd.org (Postfix) with ESMTP id A8B7015232 for ; Tue, 23 Mar 1999 07:41:50 -0800 (PST) (envelope-from rleir@hymarc.com) Received: from moe.hymarc.com (moe.hymarc.com [89.0.0.5]) by abe.hymarc.com (8.8.7/8.8.7) with SMTP id KAA22749 for <@abe.hymarc.com:stable@freebsd.org>; Tue, 23 Mar 1999 10:41:45 -0500 Received: from lisa.hymarc.com (lisa.hymarc.com [89.0.0.35]) by moe.hymarc.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id KAA14021 for <@moe.hymarc.com:stable@freebsd.org>; Tue, 23 Mar 1999 10:41:37 -0500 Received: from hymarc.com (localhost.hymarc.com [127.0.0.1]) by lisa.hymarc.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id KAA09394 for ; Tue, 23 Mar 1999 10:41:35 -0500 Message-ID: <36F7B62F.A473A632@hymarc.com> Date: Tue, 23 Mar 1999 10:41:35 -0500 From: Rick Leir Organization: Hymarc 3D Vision Systems X-Mailer: Mozilla 4.5 [en] (X11; U; IRIX64 6.4 IP30) X-Accept-Language: en MIME-Version: 1.0 Cc: stable@freebsd.org Subject: Re: NFS problems with Solaris 2.6 Server 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 have also been seeing delays that could be due to NFS. I am using FreeBSD 3.1 Stable as a fileserver for SGI boxes, IRIX 5.n, 6.3, 6.5. What is the best way to monitor NFS? Tcpdump? I feel that I should capture more info before I open a Bugtraq item. Who is developing NFS, so I could help? Gerald Pfeifer wrote: > > On Tue, 16 Mar 1999, Daniel C. Sobral wrote: > >> Is there something so serious in 3.1 to deserve another release ? > > A *LOT* of potential deadlock conditions and NFS bugs were corrected. > > Which brings me to another point: Are there any known issues between > FreeBSD 3.1 clients and Solaris 2.6 servers? > > We had no problems with FreeBSD 2.2.x, but since we switched to 3.1, we > indeterministically experience extremely long NFS delays now and then. > > Delays in the range of a couple of minutes, that is! > > What kind were these NFS bugs that have been corrected in the meantime? > I checked the GNATS database, but failed to find anything relevant for > our situation. > Gerald "Jerry" pfeifer@dbai.tuwien.ac.at http://www.dbai.tuwien.ac.at/~pfeifer/ -- Rick Leir, Hymarc 3D Vision Systems (613) 727 1584 x214 Fast, precise laser scanners. http://www.hymarc.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 23 9:22:11 1999 Delivered-To: freebsd-stable@freebsd.org Received: from knecht.sendmail.org (knecht.sendmail.org [209.31.233.160]) by hub.freebsd.org (Postfix) with ESMTP id 93F6314E98; Tue, 23 Mar 1999 09:22:10 -0800 (PST) (envelope-from mckusick@flamingo.McKusick.COM) Received: from flamingo.McKusick.COM (root@flamingo.mckusick.com [209.31.233.178]) by knecht.sendmail.org (8.9.3/8.9.3) with ESMTP id JAA25375; Tue, 23 Mar 1999 09:21:51 -0800 (PST) Received: from flamingo.McKusick.COM (mckusick@localhost [127.0.0.1]) by flamingo.McKusick.COM (8.8.5/8.8.5) with ESMTP id IAA12174; Tue, 23 Mar 1999 08:20:19 -0800 (PST) Message-Id: <199903231620.IAA12174@flamingo.McKusick.COM> To: "Kenneth D. Merry" Subject: Re: quintuple softupdates panic in -stable Cc: stable@freebsd.org, dillon@freebsd.org In-reply-to: Your message of "Mon, 22 Mar 1999 23:38:33 MST." <199903230638.XAA71643@panzer.plutotech.com> Date: Tue, 23 Mar 1999 08:20:18 -0800 From: Kirk McKusick Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ahh, the key piece of information! The filesystem was full. There is a known bug that I am chasing related to full filesystems. Before progressing further on your bug, let me finish tracking that one down. Once I have a fix for that problem, we can install that fix and see if your problem recurs. Kirk McKusick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 23 9:30:13 1999 Delivered-To: freebsd-stable@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id ED27A14D41 for ; Tue, 23 Mar 1999 09:30:08 -0800 (PST) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.2/8.9.1) id SAA76161; Tue, 23 Mar 1999 18:29:44 +0100 (CET) (envelope-from des) To: Mike Meyer Cc: stable@FreeBSD.ORG Subject: Re: Build of 3.1-STABLE failing? References: From: Dag-Erling Smorgrav Date: 23 Mar 1999 18:29:43 +0100 In-Reply-To: Mike Meyer's message of "Sun, 21 Mar 1999 15:07:08 -0800 (PST)" Message-ID: Lines: 30 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Meyer writes: > On Sun, 21 Mar 1999, Daniel C. Sobral wrote: > > Running stable is preferable than release. But the targets are > > buildworld and installworld. > If you make regular backups of userland, that represents quite a bit > of work. Since it rebuilds everything in userland, you wind up dumping > all of userland with every backup, so you need to do some kind of > special backup after doing an installworld. Putting it all together, > that's enough work that I wouldn't bother doing it except every 6-8 > weeks. But -RELEASE happens about twice that often. What's the point > of tracking -STABLE under those conditions? Add the following line to /etc/make.conf: INSTALL=install -C > You mean - people who go in and edit the userland sources? Nuts - > that's one of the reasons I *started* tracking -STABLE. I kept hoping > the patches I submitted with pr bin/9429 would show up, as well as > some of the ports I've done and submitted. Who are you paying to commit them? As it is, 9429 was committed on Sunday. Granted, it's not the best turnaround time I've experienced, but it's a lot better than many commercial Unix vendors. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 23 9:35:13 1999 Delivered-To: freebsd-stable@freebsd.org Received: from guru.phone.net (guru.phone.net [209.157.82.120]) by hub.freebsd.org (Postfix) with SMTP id 7D1CB14C40 for ; Tue, 23 Mar 1999 09:35:12 -0800 (PST) (envelope-from mwm@phone.net) Received: (qmail 21402 invoked by uid 100); 23 Mar 1999 17:34:53 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 23 Mar 1999 17:34:53 -0000 Date: Tue, 23 Mar 1999 09:34:53 -0800 (PST) From: Mike Meyer To: stable@FreeBSD.ORG Subject: Re: Build of 3.1-STABLE failing? 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 23 Mar 1999, Dag-Erling Smorgrav wrote: > Add the following line to /etc/make.conf: > > INSTALL=install -C Already covered... > > You mean - people who go in and edit the userland sources? Nuts - > > that's one of the reasons I *started* tracking -STABLE. I kept hoping > > the patches I submitted with pr bin/9429 would show up, as well as > > some of the ports I've done and submitted. > > Who are you paying to commit them? Nobody. That's why I said "hoping", and why I don't complain about it. I'm fully cognizant of the time & resource issues surrounding free software. > As it is, 9429 was committed on Sunday. Granted, it's not the best > turnaround time I've experienced, but it's a lot better than many > commercial Unix vendors. Yeah, my mentioning it here seems to have tickled jkh to go look at it :-). ; Tue, 23 Mar 1999 09:38:26 -0800 (PST) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.2/8.9.1) id SAA76302; Tue, 23 Mar 1999 18:38:04 +0100 (CET) (envelope-from des) To: Mike Meyer Cc: stable@FreeBSD.ORG Subject: Re: Build of 3.1-STABLE failing? References: From: Dag-Erling Smorgrav Date: 23 Mar 1999 18:38:03 +0100 In-Reply-To: Mike Meyer's message of "Mon, 22 Mar 1999 11:42:52 -0800 (PST)" Message-ID: Lines: 15 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Meyer writes: > If you read the handbook on backups, you'll note that the recommended > backup tool is dump - because it's the only thing that does the job > right. Wrong. Dump relies on a number of assumptions which are only correct for quiescent (i.e. unmounted) file systems. If you want to use dump reliably, mirror your file system across two disks. Unmount one of them before dumping. Sync it up with the live one once the dump is complete, and remount. This procedure guarantees that the file system is in a stable, consistent state throughout the dump. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 23 9:45:40 1999 Delivered-To: freebsd-stable@freebsd.org Received: from guru.phone.net (guru.phone.net [209.157.82.120]) by hub.freebsd.org (Postfix) with SMTP id 63C0F14E42 for ; Tue, 23 Mar 1999 09:45:39 -0800 (PST) (envelope-from mwm@phone.net) Received: (qmail 21521 invoked by uid 100); 23 Mar 1999 17:45:20 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 23 Mar 1999 17:45:20 -0000 Date: Tue, 23 Mar 1999 09:45:20 -0800 (PST) From: Mike Meyer To: stable@FreeBSD.ORG Subject: Re: Build of 3.1-STABLE failing? 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 Are you saying there's some tool that does the job right while the system is active? If so, please let us know! Otherwise, my statement is correct. That I didn't mention what should be common knowledge doesn't mean I wasn't aware of it. In fact, having to have the system down to do the post-installworld dump is part of the problem. If you don't back the system up, the buildworld/installworld path isn't to bad. But I rely on my systems for my livelyhood, and am not willing to put my data at risk that way. Date: 23 Mar 1999 18:38:03 +0100 > From: Dag-Erling Smorgrav > To: Mike Meyer > Cc: stable@FreeBSD.ORG > Subject: Re: Build of 3.1-STABLE failing? > > Mike Meyer writes: > > If you read the handbook on backups, you'll note that the recommended > > backup tool is dump - because it's the only thing that does the job > > right. > > Wrong. Dump relies on a number of assumptions which are only correct > for quiescent (i.e. unmounted) file systems. If you want to use dump > reliably, mirror your file system across two disks. Unmount one of > them before dumping. Sync it up with the live one once the dump is > complete, and remount. This procedure guarantees that the file system > is in a stable, consistent state throughout the dump. > > DES > -- > Dag-Erling Smorgrav - des@flood.ping.uio.no > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 23 10:35:51 1999 Delivered-To: freebsd-stable@freebsd.org Received: from nefertiti.lightningweb.com (nefertiti.lightningweb.com [198.68.191.157]) by hub.freebsd.org (Postfix) with ESMTP id 0485815378; Tue, 23 Mar 1999 10:35:48 -0800 (PST) (envelope-from keith@lightningweb.com) Received: from localhost (keith@localhost) by nefertiti.lightningweb.com (8.8.7/8.8.5) with SMTP id KAA17287; Tue, 23 Mar 1999 10:37:16 -0800 (PST) Date: Tue, 23 Mar 1999 10:37:15 -0800 (PST) From: Keith Woodman To: Marius Bendiksen Cc: freebsd-chat@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: fixit.flp NOW 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 All is well, The most stupid mistake followed up with the stupidest mail ever. :-) A lesson to be learned.. Just got it all comfy cozy in sinlge user mode, rebuilt the db and rebooted. Doh ! Keith On Tue, 23 Mar 1999, Marius Bendiksen wrote: > > other system users are noticed by the system at all. Even as root trying > > to do a passwd fails telling me there is no such user. This is > > Are you sure you've rebuilt the password-database? IIRC, passwd is just a > text-frontend to it, which doesn't represent the real data. > > > > > 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 Mar 23 10:38:30 1999 Delivered-To: freebsd-stable@freebsd.org Received: from ensta.ensta.fr (ensta.ensta.fr [147.250.1.1]) by hub.freebsd.org (Postfix) with ESMTP id 00A6615378 for ; Tue, 23 Mar 1999 10:38:26 -0800 (PST) (envelope-from loyer@quickstep.ensta.fr) Received: from quickstep.ensta.fr (quickstep.ensta.fr [147.250.61.100]) by ensta.ensta.fr (8.9.1/8.9.1) with ESMTP id TAA08094; Tue, 23 Mar 1999 19:38:05 +0100 (CET) Received: (from loyer@localhost) by quickstep.ensta.fr (8.9.2/8.8.5) id UAA20478; Mon, 22 Mar 1999 20:04:08 +0100 (CET) From: Frederic LOYER Message-Id: <199903221904.UAA20478@quickstep.ensta.fr> Subject: Re: Strange Error Message In-Reply-To: <000001be7402$9766b5c0$0402030a@yiff.bunnynet.org> from Matt White at "Mar 21, 1999 8:23:28 pm" To: mwhite@donet.com (Matt White) Date: Mon, 22 Mar 1999 20:04:07 +0100 (CET) Cc: freebsd-stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hello... > > Today while copying a large number of files I started getting this error > message: > > inetd in realloc(): warning: junk pointer, too low to make sense. > inetd in free(): warning: junk pointer, too low to make sense. > > This is a -STABLE system, last cvsupped and built on the 20th of this month. > > Any idea what this means? It prevented me from logging in, whenever I'd try > to start up a telnet session it would toss those two lines to me and close > the session. (I was still able to ssh in, which is not started via inetd.) > > Thanks, > Matt I've found the same problem. This means there is a bug in "inetd" or one of the called libraries. Trying to work with a debugger is difficult since inetd crash after the fork(): you can't login but the "main" inetd process is still alive to answer the following connection... and crash again. It seems to happen in malloc() called from login_getclass()... but this doesn't tell us where the memory is screwed: there must be something wrong before the fork() since this error comes on *every* connection after the first error. It could be triggered by the folowing lines: comsat dgram udp wait tty:tty /usr/libexec/comsat comsat ntalk dgram udp wait tty:tty /usr/libexec/ntalkd ntalkd tty:tty is quite recent on -STABLE, and I don't remember seeing this error before updating /etc/inetd.conf. Anyway this error is too rare to be debugged easily (I can't reproduce it). -- Frederic Loyer To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 23 11:20:15 1999 Delivered-To: freebsd-stable@freebsd.org Received: from ns2.fda.net (unknown [209.144.107.7]) by hub.freebsd.org (Postfix) with ESMTP id 273ED14C83 for ; Tue, 23 Mar 1999 11:20:12 -0800 (PST) (envelope-from shellis@fda.net) Received: from fda.net (ts35p38.fda.net [209.144.107.151]) by ns2.fda.net (8.9.1/8.9.1) with ESMTP id LAA21628 for ; Tue, 23 Mar 1999 11:22:11 -0800 (PST) Message-ID: <36F7E940.E0870A1F@fda.net> Date: Tue, 23 Mar 1999 11:19:28 -0800 From: s Reply-To: shellis@fda.net Organization: t X-Mailer: Mozilla 4.04 [en] (Win95; U) MIME-Version: 1.0 To: FreeBSD-Stable@FreeBSD.ORG Subject: boot.flp and boot floppies Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dear Folks, Because I have several hard drives with several versions of FreeBSD for experimental purposes I use boot floppies for better control. I am having a problem with revision 3.1 because I cannot create a boot floppy on an ordinary 1.4 MB set of floppies. The floppy image is about 2.9 MB, and of course will not fit on a single floppy. When I use fdimage, I immediately get a diagnostic reminding me of this. Is there a version of fdimage or other utility that is built to split up the boot disk into 2 usable floppies? I contacted the technical support line, and they said that this was a new question to which they did not have an answer. They suggested that I mail you. I am writing an article on using FreeBSD for our scientific software Web page to entice people to try FreeBSD, along with some other promotional efforts I am trying for FreeBSD. Thanks for your kind attention and a wonderful operating system. Best regards, Steve Ellis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 23 11:29: 5 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mortar.carlson.com (mortar.carlson.com [208.240.12.98]) by hub.freebsd.org (Postfix) with ESMTP id A5C7514CB9 for ; Tue, 23 Mar 1999 11:28:01 -0800 (PST) (envelope-from veldy@visi.com) Received: from mortar.carlson.com (root@localhost) by mortar.carlson.com with ESMTP id NAA02081; Tue, 23 Mar 1999 13:27:27 -0600 (CST) Received: from w142844 ([172.25.99.35]) by mortar.carlson.com with SMTP id NAA02077; Tue, 23 Mar 1999 13:27:26 -0600 (CST) Message-ID: <01d501be7563$3f4b3ca0$236319ac@w142844.carlson.com> From: "Thomas T. Veldhouse" To: , Subject: Re: boot.flp and boot floppies Date: Tue, 23 Mar 1999 13:27:52 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 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 Use kern.flp and mfsroot.flp Tom Veldhouse veldy@visi.com -----Original Message----- From: s To: FreeBSD-Stable@FreeBSD.ORG Date: Tuesday, March 23, 1999 1:21 PM Subject: boot.flp and boot floppies >Dear Folks, > >Because I have several hard drives with several versions of FreeBSD for >experimental purposes I use boot floppies for better control. I am >having a problem with revision 3.1 because I cannot create a boot floppy >on an ordinary 1.4 MB set of floppies. The floppy image is about 2.9 >MB, and of course will not fit on a single floppy. When I use fdimage, >I immediately get a diagnostic reminding me of this. > >Is there a version of fdimage or other utility that is built to split up >the boot disk into 2 usable floppies? > >I contacted the technical support line, and they said that this was a >new question to which they did not have an answer. They suggested that >I mail you. > >I am writing an article on using FreeBSD for our scientific software Web >page to entice people to try FreeBSD, along with some other promotional >efforts I am trying for FreeBSD. > >Thanks for your kind attention and a wonderful operating system. > >Best regards, >Steve Ellis > > > >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 Mar 23 11:46:25 1999 Delivered-To: freebsd-stable@freebsd.org Received: from i.caniserv.com (i.caniserv.com [139.142.95.1]) by hub.freebsd.org (Postfix) with SMTP id B8ABF1538F for ; Tue, 23 Mar 1999 11:46:20 -0800 (PST) (envelope-from Darcy@ok-connect.com) Received: (qmail 103 invoked from network); 23 Mar 1999 19:45:57 -0000 Received: from ccliii.caniserv.com (HELO dbitech) (darcyb@139.142.95.253) by 139.142.95.10 with SMTP; 23 Mar 1999 19:45:57 -0000 Message-Id: <3.0.32.19990323114713.025eaec0@mail.ok-connect.com> X-Sender: darcyb@mail.ok-connect.com X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Tue, 23 Mar 1999 11:47:13 -0800 To: FreeBSD-Stable@FreeBSD.ORG From: Darcy Buskermolen Subject: Re: boot.flp and boot floppies Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A better option in my opinion would be to store the kernel on the drive and use the boot time options to boot form a specified device, ie: boot: wd(0,a)/kernel or boot: sd(1,a)/kernel >Use kern.flp and mfsroot.flp > >Tom Veldhouse >veldy@visi.com > >-----Original Message----- >From: s >To: FreeBSD-Stable@FreeBSD.ORG >Date: Tuesday, March 23, 1999 1:21 PM >Subject: boot.flp and boot floppies > > >>Dear Folks, >> >>Because I have several hard drives with several versions of FreeBSD for >>experimental purposes I use boot floppies for better control. I am >>having a problem with revision 3.1 because I cannot create a boot floppy >>on an ordinary 1.4 MB set of floppies. The floppy image is about 2.9 >>MB, and of course will not fit on a single floppy. When I use fdimage, >>I immediately get a diagnostic reminding me of this. >> >>Is there a version of fdimage or other utility that is built to split up >>the boot disk into 2 usable floppies? >> >>I contacted the technical support line, and they said that this was a >>new question to which they did not have an answer. They suggested that >>I mail you. >> >>I am writing an article on using FreeBSD for our scientific software Web >>page to entice people to try FreeBSD, along with some other promotional >>efforts I am trying for FreeBSD. >> >>Thanks for your kind attention and a wonderful operating system. >> >>Best regards, >>Steve Ellis >> >> >> >>To Unsubscribe: send mail to majordomo@FreeBSD.org >>with "unsubscribe freebsd-stable" in the body of the message >> > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-stable" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 23 11:46:41 1999 Delivered-To: freebsd-stable@freebsd.org Received: from hp9000.chc-chimes.com (hp9000.chc-chimes.com [206.67.97.84]) by hub.freebsd.org (Postfix) with ESMTP id 99D79153E7 for ; Tue, 23 Mar 1999 11:46:35 -0800 (PST) (envelope-from billf@chc-chimes.com) Received: from localhost by hp9000.chc-chimes.com with SMTP (1.39.111.2/16.2) id AA280326300; Tue, 23 Mar 1999 14:11:40 -0500 Date: Tue, 23 Mar 1999 14:11:40 -0500 (EST) From: Bill Fumerola To: Shawn Ramsey Cc: stable@FreeBSD.ORG Subject: Re: compile error In-Reply-To: <19990323004411.A6977@cpl.net> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 23 Mar 1999, Shawn Ramsey wrote: > -L/usr/X11R6/lib -lX11 > tty.o: In function =16ideo_setborder': > tty.o(.text+0x274): undefined reference to etWindowBackground' > tty.o: In function =13etgc': > tty.o(.text+0x319): undefined reference to angeGC' > tty.o: In function =16ideo_update': > tty.o(.text+0x52d): undefined reference to awImageString' > tty.o(.text+0x5b5): undefined reference to awImageString' > tty.o(.text+0x6a2): undefined reference to angeGC' > tty.o(.text+0x719): undefined reference to llRectangle' > tty.o(.text+0x7d2): undefined reference to angeGC' > tty.o(.text+0x804): undefined reference to llRectangle' > tty.o(.text+0x812): undefined reference to ush' > tty.o: In function =04ebug_event': > tty.o(.text+0xcbe): undefined reference to =BEll' > tty.o(.text+0xcc9): undefined reference to ush' > tty.o: In function =16ideo_async_event': > tty.o(.text+0x13ab): undefined reference to ush' > tty.o(.text+0x13c3): undefined reference to extEvent' > tty.o(.text+0x1437): undefined reference to ush' > tty.o(.text+0x1470): undefined reference to extEvent' > tty.o: In function =16ideo_event': > tty.o(.text+0x1a29): undefined reference to ookupString' > tty.o(.text+0x1c09): undefined reference to ookupString' > tty.o: In function =14ty_write': > tty.o(.text+0x2b92): undefined reference to =BEll' > tty.o: In function =0BbdWrite': > tty.o(.text+0x3548): undefined reference to =BEll' > tty.o: In function =16ideo_init': > tty.o(.text+0x38c8): undefined reference to penDisplay' > tty.o(.text+0x38fd): undefined reference to splayName' > tty.o(.text+0x39d9): undefined reference to locNamedColor' > tty.o(.text+0x3a30): undefined reference to oadQueryFont' > tty.o(.text+0x3a4c): undefined reference to oadQueryFont' > tty.o(.text+0x3b1a): undefined reference to eateSimpleWindow' > tty.o(.text+0x3b7d): undefined reference to eateGC' > tty.o(.text+0x3bb4): undefined reference to eateGC' > tty.o(.text+0x3bd1): undefined reference to etNormalHints' > tty.o(.text+0x3c02): undefined reference to electInput' > tty.o(.text+0x3c16): undefined reference to apWindow' > tty.o(.text+0x3c21): undefined reference to ush' > *** Error code 1 I recently got the same thing, it's important to note this is in doscmd, which looks not to be linking the right libraries. It's difficult to debug, because I just can't make the directory, because of the upgrade environment neccesary. - 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 Mar 23 12:45:44 1999 Delivered-To: freebsd-stable@freebsd.org Received: from horse.supranet.net (horse.supranet.net [205.164.160.8]) by hub.freebsd.org (Postfix) with ESMTP id 3756014D23 for ; Tue, 23 Mar 1999 12:45:37 -0800 (PST) (envelope-from gavinb@supranet.net) Received: from rat (rat.supranet.net [205.164.160.15]) by horse.supranet.net (8.9.3/8.9.3) with SMTP id OAA23176 for ; Tue, 23 Mar 1999 14:45:14 -0600 (CST) Message-Id: <4.1.19990323143242.00b423a0@mail.supranet.net> X-Sender: gavinb@mail.supranet.net X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Tue, 23 Mar 1999 14:46:23 -0600 To: freebsd-stable@freebsd.org From: Benjamin Gavin Subject: Username size limit suggestion Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, I believe that we can all agree that there is never going to be an agreed upon limit on the username size. I have just finished rebuilding my system to support 32-character usernames (I think, have to finish testing it). I have a suggestion and also a couple of questions. First the suggestion: Suggestion: I noticed that the adduser script has the 16 character limit hard-coded into the file. I was thinking that it might be a good idea to make that a configurable global variable or something of that sort (i.e. $UT_NAMESIZE, ala. sys/params.h, at the top of the file.) That way those of us who want longer names could easily change the variable and be done with it. I understand that it is probably done this way to force people to know what they are doing when they change it. Questions: 1. Are there performance issues relating the the length of the username? 2. Are these (listed below) the only changes necessary to get the new username length to be active: a. Have full source tree b. change src/sys/sys/params.h (#define UT_NAMESIZE) to reflect the new length c. change src/include/utmp.h (#define MAXLOGNAME (UT_NAMESIZE+1)) d. make world c. cat /dev/null > /var/log/wtmp d. cat /dev/null > /var/run/utmp e. cat /dev/null > /var/log/lastlog f. edit /usr/sbin/adduser (change 16 to whatever) d. recompile ports and other programs that use wtmp,utmp and lastlog Is that it?? I am going to be completing testing, but I am wondering what gotchas are waiting for me :)... Thanks, Ben Gavin /--------------------------------------------------------------------------/ Benjamin Gavin - Senior Consultant *********** NO SPAM!! ************ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 23 13:15:52 1999 Delivered-To: freebsd-stable@freebsd.org Received: from david.siemens.de (david.siemens.de [192.35.17.14]) by hub.freebsd.org (Postfix) with ESMTP id 5DD99153C6 for ; Tue, 23 Mar 1999 13:15:48 -0800 (PST) (envelope-from andre.albsmeier@mchp.siemens.de) X-Envelope-Sender-Is: andre.albsmeier@mchp.siemens.de (at relayer david.siemens.de) Received: from mail1.siemens.de (mail1.siemens.de [139.23.33.14]) by david.siemens.de (8.9.3/8.9.3) with ESMTP id WAA24076 for ; Tue, 23 Mar 1999 22:15:39 +0100 (MET) Received: from curry.mchp.siemens.de (curry.mchp.siemens.de [146.180.31.23]) by mail1.siemens.de (8.9.3/8.9.3) with ESMTP id WAA05269 for ; Tue, 23 Mar 1999 22:15:17 +0100 (MET) Received: (from daemon@localhost) by curry.mchp.siemens.de (8.8.8/8.8.8) id WAA19538 for ; Tue, 23 Mar 1999 22:15:28 +0100 (CET) Date: Tue, 23 Mar 1999 22:15:24 +0100 From: Andre Albsmeier To: freebsd-stable@freebsd.org Subject: Heavy MSDOS fs problems with floppies Message-ID: <19990323221524.A1760@internal> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am experiencing heavy problem when using MSDOS filesystems on floppies on 3.1-STABLE. When writing to a write protected floppy, the system crashed and rebooted. When copying lots of files from the mounted floppy to the local harddrive the systems freezed after a while; no mouse movement, only the reset button helped. I am not using mtools, I am mounting with -t msdos... Anybody else has seen this? Thanks, -Andre To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 23 13:28:31 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mortar.carlson.com (mortar.carlson.com [208.240.12.98]) by hub.freebsd.org (Postfix) with ESMTP id BFEA014E66 for ; Tue, 23 Mar 1999 13:28:23 -0800 (PST) (envelope-from veldy@visi.com) Received: from mortar.carlson.com (root@localhost) by mortar.carlson.com with ESMTP id PAA02658; Tue, 23 Mar 1999 15:27:51 -0600 (CST) Received: from w142844 ([172.25.99.35]) by mortar.carlson.com with SMTP id PAA02654; Tue, 23 Mar 1999 15:27:50 -0600 (CST) Message-ID: <020b01be7574$12459a00$236319ac@w142844.carlson.com> From: "Thomas T. Veldhouse" To: "Andre Albsmeier" , Subject: Re: Heavy MSDOS fs problems with floppies Date: Tue, 23 Mar 1999 15:28:18 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 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 It has been around for a while. Try this: Insert a write protected floppy disk: dd if=/dev/zero of=/dev/fd0 bs=4096 count=10 I am sure this will crash your system too. If it doesn't try increasing the count. ;-] I thought that they had fixed this - have you built the world lately? Tom Veldhouse veldy@visi.com -----Original Message----- From: Andre Albsmeier To: freebsd-stable@FreeBSD.ORG Date: Tuesday, March 23, 1999 3:16 PM Subject: Heavy MSDOS fs problems with floppies >I am experiencing heavy problem when using MSDOS filesystems >on floppies on 3.1-STABLE. When writing to a write protected floppy, >the system crashed and rebooted. When copying lots of files from >the mounted floppy to the local harddrive the systems freezed after >a while; no mouse movement, only the reset button helped. > >I am not using mtools, I am mounting with -t msdos... > >Anybody else has seen this? > >Thanks, > > -Andre > > >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 Mar 23 14: 2: 3 1999 Delivered-To: freebsd-stable@freebsd.org Received: from diamond.ripn.net (diamond.ripn.net [195.19.26.76]) by hub.freebsd.org (Postfix) with ESMTP id 0D88C14C56 for ; Tue, 23 Mar 1999 14:01:52 -0800 (PST) (envelope-from ilya@diamond.ripn.net) Received: (from ilya@localhost) by diamond.ripn.net (8.9.2/8.9.2) id BAA30776; Wed, 24 Mar 1999 01:01:16 +0300 (MSK) (envelope-from ilya) Message-Id: <199903232201.BAA30776@diamond.ripn.net> Subject: Re: Possible bug in syslog? In-Reply-To: from Mike Meyer at "Mar 22, 1999 1:47: 9 pm" To: mwm@phone.net (Mike Meyer) Date: Wed, 24 Mar 1999 01:01:15 +0300 (MSK) Cc: stable@FreeBSD.ORG From: Ilya Varlashkin X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Mike Meyer: > I noticed what I think is a problem. If your syslog is sending log > messages to a machine that you've shut down (for example, to do a > "make installworld" on it), it stops logging until you restart it. Is > this a bug? If so, I'll look into fixing it. If not, I can switch to > the daemontools port. it would be great if syslog'd be able to queue (most likely to disk) unsent messages and re-resend them as soon as loghost become available again. but it seems to be quite complex task. -- Ilya Varlashkin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 23 14:25:16 1999 Delivered-To: freebsd-stable@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id 227E115052 for ; Tue, 23 Mar 1999 14:25:15 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id OAA00879; Tue, 23 Mar 1999 14:18:33 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199903232218.OAA00879@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: shellis@fda.net Cc: FreeBSD-Stable@FreeBSD.ORG Subject: Re: boot.flp and boot floppies In-reply-to: Your message of "Tue, 23 Mar 1999 11:19:28 PST." <36F7E940.E0870A1F@fda.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 23 Mar 1999 14:18:33 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG If you install the new (4.x) bootblocks on all your setups, you can actually boot directly from disk without needing any floppies at all. > Because I have several hard drives with several versions of FreeBSD for > experimental purposes I use boot floppies for better control. I am > having a problem with revision 3.1 because I cannot create a boot floppy > on an ordinary 1.4 MB set of floppies. The floppy image is about 2.9 > MB, and of course will not fit on a single floppy. When I use fdimage, > I immediately get a diagnostic reminding me of this. > > Is there a version of fdimage or other utility that is built to split up > the boot disk into 2 usable floppies? > > I contacted the technical support line, and they said that this was a > new question to which they did not have an answer. They suggested that > I mail you. > > I am writing an article on using FreeBSD for our scientific software Web > page to entice people to try FreeBSD, along with some other promotional > efforts I am trying for FreeBSD. > > Thanks for your kind attention and a wonderful operating system. > > Best regards, > Steve Ellis > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ 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 Mar 23 16:13:12 1999 Delivered-To: freebsd-stable@freebsd.org Received: from pi.yip.org (yip.org [142.154.6.140]) by hub.freebsd.org (Postfix) with ESMTP id 55BD814BEC for ; Tue, 23 Mar 1999 16:12:47 -0800 (PST) (envelope-from melange@yip.org) Received: from localhost (melange@localhost) by pi.yip.org (8.9.2/8.9.2) with ESMTP id TAA02674; Tue, 23 Mar 1999 19:12:36 -0500 (EST) (envelope-from melange@yip.org) Date: Tue, 23 Mar 1999 19:12:36 -0500 (EST) From: Bob K To: Benjamin Gavin Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Username size limit suggestion In-Reply-To: <4.1.19990323143242.00b423a0@mail.supranet.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, 23 Mar 1999, Benjamin Gavin wrote: [snip] > Suggestion: > I noticed that the adduser script has the 16 character limit hard-coded > into the file. I was thinking that it might be a good idea to make that a > configurable global variable or something of that sort (i.e. $UT_NAMESIZE, > ala. sys/params.h, at the top of the file.) That way those of us who want > longer names could easily change the variable and be done with it. I > understand that it is probably done this way to force people to know what > they are doing when they change it. I think this would be a great idea in the interest of seamlessness. [snip] > b. change src/sys/sys/params.h (#define UT_NAMESIZE) to reflect the > new length > c. change src/include/utmp.h (#define MAXLOGNAME (UT_NAMESIZE+1)) These are kind of backwards: it's src/sys/sys/param.h (#define MAXLOGNAME (UT_NAMESIZE+1)) and src/include/utmp.h (#define UT_NAMESIZE). > c. cat /dev/null > /var/log/wtmp Hmm. I'd still dump myself in the "novice FreeBSD user" category, so bear this in mind when reading this, but I thought wtmp was used by ac(8) for login accounting, which may in some cases be important for systems already in production environments. Maybe a mv /var/log/wtmp /var/log/wtmp.old&& touch /var/log/wtmp? > Is that it?? I am going to be completing testing, but I am wondering > what gotchas are waiting for me :)... As far as I know, it seems to be complete (aside from the minor corrections above). I'll be testing it too, once this buildworld finishes (the drive my src & obj trees were on decided to stop working during a buildworld. Good thing I never bothered putting it in my fstab :) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 23 17:15: 8 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.cs.tu-berlin.de (mail.cs.tu-berlin.de [130.149.17.13]) by hub.freebsd.org (Postfix) with ESMTP id 4105A15476 for ; Tue, 23 Mar 1999 17:15:04 -0800 (PST) (envelope-from eserte@cs.tu-berlin.de) Received: (from eserte@localhost) by mail.cs.tu-berlin.de (8.9.1/8.9.1) id CAA18030; Wed, 24 Mar 1999 02:13:15 +0100 (MET) Received: (from eserte@localhost) by cabulja.herceg.de (8.8.8/8.6.12) id WAA02275; Tue, 23 Mar 1999 22:31:13 +0100 (CET) To: Benjamin Gavin Cc: freebsd-stable@FreeBSD.org Subject: Re: Username size limit suggestion References: <4.1.19990323143242.00b423a0@mail.supranet.net> Reply-To: eserte@cs.tu-berlin.de From: Slaven Rezic Date: 23 Mar 1999 22:31:13 +0100 In-Reply-To: Benjamin Gavin's message of Tue, 23 Mar 1999 14:46:23 -0600 Message-ID: <87ogljao66.fsf@cabulja.herceg.de> Lines: 30 X-Mailer: Gnus v5.3/Emacs 19.34 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Benjamin Gavin writes: > > Hi all, > I believe that we can all agree that there is never going to be an agreed > upon limit on the username size. I have just finished rebuilding my system > to support 32-character usernames (I think, have to finish testing it). I > have a suggestion and also a couple of questions. First the suggestion: > > Suggestion: > I noticed that the adduser script has the 16 character limit hard-coded > into the file. I was thinking that it might be a good idea to make that a > configurable global variable or something of that sort (i.e. $UT_NAMESIZE, > ala. sys/params.h, at the top of the file.) This can be done automatically in perl. Something like require "sys/param.ph"; print "max logname length is " . &MAXLOGNAME . "\n"; should do the trick. Regards, Slaven -- use Tk;$c=tkinit->Canvas->pack;$x=45;for(split/_/,'KPI1_+09IPK_K;-OA1_+K!;A__1; Q!7G_1+QK_3CLPI90,_+K!;A_+1!KQ!.N_K+1Q!.F_1+KN.Q__1+KN._K+1Q!.F_1+KN.Q_+1Q__+1! KQ!.N_1;Q!7G_K3,09Q_+1!K.Q_K+1Q!.F_1+KN.Q'){s/\n//g;for(split/!/){$c->create( 'line',map{$a=-43+ord;($x+($a>>3)*2,123+($a&7)*2)}split//)}$x+=12}MainLoop To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 23 19:44:19 1999 Delivered-To: freebsd-stable@freebsd.org Received: from jade.chc-chimes.com (jade.chc-chimes.com [206.67.97.83]) by hub.freebsd.org (Postfix) with ESMTP id 8C3B814C19 for ; Tue, 23 Mar 1999 19:43:43 -0800 (PST) (envelope-from billf@jade.chc-chimes.com) Received: from localhost (billf@localhost) by jade.chc-chimes.com (8.8.8/8.8.8) with SMTP id WAA26014; Tue, 23 Mar 1999 22:44:53 -0500 (EST) (envelope-from billf@jade.chc-chimes.com) Date: Tue, 23 Mar 1999 22:44:53 -0500 (EST) From: Bill Fumerola To: freebsd-stable@freebsd.org Cc: jkh@zippy.cdrom.com Subject: `make upgrade` is borked. 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 As the subject indicated, with the latest doscmd commits the upgrade target is broke. It would seem a library is being missed for linking though, the X11 library seems to be the right one. Ignore the -DI_LIKE_BREAKING_PORTS, it's just my way of (boldly) making sure ports respect CFLAGS when I test them on this machine. - bill fumerola - billf@chc-chimes.com - BF1560 - computer horizons corp - - ph:(800) 252-2421 - bfumerol@computerhorizons.com - billf@FreeBSD.org - ===> usr.bin/doscmd uudecode /usr/src/usr.bin/doscmd/emsdriv.sys.uu uudecode /usr/src/usr.bin/doscmd/redir.com.uu cc -O -pipe -DI_LIKE_BREAKING_PORTS -I. -I/usr/X11R6/include -DDISASSEMBLER -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/usr.bin/doscmd/AsyncIO.c cc -O -pipe -DI_LIKE_BREAKING_PORTS -I. -I/usr/X11R6/include -DDISASSEMBLER -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/usr.bin/doscmd/ParseBuffer.c cc -O -pipe -DI_LIKE_BREAKING_PORTS -I. -I/usr/X11R6/include -DDISASSEMBLER -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/usr.bin/doscmd/bios.c cc -O -pipe -DI_LIKE_BREAKING_PORTS -I. -I/usr/X11R6/include -DDISASSEMBLER -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/usr.bin/doscmd/callback.c cc -O -pipe -DI_LIKE_BREAKING_PORTS -I. -I/usr/X11R6/include -DDISASSEMBLER -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/usr.bin/doscmd/cpu.c cc -O -pipe -DI_LIKE_BREAKING_PORTS -I. -I/usr/X11R6/include -DDISASSEMBLER -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/usr.bin/doscmd/dos.c cc -O -pipe -DI_LIKE_BREAKING_PORTS -I. -I/usr/X11R6/include -DDISASSEMBLER -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/usr.bin/doscmd/cmos.c cc -O -pipe -DI_LIKE_BREAKING_PORTS -I. -I/usr/X11R6/include -DDISASSEMBLER -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/usr.bin/doscmd/config.c cc -O -pipe -DI_LIKE_BREAKING_PORTS -I. -I/usr/X11R6/include -DDISASSEMBLER -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/usr.bin/doscmd/cwd.c cc -O -pipe -DI_LIKE_BREAKING_PORTS -I. -I/usr/X11R6/include -DDISASSEMBLER -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/usr.bin/doscmd/debug.c cc -O -pipe -DI_LIKE_BREAKING_PORTS -I. -I/usr/X11R6/include -DDISASSEMBLER -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/usr.bin/doscmd/disktab.c cc -O -pipe -DI_LIKE_BREAKING_PORTS -I. -I/usr/X11R6/include -DDISASSEMBLER -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/usr.bin/doscmd/doscmd.c cc -O -pipe -DI_LIKE_BREAKING_PORTS -I. -I/usr/X11R6/include -DDISASSEMBLER -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/usr.bin/doscmd/ems.c cc -O -pipe -DI_LIKE_BREAKING_PORTS -I. -I/usr/X11R6/include -DDISASSEMBLER -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/usr.bin/doscmd/emuint.c cc -O -pipe -DI_LIKE_BREAKING_PORTS -I. -I/usr/X11R6/include -DDISASSEMBLER -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/usr.bin/doscmd/exe.c cc -O -pipe -DI_LIKE_BREAKING_PORTS -I. -I/usr/X11R6/include -DDISASSEMBLER -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/usr.bin/doscmd/i386-pinsn.c cc -O -pipe -DI_LIKE_BREAKING_PORTS -I. -I/usr/X11R6/include -DDISASSEMBLER -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/usr.bin/doscmd/int.c cc -O -pipe -DI_LIKE_BREAKING_PORTS -I. -I/usr/X11R6/include -DDISASSEMBLER -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/usr.bin/doscmd/int10.c /usr/src/usr.bin/doscmd/int10.c: In function `int10': /usr/src/usr.bin/doscmd/int10.c:146: warning: passing arg 4 of `unknown_int3' from incompatible pointer type /usr/src/usr.bin/doscmd/int10.c:185: warning: passing arg 5 of `unknown_int4' from incompatible pointer type /usr/src/usr.bin/doscmd/int10.c:190: warning: passing arg 4 of `unknown_int3' from incompatible pointer type /usr/src/usr.bin/doscmd/int10.c:204: warning: passing arg 4 of `unknown_int3' from incompatible pointer type /usr/src/usr.bin/doscmd/int10.c:269: warning: passing arg 1 of `dump_regs' from incompatible pointer type /usr/src/usr.bin/doscmd/int10.c:274: warning: passing arg 3 of `unknown_int2' from incompatible pointer type cc -O -pipe -DI_LIKE_BREAKING_PORTS -I. -I/usr/X11R6/include -DDISASSEMBLER -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/usr.bin/doscmd/int13.c cc -O -pipe -DI_LIKE_BREAKING_PORTS -I. -I/usr/X11R6/include -DDISASSEMBLER -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/usr.bin/doscmd/int14.c cc -O -pipe -DI_LIKE_BREAKING_PORTS -I. -I/usr/X11R6/include -DDISASSEMBLER -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/usr.bin/doscmd/int16.c cc -O -pipe -DI_LIKE_BREAKING_PORTS -I. -I/usr/X11R6/include -DDISASSEMBLER -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/usr.bin/doscmd/int17.c cc -O -pipe -DI_LIKE_BREAKING_PORTS -I. -I/usr/X11R6/include -DDISASSEMBLER -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/usr.bin/doscmd/int1a.c cc -O -pipe -DI_LIKE_BREAKING_PORTS -I. -I/usr/X11R6/include -DDISASSEMBLER -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/usr.bin/doscmd/int2f.c cc -O -pipe -DI_LIKE_BREAKING_PORTS -I. -I/usr/X11R6/include -DDISASSEMBLER -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/usr.bin/doscmd/intff.c cc -O -pipe -DI_LIKE_BREAKING_PORTS -I. -I/usr/X11R6/include -DDISASSEMBLER -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/usr.bin/doscmd/mem.c cc -O -pipe -DI_LIKE_BREAKING_PORTS -I. -I/usr/X11R6/include -DDISASSEMBLER -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/usr.bin/doscmd/mouse.c cc -O -pipe -DI_LIKE_BREAKING_PORTS -I. -I/usr/X11R6/include -DDISASSEMBLER -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/usr.bin/doscmd/net.c cc -O -pipe -DI_LIKE_BREAKING_PORTS -I. -I/usr/X11R6/include -DDISASSEMBLER -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/usr.bin/doscmd/port.c cc -O -pipe -DI_LIKE_BREAKING_PORTS -I. -I/usr/X11R6/include -DDISASSEMBLER -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/usr.bin/doscmd/setver.c cc -O -pipe -DI_LIKE_BREAKING_PORTS -I. -I/usr/X11R6/include -DDISASSEMBLER -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/usr.bin/doscmd/signal.c cc -O -pipe -DI_LIKE_BREAKING_PORTS -I. -I/usr/X11R6/include -DDISASSEMBLER -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/usr.bin/doscmd/timer.c cc -O -pipe -DI_LIKE_BREAKING_PORTS -I. -I/usr/X11R6/include -DDISASSEMBLER -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/usr.bin/doscmd/trace.c cc -O -pipe -DI_LIKE_BREAKING_PORTS -I. -I/usr/X11R6/include -DDISASSEMBLER -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/usr.bin/doscmd/trap.c cc -O -pipe -DI_LIKE_BREAKING_PORTS -I. -I/usr/X11R6/include -DDISASSEMBLER -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/usr.bin/doscmd/tty.c /usr/src/usr.bin/doscmd/tty.c: In function `debug_event': /usr/src/usr.bin/doscmd/tty.c:737: warning: passing arg 1 of `dump_regs' from incompatible pointer type /usr/src/usr.bin/doscmd/tty.c: In function `tty_read': /usr/src/usr.bin/doscmd/tty.c:1745: warning: passing arg 1 of `fake_int' from incompatible pointer type /usr/src/usr.bin/doscmd/tty.c: In function `tty_peek': /usr/src/usr.bin/doscmd/tty.c:1787: warning: passing arg 1 of `fake_int' from incompatible pointer type /usr/src/usr.bin/doscmd/tty.c: In function `video_init': /usr/src/usr.bin/doscmd/tty.c:2000: warning: passing arg 2 of `register_callback' from incompatible pointer type /usr/src/usr.bin/doscmd/tty.c: In function `video_bios_init': /usr/src/usr.bin/doscmd/tty.c:2212: warning: passing arg 2 of `register_callback' from incompatible pointer type cc -O -pipe -DI_LIKE_BREAKING_PORTS -I. -I/usr/X11R6/include -DDISASSEMBLER -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/usr.bin/doscmd/xms.c cc -O -pipe -DI_LIKE_BREAKING_PORTS -I. -I/usr/X11R6/include -DDISASSEMBLER -I/usr/obj/elf/usr/src/tmp/usr/include -o doscmd AsyncIO.o ParseBuffer.o bios.o callback.o cpu.o dos.o cmos.o config.o cwd.o debug.o disktab.o doscmd.o ems.o emuint.o exe.o i386-pinsn.o int.o int10.o int13.o int14.o int16.o int17.o int1a.o int2f.o intff.o mem.o mouse.o net.o port.o setver.o signal.o timer.o trace.o trap.o tty.o xms.o -L/usr/X11R6/lib -lX11 tty.o: In function `video_setborder': tty.o(.text+0x25f): undefined reference to `XSetWindowBackground' tty.o: In function `setgc': tty.o(.text+0x2f5): undefined reference to `XChangeGC' tty.o: In function `video_update': tty.o(.text+0x50e): undefined reference to `XDrawImageString' tty.o(.text+0x597): undefined reference to `XDrawImageString' tty.o(.text+0x68a): undefined reference to `XChangeGC' tty.o(.text+0x712): undefined reference to `XFillRectangle' tty.o(.text+0x7be): undefined reference to `XChangeGC' tty.o(.text+0x7fb): undefined reference to `XFillRectangle' tty.o(.text+0x809): undefined reference to `XFlush' tty.o: In function `debug_event': tty.o(.text+0xc48): undefined reference to `XBell' tty.o(.text+0xc53): undefined reference to `XFlush' tty.o: In function `video_async_event': tty.o(.text+0x1233): undefined reference to `XFlush' tty.o(.text+0x124b): undefined reference to `XNextEvent' tty.o(.text+0x12c7): undefined reference to `XFlush' tty.o(.text+0x12fc): undefined reference to `XNextEvent' tty.o: In function `video_event': tty.o(.text+0x17f4): undefined reference to `XLookupString' tty.o(.text+0x1978): undefined reference to `XLookupString' tty.o: In function `tty_write': tty.o(.text+0x27fe): undefined reference to `XBell' tty.o: In function `KbdWrite': tty.o(.text+0x3083): undefined reference to `XBell' tty.o: In function `video_init': tty.o(.text+0x33e1): undefined reference to `XOpenDisplay' tty.o(.text+0x3408): undefined reference to `XDisplayName' tty.o(.text+0x34df): undefined reference to `XAllocNamedColor' tty.o(.text+0x3532): undefined reference to `XLoadQueryFont' tty.o(.text+0x354e): undefined reference to `XLoadQueryFont' tty.o(.text+0x3629): undefined reference to `XCreateSimpleWindow' tty.o(.text+0x368c): undefined reference to `XCreateGC' tty.o(.text+0x36c3): undefined reference to `XCreateGC' tty.o(.text+0x36e0): undefined reference to `XSetNormalHints' tty.o(.text+0x370a): undefined reference to `XSelectInput' tty.o(.text+0x371e): undefined reference to `XMapWindow' tty.o(.text+0x3729): undefined reference to `XFlush' *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. sh-2.01# exit exit Script done on Tue Mar 23 22:19:44 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 23 19:55:40 1999 Delivered-To: freebsd-stable@freebsd.org Received: from holly.dyndns.org (ip233.houston22.tx.pub-ip.psi.net [38.31.97.233]) by hub.freebsd.org (Postfix) with ESMTP id 14CC014CD3 for ; Tue, 23 Mar 1999 19:55:38 -0800 (PST) (envelope-from chris@holly.dyndns.org) Received: (from chris@localhost) by holly.dyndns.org (8.9.3/8.9.3) id VAA14963; Tue, 23 Mar 1999 21:56:56 -0600 (CST) (envelope-from chris) Date: Tue, 23 Mar 1999 21:56:55 -0600 From: Chris Costello To: Bill Fumerola Cc: freebsd-stable@FreeBSD.ORG, jkh@zippy.cdrom.com Subject: Re: `make upgrade` is borked. Message-ID: <19990323215655.A14872@holly.dyndns.org> Reply-To: chris@calldei.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4us In-Reply-To: ; from Bill Fumerola on Tue, Mar 23, 1999 at 10:44:53PM -0500 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Mar 23, 1999, Bill Fumerola wrote: > tty.o: In function `video_setborder': > tty.o(.text+0x25f): undefined reference to `XSetWindowBackground' > tty.o: In function `setgc': > tty.o(.text+0x2f5): undefined reference to `XChangeGC' > tty.o: In function `video_update': > tty.o(.text+0x50e): undefined reference to `XDrawImageString' > tty.o(.text+0x597): undefined reference to `XDrawImageString' > tty.o(.text+0x68a): undefined reference to `XChangeGC' > tty.o(.text+0x712): undefined reference to `XFillRectangle' [...] It looks like it needs to be linked against -lXaw and maybe -lXext. > > > 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 Mar 23 20:27:13 1999 Delivered-To: freebsd-stable@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id F15661559F for ; Tue, 23 Mar 1999 20:27:06 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id UAA87493; Tue, 23 Mar 1999 20:26:09 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Bill Fumerola Cc: freebsd-stable@freebsd.org Subject: Re: `make upgrade` is borked. In-reply-to: Your message of "Tue, 23 Mar 1999 22:44:53 EST." Date: Tue, 23 Mar 1999 20:26:09 -0800 Message-ID: <87491.922249569@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > As the subject indicated, with the latest doscmd commits the upgrade > target is broke. I fixed this in -current a few days ago, but just now MFC'd it. Please re-cvsup and try again. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 23 23:10: 3 1999 Delivered-To: freebsd-stable@freebsd.org Received: from regret.globalserve.net (regret.globalserve.net [209.90.144.72]) by hub.freebsd.org (Postfix) with ESMTP id 8E9B1152F6 for ; Tue, 23 Mar 1999 23:09:48 -0800 (PST) (envelope-from dm@regret.globalserve.net) Received: (from dm@localhost) by regret.globalserve.net (8.9.3/8.9.1) id DAA94028 for stable@freebsd.org; Wed, 24 Mar 1999 03:19:19 GMT (envelope-from dm) Message-ID: <19990324031919.B93960@globalserve.net> Date: Wed, 24 Mar 1999 03:19:19 +0000 From: Dan Moschuk To: stable@freebsd.org Subject: quotas stable? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greetings, I remember a while back trying to implement quotas on a 2.x box, and finding them very unstable (to the point of being unusable). Now, before I go off and start breaking production machines, are quotas stable in 3.1? Cheers! -- Dan Moschuk (TFreak!dm@globalserve.net) Senior Systems/Network Administrator Globalserve Communications Inc., a Primus Canada Company "If at first you don't succeed, redefine success" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 23 23:30:11 1999 Delivered-To: freebsd-stable@freebsd.org Received: from flophouse.com (flophouse.com [206.169.156.66]) by hub.freebsd.org (Postfix) with ESMTP id 4103E14D06 for ; Tue, 23 Mar 1999 23:28:11 -0800 (PST) (envelope-from dpassage@flophouse.com) Received: from flophouse.com (localhost.flophouse.com [127.0.0.1]) by flophouse.com (8.8.8/8.8.8) with ESMTP id XAA26968 for ; Tue, 23 Mar 1999 23:27:52 -0800 (PST) (envelope-from dpassage@flophouse.com) Message-Id: <199903240727.XAA26968@flophouse.com> To: freebsd-stable@freebsd.org Subject: Re: `make upgrade` is borked. In-reply-to: Your message of "Tue, 23 Mar 1999 22:44:53 EST." Date: Tue, 23 Mar 1999 23:27:51 -0800 From: "David G. Paschich" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bill Fumerola writes: > As the subject indicated, with the latest doscmd commits the upgrade > target is broke. > > It would seem a library is being missed for linking though, the X11 > library seems to be the right one. I had this happen to me as well. What's going on is this: The makefile for doscmd has some smarts in it that looks for the X11 libraries. Unfortunately, those smarts don't look at the place that the "buildworld" process uses for libraries. So the Makefile looks in ${X11BASE} for the X libraries, finds them, adds them to the link line, and then the link fails because ${X11BASE} isn't in the buildworld library path. A workaround is to edit that Makefile, find the conditional on X11, and delete everything but the "else" part. A patch follows my signature. -------- David G. Paschich dpassage@flophouse.com *** src/usr.bin/doscmd/Makefile~ Fri Jan 22 10:40:55 1999 --- src/usr.bin/doscmd/Makefile Tue Mar 23 08:39:05 1999 *************** *** 20,32 **** BINMODE=2555 EXEMODE=444 - .if exists(${X11BASE}/include) && exists(${X11BASE}/lib/libX11.a) - CFLAGS+= -I. -I${X11BASE}/include -DDISASSEMBLER - LDADD= -L${X11BASE}/lib -lX11 - DPADD= ${X11BASE}/lib/libX11.a - .else CFLAGS+= -I. -DDISASSEMBLER -DNO_X - .endif .if ${OBJFORMAT} == "aout" LDADD+= -L${DESTDIR}${LIBDIR} -lgcc -lc DPADD+= ${LIBGCC} ${LIBC} --- 20,26 ---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Mar 23 23:43:42 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 3C8FB15459 for ; Tue, 23 Mar 1999 23:43:39 -0800 (PST) (envelope-from mike@sentex.net) Received: from gravel (ospf-wat.sentex.net [209.167.248.81]) by sand2.sentex.ca (8.8.8/8.8.8) with SMTP id CAA22990; Wed, 24 Mar 1999 02:43:19 -0500 (EST) (envelope-from mike@sentex.net) Message-Id: <4.1.19990324024926.04b7b9c0@granite.sentex.ca> X-Sender: mdtancsa@granite.sentex.ca X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Wed, 24 Mar 1999 02:52:46 -0500 To: Dan Moschuk , stable@FreeBSD.ORG From: Mike Tancsa Subject: Re: quotas stable? In-Reply-To: <19990324031919.B93960@globalserve.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 10:19 PM 3/23/99 , Dan Moschuk wrote: > >Greetings, > >I remember a while back trying to implement quotas on a 2.x box, and finding >them very unstable (to the point of being unusable). > >Now, before I go off and start breaking production machines, are quotas >stable in 3.1? I have been using quotas on 2.x boxes with uptimes of several months. IIRC, the instability that some people saw occured when they were turning quotas on and off on a live file system. What sort of problems were you having ? On 3.x I have a couple of machines using quotas but they are not in production. ---Mike ********************************************************************** Mike Tancsa, Network Admin * mike@sentex.net Sentex Communications Corp, * http://www.sentex.net/mike Cambridge, Ontario * 01.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 Wed Mar 24 1:39: 7 1999 Delivered-To: freebsd-stable@freebsd.org Received: from odin.siol.net (odin.siol.net [193.189.160.10]) by hub.freebsd.org (Postfix) with ESMTP id 5326F14BD6 for ; Wed, 24 Mar 1999 01:39:01 -0800 (PST) (envelope-from tomaz.borstnar@over.net) Received: from hang ([193.189.191.33]) by odin.siol.net (Post.Office MTA v3.5.3 release 223 ID# 620-58654U60000L60000S0V35) with SMTP id net for ; Wed, 24 Mar 1999 10:38:34 +0100 Message-Id: <4.1.19990324092420.01ae7770@193.189.189.100> Message-Id: <4.1.19990324092420.01ae7770@193.189.189.100> X-Misc: N/A X-Legalese: #include Date: Wed, 24 Mar 1999 09:30:13 +0100 To: stable@FreeBSD.ORG From: Tomaz Borstnar Subject: parallel port and non-printer (modem) uses of it (was: Re: Diskless boot stopping at "NFS ROOT:...") In-Reply-To: <199903152134.NAA02842@apollo.backplane.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > If this solves your problem, I would really appreciate it if the > people developing the new parallel port stuff would look into it I was wondering if I can expect any problems when connecting Zyxel 2864I (ISDN and analog modem) to machine via parallel port? It can communicate via serial port which is limited to 115200 or parallel port. Haven't tried it yet, but I'd like to use parallel port so I can make better use of ISDN channel bundling. I'm tracking 3.1-stable. Tomaz ---- Tomaz Borstnar "Love is the answer to the final question you ask" - Unknown To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 24 2:23:29 1999 Delivered-To: freebsd-stable@freebsd.org Received: from quadrus.ru (unknown [195.133.77.43]) by hub.freebsd.org (Postfix) with ESMTP id AD96B1549A for ; Wed, 24 Mar 1999 02:23:10 -0800 (PST) (envelope-from blink@quadrus.ru) Received: from executive (deputy.quadrusm.ru [192.168.43.11]) by quadrus.ru (8.8.5/8.8.8) with SMTP id MAA12280 for ; Wed, 24 Mar 1999 12:37:21 +0300 (MSK) (envelope-from blink@quadrus.ru) Message-ID: <009501be75e0$1ec51870$0b2ba8c0@executive.quadrusm.ru> From: "Inna V. Dotsenko" To: Subject: Date: Wed, 24 Mar 1999 13:21:41 +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 4.72.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 24 5:22:27 1999 Delivered-To: freebsd-stable@freebsd.org Received: from david.siemens.de (david.siemens.de [192.35.17.14]) by hub.freebsd.org (Postfix) with ESMTP id D2568152FF for ; Wed, 24 Mar 1999 05:22:24 -0800 (PST) (envelope-from andre.albsmeier@mchp.siemens.de) X-Envelope-Sender-Is: andre.albsmeier@mchp.siemens.de (at relayer david.siemens.de) Received: from mail1.siemens.de (mail1.siemens.de [139.23.33.14]) by david.siemens.de (8.9.3/8.9.3) with ESMTP id OAA12269 for ; Wed, 24 Mar 1999 14:22:17 +0100 (MET) Received: from curry.mchp.siemens.de (curry.mchp.siemens.de [146.180.31.23]) by mail1.siemens.de (8.9.3/8.9.3) with ESMTP id OAA13314 for ; Wed, 24 Mar 1999 14:21:53 +0100 (MET) Received: (from daemon@localhost) by curry.mchp.siemens.de (8.8.8/8.8.8) id OAA39530 for ; Wed, 24 Mar 1999 14:22:04 +0100 (CET) Date: Wed, 24 Mar 1999 14:22:00 +0100 From: Andre Albsmeier To: "Thomas T. Veldhouse" Cc: Andre Albsmeier , freebsd-stable@FreeBSD.ORG Subject: Re: Heavy MSDOS fs problems with floppies Message-ID: <19990324142200.A684@internal> References: <020b01be7574$12459a00$236319ac@w142844.carlson.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <020b01be7574$12459a00$236319ac@w142844.carlson.com>; from Thomas T. Veldhouse on Tue, Mar 23, 1999 at 03:28:18PM -0600 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 23-Mar-1999 at 15:28:18 -0600, Thomas T. Veldhouse wrote: > It has been around for a while. Try this: > > Insert a write protected floppy disk: > > dd if=/dev/zero of=/dev/fd0 bs=4096 count=10 > > I am sure this will crash your system too. If it doesn't try increasing > the count. ;-] Confirmed :-( (with a _non_ write protected floppy) How about a PR? -Andre To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 24 9: 2: 3 1999 Delivered-To: freebsd-stable@freebsd.org Received: from apollo.orakel.ntnu.no (apollo.orakel.ntnu.no [129.241.56.245]) by hub.freebsd.org (Postfix) with SMTP id 3A07A14C19 for ; Wed, 24 Mar 1999 09:01:58 -0800 (PST) (envelope-from oyvindmo@orakel.ntnu.no) Received: (qmail 14103 invoked by uid 28778); 24 Mar 1999 17:01:35 -0000 To: freebsd-stable@freebsd.org Subject: SCSI hangs/timout, ncr53C8xx, 3.1-STABLE MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit From: Oyvind Moll Date: 24 Mar 1999 18:01:34 +0100 Message-ID: Lines: 219 User-Agent: Gnus/5.070075 (Pterodactyl Gnus v0.75) Emacs/20.3 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I run 3.1-STABLE with kernel and world built from source cvsupped 1999-03-04. My problem: I try to dump an audio-CD from a Philips CDD2600 CD-R-drive (using tosha). Three of the about ten times that I've tried to dump a CD, tosha would suddenly report "SCSI read/write error" or something (sorry, forgot to write that one down) and I would get messages like these on my console: ncr0: timeout nccb=0xf0bd3c00 (skip) ncr0: timeout nccb=0xf0b91c00 (skip) ncr0: timeout nccb=0xf0b91e00 (skip) ncr0: timeout nccb=0xf0b76e00 (skip) ncr0: timeout nccb=0xf0b6e400 (skip) ncr0: timeout nccb=0xf0b6b200 (skip) ... From then on, anything involving disk I/O simply hangs. I can ping my machine from elsewhere, but any process that tries to access a disk goes frozen. Annoying. The hangs happen at different times in the CDs; no apparent pattern. If it matters, I dump from the SCSI CDD2600 to an IBM IDE-drive. I have _not_ tried waiting for a very long time to see if things unfreeze -- perhaps five minutes or so. Known bug? Anything I can do to provide more helpful information? My sys/pci/ncr.c is v1.141, and my verbose dmesg is: y master/slave sample = 3, master/slave recovery = 1 intel_piix_status: primary master fastDMAonly disabled, pre/post enabled, intel_piix_status: IORDY sampling enabled, intel_piix_status: fast PIO enabled intel_piix_status: primary master/slave sample = 3, master/slave recovery = 1 intel_piix_status: primary slave fastDMAonly disabled, pre/post disabled, intel_piix_status: IORDY sampling disabled, intel_piix_status: fast PIO disabled ide_pci: busmaster 0 status: 04 from port: 0000e802 intel_piix_status: secondary master/slave sample = 3, master/slave recovery = 1 intel_piix_status: secondary master fastDMAonly disabled, pre/post enabled, intel_piix_status: IORDY sampling enabled, intel_piix_status: fast PIO enabled intel_piix_status: secondary master/slave sample = 3, master/slave recovery = 1 intel_piix_status: secondary slave fastDMAonly disabled, pre/post disabled, intel_piix_status: IORDY sampling disabled, intel_piix_status: fast PIO disabled ide_pci: busmaster 1 status: 04 from port: 0000e80a found-> vendor=0x1000, dev=0x0001, revid=0x12 class=01-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=9 map[0]: type 4, range 32, base 0000e000, size 8 map[1]: type 1, range 32, base fa000000, size 8 ncr0: rev 0x12 int a irq 9 on pci0.10.0 ncr0: minsync=25, maxsync=206, maxoffs=8, 16 dwords burst, normal dma fifo ncr0: single-ended, open drain IRQ driver found-> vendor=0x10b7, dev=0x5900, revid=0x00 class=02-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=10 map[0]: type 4, range 32, base 0000d800, size 5 vx0: <3COM 3C590 Etherlink III PCI> rev 0x00 int a irq 10 on pci0.11.0 utp/aui/bnc[*utp*]: disable 'auto select' with DOS util! address 00:a0:24:4a:bf:11 bpf: vx0 attached Warning! Defective early revision adapter! found-> vendor=0x102b, dev=0x0519, revid=0x01 class=03-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=11 map[0]: type 1, range 32, base f9800000, size 14 map[1]: type 3, range 32, base fb000000, size 23 vga0: rev 0x01 int a irq 11 on pci0.12.0 Probing for devices on the ISA bus: atkbd: the current kbd controller command byte 0047 atkbd: keyboard ID 0x41ab (2) kbdc: RESET_KBD return code:00fa kbdc: RESET_KBD status:00aa sc0 on isa sc0: fb0 kbd0 sc0: VGA color <8 virtual consoles, flags=0x0> atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa kbd0: atkbd0, AT 101/102 (2), config:0x10000, flags:0x3d0000 psm0: current command byte:0047 kbdc: TEST_AUX_PORT status:0000 kbdc: RESET_AUX return code:00fa kbdc: RESET_AUX status:00aa kbdc: RESET_AUX ID:0000 psm: status 00 02 64 psm: status 92 03 28 psm: status 92 03 28 psm: status 92 03 28 psm: status 82 01 28 psm: data 08 00 00 psm: status 00 02 64 psm0 irq 12 on isa psm0: model GlidePoint, device ID 0, 3 buttons psm0: config:00000000, flags:00000000, packet size:3 psm0: syncmask:c0, syncbits:00 sio0: irq maps: 0x1 0x11 0x1 0x1 sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1: irq maps: 0x1 0x9 0x1 0x1 sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): wd0: 9671MB (19807200 sectors), 19650 cyls, 16 heads, 63 S/T, 512 B/S wd0: ATA INQUIRE valid = 0007, dmamword = 0407, apio = 0003, udma = 0007 wdc1 at 0x170-0x177 irq 15 on isa wdc1: unit 0 (wd2): wd2: 9671MB (19807200 sectors), 19650 cyls, 16 heads, 63 S/T, 512 B/S wd2: ATA INQUIRE valid = 0007, dmamword = 0407, apio = 0003, udma = 0007 ppc0 not found vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa fb0: vga0, vga, type:VGA (5), flags:0x7007f fb0: port:0x3b0-0x3df, crtc:0x3d4, mem:0xa0000 0x20000 fb0: init mode:24, bios mode:3, current mode:24 fb0: window:0xf00b8000 size:32k gran:32k, buf:0x0 size:0k VGA parameters upon power-up 50 18 10 00 00 00 03 00 02 67 60 4f 50 83 55 81 bf 1f 00 4f 0e 0f 00 00 07 80 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff VGA parameters in BIOS for mode 24 50 18 10 00 10 00 03 00 02 67 60 4f 50 83 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff EGA/VGA parameters to be used for mode 24 50 18 10 00 10 00 03 00 02 67 60 4f 50 83 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff npx0 on motherboard npx0: INT 16 interface i586_bzero() bandwidth = 173250173 bytes/sec bzero() bandwidth = 88261253 bytes/sec imasks: bio c008c040, tty c003101a, net c0060400 BIOS Geometries: 0:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 1:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 2:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 3:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 4:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 5:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 6:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 7:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 0 accounted for Device configuration finished. Intel Pentium detected, installing workaround for F00F bug IP packet filtering initialized, divert enabled, rule-based forwarding enabled, default to accept, logging disabled bpf: tun0 attached bpf: ppp0 attached new masks: bio c008c040, tty c003101a, net c007141a bpf: lo0 attached ccd0-3: Concatenated disk drivers DUMMYNET initialized (980901) -- size dn_pkt 48 IP Filter: initialized. Default = pass all, Logging = enabled Waiting 15 seconds for SCSI devices to settle ncr0: restart (scsi reset). (probe6:ncr0:0:6:0): INQUIRY. CDB: 12 1 80 0 ff 0 (probe6:ncr0:0:6:0): ILLEGAL REQUEST asc:24,0 (probe6:ncr0:0:6:0): Invalid field in CDB sks:c8,1 (probe5:ncr0:0:5:0): INQUIRY. CDB: 12 1 80 0 ff 0 (probe5:ncr0:0:5:0): ILLEGAL REQUEST asc:24,0 (probe5:ncr0:0:5:0): Invalid field in CDB sks:c0,1 pass0 at ncr0 bus 0 target 2 lun 0 pass0: Fixed Direct Access SCSI-2 device pass0: Serial Number 02592079 pass0: 10.000MB/s transfers (10.000MHz, offset 8), Tagged Queueing Enabled pass1 at ncr0 bus 0 target 5 lun 0 pass1: Removable CD-ROM SCSI-2 device pass1: 3.300MB/s transfers pass2 at ncr0 bus 0 target 6 lun 0 pass2: Removable CD-ROM SCSI-2 device pass2: 10.000MB/s transfers (10.000MHz, offset 8) da2 at ncr0 bus 0 target 2 lun 0 da2: Fixed Direct Access SCSI-2 device da2: Serial Number 02592079 da2: 10.000MB/s transfers (10.000MHz, offset 8), Tagged Queueing Enabled da2: 4095MB (8388315 512 byte sectors: 255H 63S/T 522C) Considering FFS root f/s. changing root device to da2s1a (cd1:ncr0:0:6:0): READ CD RECORDED CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (cd1:ncr0:0:6:0): NOT READY asc:3a,0 (cd1:ncr0:0:6:0): Medium not present cd1 at ncr0 bus 0 target 6 lun 0 cd1: Removable CD-ROM SCSI-2 device cd1: 10.000MB/s transfers (10.000MHz, offset 8) cd1: Attempt to query device size failed: NOT READY, Medium not present da2s1: type 0xa5, start 62, end = 8386181, size 8386120 : OK WARNING: / was not properly dismounted wd2s1: type 0xa5, start 63, end = 19807199, size 19807137 : OK (cd0:ncr0:0:5:0): READ CD RECORDED CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (cd0:ncr0:0:5:0): NOT READY asc:4,0 (cd0:ncr0:0:5:0): Logical unit not ready, cause not reportable cd0 at ncr0 bus 0 target 5 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 3.300MB/s transfers cd0: Attempt to query device size failed: NOT READY, Logical unit not ready, cause not reportable ffs_mountfs: superblock updated for soft updates ffs_mountfs: superblock updated for soft updates wd2s1: type 0xa5, start 63, end = 19807199, size 19807137 : OK Linux-ELF exec handler installed OSS/FreeBSD loading, address = f0c026ac stray irq 7 stray irq 7 -- Ĝyvind Mĝll oyvindmo@pvv.ntnu.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 24 9:16: 3 1999 Delivered-To: freebsd-stable@freebsd.org Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (Postfix) with SMTP id 6BF63154A1 for ; Wed, 24 Mar 1999 09:16:01 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 10PrFQ-0000iV-00; Wed, 24 Mar 1999 09:15:20 -0800 Date: Wed, 24 Mar 1999 09:15:19 -0800 (PST) From: Tom X-Sender: tom@shell.uniserve.ca To: Dan Moschuk Cc: stable@freebsd.org Subject: Re: quotas stable? In-Reply-To: <19990324031919.B93960@globalserve.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 Wed, 24 Mar 1999, Dan Moschuk wrote: > Greetings, > > I remember a while back trying to implement quotas on a 2.x box, and finding > them very unstable (to the point of being unusable). > > Now, before I go off and start breaking production machines, are quotas > stable in 3.1? They have been extremely stable since 2.2. Just do not switch them on and off and on again without rebooting. > Cheers! > -- > Dan Moschuk (TFreak!dm@globalserve.net) > Senior Systems/Network Administrator > Globalserve Communications Inc., a Primus Canada Company > "If at first you don't succeed, redefine success" Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 24 11:27:51 1999 Delivered-To: freebsd-stable@freebsd.org Received: from hp9000.chc-chimes.com (hp9000.chc-chimes.com [206.67.97.84]) by hub.freebsd.org (Postfix) with ESMTP id 50C7F14DEB for ; Wed, 24 Mar 1999 11:27:44 -0800 (PST) (envelope-from billf@chc-chimes.com) Received: from localhost by hp9000.chc-chimes.com with SMTP (1.39.111.2/16.2) id AA169381587; Wed, 24 Mar 1999 13:53:08 -0500 Date: Wed, 24 Mar 1999 13:53:07 -0500 (EST) From: Bill Fumerola To: "Jordan K. Hubbard" Cc: Bill Fumerola , freebsd-stable@FreeBSD.ORG Subject: Re: `make upgrade` is borked. In-Reply-To: <87491.922249569@zippy.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 Tue, 23 Mar 1999, Jordan K. Hubbard wrote: > > As the subject indicated, with the latest doscmd commits the upgrade > > target is broke. > > I fixed this in -current a few days ago, but just now MFC'd it. Please > re-cvsup and try again. Danke. It was getting really annoying having to re-'make upgrade' (to get the proper environment) every time. - 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 Wed Mar 24 11:44:16 1999 Delivered-To: freebsd-stable@freebsd.org Received: from correo.tamnet.com.mx (correo.tamnet.com.mx [200.34.205.20]) by hub.freebsd.org (Postfix) with ESMTP id EAD6314A14 for ; Wed, 24 Mar 1999 11:44:14 -0800 (PST) (envelope-from adepoo@tamnet.com.mx) Received: from correo.tamnet.com.mx (correo.tamnet.com.mx [200.34.205.20]) by correo.tamnet.com.mx (8.9.1a/8.9.1a) with SMTP id NAA27497; Wed, 24 Mar 1999 13:41:56 -0600 (CST) Date: Wed, 24 Mar 1999 13:41:55 -0600 (CST) From: Alberto de Poo Bas To: Dan Moschuk Cc: stable@FreeBSD.ORG Subject: Re: quotas stable? In-Reply-To: <19990324031919.B93960@globalserve.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 I don't know about 3.1 but we work with quotas on 2.2.6 for over 6 months without trouble. On Wed, 24 Mar 1999, Dan Moschuk wrote: > > Greetings, > > I remember a while back trying to implement quotas on a 2.x box, and finding > them very unstable (to the point of being unusable). > > Now, before I go off and start breaking production machines, are quotas > stable in 3.1? > > Cheers! > -- > Dan Moschuk (TFreak!dm@globalserve.net) > Senior Systems/Network Administrator > Globalserve Communications Inc., a Primus Canada Company > "If at first you don't succeed, redefine success" > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > Saludos Alberto de Poo TamNet - adepoo@tamnet.com.mx To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 24 13:44: 1 1999 Delivered-To: freebsd-stable@freebsd.org Received: from monet.etfal.g12.br (monet.etfal.g12.br [200.241.165.2]) by hub.freebsd.org (Postfix) with ESMTP id BDFF914D2D for ; Wed, 24 Mar 1999 13:43:55 -0800 (PST) (envelope-from aald@monet.etfal.g12.br) Received: from localhost (aald@localhost) by monet.etfal.g12.br (8.9.1a/8.9.1) with ESMTP id SAA19223; Wed, 24 Mar 1999 18:48:26 -0300 Date: Wed, 24 Mar 1999 18:48:26 -0300 (EST) From: Aldenor Falcao To: Bill Fumerola Cc: Shawn Ramsey , stable@FreeBSD.ORG Subject: Re: compile error In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG =09I'd got the same problem. =09BYe, =09=09Aldenor ----------------------------------------------------- Aldenor Falcao Martins, M Sc DEE - UFPB - ETFAL Internet Admin aald@ieee.org ----------------------------------------------------- =20 =09And miles to go before I sleep. -- Robert Frost=20 =09P.S.=09Maybe someday I'll sleep =09=09 On Tue, 23 Mar 1999, Bill Fumerola wrote: > On Tue, 23 Mar 1999, Shawn Ramsey wrote: >=20 > > -L/usr/X11R6/lib -lX11 > > tty.o: In function =16ideo_setborder': > > tty.o(.text+0x274): undefined reference to etWindowBackground' > > tty.o: In function =13etgc': > > tty.o(.text+0x319): undefined reference to angeGC' > > tty.o: In function =16ideo_update': > > tty.o(.text+0x52d): undefined reference to awImageString' > > tty.o(.text+0x5b5): undefined reference to awImageString' > > tty.o(.text+0x6a2): undefined reference to angeGC' > > tty.o(.text+0x719): undefined reference to llRectangle' > > tty.o(.text+0x7d2): undefined reference to angeGC' > > tty.o(.text+0x804): undefined reference to llRectangle' > > tty.o(.text+0x812): undefined reference to ush' > > tty.o: In function =04ebug_event': > > tty.o(.text+0xcbe): undefined reference to =BEll' > > tty.o(.text+0xcc9): undefined reference to ush' > > tty.o: In function =16ideo_async_event': > > tty.o(.text+0x13ab): undefined reference to ush' > > tty.o(.text+0x13c3): undefined reference to extEvent' > > tty.o(.text+0x1437): undefined reference to ush' > > tty.o(.text+0x1470): undefined reference to extEvent' > > tty.o: In function =16ideo_event': > > tty.o(.text+0x1a29): undefined reference to ookupString' > > tty.o(.text+0x1c09): undefined reference to ookupString' > > tty.o: In function =14ty_write': > > tty.o(.text+0x2b92): undefined reference to =BEll' > > tty.o: In function =0BbdWrite': > > tty.o(.text+0x3548): undefined reference to =BEll' > > tty.o: In function =16ideo_init': > > tty.o(.text+0x38c8): undefined reference to penDisplay' > > tty.o(.text+0x38fd): undefined reference to splayName' > > tty.o(.text+0x39d9): undefined reference to locNamedColor' > > tty.o(.text+0x3a30): undefined reference to oadQueryFont' > > tty.o(.text+0x3a4c): undefined reference to oadQueryFont' > > tty.o(.text+0x3b1a): undefined reference to eateSimpleWindow' > > tty.o(.text+0x3b7d): undefined reference to eateGC' > > tty.o(.text+0x3bb4): undefined reference to eateGC' > > tty.o(.text+0x3bd1): undefined reference to etNormalHints' > > tty.o(.text+0x3c02): undefined reference to electInput' > > tty.o(.text+0x3c16): undefined reference to apWindow' > > tty.o(.text+0x3c21): undefined reference to ush' > > *** Error code 1 >=20 > I recently got the same thing, it's important to note this is in doscmd, > which looks not to be linking the right libraries. >=20 > It's difficult to debug, because I just can't make the directory, because > of the upgrade environment neccesary. >=20 > - bill fumerola - billf@chc-chimes.com - BF1560 - computer horizons corp = - > - ph:(800) 252-2421 - bfumerol@computerhorizons.com - billf@FreeBSD.org = - >=20 >=20 >=20 >=20 >=20 > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message >=20 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 24 16:21:54 1999 Delivered-To: freebsd-stable@freebsd.org Received: from Sisyphos.MI.Uni-Koeln.DE (Sisyphos.MI.Uni-Koeln.DE [134.95.212.10]) by hub.freebsd.org (Postfix) with ESMTP id 6B0A214D96; Wed, 24 Mar 1999 16:21:51 -0800 (PST) (envelope-from se@dialup124.zpr.uni-koeln.de) Received: from dialup124.zpr.Uni-Koeln.DE (dialup124.zpr.Uni-Koeln.DE [134.95.219.124]) by Sisyphos.MI.Uni-Koeln.DE (8.8.7/8.8.7) with ESMTP id BAA11022; Thu, 25 Mar 1999 01:21:30 +0100 (MET) Received: (from se@localhost) by dialup124.zpr.Uni-Koeln.DE (8.9.3/8.6.9) id AAA00470; Thu, 25 Mar 1999 00:59:36 +0100 (CET) Date: Thu, 25 Mar 1999 00:59:36 +0100 From: Stefan Esser To: Oyvind Moll Cc: freebsd-stable@freebsd.org, Stefan Esser Subject: Re: SCSI hangs/timout, ncr53C8xx, 3.1-STABLE Message-ID: <19990325005936.A439@dialup124.mi.uni-koeln.de> Reply-To: se@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Oyvind Moll on Wed, Mar 24, 1999 at 06:01:34PM +0100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 1999-03-24 18:01 +0100, Oyvind Moll wrote: > I run 3.1-STABLE with kernel and world built from source cvsupped > 1999-03-04. > > My problem: I try to dump an audio-CD from a Philips CDD2600 > CD-R-drive (using tosha). Three of the about ten times that I've > tried to dump a CD, tosha would suddenly report "SCSI read/write > error" or something (sorry, forgot to write that one down) and I would > get messages like these on my console: Sorry, you do not give enough detail, but what you see might be caused by too short a timeout being specified with some SCSI command. Your best bet is to enable SCSI debugging (see option CAMDEBUG and information supplied in /sys/cam/cam_debug.h for more information. You probably want to try options "CAMDEBUG=CAM_DEBUG_INFO" in your kernel config file ... You will then be able to follow the flow of commands sent to the CD-R drive. The last command issued before the error messages appear is the one that causes the trouble. Let me know what you find. (But I'm on a 10 day vacation from Friday on, so don't expect a reply during that time ;-) Regards, STefan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 24 17:10:30 1999 Delivered-To: freebsd-stable@freebsd.org Received: from terror.hungry.com (terror.hungry.com [199.181.107.40]) by hub.freebsd.org (Postfix) with SMTP id 4C21C14C0F for ; Wed, 24 Mar 1999 17:10:29 -0800 (PST) (envelope-from fn@hungry.com) Received: (qmail 418 invoked by uid 0); 25 Mar 1999 01:10:10 -0000 Received: from siren.hungry.com (undead@199.181.107.129) by terror.hungry.com with SMTP; 25 Mar 1999 01:10:10 -0000 Received: (qmail 19194 invoked by uid 507); 25 Mar 1999 01:10:19 -0000 From: Faried Nawaz To: freebsd-stable@freebsd.org Subject: [2.2.8] bind 8.2 Reply-To: Faried Nawaz Organization: Integral Domains. Date: Wed, 24 Mar 1999 17:10:19 -0800 (PST) Message-Id: <19990324171019.417204.FMU5280@siren.hungry.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I'm having trouble with bind 8.2 on a 2.2.8 machine. Running 'ndc' seems to crash the server; I traced named via gdb, but didn't find anything all that useful -- some sprintf call was dying. However, bind 8.2 runs fine on another system (running 2.2.7). The 2.2.8 machine was upgraded from 2.2.6 (via cvsup & make world). Unfortunately, I can't upgrade it to 3.1 or -stable any time soon. Has anyone else experienced this problem? faried. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 24 17:35:21 1999 Delivered-To: freebsd-stable@freebsd.org Received: from voyager.fisicc-ufm.edu (unknown [209.198.197.202]) by hub.freebsd.org (Postfix) with ESMTP id E191814EF3; Wed, 24 Mar 1999 17:31:24 -0800 (PST) (envelope-from obonilla@voyager.fisicc-ufm.edu) Received: (from obonilla@localhost) by voyager.fisicc-ufm.edu (8.9.2/8.9.2) id TAA75749; Wed, 24 Mar 1999 19:35:31 -0600 (CST) (envelope-from obonilla) Date: Wed, 24 Mar 1999 19:35:30 -0600 From: Oscar Bonilla To: jkh@freebsd.org Cc: freebsd-stable@freebsd.org Subject: make world fails Message-ID: <19990324193530.A71967@fisicc-ufm.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG while making world, an install -c of chap-auth in /usr/share/examples/ppp fails because the directory ppp does not exist under /usr/share/examples i think that directory was recently added. mkdir /usr/share/example/ppp seemed to fix the problem regards, -oscar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 24 18:43:52 1999 Delivered-To: freebsd-stable@freebsd.org Received: from hun.org (hun.org [207.49.60.254]) by hub.freebsd.org (Postfix) with ESMTP id 065FE14D15 for ; Wed, 24 Mar 1999 18:43:50 -0800 (PST) (envelope-from attila@hun.org) Received: from localhost (attila@localhost) by hun.org (8.9.2/8.9.2) with ESMTP id CAA20204; Thu, 25 Mar 1999 02:43:17 GMT (envelope-from attila@hun.org) Date: Thu, 25 Mar 1999 02:43:17 +0000 (GMT) From: attila Reply-To: attila@hun.org To: Oscar Bonilla Cc: freebsd-stable@FreeBSD.ORG Subject: Re: make world fails In-Reply-To: <19990324193530.A71967@fisicc-ufm.edu> Message-ID: Owner: attila@hun.org Organization: home for unpenitent hackers and anarcho-cryptophreaks Encrypted: NO MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 24 Mar 1999, Oscar Bonilla wrote: *while making world, an install -c of chap-auth in /usr/share/examples/ppp *fails because the directory ppp does not exist under /usr/share/examples *i think that directory was recently added. * *mkdir /usr/share/example/ppp seemed to fix the problem ^^^^^^^ should be 'examples', I believe ^ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Mar 24 19:29:39 1999 Delivered-To: freebsd-stable@freebsd.org Received: from gooey.bunnynet.org (day-oh14-50.ix.netcom.com [207.220.161.178]) by hub.freebsd.org (Postfix) with ESMTP id 7744615237 for ; Wed, 24 Mar 1999 19:29:31 -0800 (PST) (envelope-from mwhite@donet.com) Received: from yiff (yiff.bunnynet.org [10.3.2.4]) by gooey.bunnynet.org (8.9.2/8.8.7) with SMTP id WAA03830; Wed, 24 Mar 1999 22:29:54 -0500 (EST) (envelope-from mwhite@donet.com) From: "Matt White" To: "Frederic LOYER" Cc: Subject: RE: Strange Error Message Date: Wed, 24 Mar 1999 22:28:57 -0500 Message-ID: <000401be766f$9e0f41c0$0402030a@yiff.bunnynet.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 In-Reply-To: <199903221904.UAA20478@quickstep.ensta.fr> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It hasn't happened again, so I can't reproduce it either. The same box has now been up since that incident without any problems... Oh well. =) Matt -----Original Message----- From: owner-freebsd-stable@FreeBSD.ORG [mailto:owner-freebsd-stable@FreeBSD.ORG]On Behalf Of Frederic LOYER Sent: Monday, March 22, 1999 2:04 PM To: Matt White Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Strange Error Message > Hello... > > Today while copying a large number of files I started getting this error > message: > > inetd in realloc(): warning: junk pointer, too low to make sense. > inetd in free(): warning: junk pointer, too low to make sense. > > This is a -STABLE system, last cvsupped and built on the 20th of this month. > > Any idea what this means? It prevented me from logging in, whenever I'd try > to start up a telnet session it would toss those two lines to me and close > the session. (I was still able to ssh in, which is not started via inetd.) > > Thanks, > Matt I've found the same problem. This means there is a bug in "inetd" or one of the called libraries. Trying to work with a debugger is difficult since inetd crash after the fork(): you can't login but the "main" inetd process is still alive to answer the following connection... and crash again. It seems to happen in malloc() called from login_getclass()... but this doesn't tell us where the memory is screwed: there must be something wrong before the fork() since this error comes on *every* connection after the first error. It could be triggered by the folowing lines: comsat dgram udp wait tty:tty /usr/libexec/comsat comsat ntalk dgram udp wait tty:tty /usr/libexec/ntalkd ntalkd tty:tty is quite recent on -STABLE, and I don't remember seeing this error before updating /etc/inetd.conf. Anyway this error is too rare to be debugged easily (I can't reproduce it). -- Frederic Loyer 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 Mar 24 22: 3:57 1999 Delivered-To: freebsd-stable@freebsd.org Received: from misha.cisco.com (misha.cisco.com [171.69.206.50]) by hub.freebsd.org (Postfix) with ESMTP id E17E815027 for ; Wed, 24 Mar 1999 22:03:55 -0800 (PST) (envelope-from mi@misha.cisco.com) Received: (from mi@localhost) by misha.cisco.com (8.9.1/8.9.1) id BAA25809 for stable@freebsd.org; Thu, 25 Mar 1999 01:03:35 -0500 (EST) (envelope-from mi) From: Mikhail Teterin Message-Id: <199903250603.BAA25809@misha.cisco.com> Subject: installworld fails To: stable@freebsd.org Date: Thu, 25 Mar 1999 01:03:34 -0500 (EST) Reply-To: mi@aldan.algebra.com X-Mailer: ELM [version 2.4ME+ PL52 (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 [....] install -c -o root -g wheel -m 644 portal/README /usr/share/examples/portal/README install -c -o root -g wheel -m 644 portal/portal.conf /usr/share/examples/portal/portal.conf install -c -o root -g wheel -m 644 ppi/Makefile /usr/share/examples/ppi/Makefile install -c -o root -g wheel -m 644 ppi/ppilcd.c /usr/share/examples/ppi/ppilcd.c install -c -o root -g wheel -m 644 ppp/chap-auth /usr/share/examples/ppp/chap-auth install: /usr/share/examples/ppp/chap-auth: No such file or directory Indeed, the /usr/share/examples/ppp did not exist... -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Mar 25 3: 6:46 1999 Delivered-To: freebsd-stable@freebsd.org Received: from casimir.proxad.net (unknown [194.250.16.115]) by hub.freebsd.org (Postfix) with SMTP id 33BBD14F46 for ; Thu, 25 Mar 1999 03:06:39 -0800 (PST) (envelope-from rama@casimir.proxad.net) Received: (qmail 29941 invoked by uid 1001); 25 Mar 1999 11:09:22 -0000 Message-ID: <19990325120922.A29404@proxad.net> Date: Thu, 25 Mar 1999 12:09:22 +0100 From: David Ramahefason To: freebsd-questions@freebsd.org Cc: freebsd-stable@freebsd.org Subject: Problem in compile Stable Branch Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Organization: Proxad system Team Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi ... does anyone knows how to solve this problem ??? This occurs even with a freshly installed source tree... Please answer via email thx. >>> Rebuilding tools necessary to build the include files -------------------------------------------------------------- cd /usr/src; PATH=/usr/obj/usr/src/tmp/sbin:/usr/obj/usr/src/tmp/usr/sbin:/usr/obj/usr/src/tmp/bin:/usr/obj/usr/src/tmp/usr/bin:/usr/X11R6/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/bin:/home/rama/bin BISON_SIMPLE=/usr/obj/usr/src/tmp/usr/share/misc/bison.simple COMPILER_PATH=/usr/obj/usr/src/tmp/usr/libexec:/usr/obj/usr/src/tmp/usr/bin GCC_EXEC_PREFIX=/usr/obj/usr/src/tmp/usr/lib:/usr/obj/usr/src/tmp/usr/lib/ LD_LIBRARY_PATH=/usr/obj/usr/src/tmp/usr/lib LIBRARY_PATH=/usr/obj/usr/src/tmp/usr/lib:/usr/obj/usr/src/tmp/usr/lib NOEXTRADEPEND=t OBJFORMAT_PATH=/usr/obj/usr/src/tmp/usr/libexec:/usr/libexec /usr/obj/usr/src/tmp/usr/bin/make DESTDIR=/usr/obj/usr/src/tmp -f Makefile.inc1 include-tools cd /usr/src/usr.bin/compile_et; /usr/obj/usr/src/tmp/usr/bin/make cleandepend; /usr/obj/usr/src/tmp/usr/bin/make -DWORLD -DNOINFO -DNOMAN -DNOPIC -DNOPROFILE -DNOSHARED cleandepend; /usr/obj/usr/src/tmp/usr/bin/make -DWORLD -DNOINFO -DNOMAN -DNOPIC -DNOPROFILE -DNOSHARED all; /usr/obj/usr/src/tmp/usr/bin/make -DWORLD -DNOINFO -DNOMAN -DNOPIC -DNOPROFILE -DNOSHARED -B install cleandir obj rm -f .depend /usr/obj/usr/src/usr.bin/compile_et/GPATH /usr/obj/usr/src/usr.bin/compile_et/GRTAGS /usr/obj/usr/src/usr.bin/compile_et/GSYMS /usr/obj/usr/src/usr.bin/compile_et/GTAGS rm -f .depend /usr/obj/usr/src/usr.bin/compile_et/GPATH /usr/obj/usr/src/usr.bin/compile_et/GRTAGS /usr/obj/usr/src/usr.bin/compile_et/GSYMS /usr/obj/usr/src/usr.bin/compile_et/GTAGS cc -O -pipe -I. -I/usr/src/usr.bin/compile_et/../../lib/libcom_err -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/usr.bin/compile_et/compile_et.c lex -t -l /usr/src/usr.bin/compile_et/et_lex.lex.l > et_lex.lex.c yacc -o error_table.c /usr/src/usr.bin/compile_et/error_table.y cc -O -pipe -I. -I/usr/src/usr.bin/compile_et/../../lib/libcom_err -I/usr/obj/usr/src/tmp/usr/include -c error_table.c cc -O -pipe -I. -I/usr/src/usr.bin/compile_et/../../lib/libcom_err -I/usr/obj/usr/src/tmp/usr/include -static -o compile_et compile_et.o error_table.o -ll error_table.o: In function `yylex': error_table.o(.text+0x7d3): undefined reference to `yywrap' error_table.o: In function `input': error_table.o(.text+0xd48): undefined reference to `yywrap' *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. -- /David Ramahefason / /rama@netfacile.net http://casimir.proxad.net/Images/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Mar 25 3:43:41 1999 Delivered-To: freebsd-stable@freebsd.org Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (Postfix) with ESMTP id ACEEF14D7E for ; Thu, 25 Mar 1999 03:43:37 -0800 (PST) (envelope-from brian@lan.awfulhak.org) Received: from keep.lan.Awfulhak.org (keep.lan.Awfulhak.org [172.16.0.8]) by awfulhak.org (8.9.2/8.9.2) with ESMTP id LAA07597; Thu, 25 Mar 1999 11:43:04 GMT (envelope-from brian@lan.awfulhak.org) Received: from keep.lan.Awfulhak.org (localhost [127.0.0.1]) by keep.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id IAA00737; Thu, 25 Mar 1999 08:23:08 GMT (envelope-from brian@keep.lan.Awfulhak.org) Message-Id: <199903250823.IAA00737@keep.lan.Awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: mi@aldan.algebra.com Cc: stable@FreeBSD.ORG Subject: Re: installworld fails In-reply-to: Your message of "Thu, 25 Mar 1999 01:03:34 EST." <199903250603.BAA25809@misha.cisco.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 25 Mar 1999 08:23:08 +0000 From: Brian Somers Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Indeed, the /usr/share/examples/ppp did not exist... > > -mi Oops - fixed :-/ -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Mar 25 3:43:55 1999 Delivered-To: freebsd-stable@freebsd.org Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (Postfix) with ESMTP id D218E15367; Thu, 25 Mar 1999 03:43:49 -0800 (PST) (envelope-from brian@lan.awfulhak.org) Received: from keep.lan.Awfulhak.org (keep.lan.Awfulhak.org [172.16.0.8]) by awfulhak.org (8.9.2/8.9.2) with ESMTP id LAA07627; Thu, 25 Mar 1999 11:43:19 GMT (envelope-from brian@lan.awfulhak.org) Received: from keep.lan.Awfulhak.org (localhost [127.0.0.1]) by keep.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id IAA00724; Thu, 25 Mar 1999 08:22:04 GMT (envelope-from brian@keep.lan.Awfulhak.org) Message-Id: <199903250822.IAA00724@keep.lan.Awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: Oscar Bonilla Cc: jkh@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: make world fails In-reply-to: Your message of "Wed, 24 Mar 1999 19:35:30 CST." <19990324193530.A71967@fisicc-ufm.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 25 Mar 1999 08:22:04 +0000 From: Brian Somers Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > while making world, an install -c of chap-auth in /usr/share/examples/ppp > fails because the directory ppp does not exist under /usr/share/examples > i think that directory was recently added. > > mkdir /usr/share/example/ppp seemed to fix the problem > > regards, > > -oscar Yep, I noticed this after I committed, started a ``make world'', went to bed and got up this morning... It's fixed now - sorry 'bout that. -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Mar 25 4:19:59 1999 Delivered-To: freebsd-stable@freebsd.org Received: from trantor.sc.metrolink.com (trantor.sc.metrolink.com [209.12.162.18]) by hub.freebsd.org (Postfix) with ESMTP id 08E0C15002 for ; Thu, 25 Mar 1999 04:19:57 -0800 (PST) (envelope-from anderson@metrolink.com) Received: from trantor.sc.metrolink.com (trantor.sc.metrolink.com [209.12.162.18]) by trantor.sc.metrolink.com (8.8.8/8.8.8) with SMTP id HAA26070 for ; Thu, 25 Mar 1999 07:19:32 -0500 (EST) (envelope-from anderson@metrolink.com) Date: Thu, 25 Mar 1999 07:19:31 -0500 (EST) From: Stuart Anderson X-Sender: anderson@trantor.sc.metrolink.com To: freebsd-stable@FreeBSD.ORG Subject: Re: SCSI hangs/timout, ncr53C8xx, 3.1-STABLE In-Reply-To: <19990325005936.A439@dialup124.mi.uni-koeln.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 25 Mar 1999, Stefan Esser wrote: > On 1999-03-24 18:01 +0100, Oyvind Moll wrote: > > I run 3.1-STABLE with kernel and world built from source cvsupped > > 1999-03-04. > > > > My problem: I try to dump an audio-CD from a Philips CDD2600 > > CD-R-drive (using tosha). Three of the about ten times that I've > > tried to dump a CD, tosha would suddenly report "SCSI read/write > > error" or something (sorry, forgot to write that one down) and I would > > get messages like these on my console: Just as a point of information, I saw this behavior a few times on a 2.2.7 system. Stuart Stuart R. Anderson anderson@metrolink.com Metro Link Incorporated South Carolina Office 4711 North Powerline Road 129 Secret Cove Drive Fort Lauderdale, Florida 33309 Lexington, SC 29072 voice: 954.938.0283 voice: 803.951.3630 fax: 954.938.1982 SkyTel: 800.405.3401 http://www.metrolink.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Mar 25 9: 4:13 1999 Delivered-To: freebsd-stable@freebsd.org Received: from atommuell.oeh.uni-linz.ac.at (atommuell.oeh.uni-linz.ac.at [140.78.214.101]) by hub.freebsd.org (Postfix) with ESMTP id 813FA14C0D for ; Thu, 25 Mar 1999 09:04:01 -0800 (PST) (envelope-from ferdl@atommuell.oeh.uni-linz.ac.at) Received: from localhost (ferdl@localhost) by atommuell.oeh.uni-linz.ac.at (8.9.2/8.9.1) with ESMTP id SAA48269 for ; Thu, 25 Mar 1999 18:03:51 +0100 (CET) (envelope-from ferdl@atommuell.oeh.uni-linz.ac.at) Date: Thu, 25 Mar 1999 18:03:51 +0100 (CET) From: Ferdinand Goldmann To: freebsd-stable@freebsd.org Subject: Ordering 3.1 - The Saga begins Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello. I know that I am rather off-topic on this mailing list with my complaint, but I just have to get this off my mind. About 6 weeks ago, my friend and I ordered 6 FreeBSD 3.1 CD sets and some other things from www.freebsdmall.com. However, until today, we have not seen anything of our order. About one week ago, I sent e-mail to orders@cdrom.com, as suggested on this mailing list before (by Jordan Hubbard himself AFAIR). The e-mail is still un-answered. Last Saturday, we sent a fax to Walnut Creek, containing a description of the problem and the content of the e-mail my friend received from www.freebsdmall.com in response to the order. The fax is still un-answered as well. So I have one simple question, and maybe someone on this list can give me an answer. Why does Walnut Creek ignore this order? Is it not worthy enough? Have the people at Walnut Creek mixed up Austria with a country like Iraq, for which the US government has (very questionable) export restrictions? Or are they just not interested in selling FreeBSD to us? 2 of those 6 FreeBSD CD sets are intended for people who are currently primarily Linux users. They are starting to ask me why they receive Linux CDs so much faster. This is not nice. In fact, even my Sun Solaris 2.6 package arrived faster. It would be good to see more FreeBSD people around at our university, but if we can't even get some CDs to make advertisment for it, this won't be easy. I am starting to feel annoyed, so I just wanted to tell you about this. FreeBSD is such a fine product in every other respect. Again, sorry for abusing the mailing list in this way. If you know a solution (apart from calling them directly, which I have not done yet), let me know please. Regards, Goldmann Ferdinand (Ferdinand.Goldmann@oeh.uni-linz.ac.at) Joerg Lentsch (Joerg.Lentsch@oeh.uni-linz.ac.at) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Mar 25 9:17:38 1999 Delivered-To: freebsd-stable@freebsd.org Received: from holly.dyndns.org (ip42.houston2.tx.pub-ip.psi.net [38.11.201.42]) by hub.freebsd.org (Postfix) with ESMTP id 2993F14DBC for ; Thu, 25 Mar 1999 09:16:56 -0800 (PST) (envelope-from chris@holly.dyndns.org) Received: (from chris@localhost) by holly.dyndns.org (8.9.3/8.9.3) id LAA37300; Thu, 25 Mar 1999 11:15:55 -0600 (CST) (envelope-from chris) Date: Thu, 25 Mar 1999 11:15:44 -0600 From: Chris Costello To: Ferdinand Goldmann Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Ordering 3.1 - The Saga begins Message-ID: <19990325111544.A37289@holly.dyndns.org> Reply-To: chris@calldei.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4us In-Reply-To: ; from Ferdinand Goldmann on Thu, Mar 25, 1999 at 06:03:51PM +0100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Mar 25, 1999, Ferdinand Goldmann wrote: > Hello. > > I know that I am rather off-topic on this mailing list with my > complaint, but I just have to get this off my mind. > > About 6 weeks ago, my friend and I ordered 6 FreeBSD 3.1 CD sets > and some other things from www.freebsdmall.com. However, until > today, we have not seen anything of our order. > > About one week ago, I sent e-mail to orders@cdrom.com, as suggested > on this mailing list before (by Jordan Hubbard himself AFAIR). > The e-mail is still un-answered. > > Last Saturday, we sent a fax to Walnut Creek, containing a description > of the problem and the content of the e-mail my friend received > from www.freebsdmall.com in response to the order. The fax is > still un-answered as well. You could try calling them -- that's what I did. Changed to freebsd-questions. > Regards, > Goldmann Ferdinand > (Ferdinand.Goldmann@oeh.uni-linz.ac.at) > Joerg Lentsch > (Joerg.Lentsch@oeh.uni-linz.ac.at) > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Mar 25 9:36: 9 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.rdc1.on.home.com (ha1.rdc1.on.wave.home.com [24.2.9.66]) by hub.freebsd.org (Postfix) with ESMTP id E6B5C14EEA for ; Thu, 25 Mar 1999 09:36:07 -0800 (PST) (envelope-from iceage@home.com) Received: from cr857386-a ([24.112.224.81]) by mail.rdc1.on.home.com (InterMail v4.00.03 201-229-104) with ESMTP id <19990325173547.RKGJ13966.mail.rdc1.on.home.com@cr857386-a> for ; Thu, 25 Mar 1999 09:35:47 -0800 Message-ID: <199903251235080310.0582869C@mail> X-Mailer: Calypso Version 3.00.00.13 (3) Date: Thu, 25 Mar 1999 12:35:08 -0500 Reply-To: iceage@mindless.com From: "iCeAgE" To: freebsd-stable@FreeBSD.ORG Subject: please add me to your mailing list Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="=====_92238330841=_" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --=====_92238330841=_ Content-Type: text/plain; charset="us-ascii" --=====_92238330841=_ Content-Type: text/html; charset="us-ascii" --=====_92238330841=_-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Mar 25 10: 2:40 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 E41C714C3F for ; Thu, 25 Mar 1999 10:02:38 -0800 (PST) (envelope-from Cy.Schubert@uumail.gov.bc.ca) Received: (from daemon@localhost) by point.osg.gov.bc.ca (8.9.1/8.8.8) id KAA03293 for ; Thu, 25 Mar 1999 10:02:19 -0800 Received: from passer.osg.gov.bc.ca(142.32.110.29) via SMTP by point.osg.gov.bc.ca, id smtpda03291; Thu Mar 25 10:02:00 1999 Received: (from uucp@localhost) by passer.osg.gov.bc.ca (8.9.3/8.9.1) id KAA21362 for ; Thu, 25 Mar 1999 10:01:59 -0800 (PST) Message-Id: <199903251801.KAA21362@passer.osg.gov.bc.ca> Received: from localhost.osg.gov.bc.ca(127.0.0.1), claiming to be "passer.osg.gov.bc.ca" via SMTP by localhost.osg.gov.bc.ca, id smtpdv21359; Thu Mar 25 10:01:58 1999 X-Mailer: exmh version 2.0.2 2/24/98 Reply-To: Cy Schubert - ITSD Open Systems Group X-OS: FreeBSD 3.1-RELEASE X-Sender: cschuber To: freebsd-stable@freebsd.org Subject: Netscape Looping Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 25 Mar 1999 10:01:58 -0800 From: Cy Schubert Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have an interesting problem where Netscape loops during startup. It loops getting a number of FPE signals, two ALRM signals, it issues a gettimeofday(), and it loops again. It is reproducible under very specific circumstances. To give you some background I will discuss what works first and what doesn't work last. All machines are running 3.1-RELEASE ELF with a.out compatibility libraries.. Netscape in question is 4.07 and 4.08 for FreeBSD. Configuration W (at work): A single machine with a PII, 128MB RAM, and a Mach64 card. This configuration works with no problems. This machine was built using make aout-to-elf. Configuraion H (at home): Machine A ------ Ethernet through attic ------- Machine B ~~~~~~~~~ ~~~~~~~~~ P120 486DX/33 80MB RAM 20MB RAM S3 Card Trident SVGA Machine A was built using make aout-to-elf. Machine B was installed from CDROM. Netscape running on Machine B and displayed to an XServer on machine B works. Netscape running on Machine A and displayed to Machine B works. Netscape running on Machine B and displayed to Machine A works. Netscape running on Machine A and displayed to Machine A loops forever. Another interesting observation is that when using an Xserver on the Configuration H machine at work or when using an Xserver on Machine B at home vmstat reports AVM as some normal number, e.g. 3000 KB or more, while using an Xserver on Machine A at home vmstat reports that AVM is a little more than 3700000 KB. AVM on Machine a drops to a normal value when the Xserver is not in use. Machine B uses X binaries served from Machine A via NFS, so except for a different XF86Config the X11R6 directory trees are the same. Does anyone have any ideas? Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 Open Systems Group Internet: Cy.Schubert@uumail.gov.bc.ca ITSD Cy.Schubert@gems8.gov.bc.ca Province of BC To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Mar 25 11:16: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 0E8A114EFC for ; Thu, 25 Mar 1999 11:16: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.1/8.9.1) with ESMTP id LAA04612; Thu, 25 Mar 1999 11:16:29 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.2/8.9.1) id LAA03178; Thu, 25 Mar 1999 11:16:27 -0800 (PST) (envelope-from jdp@polstra.com) Date: Thu, 25 Mar 1999 11:16:27 -0800 (PST) Message-Id: <199903251916.LAA03178@vashon.polstra.com> To: chad@dcfinc.com Subject: Re: make buildworld fails (fwd) In-Reply-To: <199903211130.EAA04488@freebie.dcfinc.com> Organization: Polstra & Co., Seattle, WA Cc: stable@freebsd.org Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199903211130.EAA04488@freebie.dcfinc.com>, Chad R. Larson wrote: > Looking in the code, it seemed that "objfiles.c" needed to include > "nm.h" to get the definition of "kernel_debugging". So I deleted it > and re-cvsupped to see if the file had changed. It hadn't. > > That left me believing there had to be some cruft in my source tree. > I removed all of /usr/src/contrib, and then cvsup'd again. Way too > long later, I did another "make buildworld", which was successful. > > Anyone understand why/how the source tree could get broken in a way > that cvsup didn't catch? Yes. You had some extra files, probably .o files, in your source tree. CVSup doesn't remove files it doesn't know about. (How would you like it to remove your kernel config file, for instance?) In CVSup-16.0, there's a nifty "cvsupchk" script to check for extra files. It was contributed by Joseph Koshy. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-interest is the aphrodisiac of belief." -- James V. DeLong To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Mar 25 11:53: 4 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 E663C14EC8 for ; Thu, 25 Mar 1999 11:53:01 -0800 (PST) (envelope-from Cy.Schubert@uumail.gov.bc.ca) Received: (from daemon@localhost) by point.osg.gov.bc.ca (8.9.1/8.8.8) id LAA03691; Thu, 25 Mar 1999 11:52:42 -0800 Received: from passer.osg.gov.bc.ca(142.32.110.29) via SMTP by point.osg.gov.bc.ca, id smtpda03689; Thu Mar 25 11:52:24 1999 Received: (from uucp@localhost) by passer.osg.gov.bc.ca (8.9.3/8.9.1) id LAA23075; Thu, 25 Mar 1999 11:52:23 -0800 (PST) Message-Id: <199903251952.LAA23075@passer.osg.gov.bc.ca> Received: from localhost.osg.gov.bc.ca(127.0.0.1), claiming to be "passer.osg.gov.bc.ca" via SMTP by localhost.osg.gov.bc.ca, id smtpdf23068; Thu Mar 25 11:52:16 1999 X-Mailer: exmh version 2.0.2 2/24/98 Reply-To: Cy Schubert - ITSD Open Systems Group X-OS: FreeBSD 3.1-RELEASE X-Sender: cschuber To: Cy Schubert - ITSD Open Systems Group Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Netscape Looping In-reply-to: Your message of "Thu, 25 Mar 1999 10:01:58 PST." <199903251801.KAA21362@passer.osg.gov.bc.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 25 Mar 1999 11:52:16 -0800 From: Cy Schubert Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Let me add another wrinkle to this saga. Netscape 4.51 loops, in the same tight loop, on the Configuration W machine as on Machine A in Configuration H, below. I suspect that 4.51 is bigger and therefore this may be VM related. Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 Open Systems Group Internet: Cy.Schubert@uumail.gov.bc.ca ITSD Cy.Schubert@gems8.gov.bc.ca Province of BC In message <199903251801.KAA21362@passer.osg.gov.bc.ca>, Cy Schubert writes: > I have an interesting problem where Netscape loops during startup. > It loops getting a number of FPE signals, two ALRM signals, it > issues a gettimeofday(), and it loops again. It is reproducible > under very specific circumstances. To give you some background I > will discuss what works first and what doesn't work last. > > All machines are running 3.1-RELEASE ELF with a.out compatibility > libraries.. Netscape in question is 4.07 and 4.08 for FreeBSD. > > Configuration W (at work): > > A single machine with a PII, 128MB RAM, and a Mach64 card. This > configuration works with no problems. This machine was built using > make aout-to-elf. > > > Configuraion H (at home): > > Machine A ------ Ethernet through attic ------- Machine B > ~~~~~~~~~ ~~~~~~~~~ > P120 486DX/33 > 80MB RAM 20MB RAM > S3 Card Trident SVGA > > Machine A was built using make aout-to-elf. Machine B was > installed from CDROM. > > Netscape running on Machine B and displayed to an XServer on > machine B works. > > Netscape running on Machine A and displayed to Machine B works. > > Netscape running on Machine B and displayed to Machine A works. > > Netscape running on Machine A and displayed to Machine A loops > forever. > > Another interesting observation is that when using an Xserver on > the Configuration H machine at work or when using an Xserver on > Machine B at home vmstat reports AVM as some normal number, e.g. > 3000 KB or more, while using an Xserver on Machine A at home vmstat > reports that AVM is a little more than 3700000 KB. AVM on Machine > a drops to a normal value when the Xserver is not in use. Machine > B uses X binaries served from Machine A via NFS, so except for a > different XF86Config the X11R6 directory trees are the same. > > Does anyone have any ideas? > > > Regards, Phone: (250)387-8437 > Cy Schubert Fax: (250)387-5766 > Open Systems Group Internet: Cy.Schubert@uumail.gov.bc.ca > ITSD Cy.Schubert@gems8.gov.bc.ca > Province of BC > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Mar 25 13:43:12 1999 Delivered-To: freebsd-stable@freebsd.org Received: from csmd2.cs.uni-magdeburg.de (csmd2.CS.Uni-Magdeburg.De [141.44.22.2]) by hub.freebsd.org (Postfix) with ESMTP id 53A1814D21 for ; Thu, 25 Mar 1999 13:43:05 -0800 (PST) (envelope-from jesse@mail.CS.Uni-Magdeburg.De) Received: from knecht.cs.uni-magdeburg.de (jesse@knecht [141.44.21.3]) by csmd2.cs.uni-magdeburg.de (8.9.1a/8.9.1) with ESMTP id WAA18050 for ; Thu, 25 Mar 1999 22:42:36 +0100 (MET) Received: (from jesse@localhost) by knecht.cs.uni-magdeburg.de (8.8.8+Sun/8.8.8) id WAA01213; Thu, 25 Mar 1999 22:42:42 +0100 (MET) From: Roland Jesse MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14074.44498.157200.518328@cs.uni-magdeburg.de> Date: Thu, 25 Mar 1999 22:42:42 +0100 (MET) To: freebsd-stable@freebsd.org Subject: /usr/src/include/pthread/uthread/pthread.h not available? X-Mailer: VM 6.70 under 20.4 "Emerald" XEmacs Lucid Reply-To: Roland Jesse X-Organization: University of Magdeburg X-Pgp-Fingerprint: 5D 08 5A E3 B4 AA 68 C1 FF 67 06 29 62 DD 9A D7 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I was just going to install the latest and greatest linux threads. The port that is available at http://lt.tar.com requires /usr/src/include/pthread/uthread/pthread.h. /usr/src/include/pthread does not even exist. I cvsuped the RELENG_3 sources (src-all) today. Any ideas what I am missing? Roland To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Mar 25 15: 4:21 1999 Delivered-To: freebsd-stable@freebsd.org Received: from hyperhost.net (ether.lightrealm.com [207.159.132.5]) by hub.freebsd.org (Postfix) with ESMTP id D6FDC14E06 for ; Thu, 25 Mar 1999 15:04:11 -0800 (PST) (envelope-from patseal@hyperhost.net) Received: from port3.annex8.radix.net (port3.annex8.radix.net [205.252.108.3]) by hyperhost.net (8.8.5/8.8.5) with ESMTP id SAA20433; Thu, 25 Mar 1999 18:03:29 -0500 (EST) Date: Thu, 25 Mar 1999 18:03:20 -0500 (EST) From: Patrick Seal To: Roland Jesse Cc: freebsd-stable@FreeBSD.ORG Subject: Re: /usr/src/include/pthread/uthread/pthread.h not available? In-Reply-To: <14074.44498.157200.518328@cs.uni-magdeburg.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 25 Mar 1999, Roland Jesse wrote: > Hi, > > I was just going to install the latest and greatest linux threads. > > The port that is available at http://lt.tar.com requires > /usr/src/include/pthread/uthread/pthread.h. /usr/src/include/pthread > does not even exist. I cvsuped the RELENG_3 sources (src-all) today. > > Any ideas what I am missing? The point. > I was just going to install the latest and greatest linux threads. This is freebsd, not linux, it has pthreads already man pthread ------------------------------------ _____________________________________ Patrick Seal |"Microsoft isn't evil, they just make | really crappy operating systems." Hyperhost - http://www.hyperhost.net| -Linus Torvalds hosting and Design http://www.freebsd.org - http://www.linux.org On Thu, 25 Mar 1999, Roland Jesse wrote: > Hi, > > I was just going to install the latest and greatest linux threads. > > The port that is available at http://lt.tar.com requires > /usr/src/include/pthread/uthread/pthread.h. /usr/src/include/pthread > does not even exist. I cvsuped the RELENG_3 sources (src-all) today. > > Any ideas what I am missing? > > Roland > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Mar 25 15:10:19 1999 Delivered-To: freebsd-stable@freebsd.org Received: from klentaq1.emergingtech.org (klentaq1.emergingtech.org [199.217.151.234]) by hub.freebsd.org (Postfix) with ESMTP id 7A8D015432 for ; Thu, 25 Mar 1999 15:10:14 -0800 (PST) (envelope-from stabilizer@klentaq1.emergingtech.org) Received: (from stabilizer@localhost) by klentaq1.emergingtech.org (8.9.2/8.9.2) id RAA34177 for freebsd-stable@freebsd.org; Thu, 25 Mar 1999 17:14:12 GMT (envelope-from stabilizer) From: Wayne M Barnes Message-Id: <199903251714.RAA34177@klentaq1.emergingtech.org> Subject: .sgml To: freebsd-stable@freebsd.org Date: Thu, 25 Mar 1999 17:14:12 +0000 (GMT) X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Say, what's a .sgml file, and what software reads them? i.e.: [ seen on cvsup ] Edit doc/zh/FAQ/misc.sgml Edit doc/zh/FAQ/network.sgml Edit doc/zh/FAQ/preface.sgml Edit doc/zh/FAQ/troubleshoot.sgml Alternatively, what's the way to read the above files? Wayne M Barnes stabilizer@klentaq1.emergingtech.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Mar 25 15:18:30 1999 Delivered-To: freebsd-stable@freebsd.org Received: from angel.double-barrel.be (mail.double-barrel.be [194.7.102.20]) by hub.freebsd.org (Postfix) with ESMTP id 57B8614F71 for ; Thu, 25 Mar 1999 15:18:02 -0800 (PST) (envelope-from mvergall@ns.double-barrel.be) Received: from ns.double-barrel.be (ns.double-barrel.be [194.7.102.18]) by angel.double-barrel.be (8.9.1b+Sun/8.9.1) with ESMTP id AAA02078; Fri, 26 Mar 1999 00:16:50 +0100 (MET) Received: from localhost (mvergall@localhost) by ns.double-barrel.be (8.8.7/8.8.7) with ESMTP id AAA04434; Fri, 26 Mar 1999 00:16:47 +0100 Date: Fri, 26 Mar 1999 00:16:47 +0100 (CET) From: "Michael C. Vergallen" To: Wayne M Barnes Cc: freebsd-stable@FreeBSD.ORG Subject: Re: .sgml In-Reply-To: <199903251714.RAA34177@klentaq1.emergingtech.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 Some kind off html format. Use your imagination.. Michael --- Michael C. Vergallen A.k.A. Mad Mike, Sportstraat 28 http://www.double-barrel.be/mvergall/ B 9000 Gent ftp://ftp.double-barrel.be/pub/linux/ Belgium tel : 32-9-2227764 Fax : 32-9-2224976 On Thu, 25 Mar 1999, Wayne M Barnes wrote: > > Say, what's a .sgml file, and what software reads them? > > i.e.: [ seen on cvsup ] > Edit doc/zh/FAQ/misc.sgml > Edit doc/zh/FAQ/network.sgml > Edit doc/zh/FAQ/preface.sgml > Edit doc/zh/FAQ/troubleshoot.sgml > > > Alternatively, what's the way to read the above files? > > Wayne M Barnes stabilizer@klentaq1.emergingtech.org > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Mar 25 15:24:30 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 5AE8014D64 for ; Thu, 25 Mar 1999 15:24:20 -0800 (PST) (envelope-from pfeifer@dbai.tuwien.ac.at) Received: from alphard (alphard [128.130.111.37]) by vexpert.dbai.tuwien.ac.at (8.9.1/8.9.1) with ESMTP id AAA02468; Fri, 26 Mar 1999 00:23:59 +0100 (MET) Date: Fri, 26 Mar 1999 00:23:58 +0100 (MET) From: Gerald Pfeifer To: Ferdinand Goldmann Cc: freebsd-stable@freebsd.org Subject: Re: Ordering 3.1 - The Saga begins 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 While I cannot and do not want to speak for Jordan, having an Austrian address as well, here are my 0.02 Groschen. On Thu, 25 Mar 1999, Ferdinand Goldmann wrote: > So I have one simple question, and maybe someone on this list can > give me an answer. Why does Walnut Creek ignore this order? Is it > not worthy enough? For sure it is. I've had smaller orders shipped quickly. > Have the people at Walnut Creek mixed up Austria with a country like > Iraq, for which the US government has (very questionable) export > restrictions? No. I have received my 3.0 and 3.1 disk very quickly, and a FreeBSD cap and Polo short I ordered ten days ago arrived yesterday. So apparently your Austrian address is not the problem. My personal experience with cdrom.com has been very favourable. E-mail response has been quick and helpful, shipment immediate and with problems. Gerald -- Gerald "Jerry" pfeifer@dbai.tuwien.ac.at http://www.dbai.tuwien.ac.at/~pfeifer/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Mar 25 15:27:50 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.webmaster.com (mail.webmaster.com [209.133.28.138]) by hub.freebsd.org (Postfix) with ESMTP id DE05615597 for ; Thu, 25 Mar 1999 15:27:47 -0800 (PST) (envelope-from davids@webmaster.com) Received: from whenever ([209.133.29.2]) by mail.webmaster.com (Post.Office MTA v3.5.3 release 223 ID# 0-12345L500S10000V35) with SMTP id com; Thu, 25 Mar 1999 15:17:57 -0800 From: "David Schwartz" To: "Patrick Seal" , "Roland Jesse" Cc: Subject: RE: /usr/src/include/pthread/uthread/pthread.h not available? Date: Thu, 25 Mar 1999 15:27:26 -0800 Message-ID: <000801be7717$0ad2c190$021d85d1@whenever.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 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 In-Reply-To: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Of course, some people might want a threads implementation that performs well, doesn't crash, and works with 'poll'. DS > > Hi, > > > > I was just going to install the latest and greatest linux threads. > > > > The port that is available at http://lt.tar.com requires > > /usr/src/include/pthread/uthread/pthread.h. /usr/src/include/pthread > > does not even exist. I cvsuped the RELENG_3 sources (src-all) today. > > > > Any ideas what I am missing? > > The point. > > I was just going to install the latest and greatest linux threads. > This is freebsd, not linux, it has pthreads already > > man pthread To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Mar 25 15:40:12 1999 Delivered-To: freebsd-stable@freebsd.org Received: from freebie.dcfinc.com (freebie.dcfinc.com [138.113.5.128]) by hub.freebsd.org (Postfix) with ESMTP id 9ACC115440 for ; Thu, 25 Mar 1999 15:40:08 -0800 (PST) (envelope-from chad@freebie.dcfinc.com) Received: (from chad@localhost) by freebie.dcfinc.com (8.8.7/8.8.3a) id QAA12671; Thu, 25 Mar 1999 16:38:35 -0700 (MST) From: "Chad R. Larson" Message-Id: <199903252338.QAA12671@freebie.dcfinc.com> Subject: Re: .sgml To: mvergall@mail.double-barrel.be (Michael C. Vergallen) Date: Thu, 25 Mar 1999 16:38:35 -0700 (MST) Cc: stabilizer@klentaq1.emergingtech.org, freebsd-stable@FreeBSD.ORG In-Reply-To: from "Michael C. Vergallen" at "Mar 26, 99 00:16:47 am" Reply-To: chad@dcfinc.com X-unexpected: The Spanish Inquisition X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Thu, 25 Mar 1999, Wayne M Barnes wrote: > > > > > Say, what's a .sgml file, and what software reads them? > > > > i.e.: [ seen on cvsup ] > > Edit doc/zh/FAQ/misc.sgml > > Edit doc/zh/FAQ/network.sgml > > Edit doc/zh/FAQ/preface.sgml > > Edit doc/zh/FAQ/troubleshoot.sgml > > > > > > Alternatively, what's the way to read the above files? > > > > Wayne M Barnes stabilizer@klentaq1.emergingtech.org Standardized Graphics Markup Language (or something close to that). The language of the Web, Hypertext Markup Language (HTML), is a special case of this. And Extensible Markup Language (XML) seems to be where the world is headed. -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org chad@anasazi.com 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 Thu Mar 25 15:41:39 1999 Delivered-To: freebsd-stable@freebsd.org Received: from freebie.dcfinc.com (freebie.dcfinc.com [138.113.5.128]) by hub.freebsd.org (Postfix) with ESMTP id 5B1A014CED for ; Thu, 25 Mar 1999 15:41:37 -0800 (PST) (envelope-from chad@freebie.dcfinc.com) Received: (from chad@localhost) by freebie.dcfinc.com (8.8.7/8.8.3a) id QAA12697; Thu, 25 Mar 1999 16:40:44 -0700 (MST) From: "Chad R. Larson" Message-Id: <199903252340.QAA12697@freebie.dcfinc.com> Subject: Re: Ordering 3.1 - The Saga begins To: ferdl@atommuell.oeh.uni-linz.ac.at (Ferdinand Goldmann) Date: Thu, 25 Mar 1999 16:40:43 -0700 (MST) Cc: freebsd-stable@FreeBSD.ORG In-Reply-To: from Ferdinand Goldmann at "Mar 25, 99 06:03:51 pm" Reply-To: chad@dcfinc.com X-unexpected: The Spanish Inquisition X-Mailer: ELM [version 2.4ME+ PL22 (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 > Last Saturday, we sent a fax to Walnut Creek, containing a description > of the problem and the content of the e-mail my friend received from > www.freebsdmall.com in response to the order. The fax is still > un-answered as well. This is contrary to my experience. Walnut Creek has been =very= responsive. To e-mail, phone calls, whatever. And shipping for items that are in stock has been prompt as well. -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org chad@anasazi.com 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 Thu Mar 25 15:46:18 1999 Delivered-To: freebsd-stable@freebsd.org Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1]) by hub.freebsd.org (Postfix) with ESMTP id 99D1A14CED for ; Thu, 25 Mar 1999 15:46:10 -0800 (PST) (envelope-from jfieber@fallout.campusview.indiana.edu) Received: from localhost (jfieber@localhost) by fallout.campusview.indiana.edu (8.9.2/8.9.1) with ESMTP id SAA70677; Thu, 25 Mar 1999 18:45:17 -0500 (EST) Date: Thu, 25 Mar 1999 18:45:17 -0500 (EST) From: John Fieber To: Wayne M Barnes Cc: freebsd-stable@FreeBSD.ORG Subject: Re: .sgml In-Reply-To: <199903251714.RAA34177@klentaq1.emergingtech.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 25 Mar 1999, Wayne M Barnes wrote: > Say, what's a .sgml file, and what software reads them? ISO 8879:1986: Standard Generalized Markup Language. SGML is used to define markup languages. SGML also defines parsing rules such that a conforming parser can parse any past, present or future markup language defined with SGML. HTML is a markup language defined using SGML. The definition is known as a Document Type Definition, or DTD. The files you are looking at use a different DTD, in this case Linuxdoc. The textproc/sgmlformat port will convert these to HTML and to postscript or text via groff. XML is a simplified version of SGML. -john To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Mar 25 15:54:43 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 C530A14D03 for ; Thu, 25 Mar 1999 15:54:39 -0800 (PST) (envelope-from wheelman@nuc.net) Received: from electron (dhcp1.ecofl.com [204.49.61.49]) by lepton.nuc.net (8.8.8/8.8.8) with SMTP id RAA20376 for ; Thu, 25 Mar 1999 17:54:20 -0600 (CST) (envelope-from wheelman@nuc.net) From: "Jaime Bozza" To: Subject: PAM and Apache Date: Thu, 25 Mar 1999 17:52:38 -0600 Message-ID: <002001be771a$904be2e0$313d31cc@nuc.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211 Importance: Normal Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, Since FreeBSD now has some PAM support, I decided to try and use the mod_auth_pam Apache module. The module seems to compile just fine, but I can't manage to validate using it. Basically, I receive these errors: Mar 25 17:51:06 lepton2 httpd: unable to resolve symbol: pam_sm_acct_mgmt Mar 25 17:51:06 lepton2 httpd: unable to resolve symbol: pam_sm_chauthtok Mar 25 17:51:06 lepton2 httpd: unable to resolve symbol: pam_sm_chauthtok Mar 25 17:51:07 lepton2 httpd: unable to resolve symbol: pam_sm_acct_mgmt From what I can see, these are available in libpam, but httpd can't find them. Any ideas what I may be doing wrong? Or, (another question), has anyone else been able to use PAM with Apache under FreeBSD Stable? (3.1-stable, that is) Jaime Bozza Nucleus Communications To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Mar 25 15:54:50 1999 Delivered-To: freebsd-stable@freebsd.org Received: from shell.futuresouth.com (shell.futuresouth.com [198.78.58.28]) by hub.freebsd.org (Postfix) with ESMTP id 10D93151E7 for ; Thu, 25 Mar 1999 15:54:48 -0800 (PST) (envelope-from fullermd@futuresouth.com) Received: (from fullermd@localhost) by shell.futuresouth.com (8.9.3/8.9.3) id RAA28257; Thu, 25 Mar 1999 17:54:15 -0600 (CST) Date: Thu, 25 Mar 1999 17:54:15 -0600 From: "Matthew D. Fuller" To: Cy Schubert - ITSD Open Systems Group Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Netscape Looping Message-ID: <19990325175415.U17547@futuresouth.com> References: <199903251801.KAA21362@passer.osg.gov.bc.ca> <199903251952.LAA23075@passer.osg.gov.bc.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: <199903251952.LAA23075@passer.osg.gov.bc.ca>; from Cy Schubert on Thu, Mar 25, 1999 at 11:52:16AM -0800 X-OS: FreeBSD Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Mar 25, 1999 at 11:52:16AM -0800, a little birdie told me that Cy Schubert remarked > Let me add another wrinkle to this saga. > > Netscape 4.51 loops, in the same tight loop, on the Configuration W > machine as on Machine A in Configuration H, below. I suspect that > 4.51 is bigger and therefore this may be VM related. FWIW, I had the 'tight loop' problem a lot from 4.04-4.08. Running 4.5 now and have had the problem once in about 2 months. Used to get it about every week with 4.0x. 4.0x also crashed fairly often on sig10's, which I haven't seen with 4.5. It's certainly bigger, and it FEELS slower interactively sometimes, but it not crashing (with my customary 25+ windows open) is well worth that. --- *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* | Matthew Fuller http://www.over-yonder.net/ | * fullermd@futuresouth.com fullermd@over-yonder.net * | UNIX Systems Administrator Specializing in FreeBSD | * FutureSouth Communications ISPHelp ISP Consulting * | "The only reason I'm burning my candle at both ends, | * is because I haven't figured out how to light the * | middle yet" | *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Mar 25 15:58:28 1999 Delivered-To: freebsd-stable@freebsd.org Received: from guru.phone.net (guru.phone.net [209.157.82.120]) by hub.freebsd.org (Postfix) with SMTP id E46A514D03 for ; Thu, 25 Mar 1999 15:58:26 -0800 (PST) (envelope-from mwm@phone.net) Received: (qmail 44136 invoked by uid 100); 25 Mar 1999 23:58:07 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 25 Mar 1999 23:58:07 -0000 Date: Thu, 25 Mar 1999 15:58:07 -0800 (PST) From: Mike Meyer To: freebsd-stable@FreeBSD.ORG Subject: Re: .sgml In-Reply-To: <199903252338.QAA12671@freebie.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 Thu, 25 Mar 1999, Chad R. Larson wrote: > > > Alternatively, what's the way to read the above files? > > > > > > Wayne M Barnes stabilizer@klentaq1.emergingtech.org > > Standardized Graphics Markup Language (or something close to that). Standard Generalized Markup Language. It's a language for defining text markup languages. No graphics required. *THE* text on it is Goldfarb's "The SGML handbook." > The language of the Web, Hypertext Markup Language (HTML), is a > special case of this. The technical term is "application" - HTML is an application of SGML. The definitions of the various HTML versions are written in SGML. > And Extensible Markup Language (XML) seems to be where the world > is headed. XML is another application of SGML; this one defining a subset of SGML simplified enough to be grasped by the authors of the popular web browsers (most of *still* can't properly parse an HTML 2.0 document). Ok, that's the cynics few of XML. The official story is that it's got all the parts of SGML that aren't used by most people taken out, so that an XML parser can be written over the weekend, instead of being a major project in and of itself. ; Thu, 25 Mar 1999 16:20:59 -0800 (PST) (envelope-from jon@gw.caamora.com.au) Received: (from jon@localhost) by gw.caamora.com.au (8.8.8/8.8.8) id LAA09683; Fri, 26 Mar 1999 11:19:51 +1100 (EST) (envelope-from jon) Message-ID: <19990326111950.A9648@caamora.com.au> Date: Fri, 26 Mar 1999 11:19:50 +1100 From: jonathan michaels To: chad@dcfinc.com, Ferdinand Goldmann Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Ordering 3.1 - The Saga begins References: <199903252340.QAA12697@freebie.dcfinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199903252340.QAA12697@freebie.dcfinc.com>; from Chad R. Larson on Thu, Mar 25, 1999 at 04:40:43PM -0700 X-Operating-System: FreeBSD gw.caamora.com.au 2.2.7-RELEASE i386 X-Mood: i'm alive, if it counts Organisation: Caamora, PO Box 144, Rosebery NSW 1445 Australia Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Mar 25, 1999 at 04:40:43PM -0700, Chad R. Larson wrote: > > Last Saturday, we sent a fax to Walnut Creek, containing a description > > of the problem and the content of the e-mail my friend received from > > www.freebsdmall.com in response to the order. The fax is still > > un-answered as well. > > This is contrary to my experience. Walnut Creek has been =very= > responsive. To e-mail, phone calls, whatever. And shipping for items > that are in stock has been prompt as well. neither the original poster nor (now) i challange the veracity of the experience of those that do get a quick turnaround. but, we who do not get as good a service also need to be heard and then walnut creek might actually do something to address the very real probelms that they do have. on teh very few ocassions that i have had problems i broght them to jordans attetion and it was fixed very quickly, but off all teh email i have ever sent to orders or support at cdrom.com i have yet to get a responce .. i started with freebsd at the v2.0.5-release cd set. regards jonathan -- =============================================================================== Jonathan Michaels PO Box 144, Rosebery, NSW 1445 Australia =========================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Mar 25 17:27:55 1999 Delivered-To: freebsd-stable@freebsd.org Received: from iclub.nsu.ru (iclub.nsu.ru [193.124.222.66]) by hub.freebsd.org (Postfix) with ESMTP id CF9C915496 for ; Thu, 25 Mar 1999 17:27:46 -0800 (PST) (envelope-from fjoe@iclub.nsu.ru) Received: from localhost (fjoe@localhost) by iclub.nsu.ru (8.9.2/8.8.5) with ESMTP id HAA41649; Fri, 26 Mar 1999 07:26:57 +0600 (NS) Date: Fri, 26 Mar 1999 07:26:57 +0600 (NS) From: Max Khon To: Jaime Bozza Cc: freebsd-stable@FreeBSD.ORG Subject: Re: PAM and Apache In-Reply-To: <002001be771a$904be2e0$313d31cc@nuc.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 hi, there! On Thu, 25 Mar 1999, Jaime Bozza wrote: > Since FreeBSD now has some PAM support, I decided to try and use the > mod_auth_pam Apache module. The module seems to compile just fine, but I > can't manage to validate using it. Basically, I receive these errors: > > Mar 25 17:51:06 lepton2 httpd: unable to resolve symbol: pam_sm_acct_mgmt > Mar 25 17:51:06 lepton2 httpd: unable to resolve symbol: pam_sm_chauthtok > Mar 25 17:51:06 lepton2 httpd: unable to resolve symbol: pam_sm_chauthtok > Mar 25 17:51:07 lepton2 httpd: unable to resolve symbol: pam_sm_acct_mgmt > > >From what I can see, these are available in libpam, but httpd can't find > them. Any ideas what I may be doing wrong? Or, (another question), has > anyone else been able to use PAM with Apache under FreeBSD Stable? > (3.1-stable, that is) as far as i understand they should be defined in PAM modules. at this time FreeBSD PAM modules implement only pam_sm_setcred and pam_sm_authenticate functions /fjoe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Mar 25 18:38:12 1999 Delivered-To: freebsd-stable@freebsd.org Received: from fang.cs.sunyit.edu (fang.cs.sunyit.edu [192.52.220.66]) by hub.freebsd.org (Postfix) with ESMTP id D568315610 for ; Thu, 25 Mar 1999 18:38:08 -0800 (PST) (envelope-from meyerd1@fang.cs.sunyit.edu) Received: from fang.cs.sunyit.edu (fang.cs.sunyit.edu [192.52.220.66]) by fang.cs.sunyit.edu (8.8.8/8.8.8) with SMTP id VAA07480; Thu, 25 Mar 1999 21:39:19 -0500 (EST) (envelope-from meyerd1@fang.cs.sunyit.edu) Date: Thu, 25 Mar 1999 21:39:19 -0500 (EST) From: Daniel Aaron Meyer To: stable@FreeBSD.org Cc: Daniel Meyer Subject: NFS problem? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Im getting a lot of lag when NFS is accessed. The machines having this problem are all identical hardware. They are being served home directories via NFS. The problem does not seem to exist in 3.1-RELEASE. My initial build/install of 3.1-STABLE (3/15/99) did not have this problem. I upgraded an identical 3.1-RELEASE machine to stable and it also is having this problem. I see some changes have been committed. These machines work fine with -RELEASE, and we have an SMP machine running the lastest -STABLE without problems. Here I grab a file via ftp, downloading it to a local FS. 27533787 bytes received in 134.06 seconds (200.57 KB/s) Here is the results of the same file to an NFS mounted home directory. 27533787 bytes received in 712.78 seconds (37.72 KB/s) top during the above ftp session... ouch! last pid: 1327; load averages: 3.96, 3.25, 1.89 up 0+09:06:57 20:55:59 28 processes: 4 running, 24 sleeping CPU states: % user, % nice, % system, % interrupt, % idle Mem: 8072K Active, 30M Inact, 12M Wired, 4864K Cache, 7572K Buf, 6612K Free Swap: 200M Total, 200M Free PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND 134 root 2 0 208K 28K RUN 6:16 72.31% 72.31% nfsiod 135 root 10 0 208K 28K nfsidl 1:49 15.04% 15.04% nfsiod 1313 root 45 0 1276K 844K RUN 0:37 5.52% 5.52% ftp 1326 root 41 0 1584K 820K RUN 0:03 5.46% 4.88% top Copyright (c) 1992-1999 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.1-STABLE #4: Thu Mar 25 08:14:16 EST 1999 meyerd1@spunky.cs.sunyit.edu:/usr/src/sys/compile/SPUNKY Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 300683170 Hz CPU: Pentium II (300.68-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x634 Stepping=4 Features=0x80fbff real memory = 67108864 (65536K bytes) avail memory = 62517248 (61052K bytes) Preloaded elf kernel "kernel" at 0xf02a1000. Probing for devices on PCI bus 0: chip0: rev 0x02 on pci0.0.0 chip1: rev 0x02 on pci0.1.0 chip2: rev 0x02 on pci0.7.0 ide_pci0: rev 0x01 on pci0.7.1 chip3: rev 0x02 on pci0.7.3 tx0: rev 0x06 int a irq 11 on pci0.15.0 tx0: address 00:e0:29:1f:b0:4d, type SMC9432TX, Auto-Neg 10Mbps vga0: rev 0x9a on pci0.20.0 Probing for devices on PCI bus 1: Probing for PnP devices: CSN 1 Vendor ID: CTL0070 [0x70008c0e] Serial 0xffffffff Comp ID: PNPb02f [0x2fb0d041] pcm1 (SB16pnp sn 0xffffffff) at 0x220-0x22f irq 5 drq 1 flags 0x15 on isa Probing for devices on the ISA bus: sc0 on isa sc0: VGA color <16 virtual consoles, flags=0x0> atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa psm0 irq 12 on isa psm0: model Generic PS/2 mouse, device ID 0 sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A pcm0 not probed due to drq conflict with pcm1 at 1 fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): wd0: 6149MB (12594960 sectors), 13328 cyls, 15 heads, 63 S/T, 512 B/S wdc0: unit 1 (atapi): , removable, accel, dma, iordy acd0: drive speed 171 - 1367KB/sec, 128KB cache acd0: supported read types: CD-DA acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked wdc1 at 0x170-0x177 irq 15 on isa wdc1: unit 0 (atapi): , removable, dma, iordy wfd0: medium type unknown (no disk) ppc0 at 0x378 irq 7 on isa ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode nlpt0: on ppbus 0 nlpt0: Interrupt-driven port ppi0: on ppbus 0 plip0: on ppbus 0 vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa npx0 on motherboard npx0: INT 16 interface changing root device to wd0s1a ffs_mountfs: superblock updated for soft updates ffs_mountfs: superblock updated for soft updates ffs_mountfs: superblock updated for soft updates To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Mar 25 19:39:53 1999 Delivered-To: freebsd-stable@freebsd.org Received: from freebie.dcfinc.com (freebie.dcfinc.com [138.113.5.128]) by hub.freebsd.org (Postfix) with ESMTP id 81F77151E7 for ; Thu, 25 Mar 1999 19:39:47 -0800 (PST) (envelope-from chad@freebie.dcfinc.com) Received: (from chad@localhost) by freebie.dcfinc.com (8.8.7/8.8.3a) id UAA13216; Thu, 25 Mar 1999 20:38:56 -0700 (MST) From: "Chad R. Larson" Message-Id: <199903260338.UAA13216@freebie.dcfinc.com> Subject: Re: .sgml To: mwm@phone.net (Mike Meyer) Date: Thu, 25 Mar 1999 20:38:55 -0700 (MST) Cc: stable@freebsd.org In-Reply-To: from Mike Meyer at "Mar 25, 99 03:58:07 pm" Reply-To: chad@dcfinc.com X-unexpected: The Spanish Inquisition X-Mailer: ELM [version 2.4ME+ PL22 (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 > > And Extensible Markup Language (XML) seems to be where the world > > is headed. > > XML is another application of SGML; this one defining a subset of SGML > simplified enough to be grasped by the authors of the popular web > browsers (most of *still* can't properly parse an HTML 2.0 document). > Ok, that's the cynics few of XML. The official story is that it's got > all the parts of SGML that aren't used by most people taken out, so > that an XML parser can be written over the weekend, instead of being a > major project in and of itself. And don't forget the "Extensible" part. You get to define your own tags. We're using that commercially to define the interfaces to our systems for third party vendors. They no longer have to track our releases. If we add a feature, they can (while parsing) say, "I don't know what that is, but I sure know how to ignore it." -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org chad@anasazi.com 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 Thu Mar 25 20: 6:24 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mailhub1.anasazi.com (mailhub1.anasazi.com [138.113.128.8]) by hub.freebsd.org (Postfix) with ESMTP id E615414D2A for ; Thu, 25 Mar 1999 20:06:23 -0800 (PST) (envelope-from chad@anasazi.com) Received: from chad.anasazi.com (chad.anasazi.com [138.113.128.36]) by mailhub1.anasazi.com (8.9.1/8.9.1) with ESMTP id VAA17425 for ; Thu, 25 Mar 1999 21:06:03 -0700 (MST) (envelope-from chad@anasazi.com) Received: (from chad@localhost) by chad.anasazi.com (8.8.8/8.8.8) id VAA14834 for stable@FreeBSD.org; Thu, 25 Mar 1999 21:06:03 -0700 (MST) (envelope-from chad) From: "Chad R. Larson" Message-Id: <199903260406.VAA14834@chad.anasazi.com> Subject: what does stable mean? To: stable@FreeBSD.org Date: Thu, 25 Mar 1999 21:06:03 -0700 (MST) Reply-To: chad@rez.com X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just for grins... On the LAN segment where I live. chad> ruptime cerebus up 139+01:56, 0 users, load 0.01, 0.01, 0.01 chad up 5+05:38, 1 user, load 0.00, 0.00, 0.00 mailhost up 115+10:11, 0 users, load 0.28, 0.27, 0.27 mailhub1 up 20+18:05, 0 users, load 0.07, 0.02, 0.00 wbloom up 18+01:07, 2 users, load 0.51, 0.48, 0.39 Cerebus is a Radius database and DNS server. Mailhost and mailhub1 are SMTP gateways (and nameservers and some misc stuff like receiving syslog data from terminal servers). Wbloom and chad are personal desktops of SysAdm/developer folks. Any WinNT boxes doing =real= work that have been up for over four months? We had an OLTP system (a Pyramid running SysVr4) that ran for slightly over a year (370 days) processing a half million transactions a day (or so). It came down because we had to reboot it for an application software upgrade. Sorry about that. The Windoze folks have been particularly annoying today. -crl -- Chad R. Larson (CRL22) REZsolutions, Inc. 602-870-3330 chad@REZsolutions.com chad@anasazi.com chad@dcfinc.com 7500 North Dreamy Draw Drive, Suite 120, Phoenix, Az 85020 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Mar 25 22:22:18 1999 Delivered-To: freebsd-stable@freebsd.org Received: from guru.phone.net (guru.phone.net [209.157.82.120]) by hub.freebsd.org (Postfix) with SMTP id 85F5714E07 for ; Thu, 25 Mar 1999 22:22:17 -0800 (PST) (envelope-from mwm@phone.net) Received: (qmail 45845 invoked by uid 100); 26 Mar 1999 06:21:58 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 26 Mar 1999 06:21:58 -0000 Date: Thu, 25 Mar 1999 22:21:58 -0800 (PST) From: Mike Meyer To: stable@freebsd.org Subject: Re: .sgml In-Reply-To: <199903260338.UAA13216@freebie.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 Thu, 25 Mar 1999, Chad R. Larson wrote: > Date: Thu, 25 Mar 1999 20:38:55 -0700 (MST) > From: Chad R. Larson > Reply-To: chad@dcfinc.com > To: Mike Meyer > Cc: stable@freebsd.org > Subject: Re: .sgml > > > > And Extensible Markup Language (XML) seems to be where the world > > > is headed. > > > > XML is another application of SGML; this one defining a subset of SGML > > simplified enough to be grasped by the authors of the popular web > > browsers (most of *still* can't properly parse an HTML 2.0 document). > > Ok, that's the cynics few of XML. The official story is that it's got > > all the parts of SGML that aren't used by most people taken out, so > > that an XML parser can be written over the weekend, instead of being a > > major project in and of itself. > > And don't forget the "Extensible" part. You get to define your own > tags. We're using that commercially to define the interfaces to our > systems for third party vendors. They no longer have to track our > releases. If we add a feature, they can (while parsing) say, "I > don't know what that is, but I sure know how to ignore it." That's one it's a subset of SGML - it's an application that lets you add tags. Not the first one, but the one that's gotten the most press. In theory, you could add tags in HTML that would be safely ignored by other browsers. In practice, the people writing the popular browsers did a lousy job of defining tags that wouldn't cause problems if you ignored them. Hence was born attribute-based styling and CSS. ; Thu, 25 Mar 1999 22:24:51 -0800 (PST) (envelope-from mwm@phone.net) Received: (qmail 45867 invoked by uid 100); 26 Mar 1999 06:24:31 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 26 Mar 1999 06:24:31 -0000 Date: Thu, 25 Mar 1999 22:24:31 -0800 (PST) From: Mike Meyer To: stable@FreeBSD.org Subject: Re: what does stable mean?6 In-Reply-To: <199903260406.VAA14834@chad.anasazi.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 It's ok - just make sure to do the Losedos bashing in private, otherwise people will think you're a fanatic. On Thu, 25 Mar 1999, Chad R. Larson wrote: > Any WinNT boxes doing =real= work that have been up for over four > months? Hmm - there's a bug in Windows 95/98 that causes the system to freeze at 57 days. Maybe that's in NT? > We had an OLTP system (a Pyramid running SysVr4) that ran for > slightly over a year (370 days) processing a half million > transactions a day (or so). It came down because we had to reboot > it for an application software upgrade. My favorite story is the bug report4.X BSD) that "uptime" formatting was broken if you had been up for more than 999 days.... To: Mike Meyer Cc: chat@FreeBSD.ORG Subject: Re: what does stable mean?6 Message-ID: <19990326004328.A3156@holly.dyndns.org> Reply-To: chris@calldei.com References: <199903260406.VAA14834@chad.anasazi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4us In-Reply-To: ; from Mike Meyer on Thu, Mar 25, 1999 at 10:24:31PM -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Mar 26, 1999, Mike Meyer wrote: > It's ok - just make sure to do the Losedos bashing in private, > otherwise people will think you're a fanatic. > > On Thu, 25 Mar 1999, Chad R. Larson wrote: > > Any WinNT boxes doing =real= work that have been up for over four > > months? > > Hmm - there's a bug in Windows 95/98 that causes the system to freeze > at 57 days. Maybe that's in NT? It's not in NT, and it's 49 days. Replies set to freebsd-chat (if I get it right). > > > We had an OLTP system (a Pyramid running SysVr4) that ran for > > slightly over a year (370 days) processing a half million > > transactions a day (or so). It came down because we had to reboot > > it for an application software upgrade. > > My favorite story is the bug report4.X BSD) that "uptime" formatting > was broken if you had been up for more than 999 days.... > > -Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Mar 25 23:46:38 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 B863B150A2 for ; Thu, 25 Mar 1999 23:46:34 -0800 (PST) (envelope-from nik@nothing-going-on.demon.co.uk) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.8.8/8.8.8) id AAA16629; Fri, 26 Mar 1999 00:06:16 GMT (envelope-from nik) Date: Fri, 26 Mar 1999 00:06:16 +0000 From: Nik Clayton To: Wayne M Barnes Cc: freebsd-stable@freebsd.org Subject: Re: .sgml Message-ID: <19990326000616.A16436@catkin.nothing-going-on.org> References: <199903251714.RAA34177@klentaq1.emergingtech.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <199903251714.RAA34177@klentaq1.emergingtech.org>; from Wayne M Barnes on Thu, Mar 25, 1999 at 05:14:12PM +0000 Organization: Nik at home, where there's nothing going on Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Mar 25, 1999 at 05:14:12PM +0000, Wayne M Barnes wrote: > Say, what's a .sgml file, and what software reads them? http://www.freebsd.org/~nik/primer/index.html Should answer most of your questions. Should you get a hankering to put this knowledge to good use, come and join us over in the -doc mailing list. N -- Bagel: The carbohydrate with the hole To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Mar 25 23:52:51 1999 Delivered-To: freebsd-stable@freebsd.org Received: from csmd2.cs.uni-magdeburg.de (csmd2.CS.Uni-Magdeburg.De [141.44.22.2]) by hub.freebsd.org (Postfix) with ESMTP id C56DB15448 for ; Thu, 25 Mar 1999 23:52:49 -0800 (PST) (envelope-from jesse@mail.CS.Uni-Magdeburg.De) Received: from knecht.cs.uni-magdeburg.de (jesse@knecht [141.44.21.3]) by csmd2.cs.uni-magdeburg.de (8.9.1a/8.9.1) with ESMTP id IAA06087; Fri, 26 Mar 1999 08:52:28 +0100 (MET) Received: (from jesse@localhost) by knecht.cs.uni-magdeburg.de (8.8.8+Sun/8.8.8) id IAA01521; Fri, 26 Mar 1999 08:52:33 +0100 (MET) From: Roland Jesse MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14075.15553.579018.279728@cs.uni-magdeburg.de> Date: Fri, 26 Mar 1999 08:52:33 +0100 (MET) To: Patrick Seal Cc: freebsd-stable@FreeBSD.ORG Subject: Re: /usr/src/include/pthread/uthread/pthread.h not available? In-Reply-To: References: <14074.44498.157200.518328@cs.uni-magdeburg.de> X-Mailer: VM 6.70 under 20.4 "Emerald" XEmacs Lucid Reply-To: jesse@mail.CS.Uni-Magdeburg.De X-Pgp-Fingerprint: 5D 08 5A E3 B4 AA 68 C1 FF 67 06 29 62 DD 9A D7 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Patrick Seal writes: > This is freebsd, not linux, it has pthreads already Well, I know that. But you did take a look at http://lt.tar.com, didn't you? And just in case you do have the motivation, time, and disk space to do so, you might want to take a look at ACE (http://www.Pinyon.ORG/ace/) to get an idea about why I want to use the linux threads. So, is that a -current only issue? Roland To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Mar 26 0:42:32 1999 Delivered-To: freebsd-stable@freebsd.org Received: from iclub.nsu.ru (iclub.nsu.ru [193.124.222.66]) by hub.freebsd.org (Postfix) with ESMTP id 7DB5C14A14 for ; Fri, 26 Mar 1999 00:42:22 -0800 (PST) (envelope-from fjoe@iclub.nsu.ru) Received: from localhost (fjoe@localhost) by iclub.nsu.ru (8.9.2/8.8.5) with ESMTP id OAA50330 for ; Fri, 26 Mar 1999 14:41:20 +0600 (NS) Date: Fri, 26 Mar 1999 14:41:20 +0600 (NS) From: Max Khon To: stable@freebsd.org Subject: console lockups with xdm 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, there! 3.1-STABLE (cvsupped yesterday), XFree86 3.3.3.1 from 3.1-RELEASE, syscons with atkbdc, splash, ET6000, xdm started from /etc/ttys: try to switch consoles while xdm is loading (when booting) with Alt-Fx. After xdm is started Ctrl-Alt-Fx do not switch consoles anymore (beeps one time). AFAIR the problem existed even in 2.2.x with old kbd/vga driver. /fjoe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Mar 26 1:48:29 1999 Delivered-To: freebsd-stable@freebsd.org Received: from carmel.diva.nl (carmel.diva.nl [195.86.39.25]) by hub.freebsd.org (Postfix) with ESMTP id 649361512C for ; Fri, 26 Mar 1999 01:47:48 -0800 (PST) (envelope-from michiel@carmel.diva.nl) Received: from localhost (michiel@localhost) by carmel.diva.nl (8.9.3/8.9.3) with ESMTP id KAA24648; Fri, 26 Mar 1999 10:47:24 +0100 (CET) Date: Fri, 26 Mar 1999 10:47:24 +0100 (CET) From: Michiel Boland To: Mike Meyer Cc: stable@FreeBSD.ORG Subject: Re: what does stable mean?6 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hmm - there's a bug in Windows 95/98 that causes the system to freeze > at 57 days. Maybe that's in NT? No, there was another problem that limited the uptime of NT boxes. See KB article Q169847. (SNMP SysUpTime Counter Resets After 49.7 Days.) Cheers Michiel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Mar 26 5: 5: 8 1999 Delivered-To: freebsd-stable@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 6834A14F7F for ; Fri, 26 Mar 1999 05:04:44 -0800 (PST) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 26 Mar 99 13:04:25 +0000 (GMT) To: freebsd-stable@freebsd.org Subject: Re: Netscape Looping In-reply-to: Your message of "Thu, 25 Mar 1999 10:01:58 PST." <199903251801.KAA21362@passer.osg.gov.bc.ca> X-Request-Do: Date: Fri, 26 Mar 1999 13:04:24 +0000 From: David Malone Message-ID: <9903261304.aa10667@salmon.maths.tcd.ie> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I see netscape freezes at home all the time, but never with the machines in college. I do now have a rather weird workaround at home, where I run ico (you know that x program which bounces an icosahedron around the screen) before running netscape, netscape then takes a while to start 'cos the screen is so busy, and then kill it once the netscape window pops up! A bit icky - but it works all the time. Without it netscape never starts. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Mar 26 5:53:43 1999 Delivered-To: freebsd-stable@freebsd.org Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1]) by hub.freebsd.org (Postfix) with ESMTP id CC88D14F65 for ; Fri, 26 Mar 1999 05:53:38 -0800 (PST) (envelope-from jfieber@fallout.campusview.indiana.edu) Received: from localhost (jfieber@localhost) by fallout.campusview.indiana.edu (8.9.2/8.9.1) with ESMTP id IAA72470; Fri, 26 Mar 1999 08:53:13 -0500 (EST) Date: Fri, 26 Mar 1999 08:53:13 -0500 (EST) From: John Fieber To: Mike Meyer Cc: freebsd-stable@FreeBSD.ORG Subject: Re: .sgml 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, 25 Mar 1999, Mike Meyer wrote: > XML is another application of SGML; XML is a subset, but definately not an application. An application is a markup language defined in terms of SGML or XML. Calling XML an application puts it in the same box as HTML or Linuxdoc or Docbook. SGML and XML are both metalanguages sitting together in a completely different box. In standards jargon, XML could be called a "profile" of SGML. -john To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Mar 26 6: 4:54 1999 Delivered-To: freebsd-stable@freebsd.org Received: from freed.libdns.qc.ca (derby.JSP.UMontreal.CA [132.204.45.26]) by hub.freebsd.org (Postfix) with ESMTP id 33B0915174 for ; Fri, 26 Mar 1999 06:04:40 -0800 (PST) (envelope-from spidey@libdns.qc.ca) Received: from localhost (spidey@localhost) by freed.libdns.qc.ca (8.9.2/8.9.2) with SMTP id JAA27175; Fri, 26 Mar 1999 09:03:53 -0500 (EST) (envelope-from spidey@libdns.qc.ca) X-Authentication-Warning: freed.libdns.qc.ca: spidey owned process doing -bs Date: Fri, 26 Mar 1999 09:03:53 -0500 (EST) From: Spidey Reply-To: Spidey To: Mike Meyer Cc: stable@FreeBSD.ORG Subject: Re: what does stable mean?6 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 Sorry, that's 49,7 of improbable Windows survival... ;) On Thu, 25 Mar 1999, Mike Meyer wrote: > It's ok - just make sure to do the Losedos bashing in private, > otherwise people will think you're a fanatic. > > On Thu, 25 Mar 1999, Chad R. Larson wrote: > > Any WinNT boxes doing =real= work that have been up for over four > > months? > > Hmm - there's a bug in Windows 95/98 that causes the system to freeze > at 57 days. Maybe that's in NT? > > > We had an OLTP system (a Pyramid running SysVr4) that ran for > > slightly over a year (370 days) processing a half million > > transactions a day (or so). It came down because we had to reboot > > it for an application software upgrade. > > My favorite story is the bug report4.X BSD) that "uptime" formatting > was broken if you had been up for more than 999 days.... > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > When a man lies he murders some part of the world These are the pale deaths which men miscall their lives All this I can witness any longer Cannot the kingdom of salvation take me home To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Mar 26 6:43:43 1999 Delivered-To: freebsd-stable@freebsd.org Received: from angel.double-barrel.be (mail.double-barrel.be [194.7.102.20]) by hub.freebsd.org (Postfix) with ESMTP id 34DC8150B0 for ; Fri, 26 Mar 1999 06:43:31 -0800 (PST) (envelope-from mvergall@ns.double-barrel.be) Received: from ns.double-barrel.be (ns.double-barrel.be [194.7.102.18]) by angel.double-barrel.be (8.9.1b+Sun/8.9.1) with ESMTP id PAA02497; Fri, 26 Mar 1999 15:42:33 +0100 (MET) Received: from localhost (mvergall@localhost) by ns.double-barrel.be (8.8.7/8.8.7) with ESMTP id PAA04659; Fri, 26 Mar 1999 15:42:29 +0100 Date: Fri, 26 Mar 1999 15:42:29 +0100 (CET) From: "Michael C. Vergallen" To: David Malone Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Netscape Looping In-Reply-To: <9903261304.aa10667@salmon.maths.tcd.ie> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 26 Mar 1999, David Malone wrote: > I see netscape freezes at home all the time, but never with the machines > in college. I do now have a rather weird workaround at home, where I run > ico (you know that x program which bounces an icosahedron around the screen) > before running netscape, netscape then takes a while to start 'cos the screen > is so busy, and then kill it once the netscape window pops up! what the hell ... me think you crazy but... > A bit icky - but it works all the time. Without it netscape never starts. Do you use the static version for linux with the linux module loaded ? because even on my 486 it works fine aldo slowly at loadtime becuase the box only has 32Mb of RAM. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Mar 26 6:49:34 1999 Delivered-To: freebsd-stable@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 091BE14DD3 for ; Fri, 26 Mar 1999 06:49:30 -0800 (PST) (envelope-from dwmalone@maths.tcd.ie) Received: from gosset.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 26 Mar 99 14:49:11 +0000 (GMT) To: "Michael C. Vergallen" Cc: freebsd-stable@freebsd.org Subject: Re: Netscape Looping In-reply-to: Your message of "Fri, 26 Mar 1999 15:42:29 +0100." X-Request-Do: Date: Fri, 26 Mar 1999 14:49:11 +0000 From: David Malone Message-ID: <9903261449.aa20738@salmon.maths.tcd.ie> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > what the hell ... me think you crazy but... ;-) You can basically do anything that loads the xserver I think. I originally noticed when I was running kdump on a huge ktrace file in an xterm while trying to figure out what was going on. The busy xterm made it work too. ico is just a nicer way of doing it (and it's in my tvtwm menues ;-) > > A bit icky - but it works all the time. Without it netscape never starts. > > Do you use the static version for linux with the linux module loaded ? > because even on my 486 it works fine aldo slowly at loadtime becuase the > box only has 32Mb of RAM. I've been using the FreeBSD version, and I think I've had similar trouble since version 3. Definitely I've had trouble with all the version 4 netscapes. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Mar 26 6:50:56 1999 Delivered-To: freebsd-stable@freebsd.org Received: from Gog.studioarchetype.com (Gog.studioarchetype.com [204.162.75.26]) by hub.freebsd.org (Postfix) with ESMTP id C42B315548 for ; Fri, 26 Mar 1999 06:50:55 -0800 (PST) (envelope-from blanders@studioarchetype.com) Received: from mis4100 (atl-bh-ext.studioarchetype.com [208.226.114.2]) by Gog.studioarchetype.com (post.office MTA v2.0 0813 ID# 0-12986) with SMTP id AAA18006 for ; Fri, 26 Mar 1999 06:59:33 -0800 From: blanders@studioarchetype.com (Brian Landers) To: Subject: Problems building 3.1-stable Date: Fri, 26 Mar 1999 09:50:34 -0500 Message-ID: <000001be7798$00a26690$1d03d50a@studioarchetype.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 In-Reply-To: <9903261304.aa10667@salmon.maths.tcd.ie> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm currently unable to build 3.1-stable. My system: Compaq Prosignia 720, P2/400, 128MB, 9.1GB, 3.1-RELEASE I used CVSup yesterday evening to get the 3.1-stable source tree, followed the instructions in the tutorial, then ran 'make buildworld' from /usr/src. It runs for a while, then dies with a bunch of "Error code 1" and "Error code 2" messages while building Perl (I think). Looking through the build logs shows several instances of "Makefile out of date with respect to foo". I also see the messages below: Writing Makefile for foo ==> Your Makefile has been rebuilt. <== ==> Please rerun the make command. <== false false: not found Can anyone help with this? I have long experience with Linux, but almost none with FreeBSD so I'm a bit of a newbie I suppose. Thanks in advance, Brian Landers ====================================================================== Brian Landers, MCP S T U D I O A R C H E T Y P E Systems Exorcist Atlanta New York San Francisco blanders@studioarchetype.com http://www.studioarchetype.com For PGP public key, use finger or just ask ====================================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Mar 26 7:54: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 C2DCB150BB for ; Fri, 26 Mar 1999 07:54:12 -0800 (PST) (envelope-from cy@cschuber.net.gov.bc.ca) Received: (from daemon@localhost) by point.osg.gov.bc.ca (8.9.1/8.8.8) id HAA06807; Fri, 26 Mar 1999 07:53:52 -0800 Received: from cschuber.net.gov.bc.ca(142.31.240.113), claiming to be "cwsys.cwsent.com" via SMTP by point.osg.gov.bc.ca, id smtpda06805; Fri Mar 26 07:53:44 1999 Received: (from uucp@localhost) by cwsys.cwsent.com (8.9.3/8.9.1) id HAA32102; Fri, 26 Mar 1999 07:53:36 -0800 (PST) Message-Id: <199903261553.HAA32102@cwsys.cwsent.com> Received: from localhost.cwsent.com(127.0.0.1), claiming to be "cwsys" via SMTP by localhost.cwsent.com, id smtpdG32098; Fri Mar 26 07:53:33 1999 X-Mailer: exmh version 2.0.2 2/24/98 Reply-To: Cy Schubert - ITSD Open Systems Group From: Cy Schubert - ITSD Open Systems Group X-OS: FreeBSD 2.2.8-RELEASE X-Sender: cy To: "Michael C. Vergallen" Cc: David Malone , freebsd-stable@FreeBSD.ORG Subject: Re: Netscape Looping In-reply-to: Your message of "Fri, 26 Mar 1999 15:42:29 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 26 Mar 1999 07:53:33 -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , "Mich ael C. Vergallen" writes: > On Fri, 26 Mar 1999, David Malone wrote: > > > I see netscape freezes at home all the time, but never with the machines > > in college. I do now have a rather weird workaround at home, where I run > > ico (you know that x program which bounces an icosahedron around the screen > ) > > before running netscape, netscape then takes a while to start 'cos the scre > en > > is so busy, and then kill it once the netscape window pops up! > what the hell ... me think you crazy but... > > > A bit icky - but it works all the time. Without it netscape never starts. > > Do you use the static version for linux with the linux module loaded ? > because even on my 486 it works fine aldo slowly at loadtime becuase the > box only has 32Mb of RAM. I just replaced the "unsupported" FreeBSD version with a "supported" Linux version. It works like a charm on all machines under every circumstance. I'm not sure whether it's me or not but the only differences I can see are that the fonts look a little different and the spacing of the buttons in the button bar is a little wider. These didn't take long to get used to, especially now that it works consistently. Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 Open Systems Group Internet: Cy.Schubert@uumail.gov.bc.ca ITSD Cy.Schubert@gems8.gov.bc.ca Province of BC To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Mar 26 8:45:25 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 BF53014CC2 for ; Fri, 26 Mar 1999 08:45:22 -0800 (PST) (envelope-from wheelman@nuc.net) Received: from electron (dhcp1.ecofl.com [204.49.61.49]) by lepton.nuc.net (8.8.8/8.8.8) with SMTP id KAA14787; Fri, 26 Mar 1999 10:43:41 -0600 (CST) (envelope-from wheelman@nuc.net) From: "Jaime Bozza" To: "Max Khon" Cc: Subject: RE: PAM and Apache Date: Fri, 26 Mar 1999 10:41:57 -0600 Message-ID: <001301be77a7$904c0ee0$313d31cc@nuc.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211 In-reply-to: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > as far as i understand they should be defined in PAM modules. > at this time FreeBSD PAM modules implement only pam_sm_setcred and > pam_sm_authenticate functions Ok... I got that part working. :) But it still seems to not want to validate a password. Is PAM subject to the same issues with getpwnam()? (Unless your effective uid is 0, it returns '*' for a password) Jaime Bozza Nucleus Communications To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Mar 26 10: 6:31 1999 Delivered-To: freebsd-stable@freebsd.org Received: from citadel.evolving.com (citadel.evolving.com [198.202.204.162]) by hub.freebsd.org (Postfix) with ESMTP id AD2C9155C7 for ; Fri, 26 Mar 1999 10:06:25 -0800 (PST) (envelope-from Deborah.Hooker@evolving.com) Received: from valiant.evolving.com (valiant.evolving.com [198.202.204.66]) by citadel.evolving.com (8.9.1/8.6.9) with ESMTP id LAA26017 for ; Fri, 26 Mar 1999 11:06:03 -0700 (MST) Received: from sappho.evolving.com (sappho [199.182.250.6]) by valiant.evolving.com (8.9.1/8.6.9) with ESMTP id LAA08645 for ; Fri, 26 Mar 1999 11:05:56 -0700 (MST) Received: (from deb@localhost) by sappho.evolving.com (8.6.12/8.6.9) id LAA16210; Fri, 26 Mar 1999 11:05:54 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Fri, 26 Mar 1999 11:05:53 -0700 (MST) From: Deborah Hooker To: freebsd-stable@freebsd.org Subject: Just a note... X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14075.52088.162842.900964@sappho.evolving.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just for reference... A couple of days ago I dug my FreeBSD box out of the moving stuff (it's been sort of mothballed since we moved last November and I started needing it again and actually had time to rebuild it). At the time I mothballed it, I was tracking RELENG_2_2. Last cvsup and build had been Oct 29, 1998. My kernel was indicating 2.2.7, just for reference. I cvsupped RELENG_3, did a make upgrade. Had one little problem in the install (/usr/share/examples/ppp didn't get created, so the install into that directory failed). Simple tweak to fix. When the machine rebooted I still had a few weird problems, so I did a fresh make buildworld, make installworld cycle, and my machine is now up and running on 3.1-STABLE with new bootblocks, an elf kernel and an elf world. And reasonably happy, even. Most of my /usr/local is still broken, but I'll get there. (I need to actually install the compat22 stuff until I get all the ports I use rebuilt, working on that. cvsupped ports-all this morning.) I'm impressed. It was a remarkably easy upgrade. Thanks, guys. :) -Deb -- I'm a bitch, I'm a tease, I'm a goddess on my knees... | deb@pobox.com ____ "For extra fun, pop eyeball out of eye socket!" _______| DoD#0034 __\_ / May your soul be celebrating in Valhalla before | Big Wet Sleepy Eyes \ // the Christian God notices that you're dead. | Of A Tree Nymph \/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Mar 26 10:36:10 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mailbox.hunter.com (mailbox.hunter.com [199.217.245.230]) by hub.freebsd.org (Postfix) with ESMTP id E952614C37 for ; Fri, 26 Mar 1999 10:36:08 -0800 (PST) (envelope-from KHamilton@Hunter.COM) Received: by mailbox.Hunter.COM with Internet Mail Service (5.5.2448.0) id ; Fri, 26 Mar 1999 12:35:46 -0600 Message-ID: <2105C00EC6FED11183F300A0C9C83B446BE554@mailbox.Hunter.COM> From: "Hamilton, Kent" To: stable@FreeBSD.ORG Subject: UCD SNMP on 3.1-STABLE Date: Fri, 26 Mar 1999 12:35:44 -0600 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is anyone other than me having huge problems with snmpd on 3.1-STABLE? I've tried installing the package version, I've tried the ports version and I'm having the same problem with both. Oh, and I've tried it on 3 different STABLE systems with the same results. Here's the excerpt from the log files. 1999-03-26 12:23:39 UCD-SNMP version 3.5.3 snmpd: /usr/local/share/snmp/snmpd.local.conf: No such file or directory snmpd: /usr/local/lib/snmp/snmpd.conf: No such file or directory snmpd: /usr/local/lib/snmp/snmpd.local.conf: No such file or directory Opening port(s): 161 ... mgmt.interfaces query comes in. I've deleted the info for that from here. then we get to this point and: var_ip: ip.ipNetToMediaTable.ipNetToMediaEntry.ipNetToMediaType.1.10.2.1.1 kvm_read(*, 3c7, 0xefbfb7f8, 96) = 0: kvm_read: Bad address TCP_Count_Connections - inpcb: Bad address kvm_read(*, 1bddb3, 0xefbfb73c, 188) = 0: kvm_read: Bad address TCP_Count_Connections - tcpcb: Bad address kvm_read(*, 3c7, 0x80654f0, 96) = 0: kvm_read: Bad address kvm_read(*, 1bddb3, 0xefbfb3f4, 188) = 0: kvm_read: Bad address kvm_read(*, 3c7, 0x80654f0, 96) = 0: kvm_read: Bad address kvm_read(*, 1bddb3, 0xefbfb3f4, 188) = 0: kvm_read: Bad address kvm_read(*, 3c7, 0x80654f0, 96) = 0: kvm_read: Bad address kvm_read(*, 1bddb3, 0xefbfb3f4, 188) = 0: kvm_read: Bad address kvm_read(*, 3c7, 0x80654f0, 96) = 0: kvm_read: Bad address kvm_read(*, 1bddb3, 0xefbfb3f4, 188) = 0: kvm_read: Bad address kvm_read(*, 3c7, 0x80654f0, 96) = 0: kvm_read: Bad address kvm_read(*, 1bddb3, 0xefbfb3f4, 188) = 0: kvm_read: Bad address kvm_read(*, 3c7, 0x80654f0, 96) = 0: kvm_read: Bad address kvm_read(*, 1bddb3, 0xefbfb3f4, 188) = 0: kvm_read: Bad address kvm_read(*, 3c7, 0x80654f0, 96) = 0: kvm_read: Bad address kvm_read(*, 1bddb3, 0xefbfb3f4, 188) = 0: kvm_read: Bad address This went on for about 5 minutes and 12MB of log file so..... Any help would be appreciated. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Mar 26 10:47: 3 1999 Delivered-To: freebsd-stable@freebsd.org Received: from angel.double-barrel.be (mail.double-barrel.be [194.7.102.20]) by hub.freebsd.org (Postfix) with ESMTP id 5ECAF155DD for ; Fri, 26 Mar 1999 10:46:49 -0800 (PST) (envelope-from mvergall@ns.double-barrel.be) Received: from ns.double-barrel.be (ns.double-barrel.be [194.7.102.18]) by angel.double-barrel.be (8.9.1b+Sun/8.9.1) with ESMTP id TAA02628; Fri, 26 Mar 1999 19:45:18 +0100 (MET) Received: from localhost (mvergall@localhost) by ns.double-barrel.be (8.8.7/8.8.7) with ESMTP id TAA04735; Fri, 26 Mar 1999 19:45:15 +0100 Date: Fri, 26 Mar 1999 19:45:15 +0100 (CET) From: "Michael C. Vergallen" To: "Hamilton, Kent" Cc: stable@FreeBSD.ORG Subject: Re: UCD SNMP on 3.1-STABLE In-Reply-To: <2105C00EC6FED11183F300A0C9C83B446BE554@mailbox.Hunter.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 did you see those config files are installed ? you may need to create those files from the samples provided. Michael --- Michael C. Vergallen A.k.A. Mad Mike, Sportstraat 28 http://www.double-barrel.be/mvergall/ B 9000 Gent ftp://ftp.double-barrel.be/pub/linux/ Belgium tel : 32-9-2227764 Fax : 32-9-2224976 On Fri, 26 Mar 1999, Hamilton, Kent wrote: > Is anyone other than me having huge problems with snmpd on 3.1-STABLE? > > I've tried installing the package version, I've tried the ports version and > I'm having the same problem with both. Oh, and I've tried it on 3 different > STABLE systems with the same results. > > Here's the excerpt from the log files. > > 1999-03-26 12:23:39 UCD-SNMP version 3.5.3 > snmpd: /usr/local/share/snmp/snmpd.local.conf: No such file or directory > snmpd: /usr/local/lib/snmp/snmpd.conf: No such file or directory > snmpd: /usr/local/lib/snmp/snmpd.local.conf: No such file or directory > Opening port(s): 161 > > ... mgmt.interfaces query comes in. I've deleted the info for that from > here. > then we get to this point and: > > var_ip: ip.ipNetToMediaTable.ipNetToMediaEntry.ipNetToMediaType.1.10.2.1.1 > kvm_read(*, 3c7, 0xefbfb7f8, 96) = 0: kvm_read: Bad address > TCP_Count_Connections - inpcb: Bad address > kvm_read(*, 1bddb3, 0xefbfb73c, 188) = 0: kvm_read: Bad address > TCP_Count_Connections - tcpcb: Bad address > kvm_read(*, 3c7, 0x80654f0, 96) = 0: kvm_read: Bad address > kvm_read(*, 1bddb3, 0xefbfb3f4, 188) = 0: kvm_read: Bad address > kvm_read(*, 3c7, 0x80654f0, 96) = 0: kvm_read: Bad address > kvm_read(*, 1bddb3, 0xefbfb3f4, 188) = 0: kvm_read: Bad address > kvm_read(*, 3c7, 0x80654f0, 96) = 0: kvm_read: Bad address > kvm_read(*, 1bddb3, 0xefbfb3f4, 188) = 0: kvm_read: Bad address > kvm_read(*, 3c7, 0x80654f0, 96) = 0: kvm_read: Bad address > kvm_read(*, 1bddb3, 0xefbfb3f4, 188) = 0: kvm_read: Bad address > kvm_read(*, 3c7, 0x80654f0, 96) = 0: kvm_read: Bad address > kvm_read(*, 1bddb3, 0xefbfb3f4, 188) = 0: kvm_read: Bad address > kvm_read(*, 3c7, 0x80654f0, 96) = 0: kvm_read: Bad address > kvm_read(*, 1bddb3, 0xefbfb3f4, 188) = 0: kvm_read: Bad address > kvm_read(*, 3c7, 0x80654f0, 96) = 0: kvm_read: Bad address > kvm_read(*, 1bddb3, 0xefbfb3f4, 188) = 0: kvm_read: Bad address > > This went on for about 5 minutes and 12MB of log file so..... > > Any help would be appreciated. > > > 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 Mar 26 10:59:33 1999 Delivered-To: freebsd-stable@freebsd.org Received: from granite.sentex.net (granite.sentex.ca [199.212.134.1]) by hub.freebsd.org (Postfix) with ESMTP id 74AE215082 for ; Fri, 26 Mar 1999 10:59:23 -0800 (PST) (envelope-from mike@sentex.net) Received: from leaverite (leaverite.sentex.ca [209.112.4.36]) by granite.sentex.net (8.8.8/8.6.9) with SMTP id NAA05267; Fri, 26 Mar 1999 13:58:51 -0500 (EST) Message-Id: <3.0.5.32.19990326140302.048dbea0@staff.sentex.ca> X-Sender: mdtpop@staff.sentex.ca X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Fri, 26 Mar 1999 14:03:02 -0500 To: KHamilton@Hunter.COM From: Mike Tancsa Subject: Re: UCD SNMP on 3.1-STABLE Cc: stable@FreeBSD.ORG In-Reply-To: References: <2105C00EC6FED11183F300A0C9C83B446BE554@mailbox.Hunter.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 07:45 PM 3/26/99 +0100, Michael C. Vergallen wrote: >did you see those config files are installed ? >you may need to create those files from the samples provided. It will still barf with the .conf files installed. There was a patch that someone was kind enough to post along with a PR for this. I dont have the orignial author's name handy (see the PR filing for it), but I do have his/her patch that seems to fix the problem. ---Mike ----------------------------------- *** agent/mibgroup/mibII/tcp.c.orig Mon Nov 30 20:00:46 1998 --- agent/mibgroup/mibII/tcp.c Mon Nov 30 20:04:04 1998 *************** *** 818,823 **** --- 818,824 ---- if((klookup((unsigned long)next, (char *)&inpcb, sizeof (inpcb)) == 0)) { perror("TCP_Count_Connections - inpcb"); + break; } #if !(defined(freebsd2) || defined(netbsd1) || defined(openbsd2)) if (inpcb.INP_PREV_SYMBOL != prev) { /* ??? */ *************** *** 951,962 **** next = tcp_inpcb.INP_NEXT_SYMBOL; ! klookup((unsigned long)next, (char *)&tcp_inpcb, sizeof (tcp_inpcb)); #if !(defined(netbsd1) || defined(freebsd2)) || defined(openbsd2) if (tcp_inpcb.INP_PREV_SYMBOL != tcp_prev) /* ??? */ return(-1); /* "FAILURE" */ #endif /* !(defined(netbsd1) || defined(freebsd2) || defined(openbsd2)) */ ! klookup ( (int)tcp_inpcb.inp_ppcb, (char *)&tcpcb, sizeof (tcpcb)); *State = tcpcb.t_state; #else /* linux */ if (! tcp_prev) --- 952,965 ---- next = tcp_inpcb.INP_NEXT_SYMBOL; ! if (!klookup((unsigned long)next,(char *)&tcp_inpcb,sizeof(tcp_inpcb))) ! return 0; #if !(defined(netbsd1) || defined(freebsd2)) || defined(openbsd2) if (tcp_inpcb.INP_PREV_SYMBOL != tcp_prev) /* ??? */ return(-1); /* "FAILURE" */ #endif /* !(defined(netbsd1) || defined(freebsd2) || defined(openbsd2)) */ ! if (!klookup((int)tcp_inpcb.inp_ppcb, (char *)&tcpcb, sizeof (tcpcb))) ! return 0; *State = tcpcb.t_state; #else /* linux */ if (! tcp_prev) ------------------------------------------------------ >Michael >--- >Michael C. Vergallen A.k.A. Mad Mike, >Sportstraat 28 http://www.double-barrel.be/mvergall/ >B 9000 Gent ftp://ftp.double-barrel.be/pub/linux/ >Belgium tel : 32-9-2227764 Fax : 32-9-2224976 > >On Fri, 26 Mar 1999, Hamilton, Kent wrote: > >> Is anyone other than me having huge problems with snmpd on 3.1-STABLE? >> >> I've tried installing the package version, I've tried the ports version and >> I'm having the same problem with both. Oh, and I've tried it on 3 different >> STABLE systems with the same results. >> >> Here's the excerpt from the log files. >> >> 1999-03-26 12:23:39 UCD-SNMP version 3.5.3 >> snmpd: /usr/local/share/snmp/snmpd.local.conf: No such file or directory >> snmpd: /usr/local/lib/snmp/snmpd.conf: No such file or directory >> snmpd: /usr/local/lib/snmp/snmpd.local.conf: No such file or directory >> Opening port(s): 161 >> >> ... mgmt.interfaces query comes in. I've deleted the info for that from >> here. >> then we get to this point and: >> >> var_ip: ip.ipNetToMediaTable.ipNetToMediaEntry.ipNetToMediaType.1.10.2.1.1 >> kvm_read(*, 3c7, 0xefbfb7f8, 96) = 0: kvm_read: Bad address >> TCP_Count_Connections - inpcb: Bad address >> kvm_read(*, 1bddb3, 0xefbfb73c, 188) = 0: kvm_read: Bad address >> TCP_Count_Connections - tcpcb: Bad address >> kvm_read(*, 3c7, 0x80654f0, 96) = 0: kvm_read: Bad address >> kvm_read(*, 1bddb3, 0xefbfb3f4, 188) = 0: kvm_read: Bad address >> kvm_read(*, 3c7, 0x80654f0, 96) = 0: kvm_read: Bad address >> kvm_read(*, 1bddb3, 0xefbfb3f4, 188) = 0: kvm_read: Bad address >> kvm_read(*, 3c7, 0x80654f0, 96) = 0: kvm_read: Bad address >> kvm_read(*, 1bddb3, 0xefbfb3f4, 188) = 0: kvm_read: Bad address >> kvm_read(*, 3c7, 0x80654f0, 96) = 0: kvm_read: Bad address >> kvm_read(*, 1bddb3, 0xefbfb3f4, 188) = 0: kvm_read: Bad address >> kvm_read(*, 3c7, 0x80654f0, 96) = 0: kvm_read: Bad address >> kvm_read(*, 1bddb3, 0xefbfb3f4, 188) = 0: kvm_read: Bad address >> kvm_read(*, 3c7, 0x80654f0, 96) = 0: kvm_read: Bad address >> kvm_read(*, 1bddb3, 0xefbfb3f4, 188) = 0: kvm_read: Bad address >> kvm_read(*, 3c7, 0x80654f0, 96) = 0: kvm_read: Bad address >> kvm_read(*, 1bddb3, 0xefbfb3f4, 188) = 0: kvm_read: Bad address >> >> This went on for about 5 minutes and 12MB of log file so..... >> >> Any help would be appreciated. >> >> >> 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 > > ------------------------------------------------------------------------ Mike Tancsa, tel 01.519.651.3400 Network Administrator, mike@sentex.net Sentex Communications www.sentex.net Cambridge, Ontario Canada To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Mar 26 11: 0:33 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mailbox.hunter.com (mailbox.hunter.com [199.217.245.230]) by hub.freebsd.org (Postfix) with ESMTP id E84441500E for ; Fri, 26 Mar 1999 11:00:31 -0800 (PST) (envelope-from KHamilton@Hunter.COM) Received: by mailbox.Hunter.COM with Internet Mail Service (5.5.2448.0) id ; Fri, 26 Mar 1999 13:00:06 -0600 Message-ID: <2105C00EC6FED11183F300A0C9C83B446BE555@mailbox.Hunter.COM> From: "Hamilton, Kent" To: "'Michael C. Vergallen'" Cc: stable@FreeBSD.ORG Subject: RE: UCD SNMP on 3.1-STABLE Date: Fri, 26 Mar 1999 13:00:05 -0600 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a *really* basic config file installed. It's pretty much com2sec public default public com2sec private default removed-for-privacy group public any public group private any private view all included .1 80 access public "" any noauth 0 all none none access private "" any noauth 0 all all none syscontact System Administrators syslocation Eng. Dept. / Hunter Eng. Co. / 11250 Hunter Drive / Bridgeton, MO US 63044 / LatLong: 38.745141 -90.391653 authtrapenable 1 trapsink 10.2.6.17 trapcommunity removed-for-privacy > -----Original Message----- > From: Michael C. Vergallen [mailto:mvergall@mail.double-barrel.be] > Sent: Friday, March 26, 1999 12:45 PM > To: Hamilton, Kent > Cc: stable@FreeBSD.ORG > Subject: Re: UCD SNMP on 3.1-STABLE > > > did you see those config files are installed ? > you may need to create those files from the samples provided. > > Michael > --- > Michael C. Vergallen A.k.A. Mad Mike, > Sportstraat 28 > http://www.double-barrel.be/mvergall/ > B 9000 Gent ftp://ftp.double-barrel.be/pub/linux/ > Belgium tel : 32-9-2227764 Fax > : 32-9-2224976 > > On Fri, 26 Mar 1999, Hamilton, Kent wrote: > > > Is anyone other than me having huge problems with snmpd on > 3.1-STABLE? > > > > I've tried installing the package version, I've tried the > ports version and > > I'm having the same problem with both. Oh, and I've tried > it on 3 different > > STABLE systems with the same results. > > > > Here's the excerpt from the log files. > > > > 1999-03-26 12:23:39 UCD-SNMP version 3.5.3 > > snmpd: /usr/local/share/snmp/snmpd.local.conf: No such file > or directory > > snmpd: /usr/local/lib/snmp/snmpd.conf: No such file or directory > > snmpd: /usr/local/lib/snmp/snmpd.local.conf: No such file > or directory > > Opening port(s): 161 > > > > ... mgmt.interfaces query comes in. I've deleted the info > for that from > > here. > > then we get to this point and: > > > > var_ip: > ip.ipNetToMediaTable.ipNetToMediaEntry.ipNetToMediaType.1.10.2.1.1 > > kvm_read(*, 3c7, 0xefbfb7f8, 96) = 0: kvm_read: Bad address > > TCP_Count_Connections - inpcb: Bad address > > kvm_read(*, 1bddb3, 0xefbfb73c, 188) = 0: kvm_read: Bad address > > TCP_Count_Connections - tcpcb: Bad address > > kvm_read(*, 3c7, 0x80654f0, 96) = 0: kvm_read: Bad address > > kvm_read(*, 1bddb3, 0xefbfb3f4, 188) = 0: kvm_read: Bad address > > kvm_read(*, 3c7, 0x80654f0, 96) = 0: kvm_read: Bad address > > kvm_read(*, 1bddb3, 0xefbfb3f4, 188) = 0: kvm_read: Bad address > > kvm_read(*, 3c7, 0x80654f0, 96) = 0: kvm_read: Bad address > > kvm_read(*, 1bddb3, 0xefbfb3f4, 188) = 0: kvm_read: Bad address > > kvm_read(*, 3c7, 0x80654f0, 96) = 0: kvm_read: Bad address > > kvm_read(*, 1bddb3, 0xefbfb3f4, 188) = 0: kvm_read: Bad address > > kvm_read(*, 3c7, 0x80654f0, 96) = 0: kvm_read: Bad address > > kvm_read(*, 1bddb3, 0xefbfb3f4, 188) = 0: kvm_read: Bad address > > kvm_read(*, 3c7, 0x80654f0, 96) = 0: kvm_read: Bad address > > kvm_read(*, 1bddb3, 0xefbfb3f4, 188) = 0: kvm_read: Bad address > > kvm_read(*, 3c7, 0x80654f0, 96) = 0: kvm_read: Bad address > > kvm_read(*, 1bddb3, 0xefbfb3f4, 188) = 0: kvm_read: Bad address > > > > This went on for about 5 minutes and 12MB of log file so..... > > > > Any help would be appreciated. > > > > > > 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 Mar 26 12: 3:33 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mailgate.program-products.co.uk (samson.program-products.co.uk [212.240.242.226]) by hub.freebsd.org (Postfix) with ESMTP id 351AE1505A for ; Fri, 26 Mar 1999 12:03:25 -0800 (PST) (envelope-from terry@program-products.co.uk) Received: by mailgate.program-products.co.uk via smap (V2.1) id xma008693; Fri, 26 Mar 99 20:02:36 GMT Date: Fri, 26 Mar 99 20:02:34 GMT Message-Id: <9903262002.AA15201@program-products.co.uk> From: Terry Glanfield To: freebsd-stable@freebsd.org Subject: FIN not send on socket close() Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I'm having trouble getting an FTP proxy working on 3.1-STABLE (~1 week old). The proxy is a PASV aware version of the FTWK ftp-gw. When trying to STOR a file through the proxy the receiving end hangs waiting for a FIN packet that is never sent. The ktrace output below shows the socket being closed. I've also included some short packet traces - sorry about the line length - and dumps of a pftp session for comparison. The only difference I can see is that the proxy is being launched from inetd. Any help would be greatly appreciated. Cheers, Terry. Fristly the traces from the proxy version. Receiver: 6952 ftpd CALL read(0x8,0xefbfcfbc,0x400) 6952 ftpd GIO fd 8 read 5 bytes "test " 6952 ftpd RET read 5 6952 ftpd CALL write(0x7,0xefbfcfbc,0x5) 6952 ftpd GIO fd 7 wrote 5 bytes "test " 6952 ftpd RET write 5 6952 ftpd CALL read(0x8,0xefbfcfbc,0x400) >>read never returns... Sender: 8543 ftp-gw CALL read(0x8,0xefbfce5c,0x800) 8543 ftp-gw GIO fd 8 read 5 bytes "test " 8543 ftp-gw RET read 5 8543 ftp-gw CALL write(0x7,0xefbfce5c,0x5) 8543 ftp-gw GIO fd 7 wrote 5 bytes "test " 8543 ftp-gw RET write 5 8543 ftp-gw CALL select(0x400,0xefbfdcb0,0,0,0xefbfdd30) 8543 ftp-gw RET select 1 8543 ftp-gw CALL read(0x8,0xefbfce5c,0x800) 8543 ftp-gw GIO fd 8 read 0 bytes "" 8543 ftp-gw RET read 0 8543 ftp-gw CALL close(0x8) 8543 ftp-gw RET close 0 8543 ftp-gw CALL close(0x7) 8543 ftp-gw RET close 0 >>... but the socket is closed Here are the traces from the pftp version. Receiver: 6966 ftpd CALL read(0x8,0xefbfcfbc,0x400) 6966 ftpd GIO fd 8 read 5 bytes "test " 6966 ftpd RET read 5 6966 ftpd CALL write(0x7,0xefbfcfbc,0x5) 6966 ftpd GIO fd 7 wrote 5 bytes "test " 6966 ftpd RET write 5 6966 ftpd CALL read(0x8,0xefbfcfbc,0x400) 6966 ftpd GIO fd 8 read 0 bytes "" 6966 ftpd RET read 0 >>read returns cleanly... 6966 ftpd CALL write(0x1,0x8059000,0x18) 6966 ftpd GIO fd 1 wrote 24 bytes "226 Transfer complete.\r " Sender: 8595 pftp CALL read(0x4,0xefbfd3e4,0x400) 8595 pftp GIO fd 4 read 5 bytes "test " 8595 pftp RET read 5 8595 pftp CALL write(0x5,0xefbfd3e4,0x5) 8595 pftp GIO fd 5 wrote 5 bytes "test " 8595 pftp RET write 5 8595 pftp CALL read(0x4,0xefbfd3e4,0x400) 8595 pftp GIO fd 4 read 0 bytes "" 8595 pftp RET read 0 8595 pftp CALL gettimeofday(0xefbfd290,0) 8595 pftp RET gettimeofday 0 8595 pftp CALL write(0x1,0xefbfd298,0x1c) 8595 pftp GIO fd 1 wrote 28 bytes "\r100% 5 00:00 ETA" 8595 pftp RET write 28/0x1c 8595 pftp CALL setitimer(0,0xefbfd234,0) 8595 pftp RET setitimer 0 8595 pftp CALL write(0x1,0x8069000,0x1) 8595 pftp GIO fd 1 wrote 1 byte " " 8595 pftp RET write 1 8595 pftp CALL close(0x4) 8595 pftp RET close 0 8595 pftp CALL close(0x5) 8595 pftp RET close 0 8595 pftp CALL sigaction(0x2,0xefbfcf50,0xefbfcf44) 8595 pftp RET sigaction 0 8595 pftp CALL read(0x3,0x8079000,0x4356) 8595 pftp GIO fd 3 read 24 bytes "226 Transfer complete.\r " Finally the packet traces. Proxy version: 19:29:48.050523 212.240.242.226.2990 > 10.3.1.251.21: P 1748251412:1748251418(6) ack 1627790365 win 17238 (DF) 19:29:48.054606 10.3.1.251.21 > 212.240.242.226.2990: P 1:47(46) ack 6 win 17238 (DF) [tos 0x10] 19:29:48.055582 212.240.242.226.2992 > 10.3.1.251.49157: S 1754860719:1754860719(0) win 16384 (DF) 19:29:48.056321 10.3.1.251.49157 > 212.240.242.226.2992: S 1634641441:1634641441(0) ack 1754860720 win 17238 (DF) 19:29:48.056656 212.240.242.226.2992 > 10.3.1.251.49157: . ack 1 win 17238 (DF) 19:29:48.066298 212.240.242.226.2990 > 10.3.1.251.21: P 6:14(8) ack 47 win 17238 (DF) 19:29:48.072126 10.3.1.251.21 > 212.240.242.226.2990: P 47:97(50) ack 14 win 17238 (DF) [tos 0x10] 19:29:48.075895 212.240.242.226.2992 > 10.3.1.251.49157: P 1:6(5) ack 1 win 17238 (DF) 19:29:48.116205 212.240.242.226.2990 > 10.3.1.251.21: . ack 97 win 17238 (DF) 19:29:48.275329 10.3.1.251.49157 > 212.240.242.226.2992: . ack 6 win 17238 (DF) [tos 0x8] pftp version: 19:35:11.579785 212.240.242.226.2998 > 10.3.1.251.21: P 1809781922:1809781928(6) ack 1688388446 win 17238 (DF) [tos 0x10] 19:35:11.584555 10.3.1.251.21 > 212.240.242.226.2998: P 1:47(46) ack 6 win 17238 (DF) [tos 0x10] 19:35:11.587443 212.240.242.226.2999 > 10.3.1.251.49158: S 1817760134:1817760134(0) win 16384 (DF) 19:35:11.588171 10.3.1.251.49158 > 212.240.242.226.2999: S 1696091157:1696091157(0) ack 1817760135 win 17238 (DF) 19:35:11.588500 212.240.242.226.2999 > 10.3.1.251.49158: . ack 1 win 17238 (DF) 19:35:11.589643 212.240.242.226.2998 > 10.3.1.251.21: P 6:14(8) ack 47 win 17238 (DF) [tos 0x10] 19:35:11.593372 10.3.1.251.21 > 212.240.242.226.2998: P 47:97(50) ack 14 win 17238 (DF) [tos 0x10] 19:35:11.597962 212.240.242.226.2999 > 10.3.1.251.49158: P 1:6(5) ack 1 win 17238 (DF) [tos 0x8] 19:35:11.601319 212.240.242.226.2999 > 10.3.1.251.49158: F 6:6(0) ack 1 win 17238 (DF) [tos 0x8] 19:35:11.601936 10.3.1.251.49158 > 212.240.242.226.2999: . ack 7 win 17238 (DF) [tos 0x8] 19:35:11.602827 10.3.1.251.21 > 212.240.242.226.2998: P 97:121(24) ack 14 win 17238 (DF) [tos 0x10] 19:35:11.603530 10.3.1.251.49158 > 212.240.242.226.2999: F 1:1(0) ack 7 win 17238 (DF) [tos 0x8] 19:35:11.603833 212.240.242.226.2999 > 10.3.1.251.49158: . ack 2 win 17238 (DF) [tos 0x8] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Mar 26 13:37:42 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 A7A4B14FBA for ; Fri, 26 Mar 1999 13:37:41 -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.1/8.9.1) with ESMTP id NAA10543; Fri, 26 Mar 1999 13:37:21 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.2/8.9.1) id NAA06321; Fri, 26 Mar 1999 13:37:21 -0800 (PST) (envelope-from jdp@polstra.com) Date: Fri, 26 Mar 1999 13:37:21 -0800 (PST) Message-Id: <199903262137.NAA06321@vashon.polstra.com> To: wheelman@nuc.net Subject: Re: PAM and Apache In-Reply-To: <001301be77a7$904c0ee0$313d31cc@nuc.net> Organization: Polstra & Co., Seattle, WA Cc: stable@freebsd.org Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <001301be77a7$904c0ee0$313d31cc@nuc.net>, Jaime Bozza wrote: > > Ok... I got that part working. :) But it still seems to not want to > validate a password. Is PAM subject to the same issues with getpwnam()? > (Unless your effective uid is 0, it returns '*' for a password) Yes. The PAM module calls getpwnam(). John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-interest is the aphrodisiac of belief." -- James V. DeLong -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-interest is the aphrodisiac of belief." -- James V. DeLong To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Mar 26 13:41:20 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 153AA14FBA for ; Fri, 26 Mar 1999 13:41:18 -0800 (PST) (envelope-from wheelman@nuc.net) Received: from electron (dhcp1.ecofl.com [204.49.61.49]) by lepton.nuc.net (8.8.8/8.8.8) with SMTP id PAA25258; Fri, 26 Mar 1999 15:40:50 -0600 (CST) (envelope-from wheelman@nuc.net) From: "Jaime Bozza" To: "John Polstra" Cc: Subject: RE: PAM and Apache Date: Fri, 26 Mar 1999 15:39:06 -0600 Message-ID: <000f01be77d1$135413e0$313d31cc@nuc.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211 In-reply-to: <199903262137.NAA06321@vashon.polstra.com> Importance: Normal Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In article <001301be77a7$904c0ee0$313d31cc@nuc.net>, > Jaime Bozza wrote: > > > > Ok... I got that part working. :) But it still seems to not want to > > validate a password. Is PAM subject to the same issues with getpwnam()? > > (Unless your effective uid is 0, it returns '*' for a password) > > Yes. The PAM module calls getpwnam(). Looks like this won't be easy for me. :) Oh well. Thanks for the quick response! Jaime Bozza Nucleus Communications To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Mar 26 15: 0:38 1999 Delivered-To: freebsd-stable@freebsd.org Received: from freebie.dcfinc.com (freebie.dcfinc.com [138.113.5.128]) by hub.freebsd.org (Postfix) with ESMTP id C7C5D15552 for ; Fri, 26 Mar 1999 15:00:35 -0800 (PST) (envelope-from chad@freebie.dcfinc.com) Received: (from chad@localhost) by freebie.dcfinc.com (8.8.7/8.8.3a) id QAA14781 for stable@FreeBSD.org; Fri, 26 Mar 1999 16:00:16 -0700 (MST) From: "Chad R. Larson" Message-Id: <199903262300.QAA14781@freebie.dcfinc.com> Subject: Re: bin/10705: enhancement to "newsyslog" To: stable@FreeBSD.org Date: Fri, 26 Mar 1999 16:00:15 -0700 (MST) Reply-To: chad@dcfinc.com X-unexpected: The Spanish Inquisition X-Mailer: ELM [version 2.4ME+ PL22 (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 I submitted an enhancement to the "newsyslog" program. I'm curious how long it usually is between a PR with attached diffs and a commitment. Is there a ball-park estimate for such things? Is there somewhere the depth of the queue that "freebsd-bugs" is working gets displayed? ----- Forwarded message from gnats-admin@FreeBSD.org ----- From gnats@FreeBSD.org Sun Mar 21 04:10:04 1999 Date: Sun, 21 Mar 1999 03:10:01 -0800 (PST) Message-Id: <199903211110.DAA19768@freefall.freebsd.org> To: chad@dcfinc.com From: gnats-admin@FreeBSD.org Subject: Re: bin/10705: enhancement to "newsyslog" Reply-To: gnats-admin@FreeBSD.org, freebsd-bugs@FreeBSD.org In-Reply-To: Your message of Sun, 21 Mar 1999 04:07:37 -0700 (MST) <199903211107.EAA04417@freebie.dcfinc.com> Sender: gnats@FreeBSD.org Thank you very much for your problem report. It has the internal identification `bin/10705'. The individual assigned to look at your report is: freebsd-bugs. >Category: bin >Responsible: freebsd-bugs >Synopsis: enhancement to "newsyslog" >Arrival-Date: Sun Mar 21 03:10:01 PST 1999 ----- End of forwarded message from gnats-admin@FreeBSD.org ----- -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org chad@anasazi.com 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 Mar 26 15:10: 9 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 9575714F65 for ; Fri, 26 Mar 1999 15:10:07 -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.1/8.9.1) with ESMTP id PAA10784; Fri, 26 Mar 1999 15:09:47 -0800 (PST) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.2/8.9.1) id PAA06681; Fri, 26 Mar 1999 15:09:47 -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: <000f01be77d1$135413e0$313d31cc@nuc.net> Date: Fri, 26 Mar 1999 15:09:46 -0800 (PST) Organization: Polstra & Co., Inc. From: John Polstra To: Jaime Bozza Subject: RE: PAM and Apache Cc: stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jaime Bozza wrote: >> In article <001301be77a7$904c0ee0$313d31cc@nuc.net>, >> Jaime Bozza wrote: >> > >> > Ok... I got that part working. :) But it still seems to not want to >> > validate a password. Is PAM subject to the same issues with getpwnam()? >> > (Unless your effective uid is 0, it returns '*' for a password) >> >> Yes. The PAM module calls getpwnam(). > > Looks like this won't be easy for me. :) Oh well. Well, I'm sure you understand the basic problem. The /etc/master.passwd file is readable only by root, so you have to be UID 0 to use it for authentication. About the only way for a non-root process to use it is to contact a daemon (running as root) that will read the file and perform the authentication. One possibility for you would be to run a RADIUS server (as root, of course) on the same machine, and use the pam_radius module to contact it. Most (if not all) of the RADIUS servers can be configured to authenticate via the passwd file. John --- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-interest is the aphrodisiac of belief." -- James V. DeLong To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Mar 26 15:15:13 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 4E87115092 for ; Fri, 26 Mar 1999 15:15:10 -0800 (PST) (envelope-from wheelman@nuc.net) Received: from electron (dhcp1.ecofl.com [204.49.61.49]) by lepton.nuc.net (8.8.8/8.8.8) with SMTP id RAA29005; Fri, 26 Mar 1999 17:14:46 -0600 (CST) (envelope-from wheelman@nuc.net) From: "Jaime Bozza" To: "John Polstra" Cc: Subject: RE: PAM and Apache Date: Fri, 26 Mar 1999 17:13:03 -0600 Message-ID: <001801be77de$33134ae0$313d31cc@nuc.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211 In-reply-to: Importance: Normal Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Well, I'm sure you understand the basic problem. The > /etc/master.passwd file is readable only by root, so you have to be Yep! I was just sort of hoping I could get away with a pre-made module that would do it directly. :) Don't worry, I would rather have the password database tightly secured, so in a way I'm glad it's this difficult. > One possibility for you would be to run a RADIUS server (as root, of > course) on the same machine, and use the pam_radius module to contact > it. Most (if not all) of the RADIUS servers can be configured to > authenticate via the passwd file. That's exactly what I switched over to. I set up a mini RADIUS server that does nothing but authenticate via the password file and only accepts requests from the same system. Everything appears to be working fine now. :) Jaime Bozza Nucleus Communications To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Mar 26 19:33:54 1999 Delivered-To: freebsd-stable@freebsd.org Received: from klentaq1.emergingtech.org (klentaq1.emergingtech.org [199.217.151.234]) by hub.freebsd.org (Postfix) with ESMTP id 3849814F61 for ; Fri, 26 Mar 1999 19:33:46 -0800 (PST) (envelope-from stabilizer@klentaq1.emergingtech.org) Received: (from stabilizer@localhost) by klentaq1.emergingtech.org (8.9.2/8.9.2) id VAA40259 for freebsd-stable@freebsd.org; Fri, 26 Mar 1999 21:37:54 GMT (envelope-from stabilizer) From: Wayne M Barnes Message-Id: <199903262137.VAA40259@klentaq1.emergingtech.org> Subject: elm and from To: freebsd-stable@freebsd.org Date: Fri, 26 Mar 1999 21:37:54 +0000 (GMT) X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dear Stabilizers, Boy, what a circular, tail-biting bug this is. Notice that this mail does not show my login name 'stabilizer' in your email listing? Instead, it shows 'To freebsd-stable...' This happened before when my login was 'wayne'. In both cases I my 3.1 system has been told my real name at adduser time. My mail is aliased to elm. Any idea how to fix this? Or is it a blessing? Wayne M Barnes stabilizer@klentaq1.emergingtech.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Mar 26 20:47:38 1999 Delivered-To: freebsd-stable@freebsd.org Received: from minubian.houabg.com (minubian.houabg.com [206.109.247.11]) by hub.freebsd.org (Postfix) with ESMTP id 3AF3614D20 for ; Fri, 26 Mar 1999 20:47:35 -0800 (PST) (envelope-from dchapman@houabg.com) Received: from houcbs2.houabg.com (HOUABG.COM [206.109.247.20]) by minubian.houabg.com (8.8.8/8.8.8) with ESMTP id XAA04903 for ; Fri, 26 Mar 1999 23:00:07 -0600 (CST) (envelope-from dchapman@houabg.com) Received: from sdn-ar-002txhousP229.dialsprint.net by houcbs2.houabg.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.0.1457.7) id HQ96QQC1; Fri, 26 Mar 1999 22:56:57 -0600 Message-ID: <36FC6410.957A198A@houabg.com> Date: Fri, 26 Mar 1999 22:52:32 -0600 From: "David W. Chapman Jr." X-Mailer: Mozilla 4.08 [en] (X11; I; FreeBSD 3.1-STABLE i386) MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: 3.1-RELEASE ISO Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Where can I find a 3.1-RELEASE ISO of FreeBSD? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Mar 26 23: 9: 3 1999 Delivered-To: freebsd-stable@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 94C1314DE2 for ; Fri, 26 Mar 1999 23:09:02 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id XAA12085; Fri, 26 Mar 1999 23:08:35 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: "David W. Chapman Jr." Cc: freebsd-stable@FreeBSD.ORG Subject: Re: 3.1-RELEASE ISO In-reply-to: Your message of "Fri, 26 Mar 1999 22:52:32 CST." <36FC6410.957A198A@houabg.com> Date: Fri, 26 Mar 1999 23:08:35 -0800 Message-ID: <12083.922518515@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Where can I find a 3.1-RELEASE ISO of FreeBSD? ftp://ftp7.de.freebsd.org/pub/FreeBSD And no, there are no mirrors that I know of. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Mar 27 0: 2:49 1999 Delivered-To: freebsd-stable@freebsd.org Received: from flash.Lakeheadu.ca (flash.lakeheadu.ca [192.75.62.101]) by hub.freebsd.org (Postfix) with ESMTP id B576314F72 for ; Sat, 27 Mar 1999 00:02:23 -0800 (PST) (envelope-from wmartin@flash.lakeheadu.ca) Received: from myrtle (ludyn-16.lakeheadu.ca [207.210.126.16]) by flash.Lakeheadu.ca (8.8.8/8.8.8) with SMTP id DAA05185 for ; Sat, 27 Mar 1999 03:02:45 -0500 (EST) Message-ID: <000801be7828$949e9b80$107ed2cf@myrtle> From: "Walter Martin" To: Subject: Joining the Stable Mailing List Date: Sat, 27 Mar 1999 03:05:27 -0500 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0005_01BE77FE.AA89AAE0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2014.211 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0005_01BE77FE.AA89AAE0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi. I would like to join the Stable Mailing list...Just installed 3.1 on = my system. Russ ------=_NextPart_000_0005_01BE77FE.AA89AAE0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi. I would like to join the Stable Mailing = list...Just=20 installed 3.1 on my system.
 
Russ
 
------=_NextPart_000_0005_01BE77FE.AA89AAE0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Mar 27 0:28: 7 1999 Delivered-To: freebsd-stable@freebsd.org Received: from pike.cdrom.com (pike.cdrom.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 4BB2914BE6 for ; Sat, 27 Mar 1999 00:28:05 -0800 (PST) (envelope-from rab@pike.cdrom.com) Received: from pike.cdrom.com (localhost.cdrom.com [127.0.0.1]) by pike.cdrom.com (8.9.1a/8.9.1) with ESMTP id AAA07933; Sat, 27 Mar 1999 00:29:33 -0800 (PST) Message-Id: <199903270829.AAA07933@pike.cdrom.com> To: freebsd-stable@freebsd.org Cc: rab@pike.cdrom.com Subject: Walnut Creek CDROM Date: Sat, 27 Mar 1999 00:29:32 -0800 From: "Robert A. Bruce" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I do not subscribe to this list, but I have heard that several people have sent complaints to this list about poor customer service and/or slow shipments from Walnut Creek CDROM. I would like to address each of these issues: 1. Customer service: If you contact Walnut Creek CDROM by phone, fax or email, and you get either no response, a slow response, or an unsatisfactory response, please send email to me at president@cdrom.com. There is no excuse for delivering anything other than excellent service. Any problem should be addressed promptly, within one business day at the longest. You should always be treated politely. All our products are unconditionally guaranteed, so no one should ever tell you that you cannot receive a full refund or exchange. I would greatly appreciate knowing about every instance where we fail to achieve these standards. 2. Slow shipments: The FreeBSD 3.1 CDROMs were replicated in near record time, but once we received them in stock, a number of mistakes were made. Our shipping department didn't have enough temporary help scheduled, and they didn't have enough shipping boxes pre-assembled. There were also some mixups left over from the transition from 2.2.8 to 3.0, because a lot of people wanted only one of those, so an invoice note was added to their order. This caused their 3.1 subscription to be kicked out for manual processing by our software. This is not an excuse, just an explaination. We have fixed the software, so this shouldn't be a problem in the future. All of these problems combined to cause unacceptable delays. WC-CDROM has made changes in our procedures and management responsibilities as a result of these problems, and we are committed to doing better in the future. Bob Bruce President, WC-CDROM To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Mar 27 0:59: 4 1999 Delivered-To: freebsd-stable@freebsd.org Received: from iclub.nsu.ru (iclub.nsu.ru [193.124.222.66]) by hub.freebsd.org (Postfix) with ESMTP id 0C15914C3F for ; Sat, 27 Mar 1999 00:58:08 -0800 (PST) (envelope-from fjoe@iclub.nsu.ru) Received: from localhost (fjoe@localhost) by iclub.nsu.ru (8.9.2/8.8.5) with ESMTP id OAA33452; Sat, 27 Mar 1999 14:54:53 +0600 (NS) Date: Sat, 27 Mar 1999 14:54:53 +0600 (NS) From: Max Khon To: "Jordan K. Hubbard" Cc: "David W. Chapman Jr." , freebsd-stable@FreeBSD.ORG Subject: Re: 3.1-RELEASE ISO In-Reply-To: <12083.922518515@zippy.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 hi, there! On Fri, 26 Mar 1999, Jordan K. Hubbard wrote: > > Where can I find a 3.1-RELEASE ISO of FreeBSD? > > ftp://ftp7.de.freebsd.org/pub/FreeBSD > > And no, there are no mirrors that I know of. ftp://ftp.gamma.ru/pub/FreeBSD/CD-ROM-images/ /fjoe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Mar 27 5:17:12 1999 Delivered-To: freebsd-stable@freebsd.org Received: from p100.isafeelin.org (isafeelin.org [194.134.1.136]) by hub.freebsd.org (Postfix) with ESMTP id 862871508B for ; Sat, 27 Mar 1999 05:17:09 -0800 (PST) (envelope-from free@p100.isafeelin.org) Received: (from free@localhost) by p100.isafeelin.org (8.9.2/8.9.2) id OAA06489 for freebsd-stable@freebsd.org; Sat, 27 Mar 1999 14:26:01 GMT From: Frederique Rijsdijk Message-Id: <199903271426.OAA06489@p100.isafeelin.org> Subject: is this a majordomo ? To: freebsd-stable@freebsd.org Date: Sat, 27 Mar 1999 14:26:01 +0000 (GMT) Reply-To: free@isafeelin.org 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 info To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Mar 27 5:42:12 1999 Delivered-To: freebsd-stable@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 87CF614EA0 for ; Sat, 27 Mar 1999 05:42:09 -0800 (PST) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 27 Mar 99 13:41:50 +0000 (GMT) To: Brian Campbell Cc: freebsd-stable@freebsd.org Subject: Re: Netscape Looping In-reply-to: Your message of "Fri, 26 Mar 1999 11:18:55 EST." <19990326111855.31338@pobox.com> X-Request-Do: Date: Sat, 27 Mar 1999 13:41:50 +0000 From: David Malone Message-ID: <9903271341.aa26260@salmon.maths.tcd.ie> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > You can basically do anything that loads the xserver I think. I originally > > noticed when I was running kdump on a huge ktrace file in an xterm while > > trying to figure out what was going on. The busy xterm made it work too. > > ico is just a nicer way of doing it (and it's in my tvtwm menues ;-) > > Have you tried running netscape as (in bourne/korn shells)? > XCMSDB=/dev/null netscape > > has been working for quite some time with my native freebsd version This seems to work, and is somewhat more straightforward than running ico. What does that variable control? David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Mar 27 8:26: 6 1999 Delivered-To: freebsd-stable@freebsd.org Received: from kot.ne.mediaone.net (kot.ne.mediaone.net [24.218.12.203]) by hub.freebsd.org (Postfix) with ESMTP id 15E5214D20 for ; Sat, 27 Mar 1999 08:26:04 -0800 (PST) (envelope-from mi@kot.ne.mediaone.net) Received: (from mi@localhost) by kot.ne.mediaone.net (8.9.1a/8.9.1) id LAA24159 for stable@freebsd.org; Sat, 27 Mar 1999 11:24:22 -0500 (EST) From: Mikhail Teterin Message-Id: <199903271624.LAA24159@kot.ne.mediaone.net> Subject: install over NFS over ep0 hangs To: stable@freebsd.org Date: Sat, 27 Mar 1999 11:24:22 -0500 (EST) X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli"; Sat, 27 Mar 1999 09:59:54 -0800 (PST) (envelope-from stabilizer@klentaq1.emergingtech.org) Received: (from stabilizer@localhost) by klentaq1.emergingtech.org (8.9.2/8.9.2) id MAA44487 for freebsd-stable@freebsd.org; Sat, 27 Mar 1999 12:04:07 GMT (envelope-from stabilizer) From: Wayne M Barnes Message-Id: <199903271204.MAA44487@klentaq1.emergingtech.org> Subject: elm and from To: freebsd-stable@freebsd.org Date: Sat, 27 Mar 1999 12:04:07 +0000 (GMT) X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dear Stabilizers, My mail shows all you guys with your names, but when I see my message, it shows as 'To freebsd-stable@' See screen piece below: 12 Mar 26 Jaime Bozza (68) RE: PAM and Apache 13 Mar 26 John Polstra (78) RE: PAM and Apache 14 Mar 26 Chad R. Larson (77) Re: bin/10705: enhancement to "newsysl N 15 Mar 26 To freebsd-stable@ (56) elm and from 16 Mar 26 Mike Tancsa (170) Re: UCD SNMP on 3.1-STABLE 17 Mar 26 Hamilton, Kent (136) RE: UCD SNMP on 3.1-STABLE 18 Mar 26 Michael C. Vergall (102) Re: UCD SNMP on 3.1-STABLE 19 Mar 26 Hamilton, Kent (80) UCD SNMP on 3.1-STABLE 20 Mar 26 Jaime Bozza (59) RE: PAM and Apache From some answers I got, I take it that everyone doesn't see my message this way. Do you each see your own messages this way? Wayne M Barnes stabilizer@klentaq1.emergingtech.org http:// " To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Mar 27 10: 8:57 1999 Delivered-To: freebsd-stable@freebsd.org Received: from pi.yip.org (yip.org [142.154.6.140]) by hub.freebsd.org (Postfix) with ESMTP id B090115469 for ; Sat, 27 Mar 1999 10:08:52 -0800 (PST) (envelope-from melange@yip.org) Received: from localhost (melange@localhost) by pi.yip.org (8.9.2/8.9.2) with ESMTP id NAA53469; Sat, 27 Mar 1999 13:08:37 -0500 (EST) (envelope-from melange@yip.org) Date: Sat, 27 Mar 1999 13:08:37 -0500 (EST) From: Bob K X-Sender: melange@localhost To: Wayne M Barnes Cc: freebsd-stable@FreeBSD.ORG Subject: Re: elm and from In-Reply-To: <199903271204.MAA44487@klentaq1.emergingtech.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 > My mail shows all you guys with your names, but when I > see my message, it shows as 'To freebsd-stable@' > > See screen piece below: > > 12 Mar 26 Jaime Bozza (68) RE: PAM and Apache > 13 Mar 26 John Polstra (78) RE: PAM and Apache > 14 Mar 26 Chad R. Larson (77) Re: bin/10705: enhancement to "newsysl > N 15 Mar 26 To freebsd-stable@ (56) elm and from > 16 Mar 26 Mike Tancsa (170) Re: UCD SNMP on 3.1-STABLE > 17 Mar 26 Hamilton, Kent (136) RE: UCD SNMP on 3.1-STABLE > 18 Mar 26 Michael C. Vergall (102) Re: UCD SNMP on 3.1-STABLE > 19 Mar 26 Hamilton, Kent (80) UCD SNMP on 3.1-STABLE > 20 Mar 26 Jaime Bozza (59) RE: PAM and Apache > > From some answers I got, I take it that everyone doesn't > see my message this way. Do you each see your own messages > this way? This sort of question would be more suitable for freebsd-questions. Anyway, I use Pine, but it behaves in exactly the same way, and has always done so. If you're using some sort of GUI, try making the window wider; I'll bet it'll then show 'To freebsd-stable@freebsd.org'. Besides, isn't it more useful to see where you sent mail to rather than just seeing that it's from you? melange@yip.org - Shave A Tree Today! (TM) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Mar 27 10:26: 7 1999 Delivered-To: freebsd-stable@freebsd.org Received: from holly.dyndns.org (ip77.houston13.tx.pub-ip.psi.net [38.27.213.77]) by hub.freebsd.org (Postfix) with ESMTP id 9DB0914BED for ; Sat, 27 Mar 1999 10:25:59 -0800 (PST) (envelope-from chris@holly.dyndns.org) Received: (from chris@localhost) by holly.dyndns.org (8.9.3/8.9.3) id MAA19267; Sat, 27 Mar 1999 12:25:17 -0600 (CST) (envelope-from chris) Date: Sat, 27 Mar 1999 12:25:15 -0600 From: Chris Costello To: Wayne M Barnes Cc: freebsd-stable@FreeBSD.ORG Subject: Re: elm and from Message-ID: <19990327122515.A15072@holly.dyndns.org> Reply-To: chris@calldei.com References: <199903271204.MAA44487@klentaq1.emergingtech.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4us In-Reply-To: <199903271204.MAA44487@klentaq1.emergingtech.org>; from Wayne M Barnes on Sat, Mar 27, 1999 at 12:04:07PM +0000 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Mar 27, 1999, Wayne M Barnes wrote: > Dear Stabilizers, > > My mail shows all you guys with your names, but when I > see my message, it shows as 'To freebsd-stable@' > > See screen piece below: > > 12 Mar 26 Jaime Bozza (68) RE: PAM and Apache > 13 Mar 26 John Polstra (78) RE: PAM and Apache > 14 Mar 26 Chad R. Larson (77) Re: bin/10705: enhancement to "newsysl > N 15 Mar 26 To freebsd-stable@ (56) elm and from > 16 Mar 26 Mike Tancsa (170) Re: UCD SNMP on 3.1-STABLE > 17 Mar 26 Hamilton, Kent (136) RE: UCD SNMP on 3.1-STABLE > 18 Mar 26 Michael C. Vergall (102) Re: UCD SNMP on 3.1-STABLE > 19 Mar 26 Hamilton, Kent (80) UCD SNMP on 3.1-STABLE > 20 Mar 26 Jaime Bozza (59) RE: PAM and Apache > > From some answers I got, I take it that everyone doesn't > see my message this way. Do you each see your own messages > this way? This doesn't necessarily belong in freebsd-stable@, but yes, we do. Anton Berezin bin/10805: h2ph incorrectly deals with #error and #warning To freebsd-bugs@FreeBSD.ORG Re: misc/10803: whois(1) client enchancements Steve Price Re: Ports question > > Wayne M Barnes stabilizer@klentaq1.emergingtech.org > http:// " > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Mar 27 10:48:38 1999 Delivered-To: freebsd-stable@freebsd.org Received: from freesbee.t.dk (freesbee.t.dk [193.162.159.97]) by hub.freebsd.org (Postfix) with SMTP id F086314BF3 for ; Sat, 27 Mar 1999 10:48:36 -0800 (PST) (envelope-from jesper@freesbee.t.dk) Received: (qmail 17958 invoked by uid 1001); 27 Mar 1999 18:48:16 -0000 Date: Sat, 27 Mar 1999 19:48:16 +0100 From: Jesper Skriver To: freebsd-stable@freebsd.org Subject: Legato Networker client on 3.1-STABLE ?? Message-ID: <19990327194816.A17897@skriver.dk> 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 Hi, I've tried the clients found at ftp://ftp.legato.com/pub/Unsupported/FreeBSD_Client/MJFeral_8_11_98_SNAP_freebsd_3_CAM_i386.tgz ftp://ftp.legato.com/pub/Unsupported/FreeBSD_Client/MJFeral_8_11_98_SNAP_freebsd_2_2_2_i386.tgz ftp://ftp.legato.com/pub/Unsupported/freebsd2.tar.gz All dumps core with a bus error when you start the nsrexecd daemon ... Does any have a working client for 3.1-STABLE, or any ideas on how to get these to work ? /Jesper -- Jesper Skriver (JS4261-RIPE), Network manager Tele Danmark DataNet, IP section (AS3292) 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 Sat Mar 27 11:19:20 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.westbend.net (ns1.westbend.net [209.224.254.131]) by hub.freebsd.org (Postfix) with ESMTP id 14DB014BE6 for ; Sat, 27 Mar 1999 11:19:18 -0800 (PST) (envelope-from hetzels@westbend.net) Received: from admin (admin.westbend.net [209.224.254.141]) by mail.westbend.net (8.8.8/8.8.8) with SMTP id NAA01658; Sat, 27 Mar 1999 13:18:54 -0600 (CST) (envelope-from hetzels@westbend.net) Message-ID: <019001be7886$a7e4e7e0$8dfee0d1@westbend.net> From: "Scot W. Hetzel" To: Cc: References: Subject: Re: Problem with "make release" Date: Sat, 27 Mar 1999 13:18:54 -0600 Organization: West Bend Internet 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.2014.211 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From: Vladimir Litovka > without errors. Optimization.... BTW do FreeBSD's team have plans to use > egcs as main compiler or no? Or gcc 2.8.x at least... > The FreeBSD team is looking into adding egcs into 4.0-CURRENT as the next compiler for FreeBSD. Currently, it appears to be working but hasn't been integrated into the 4.0-CURRENT source tree. Scot To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Mar 27 11:28:22 1999 Delivered-To: freebsd-stable@freebsd.org Received: from freebie.dcfinc.com (freebie.dcfinc.com [138.113.5.128]) by hub.freebsd.org (Postfix) with ESMTP id AA9C614DE5 for ; Sat, 27 Mar 1999 11:28:21 -0800 (PST) (envelope-from chad@freebie.dcfinc.com) Received: (from chad@localhost) by freebie.dcfinc.com (8.8.7/8.8.3a) id MAA17414; Sat, 27 Mar 1999 12:27:17 -0700 (MST) From: "Chad R. Larson" Message-Id: <199903271927.MAA17414@freebie.dcfinc.com> Subject: Re: elm and from To: stabilizer@klentaq1.emergingtech.org (Wayne M Barnes) Date: Sat, 27 Mar 1999 12:27:17 -0700 (MST) Cc: freebsd-stable@FreeBSD.ORG In-Reply-To: <199903271204.MAA44487@klentaq1.emergingtech.org> from Wayne M Barnes at "Mar 27, 99 12:04:07 pm" Reply-To: chad@dcfinc.com X-unexpected: The Spanish Inquisition X-Mailer: ELM [version 2.4ME+ PL22 (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 > Dear Stabilizers, > > My mail shows all you guys with your names, but when I > see my message, it shows as 'To freebsd-stable@' It's the way ELM and frm work. They will show mail you originated as "To" the first recipient on your address list. Other mail shows the sender. The other people on the list will see your name in that spot. It's a feature, and one I like. -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org chad@anasazi.com 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 Sat Mar 27 12:29:18 1999 Delivered-To: freebsd-stable@freebsd.org Received: from freesbee.t.dk (freesbee.t.dk [193.162.159.97]) by hub.freebsd.org (Postfix) with SMTP id AD6DF14FCA for ; Sat, 27 Mar 1999 12:29:14 -0800 (PST) (envelope-from jesper@freesbee.t.dk) Received: (qmail 19548 invoked by uid 1001); 27 Mar 1999 20:28:54 -0000 Date: Sat, 27 Mar 1999 21:28:54 +0100 From: Jesper Skriver To: freebsd-stable@freebsd.org Subject: Re: Legato Networker client on 3.1-STABLE ?? Message-ID: <19990327212854.A19525@skriver.dk> References: <19990327194816.A17897@skriver.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <19990327194816.A17897@skriver.dk>; from Jesper Skriver on Sat, Mar 27, 1999 at 07:48:16PM +0100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Mar 27, 1999 at 07:48:16PM +0100, Jesper Skriver wrote: > Hi, > > I've tried the clients found at > > ftp://ftp.legato.com/pub/Unsupported/FreeBSD_Client/MJFeral_8_11_98_SNAP_freebsd_3_CAM_i386.tgz > ftp://ftp.legato.com/pub/Unsupported/FreeBSD_Client/MJFeral_8_11_98_SNAP_freebsd_2_2_2_i386.tgz > ftp://ftp.legato.com/pub/Unsupported/freebsd2.tar.gz > > All dumps core with a bus error when you start the nsrexecd daemon ... > > Does any have a working client for 3.1-STABLE, or any ideas on how to > get these to work ? I got them working, Matthew Jacob identified that it was caused by too many files pr. user, and it works after lowering MAXUSERS from 256 to 16 /Jesper -- Jesper Skriver (JS4261-RIPE), Network manager Tele Danmark DataNet, IP section (AS3292) 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 Sat Mar 27 12:43:42 1999 Delivered-To: freebsd-stable@freebsd.org Received: from main.avias.com (avias-gw.corbina.net [195.14.40.4]) by hub.freebsd.org (Postfix) with ESMTP id 430EE15244 for ; Sat, 27 Mar 1999 12:43:39 -0800 (PST) (envelope-from j@avias.com) Received: from dialup1.avias.com (dialup1.avias.com [195.14.38.68]) by main.avias.com (8.9.2/8.9.2) with SMTP id XAA04947 for ; Sat, 27 Mar 1999 23:43:19 +0300 (MSK) (envelope-from j@avias.com) Date: Sat, 27 Mar 1999 23:44:59 +0300 From: Juriy Goloveshkin X-Mailer: The Bat! (v1.22) S/N D508402B Reply-To: Juriy Goloveshkin X-Priority: 3 (Normal) Message-ID: <16989.990327@avias.com> To: freebsd-stable@freebsd.org Subject: ntfs Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Recently ntfs-specific code has been added in stable branch. When will this code activate in Makefile`s? Bye, Juriy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Mar 27 13: 7:22 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 7214314EE7 for ; Sat, 27 Mar 1999 13:07:10 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: (from uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id VAA22245; Sat, 27 Mar 1999 21:40:23 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.8.8/8.6.12) id VAA01948; Sat, 27 Mar 1999 21:24:14 +0100 (CET) From: Wilko Bulte Message-Id: <199903272024.VAA01948@yedi.iaf.nl> Subject: Re: Legato Networker client on 3.1-STABLE ?? In-Reply-To: <19990327194816.A17897@skriver.dk> from Jesper Skriver at "Mar 27, 1999 7:48:16 pm" To: jesper@skriver.dk (Jesper Skriver) Date: Sat, 27 Mar 1999 21:24:13 +0100 (CET) Cc: freebsd-stable@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As Jesper Skriver wrote ... > Hi, > > I've tried the clients found at > > ftp://ftp.legato.com/pub/Unsupported/FreeBSD_Client/MJFeral_8_11_98_SNAP_freebsd_3_CAM_i386.tgz > ftp://ftp.legato.com/pub/Unsupported/FreeBSD_Client/MJFeral_8_11_98_SNAP_freebsd_2_2_2_i386.tgz > ftp://ftp.legato.com/pub/Unsupported/freebsd2.tar.gz > > All dumps core with a bus error when you start the nsrexecd daemon ... > > Does any have a working client for 3.1-STABLE, or any ideas on how to > get these to work ? You could ask Matt Jacob, as he is the one who creates the NSR clients for FreeBSD. AFAIK he has a special arrangement with Legato enabling him to use the Legato source base and distribute binary-only clients, all under the assumption that Legato does not want to be bothered by supporting them. See also www.feral.com Groeten / Cheers, Wilko _ ______________________________________________________________________ | / o / / _ Arnhem, The Netherlands |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl _______________________ Powered by FreeBSD ___ 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 Sat Mar 27 18:19: 5 1999 Delivered-To: freebsd-stable@freebsd.org Received: from kot.ne.mediaone.net (kot.ne.mediaone.net [24.218.12.203]) by hub.freebsd.org (Postfix) with ESMTP id 206B215673 for ; Sat, 27 Mar 1999 18:19:02 -0800 (PST) (envelope-from mi@aldan.algebra.com) Received: from rtfm.ziplink.net (rtfm [10.10.0.1]) by kot.ne.mediaone.net (8.9.1a/8.9.1) with ESMTP id VAA27881 for ; Sat, 27 Mar 1999 21:18:38 -0500 (EST) From: Mikhail Teterin X-Relay-IP: 10.10.0.1 Received: (from mi@localhost) by rtfm.ziplink.net (8.9.2/8.9.1) id VAA64903 for stable@freebsd.org; Sat, 27 Mar 1999 21:18:34 -0500 (EST) Message-Id: <199903280218.VAA64903@rtfm.ziplink.net> Subject: panic on Mar 26 3.1-stable snapshot To: stable@freebsd.org Date: Sat, 27 Mar 1999 21:18:34 -0500 (EST) X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli"; Sat, 27 Mar 1999 18:20:03 -0800 (PST) (envelope-from wolfnet@wolfnet-irc.org) Received: from wolfnet-irc.org (users.wolfnet-irc.org [209.64.46.42]) by falcon.lonetree.com (8.8.7/8.8.7) with ESMTP id TAA31166 for ; Sat, 27 Mar 1999 19:19:42 -0700 Message-ID: <36FD92ED.AE91B6AF@wolfnet-irc.org> Date: Sat, 27 Mar 1999 19:24:46 -0700 From: Jonathan Frazier Organization: The WolfNet-IRC Organization X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 3.1-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: Netscape 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 been having errors after installing Netscape 4.5 on my 3.1-stable box. ld.so failed: Can't find shared library "libXt.so.6.0" If I type this: ldconfig -aout -m /usr/X11R6/lib then everything works and I have no problem, but that gets really old typing that after every reboot. I checked out my "ldconfig -aout -r" and /usr/X11R6/lib/aout is in there however /usr/X11R6/lib is not. And my /usr/X11R6/lib/aout directory is empty. Any help with this would be appreciated...not sure if I should copy the /usr/X11R6/lib directory to the aout lib directory or not....or if there will be any repercussions. Thanks. -- Jonathan C. Frazier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Mar 27 21:10:17 1999 Delivered-To: freebsd-stable@freebsd.org Received: from bolero-x.rahul.net (bolero.rahul.net [192.160.13.1]) by hub.freebsd.org (Postfix) with SMTP id AD15615238 for ; Sat, 27 Mar 1999 21:10:16 -0800 (PST) (envelope-from dhesi@rahul.net) Received: from q.bolero.rahul.net (bolero.rahul.net) by bolero-x.rahul.net with SMTP id AA12831 (5.67b8/IDA-1.5 for ); Sat, 27 Mar 1999 21:09:57 -0800 Message-Id: <199903280509.AA12831@bolero-x.rahul.net> Received: (qmail 12827 invoked from network); 28 Mar 1999 05:09:56 -0000 Received: from waltz.rahul.net (192.160.13.9) by bolero.rahul.net with SMTP; 28 Mar 1999 05:09:56 -0000 To: freebsd-stable@freebsd.org Subject: NFS hangs in 3.0-RELEASE, 3.1-RELEASE, 3.1-19990323-STABLE Date: Sat, 27 Mar 1999 21:09:55 -0800 From: Rahul Dhesi Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am able to make NFS hang as follows: - Have two machines running 3.1-19990323-STABLE NFS-mount filesystems from each other. - On each machine, on a filesystem NFS-mounted from the other, create 10 subdirectories, and start 10 tar pipelines copying the entire /usr/src directory tree into each of said subdirectories. After a few minutes, you will get 'NFS server xxx not responding' messages on both machines. All activities that cause NFS access, including 'df', will hang. Other activities will work just fine. Load average will be low. New process creation is not affected. Compiling a kernel with maxusers=256 does not help. Both 'reboot' and 'reboot -q' will hang and fail to reboot the machine. But 'reboot -n' will succeed in rebooting the machine. I have done this experiment with all of: 3.0-RELEASE, 3.1-RELEASE, 3.1-19990323-STABLE, and a number of snapshots between 3.0-RELEASE and 3.1-RELEASE. In all cases the above experiment causes NFS to hang. I will be happy to provide more detailed information if anybody needs it. Formal PR upon specific request, if somebody can find the time to work on it. Rahul To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Mar 27 23:27: 8 1999 Delivered-To: freebsd-stable@freebsd.org Received: from david.siemens.de (david.siemens.de [192.35.17.14]) by hub.freebsd.org (Postfix) with ESMTP id 75C03151C1 for ; Sat, 27 Mar 1999 23:27:05 -0800 (PST) (envelope-from andre.albsmeier@mchp.siemens.de) X-Envelope-Sender-Is: andre.albsmeier@mchp.siemens.de (at relayer david.siemens.de) Received: from mail1.siemens.de (mail1.siemens.de [139.23.33.14]) by david.siemens.de (8.9.3/8.9.3) with ESMTP id JAA06236 for ; Sun, 28 Mar 1999 09:27:01 +0200 (MET DST) Received: from curry.mchp.siemens.de (curry.mchp.siemens.de [146.180.31.23]) by mail1.siemens.de (8.9.3/8.9.3) with ESMTP id JAA09572 for ; Sun, 28 Mar 1999 09:26:32 +0200 (MET DST) Received: (from daemon@localhost) by curry.mchp.siemens.de (8.8.8/8.8.8) id JAA76382 for ; Sun, 28 Mar 1999 09:26:45 +0200 (CEST) Date: Sun, 28 Mar 1999 09:26:43 +0200 From: Andre Albsmeier To: freebsd-stable@freebsd.org Subject: Still no CTMs for international crypto stuff? Message-ID: <19990328092643.A25660@internal> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just looked on ftp.internat.freebsd.org but couldn't find any international crypto stuff for FreeBSD-3.x. Is there a different place to look? Thanks, -Andre To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message