From owner-freebsd-stable  Sun Mar 26  2:27:15 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from mail.uct.ac.za (mail.uct.ac.za [137.158.128.3])
	by hub.freebsd.org (Postfix) with ESMTP id 0290B37B8E2
	for <stable@freebsd.org>; Sun, 26 Mar 2000 02:27:07 -0800 (PST)
	(envelope-from dks@its.uct.ac.za)
Received: from dks.its.uct.ac.za ([137.158.27.4] helo=its.uct.ac.za)
	by mail.uct.ac.za with esmtp (Exim 3.13 #1)
	id 12ZAG5-0005a0-00
	for stable@freebsd.org; Sun, 26 Mar 2000 12:27:01 +0200
Message-ID: <38DDE5F9.C8FF62A4@its.uct.ac.za>
Date: Sun, 26 Mar 2000 12:27:05 +0200
From: Daniel Smith <dks@its.uct.ac.za>
Organization: University of Cape Town
X-Mailer: Mozilla 4.7 [en-gb] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: stable@freebsd.org
Subject: NDS for Linux support?
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hi,

I see that Novell announced NDS for Linux (
http://www.novell.com/products/nds/ ) on March 13th.

Has anyone had chance to see how (or if) this ties in with the linux
emulation code yet?

Cheers,

Daniel.

----------------------------------------------------
Daniel Smith               Systems Software Manager
University of Cape Town      Systems Administrator



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


From owner-freebsd-stable  Sun Mar 26  4:16:10 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from phoenix.kurgan.ru (phoenix.kurgan.ru [195.54.28.21])
	by hub.freebsd.org (Postfix) with ESMTP id 5B67437B6DC
	for <freebsd-stable@FreeBSD.ORG>; Sun, 26 Mar 2000 04:16:03 -0800 (PST)
	(envelope-from Martin@McFlySr.Kurgan.Ru)
Received: from PAVEL (hilldale.kurgan.ru [195.54.28.11])
	by phoenix.kurgan.ru (8.9.3/8.9.3) with ESMTP id SAA05186
	for <freebsd-stable@FreeBSD.ORG>; Sun, 26 Mar 2000 18:15:58 +0600 (YEKST)
Date: Sun, 26 Mar 2000 18:15:57 +0600
From: Martin McFlySr <Martin@McFlySr.Kurgan.Ru>
Reply-To: Martin McFlySr <Martin@McFlySr.Kurgan.Ru>
Organization: Back To The Future
X-Priority: 3 (Normal)
Message-ID: <8761.000326@McFlySr.Kurgan.Ru>
To: freebsd-stable@FreeBSD.ORG
Subject: update from 3.x to 4.0 stable - make buildworld fails :(
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 ,

1. maked cvsup (all components)
2. reading /usr/src/UPDATING:

To update from 3.x to 4.0 stable
--------------------------------
<see notes below>                               [***]
[***] Update to 4.0-stable sources.  Make sure that you get all
the parts.  If you are using cvsup files that are older than a
couple of months, be sure they have all the components listed
in /usr/share/examples/cvsup.  Crypto and secure are now
required.

done.

cd /usr/src
<see notes below>                               [**]

[**] If you have any of the following in your /etc/make.conf,
please comment them out before following these instructions
and then do a make buildworld + make installworld after you
are back to <multi-user> above:
        MAKE_KERBEROS4

#grep "MAKE_KERBEROS4" /etc/make.conf
MAKE_KERBEROS4= yes


#cd /usr
#ls -ls |grep src
src -> /pub/usr/src
#cd src

make buildworld

>
> --------------------------------------------------------------
>>>> Rebuilding the temporary build tree
> --------------------------------------------------------------
> rm -rf /usr/obj/pub/usr/src/i386
> mkdir -p /usr/obj/pub/usr/src/i386/usr/bin
> mkdir -p /usr/obj/pub/usr/src/i386/usr/lib/compat/aout
> mkdir -p /usr/obj/pub/usr/src/i386/usr/games
> mkdir -p /usr/obj/pub/usr/src/i386/usr/libdata/ldscripts
> mkdir -p /usr/obj/pub/usr/src/i386/usr/libexec/elf
> mkdir -p /usr/obj/pub/usr/src/i386/usr/sbin
> mkdir -p /usr/obj/pub/usr/src/i386/usr/share/misc
> mkdir -p /usr/obj/pub/usr/src/i386/usr/include/arpa
> mkdir -p /usr/obj/pub/usr/src/i386/usr/include/g++/std
> mkdir -p /usr/obj/pub/usr/src/i386/usr/include/objc
> mkdir -p /usr/obj/pub/usr/src/i386/usr/include/protocols
> mkdir -p /usr/obj/pub/usr/src/i386/usr/include/readline
> mkdir -p /usr/obj/pub/usr/src/i386/usr/include/rpc
> mkdir -p /usr/obj/pub/usr/src/i386/usr/include/rpcsvc
> mkdir -p /usr/obj/pub/usr/src/i386/usr/include/openssl
> mkdir -p /usr/obj/pub/usr/src/i386/usr/include/security
> mkdir -p /usr/obj/pub/usr/src/i386/usr/include/ss
> ln -sf /pub/usr/src/sys /usr/obj/pub/usr/src/i386/sys
> 
> --------------------------------------------------------------
>>>> stage 1: bootstrap tools
> --------------------------------------------------------------
> cd /pub/usr/src; MAKEOBJDIRPREFIX=/usr/obj/pub/usr/src/i386  DESTDIR=/usr/obj/pub/usr/src/i386  INSTALL="sh
> /pub/usr/src/tools/install.sh"  MACHINE_ARCH=i386  TOOLS_PREFIX=/usr/obj/pub/usr/src/i386 
> PATH=/usr/obj/pub/usr/src/i386/usr/sbin:/usr/obj/pub/usr/src/i386/usr/bin:/usr/obj/pub/usr/src/i386/usr/games:/sbin:/bin:/usr/sbin:/usr/bin
> make -f Makefile.inc1 -DNOMAN -DNOINFO -DNOHTML bootstrap-tools
> cd /pub/usr/src/usr.bin/yacc;  make obj;  make depend;  make all;  make install
> /usr/obj/pub/usr/src/i386/pub/usr/src/usr.bin/yacc created for /pub/usr/src/usr.bin/yacc
> rm -f .depend
> mkdep -f .depend -a    -I/usr/obj/pub/usr/src/i386/usr/include  /pub/usr/src/usr.bin/yacc/closure.c
> /pub/usr/src/usr.bin/yacc/error.c /pub/usr/src/usr.bin/yacc/lalr.c /pub/usr/src/usr.bin/yacc/lr0.c
> /pub/usr/src/usr.bin/yacc/main.c /pub/usr/src/usr.bin/yacc/mkpar.c /pub/usr/src/usr.bin/yacc/output.c
> /pub/usr/src/usr.bin/yacc/reader.c /pub/usr/src/usr.bin/yacc/skeleton.c /pub/usr/src/usr.bin/yacc/symtab.c
> /pub/usr/src/usr.bin/yacc/verbose.c /pub/usr/src/usr.bin/yacc/warshall.c
> cd /pub/usr/src/usr.bin/yacc; make _EXTRADEPEND
> echo yacc: /usr/obj/pub/usr/src/i386/usr/lib/libc.a  >> .depend
> cc -O -pipe   -I/usr/obj/pub/usr/src/i386/usr/include -c /pub/usr/src/usr.bin/yacc/closure.c
> cc -O -pipe   -I/usr/obj/pub/usr/src/i386/usr/include -c /pub/usr/src/usr.bin/yacc/error.c
> cc -O -pipe   -I/usr/obj/pub/usr/src/i386/usr/include -c /pub/usr/src/usr.bin/yacc/lalr.c
> cc -O -pipe   -I/usr/obj/pub/usr/src/i386/usr/include -c /pub/usr/src/usr.bin/yacc/lr0.c
> cc -O -pipe   -I/usr/obj/pub/usr/src/i386/usr/include -c /pub/usr/src/usr.bin/yacc/main.c
> cc -O -pipe   -I/usr/obj/pub/usr/src/i386/usr/include -c /pub/usr/src/usr.bin/yacc/mkpar.c
> cc -O -pipe   -I/usr/obj/pub/usr/src/i386/usr/include -c /pub/usr/src/usr.bin/yacc/output.c
> cc -O -pipe   -I/usr/obj/pub/usr/src/i386/usr/include -c /pub/usr/src/usr.bin/yacc/reader.c
> cc -O -pipe   -I/usr/obj/pub/usr/src/i386/usr/include -c /pub/usr/src/usr.bin/yacc/skeleton.c
> cc -O -pipe   -I/usr/obj/pub/usr/src/i386/usr/include -c /pub/usr/src/usr.bin/yacc/symtab.c
> cc -O -pipe   -I/usr/obj/pub/usr/src/i386/usr/include -c /pub/usr/src/usr.bin/yacc/verbose.c
> cc -O -pipe   -I/usr/obj/pub/usr/src/i386/usr/include -c /pub/usr/src/usr.bin/yacc/warshall.c
> cc -O -pipe   -I/usr/obj/pub/usr/src/i386/usr/include  -o yacc closure.o error.o lalr.o lr0.o main.o mkpar.o
> output.o reader.o skeleton.o symtab.o verbose.o warshall.o  
> sh /pub/usr/src/tools/install.sh -c -o root -g wheel -m 555  /pub/usr/src/usr.bin/yacc/yyfix.sh
> /usr/obj/pub/usr/src/i386/usr/bin/yyfix
> sh /pub/usr/src/tools/install.sh -c -s -o root -g wheel -m 555   yacc /usr/obj/pub/usr/src/i386/usr/bin
> /usr/obj/pub/usr/src/i386/usr/bin/byacc -> /usr/obj/pub/usr/src/i386/usr/bin/yacc
> cd /pub/usr/src/usr.bin/colldef;  make obj;  make depend;  make all;  make install
> /usr/obj/pub/usr/src/i386/pub/usr/src/usr.bin/colldef created for /pub/usr/src/usr.bin/colldef
> yacc -d /pub/usr/src/usr.bin/colldef/parse.y
> *** Signal 12
> 
> Stop.
> *** Error code 1
> 
> Stop.
> *** Error code 1
> 
> Stop.
> *** Error code 1
> 
> Stop.

What can i fix errors and updating my 3.4s to 4.0?

Thank you,


-- 
Sunday, March 26, 2000,
18:05

Best regards from future,
Martin McFlySr, HillDale.




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


From owner-freebsd-stable  Sun Mar 26  4:49:18 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from tasogare.imasy.or.jp (tasogare.imasy.or.jp [202.227.24.5])
	by hub.freebsd.org (Postfix) with ESMTP id A67FC37B6DC
	for <freebsd-stable@FreeBSD.ORG>; Sun, 26 Mar 2000 04:49:16 -0800 (PST)
	(envelope-from iwasaki@jp.FreeBSD.org)
Received: from localhost (isdnb52.imasy.or.jp [202.227.24.180])
	by tasogare.imasy.or.jp (8.9.3+3.2W/3.7W-tasogare/smtpfeed 1.01) with ESMTP id VAA05285;
	Sun, 26 Mar 2000 21:49:13 +0900 (JST)
	(envelope-from iwasaki@jp.FreeBSD.org)
Message-Id: <200003261249.VAA05285@tasogare.imasy.or.jp>
To: imp@village.org
Cc: winter@jurai.net, iwasaki@jp.FreeBSD.org,
	freebsd-stable@FreeBSD.ORG
Subject: Re: FIXED --> Thanks! Re: ep0 eeprom failed to come ready... 
In-Reply-To: Your message of "Sat, 25 Mar 2000 18:12:07 -0700"
	<200003260112.SAA76635@harmony.village.org>
References: <200003260112.SAA76635@harmony.village.org>
X-Mailer: Mew version 1.93 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Sun, 26 Mar 2000 21:49:13 +0900
From: Mitsuru IWASAKI <iwasaki@jp.FreeBSD.org>
X-Dispatcher: imput version 980905(IM100)
Lines: 25
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hi,

> In message <Pine.BSF.4.21.0003251939390.50194-100000@sasami.jurai.net> "Matthew N. Dodd" writes:
> : Ah.  So what we really want is some mechanism to tell the kernel 'hey,
> : you!  don't use this ioport/irq whatever.' (or otherwise mark some
> : resources as not being available to PnP devices.)
> 
> I think that a null driver could easily be written.
> 
> I also think that combined with the hint mechanism I posted to new-bus
> a couple of days ago this could be a viable way to reserve interrupts
> from the boot loader.

That would be good.  I'm also having similer idea that loading kernel
loadable module for legacy non-PnP devices specifying thier resources, like;

load pcm
load sbc port 0x220 irq 5 drq 1 flags 0x15

Or, null driver module maybe just enough to hold resources;
load resourceholder port 0x220 irq 5 drq 1
load resourceholder port drq 5

# BTW, it seems that the discussion is away from ep driver and -stable already :)
# Should we move to somewhere?


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


From owner-freebsd-stable  Sun Mar 26  5:18:43 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from mail2.gmx.net (mail2.gmx.net [194.221.183.62])
	by hub.freebsd.org (Postfix) with SMTP id A3C2F37B585
	for <freebsd-stable@FreeBSD.ORG>; Sun, 26 Mar 2000 05:18:39 -0800 (PST)
	(envelope-from Gerhard.Sittig@gmx.net)
Received: (qmail 3711 invoked by uid 0); 26 Mar 2000 13:18:36 -0000
Received: from p3e9c3597.dip.t-dialin.net (HELO speedy.gsinet) (62.156.53.151)
  by mail2.gmx.net with SMTP; 26 Mar 2000 13:18:36 -0000
Received: (from sittig@localhost)
	by speedy.gsinet (8.8.8/8.8.8) id LAA07671
	for freebsd-stable@FreeBSD.ORG; Sun, 26 Mar 2000 11:31:27 +0200
Date: Sun, 26 Mar 2000 11:31:27 +0200
From: Gerhard Sittig <Gerhard.Sittig@gmx.net>
To: freebsd-stable@FreeBSD.ORG
Subject: Re: FIXED --> Thanks! Re: ep0 eeprom failed to come ready...
Message-ID: <20000326113126.D24822@speedy.gsinet>
Mail-Followup-To: freebsd-stable@FreeBSD.ORG
References: <Pine.BSF.4.21.0003251939390.50194-100000@sasami.jurai.net> <200003260112.SAA76635@harmony.village.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0i
In-Reply-To: <200003260112.SAA76635@harmony.village.org>; from imp@village.org on Sat, Mar 25, 2000 at 06:12:07PM -0700
Organization: System Defenestrators Inc.
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Sat, Mar 25, 2000 at 18:12 -0700, Warner Losh wrote:
> In message <Pine.BSF.4.21.0003251939390.50194-100000@sasami.jurai.net> "Matthew N. Dodd" writes:
> : Ah.  So what we really want is some mechanism to tell the kernel 'hey,
> : you!  don't use this ioport/irq whatever.' (or otherwise mark some
> : resources as not being available to PnP devices.)
> 
> I think that a null driver could easily be written.

Thinking a little longer about this one it seems to be even more
complex:  It had to "allocate" some resources for itself so that
no other PCI or ICU component can get it.  BUT there should be
means to release them later or hand them out in case some
(legacy) ISA hardware needs it.

> I also think that combined with the hint mechanism I posted to
> new-bus a couple of days ago this could be a viable way to
> reserve interrupts from the boot loader.

This sounds like what is written above and what's badly needed:
A way to "shrink" the pool of available resources for automatic
assignment.  This is really essential for those cases where the
BIOS provides no way of doing so (speaking for myself this is
more of the usual case than an exception, here).


virtually yours   82D1 9B9C 01DC 4FB4 D7B4  61BE 3F49 4F77 72DE DA76
Gerhard Sittig   true | mail -s "get gpg key" Gerhard.Sittig@gmx.net
-- 
     If you don't understand or are scared by any of the above
             ask your parents or an adult to help you.


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


From owner-freebsd-stable  Sun Mar 26  5:28:38 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from charon.ipass.net (charon.ipass.net [198.79.53.8])
	by hub.freebsd.org (Postfix) with ESMTP id 19FE437B6F3
	for <stable@freebsd.org>; Sun, 26 Mar 2000 05:28:36 -0800 (PST)
	(envelope-from rhh@ipass.net)
Received: from stealth.ipass.net. (ppp-4-93.dialup.rdu.ipass.net [209.170.134.93])
	by charon.ipass.net (8.9.3/8.9.3) with ESMTP id IAA04303
	for <stable@freebsd.org>; Sun, 26 Mar 2000 08:28:27 -0500 (EST)
Received: (from rhh@localhost)
	by stealth.ipass.net. (8.9.3/8.8.8) id IAA75637
	for stable@freebsd.org; Sun, 26 Mar 2000 08:31:01 -0500 (EST)
	(envelope-from rhh)
Date: Sun, 26 Mar 2000 08:31:00 -0500
From: Randall Hopper <aa8vb@ipass.net>
To: stable@freebsd.org
Subject: send-pr and emacs -- problem
Message-ID: <20000326083100.A75560@ipass.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0.1i
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Is anyone using send-pr with emacs?

When I save and quit, about half the time it works, and the other half
send-pr aborts, doesn't send the PR, and doesn't give me a backup (unless
I'd thought to save one):

  -:---F1  p74973           (Text Fill)--L129--Bot-----------------------------
  send-pr: Aborting ...
  stealth : /tmp >

In my environment, I have:

  EDITOR="emacs -nw"                  (without quotes)

Is there something else I should be doing to get send-pr to play nicely
with Emacs?

Thanks,

Randall


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


From owner-freebsd-stable  Sun Mar 26  6:17:31 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from info.iet.unipi.it (info.iet.unipi.it [131.114.9.184])
	by hub.freebsd.org (Postfix) with ESMTP id 2C03437B9DE
	for <freebsd-stable@FreeBSD.ORG>; Sun, 26 Mar 2000 06:17:25 -0800 (PST)
	(envelope-from luigi@info.iet.unipi.it)
Received: (from luigi@localhost)
	by info.iet.unipi.it (8.9.3/8.9.3) id QAA19680;
	Sun, 26 Mar 2000 16:18:12 +0200 (CEST)
	(envelope-from luigi)
From: Luigi Rizzo <luigi@info.iet.unipi.it>
Message-Id: <200003261418.QAA19680@info.iet.unipi.it>
Subject: Re: Minor rc.network bug for 4.0 and ipfw
In-Reply-To: <p04310101b5032cb2a0b9@[207.244.92.51]> from Tom Legg at "Mar 25,
 2000 10:19:05 pm"
To: Tom Legg <tjlegg@shore.net>
Date: Sun, 26 Mar 2000 16:18:12 +0200 (CEST)
Cc: freebsd-stable@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL61 (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

Since I was the one who introduced net.inet.ip.fw.enable ...
The variable was inserted so that one could independently
choose to use the firewall at the IP level, or at the bridging level,
or at both places. Soon after that i introduced the 'bridged'
specifier in ipfw rules which rendered the variable partly
superflous for the above purpose, except that it helps in
some cases when one wants to debug a ruleset and temporarily
bring the machine online whitout deleting the entire ruleset
(e.g. think of remote management: you build a script that
introduces the new ruleset, sets net.inet.ip.fw.enable=1, and
if no confirmation arrives within the next 15 seconds brings
the variable back to 0 so a remote admin can try sort things out).

So i dont think rc.network should touch the sysctl variable depending
on the shell variable firewall_enable.

	cheers
	luigi

> If you compile a kernel with ipfw in the kernel but do nothing to 
> modify /etc/defaults/rc.conf and boot, net.inet.ip.fw.enable is set 
> to 1 and since the defaults for enable is NO, no further action is 
> done upon the firewall scripts.
> 
> Since the current /etc/rc.network only seems to check for 
> firewall_enable="yes", it doesn't seem to reverse the default (which 
> is enable=1) and at the same time doesn't read any of the options 
> about what type of firewall the user would like. I've written a test 
> patch for /etc/rc.network that checks for the case 
> firewall_enable="no" and set net.inet.ip.fw.enable to 0. (note: this 
> has to go at least before the dhcp client invocation *grin*) But 
> something seems wrong about doing a check during a boot to reset the 


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


From owner-freebsd-stable  Sun Mar 26  6:37:36 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from wally.bellnetworks.net (www.bellnetworks.net [216.214.153.70])
	by hub.freebsd.org (Postfix) with ESMTP id 015F337B693
	for <freebsd-stable@FreeBSD.ORG>; Sun, 26 Mar 2000 06:37:31 -0800 (PST)
	(envelope-from jerry@bellnetworks.net)
Received: from itbell (dhcp-247.bellnetworks.net [208.177.187.247])
	by wally.bellnetworks.net (8.9.3/8.9.3) with SMTP id JAA45915
	for <freebsd-stable@FreeBSD.ORG>; Sun, 26 Mar 2000 09:37:29 -0500 (EST)
	(envelope-from jerry@bellnetworks.net)
Message-ID: <015801bf96cc$14f8fce0$f7bbb1d0@netrex.com>
From: "Jerry Bell" <jerry@bellnetworks.net>
To: <freebsd-stable@FreeBSD.ORG>
References: <XFMail.000326095323.mike@rbc.ru>
Subject: Re: ps, w, top and netstat problem
Date: Sat, 25 Mar 2000 21:36:25 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="KOI8-R"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

It seems like no matter what I do, I am still get this problem.  I had
originally installed 4.0RELEASE on this box, and it worked perfectly.

I ran mergemaster to make sure all the configuration files were up to date.
I copied cp /usr/src/etc/MAKEDEV to /dev and ran a ./MAKEDEV all.

I just tried removing the 'options PROCFS' from the kernel config and
recompiled.  After a reboot, I get the same thing.

I ran another make buildworld and make installworld, so the ps, w, top and
netstat binaries are _definately_ in sync with the kernel.  I removed all
compiler options during this make world.

I recompiled the kernel with PROCFS back in, rebooted and still the same
error:

dogbert# w
 9:30AM  up 9 mins, 1 user, load averages: 0.00, 0.01, 0.00
USER             TTY      FROM              LOGIN@  IDLE WHAT
w: proc size mismatch (31320 total, 1056 chunks): Undefined error: 0
dogbert# ps
ps: proc size mismatch (24012 total, 1056 chunks)
dogbert# top
kvm_open: proc size mismatch (31320 total, 1056 chunks)
top: Out of memory.
dogbert# netstat -a
dogbert#
dogbert# uname -a
FreeBSD dogbert.bellnetworks.net 4.0-STABLE FreeBSD 4.0-STABLE #2: Sun Mar
26 09:19:03 EST 2000
jerry@dogbert.bellnetworks.net:/usr/src/sys/compile/GENERIC  i386
dogbert# which ps
/bin/ps
dogbert# ls -l /bin/ps
-r-xr-xr-x  1 root  wheel  203000 Mar 26 09:11 /bin/ps
dogbert#


Any ideas on how I can fix this, or what other info would be helpful to
track this down?

Thanks for the help,

Jerry
---- Original Message -----
From: Mike Ju. Volkov <mike@rbc.ru>>
> On 25-Mar-00 Jerry Bell wrote:
> > Actually, I am running a rebuilt kernel.  For sanity's sake, I just
rebuilt
> > it again, with the config -r, and run MAKEDEV all (copied from
> > /usr/src/etc).
> >
> > Anyway, I'm still having the same problem.
>
> Try to remove PROCFS from kernel config.
>
> ----------------------------------
> E-Mail: Mike Ju. Volkov <mike@rbc.ru>
> Date: 26-Mar-00
> Time: 09:51:35
>
> ICQ: 5173328
> ---
> Ban the bomb.  Save the world for conventional warfare.
>
> ----------------------------------
>
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-stable" in the body of the message
>



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


From owner-freebsd-stable  Sun Mar 26  6:42:14 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from shell.jeah.net (shell.jeah.net [216.114.10.42])
	by hub.freebsd.org (Postfix) with ESMTP
	id 0B95B37B755; Sun, 26 Mar 2000 06:42:10 -0800 (PST)
	(envelope-from chris@shell.jeah.net)
Received: (from chris@localhost)
	by shell.jeah.net (8.9.3/8.9.3) id IAA59973;
	Sun, 26 Mar 2000 08:42:10 -0600 (CST)
	(envelope-from chris)
Date: Sun, 26 Mar 2000 08:42:10 -0600 (CST)
From: Chris Byrnes <chris@shell.jeah.net>
Message-Id: <200003261442.IAA59973@shell.jeah.net>
To: freebsd-questions@freebsd.org, freebsd-stable@freebsd.org
Subject: Uh.  FreeBSD/BSDi merger.
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Is this merger something I should be scared of?


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


From owner-freebsd-stable  Sun Mar 26  6:46: 1 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from semail00.eng.us.uu.net (semail00.eng.us.uu.net [206.64.200.131])
	by hub.freebsd.org (Postfix) with ESMTP id 3483B37B8D0
	for <stable@freebsd.org>; Sun, 26 Mar 2000 06:45:57 -0800 (PST)
	(envelope-from stripes@eng.us.uu.net)
Received: from pub01.eng.us.uu.net by semail00.eng.us.uu.net with ESMTP 
	(peer crosschecked as: pub01.eng.us.uu.net [199.170.212.130])
	id JAA15990; Sun, 26 Mar 2000 09:45:52 -0500 (EST)
Received: from pub01.eng.us.uu.net by pub01.eng.us.uu.net with ESMTP 
	(peer crosschecked as: localhost.eng.us.uu.net [127.0.0.1])
	id JAA08795; Sun, 26 Mar 2000 09:45:52 -0500 (EST)
Message-Id: <JAA08795.200003261445@pub01.eng.us.uu.net>
To: usb-bsd@egroups.com, stable@freebsd.org
Subject: Re: [usb-bsd] Re: USB error messages talking to D-Link DSB-H3E under FreeBSD4.0 
In-Reply-To: Message from Doug Ambrisko <ambrisko@whistle.com> 
   of "Fri, 24 Mar 2000 17:36:09 PST." <200003250136.RAA80385@whistle.com> 
Date: Sun, 26 Mar 2000 09:45:52 -0500
From: "Josh M. Osborne" <stripes@eng.us.uu.net>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

In message <200003250136.RAA80385@whistle.com>, Doug Ambrisko writes:
[...I wrote about my non-working Kawasaki LSI baised USB ethernet 
integrated into my USB hub...]

>Works for me on OHCI (after I set the IP address)
[...]
>However, I have had trouble talking to the kue0 via a bus powered
>hub (2 different types).  I forget if it works if I power the 
>hub but I think it did.  I know it worked when I tried it on 
>an Entrega hub.  This was on UHCI.

Ah!!  AhAhAhhh!   I removed power from the hub, and the thing probed
ok as an unrecognised KLSI device and got the ugen driver.

Two little changes to the kernel's data tables later:

diff -c usbdevs.orig usbdevs ; diff -c if_kue.c.orig if_kue.c
*** usbdevs.orig        Sun Mar 26 09:27:53 2000
--- usbdevs     Sat Mar 25 13:24:57 2000
***************
*** 424,426 ****
--- 424,429 ----
  
  /* Zoom Telephonics Inc. products */
  product ZOOM 2986L            0x9700  2986L Fax modem
+ 
+ /* Kawasaki LSI products -- I think JMO */
+ product KLSI DUH3E10BT      0x0008  10BT Ethernet adapter, in the DU-H3E
*** if_kue.c.orig       Sun Mar 26 09:27:41 2000
--- if_kue.c    Sat Mar 25 13:22:25 2000
***************
*** 113,118 ****
--- 113,119 ----
        { USB_VENDOR_COREGA, USB_PRODUCT_COREGA_ETHER_USB_T },
        { USB_VENDOR_DLINK, USB_PRODUCT_DLINK_DSB650C },
        { USB_VENDOR_SMC, USB_PRODUCT_SMC_2102USB },
+       { USB_VENDOR_KLSI, USB_PRODUCT_KLSI_DUH3E10BT },
        { 0, 0 }
  };
  

And it's an anemic little ethernet!  Thank you.  

I'm going to expariment more with it's boundry conditions once I
make it no longer my primary ethernet (I had to test it somehow...)

Now, is this the right way to patch the kernel to recognise an additonal
"vender" for the device, or is there a better method?   How do I submit
these patches back to FreeBSD?


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


From owner-freebsd-stable  Sun Mar 26  6:49: 4 2000
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 6577837B897
	for <freebsd-stable@FreeBSD.ORG>; Sun, 26 Mar 2000 06:48:54 -0800 (PST)
	(envelope-from Cy.Schubert@uumail.gov.bc.ca)
Received: (from daemon@localhost)
	by point.osg.gov.bc.ca (8.8.7/8.8.8) id GAA11695;
	Sun, 26 Mar 2000 06:48:16 -0800
Received: from passer.osg.gov.bc.ca(142.32.110.29)
 via SMTP by point.osg.gov.bc.ca, id smtpda11693; Sun Mar 26 06:48:08 2000
Received: (from uucp@localhost)
	by passer.osg.gov.bc.ca (8.9.3/8.9.1) id GAA03350;
	Sun, 26 Mar 2000 06:48:07 -0800 (PST)
Received: from cwsys9.cwsent.com(10.2.2.1), claiming to be "cwsys.cwsent.com"
 via SMTP by passer9.cwsent.com, id smtpdTq3347; Sun Mar 26 06:47:15 2000
Received: (from uucp@localhost)
	by cwsys.cwsent.com (8.9.3/8.9.1) id GAA28467;
	Sun, 26 Mar 2000 06:47:13 -0800 (PST)
Message-Id: <200003261447.GAA28467@cwsys.cwsent.com>
Received: from localhost.cwsent.com(127.0.0.1), claiming to be "cwsys"
 via SMTP by localhost.cwsent.com, id smtpdP28463; Sun Mar 26 06:46:33 2000
X-Mailer: exmh version 2.1.1 10/15/1999
Reply-To: Cy Schubert - ITSD Open Systems Group <Cy.Schubert@uumail.gov.bc.ca>
From: Cy Schubert - ITSD Open Systems Group <Cy.Schubert@uumail.gov.bc.ca>
X-OS: FreeBSD 3.4-RELEASE
X-Sender: cy
To: Kenneth W Cochran <kwc@world.std.com>
Cc: Matt Loschert <loschert@servint.com>, freebsd-stable@FreeBSD.ORG
Subject: Re: Questions source-upgrading 3.4-s to 4.0-s 
In-reply-to: Your message of "Fri, 24 Mar 2000 15:44:25 EST."
             <200003242044.PAA00854@world.std.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sun, 26 Mar 2000 06:46:32 -0800
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

In message <200003242044.PAA00854@world.std.com>, Kenneth W Cochran 
writes:
> >From loschert@servint.com  Fri Mar 24 14:02:06 2000
> >Date: Fri, 24 Mar 2000 13:55:23 -0500 (EST)
> >Subject: Re: Questions source-upgrading 3.4-s to 4.0-s
> >
> >On Fri, 24 Mar 2000, Kenneth W Cochran wrote:
> >> It appears that my new 4.0 system (& the new C compiler) will be
> >> built using the 3.4-stable tools; is this ok?  I'm guessing that
> >> the "last step(s)" of this process is to re-gen (cvsup/make
> >> [build, install]world...), just as I've always done with 3.x.
> >
> >Before building your new 4.0 userland, the buildworld process
> >builds the 4.0 compiler (gcc-2.95.2) (along with other build
> >tools), and then uses that to compile everything (including
> >recompiling the compiler).
> 
> So buildworld runs in its "own complete isolated" environment?
> IOW, buildworld uses its "own" tools, etc., & doesn't need ie.
> /bin, /usr/bin ...  ??  (Except for a few basic things, like the
> compiler (with which to "bootstrap" itself?"...  :)

Actually it doesn't.  It upgrades /usr/bin/make before it begins 
building anything else.  If you're building and testing on a separate 
disk, you can copy 3.4 to that disk, chroot, and build.


Regards,                       Phone:  (250)387-8437
Cy Schubert                      Fax:  (250)387-5766
Team Leader, Sun/DEC Team   Internet:  Cy.Schubert@osg.gov.bc.ca
Open Systems Group, ITSD, ISTA
Province of BC





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


From owner-freebsd-stable  Sun Mar 26  7:10:34 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from netcom.com (netcom3.netcom.com [199.183.9.103])
	by hub.freebsd.org (Postfix) with ESMTP id 3317F37B9AE
	for <freebsd-stable@freebsd.org>; Sun, 26 Mar 2000 07:10:29 -0800 (PST)
	(envelope-from stanb@netcom.com)
Received: (from stanb@localhost)
	by netcom.com (8.9.3/8.9.3) id HAA01165
	for freebsd-stable@freebsd.org; Sun, 26 Mar 2000 07:10:23 -0800 (PST)
From: Stan Brown <stanb@netcom.com>
Message-Id: <200003261510.HAA01165@netcom.com>
Subject: 4.0 STABLE CVSUP tags?
To: freebsd-stable@freebsd.org (FreeBSD Stable List)
Date: Sun, 26 Mar 2000 10:10:23 -0500 (EST)
X-Mailer: ELM [version 2.5 PL3]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

	Building my first 4.0 machine.

	Could someone please give me the tags for 4.0 STABLE, and the ports
	tree for it. Probably need the 4.0 security set tag also.

	Also, I have a CD subscrbtion to SATBLE. Will I automaticly start
	recieveing the 4.0 branch, or do I need to call?

	Thanks.

-- 
Stan Brown     stanb@netcom.com                                    404-996-6955
Factory Automation Systems
Atlanta Ga.
-- 
Look, look, see Windows 95.  Buy, lemmings, buy!   
Pay no attention to that cliff ahead...            Henry Spencer
(c) 1998 Stan Brown.  Redistribution via the Microsoft Network is prohibited.


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


From owner-freebsd-stable  Sun Mar 26  7:11:10 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from vinyl.sentex.ca (vinyl.sentex.ca [209.112.4.14])
	by hub.freebsd.org (Postfix) with ESMTP
	id 7B52A37BEA6; Sun, 26 Mar 2000 07:11:07 -0800 (PST)
	(envelope-from mike@sentex.net)
Received: from granite.sentex.net (granite-atm.sentex.ca [209.112.4.1])
	by vinyl.sentex.ca (8.9.3/8.9.3) with ESMTP id KAA70072;
	Sun, 26 Mar 2000 10:11:05 -0500 (EST)
	(envelope-from mike@sentex.net)
Received: from chimp (ospf-mdt.sentex.net [205.211.164.81]) by granite.sentex.net (8.8.8/8.6.9) with ESMTP id KAA06691; Sun, 26 Mar 2000 10:11:04 -0500 (EST)
Message-Id: <4.2.2.20000326100950.03297008@mail.sentex.net>
X-Sender: mdtancsa@mail.sentex.net
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 
Date: Sun, 26 Mar 2000 10:11:15 -0500
To: Chris Byrnes <chris@shell.jeah.net>,
	freebsd-questions@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG
From: Mike Tancsa <mike@sentex.net>
Subject: Re: Uh.  FreeBSD/BSDi merger.
In-Reply-To: <200003261442.IAA59973@shell.jeah.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

At 08:42 AM 3/26/2000 -0600, Chris Byrnes wrote:
>Is this merger something I should be scared of?

There were several lengthy discussion on the chat mailing list and in the 
FreeBSD newsgroup.

         ---Mike




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


From owner-freebsd-stable  Sun Mar 26  7:20:18 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from vinyl.sentex.ca (vinyl.sentex.ca [209.112.4.14])
	by hub.freebsd.org (Postfix) with ESMTP id E955137B630
	for <freebsd-stable@FreeBSD.ORG>; Sun, 26 Mar 2000 07:20:13 -0800 (PST)
	(envelope-from mike@sentex.net)
Received: from granite.sentex.net (granite-atm.sentex.ca [209.112.4.1])
	by vinyl.sentex.ca (8.9.3/8.9.3) with ESMTP id KAA70318;
	Sun, 26 Mar 2000 10:20:10 -0500 (EST)
	(envelope-from mike@sentex.net)
Received: from chimp (ospf-mdt.sentex.net [205.211.164.81]) by granite.sentex.net (8.8.8/8.6.9) with ESMTP id KAA07978; Sun, 26 Mar 2000 10:20:09 -0500 (EST)
Message-Id: <4.2.2.20000326101856.033e1de8@mail.sentex.net>
X-Sender: mdtancsa@mail.sentex.net
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 
Date: Sun, 26 Mar 2000 10:20:20 -0500
To: Stan Brown <stanb@netcom.com>,
	freebsd-stable@FreeBSD.ORG (FreeBSD Stable List)
From: Mike Tancsa <mike@sentex.net>
Subject: Re: 4.0 STABLE CVSUP tags?
In-Reply-To: <200003261510.HAA01165@netcom.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

At 10:10 AM 3/26/2000 -0500, Stan Brown wrote:
>         Building my first 4.0 machine.
>
>         Could someone please give me the tags for 4.0 STABLE, and the ports
>         tree for it. Probably need the 4.0 security set tag also.


Try,

*default host=cvsup5.FreeBSD.org
*default base=/usr
*default prefix=/usr
*default release=cvs tag=RELENG_4
*default delete use-rel-suffix
src-all
cvs-crypto



Ports are the same as always.  See the examples/cvsup directory for examples.

         ---Mike



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


From owner-freebsd-stable  Sun Mar 26  7:26:50 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from majordomo2.umd.edu (majordomo2.umd.edu [128.8.10.7])
	by hub.freebsd.org (Postfix) with ESMTP
	id 1C1A537B79A; Sun, 26 Mar 2000 07:26:46 -0800 (PST)
	(envelope-from culverk@wam.umd.edu)
Received: from rac10.wam.umd.edu (root@rac10.wam.umd.edu [128.8.10.150])
	by majordomo2.umd.edu (8.9.3/8.9.3) with ESMTP id KAA19234;
	Sun, 26 Mar 2000 10:26:33 -0500 (EST)
Received: from rac10.wam.umd.edu (sendmail@localhost [127.0.0.1])
	by rac10.wam.umd.edu (8.9.3/8.9.3) with SMTP id KAA05898;
	Sun, 26 Mar 2000 10:26:34 -0500 (EST)
Received: from localhost (culverk@localhost)
	by rac10.wam.umd.edu (8.9.3/8.9.3) with ESMTP id KAA05894;
	Sun, 26 Mar 2000 10:26:34 -0500 (EST)
X-Authentication-Warning: rac10.wam.umd.edu: culverk owned process doing -bs
Date: Sun, 26 Mar 2000 10:26:34 -0500 (EST)
From: Kenneth Wayne Culver <culverk@wam.umd.edu>
To: Chris Byrnes <chris@shell.jeah.net>
Cc: freebsd-questions@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG
Subject: Re: Uh.  FreeBSD/BSDi merger.
In-Reply-To: <200003261442.IAA59973@shell.jeah.net>
Message-ID: <Pine.GSO.4.21.0003261026310.5426-100000@rac10.wam.umd.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

No


=================================================================
| Kenneth Culver              | FreeBSD: The best OS around.    |
| Unix Systems Administrator  | ICQ #: 24767726                 |
| and student at The          | AIM: muythaibxr                 |
| The University of Maryland, | Website: (Under Construction)   |
| College Park.	              | http://www.wam.umd.edu/~culverk/|
=================================================================

On Sun, 26 Mar 2000, Chris Byrnes wrote:

> Is this merger something I should be scared of?
> 
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-questions" in the body of the message
> 



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


From owner-freebsd-stable  Sun Mar 26  7:53:53 2000
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 D500037B693; Sun, 26 Mar 2000 07:53:48 -0800 (PST)
	(envelope-from des@flood.ping.uio.no)
Received: (from des@localhost)
	by flood.ping.uio.no (8.9.3/8.9.3) id RAA18788;
	Sun, 26 Mar 2000 17:53:43 +0200 (CEST)
	(envelope-from des@flood.ping.uio.no)
To: Chris Byrnes <chris@shell.jeah.net>
Cc: freebsd-questions@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG
Subject: Re: Uh.  FreeBSD/BSDi merger.
References: <200003261442.IAA59973@shell.jeah.net>
From: Dag-Erling Smorgrav <des@flood.ping.uio.no>
Date: 26 Mar 2000 17:53:43 +0200
In-Reply-To: Chris Byrnes's message of "Sun, 26 Mar 2000 08:42:10 -0600 (CST)"
Message-ID: <xzpg0tdk9rs.fsf@flood.ping.uio.no>
Lines: 9
User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.4
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Chris Byrnes <chris@shell.jeah.net> writes:
> Is this merger something I should be scared of?

FreeBSD isn't merging with anyone. Walnut Creek is. The difference is
quite significant.

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  Sun Mar 26  8: 2:19 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from isabase.philol.msu.ru (isabase.philol.msu.ru [195.208.217.73])
	by hub.freebsd.org (Postfix) with ESMTP id B64A837B52C
	for <freebsd-stable@freebsd.org>; Sun, 26 Mar 2000 08:02:09 -0800 (PST)
	(envelope-from grg@isabase.philol.msu.ru)
Received: (from grg@localhost)
	by isabase.philol.msu.ru (8.9.3/8.9.2) id UAA07719
	for freebsd-stable@freebsd.org; Sun, 26 Mar 2000 20:02:11 +0400 (MSD)
	(envelope-from grg)
Date: Sun, 26 Mar 2000 20:02:11 +0400
From: Grigoriy Strokin <grg@philol.msu.ru>
To: freebsd-stable@freebsd.org
Subject: Audio record problems in 4.0-STABLE: 1. Creative ViBRA16X
Message-ID: <20000326200211.A6863@isabase.philol.msu.ru>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0i
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

SYNOPSIS: device timeout(?) during the attempt to record anything

Hello,

I have two sound cards (only one is inserted into the box at any given
moment) and am unable to make record properly any of them.

The FreeBSD sources I use have been CVSUPed on Mar 24.

FreeBSD isabase.philol.msu.ru 4.0-STABLE FreeBSD 4.0-STABLE #2: Sat Mar 25
21:31:20 MSK 2000
grg@isabase.philol.msu.ru:/usr/src/sys/compile/ISABASE  i386

Now on the first card, it is ISA, behaves as a PnP card and is detected as
Creative ViBRA16X.

kernel config
-------------

I have the following lines in my config:

  # (also tried with the this option commented out)
  options        PNPBIOS

  # (also tried as "device pcm0 at isa? irq 5 drq 1 flags 0x15", to 
  # try forcing the card be detected as non-PnP, with the only
  # effect of appearing "pcm1" instead of "pcm0" in dmesg)
  device pcm

  # (also tried with this device commented out
  # and also "device sbc0 at isa? port 0x220 irq 5 drq 1 # flags 0x15",
  # effect of appearing "sbc1" instead of "sbc0" in dmesg)
  device sbc

boot loader config
------------------

In FreeBSD 3.4, I had the following command required
to make my SB work in /boot/kernel.conf:
   pnp 1 0 os enable port0 0x220 irq0 5 drq0 1 drq1 3
Now it seems that it is not required and considered as error,
though "man pnp" states the contrary. So I tried to boot
with and without this command.

BIOS setup
-----------

All configurations have been tried with both
"PnP OS installed: Yes" and "PnP OS installed: No",
without any effect the behaviour of the card.

dmesg
-----

The messages in dmesg related to audio and PnP are as follows:
   
1) With "options PNPBIOS":

unknown: <PNP0000> can't assign resources
unknown0: <PNP0200> at port 0-0xf,0x81-0x83,0x87,0x89-0x8b,0x8f-0x91,0xc0-0xdf drq 4 on isa0
unknown1: <PNP0100> at port 0x40-0x43 irq 0 on isa0
unknown2: <PNP0b00> at port 0x70-0x71 irq 8 on isa0
unknown: <PNP0303> can't assign resources
unknown: <PNP0800> can't assign resources
unknown3: <PNP0c04> at port 0xf0-0xff irq 13 on isa0
unknown4: <PNP0c01> at iomem 0-0x9ffff,0xfffe0000-0xffffffff,0x100000-0x3ffffff on isa0
unknown5: <PNP0c02> at iomem 0xf0000-0xf3fff,0xf4000-0xf7fff,0xf8000-0xfbfff,0xfc000-0xfffff on isa0
unknown6: <PNP0a03> at port 0x294-0x297,0x4d0-0x4d1,0xcf8-0xcff,0x480-0x48f,0x4000-0x403f,0x5000-0x501f on isa0
unknown7: <PNP0c02> at port 0x208-0x20f on isa0
unknown: <PNP0501> can't assign resources
unknown: <PNP0700> can't assign resources
unknown: <PNP0401> can't assign resources
unknown: <PNP0501> can't assign resources
sbc0: <Creative ViBRA16X> at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5 drq 1,3 on isa0
sbc0: setting card to irq 5, drq 1, 3
pcm0: <SB DSP 4.16 (ViBRA16X)> on sbc0
unknown8: <Game> at port 0x201 on isa0

2) Without "options PNPBIOS":

sbc0: <Creative ViBRA16X> at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5
drq 1,3 on isa0
sbc0: setting card to irq 5, drq 1, 3
pcm0: <SB DSP 4.16 (ViBRA16X)> on sbc0
unknown0: <Game> at port 0x201 on isa0


Problems
---------

Playback of .au, .wav, .mp3 works as expected.

However, when I attempt to record an .au or .wav
with the 'rec' program from sox, e. g.:
  grg@isabase.1:~$ rec a.au
  Send break (control-c) to end recording

I cant interrupt the recording with pressing
control-c one or several times: the "^C" is just printed on the terminal,
and the program won't stop.

If I press "^\" (quit), "^\" is printed, and
there is no any effect for more than 3 seconds, and only after that I see
"Quit - core dumped". The resulting file, a.au has zero length.
There are no any messages on the console except:
  /kernel: pid 7403 (sox), uid 1001: exited on signal 3 (core dumped)
It looks like device timeout for me, but whatever it is,
I can't record anything.

I tried to record 16-bit sound instead of default 8-bit,
with the same effect.

Also, I try to record using the 'lrecord' command
from ESPS/waves+, a commercial software equipment
compiled for Linux (lrecord states for Linux-record). 
lrecord worked for me
on FreeBSD 3.4. Now I get the following:
  grg@isabase.1:~$ lrecord a.sd
  [then I press ^C]

  Problems writing samples at sample number 0
  No samples collected!

Now what?

History
--------

Both 'rec' and 'lrecord' worked for me for 8-bit and 16-bit
8 KHz sound on FreeBSD 3.4-STABLE.
However, there were a strange message on the console
just after starting rec or lrecord that looked something like:
   drq0 and drq1 swap: now 3 and 1
and just after finishing the recording:
   drq0 and drq1 swap: now 1 and 3
I have no idea if this is a problem at all,
but on other machines with other sound cards
there is no such a message.

But also, there WAS another problem on FreeBSD 3.4-STABLE:
If I recorded 16 KHz sound instead of 8 KHz,
it seemed to work OK, and the sound was actually recorded.
However, if I used tools for drawing dynamic spectrograms
of the sound (such as sound processing tools from ESPS)
they showed no spectral information above 4 KHz.
This is the evidence of that the hardware actually
recorded the audio at the frequency rate of 8KHz,
though software thought it put the hardware in
16KHz mode (when you make a spectrum, for a 8KHz
sound, you only can see spectral information
up to 4Khz, for 16KHz sound you can see it up to 8KHz,
and so on).

If I recorded a 16KHz sound on another machine
copied it to my machine and visualized using the same
tools, I could see spectral information up to 
8KHz, as expected.

So the was apparently pcm driver problem in FreeBSD 3.4-STABLE.
I have installed 4-STABLE that early in hope that
new pcm driver would work better, and as result
I cannot record audio at all.

What now?
Please help.


P.S. I don't know the exact model name of this SB16 Vibra:
it was preinstalled in that newly bought machine and the only
documentation for the SB was a four-page paper with intructions
on how to install Windows drivers for it.

-- 
=== Grigoriy Strokin, Lomonosov University (MGU), Moscow ===
=== contact info: http://isabase.philol.msu.ru/~grg/     ===


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


From owner-freebsd-stable  Sun Mar 26  8:13: 7 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from isabase.philol.msu.ru (isabase.philol.msu.ru [195.208.217.73])
	by hub.freebsd.org (Postfix) with ESMTP id 8EC1B37B897
	for <freebsd-stable@freebsd.org>; Sun, 26 Mar 2000 08:13:03 -0800 (PST)
	(envelope-from grg@isabase.philol.msu.ru)
Received: (from grg@localhost)
	by isabase.philol.msu.ru (8.9.3/8.9.2) id UAA07778
	for freebsd-stable@freebsd.org; Sun, 26 Mar 2000 20:13:11 +0400 (MSD)
	(envelope-from grg)
Date: Sun, 26 Mar 2000 20:13:11 +0400
From: Grigoriy Strokin <grg@philol.msu.ru>
To: freebsd-stable@freebsd.org
Subject: Re: Audio record problems in 4.0-STABLE: 1. Creative ViBRA16X
Message-ID: <20000326201311.B6863@isabase.philol.msu.ru>
References: <20000326200211.A6863@isabase.philol.msu.ru>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0i
In-Reply-To: <20000326200211.A6863@isabase.philol.msu.ru>; from grg@philol.msu.ru on Sun, Mar 26, 2000 at 08:02:11PM +0400
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Oops. I forgot an important detail in "History".

> Problems
> ---------
> 
> Playback of .au, .wav, .mp3 works as expected.
> 

Yes, it worked as expected in most cases.
However, SOMETIMES, during a playback of 
mp3, the music was changed into a white noise
at some moment (sounds like a random
non-audio binary file was send to the sound card).
To get rid of the noise, I suspended mpg123,
waited for the sound to stop and typed 'fg'
to continue. The music was being heard again.


-- 
=== Grigoriy Strokin, Lomonosov University (MGU), Moscow ===
=== contact info: http://isabase.philol.msu.ru/~grg/     ===


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


From owner-freebsd-stable  Sun Mar 26  8:14:45 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from isabase.philol.msu.ru (isabase.philol.msu.ru [195.208.217.73])
	by hub.freebsd.org (Postfix) with ESMTP id 2207937B918
	for <freebsd-stable@freebsd.org>; Sun, 26 Mar 2000 08:14:42 -0800 (PST)
	(envelope-from grg@isabase.philol.msu.ru)
Received: (from grg@localhost)
	by isabase.philol.msu.ru (8.9.3/8.9.2) id UAA07799
	for freebsd-stable@freebsd.org; Sun, 26 Mar 2000 20:14:48 +0400 (MSD)
	(envelope-from grg)
Date: Sun, 26 Mar 2000 20:14:48 +0400
From: Grigoriy Strokin <grg@philol.msu.ru>
To: freebsd-stable@freebsd.org
Subject: Re: Audio record problems in 4.0-STABLE: 1. Creative ViBRA16X
Message-ID: <20000326201448.C6863@isabase.philol.msu.ru>
References: <20000326200211.A6863@isabase.philol.msu.ru> <20000326201311.B6863@isabase.philol.msu.ru>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0i
In-Reply-To: <20000326201311.B6863@isabase.philol.msu.ru>; from grg@philol.msu.ru on Sun, Mar 26, 2000 at 08:13:11PM +0400
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Another addition.

On Sun, Mar 26, 2000 at 08:13:11PM +0400, Grigoriy Strokin wrote:
> Oops. I forgot an important detail in "History".
> 
> > Problems
> > ---------
> > 
> > Playback of .au, .wav, .mp3 works as expected.
> > 
> 
> Yes, it worked as expected in most cases.
> However, SOMETIMES, during a playback of 
> mp3, the music was changed into a white noise
> at some moment (sounds like a random
> non-audio binary file was send to the sound card).
> To get rid of the noise, I suspended mpg123,
> waited for the sound to stop and typed 'fg'
> to continue. The music was being heard again.
> 

This was also the case in 3.4-STABLE.



-- 
=== Grigoriy Strokin, Lomonosov University (MGU), Moscow ===
=== contact info: http://isabase.philol.msu.ru/~grg/     ===


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


From owner-freebsd-stable  Sun Mar 26  8:21:17 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from smtp13.bellglobal.com (smtp13.bellglobal.com [204.101.251.52])
	by hub.freebsd.org (Postfix) with ESMTP id 40B9F37B9BC
	for <freebsd-stable@freebsd.org>; Sun, 26 Mar 2000 08:21:13 -0800 (PST)
	(envelope-from bjf@shogun.apt.samurai.com)
Received: from shogun.apt.samurai.com (HSE-Toronto-ppp89584.sympatico.ca [216.209.35.73])
	by smtp13.bellglobal.com (8.8.5/8.8.5) with ESMTP id LAA26520
	for <freebsd-stable@freebsd.org>; Sun, 26 Mar 2000 11:24:24 -0500 (EST)
Received: by shogun.apt.samurai.com (Postfix, from userid 1000)
	id 8F086204; Sun, 26 Mar 2000 11:21:10 -0500 (EST)
Date: Sun, 26 Mar 2000 11:21:10 -0500
From: bjf <bjf@samurai.com>
To: freebsd-stable@freebsd.org
Subject: CURRENT->STABLE - make world dies
Message-ID: <20000326112110.D7981@samurai.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.1.4i
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Howdy.  I have a box which is running 4.0-CURRENT from end of January.  Last
night I cvsup'ed src-all to 4.0-STABLE and tried a 'make world'.  It dies
with the following:

===============
===> lib/libcrypt
install -c -o root -g wheel -m 444   libscrypt.a /usr/lib
install -c -o root -g wheel -m 444   libscrypt_p.a /usr/lib
install -c -s -o root -g wheel -m 444   -fschg  libscrypt.so.2 /usr/lib
/usr/libexec/ld-elf.so.1: install: Undefined symbol "setflags"
*** Error code 1

Stop in /usr/src/lib/libcrypt.
*** Error code 1

Stop in /usr/src/lib.
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.
===============

It would appear that /usr/bin/install either wasn't correctly created last
time I did a make world, or else it's arguments have changed slightly since
then.  However, there is no /usr/src/usr.bin/install, and there's no
/usr/src/gnu/usr.bin/install, so I'm not quite sure where to find install
to rebuild it separately.  Looking for a directory called 'install' with
find didn't prove productive (there are a couple, but none seemed to be the
right one).

I updated a 4.0-RELEASE machine to 4.0-STABLE last night with cvsup and make
world and it went without a hitch.

Any suggestions would be appreciated.

Thanks,

Bryan

-- 
Bryan Fullerton                http://bryanfullerton.com/
Core Competency
Samurai Consulting
Can you feel the Ohmu call?


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


From owner-freebsd-stable  Sun Mar 26  8:24:37 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13])
	by hub.freebsd.org (Postfix) with ESMTP id DDF7737B980
	for <freebsd-stable@freebsd.org>; Sun, 26 Mar 2000 08:24:22 -0800 (PST)
	(envelope-from ben@scientia.demon.co.uk)
Received: from strontium.scientia.demon.co.uk ([192.168.91.36] ident=exim)
	by scientia.demon.co.uk with esmtp (Exim 3.12 #1)
	id 12ZF5h-000Aae-00; Sun, 26 Mar 2000 16:36:37 +0100
Received: (from ben) by strontium.scientia.demon.co.uk (Exim 3.12 #7)
	id 12ZF5h-000OMd-00; Sun, 26 Mar 2000 16:36:37 +0100
Date: Sun, 26 Mar 2000 16:36:37 +0100
From: Ben Smithurst <ben@scientia.demon.co.uk>
To: Stan Brown <stanb@netcom.com>
Cc: FreeBSD Stable List <freebsd-stable@freebsd.org>
Subject: Re: 4.0 STABLE CVSUP tags?
Message-ID: <20000326163637.P86036@strontium.scientia.demon.co.uk>
References: <200003261510.HAA01165@netcom.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0i
In-Reply-To: <200003261510.HAA01165@netcom.com>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Stan Brown wrote:

> 	Building my first 4.0 machine.
> 
> 	Could someone please give me the tags for 4.0 STABLE, and the ports
> 	tree for it. Probably need the 4.0 security set tag also.

for cvsup,

src-all tag=RELENG_4
cvs-crypto tag=RELENG_4
ports-all tag=.

The ports tree *never* uses a tag other than ".", it's not branched in
the way the source tree is.

-- 
Ben Smithurst / ben@scientia.demon.co.uk / PGP: 0x99392F7D


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


From owner-freebsd-stable  Sun Mar 26  8:24:40 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13])
	by hub.freebsd.org (Postfix) with ESMTP id 3CDDA37B97D
	for <freebsd-stable@freebsd.org>; Sun, 26 Mar 2000 08:24:36 -0800 (PST)
	(envelope-from ben@scientia.demon.co.uk)
Received: from strontium.scientia.demon.co.uk ([192.168.91.36] ident=exim)
	by scientia.demon.co.uk with esmtp (Exim 3.12 #1)
	id 12ZF45-000AaU-00; Sun, 26 Mar 2000 16:34:57 +0100
Received: (from ben) by strontium.scientia.demon.co.uk (Exim 3.12 #7)
	id 12ZF45-000Ngs-00; Sun, 26 Mar 2000 16:34:57 +0100
Date: Sun, 26 Mar 2000 16:34:57 +0100
From: Ben Smithurst <ben@scientia.demon.co.uk>
To: Jerry Bell <jerry@bellnetworks.net>
Cc: freebsd-stable@FreeBSD.ORG
Subject: Re: ps, w, top and netstat problem
Message-ID: <20000326163457.O86036@strontium.scientia.demon.co.uk>
References: <XFMail.000326095323.mike@rbc.ru> <015801bf96cc$14f8fce0$f7bbb1d0@netrex.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0i
In-Reply-To: <015801bf96cc$14f8fce0$f7bbb1d0@netrex.com>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Jerry Bell wrote:

> I just tried removing the 'options PROCFS' from the kernel config and
> recompiled.  After a reboot, I get the same thing.
> 
> I ran another make buildworld and make installworld, so the ps, w, top and
> netstat binaries are _definately_ in sync with the kernel.  I removed all
> compiler options during this make world.

ok, I hate to ask questions which imply you're stupid, but you *did* do
'make install' in the kernel compile directory, didn't you? It's just
that you've never explicitly mentioned that, and I don't know what else
would cause these problems.

-- 
Ben Smithurst / ben@scientia.demon.co.uk / PGP: 0x99392F7D


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


From owner-freebsd-stable  Sun Mar 26  8:26:55 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from wally.bellnetworks.net (www.bellnetworks.net [216.214.153.70])
	by hub.freebsd.org (Postfix) with ESMTP id 1635E37B6A6
	for <freebsd-stable@FreeBSD.ORG>; Sun, 26 Mar 2000 08:26:52 -0800 (PST)
	(envelope-from jerry@bellnetworks.net)
Received: from itbell (dhcp-247.bellnetworks.net [208.177.187.247])
	by wally.bellnetworks.net (8.9.3/8.9.3) with SMTP id LAA56410;
	Sun, 26 Mar 2000 11:26:43 -0500 (EST)
	(envelope-from jerry@bellnetworks.net)
Message-ID: <01b001bf96db$55ee0650$f7bbb1d0@netrex.com>
From: "Jerry Bell" <jerry@bellnetworks.net>
To: "Ben Smithurst" <ben@scientia.demon.co.uk>
Cc: <freebsd-stable@FreeBSD.ORG>
References: <XFMail.000326095323.mike@rbc.ru> <015801bf96cc$14f8fce0$f7bbb1d0@netrex.com> <20000326163457.O86036@strontium.scientia.demon.co.uk>
Subject: Re: ps, w, top and netstat problem
Date: Sat, 25 Mar 2000 23:25:37 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Yep, I did.  Sorry for not mentioning that (I did include the uname -a,
though).  I'm kind of at a loss as well.

Jerry

----- Original Message -----
From: Ben Smithurst <ben@scientia.demon.co.uk>
To: Jerry Bell <jerry@bellnetworks.net>
Cc: <freebsd-stable@FreeBSD.ORG>
Sent: Sunday, March 26, 2000 10:34 AM
Subject: Re: ps, w, top and netstat problem


> Jerry Bell wrote:
>
> > I just tried removing the 'options PROCFS' from the kernel config and
> > recompiled.  After a reboot, I get the same thing.
> >
> > I ran another make buildworld and make installworld, so the ps, w, top
and
> > netstat binaries are _definately_ in sync with the kernel.  I removed
all
> > compiler options during this make world.
>
> ok, I hate to ask questions which imply you're stupid, but you *did* do
> 'make install' in the kernel compile directory, didn't you? It's just
> that you've never explicitly mentioned that, and I don't know what else
> would cause these problems.
>
> --
> Ben Smithurst / ben@scientia.demon.co.uk / PGP: 0x99392F7D
>



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


From owner-freebsd-stable  Sun Mar 26  8:48:17 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from merlin.prod.itd.earthlink.net (merlin.prod.itd.earthlink.net [207.217.120.156])
	by hub.freebsd.org (Postfix) with ESMTP id 1DFFA37B9A2
	for <freebsd-stable@freebsd.org>; Sun, 26 Mar 2000 08:48:13 -0800 (PST)
	(envelope-from eogren@earthlink.net)
Received: from red.ogren.house (ip229.cambridge2.ma.pub-ip.psi.net [38.32.112.229])
	by merlin.prod.itd.earthlink.net (8.9.3/8.9.3) with ESMTP id IAA04245;
	Sun, 26 Mar 2000 08:48:10 -0800 (PST)
Received: (from eogren@localhost)
	by red.ogren.house (8.9.3/8.9.3/Debian/GNU) id LAA13010;
	Sun, 26 Mar 2000 11:42:34 -0500
Date: Sun, 26 Mar 2000 11:42:34 -0500
From: Eric Ogren <eogren@earthlink.net>
To: bjf <bjf@samurai.com>
Cc: freebsd-stable@freebsd.org
Subject: Re: CURRENT->STABLE - make world dies
Message-ID: <20000326114234.A12771@earthlink.net>
References: <20000326112110.D7981@samurai.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.3i
In-Reply-To: <20000326112110.D7981@samurai.com>; from bjf on Sun, Mar 26, 2000 at 11:21:10AM -0500
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Sun, Mar 26, 2000 at 11:21:10AM -0500, bjf wrote:
> Howdy.  I have a box which is running 4.0-CURRENT from end of January.  Last
> night I cvsup'ed src-all to 4.0-STABLE and tried a 'make world'.  It dies
> with the following:
> 
> ===============
> ===> lib/libcrypt
> install -c -o root -g wheel -m 444   libscrypt.a /usr/lib
> install -c -o root -g wheel -m 444   libscrypt_p.a /usr/lib
> install -c -s -o root -g wheel -m 444   -fschg  libscrypt.so.2 /usr/lib
> /usr/libexec/ld-elf.so.1: install: Undefined symbol "setflags"
> *** Error code 1
> 
> Stop in /usr/src/lib/libcrypt.
> *** Error code 1
> 
> Stop in /usr/src/lib.
> *** Error code 1
> 
> Stop in /usr/src.
> *** Error code 1
> 
> Stop in /usr/src.
> *** Error code 1
> 
> Stop in /usr/src.
> *** Error code 1
> 
> Stop in /usr/src.
> ===============
> 
> It would appear that /usr/bin/install either wasn't correctly created last
> time I did a make world, or else it's arguments have changed slightly since
> then.  However, there is no /usr/src/usr.bin/install, and there's no
> /usr/src/gnu/usr.bin/install, so I'm not quite sure where to find install
> to rebuild it separately.  Looking for a directory called 'install' with
> find didn't prove productive (there are a couple, but none seemed to be the
> right one).
>

 The install src code is actually in /usr/src/usr.bin/xinstall, if I
remember correctly (I'm not at a FreeBSD box right now). Running 'make install'
in that directory should fix your problem.

Eric 


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


From owner-freebsd-stable  Sun Mar 26  9:22:29 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13])
	by hub.freebsd.org (Postfix) with ESMTP id 3529E37BA00
	for <freebsd-stable@freebsd.org>; Sun, 26 Mar 2000 09:22:22 -0800 (PST)
	(envelope-from ben@scientia.demon.co.uk)
Received: from strontium.scientia.demon.co.uk ([192.168.91.36] ident=exim)
	by scientia.demon.co.uk with esmtp (Exim 3.12 #1)
	id 12ZFvd-000Afr-00; Sun, 26 Mar 2000 17:30:17 +0100
Received: (from ben) by strontium.scientia.demon.co.uk (Exim 3.12 #7)
	id 12ZFvd-000DCJ-00; Sun, 26 Mar 2000 17:30:17 +0100
Date: Sun, 26 Mar 2000 17:30:17 +0100
From: Ben Smithurst <ben@scientia.demon.co.uk>
To: bjf <bjf@samurai.com>
Cc: freebsd-stable@freebsd.org
Subject: Re: CURRENT->STABLE - make world dies
Message-ID: <20000326173017.Q86036@strontium.scientia.demon.co.uk>
References: <20000326112110.D7981@samurai.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0i
In-Reply-To: <20000326112110.D7981@samurai.com>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

bjf wrote:

> It would appear that /usr/bin/install either wasn't correctly created last
> time I did a make world, or else it's arguments have changed slightly since
> then.  However, there is no /usr/src/usr.bin/install, and there's no
> /usr/src/gnu/usr.bin/install, so I'm not quite sure where to find install

usr.bin/xinstall

It can't be called "install" because that would confuse "make install",
or something.

-- 
Ben Smithurst / ben@scientia.demon.co.uk / PGP: 0x99392F7D


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


From owner-freebsd-stable  Sun Mar 26  9:53:22 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from tinker.exit.com (exit-gw.power.net [207.151.46.196])
	by hub.freebsd.org (Postfix) with ESMTP id EC68637B693
	for <freebsd-stable@FreeBSD.ORG>; Sun, 26 Mar 2000 09:53:15 -0800 (PST)
	(envelope-from frank@exit.com)
Received: from realtime.exit.com (realtime.exit.com [206.223.0.5])
	by tinker.exit.com (8.9.3/8.9.3) with ESMTP id JAA42347;
	Sun, 26 Mar 2000 09:53:14 -0800 (PST)
	(envelope-from frank@exit.com)
Received: (from frank@localhost)
	by realtime.exit.com (8.9.3/8.9.3) id JAA42282;
	Sun, 26 Mar 2000 09:53:14 -0800 (PST)
	(envelope-from frank)
From: Frank Mayhar <frank@exit.com>
Message-Id: <200003261753.JAA42282@realtime.exit.com>
Subject: Re: Audio record problems in 4.0-STABLE: 1. Creative ViBRA16X
In-Reply-To: <20000326201311.B6863@isabase.philol.msu.ru> from Grigoriy Strokin
 at "Mar 26, 2000 08:13:11 pm"
To: Grigoriy Strokin <grg@philol.msu.ru>
Date: Sun, 26 Mar 2000 09:53:14 -0800 (PST)
Cc: freebsd-stable@FreeBSD.ORG
Reply-To: frank@exit.com
Organization: Exit Consulting
X-Copyright0: Copyright 2000 Frank Mayhar.  All Rights Reserved.
X-Copyright1: Permission granted for electronic reproduction as Usenet News or email only.
X-Mailer: ELM [version 2.4ME+ PL68 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Grigoriy Strokin wrote:
> Oops. I forgot an important detail in "History".
> > Problems
> > ---------
> > 
> > Playback of .au, .wav, .mp3 works as expected.
> > 
> Yes, it worked as expected in most cases.
> However, SOMETIMES, during a playback of 
> mp3, the music was changed into a white noise
> at some moment (sounds like a random
> non-audio binary file was send to the sound card).
> To get rid of the noise, I suspended mpg123,
> waited for the sound to stop and typed 'fg'
> to continue. The music was being heard again.

I see (well, hear) this exact problem using a Televideo Soundblaster clone,
on 3.4-stable.  Once in a while it will just start emitting white noise, like
the byte-swabbing got messed up somehow, usually at the beginning of a
playback.  I suspect it's a bug in mpg123, but it might be the sound driver
(less likely, though, if you're seeing it in 4.0).

The sound card probes as:

Probing for PnP devices:
CSN 1 Vendor ID: OPT0931 [0x3109143e] Serial 0xffffffff Comp ID: @@@0000 [0x00000000]
mss_attach <OPTi931>1 at 0x530 irq 10 dma 1:6 flags 0x16
pcm1 (OPTi931 <OPTi931> sn 0xffffffff) at 0x530-0x537 irq 10 drq 1 flags 0x16 on isa

With a userconfig_script of
pnp 1 1 os enable port0 0x534 port2 0x220 port3 0xe0d irq0 10 drq0 1 drq1 6

Otherwise the card works fine.
-- 
Frank Mayhar frank@exit.com	http://www.exit.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 26 11:21: 0 2000
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 A35C737B8E2; Sun, 26 Mar 2000 11:20:53 -0800 (PST)
	(envelope-from jkh@zippy.cdrom.com)
Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1])
	by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id LAA01856;
	Sun, 26 Mar 2000 11:22:01 -0800 (PST)
	(envelope-from jkh@zippy.cdrom.com)
To: Chris Byrnes <chris@shell.jeah.net>
Cc: freebsd-questions@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG
Subject: Re: Uh. FreeBSD/BSDi merger. 
In-reply-to: Your message of "Sun, 26 Mar 2000 08:42:10 CST."
             <200003261442.IAA59973@shell.jeah.net> 
Date: Sun, 26 Mar 2000 11:22:01 -0800
Message-ID: <1853.954098521@zippy.cdrom.com>
From: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> Is this merger something I should be scared of?

No.


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


From owner-freebsd-stable  Sun Mar 26 11:43:25 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from ns.altadena.net (ns.altadena.net [206.126.144.2])
	by hub.freebsd.org (Postfix) with ESMTP id C35B437B505
	for <stable@freebsd.org>; Sun, 26 Mar 2000 11:43:20 -0800 (PST)
	(envelope-from pete@ns.altadena.net)
Received: (from pete@localhost)
	by ns.altadena.net (8.9.3/8.8.8) id LAA61959
	for stable@freebsd.org; Sun, 26 Mar 2000 11:43:20 -0800 (PST)
	(envelope-from pete)
From: Pete Carah <pete@ns.altadena.net>
Message-Id: <200003261943.LAA61959@ns.altadena.net>
Subject: cvsup this morning, secure rolls over
To: stable@freebsd.org
Date: Sun, 26 Mar 2000 11:43:20 -0800 (PST)
X-Mailer: ELM [version 2.4ME+ PL61 (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

RELENG_4 CVSUP as of a few hours ago (3/26 about 9AM PST):
----------------------------------------------------------
Don't know if this is related to the RSA intl vs RSAREF stuff but it offhand
looks like it could be.

I also have a -current making on another system; don't know if it does 
this too or not since it hasn't gotten that far yet.

I had removed /usr/src/crypto, /usr/src/kerberosIV and /usr/src/kerberos5
to fix a problem I had with both -DMAKE_KERBEROS4 and -DMAKE_KERBEROS5 dying
on libkafs5, so all were clean.  I may or man not have removed secure.

Is the current way to get everything with just src-all and cvs-crypto
like it was?

-- Pete
--------------------------------------------------------------------------

===> secure/usr.bin/ssh-keygen
cc -O -pipe   -I/usr/obj/usr/src/i386/usr/include -c /usr/src/secure/usr.bin/ssh
-keygen/../../../crypto/openssh/ssh-keygen.c
cc -O -pipe   -I/usr/obj/usr/src/i386/usr/include -c /usr/src/secure/usr.bin/ssh
-keygen/../../../crypto/openssh/log-client.c
cc -O -pipe   -I/usr/obj/usr/src/i386/usr/include  -o ssh-keygen ssh-keygen.o lo
g-client.o  -L/usr/obj/usr/src/secure/usr.bin/ssh-keygen/../../lib/libssh -lssh
-lcrypto -lcrypt -lutil -lz
/usr/obj/usr/src/secure/usr.bin/ssh-keygen/../../lib/libssh/libssh.a(hostfile.o)
: In function `hostfile_read_key':
hostfile.o(.text+0x60): undefined reference to `key_read'
/usr/obj/usr/src/secure/usr.bin/ssh-keygen/../../lib/libssh/libssh.a(hostfile.o)
: In function `auth_rsa_read_key':
hostfile.o(.text+0xa9): undefined reference to `key_new'
hostfile.o(.text+0xeb): undefined reference to `key_free'
/usr/obj/usr/src/secure/usr.bin/ssh-keygen/../../lib/libssh/libssh.a(hostfile.o)
: In function `check_host_in_hostfile':
hostfile.o(.text+0x2d8): undefined reference to `key_equal'
/usr/obj/usr/src/secure/usr.bin/ssh-keygen/../../lib/libssh/libssh.a(hostfile.o)
: In function `add_host_to_hostfile':
hostfile.o(.text+0x37f): undefined reference to `key_write'
*** Error code 1

Stop in /usr/src/secure/usr.bin/ssh-keygen.
*** Error code 1

Stop in /usr/src/secure/usr.bin.
*** Error code 1

Stop in /usr/src/secure.
*** Error Code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.



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


From owner-freebsd-stable  Sun Mar 26 11:55:22 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from ants.pocketscience.com (gateway1.pocketscience.com [209.24.64.3])
	by hub.freebsd.org (Postfix) with ESMTP
	id 2633637BA82; Sun, 26 Mar 2000 11:55:18 -0800 (PST)
	(envelope-from brian@pocketscience.com)
Received: from pocketscience.com (southpark.i.pocketscience.com [10.10.4.2]) by ants.pocketscience.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2448.0)
	id HGNVL6ZT; Sun, 26 Mar 2000 11:55:17 -0800
Message-ID: <38DE6B27.5B6FA71F@pocketscience.com>
Date: Sun, 26 Mar 2000 11:55:19 -0800
From: Brian Nelson <brian@pocketscience.com>
Organization: PocketScience, Inc
X-Mailer: Mozilla 4.72 [en] (X11; U; FreeBSD 4.0-STABLE i386)
X-Accept-Language: en,pdf
MIME-Version: 1.0
To: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Cc: Chris Byrnes <chris@shell.jeah.net>,
	freebsd-questions@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG
Subject: Re: Uh. FreeBSD/BSDi merger.
References: <1853.954098521@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

"Jordan K. Hubbard" wrote:
> 
> > Is this merger something I should be scared of?
> 
> No.
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-stable" in the body of the message

Well, of COURSE jkh is going to say no.  =P

But from what I have read, and my beliefs about the philosophy behind
BSD, there is little you should be scared of when it comes to BSD...  if
BSDi/WC start doing "the wrong thing" (which is very unlikely), then
someone will branch off and create ReallyFreeBSD(tm) and we'll all be
happy again.


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


From owner-freebsd-stable  Sun Mar 26 11:59: 6 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from wally.bellnetworks.net (www.bellnetworks.net [216.214.153.70])
	by hub.freebsd.org (Postfix) with ESMTP id 4B21337BA3B
	for <freebsd-stable@FreeBSD.ORG>; Sun, 26 Mar 2000 11:58:58 -0800 (PST)
	(envelope-from jerry@bellnetworks.net)
Received: from itbell (dhcp-247.bellnetworks.net [208.177.187.247])
	by wally.bellnetworks.net (8.9.3/8.9.3) with SMTP id OAA76292;
	Sun, 26 Mar 2000 14:56:49 -0500 (EST)
	(envelope-from jerry@bellnetworks.net)
Message-ID: <01de01bf96f8$acacba00$f7bbb1d0@netrex.com>
From: "Jerry Bell" <jerry@bellnetworks.net>
To: "Ted Spradley" <tsprad@set.spradley.org>
Cc: "Ben Smithurst" <ben@scientia.demon.co.uk>,
	<freebsd-stable@FreeBSD.ORG>
References: <200003261727.LAA54114@set.spradley.org>
Subject: Re: ps, w, top and netstat problem 
Date: Sun, 26 Mar 2000 02:55:38 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

dogbert# /bin/ps
ps: proc size mismatch (26100 total, 1056 chunks)

I'm kind of at a loss.  The binaries I'm running are definately the new
ones, and I'm definately running the new kernel.

Any thoughts?

Jerry

----- Original Message -----
From: Ted Spradley <tsprad@set.spradley.org>
To: Jerry Bell <jerry@bellnetworks.net>
Cc: Ben Smithurst <ben@scientia.demon.co.uk>; <freebsd-stable@FreeBSD.ORG>
Sent: Sunday, March 26, 2000 12:27 PM
Subject: Re: ps, w, top and netstat problem


> > Yep, I did.  Sorry for not mentioning that (I did include the uname -a,
> > though).  I'm kind of at a loss as well.
>
> One more thing:  Are you sure that the ps and top, etc. you're running
> are the new ones you built and installed?  Might there be an old version
> somewhere else in your $PATH?  Try "which ps", or "/bin/ps".
>
> >
> > Jerry
> >
> > ----- Original Message -----
> > From: Ben Smithurst <ben@scientia.demon.co.uk>
> > To: Jerry Bell <jerry@bellnetworks.net>
> > Cc: <freebsd-stable@FreeBSD.ORG>
> > Sent: Sunday, March 26, 2000 10:34 AM
> > Subject: Re: ps, w, top and netstat problem
> >
> >
> > > Jerry Bell wrote:
> > >
> > > > I just tried removing the 'options PROCFS' from the kernel config
and
> > > > recompiled.  After a reboot, I get the same thing.
> > > >
> > > > I ran another make buildworld and make installworld, so the ps, w,
top
> > and
> > > > netstat binaries are _definately_ in sync with the kernel.  I
removed
> > all
> > > > compiler options during this make world.
> > >
> > > ok, I hate to ask questions which imply you're stupid, but you *did*
do
> > > 'make install' in the kernel compile directory, didn't you? It's just
> > > that you've never explicitly mentioned that, and I don't know what
else
> > > would cause these problems.
> > >
> > > --
> > > Ben Smithurst / ben@scientia.demon.co.uk / PGP: 0x99392F7D




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


From owner-freebsd-stable  Sun Mar 26 12:18: 9 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from ns.altadena.net (ns.altadena.net [206.126.144.2])
	by hub.freebsd.org (Postfix) with ESMTP id 5586137B900
	for <stable@freebsd.org>; Sun, 26 Mar 2000 12:18:07 -0800 (PST)
	(envelope-from pete@ns.altadena.net)
Received: (from pete@localhost)
	by ns.altadena.net (8.9.3/8.8.8) id MAA63044
	for stable@freebsd.org; Sun, 26 Mar 2000 12:18:06 -0800 (PST)
	(envelope-from pete)
From: Pete Carah <pete@ns.altadena.net>
Message-Id: <200003262018.MAA63044@ns.altadena.net>
Subject: oops
To: stable@freebsd.org
Date: Sun, 26 Mar 2000 12:18:06 -0800 (PST)
X-Mailer: ELM [version 2.4ME+ PL61 (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

Pardon my last; the stable-supfile had tag=. for some strange reason
so the complaint about ssh-keygen should belong to current...  (still
a complaint, though :-)

That has been fixed along with another remove of src/crypto, secure, 
kerberos*, so we'll see if the problem applies to stable too.

-- Pete


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


From owner-freebsd-stable  Sun Mar 26 12:29:56 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from smtp11.bellglobal.com (smtp11.bellglobal.com [204.101.251.53])
	by hub.freebsd.org (Postfix) with ESMTP id B561237B9B9
	for <freebsd-stable@freebsd.org>; Sun, 26 Mar 2000 12:29:47 -0800 (PST)
	(envelope-from bjf@shogun.apt.samurai.com)
Received: from shogun.apt.samurai.com (HSE-Toronto-ppp89584.sympatico.ca [216.209.35.73])
	by smtp11.bellglobal.com (8.8.5/8.8.5) with ESMTP id PAA02908;
	Sun, 26 Mar 2000 15:35:17 -0500 (EST)
Received: by shogun.apt.samurai.com (Postfix, from userid 1000)
	id 141FA204; Sun, 26 Mar 2000 15:29:41 -0500 (EST)
Date: Sun, 26 Mar 2000 15:29:41 -0500
From: bjf <bjf@samurai.com>
To: Ben Smithurst <ben@scientia.demon.co.uk>
Cc: freebsd-stable@freebsd.org, eogren@earthlink.net
Subject: Re: CURRENT->STABLE - make world dies
Message-ID: <20000326152941.A11539@samurai.com>
References: <20000326112110.D7981@samurai.com> <20000326173017.Q86036@strontium.scientia.demon.co.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.1.9i
In-Reply-To: <20000326173017.Q86036@strontium.scientia.demon.co.uk>; from ben@scientia.demon.co.uk on Sun, Mar 26, 2000 at 05:30:17PM +0100
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Sun, Mar 26, 2000 at 05:30:17PM +0100, Ben Smithurst <ben@scientia.demon.co.uk> wrote:
> 
> usr.bin/xinstall
> 
> It can't be called "install" because that would confuse "make install",
> or something.

That did it - the machine is now happily running -STABLE.

Thanks!

Bryan

-- 
Bryan Fullerton                http://bryanfullerton.com/
Core Competency
Samurai Consulting
Can you feel the Ohmu call?


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


From owner-freebsd-stable  Sun Mar 26 13:45:49 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from dt051n0b.san.rr.com (dt051n0b.san.rr.com [204.210.32.11])
	by hub.freebsd.org (Postfix) with ESMTP id 8403337BA98
	for <freebsd-stable@freebsd.org>; Sun, 26 Mar 2000 13:45:46 -0800 (PST)
	(envelope-from Doug@gorean.org)
Received: from gorean.org (doug@master [10.0.0.2])
	by dt051n0b.san.rr.com (8.9.3/8.9.3) with ESMTP id NAA14548;
	Sun, 26 Mar 2000 13:45:37 -0800 (PST)
	(envelope-from Doug@gorean.org)
Message-ID: <38DE8501.849ECF20@gorean.org>
Date: Sun, 26 Mar 2000 13:45:37 -0800
From: Doug Barton <Doug@gorean.org>
Organization: Triborough Bridge & Tunnel Authority
X-Mailer: Mozilla 4.72 [en] (X11; U; FreeBSD 5.0-CURRENT-0322 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Ben Smithurst <ben@scientia.demon.co.uk>
Cc: Stan Brown <stanb@netcom.com>,
	FreeBSD Stable List <freebsd-stable@freebsd.org>
Subject: Re: 4.0 STABLE CVSUP tags?
References: <200003261510.HAA01165@netcom.com> <20000326163637.P86036@strontium.scientia.demon.co.uk>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Ben Smithurst wrote:
> 
> Stan Brown wrote:
> 
> >       Building my first 4.0 machine.
> >
> >       Could someone please give me the tags for 4.0 STABLE, and the ports
> >       tree for it. Probably need the 4.0 security set tag also.
> 
> for cvsup,
> 
> src-all tag=RELENG_4
> cvs-crypto tag=RELENG_4
> ports-all tag=.
> 
> The ports tree *never* uses a tag other than ".", it's not branched in
> the way the source tree is.

	That's not entirely true. Asami-san does tag the ports tree with a
release tag so that one could check out the exact copies of the ports
that went on a specific CD, but other than that you are correct, and for
normal, 99% of the time use tag=. is the way to go.

Doug
-- 
    "So, the cows were part of a dream that dreamed itself into
existence? Is that possible?" asked the student incredulously.
    The master simply replied, "Mu."


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


From owner-freebsd-stable  Sun Mar 26 15: 1:28 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from picalon.gun.de (picalon.gun.de [192.109.159.1])
	by hub.freebsd.org (Postfix) with ESMTP id 40DB337B824
	for <stable@freebsd.org>; Sun, 26 Mar 2000 15:01:20 -0800 (PST)
	(envelope-from andreas@klemm.gtn.com)
Received: (from uucp@localhost)
	by picalon.gun.de (8.9.3/8.9.3) id BAA29288;
	Mon, 27 Mar 2000 01:01:01 +0200 (MET DST)
>Received: (from andreas@localhost)
	by klemm.gtn.com (8.9.3/8.9.3) id BAA37325;
	Mon, 27 Mar 2000 01:00:54 +0200 (CEST)
	(envelope-from andreas)
Date: Mon, 27 Mar 2000 01:00:54 +0200
From: Andreas Klemm <andreas@klemm.gtn.com>
To: Jaye Mathisen <mrcpu@internetcds.com>
Cc: stable@freebsd.org
Subject: Re: Samba perf in the toilet with 4.0
Message-ID: <20000327010054.A37014@titan.klemm.gtn.com>
References: <Pine.BSF.4.21.0003231410060.26102-100000@schizo.cdsnet.net>
Mime-Version: 1.0
X-Mailer: Mutt 1.0.1i
In-Reply-To: <Pine.BSF.4.21.0003231410060.26102-100000@schizo.cdsnet.net>; from mrcpu@internetcds.com on Thu, Mar 23, 2000 at 02:12:31PM -0800
X-Operating-System: FreeBSD 4.0-STABLE SMP
X-Disclaimer: A free society is one where it is safe to be unpopular
Content-Type: text/plain; charset=us-ascii
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

read freebsd-net.... There was a thread concerning ACKs and such...

and the performance tuning tips in the samba sources.

Performance is really o.k.

I get ~800-900KByte/src on 10 Mbit shared network with my
notebook....

	Andreas ///

-- 
Andreas Klemm                               http://people.FreeBSD.ORG/~andreas
                                     http://www.freebsd.org/~fsmp/SMP/SMP.html
                                   powered by Symmetric MultiProcessor FreeBSD
New APSFILTER 520 and songs from our band - http://people.freebsd.org/~andreas



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


From owner-freebsd-stable  Sun Mar 26 15:26:15 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from ants.pocketscience.com (gateway1.pocketscience.com [209.24.64.3])
	by hub.freebsd.org (Postfix) with ESMTP id 3E52537BB5B
	for <freebsd-stable@FreeBSD.ORG>; Sun, 26 Mar 2000 15:26:08 -0800 (PST)
	(envelope-from brian@pocketscience.com)
Received: from pocketscience.com (southpark.i.pocketscience.com [10.10.4.2]) by ants.pocketscience.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2448.0)
	id HXB8FPB6; Sun, 26 Mar 2000 15:26:07 -0800
Message-ID: <38DE9C8F.3F9D6246@pocketscience.com>
Date: Sun, 26 Mar 2000 15:26:07 -0800
From: Brian Nelson <brian@pocketscience.com>
Organization: PocketScience, Inc
X-Mailer: Mozilla 4.72 [en] (X11; U; FreeBSD 4.0-STABLE i386)
X-Accept-Language: en, pdf
MIME-Version: 1.0
To: Ben Smithurst <ben@scientia.demon.co.uk>
Cc: Jerry Bell <jerry@bellnetworks.net>, freebsd-stable@FreeBSD.ORG
Subject: Re: ps, w, top and netstat problem
References: <XFMail.000326095323.mike@rbc.ru> <015801bf96cc$14f8fce0$f7bbb1d0@netrex.com> <20000326163457.O86036@strontium.scientia.demon.co.uk>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Could you have possibly also compiled the OS, re-CVSup'd to a NEWER
version of the source, and then compiled a kernel?

Make sure you following all the following steps:
cvsup -L 2 -g stable-supfile
cd /usr/src
make buildworld 
make installworld
cd /usr/src/sys/i386/conf
config -r MYKERNEL
cd ../../compile/MYKERNEL
make depend
make
make install

at each step, you should stop and make sure NOTHING error'd out.

reboot

Ben Smithurst wrote:
> 
> Jerry Bell wrote:
> 
> > I just tried removing the 'options PROCFS' from the kernel config and
> > recompiled.  After a reboot, I get the same thing.
> >
> > I ran another make buildworld and make installworld, so the ps, w, top and
> > netstat binaries are _definately_ in sync with the kernel.  I removed all
> > compiler options during this make world.
> 
> ok, I hate to ask questions which imply you're stupid, but you *did* do
> 'make install' in the kernel compile directory, didn't you? It's just
> that you've never explicitly mentioned that, and I don't know what else
> would cause these problems.
> 
> --
> Ben Smithurst / ben@scientia.demon.co.uk / PGP: 0x99392F7D
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-stable" in the body of the message


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


From owner-freebsd-stable  Sun Mar 26 15:28:48 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from rover.village.org (rover.village.org [204.144.255.49])
	by hub.freebsd.org (Postfix) with ESMTP
	id 7B40A37BA9D; Sun, 26 Mar 2000 15:28:34 -0800 (PST)
	(envelope-from imp@harmony.village.org)
Received: from harmony.village.org (harmony.village.org [10.0.0.6])
	by rover.village.org (8.9.3/8.9.3) with ESMTP id QAA51248;
	Sun, 26 Mar 2000 16:28:33 -0700 (MST)
	(envelope-from imp@harmony.village.org)
Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id QAA87382; Sun, 26 Mar 2000 16:28:19 -0700 (MST)
Message-Id: <200003262328.QAA87382@harmony.village.org>
To: Chris Byrnes <chris@shell.jeah.net>
Subject: Re: Uh. FreeBSD/BSDi merger. 
Cc: freebsd-questions@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG
In-reply-to: Your message of "Sun, 26 Mar 2000 08:42:10 CST."
		<200003261442.IAA59973@shell.jeah.net> 
References: <200003261442.IAA59973@shell.jeah.net>  
Date: Sun, 26 Mar 2000 16:28:19 -0700
From: Warner Losh <imp@village.org>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

In message <200003261442.IAA59973@shell.jeah.net> Chris Byrnes writes:
: Is this merger something I should be scared of?

No.

Warner


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


From owner-freebsd-stable  Sun Mar 26 15:46:24 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from netcom.com (netcom13.netcom.com [199.183.9.113])
	by hub.freebsd.org (Postfix) with ESMTP id 4327937BA7B
	for <freebsd-stable@freebsd.org>; Sun, 26 Mar 2000 15:46:22 -0800 (PST)
	(envelope-from stanb@netcom.com)
Received: (from stanb@localhost)
	by netcom.com (8.9.3/8.9.3) id PAA05302
	for freebsd-stable@freebsd.org; Sun, 26 Mar 2000 15:46:16 -0800 (PST)
From: Stan Brown <stanb@netcom.com>
Message-Id: <200003262346.PAA05302@netcom.com>
Subject: How to shutdown to single user in 4.0?
To: freebsd-stable@freebsd.org (FreeBSD Stable List)
Date: Sun, 26 Mar 2000 18:46:16 -0500 (EST)
X-Mailer: ELM [version 2.5 PL3]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

	How do I _shut down_ to single user in 4.0. I lnow i can door shutdown
	0r and catch it on the way up, and do a boot -s, but on 3.x I could do
	"shutdown now", and wind up in single user, so that I could cd /usr/src
	; make world; make kernel ; and reboot to upgrafe.

	I would like to do the same in 4.x Why did this change?

-- 
Stan Brown     stanb@netcom.com                                    404-996-6955
Factory Automation Systems
Atlanta Ga.
-- 
Look, look, see Windows 95.  Buy, lemmings, buy!   
Pay no attention to that cliff ahead...            Henry Spencer
(c) 1998 Stan Brown.  Redistribution via the Microsoft Network is prohibited.


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


From owner-freebsd-stable  Sun Mar 26 15:50:35 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from epsilon.lucida.qc.ca (epsilon.lucida.qc.ca [216.95.146.6])
	by hub.freebsd.org (Postfix) with SMTP id CDFA537BA9D
	for <freebsd-stable@freebsd.org>; Sun, 26 Mar 2000 15:50:29 -0800 (PST)
	(envelope-from matt@ARPA.MAIL.NET)
Received: (qmail 15029 invoked by uid 1000); 26 Mar 2000 23:50:25 -0000
Received: from localhost (sendmail-bs@127.0.0.1)
  by localhost with SMTP; 26 Mar 2000 23:50:25 -0000
Date: Sun, 26 Mar 2000 18:50:23 -0500 (EST)
From: Matt Heckaman <matt@ARPA.MAIL.NET>
X-Sender: matt@epsilon.lucida.qc.ca
To: Stan Brown <stanb@netcom.com>
Cc: FreeBSD Stable List <freebsd-stable@freebsd.org>
Subject: Re: How to shutdown to single user in 4.0?
In-Reply-To: <200003262346.PAA05302@netcom.com>
Message-ID: <Pine.BSF.4.21.0003261849560.15006-100000@epsilon.lucida.qc.ca>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I believe that "init 1" is what you're looking for.

Matt

On Sun, 26 Mar 2000, Stan Brown wrote:

: Date: Sun, 26 Mar 2000 18:46:16 -0500
: From: Stan Brown <stanb@netcom.com>
: To: FreeBSD Stable List <freebsd-stable@freebsd.org>
: Subject: How to shutdown to single user in 4.0?
: 
: 	How do I _shut down_ to single user in 4.0. I lnow i can door shutdown
: 	0r and catch it on the way up, and do a boot -s, but on 3.x I could do
: 	"shutdown now", and wind up in single user, so that I could cd /usr/src
: 	; make world; make kernel ; and reboot to upgrafe.
: 
: 	I would like to do the same in 4.x Why did this change?
: 
: -- 
: Stan Brown     stanb@netcom.com                                    404-996-6955
: Factory Automation Systems
: Atlanta Ga.
: -- 
: Look, look, see Windows 95.  Buy, lemmings, buy!   
: Pay no attention to that cliff ahead...            Henry Spencer
: (c) 1998 Stan Brown.  Redistribution via the Microsoft Network is prohibited.
: 
: 
: To Unsubscribe: send mail to majordomo@FreeBSD.org
: with "unsubscribe freebsd-stable" in the body of the message
: 

Matt Heckaman
matt@arpa.mail.net
http://www.lucida.qc.ca

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.1 (FreeBSD)
Comment: http://www.lucida.qc.ca/pgp

iD8DBQE43qJBdMMtMcA1U5ARAsfbAJ4qL19N9O+9W37g5ZrzDY1wGm0eGgCgu5AD
pTBnsUtJ5Kv07Z6VZHiguFY=
=82/y
-----END PGP SIGNATURE-----




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


From owner-freebsd-stable  Sun Mar 26 15:55:12 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from dt051n0b.san.rr.com (dt051n0b.san.rr.com [204.210.32.11])
	by hub.freebsd.org (Postfix) with ESMTP id 396A937BA98
	for <freebsd-stable@freebsd.org>; Sun, 26 Mar 2000 15:55:07 -0800 (PST)
	(envelope-from DougGuy@san.rr.com)
Received: from san.rr.com (doug@master [10.0.0.2])
	by dt051n0b.san.rr.com (8.9.3/8.9.3) with ESMTP id PAA15477;
	Sun, 26 Mar 2000 15:55:02 -0800 (PST)
	(envelope-from DougGuy@san.rr.com)
Message-ID: <38DEA356.BD4B1255@san.rr.com>
Date: Sun, 26 Mar 2000 15:55:02 -0800
From: Doug Barton <DougGuy@san.rr.com>
Organization: Triborough Bridge & Tunnel Authority
X-Mailer: Mozilla 4.72 [en] (X11; U; FreeBSD 5.0-CURRENT-0325 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Stan Brown <stanb@netcom.com>
Cc: FreeBSD Stable List <freebsd-stable@freebsd.org>
Subject: Re: How to shutdown to single user in 4.0?
References: <200003262346.PAA05302@netcom.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Stan Brown wrote:
> 
>         How do I _shut down_ to single user in 4.0. I lnow i can door shutdown
>         0r and catch it on the way up, and do a boot -s, but on 3.x I could do
>         "shutdown now", and wind up in single user,

	This didn't change. What happens when you type "shutdown now" at a root
prompt?

> so that I could cd /usr/src
>         ; make world; make kernel ; and reboot to upgrafe.

	You don't need to go to single user mode to upgrade unless you have a
lot of other users logging into your system. At worst, you can do 'make
buildworld' multi-user, then switch to single user and do 'make
installworld' which only takes a few minutes. The combination of make
buildworld and make installworld do everything that 'make world' does. 

Good luck,

Doug
-- 
    "So, the cows were part of a dream that dreamed itself into
existence? Is that possible?" asked the student incredulously.
    The master simply replied, "Mu."


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


From owner-freebsd-stable  Sun Mar 26 16:14:59 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32])
	by hub.freebsd.org (Postfix) with ESMTP id 48C3337BAFA
	for <stable@FreeBSD.ORG>; Sun, 26 Mar 2000 16:14:56 -0800 (PST)
	(envelope-from dwhite@resnet.uoregon.edu)
Received: from localhost (dwhite@localhost)
	by resnet.uoregon.edu (8.9.3/8.9.3) with ESMTP id QAA36790;
	Sun, 26 Mar 2000 16:14:47 -0800 (PST)
	(envelope-from dwhite@resnet.uoregon.edu)
Date: Sun, 26 Mar 2000 16:14:47 -0800 (PST)
From: Doug White <dwhite@resnet.uoregon.edu>
To: Andreas Klemm <andreas@klemm.gtn.com>
Cc: stable@FreeBSD.ORG
Subject: Re: HEADS-UP please: syslogd problems in 4.0: rejected in rule 0
 due to port mismatch.
In-Reply-To: <20000325141343.A26444@titan.klemm.gtn.com>
Message-ID: <Pine.BSF.4.21.0003261613370.67760-100000@resnet.uoregon.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Sending help mail with HEADS-UP would seem bad form; HEADSUP is reserved
for changes that require user intervention before the next build.

On Sat, 25 Mar 2000, Andreas Klemm wrote:

> On Sat, Mar 25, 2000 at 01:53:09PM +0100, Andreas Klemm wrote:
> > My cisco is unable to write to the syslog daemon.
> > Even adding the IP address with -a flags doesn't cure the problem.
> > 
> > syslogd -d -v -a 172.16.2.2/32 
> 
> Well, to be more precise,
> syslogd runs, but -a doesn't allow me to accept only syslog updates
> from my cisco.
> 
> First I overlooked -s after mergemaster run...

What port is the cisco sending the syslog updates from?  The default -a
requires it to be sent *from* the syslogd port.  A tcpdump is probably in
order.

Doug White                    |  FreeBSD: The Power to Serve
dwhite@resnet.uoregon.edu     |  www.FreeBSD.org



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


From owner-freebsd-stable  Sun Mar 26 16:19:34 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from cx344940-a.meta1.la.home.com (cx344940-a.meta1.la.home.com [24.6.21.74])
	by hub.freebsd.org (Postfix) with ESMTP id D09D137BA81
	for <stable@FreeBSD.ORG>; Sun, 26 Mar 2000 16:19:30 -0800 (PST)
	(envelope-from conrads@cx344940-a.meta1.la.home.com)
Received: (from conrads@localhost)
	by cx344940-a.meta1.la.home.com (8.9.3/8.9.3) id SAA52447;
	Sun, 26 Mar 2000 18:19:24 -0600 (CST)
	(envelope-from conrads)
Message-ID: <XFMail.000326181923.conrads@home.com>
X-Mailer: XFMail 1.4.0 on FreeBSD
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <38DC55BC.BA2240C2@newsguy.com>
Date: Sun, 26 Mar 2000 18:19:23 -0600 (CST)
Organization: @Home Network
From: Conrad Sabatier <conrads@home.com>
To: "Daniel C. Sobral" <dcs@newsguy.com>
Subject: Re: What does "Voxware still supported in 4.0" mean exactly?
Cc: stable@FreeBSD.ORG
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


On 25-Mar-00 Daniel C. Sobral wrote:
> If you will allow me, I'll explain the issues here.

[snipped for brevity]

Thank you very much for that very clear and thorough explanation.
I've decided that, for the time being, I'll just stick with 3.4-STABLE,
until such time as I see that my card is supported under 4.x or later.

I wish I could help with the development of the pcm driver, but
unfortunately, it's been quite a while since I undertook any sort of
serious programming project, and my skills are quite rusty, not to mention
that device driver programming was never something I ever delved into, and
from looking at the sources, is not something I really feel capable at all
of dealing with.  :-)

I'll shut up now.

-- 
Conrad Sabatier
http://members.home.net/conrads/
ICQ# 1147270



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


From owner-freebsd-stable  Sun Mar 26 17: 9: 6 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from wally.bellnetworks.net (www.bellnetworks.net [216.214.153.70])
	by hub.freebsd.org (Postfix) with ESMTP id ADF4F37B8F7
	for <stable@FreeBSD.ORG>; Sun, 26 Mar 2000 17:08:58 -0800 (PST)
	(envelope-from jerry@bellnetworks.net)
Received: from itbell (dhcp-247.bellnetworks.net [208.177.187.247])
	by wally.bellnetworks.net (8.9.3/8.9.3) with SMTP id UAA05703
	for <stable@FreeBSD.ORG>; Sun, 26 Mar 2000 20:08:57 -0500 (EST)
	(envelope-from jerry@bellnetworks.net)
Message-ID: <022001bf9724$44358c00$f7bbb1d0@netrex.com>
From: "Jerry Bell" <jerry@bellnetworks.net>
To: <stable@FreeBSD.ORG>
References: <XFMail.000326095323.mike@rbc.ru> <015801bf96cc$14f8fce0$f7bbb1d0@netrex.com> <20000326163457.O86036@strontium.scientia.demon.co.uk> <38DE9C8F.3F9D6246@pocketscience.com>
Subject: Re: ps, w, top and netstat problem
Date: Sun, 26 Mar 2000 08:07:40 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Yes sir, this is how I've been doing it.  Everything with this problem looks
to be an inconsistency between the kernel and the binaries, but I'm pretty
certain this is not the case.

Here's a little more background:  twice now, I've installed 4.0 RELEASE on
this box, cvsup'd to RELENG_4, run make world, built (and installed) a new
kernel based on those sources, and after a reboot, I get this problem.

I don't know if it will help at all, but here's some more info on this
system:

dogbert# dmesg
Copyright (c) 1992-2000 The FreeBSD Project.
Copyright (c) 1982, 1986, 1989, 1991, 1993
        The Regents of the University of California. All rights reserved.
FreeBSD 4.0-STABLE #2: Sun Mar 26 09:19:03 EST 2000
    jerry@dogbert.bellnetworks.net:/usr/src/sys/compile/GENERIC
Timecounter "i8254"  frequency 1193182 Hz
CPU: AMD-K6(tm) 3D processor (400.91-MHz 586-class CPU)
  Origin = "AuthenticAMD"  Id = 0x58c  Stepping = 12
  Features=0x8021bf<FPU,VME,DE,PSE,TSC,MSR,MCE,CX8,PGE,MMX>
  AMD Features=0x80000800<SYSCALL,3DNow!>
real memory  = 268435456 (262144K bytes)
avail memory = 256413696 (250404K bytes)
Preloaded elf kernel "kernel" at 0xc03c0000.
md0: Malloc disk
npx0: <math processor> on motherboard
npx0: INT 16 interface
pcib0: <Host to PCI bridge> on motherboard
pci0: <PCI bus> on pcib0
pcib2: <VIA 82C598MVP (Apollo MVP3) PCI-PCI (AGP) bridge> at device 1.0 on
pci0
pci1: <PCI bus> on pcib2
isab0: <VIA 82C586 PCI-ISA bridge> at device 7.0 on pci0
isa0: <ISA bus> on isab0
atapci0: <VIA 82C586 ATA33 controller> port 0xd000-0xd00f at device 7.1 on
pci0
ata0: at 0x1f0 irq 14 on atapci0
ata1: at 0x170 irq 15 on atapci0
pci0: <VIA 83C572 USB controller> at 7.2 irq 0
pci0: <Alliance PMAT24 SVGA controller> at 8.0
ed0: <NE2000 PCI Ethernet (RealTek 8029)> port 0xdc00-0xdc1f irq 11 at
device 9.0 on pci0
ed0: supplying EUI64: 00:80:c8:ff:fe:c1:f5:30
ed0: address 00:80:c8:c1:f5:30, type NE2000 (16 bit)
ahc0: <Adaptec 2940A Ultra SCSI adapter> port 0xe000-0xe0ff mem
0xe7000000-0xe7000fff irq 4 at device 10.0 on pci0
ahc0: aic7860 Single Channel A, SCSI Id=7, 3/255 SCBs
pcib1: <Host to PCI bridge> on motherboard
pci2: <PCI bus> on pcib1
fdc0: <NEC 72065B or clone> at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0
fdc0: FIFO enabled, 8 bytes threshold
fd0: <1440-KB 3.5" drive> on fdc0 drive 0
atkbdc0: <keyboard controller (i8042)> at port 0x60-0x6f on isa0
atkbd0: <AT Keyboard> irq 1 on atkbdc0
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
sc0: <System console> on isa0
sc0: VGA <16 virtual consoles, flags=0x200>
sio0: configured irq 4 not in bitmap of probed irqs 0
sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
sio0: type 8250
sio1: configured irq 3 not in bitmap of probed irqs 0
ppc0: <Parallel port> at port 0x378-0x37f irq 7 on isa0
ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode
ppi0: <Parallel I/O> on ppbus0
lpt0: <Printer> on ppbus0
lpt0: Interrupt-driven port
plip0: <PLIP network interface> on ppbus0
IP Filter: initialized.  Default = pass all, Logging = enabled
IP Filter: v3.3.8
ad0: 6485MB <Maxtor 90680D4> [13176/16/63] at ata0-master using UDMA33
ad2: 6679MB <Maxtor 87000D8> [14475/15/63] at ata1-master using UDMA33
Waiting 15 seconds for SCSI devices to settle
Mounting root from ufs:/dev/ad0s1a
da0 at ahc0 bus 0 target 0 lun 0
da0: <IBM DGHS18Y 03B0> Fixed Direct Access SCSI-3 device
da0: 20.000MB/s transfers (20.000MHz, offset 15), Tagged Queueing Enabled
da0: 17501MB (35843670 512 byte sectors: 255H 63S/T 2231C)
ed0: starting DAD for fe80:0001::0280:c8ff:fec1:f530
ed0: DAD complete for fe80:0001::0280:c8ff:fec1:f530 - no duplicates found

Here is the top part of my kernel config (the rest is stock from GENERIC):


machine         i386
cpu             I586_CPU
cpu             I686_CPU
ident           GENERIC
maxusers        100

#makeoptions    DEBUG=-g                #Build kernel with gdb(1) debug
symbols

options         INET                    #InterNETworking
options         INET6                   #IPv6 communications protocols
options         FFS                     #Berkeley Fast Filesystem
options         FFS_ROOT                #FFS usable as root device [keep
this!]
options         MFS                     #Memory Filesystem
options         MD_ROOT                 #MD is a potential root device
options         NFS                     #Network Filesystem
options         NFS_ROOT                #NFS usable as root device, NFS
required
options         PROCFS                  #Process filesystem
options         COMPAT_43               #Compatible with BSD 4.3 [KEEP
THIS!]
options         SCSI_DELAY=15000        #Delay (in ms) before probing SCSI
options         UCONSOLE                #Allow users to grab the console
options         USERCONFIG              #boot -c editor
options         VISUAL_USERCONFIG       #visual boot -c editor
options         SYSVSHM                 #SYSV-style shared memory
options         SYSVMSG                 #SYSV-style message queues
options         SYSVSEM                 #SYSV-style semaphores
options         P1003_1B                #Posix P1003_1B real-time extentions
options         _KPOSIX_PRIORITY_SCHEDULING
options         ICMP_BANDLIM            #Rate limit bad replies
options         PQ_HUGECACHE
options         NO_F00F_HACK
options         CPU_WT_ALLOC

options         IPFILTER                #ipfilter support
options         IPFILTER_LOG            #ipfilter logging
options         TCP_DROP_SYNFIN         #drop TCP packets with SYN+FIN
options         TCP_RESTRICT_RST        #restrict emission of TCP RST



Please  help!!!

Thank you,

Jerry


----- Original Message -----
From: Brian Nelson <brian@pocketscience.com>
To: Ben Smithurst <ben@scientia.demon.co.uk>
Cc: Jerry Bell <jerry@bellnetworks.net>; <freebsd-stable@FreeBSD.ORG>
Sent: Sunday, March 26, 2000 6:26 PM
Subject: Re: ps, w, top and netstat problem


> Could you have possibly also compiled the OS, re-CVSup'd to a NEWER
> version of the source, and then compiled a kernel?
>
> Make sure you following all the following steps:
> cvsup -L 2 -g stable-supfile
> cd /usr/src
> make buildworld
> make installworld
> cd /usr/src/sys/i386/conf
> config -r MYKERNEL
> cd ../../compile/MYKERNEL
> make depend
> make
> make install
>
> at each step, you should stop and make sure NOTHING error'd out.
>
> reboot




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


From owner-freebsd-stable  Sun Mar 26 17:10: 5 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from rover.village.org (rover.village.org [204.144.255.49])
	by hub.freebsd.org (Postfix) with ESMTP id 4C8DB37BA7A
	for <freebsd-stable@FreeBSD.ORG>; Sun, 26 Mar 2000 17:09:58 -0800 (PST)
	(envelope-from imp@harmony.village.org)
Received: from harmony.village.org (harmony.village.org [10.0.0.6])
	by rover.village.org (8.9.3/8.9.3) with ESMTP id SAA51511;
	Sun, 26 Mar 2000 18:09:56 -0700 (MST)
	(envelope-from imp@harmony.village.org)
Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id SAA87917; Sun, 26 Mar 2000 18:09:42 -0700 (MST)
Message-Id: <200003270109.SAA87917@harmony.village.org>
To: Stan Brown <stanb@netcom.com>
Subject: Re: How to shutdown to single user in 4.0? 
Cc: freebsd-stable@FreeBSD.ORG (FreeBSD Stable List)
In-reply-to: Your message of "Sun, 26 Mar 2000 18:46:16 EST."
		<200003262346.PAA05302@netcom.com> 
References: <200003262346.PAA05302@netcom.com>  
Date: Sun, 26 Mar 2000 18:09:42 -0700
From: Warner Losh <imp@village.org>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

In message <200003262346.PAA05302@netcom.com> Stan Brown writes:
: 	How do I _shut down_ to single user in 4.0.

# kill 1

I discovered this by mistake several years ago when I typed
	kill 1 1
instead of
	kill -1 1
when restarting getties.  Of course this wasn't on my personal
workstation, but rather a 8 cpu machine that the entire OS group was
using for development. :-(.  At least I got a very detailed and
explicit explanation of what I had done and why it was do bad...

Warner


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


From owner-freebsd-stable  Sun Mar 26 17:33:49 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from workhorse.iMach.com (workhorse.iMach.com [206.127.77.89])
	by hub.freebsd.org (Postfix) with ESMTP id 33F5E37B9D2
	for <freebsd-stable@FreeBSD.ORG>; Sun, 26 Mar 2000 17:33:45 -0800 (PST)
	(envelope-from forrestc@workhorse.iMach.com)
Received: from localhost (forrestc@localhost)
	by workhorse.iMach.com (8.9.3/8.9.3) with ESMTP id SAA13666;
	Sun, 26 Mar 2000 18:28:10 -0700 (MST)
Date: Sun, 26 Mar 2000 18:28:09 -0700 (MST)
From: "Forrest W. Christian" <forrestc@iMach.com>
To: Warner Losh <imp@village.org>
Cc: Stan Brown <stanb@netcom.com>,
	FreeBSD Stable List <freebsd-stable@FreeBSD.ORG>
Subject: Re: How to shutdown to single user in 4.0? 
In-Reply-To: <200003270109.SAA87917@harmony.village.org>
Message-ID: <Pine.BSF.4.21.0003261822520.13592-100000@workhorse.iMach.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Sun, 26 Mar 2000, Warner Losh wrote:

> I discovered this by mistake several years ago when I typed
> 	kill 1 1

Yep, been there, done that.

As a result I now use kill -HUP instead of kill -1.  Too easy to typo the
former.

On a related note, I had a friend running Caldera Linux who's system
started doing weird things.  We discovered that for some reason the system
was running without init (or any process 1).   Don't ask me how, or why or
tell me it's not possible.   It even ended up that way after a
reboot.  What was weird is that you could log into the system in some ways
but not others - the console worked, and I believe FTP didn't.  Not sure
beyond that.

He re-installed and it fixed it.

- Forrest W. Christian (forrestc@imach.com) KD7EHZ
----------------------------------------------------------------------
iMach, Ltd., P.O. Box 5749, Helena, MT 59604      http://www.imach.com
Solutions for your high-tech problems.                  (406)-442-6648
----------------------------------------------------------------------



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


From owner-freebsd-stable  Sun Mar 26 17:38:43 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from jander.fl.net.au (jander.fl.net.au [202.181.0.27])
	by hub.freebsd.org (Postfix) with ESMTP id 0CCB337BA2B
	for <freebsd-stable@freebsd.org>; Sun, 26 Mar 2000 17:38:38 -0800 (PST)
	(envelope-from acs@jander.fl.net.au)
Received: from localhost (acs@localhost)
	by jander.fl.net.au (8.9.2/8.8.8) with ESMTP id LAA53172
	for <freebsd-stable@freebsd.org>; Mon, 27 Mar 2000 11:38:32 +1000 (EST)
	(envelope-from acs@jander.fl.net.au)
Date: Mon, 27 Mar 2000 11:38:32 +1000 (EST)
From: Andrew <acs@fl.net.au>
To: freebsd-stable@freebsd.org
Subject: DMA on a UDMA 33 drive
Message-ID: <Pine.BSF.4.05.10003271126070.53046-100000@jander.fl.net.au>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hi,

What is the current status of DMA support? I've always had trouble with it
and just then I enabled it, caused a lot of disk activity and the machine
paniced. On reboot It took me several goes to get fsck to get through all
the errors with out complaining it couldn't find an inode. My lost+found
directy filled up and fsck had to extend it. Half the source tree ended up
in lost+found. I'm not sure if any files were lost as I didnt bother
putting them back, just rmed them and cvsupped again.

This was with 3.4-STABLE asof yesterday. Extracts from dmesg:

CPU: Cyrix 6x86MX (250.57-MHz 686-class CPU)
  Origin = "CyrixInstead"  Id = 0x600  Stepping = 0  DIR=0x0853
  Features=0x80a135<FPU,DE,TSC,MSR,CX8,PGE,CMOV,MMX>
real memory  = 67108864 (65536K bytes)
config> en wdc1
config> po wdc1 0x170
config> ir wdc1 15
config> f wdc1 0xa0ff
config> en wdc0
config> po wdc0 0x1f0
config> ir wdc0 14
config> f wdc0 0x80ff
config> q

Probing for devices on PCI bus 0:
chip0: <VIA 82C597 (Apollo VP3) system controller> rev 0x04 on pci0.0.0
chip1: <VIA 82C598MVP (Apollo MVP3) PCI-PCI bridge> rev 0x00 on pci0.1.0
chip2: <VIA 82C586 PCI-ISA bridge> rev 0x47 on pci0.7.0
ide_pci0: <VIA 82C586x (Apollo) Bus-master IDE controller> rev 0x06 on pci0.7.1
chip3: <VIA 82C586B ACPI interface> rev 0x10 on pci0.7.3

<I have turned off DMA here>

wdc0 at 0x1f0-0x1f7 irq 14 flags 0x80ff on isa
wdc0: unit 0 (wd0): <Maxtor 90845D4>, 32-bit, multi-block-16
wd0: 8063MB (16514064 sectors), 16383 cyls, 16 heads, 63 S/T, 512 B/S
wdc1 at 0x170-0x177 irq 15 flags 0x80ff on isa
wdc1: unit 0 (wd2): <FUJITSU MPC3043AT>, 32-bit, multi-block-16
wd2: 4125MB (8448300 sectors), 8940 cyls, 15 heads, 63 S/T, 512 B/S

It was the fujitsu that I ahd DMA turend on, the Maxtor wasn't mounted.
Just before the panic I got DMA failure, DMA status 5<active>.

Anyway what I wanted to know is is DMA known to be broken or am I just
cursed? Does it depend on the motherboard or the drive?

Does anyone want me to collect debugging output for them? Would I have
more luck with 4.0?

Thanks,

Andrew (who has had almost every hard drive he owns fail in the past
week...:-( )



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


From owner-freebsd-stable  Sun Mar 26 17:43:59 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from vinyl.sentex.ca (vinyl.sentex.ca [209.112.4.14])
	by hub.freebsd.org (Postfix) with ESMTP id D469D37B7DB
	for <freebsd-stable@FreeBSD.ORG>; Sun, 26 Mar 2000 17:43:54 -0800 (PST)
	(envelope-from mike@sentex.net)
Received: from granite.sentex.net (granite-atm.sentex.ca [209.112.4.1])
	by vinyl.sentex.ca (8.9.3/8.9.3) with ESMTP id UAA93402;
	Sun, 26 Mar 2000 20:43:52 -0500 (EST)
	(envelope-from mike@sentex.net)
Received: from chimp (ospf-mdt.sentex.net [205.211.164.81]) by granite.sentex.net (8.8.8/8.6.9) with ESMTP id UAA28389; Sun, 26 Mar 2000 20:43:50 -0500 (EST)
Message-Id: <4.2.2.20000326204211.0321ba48@mail.sentex.net>
X-Sender: mdtancsa@mail.sentex.net
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 
Date: Sun, 26 Mar 2000 20:44:03 -0500
To: Andrew <acs@fl.net.au>, freebsd-stable@FreeBSD.ORG
From: Mike Tancsa <mike@sentex.net>
Subject: Re: DMA on a UDMA 33 drive
In-Reply-To: <Pine.BSF.4.05.10003271126070.53046-100000@jander.fl.net.au
 >
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

At 11:38 AM 3/27/2000 +1000, Andrew wrote:
>Hi,
>
>What is the current status of DMA support? I've always had trouble with it
>and just then I enabled it, caused a lot of disk activity and the machine


I have had good luck with 4.x STABLE and the Intel PIIX4 and various 
Quantum drives.  Dont know how the others fair, but you might search 
through the archives to see

>chip0: <VIA 82C597 (Apollo VP3) system controller> rev 0x04 on pci0.0.0
>chip1: <VIA 82C598MVP (Apollo MVP3) PCI-PCI bridge> rev 0x00 on pci0.1.0
>chip2: <VIA 82C586 PCI-ISA bridge> rev 0x47 on pci0.7.0
>ide_pci0: <VIA 82C586x (Apollo) Bus-master IDE controller> rev 0x06 on 
>pci0.7.1
>chip3: <VIA 82C586B ACPI interface> rev 0x10 on pci0.7.3
>
>Does anyone want me to collect debugging output for them? Would I have
>more luck with 4.0?

Possibly.  From the ata man pages,

      The currently supported controllers with their maximum speed include:

      Acerlabs Aladdin         Ultra DMA 33 (UDMA2), 33 MB/sec
      AMD 756                  Ultra DMA 66 (UDMA4), 66 MB/sec
      HighPoint HPT366         Ultra DMA 66 (UDMA4), 66 MB/sec
      Intel PIIX               DMA 2 (WDMA2), 16 MB/sec
      Intel PIIX3              DMA 2 (WDMA2), 16 MB/sec
      Intel PIIX4              Ultra DMA 33 (UDMA2), 33 MB/sec
      Intel ICH                Ultra DMA 66 (UDMA4), 66 MB/sec
      Promise Fasttrak-33      Ultra DMA 33 (UDMA2), 33 MB/sec
      Promise Fasttrak-66      Ultra DMA 66 (UDMA4), 66 MB/sec
      Promise Ultra-33         Ultra DMA 33 (UDMA2), 33 MB/sec
      Promise Ultra-66         Ultra DMA 66 (UDMA4), 66 MB/sec
      SiS 5591                 Ultra DMA 33 (UDMA2), 33 MB/sec
      VIA 82C586               Ultra DMA 33 (UDMA2), 33 MB/sec
      VIA 82C686               Ultra DMA 66 (UDMA4), 66 MB/sec
      CMD 646                  DMA 2 (WDMA2), 16 MB/sec
      Cypress 82C693           DMA 2 (WDMA2), 16 MB/sec

      All unknown chipsets can be supported at the maximum speed of 16 MB/sec.


         ---Mike



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


From owner-freebsd-stable  Sun Mar 26 19:27:52 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from charon.ipass.net (charon.ipass.net [198.79.53.8])
	by hub.freebsd.org (Postfix) with ESMTP id BD37537BAE4
	for <stable@freebsd.org>; Sun, 26 Mar 2000 19:27:48 -0800 (PST)
	(envelope-from rhh@ipass.net)
Received: from stealth.ipass.net. (ppp-1-253.dialup.rdu.ipass.net [209.170.132.253])
	by charon.ipass.net (8.9.3/8.9.3) with ESMTP id WAA00040
	for <stable@freebsd.org>; Sun, 26 Mar 2000 22:27:46 -0500 (EST)
Received: (from rhh@localhost)
	by stealth.ipass.net. (8.9.3/8.8.8) id WAA47105
	for stable@freebsd.org; Sun, 26 Mar 2000 22:30:26 -0500 (EST)
	(envelope-from rhh)
Date: Sun, 26 Mar 2000 22:30:26 -0500
From: Randall Hopper <aa8vb@ipass.net>
To: stable@freebsd.org
Subject: Compiling FORTRAN code on -stable
Message-ID: <20000326223026.A46836@ipass.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0.1i
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

I'm trying to build a fluid dynamics library on FreeBSD, and I'm getting
repeated occurrances of this compiler error in many FORTRAN source files:

    Error on line 5 of tst.f: Statement order error: declaration after DATA

As a visual aid, here's a short sample that produces this error:

                SUBROUTINE XMDF2T(APARM)
                IMPLICIT DOUBLE PRECISION(A)
                INTEGER  INT1
                DATA FR/0D0/
                INTEGER  INT2
          99998 END
        and compile using "f77 -c tst.f":

Apparently f77 compilers will eat this, but our f77 (from bin or ports)
will not.

Any FORTRAN folks out there that know how to get around this?
(there are close to 100 files with this problem.)

Thanks,

Randall


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


From owner-freebsd-stable  Sun Mar 26 20:24:57 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from charon.ipass.net (charon.ipass.net [198.79.53.8])
	by hub.freebsd.org (Postfix) with ESMTP id B459A37BA63
	for <stable@FreeBSD.ORG>; Sun, 26 Mar 2000 20:24:54 -0800 (PST)
	(envelope-from rhh@ipass.net)
Received: from stealth.ipass.net. (ppp-1-253.dialup.rdu.ipass.net [209.170.132.253])
	by charon.ipass.net (8.9.3/8.9.3) with ESMTP id XAA04529
	for <stable@FreeBSD.ORG>; Sun, 26 Mar 2000 23:24:52 -0500 (EST)
Received: (from rhh@localhost)
	by stealth.ipass.net. (8.9.3/8.8.8) id XAA73606
	for stable@FreeBSD.ORG; Sun, 26 Mar 2000 23:27:31 -0500 (EST)
	(envelope-from rhh)
Date: Sun, 26 Mar 2000 23:27:31 -0500
From: Randall Hopper <aa8vb@ipass.net>
To: stable@FreeBSD.ORG
Subject: Re: Compiling FORTRAN code on -stable
Message-ID: <20000326232731.A73462@ipass.net>
References: <20000326223026.A46836@ipass.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0.1i
In-Reply-To: <20000326223026.A46836@ipass.net>; from aa8vb@ipass.net on Sun, Mar 26, 2000 at 10:30:26PM -0500
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Randall Hopper:
 |    Error on line 5 of tst.f: Statement order error: declaration after DATA
...
 |                INTEGER  INT1
 |                DATA FR/0D0/
 |                INTEGER  INT2
...
 |Apparently f77 compilers will eat this, but our f77 (from bin or ports)
 |will not.

Ahh, yes.  I found a cool tool that pre-chews FORTRAN so that f2c can
digest it.  It also comes with a "f77" front-end script:

     http://www-hermes.desy.de/ww/f77prob.html

Expect a port soon.

Randall


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


From owner-freebsd-stable  Sun Mar 26 22:15:58 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from picalon.gun.de (picalon.gun.de [192.109.159.1])
	by hub.freebsd.org (Postfix) with ESMTP id 62EF137B8FF
	for <stable@FreeBSD.ORG>; Sun, 26 Mar 2000 22:15:52 -0800 (PST)
	(envelope-from andreas@klemm.gtn.com)
Received: (from uucp@localhost)
	by picalon.gun.de (8.9.3/8.9.3) id IAA27780;
	Mon, 27 Mar 2000 08:15:33 +0200 (MET DST)
>Received: (from andreas@localhost)
	by klemm.gtn.com (8.9.3/8.9.3) id IAA54114;
	Mon, 27 Mar 2000 08:10:11 +0200 (CEST)
	(envelope-from andreas)
Date: Mon, 27 Mar 2000 08:10:11 +0200
From: Andreas Klemm <andreas@klemm.gtn.com>
To: Doug White <dwhite@resnet.uoregon.edu>
Cc: stable@FreeBSD.ORG
Subject: Re: HEADS-UP please: syslogd problems in 4.0: rejected in rule 0 due to port mismatch.
Message-ID: <20000327081011.A53108@titan.klemm.gtn.com>
References: <20000325141343.A26444@titan.klemm.gtn.com> <Pine.BSF.4.21.0003261613370.67760-100000@resnet.uoregon.edu>
Mime-Version: 1.0
X-Mailer: Mutt 1.0.1i
In-Reply-To: <Pine.BSF.4.21.0003261613370.67760-100000@resnet.uoregon.edu>; from dwhite@resnet.uoregon.edu on Sun, Mar 26, 2000 at 04:14:47PM -0800
X-Operating-System: FreeBSD 4.0-STABLE SMP
X-Disclaimer: A free society is one where it is safe to be unpopular
Content-Type: text/plain; charset=us-ascii
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Sun, Mar 26, 2000 at 04:14:47PM -0800, Doug White wrote:
> Sending help mail with HEADS-UP would seem bad form; HEADSUP is reserved
> for changes that require user intervention before the next build.

You are right, sorry, was bad style.

> What port is the cisco sending the syslog updates from?  The default -a
> requires it to be sent *from* the syslogd port.  A tcpdump is probably in
> order.

Or ethereal ;-) Well the cisco sends syslog messages from port 49902.
IOS 12.0(9).

-- 
Andreas Klemm                               http://people.FreeBSD.ORG/~andreas
                                     http://www.freebsd.org/~fsmp/SMP/SMP.html
                                   powered by Symmetric MultiProcessor FreeBSD
New APSFILTER 520 and songs from our band - http://people.freebsd.org/~andreas



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


From owner-freebsd-stable  Sun Mar 26 23: 5: 8 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from jason.argos.org (a1-3b058.neo.rr.com [24.93.181.58])
	by hub.freebsd.org (Postfix) with ESMTP id 50B8437B6B6
	for <stable@FreeBSD.ORG>; Sun, 26 Mar 2000 23:05:03 -0800 (PST)
	(envelope-from mike@argos.org)
Received: from localhost (mike@localhost)
	by jason.argos.org (8.9.1/8.9.1) with ESMTP id CAA15505;
	Mon, 27 Mar 2000 02:04:18 -0500
Date: Mon, 27 Mar 2000 02:04:18 -0500 (EST)
From: Mike Nowlin <mike@argos.org>
To: Doug White <dwhite@resnet.uoregon.edu>
Cc: Andreas Klemm <andreas@klemm.gtn.com>, stable@FreeBSD.ORG
Subject: Re: HEADS-UP please: syslogd problems in 4.0: rejected in rule 0
 due to port mismatch.
In-Reply-To: <Pine.BSF.4.21.0003261613370.67760-100000@resnet.uoregon.edu>
Message-ID: <Pine.LNX.4.05.10003270155310.15121-100000@jason.argos.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


> What port is the cisco sending the syslog updates from?  The default -a
> requires it to be sent *from* the syslogd port.  A tcpdump is probably in
> order.

Is this "the right way" to do it?  I'm just wondering why the requirement
that the messages come from the syslog port.  My Linux & DEC UNIX machines
don't require this, although they're not using any kind of allowed_peer
restrictions - just "remote logging enabled".  

BTW: My cisco 2610 & 1720 routers are successfully logging to a Linux box
using the following:

logging facility daemon
logging 208.132.36.130

...the log packets come over from 1025, 40282, whatever..  Seems random,
but (in my opinion), "The Right Way".  If a user-level program opens a
port to syslog, it shouldn't be required to use port 514 to log to a
remote host.    

(If this seems goofy, I've had a few tonight.....:) )

mike




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


From owner-freebsd-stable  Mon Mar 27  0:42:31 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from alpha.dgweb.com (alpha.dgweb.com [207.218.73.252])
	by hub.freebsd.org (Postfix) with ESMTP id 0B4A137B920
	for <FreeBSD-Stable@freebsd.org>; Mon, 27 Mar 2000 00:41:26 -0800 (PST)
	(envelope-from kuzak@kuzak.net)
Received: from kuzak (killer@sac1-35.dgweb.com [207.218.73.35])
	by alpha.dgweb.com (8.10.0/8.10.0) with SMTP id e2R8gLX55654
	for <FreeBSD-Stable@freebsd.org>; Mon, 27 Mar 2000 00:42:21 -0800 (PST)
Message-Id: <200003270842.e2R8gLX55654@alpha.dgweb.com>
X-Sender: kuzak@mail.kuzak.net (Unverified)
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0
Date: Mon, 27 Mar 2000 00:30:17 -0800
To: FreeBSD-Stable@freebsd.org
From: Kuzak <kuzak@kuzak.net>
Subject: 4.0 Kernel
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

	Tonight I cvsup't and made a new kernel to go -STABLE and
after rebooting into the new kernel I noticed this happens..


Mar 27 00:29:13 he /kernel: real memory  = 268435456 (262144K bytes)
Mar 27 00:29:13 he /kernel: config> di psm0
Mar 27 00:29:13 he /kernel: No such device: psm0
Mar 27 00:29:13 he /kernel: Invalid command or syntax.  Type `?' for help.
Mar 27 00:29:13 he /kernel: config> di sio1
Mar 27 00:29:13 he /kernel: No such device: sio1
Mar 27 00:29:13 he /kernel: Invalid command or syntax.  Type `?' for help.
Mar 27 00:29:13 he /kernel: config> di sio0
Mar 27 00:29:13 he /kernel: No such device: sio0
Mar 27 00:29:13 he /kernel: Invalid command or syntax.  Type `?' for help.
Mar 27 00:29:13 he /kernel: config> di ppc0
Mar 27 00:29:13 he /kernel: No such device: ppc0
Mar 27 00:29:13 he /kernel: Invalid command or syntax.  Type `?' for help.
Mar 27 00:29:13 he /kernel: config> di sn0
Mar 27 00:29:13 he /kernel: No such device: sn0
Mar 27 00:29:13 he /kernel: Invalid command or syntax.  Type `?' for help.
Mar 27 00:29:13 he /kernel: config> di lnc0
Mar 27 00:29:13 he /kernel: No such device: lnc0
Mar 27 00:29:13 he /kernel: Invalid command or syntax.  Type `?' for help.
Mar 27 00:29:13 he /kernel: config> di le0
Mar 27 00:29:13 he /kernel: No such device: le0
Mar 27 00:29:13 he /kernel: Invalid command or syntax.  Type `?' for help.
Mar 27 00:29:13 he /kernel: config> di ie0
Mar 27 00:29:13 he /kernel: No such device: ie0
Mar 27 00:29:13 he /kernel: Invalid command or syntax.  Type `?' for help.
Mar 27 00:29:13 he /kernel: config> di fe0
Mar 27 00:29:13 he /kernel: No such device: fe0
Mar 27 00:29:13 he /kernel: Invalid command or syntax.  Type `?' for help.
Mar 27 00:29:13 he /kernel: config> di ed0
Mar 27 00:29:13 he /kernel: No such device: ed0
Mar 27 00:29:13 he /kernel: Invalid command or syntax.  Type `?' for help.
Mar 27 00:29:13 he /kernel: config> di cs0
Mar 27 00:29:13 he /kernel: No such device: cs0
Mar 27 00:29:13 he /kernel: Invalid command or syntax.  Type `?' for help.
Mar 27 00:29:13 he /kernel: config> di bt0
Mar 27 00:29:13 he /kernel: No such device: bt0
Mar 27 00:29:13 he /kernel: Invalid command or syntax.  Type `?' for help.
Mar 27 00:29:13 he /kernel: config> di aic0
Mar 27 00:29:13 he /kernel: No such device: aic0
Mar 27 00:29:13 he /kernel: Invalid command or syntax.  Type `?' for help.
Mar 27 00:29:13 he /kernel: config> di aha0
Mar 27 00:29:13 he /kernel: No such device: aha0
Mar 27 00:29:13 he /kernel: Invalid command or syntax.  Type `?' for help.
Mar 27 00:29:13 he /kernel: config> di adv0
Mar 27 00:29:13 he /kernel: No such device: adv0
Mar 27 00:29:13 he /kernel: Invalid command or syntax.  Type `?' for help.
Mar 27 00:29:13 he /kernel: config> q
Mar 27 00:29:13 he /kernel: avail memory = 257024000 (251000K bytes)
Mar 27 00:29:13 he /kernel: Preloaded elf kernel "kernel" at 0xc02eb000.

Those all appear to be things that I purposely commented out of the kernel
so I was just wondering why they are showing up there, and what I do to
fix/get rid of that.. Did I miss or forget something in building the kernel?
	-Aric


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


From owner-freebsd-stable  Mon Mar 27  0:51: 7 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from dt051n0b.san.rr.com (dt051n0b.san.rr.com [204.210.32.11])
	by hub.freebsd.org (Postfix) with ESMTP id C7E0B37BA4F
	for <FreeBSD-Stable@freebsd.org>; Mon, 27 Mar 2000 00:51:02 -0800 (PST)
	(envelope-from ugothrhos@gor.com)
Received: from gor.com (doug@master [10.0.0.2])
	by dt051n0b.san.rr.com (8.9.3/8.9.3) with ESMTP id AAA19374;
	Mon, 27 Mar 2000 00:50:56 -0800 (PST)
	(envelope-from ugothrhos@gor.com)
Message-ID: <38DF20F0.930E3093@gor.com>
Date: Mon, 27 Mar 2000 00:50:56 -0800
From: Doug Barton <ugothrhos@gor.com>
Organization: Triborough Bridge & Tunnel Authority
X-Mailer: Mozilla 4.72 [en] (X11; U; FreeBSD 5.0-CURRENT-0325 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Kuzak <kuzak@kuzak.net>
Cc: FreeBSD-Stable@freebsd.org
Subject: Re: 4.0 Kernel
References: <200003270842.e2R8gLX55654@alpha.dgweb.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Kuzak wrote:
> 
>         Tonight I cvsup't and made a new kernel to go -STABLE and
> after rebooting into the new kernel I noticed this happens..

	rm /boot/kernel.conf

Good luck,

Doug
-- 
    "So, the cows were part of a dream that dreamed itself into
existence? Is that possible?" asked the student incredulously.
    The master simply replied, "Mu."


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


From owner-freebsd-stable  Mon Mar 27  1: 0:12 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from mail.enteract.com (mail.enteract.com [207.229.143.33])
	by hub.freebsd.org (Postfix) with ESMTP id 5347637BA4F
	for <freebsd-stable@freebsd.org>; Mon, 27 Mar 2000 00:59:58 -0800 (PST)
	(envelope-from jim@nasby.net)
Received: from nasby.net (sysnasby@2.nasby.dsl.enteract.com [216.80.51.18])
	by mail.enteract.com (8.9.3/8.9.3) with ESMTP id CAA99742
	for <freebsd-stable@freebsd.org>; Mon, 27 Mar 2000 02:59:56 -0600 (CST)
	(envelope-from jim@nasby.net)
Message-ID: <38DF230C.B329FB12@nasby.net>
Date: Mon, 27 Mar 2000 02:59:56 -0600
From: "Jim C. Nasby" <jim@nasby.net>
Organization: distributed.net
X-Mailer: Mozilla 4.7 [en] (WinNT; U)
X-Accept-Language: en-US,en
MIME-Version: 1.0
To: freebsd-stable@freebsd.org
Subject: vinum drive is dead
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 suffered from a kernel panic, and the aftermath is that one of my
disks apparently got obliterated. disklabel -r da1 gives me an error
(don't remember what it is offhand), but the device itself seems ok. The
SCSI controller can read the drive (I had the controller verify the
media, it checked out ok), and the kernel recognizes it (although the
drives now show up in the order da0, da3, da2, da1 upon bootup, where it
used to be da0, 1, 2, 3).

I'm hoping that I can just re-label the drive and get back up and
running, since most everything lives on vinum raid5 plexes. The problem
is that I don't know what the proper way to do this would be. Should I
detache the affected subdisks, redo the disk, and re-attach? I'm real
hesitant to screw with things since somehow the raid plex that houses
/tmp got corrupted.

I think Greg is out of town for this week, but I'm hoping that someone
else can give me some pointers here. A vinum recovery page would be most
appreciated!!

TIA,
dB!
-- 
Jim C. Nasby (aka Decibel!)                                  /^\ 
jim@nasby.net                                               /___\
Freelance lighting designer and database developer         /  |  \
Member: Triangle Fraternity, Sports Car Club of America   /___|___\

Give your computer some brain candy! www.distributed.net Team #1828
Get paid to surf!! http://www.enteract.com/~nasby/alladvantage.html


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


From owner-freebsd-stable  Mon Mar 27  1: 7:56 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from storm.FreeBSD.org.uk (storm.freebsd.org.uk [194.242.139.170])
	by hub.freebsd.org (Postfix) with ESMTP id 6771D37B51C
	for <stable@FreeBSD.org>; Mon, 27 Mar 2000 01:07:51 -0800 (PST)
	(envelope-from brian@Awfulhak.org)
Received: from hak.lan.Awfulhak.org (hak.nat.Awfulhak.org [172.31.0.12])
	by storm.FreeBSD.org.uk (8.9.3/8.9.3) with ESMTP id KAA13292;
	Mon, 27 Mar 2000 10:07:48 +0100 (BST)
	(envelope-from brian@Awfulhak.org)
Received: from hak.lan.Awfulhak.org (localhost [127.0.0.1])
	by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id KAA01037;
	Mon, 27 Mar 2000 10:07:43 +0100 (BST)
	(envelope-from brian@hak.lan.Awfulhak.org)
Message-Id: <200003270907.KAA01037@hak.lan.Awfulhak.org>
X-Mailer: exmh version 2.1.1 10/15/1999
To: Ian Hart <ianjhart@yahoo.com>
Cc: stable@FreeBSD.org, brian@hak.lan.Awfulhak.org
Subject: Re: tun0 lost in 4.0 
In-Reply-To: Message from Ian Hart <ianjhart@yahoo.com> 
   of "Sat, 25 Mar 2000 20:49:03 -0800." <20000326044903.4764.qmail@web214.mail.yahoo.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 27 Mar 2000 10:07:42 +0100
From: Brian Somers <brian@Awfulhak.org>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> Walter Brameld wrote:
> > 
> > On Sun, 19 Mar 2000, in a never-ending search for
> enlightenment, Sergei Vyshenski wrote:
> > > Can not revive tun0 interface after moving to 4.0
> from 3.4
> > > in a way that src/UPDATING teaches.
> > >
> > > Kernel file has "pseudo-device   tun     1",
> kernel builds ok;
> > > ./MAKEDEV tun0 in /dev does not complain;
> > > bbut ifconfig says: "interface tun0 does not
> exist"
> > >
> > > Actually, I need tun0 to accept incoming user-ppp,
> > > and would be happy to hear of workaround at least.
> > >
> > > Thank you in advance.
> > > Sergei
> > 
> > Believe it should only be "pseudo-device tun" with
> no "1".
> > 
> > --
> > Walter Brameld
> 
> Sergei, did you fix your problem?
> 
> A bit late on this thread I know. The reason being -
> no modem for over a week. When I ran ppp and went to
> terminal mode there was no response at all from the
> modem. I was running 4.0-STABLE. Was A1 under
> 3.4-STABLE. I managed to get online (very) early
> Saturday morning to cvsup. Sometime during the power
> down/make world/reading of 500+ emails it broke again.
> It's currently working (obviously), but I'm too
> paranoid to do anything in case I break it again. I
> have set pseudo-device tun 1, contrary to GENERIC
> setting.

You shouldn't even need this line.  Ppp(8) will load the module if it 
needs to.  The fact that ppp actually started means that there are no 
tun(4) related problems.  If you're getting no response from the 
modem, then you really need to look in that direction.

> The modem is a no-name (ORIGO) 56k6 Rockwell Voice,
> ISA with jumpers, set to COM 4 IRQ 9. Tried in the two
> machines I have at home. One with PNP COM ports, the
> other not. Could be broken hardware of course.

Hmm, I tend to avoid irq 2/9....

> I also find I can no longer authenticate on freeserve
> (UK). X-stream is okay. Can someone who uses freeserve
> confirm/deny connection with 4.0-STABLE. Could be
> broken ISP of course.

Have you built ppp with DES ?  You should see be a -DHAVE_DES option on 
the cc line when building.  Also, make sure you haven't got any # 
characters in you password - if you have, you'll need to quote ("") 
the password string or escape the #.

> Any assistance would be most welcome. I can provide
> dmesg or whatever, but I'm not sure that will help as
> it's currently okay. Could be broken 'userware' of
> course :-)
> 
> On a positive note, at least I now know how to set up
> a gateway host and DNS servers. Next step - packet
> filtering and proxy servers. Joy Joy Joy.
> 
> ian j hart
> 
> PS. The upgrade 3.4-4.0 went more or less without a
> hitch. Slightly sweaty palms I couldn't remount /
> single user. Fixed that once I realised it was still
> on wd0 not ad0.
> 
> PPS. This probably will not attach to the thread. I
> find I cannot send mail (ISP firewall?). Thank God for
> Yahoo in emergencies.
> 
> __________________________________________________
> Do You Yahoo!?
> Talk to your friends online with Yahoo! Messenger.
> http://im.yahoo.com

-- 
Brian <brian@Awfulhak.org>                        <brian@[uk.]FreeBSD.org>
      <http://www.Awfulhak.org>                   <brian@[uk.]OpenBSD.org>
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 27  1:38:26 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from ZGIA.zp.ua (ZGIA.zp.ua [212.35.173.98])
	by hub.freebsd.org (Postfix) with ESMTP id A2D5637BC3E
	for <FreeBSD-Stable@FreeBSD.ORG>; Mon, 27 Mar 2000 01:37:49 -0800 (PST)
	(envelope-from laa@zgia.zp.ua)
Received: from localhost (laa@localhost)
	by ZGIA.zp.ua (8.9.3/8.9.3) with ESMTP id MAA48984;
	Mon, 27 Mar 2000 12:32:27 +0300 (EEST)
	(envelope-from laa@zgia.zp.ua)
Date: Mon, 27 Mar 2000 12:32:27 +0300 (EEST)
From: Alexandr Listopad <laa@ZGIA.zp.ua>
To: Kuzak <kuzak@kuzak.net>
Cc: FreeBSD-Stable@FreeBSD.ORG
Subject: Re: 4.0 Kernel
In-Reply-To: <200003270842.e2R8gLX55654@alpha.dgweb.com>
Message-ID: <Pine.BSF.4.10.10003271228100.48901-100000@Eagle.ZGIA.zp.ua>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

see: /boot/kernel.conf

and: /boot/defaults/loader.conf

and also edit /boot/loader.conf
this is my /boot/loader.conf :

# -- sysinstall generated deltas -- #
userconfig_script_load="NO"
autoboot_delay="0"

splash_bmp_load="YES"
bitmap_load="YES"
bitmap_name="/boot/daemon.bmp"  # Set this to the name of
the bmp or pcx file
bitmap_type="splash_image_data"

>	Tonight I cvsup't and made a new kernel to go -STABLE and
>after rebooting into the new kernel I noticed this happens..
>
>
>Mar 27 00:29:13 he /kernel: real memory  = 268435456 (262144K bytes)
>Mar 27 00:29:13 he /kernel: config> di psm0
>Mar 27 00:29:13 he /kernel: No such device: psm0
>Mar 27 00:29:13 he /kernel: Invalid command or syntax.  Type `?' for help.
>Mar 27 00:29:13 he /kernel: config> di sio1
>Mar 27 00:29:13 he /kernel: No such device: sio1
>Mar 27 00:29:13 he /kernel: Invalid command or syntax.  Type `?' for help.
>Mar 27 00:29:13 he /kernel: config> di sio0
>Mar 27 00:29:13 he /kernel: No such device: sio0
>Mar 27 00:29:13 he /kernel: Invalid command or syntax.  Type `?' for help.
>Mar 27 00:29:13 he /kernel: config> di ppc0
>Mar 27 00:29:13 he /kernel: No such device: ppc0
>Mar 27 00:29:13 he /kernel: Invalid command or syntax.  Type `?' for help.
>Mar 27 00:29:13 he /kernel: config> di sn0
>Mar 27 00:29:13 he /kernel: No such device: sn0
>Mar 27 00:29:13 he /kernel: Invalid command or syntax.  Type `?' for help.
>Mar 27 00:29:13 he /kernel: config> di lnc0
>Mar 27 00:29:13 he /kernel: No such device: lnc0
>Mar 27 00:29:13 he /kernel: Invalid command or syntax.  Type `?' for help.
>Mar 27 00:29:13 he /kernel: config> di le0
>Mar 27 00:29:13 he /kernel: No such device: le0
>Mar 27 00:29:13 he /kernel: Invalid command or syntax.  Type `?' for help.
>Mar 27 00:29:13 he /kernel: config> di ie0
>Mar 27 00:29:13 he /kernel: No such device: ie0
>Mar 27 00:29:13 he /kernel: Invalid command or syntax.  Type `?' for help.
>Mar 27 00:29:13 he /kernel: config> di fe0
>Mar 27 00:29:13 he /kernel: No such device: fe0
>Mar 27 00:29:13 he /kernel: Invalid command or syntax.  Type `?' for help.
>Mar 27 00:29:13 he /kernel: config> di ed0
>Mar 27 00:29:13 he /kernel: No such device: ed0
>Mar 27 00:29:13 he /kernel: Invalid command or syntax.  Type `?' for help.
>Mar 27 00:29:13 he /kernel: config> di cs0
>Mar 27 00:29:13 he /kernel: No such device: cs0
>Mar 27 00:29:13 he /kernel: Invalid command or syntax.  Type `?' for help.
>Mar 27 00:29:13 he /kernel: config> di bt0
>Mar 27 00:29:13 he /kernel: No such device: bt0
>Mar 27 00:29:13 he /kernel: Invalid command or syntax.  Type `?' for help.
>Mar 27 00:29:13 he /kernel: config> di aic0
>Mar 27 00:29:13 he /kernel: No such device: aic0
>Mar 27 00:29:13 he /kernel: Invalid command or syntax.  Type `?' for help.
>Mar 27 00:29:13 he /kernel: config> di aha0
>Mar 27 00:29:13 he /kernel: No such device: aha0
>Mar 27 00:29:13 he /kernel: Invalid command or syntax.  Type `?' for help.
>Mar 27 00:29:13 he /kernel: config> di adv0
>Mar 27 00:29:13 he /kernel: No such device: adv0
>Mar 27 00:29:13 he /kernel: Invalid command or syntax.  Type `?' for help.
>Mar 27 00:29:13 he /kernel: config> q
>Mar 27 00:29:13 he /kernel: avail memory = 257024000 (251000K bytes)
>Mar 27 00:29:13 he /kernel: Preloaded elf kernel "kernel" at 0xc02eb000.
>
>Those all appear to be things that I purposely commented out of the kernel
>so I was just wondering why they are showing up there, and what I do to
>fix/get rid of that.. Did I miss or forget something in building the kernel?
>	-Aric
>

--
 Laa.



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


From owner-freebsd-stable  Mon Mar 27  3:57:22 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from avenger.alex-ua.com (nat.alex-ua.com [195.5.22.36])
	by hub.freebsd.org (Postfix) with ESMTP id 6C70837BC49
	for <freebsd-stable@freebsd.org>; Mon, 27 Mar 2000 03:56:58 -0800 (PST)
	(envelope-from qd@sea.com.ua)
Received: from qdamage.localdomain (sea1.alex-ua.com [195.5.27.118] (may be forged))
	by avenger.alex-ua.com (8.8.8/8.8.8) with ESMTP id OAA13496;
	Mon, 27 Mar 2000 14:56:50 +0300 (EEST)
	(envelope-from qd@sea.com.ua)
Received: (from qd@localhost)
	by qdamage.localdomain (8.9.3/8.9.3) id NAA01953;
	Mon, 27 Mar 2000 13:59:20 +0300 (EEST)
	(envelope-from qd)
Date: Mon, 27 Mar 2000 13:59:20 +0300
From: Valery Zamarayev <qd@sea.com.ua>
To: "Forrest W. Christian" <forrestc@iMach.com>
Cc: freebsd-stable@freebsd.org
Subject: Re: How to shutdown to single user in 4.0?
Message-ID: <20000327135920.A1937@sea.com.ua>
References: <20000327105506.A972@sea.com.ua> <Pine.BSF.4.21.0003270233090.16946-100000@workhorse.iMach.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0pre2i
In-Reply-To: <Pine.BSF.4.21.0003270233090.16946-100000@workhorse.iMach.com>
Organization: SEA Company
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Mon, Mar 27, 2000 at 02:34:33AM -0700, Forrest W. Christian wrote:
> 
> Regardless, I believe (I can't remember) that I tried killing -9 1 without
> any luck (in crashing the system, that is).

well, this world is full of mysterious things :))

-- 
Sincerely etc.  Valery Zamarayev 
http://www.sea.com.ua


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


From owner-freebsd-stable  Mon Mar 27  4:37:43 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from palamas.noc.uoa.gr (palamas.noc.uoa.gr [195.134.100.107])
	by hub.freebsd.org (Postfix) with ESMTP id E554037BC91
	for <stable@freebsd.org>; Mon, 27 Mar 2000 04:31:19 -0800 (PST)
	(envelope-from isach@noc.uoa.gr)
Received: from localhost (ilias@localhost)
	by palamas.noc.uoa.gr (8.9.3/8.9.3) with ESMTP id PAA30636
	for <stable@freebsd.org>; Mon, 27 Mar 2000 15:31:32 +0300 (EEST)
	(envelope-from isach@noc.uoa.gr)
X-Authentication-Warning: palamas.noc.uoa.gr: ilias owned process doing -bs
Date: Mon, 27 Mar 2000 15:31:32 +0300 (EEST)
From: Ilias Sachpazidis <isach@noc.uoa.gr>
X-Sender: ilias@palamas.noc.uoa.gr
To: stable@freebsd.org
Subject: Acroread4
Message-ID: <Pine.BSF.4.21.0003271521050.30367-100000@palamas.noc.uoa.gr>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


I use FreeBSD 4.0-20000320-STABLE but I cannot run acroread

palamas:~ > acroread4 
Warning: charset of fontList (*-7) does not match locale (ISO8859-1).
Floating exception(core dumped)

Core dump file is located on  
http://www.noc.uoa.gr/~isach/acroread.core.gz



Could someone tell what is going on ?


+-----------------------------------------------------------------------+
|Ilias Sachpazidis                                                      |
|                                                                       |
|Network Operations Center University of Athens                         |
|                                                                       |
|Department of Informatics,             phone : +30 1 727 ???           |
|University of Athens.                  fax   : +30 1 727 ???           |
|Panepistimioupoli, Ilissia,            email : isach@noc.uoa.gr        |
|157 84 Athens, Greece                  http://www.noc.uoa.gr/~isach/   |
+-----------------------------------------------------------------------+




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


From owner-freebsd-stable  Mon Mar 27  4:39:33 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from mel.alcatel.fr (mel.alcatel.fr [212.208.74.132])
	by hub.freebsd.org (Postfix) with ESMTP id 612C037B551
	for <freebsd-stable@FreeBSD.ORG>; Mon, 27 Mar 2000 04:39:16 -0800 (PST)
	(envelope-from Thierry.Herbelot@alcatel.fr)
Received: from aifhs10.alcatel.fr (mailhub2.alcatel.fr [155.132.188.80])
        by mel.alcatel.fr (ALCANET/SMTP) with ESMTP id OAA04919;
        Mon, 27 Mar 2000 14:36:21 +0200
From: Thierry.Herbelot@alcatel.fr
Received: from frmta003.netfr.alcatel.fr (frmta003.netfr.alcatel.fr [155.132.251.32])
        by aifhs10.alcatel.fr (ALCANET/SMTP2) with SMTP id OAA13769;
        Mon, 27 Mar 2000 14:31:50 +0200 (MET DST)
Received: by frmta003.netfr.alcatel.fr(Lotus SMTP MTA v4.6.6  (890.1 7-16-1999))  id C12568AF.004576E3 ; Mon, 27 Mar 2000 14:38:44 +0200
X-Lotus-FromDomain: ALCATEL
To: "Jim C. Nasby" <jim@nasby.net>
Cc: freebsd-stable@FreeBSD.ORG
Message-ID: <C12568AF.00457395.00@frmta003.netfr.alcatel.fr>
Date: Mon, 27 Mar 2000 14:38:31 +0200
Subject: Re: vinum drive is dead
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG



Hello,

I have  had a crash on the machine where I have a stripped vinum :
you just have to make a "fsck <vinum partition>" and all will be well

     TfH




"Jim C. Nasby" <jim@nasby.net> on 27/03/2000 10:59:56
                                                              
                                                              
                                                              
 To:      freebsd-stable@FreeBSD.ORG                          
                                                              
 cc:      (bcc: Thierry HERBELOT/FR/ALCATEL)                  
                                                              
                                                              
                                                              
 Subject: vinum drive is dead                                 
                                                              





I just suffered from a kernel panic, and the aftermath is that one of my
disks apparently got obliterated. disklabel -r da1 gives me an error
(don't remember what it is offhand), but the device itself seems ok. The
SCSI controller can read the drive (I had the controller verify the
media, it checked out ok), and the kernel recognizes it (although the
drives now show up in the order da0, da3, da2, da1 upon bootup, where it
used to be da0, 1, 2, 3).

I'm hoping that I can just re-label the drive and get back up and
running, since most everything lives on vinum raid5 plexes. The problem
is that I don't know what the proper way to do this would be. Should I
detache the affected subdisks, redo the disk, and re-attach? I'm real
hesitant to screw with things since somehow the raid plex that houses
/tmp got corrupted.

I think Greg is out of town for this week, but I'm hoping that someone
else can give me some pointers here. A vinum recovery page would be most
appreciated!!

TIA,
dB!
--
Jim C. Nasby (aka Decibel!)                                  /^\
jim@nasby.net                                               /___\
Freelance lighting designer and database developer         /  |  \
Member: Triangle Fraternity, Sports Car Club of America   /___|___\

Give your computer some brain candy! www.distributed.net Team #1828
Get paid to surf!! http://www.enteract.com/~nasby/alladvantage.html


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





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


From owner-freebsd-stable  Mon Mar 27  5:37:44 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from calvin.augustsson.net (calvin.augustsson.net [193.12.107.25])
	by hub.freebsd.org (Postfix) with ESMTP id 5EE2F37BCA8
	for <stable@freebsd.org>; Mon, 27 Mar 2000 05:37:40 -0800 (PST)
	(envelope-from lennart@augustsson.net)
Received: from augustsson.net (opus.augustsson.net [192.168.1.4])
	by calvin-local.augustsson.net (8.9.3/8.9.3) with ESMTP id AAA01013;
	Sat, 25 Mar 2000 00:01:37 +0100 (CET)
Message-ID: <38DBF3D0.A28BCAAF@augustsson.net>
Date: Sat, 25 Mar 2000 00:01:37 +0100
From: Lennart Augustsson <lennart@augustsson.net>
Organization: Home, sweet home
X-Mailer: Mozilla 4.7 [en] (X11; I; NetBSD 1.4W i386)
X-Accept-Language: en
MIME-Version: 1.0
To: usb-bsd@egroups.com
Cc: stable@freebsd.org
Subject: Re: [usb-bsd] USB error messages talking to D-Link DSB-H3E under 
 FreeBSD4.0
References: <RAA01871.200003242253@garotte.eng.us.uu.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

"Josh M. Osborne" wrote:

> On my brand spanking new 4.0 system (installed so I can try some USB
> stuff) I get the following from the kernel:
>
> ohci0: <AMD-756 USB Controller> mem 0xe6100000-0xe6100fff irq 12 at device 7 on pci0
> usb0: OHCI version 1.0, legacy support
> usb0: <AMD-756 USB Controller> on ohci0
> usb0: USB revision 1.0
> uhub0: AMD OHCI root hub, class 9/0, rev 1.00/1.00, addr 1
> uhub0: 4 ports with 4 removable, self powered
> uhub1: Texas Instruments UT-USB41 hub, class 9/0, rev 1.10/1.10, addr 2
> uhub1: 4 ports with 4 removable, self powered
> uhub1: port 4, set config at addr 3 failed
> uhub1: device problem, disabling port 4
>
> The usb0 and uhub0 are (I assume) part of my motherbord, a Gigabyte
> 7IX.  The "uhub1" is a D-Link "DSB-H3E", which is 3 USB ports and
> an itegrated 10baseT Ethernet part (I think the ethernet is a
> Kawasaki LSI KU5KUSB101B part).

I don't understand the error message you get, but the Kawasaki driver
as distributed with FreeBSD doesn't work with the OHCI conbtroller.

--

        -- Lennart





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


From owner-freebsd-stable  Mon Mar 27  5:47:50 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from web1.allunix.com (17.93.rsvl.dsl.quiknet.com [207.231.93.17])
	by hub.freebsd.org (Postfix) with ESMTP
	id 72D9037BB43; Mon, 27 Mar 2000 05:47:45 -0800 (PST)
	(envelope-from dave@allunix.com)
Received: from laptop ([192.168.3.5])
	by web1.allunix.com (8.9.3/8.9.3) with ESMTP id FAA01289;
	Mon, 27 Mar 2000 05:52:14 -0800 (PST)
	(envelope-from dave@allunix.com)
Message-Id: <200003271352.FAA01289@web1.allunix.com>
From: dave@allunix.com
To: freebsd-isp@freebsd.org
Date: Mon, 27 Mar 2000 05:57:29 +0000
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: sandbox of virtual servers
Cc: freebsd-stable@freebsd.org
X-mailer: Pegasus Mail for Windows (v3.12b)
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Has anyone out there setup a sandbox limiting users to their own 
home directories in a telnet or ftp session?

I have looked all over for docs relating to this issue. I know that 
there are ISP's out there who offer virtual servers in what I think is a 
chroot enviroment. Complete with their own sendmail and apache 
configuration files?

As I do not subscribe to the stable list, please cross post it to the 
isp or questions list.

Thank You in Advance,
David DeTinne


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


From owner-freebsd-stable  Mon Mar 27  5:59:36 2000
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 B287F37B881
	for <stable@FreeBSD.ORG>; Mon, 27 Mar 2000 05:59:33 -0800 (PST)
	(envelope-from Cy.Schubert@uumail.gov.bc.ca)
Received: (from daemon@localhost)
	by point.osg.gov.bc.ca (8.8.7/8.8.8) id FAA14580;
	Mon, 27 Mar 2000 05:58:52 -0800
Received: from passer.osg.gov.bc.ca(142.32.110.29)
 via SMTP by point.osg.gov.bc.ca, id smtpda14576; Mon Mar 27 05:58:47 2000
Received: (from uucp@localhost)
	by passer.osg.gov.bc.ca (8.9.3/8.9.1) id FAA07475;
	Mon, 27 Mar 2000 05:58:46 -0800 (PST)
Received: from cwsys9.cwsent.com(10.2.2.1), claiming to be "cwsys.cwsent.com"
 via SMTP by passer9.cwsent.com, id smtpdpd7473; Mon Mar 27 05:58:01 2000
Received: (from uucp@localhost)
	by cwsys.cwsent.com (8.9.3/8.9.1) id FAA02567;
	Mon, 27 Mar 2000 05:58:01 -0800 (PST)
Message-Id: <200003271358.FAA02567@cwsys.cwsent.com>
Received: from localhost.cwsent.com(127.0.0.1), claiming to be "cwsys"
 via SMTP by localhost.cwsent.com, id smtpdle2505; Mon Mar 27 05:57:08 2000
X-Mailer: exmh version 2.1.1 10/15/1999
Reply-To: Cy Schubert - ITSD Open Systems Group <Cy.Schubert@uumail.gov.bc.ca>
From: Cy Schubert - ITSD Open Systems Group <Cy.Schubert@uumail.gov.bc.ca>
X-OS: FreeBSD 3.4-RELEASE
X-Sender: cy
To: Ilias Sachpazidis <isach@noc.uoa.gr>
Cc: stable@FreeBSD.ORG
Subject: Re: Acroread4 
In-reply-to: Your message of "Mon, 27 Mar 2000 15:31:32 +0300."
             <Pine.BSF.4.21.0003271521050.30367-100000@palamas.noc.uoa.gr> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 27 Mar 2000 05:57:08 -0800
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

In message <Pine.BSF.4.21.0003271521050.30367-100000@palamas.noc.uoa.gr>
, Ilias
 Sachpazidis writes:
> 
> I use FreeBSD 4.0-20000320-STABLE but I cannot run acroread
> 
> palamas:~ > acroread4 
> Warning: charset of fontList (*-7) does not match locale (ISO8859-1).
> Floating exception(core dumped)
> 
> Core dump file is located on  
> http://www.noc.uoa.gr/~isach/acroread.core.gz
> 
> 
> 
> Could someone tell what is going on ?

I don't think this is a 4.0 issue.  I get the same on a couple of 3.4R 
systems, minus the locale message.


Regards,                       Phone:  (250)387-8437
Cy Schubert                      Fax:  (250)387-5766
Team Leader, Sun/DEC Team   Internet:  Cy.Schubert@osg.gov.bc.ca
Open Systems Group, ITSD, ISTA
Province of BC





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


From owner-freebsd-stable  Mon Mar 27  6:16:44 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from alydar.infoteam.com (alydar.infoteam.com [207.246.83.5])
	by hub.freebsd.org (Postfix) with ESMTP id 9138A37BB46
	for <freebsd-stable@freebsd.org>; Mon, 27 Mar 2000 06:16:42 -0800 (PST)
	(envelope-from kmartin@infoteam.com)
Received: from infoteam.net (localhost.infoteam.com [127.0.0.1])
	by alydar.infoteam.com (Postfix) with SMTP id D546B5DFE
	for <freebsd-stable@freebsd.org>; Mon, 27 Mar 2000 09:16:40 -0500 (EST)
To: freebsd-stable@freebsd.org
Subject: Re: sandbox of virtual servers
From: Kenn Martin <kmartin@infoteam.com>
X-Mailer: TWIG 2.2.2
Reply-To: kmartin@infoteam.com
Message-Id: <20000327141640.D546B5DFE@alydar.infoteam.com>
Date: Mon, 27 Mar 2000 09:16:40 -0500 (EST)
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

dave@allunix.com said: 

> Has anyone out there setup a sandbox limiting users to their own 
> home directories in a telnet or ftp session?
> 
> I have looked all over for docs relating to this issue. I know that 
> there are ISP's out there who offer virtual servers in what I think 
is a 
> chroot enviroment. Complete with their own sendmail and apache 
> configuration files?
> 
> As I do not subscribe to the stable list, please cross post it to 
the 
> isp or questions list.
> 
> Thank You in Advance,
> David DeTinne

For telnet/ssh, you can use the rbash shell (install the bash port).
For ftp, it depends upon which daemon you use.  ProFTPd has a
directive that works nicely; the default FreeBSD daemon uses
/etc/ftpchroot.

kenn

________________________powered by InfoTeam____ http://infoteam.net



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


From owner-freebsd-stable  Mon Mar 27  6:53: 1 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from jade.chc-chimes.com (jade.chc-chimes.com [216.28.46.6])
	by hub.freebsd.org (Postfix) with ESMTP id E4BDE37BC05
	for <stable@freebsd.org>; Mon, 27 Mar 2000 06:52:58 -0800 (PST)
	(envelope-from billf@jade.chc-chimes.com)
Received: by jade.chc-chimes.com (Postfix, from userid 1001)
	id B83FF1C4A; Mon, 27 Mar 2000 09:52:57 -0500 (EST)
Date: Mon, 27 Mar 2000 09:52:57 -0500
From: Bill Fumerola <billf@chc-chimes.com>
To: Lennart Augustsson <lennart@augustsson.net>
Cc: usb-bsd@egroups.com, stable@freebsd.org
Subject: Re: [usb-bsd] USB error messages talking to D-Link DSB-H3E under FreeBSD4.0
Message-ID: <20000327095257.A25438@jade.chc-chimes.com>
References: <RAA01871.200003242253@garotte.eng.us.uu.net> <38DBF3D0.A28BCAAF@augustsson.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0i
In-Reply-To: <38DBF3D0.A28BCAAF@augustsson.net>; from lennart@augustsson.net on Sat, Mar 25, 2000 at 12:01:37AM +0100
X-Operating-System: FreeBSD 3.2-RELEASE i386
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Sat, Mar 25, 2000 at 12:01:37AM +0100, Lennart Augustsson wrote:

> I don't understand the error message you get, but the Kawasaki driver
> as distributed with FreeBSD doesn't work with the OHCI conbtroller.

Speaking as someone who has both of the above, why? 

I'm sure the driver's author would like to know.

-- 
Bill Fumerola - Network Architect
Computer Horizons Corp - CVM
e-mail: billf@chc-chimes.com / billf@FreeBSD.org
Office: 800-252-2421 x128 / Cell: 248-761-7272





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


From owner-freebsd-stable  Mon Mar 27  7:13:41 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from europe.std.com (europe.std.com [199.172.62.20])
	by hub.freebsd.org (Postfix) with ESMTP id 9D01737B5F6
	for <freebsd-stable@freebsd.org>; Mon, 27 Mar 2000 07:13:28 -0800 (PST)
	(envelope-from kwc@world.std.com)
Received: from world.std.com (root@world-f.std.com [199.172.62.5])
	by europe.std.com (8.9.3/8.9.3) with ESMTP id KAA11456;
	Mon, 27 Mar 2000 10:13:25 -0500 (EST)
Received: (from kwc@localhost)
	by world.std.com (8.9.3/8.9.3) id KAA18256;
	Mon, 27 Mar 2000 10:09:19 -0500 (EST)
Date: Mon, 27 Mar 2000 10:09:19 -0500 (EST)
From: Kenneth W Cochran <kwc@world.std.com>
Message-Id: <200003271509.KAA18256@world.std.com>
To: Matt Loschert <loschert@servint.com>
Subject: Re: Questions source-upgrading 3.4-s to 4.0-s
Cc: freebsd-stable@freebsd.org
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

>From loschert@servint.com  Sat Mar 25 00:14:38 2000
>Date: Sat, 25 Mar 2000 00:11:44 -0500 (EST)
>Subject: Re: Questions source-upgrading 3.4-s to 4.0-s
>
>On Fri, 24 Mar 2000, Kenneth W Cochran wrote:
>> So buildworld runs in its "own complete isolated" environment?
>> IOW, buildworld uses its "own" tools, etc., & doesn't need ie.
>> /bin, /usr/bin ...  ??  (Except for a few basic things, like the
>> compiler (with which to "bootstrap" itself?"...  :)
>
>Exactly.  The only time there are snags is when an install or
>building tool is not included in the world building tool chain.
>AFAIK, this is the reason for the installworld -DNOINFO hack.
>install-info is not part of the build chain, but the install
>relies upon it (and in the case of the 3.x->4.0 upgrade, it
>relies on a new feature for the version not yet installed on the
>system).  I could be mistaken on this point, but this is how I
>interpreted the discussion on -current.

Hmmm...  Ok...

>> >cvs-crypto
>>
>> UPDATING says "Crypto & secure are now required."  That, as I
>> understand would be src-crypto and src-secure.  How would these
>> differ from cvs-crypto?  Ie. would it be "better" to use those 2
>> "tags" or to use the one cvs-crypto?  I suppose what I may be
>> asking is "how do I make my new system look most like the
>> distributed CDs?"
>
>As mentioned in another reply, cvs-crypto is simply a crypto
>catch-all tag.  I prefer it because I want all crypto and thus I
>see it as cleaner.  It's just personal preference though.

Okay, here are the crypto tags "as I understand" so far (someone
please update/correct this):

cvs-crypto	"catch-all;" includes all the following 3

src-crypto	Userland stuff?

src-secure	Userland different stuff?  :)

src-sys-crypto	Kernel crypto?  Required for IPv6?

I would guess that the reason(s) that "Crypto & secure are now
required" would be to support IPv6 (src-sys-crupto, not needed
if you're not configuring IPv6) & to support the "new" OpenSSH
(what tags for that?).

I would also guess that now that OpenSSH has been "merged" (?)
into the main source tree, it will install someplace besides
/usr/local/* (where SSH1/2 both happen to be)?

So now, what is the "status" of the "export restricted" stuff,
wrt with the recent changes in export controls?  I guess what I
may be asking is the following:

1.  What was (& now is) export restricted to start with?
2.  What was (& now is) different about what you get if you use
    the "international" cvsup site?  (using the
    secure-stable-supfile as an example; apparently it only
    fetches crypto)

>> >If you want the latest ports collection and documentation, specify:
>> >ports-all tag=.
>> >doc-all   tag=.
>>
>> I do that with a separate cvsup file/job...
>
>Why?  Cvsup ports and docs more or less often?  I just lump them

Yup.  Somewhat because of speed/reliablilty problems with my
connection(s), it is "easier" for me to update my system in
"smaller" pieces...

>all into my sup-file, along with src-all and cvs-crypto for
>RELENG_3, RELENG_4, and -CURRENT, all going into different
>directories.  That way I can read through the source changes to
>all of the active branches, or upgrade/downgrade any way I want.

Hmmm, interesting...

[...]
>> >cd /usr/src/sbin/mknod && make install
>>
>> Along the lines of "dotting all the "i"s & "crossong all the
>> "t"s", I believe it would be a Good Idea to make this more
>> explicit in the instructions...  :)
>
>Warner Losh is the man in charge of the UPDATING file.  You
>might want to pass the suggestion along to him.

I hope he is already reading this thread?  :)

[...]
>> >For the upgrade, yes, install GENERIC.  Once you have rebooted
>> >after the upgrade, it is much safer to rebuild your custom kernel.
>>
>> So, substitute GENERIC for "YOUR_KERNEL_HERE?"
>
>GENERIC for the initial upgrade kernel, YOUR_KERNEL_HERE after
>upgrade complete.

After upgrading (& with 4.x) am I required to use those new make
targets or can I do it the Good Old-fashioned Way?  (cd
/sys/i386/conf; <edit config>; config <...>; cd
/sys/compile/...; make dep; make; make install)

>> I think it would be a Very Good Idea to get "appropriate
>> portions" of this information into the UPDATING instructions; it
>> might help slow down the upgrading-deluge "here" on -stable...  :)
>
>Again, send your suggestions to Warner Losh <imp@village.org>.
>He maintains the UPDATING file.

I hope he's reading...  :)

>Enjoy 4.0.

Thanks, I plan to.  :)  Speaking of which, will things like
XFree86 3.3.5 (as distributed with the 3.4 CD set) run ok with
4.x or must I recompile or upgrade it as well?

>- Matt

-kc


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


From owner-freebsd-stable  Mon Mar 27  7:15:49 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from calvin.augustsson.net (calvin.augustsson.net [193.12.107.25])
	by hub.freebsd.org (Postfix) with ESMTP id 294AE37BCDD
	for <stable@freebsd.org>; Mon, 27 Mar 2000 07:15:22 -0800 (PST)
	(envelope-from lennart@augustsson.net)
Received: from augustsson.net (opus.augustsson.net [192.168.1.4])
	by calvin.augustsson.net (8.9.3/8.9.3) with ESMTP id RAA13555;
	Mon, 27 Mar 2000 17:14:53 +0200 (CEST)
Message-ID: <38DF7AEC.B9DA1AF1@augustsson.net>
Date: Mon, 27 Mar 2000 17:14:53 +0200
From: Lennart Augustsson <lennart@augustsson.net>
Organization: Home, sweet home
X-Mailer: Mozilla 4.7 [en] (X11; I; NetBSD 1.4X i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Bill Fumerola <billf@chc-chimes.com>
Cc: usb-bsd@egroups.com, stable@freebsd.org
Subject: Re: [usb-bsd] USB error messages talking to D-Link DSB-H3E under 
 FreeBSD4.0
References: <RAA01871.200003242253@garotte.eng.us.uu.net> <38DBF3D0.A28BCAAF@augustsson.net> <20000327095257.A25438@jade.chc-chimes.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Bill Fumerola wrote:

> On Sat, Mar 25, 2000 at 12:01:37AM +0100, Lennart Augustsson wrote:
>
> > I don't understand the error message you get, but the Kawasaki driver
> > as distributed with FreeBSD doesn't work with the OHCI conbtroller.
>
> Speaking as someone who has both of the above, why?
>
> I'm sure the driver's author would like to know.

Well, with *my* OHCI controller the Ethernet adapter wedges when the
driver tries to determine if it is being cold booted or not.  Doing a control
transfer with USBD_SHORT_XFER_OK behaves differently on UHCI
and OHCI it seems.  The UHCI driver aborts the status stage, but the OHCI
driver doesn't.
I've changed the way cold boot is tested and now it works for me.

--

        -- Lennart





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


From owner-freebsd-stable  Mon Mar 27  7:58:51 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from atlrel2.hp.com (atlrel2.hp.com [156.153.255.202])
	by hub.freebsd.org (Postfix) with ESMTP
	id CA0F337B655; Mon, 27 Mar 2000 07:58:41 -0800 (PST)
	(envelope-from steve@sse0691.bri.hp.com)
Received: from sse0691.bri.hp.com (sse0691.bri.hp.com [15.144.0.53])
	by atlrel2.hp.com (Postfix) with ESMTP
	id 9752FB0C; Mon, 27 Mar 2000 10:58:13 -0500 (EST)
Received: (from steve@localhost)
	by sse0691.bri.hp.com (8.9.3/8.9.3) id QAA31265;
	Mon, 27 Mar 2000 16:56:29 +0100 (BST)
	(envelope-from steve)
Date: Mon, 27 Mar 2000 16:56:29 +0100
From: Steve Roome <steve@sse0691.bri.hp.com>
To: Conrad Sabatier <conrads@home.com>
Cc: multimedia@freebsd.org, stable@freebsd.org
Subject: Re: What does "Voxware still supported in 4.0" mean exactly?
Message-ID: <20000327165629.B29833@moose.bri.hp.com>
References: <38DC55BC.BA2240C2@newsguy.com> <XFMail.000326181923.conrads@home.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0.1i
In-Reply-To: <XFMail.000326181923.conrads@home.com>; from conrads@home.com on Sun, Mar 26, 2000 at 06:19:23PM -0600
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Sun, Mar 26, 2000 at 06:19:23PM -0600, Conrad Sabatier wrote:
> I wish I could help with the development of the pcm driver,

Me too, as I mentioned on the -mmedia list (at the beginning of this
thread last week!, I gave away my AWE card because it wasn't supported.

I think there's a lot of folks who are willing to help test, and work
on the various sound drivers . It just seems to need co-ordinating
such that people can all help in a constructive way.

Anyway, perhaps this sound driver stuff should wrap up and mosey on
back to the -multimedia list, and perhaps we should look at sorting
out what we all want and get everyone who can to help in whatever way
they can.. Then we'll have awe in pcm, and midi, and mmapped buffers,
and everything else we might want - but only if we can work on it
rather than have such a lot of useless vitriol on the mailing lists!

	Steve

... and I won't have to swap my new sb16pci (es1373) out for an
archaic ISA card to play gl-quake - which seems like an odd solution!

[ sorry for crossposting, but hopefully we could move this back to -mm
this way and make it a constructive conversation- here's hoping ]


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


From owner-freebsd-stable  Mon Mar 27  8: 5:48 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from mecca.servint.com (mecca.servint.com [209.50.225.14])
	by hub.freebsd.org (Postfix) with ESMTP id CD57437B9BC
	for <freebsd-stable@freebsd.org>; Mon, 27 Mar 2000 08:05:39 -0800 (PST)
	(envelope-from loschert@servint.com)
Received: from delft.servint.com (207-172-244-45.s45.tnt4.rcm.va.dialup.rcn.com [207.172.244.45])
	by mecca.servint.com (8.9.3/8.9.0) with ESMTP id LAA16762
	for <freebsd-stable@freebsd.org>; Mon, 27 Mar 2000 11:25:05 -0500 (EST)
Received: (qmail 6295 invoked by uid 1000); 27 Mar 2000 16:05:27 -0000
Received: from localhost (sendmail-bs@127.0.0.1)
  by localhost with SMTP; 27 Mar 2000 16:05:27 -0000
Date: Mon, 27 Mar 2000 11:05:27 -0500 (EST)
From: Matt Loschert <loschert@servint.com>
To: Kenneth W Cochran <kwc@world.std.com>
Cc: freebsd-stable@freebsd.org
Subject: Re: Questions source-upgrading 3.4-s to 4.0-s
In-Reply-To: <200003271509.KAA18256@world.std.com>
Message-ID: <Pine.BSF.4.21.0003271059380.6284-100000@delft.servint.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Mon, 27 Mar 2000, Kenneth W Cochran wrote:

> I would guess that the reason(s) that "Crypto & secure are now
> required" would be to support IPv6 (src-sys-crupto, not needed
> if you're not configuring IPv6) & to support the "new" OpenSSH
> (what tags for that?).

AFAIK

> I would also guess that now that OpenSSH has been "merged" (?)
> into the main source tree, it will install someplace besides
> /usr/local/* (where SSH1/2 both happen to be)?

Yes, /usr/bin.  You will probably want to either remove these, or alter
your paths to allow you to access them, if desired.

> So now, what is the "status" of the "export restricted" stuff,
> wrt with the recent changes in export controls?  I guess what I
> may be asking is the following:
> 
> 1.  What was (& now is) export restricted to start with?
> 2.  What was (& now is) different about what you get if you use
>     the "international" cvsup site?  (using the
>     secure-stable-supfile as an example; apparently it only
>     fetches crypto)

Not exactly sure, check the mail archives if you are really curious.  
Otherwise, just set your /etc/make.conf file appropriately, cvsup from the
appropriate host, and you should be fine.

> After upgrading (& with 4.x) am I required to use those new make
> targets or can I do it the Good Old-fashioned Way?  (cd
> /sys/i386/conf; <edit config>; config <...>; cd
> /sys/compile/...; make dep; make; make install)

You should be able to do it the old fashioned way, because at that point
all of the supporting tools for 4.0 have been installed.

> Thanks, I plan to.  :)  Speaking of which, will things like
> XFree86 3.3.5 (as distributed with the 3.4 CD set) run ok with
> 4.x or must I recompile or upgrade it as well?

Not sure, I haven't tried X on an upgraded box yet.

- Matt

--
Matt Loschert                           loschert@servint.com
Software Engineer                       voice (703) 847-1381
ServInt Internet Services               fax   (703) 847-1383





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


From owner-freebsd-stable  Mon Mar 27  8:19: 0 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from elwood.akitanet.co.uk (elwood.akitanet.co.uk [212.1.130.149])
	by hub.freebsd.org (Postfix) with ESMTP
	id 57C4E37B918; Mon, 27 Mar 2000 08:18:03 -0800 (PST)
	(envelope-from wigstah@akitanet.co.uk)
Received: from elwood.akitanet.co.uk (elwood.akitanet.co.uk [212.1.130.149])
	by elwood.akitanet.co.uk (8.9.3/8.9.1) with ESMTP id RAA45458;
	Mon, 27 Mar 2000 17:16:48 +0100 (BST)
Date: Mon, 27 Mar 2000 17:16:48 +0100 (BST)
From: Paul Robinson <wigstah@akitanet.co.uk>
To: dave@allunix.com
Cc: freebsd-isp@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG
Subject: Re: sandbox of virtual servers
In-Reply-To: <200003271352.FAA01289@web1.allunix.com>
Message-ID: <Pine.BSF.4.10.10003271709330.44309-100000@elwood.akitanet.co.uk>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Mon, 27 Mar 2000 dave@allunix.com wrote:

> Has anyone out there setup a sandbox limiting users to their own 
> home directories in a telnet or ftp session?

You mean a chroot(2) environemnt? I.e. you stop users getting out of their
own hom directory? Are you talking more about the jail() call in FreeBSD
4.0?

If all you need is to chroot them, take a look at the OpenBSD ftpd, or in
fact proftpd, wu-ftpd etc. If you need to stop them running all over the
place in telnet, then you need to write a restricted shell, although I
hear there is already one around whose name escapes me.

As far as sandboxing is concerned in terms of CGI's and so on, the best
webserver I know to handle this is Zeus (which costs around $1500 but is
worth every penny). Not only will it sandbox the CGI for you, but it also
is easily around 5-10 times faster than Apache in my experience. It also
has better stats, can handle a theoretical infinte number of virtual
servers, and is generally far easier ot configure, run and maintain than
any other piece of software I've encountered in the ISP game. Don't work
for them, but I do like their code... :) they're at www.zeustechnology.com
 
> chroot enviroment. Complete with their own sendmail and apache 
> configuration files?

Sounds like jail() which is not really marked for production use at the
moment as I understand it. I've also heard a whisper that some of the
nasty hax0rs out there have already managed to find a way to break it,
although that could all be just smoke and mirrors... :)
 
> As I do not subscribe to the stable list, please cross post it to the 
> isp or questions list.

If you don't subscribe to a list, don't post to it. It's rude. I'm almost
tempted to not cross-post it, just to annoy you as much as that statement
has annoyed me. :)
 
-- 
Paul Robinson - Developer/Systems Administrator @ Akitanet Internet



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


From owner-freebsd-stable  Mon Mar 27  9:45: 2 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from sabre.velocet.net (sabre.velocet.net [198.96.118.66])
	by hub.freebsd.org (Postfix) with ESMTP id B671F37B920
	for <freebsd-stable@freebsd.org>; Mon, 27 Mar 2000 09:44:43 -0800 (PST)
	(envelope-from dgilbert@office.tor.velocet.net)
Received: from office.tor.velocet.net (trooper.velocet.net [216.126.82.226])
	by sabre.velocet.net (Postfix) with ESMTP id A50F6137FE5
	for <freebsd-stable@freebsd.org>; Mon, 27 Mar 2000 12:44:40 -0500 (EST)
Received: (from dgilbert@localhost)
	by office.tor.velocet.net (8.9.3/8.9.3) id MAA21594;
	Mon, 27 Mar 2000 12:44:35 -0500 (EST)
	(envelope-from dgilbert)
From: David Gilbert <dgilbert@velocet.ca>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <14559.40450.544687.51037@trooper.velocet.net>
Date: Mon, 27 Mar 2000 12:44:34 -0500 (EST)
To: freebsd-stable@freebsd.org
Subject: 4.0-STABLE dhcp conflicts.
X-Mailer: VM 6.75 under 20.4 "Emerald" XEmacs  Lucid
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

It appears that when I run two (not sure if one does it) tcpdumps on
the dhcp server, the dhcp clients don't get any responses to their
queries.  Is there some flaw in the dhcpd bpf rules?

Dave.

-- 
============================================================================
|David Gilbert, Velocet Communications.       | Two things can only be     |
|Mail:       dgilbert@velocet.net             |  equal if and only if they |
|http://www.velocet.net/~dgilbert             |   are precisely opposite.  |
=========================================================GLO================


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


From owner-freebsd-stable  Mon Mar 27 10: 4:57 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from account.abs.net (account.abs.net [207.114.5.70])
	by hub.freebsd.org (Postfix) with ESMTP
	id 9A93E37B918; Mon, 27 Mar 2000 10:04:44 -0800 (PST)
	(envelope-from howardl@account.abs.net)
Received: (from howardl@localhost)
	by account.abs.net (8.9.3/8.9.3+RBL+DUL+RSS+ORBS) id NAA94040;
	Mon, 27 Mar 2000 13:04:42 -0500 (EST)
	(envelope-from howardl)
From: Howard Leadmon <howardl@account.abs.net>
Message-Id: <200003271804.NAA94040@account.abs.net>
Subject: Troubles with network & buffers..  Any Ideas??
To: freebsd-stable@freebsd.org, freebsd-hackers@freebsd.org
Date: Mon, 27 Mar 2000 13:04:42 -0500 (EST)
X-Mailer: ELM [version 2.4ME+ PL72 (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, I am running a 4.0-STABLE machine which is being used to host an
Undernet IRC server, and the machine keeps dying at times, or should I say
the networking side of it is at least dying.  At first I thought it might
have been related to the dc (DEC Chip) based drivers, so I replaced it with
a EEpro board using the fxp driver, but the same results.  

 I have also set MNBCLUSTERS to 20480, and when I do a netstat I see in
general plenty of free clusters, but suspect I must be running out of some
other resource.  If I do a netstat -m, I see info like this:

u2$ netstat -m
1697/2144/81920 mbufs in use (current/peak/max):
        498 mbufs allocated to data
        1199 mbufs allocated to packet headers
221/514/20480 mbuf clusters in use (current/peak/max)
1296 Kbytes allocated to network (50% in use)
0 requests for memory denied
0 requests for memory delayed
0 calls to protocol drain routines


When the machine last froze, the Kbytes allocated to the network was 99% in 
use, and the mbufs were up to about 20K of the 80K allocated, but I saw no
calls for memory denied or delayed.

Still after a few hours of uptime, I start seeing errors like this, and then
the machines network interface dies and I have to reboot to get everything
back in operation:

Mar 27 12:39:00 u2 /kernel: fxp0: device timeout
Mar 27 12:39:00 u2 syslogd: sendto: No buffer space available
Mar 27 12:39:38 u2 last message repeated 2 times
Mar 27 12:41:32 u2 last message repeated 6 times
Mar 27 12:44:15 u2 syslogd: sendto: No buffer space available
Mar 27 12:44:04 u2 last message repeated 8 times


Not sure what other information to send, but here is a dmesg on the machine,
and if anyone has any ideas, or needs more info please let me know.  It's
very annoying to have to reboot this machine daily, sometimes more often.. :(

Copyright (c) 1992-2000 The FreeBSD Project.
Copyright (c) 1982, 1986, 1989, 1991, 1993
        The Regents of the University of California. All rights reserved.
FreeBSD 4.0-STABLE #8: Wed Mar 22 18:31:51 EST 2000
    howardl@u2.abs.net:/usr/src/sys/compile/U2
Timecounter "i8254"  frequency 1193182 Hz
CPU: Pentium II/Pentium II Xeon/Celeron (551.25-MHz 686-class CPU)
  Origin = "GenuineIntel"  Id = 0x665  Stepping = 5
  Features=0x183fbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR>
real memory  = 402587648 (393152K bytes)
config> q
avail memory = 387022848 (377952K bytes)
Programming 24 pins in IOAPIC #0
IOAPIC #0 intpin 2 -> irq 0
FreeBSD/SMP: Multiprocessor motherboard
 cpu0 (BSP): apic id:  0, version: 0x00040011, at 0xfee00000
 cpu1 (AP):  apic id:  1, version: 0x00040011, at 0xfee00000
 io0 (APIC): apic id:  2, version: 0x00170011, at 0xfec00000
Preloaded elf kernel "kernel" at 0xc02c8000.
Preloaded userconfig_script "/boot/kernel.conf" at 0xc02c809c.
Pentium Pro MTRR support enabled
md0: Malloc disk
npx0: <math processor> on motherboard
npx0: INT 16 interface
pcib0: <Intel 82443BX (440 BX) host to PCI bridge> on motherboard
pci0: <PCI bus> on pcib0
pcib1: <Intel 82443BX (440 BX) PCI-PCI (AGP) bridge> at device 1.0 on pci0
pci1: <PCI bus> on pcib1
isab0: <Intel 82371AB PCI to ISA bridge> at device 7.0 on pci0
isa0: <ISA bus> on isab0
atapci0: <Intel PIIX4 ATA33 controller> port 0xf000-0xf00f at device 7.1 on pci0
ata0: at 0x1f0 irq 14 on atapci0
pci0: <Intel 82371AB/EB (PIIX4) USB controller> at 7.2 irq 5
Timecounter "PIIX"  frequency 3579545 Hz
chip1: <Intel 82371AB Power management controller> port 0x5000-0x500f at device 7.3 on pci0
fxp0: <Intel EtherExpress Pro 10/100B Ethernet> port 0xd400-0xd41f mem 0xd5400000-0xd54fffff,0xd5510000-0xd5510fff irq 17 at device 13.0 on pci0
fxp0: Ethernet address 00:a0:c9:c7:fb:ff
pci0: <Trident model 9660 VGA-compatible display device> at 15.0 irq 16
atapci1: <HighPoint HPT366 ATA66 controller> port 0xe000-0xe0ff,0xdc00-0xdc03,0xd800-0xd807 irq 18 at device 19.0 on pci0
atapci2: <HighPoint HPT366 ATA66 controller> port 0xec00-0xecff,0xe800-0xe803,0xe400-0xe407 irq 18 at device 19.1 on pci0
fdc0: <NEC 72065B or clone> at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0
fdc0: FIFO enabled, 8 bytes threshold
fd0: <1440-KB 3.5" drive> on fdc0 drive 0
atkbdc0: <keyboard controller (i8042)> at port 0x60-0x6f on isa0
atkbd0: <AT Keyboard> irq 1 on atkbdc0
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
sc0: <System console> on isa0
sc0: VGA <16 virtual consoles, flags=0x200>
sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
sio0: type 16550A
sio1 at port 0x2f8-0x2ff irq 3 on isa0
sio1: type 16550A
ppc0: <Parallel port> at port 0x378-0x37f irq 7 on isa0
ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode
ppi0: <Parallel I/O> on ppbus0
lpt0: <Printer> on ppbus0
lpt0: Interrupt-driven port
plip0: <PLIP network interface> on ppbus0
APIC_IO: Testing 8254 interrupt delivery
APIC_IO: routing 8254 via IOAPIC #0 intpin 2
SMP: AP CPU #1 Launched!
ad0: 8693MB <ST39140A> [17662/16/63] at ata0-master using UDMA33
Mounting root from ufs:/dev/ad0s1a



---
Howard Leadmon - howardl@abs.net - http://www.abs.net
ABSnet Internet Services - Phone: 410-361-8160 - FAX: 410-361-8162



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


From owner-freebsd-stable  Mon Mar 27 10: 9: 5 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from mail.enteract.com (mail.enteract.com [207.229.143.33])
	by hub.freebsd.org (Postfix) with ESMTP id 3BEC937B8D2
	for <freebsd-stable@FreeBSD.ORG>; Mon, 27 Mar 2000 10:08:57 -0800 (PST)
	(envelope-from nasby@shell-1.enteract.com)
Received: from shell-1.enteract.com (nasby@shell-1.enteract.com [207.229.143.40])
	by mail.enteract.com (8.9.3/8.9.3) with ESMTP id MAA94001
	for <freebsd-stable@FreeBSD.ORG>; Mon, 27 Mar 2000 12:08:55 -0600 (CST)
	(envelope-from nasby@shell-1.enteract.com)
Received: (from nasby@localhost)
	by shell-1.enteract.com (8.9.3/8.9.3) id MAA63974
	for freebsd-stable@FreeBSD.ORG; Mon, 27 Mar 2000 12:08:55 -0600 (CST)
	(envelope-from nasby)
Date: Mon, 27 Mar 2000 12:08:55 -0600
From: "Jim C. Nasby" <jim@nasby.net>
To: freebsd-stable@FreeBSD.ORG
Subject: Re: vinum drive is dead
Message-ID: <20000327120854.A46955@enteract.com>
Reply-To: jim@nasby.net
Mail-Followup-To: freebsd-stable@FreeBSD.ORG
References: <C12568AF.00457395.00@frmta003.netfr.alcatel.fr>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0pre3i
In-Reply-To: <C12568AF.00457395.00@frmta003.netfr.alcatel.fr>
X-Operating-System: FreeBSD 3.3-STABLE i386
X-Distributed: Join the Effort!  http://www.distributed.net
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

There are blocks that fsck reports as un-readable. I'm hoping that this is
because the dead drive is still attached to the plex.

On Mon, Mar 27, 2000 at 02:38:31PM +0200, Thierry.Herbelot@alcatel.fr wrote:
> 
> 
> Hello,
> 
> I have  had a crash on the machine where I have a stripped vinum :
> you just have to make a "fsck <vinum partition>" and all will be well
> 
>      TfH
> 
> 
> 
> 
> "Jim C. Nasby" <jim@nasby.net> on 27/03/2000 10:59:56
>                                                               
>                                                               
>                                                               
>  To:      freebsd-stable@FreeBSD.ORG                          
>                                                               
>  cc:      (bcc: Thierry HERBELOT/FR/ALCATEL)                  
>                                                               
>                                                               
>                                                               
>  Subject: vinum drive is dead                                 
>                                                               
> 
> 
> 
> 
> 
> I just suffered from a kernel panic, and the aftermath is that one of my
> disks apparently got obliterated. disklabel -r da1 gives me an error
> (don't remember what it is offhand), but the device itself seems ok. The
> SCSI controller can read the drive (I had the controller verify the
> media, it checked out ok), and the kernel recognizes it (although the
> drives now show up in the order da0, da3, da2, da1 upon bootup, where it
> used to be da0, 1, 2, 3).
> 
> I'm hoping that I can just re-label the drive and get back up and
> running, since most everything lives on vinum raid5 plexes. The problem
> is that I don't know what the proper way to do this would be. Should I
> detache the affected subdisks, redo the disk, and re-attach? I'm real
> hesitant to screw with things since somehow the raid plex that houses
> /tmp got corrupted.
> 
> I think Greg is out of town for this week, but I'm hoping that someone
> else can give me some pointers here. A vinum recovery page would be most
> appreciated!!
> 
> TIA,
> dB!
> --
> Jim C. Nasby (aka Decibel!)                                  /^\
> jim@nasby.net                                               /___\
> Freelance lighting designer and database developer         /  |  \
> Member: Triangle Fraternity, Sports Car Club of America   /___|___\
> 
> Give your computer some brain candy! www.distributed.net Team #1828
> Get paid to surf!! http://www.enteract.com/~nasby/alladvantage.html
> 
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-stable" in the body of the message
> 
> 
> 
> 
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-stable" in the body of the message

-- 
Jim C. Nasby (aka Decibel!)                                  /^\
jim@nasby.net                                               /___\
Freelance lighting designer and database developer         /  |  \
Member: Triangle Fraternity, Sports Car Club of America   /___|___\

Give your computer some brain-candy! www.distributed.net Team #1828
Get paid to surf!! http://www.enteract.com/~nasby/alladvantage.html


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


From owner-freebsd-stable  Mon Mar 27 10:12:13 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from vinyl.sentex.ca (vinyl.sentex.ca [209.112.4.14])
	by hub.freebsd.org (Postfix) with ESMTP id 572A637BA2E
	for <freebsd-stable@FreeBSD.ORG>; Mon, 27 Mar 2000 10:11:59 -0800 (PST)
	(envelope-from mike@sentex.ca)
Received: from simoeon (simeon.sentex.ca [209.112.4.47])
	by vinyl.sentex.ca (8.9.3/8.9.3) with SMTP id NAA50284;
	Mon, 27 Mar 2000 13:11:47 -0500 (EST)
	(envelope-from mike@sentex.ca)
Message-Id: <3.0.5.32.20000327130927.01b3d5e0@marble.sentex.ca>
X-Sender: mdtpop@marble.sentex.ca
X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32)
Date: Mon, 27 Mar 2000 13:09:27 -0500
To: Howard Leadmon <howardl@account.abs.net>,
	freebsd-stable@FreeBSD.ORG
From: Mike Tancsa <mike@sentex.ca>
Subject: Re: Troubles with network & buffers..  Any Ideas??
In-Reply-To: <200003271804.NAA94040@account.abs.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 01:04 PM 3/27/00 -0500, Howard Leadmon wrote:


>
> I have also set MNBCLUSTERS to 20480, and when I do a netstat I see in
>general plenty of free clusters, but suspect I must be running out of some
>other resource.  If I do a netstat -m, I see info like this:

What does vmstat -m show you in terms of memory hitting Limits ?

	---Mike
------------------------------------------------------------------------
Mike Tancsa,                          	          tel +1 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  Mon Mar 27 10:40:59 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from rover.village.org (rover.village.org [204.144.255.49])
	by hub.freebsd.org (Postfix) with ESMTP id 237E337BBFA
	for <freebsd-stable@FreeBSD.ORG>; Mon, 27 Mar 2000 10:40:53 -0800 (PST)
	(envelope-from imp@harmony.village.org)
Received: from harmony.village.org (harmony.village.org [10.0.0.6])
	by rover.village.org (8.9.3/8.9.3) with ESMTP id LAA55007;
	Mon, 27 Mar 2000 11:40:49 -0700 (MST)
	(envelope-from imp@harmony.village.org)
Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id LAA95110; Mon, 27 Mar 2000 11:40:32 -0700 (MST)
Message-Id: <200003271840.LAA95110@harmony.village.org>
To: Kenneth W Cochran <kwc@world.std.com>
Subject: Re: Questions source-upgrading 3.4-s to 4.0-s 
Cc: Matt Loschert <loschert@servint.com>, freebsd-stable@FreeBSD.ORG
In-reply-to: Your message of "Mon, 27 Mar 2000 10:09:19 EST."
		<200003271509.KAA18256@world.std.com> 
References: <200003271509.KAA18256@world.std.com>  
Date: Mon, 27 Mar 2000 11:40:32 -0700
From: Warner Losh <imp@village.org>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

In message <200003271509.KAA18256@world.std.com> Kenneth W Cochran writes:
: >> I think it would be a Very Good Idea to get "appropriate
: >> portions" of this information into the UPDATING instructions; it
: >> might help slow down the upgrading-deluge "here" on -stable...  :)
: >
: >Again, send your suggestions to Warner Losh <imp@village.org>.
: >He maintains the UPDATING file.
: 
: I hope he's reading...  :)

Reading, yes.  Understanding what you want changed, no.  Send me a
patch, or post it here.

Warner


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


From owner-freebsd-stable  Mon Mar 27 12:20:22 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from mail.hiwaay.net (fly.HiWAAY.net [208.147.154.56])
	by hub.freebsd.org (Postfix) with ESMTP id 3B72D37B9F4
	for <freebsd-stable@freebsd.org>; Mon, 27 Mar 2000 12:20:18 -0800 (PST)
	(envelope-from dkelly@hiwaay.net)
Received: from [10.0.0.20] (spider.interactplus.com [216.180.46.102])
	by mail.hiwaay.net (8.10.0/8.10.0) with ESMTP id e2RKKG213399
	for <freebsd-stable@freebsd.org>; Mon, 27 Mar 2000 14:20:16 -0600 (CST)
Mime-Version: 1.0
X-Sender: dkelly@hiwaay.net (Unverified)
Message-Id: <p04310103b5056e16548a@[10.0.0.20]>
Date: Mon, 27 Mar 2000 14:20:12 -0600
To: freebsd-stable@freebsd.org
From: David Kelly <dkelly@hiwaay.net>
Subject: 4.0-RELEASE (March 20) hangs at atapci0
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

My super el-cheapo (even 4 years ago) UMC chipset (UM8881F is the
only chip I can easily see) VIP PCI/VL MB with AMD 5x86/133 doesn't
like the 4.0-RELEASE kernel. Initially I had no ATA/IDE devices
attached and both IDE disabled in the AMI WinBIOS. Booting the
4.0-RELEASE floppies hangs at the ataide0 probe.

Added an old 487MB IDE HD. 4.0-RELEASE still hangs.

This is the retyped message off the screen:

atapci0 <unknown PCI ATA controller (generic mode)> port 
0xfff0-0xfff3, 0xffe0-0xffe7, 0x374-0x377, 0x170-0x177 device 18.1 on 
pci0
ata0: at 0x1f0 irq 14 on atapci0

Its been there for at least 30 minutes.

Didn't work with IDE disabled in the BIOS (FreeBSD still probed the 
hardware and ports).

Didn't work with IDE disabled in the bios and both IDE disabled in 
the full screen kernel config.

Didn't work with IDE enabled in BIOS with HD attached.

Didn't write until I searched the mail lists and re-read ERRATA.TXT,
HARDWARE.TXT, INSTALL.TXT, and TROUBLE.TXT.

Where to next? Suspect that "unknown PCI ATA controller" above is the
key to my problems.
-- 
--
David Kelly N4HHE, dkelly@hiwaay.net
========================================================================
Whom computers would destroy, they must first drive mad.


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


From owner-freebsd-stable  Mon Mar 27 12:27:14 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from workhorse.iMach.com (workhorse.iMach.com [206.127.77.89])
	by hub.freebsd.org (Postfix) with ESMTP id CF39A37BC02
	for <freebsd-stable@FreeBSD.ORG>; Mon, 27 Mar 2000 12:27:08 -0800 (PST)
	(envelope-from forrestc@workhorse.iMach.com)
Received: from localhost (forrestc@localhost)
	by workhorse.iMach.com (8.9.3/8.9.3) with ESMTP id NAA25805;
	Mon, 27 Mar 2000 13:21:35 -0700 (MST)
Date: Mon, 27 Mar 2000 13:21:33 -0700 (MST)
From: "Forrest W. Christian" <forrestc@iMach.com>
To: David Kelly <dkelly@hiwaay.net>
Cc: freebsd-stable@FreeBSD.ORG
Subject: Re: 4.0-RELEASE (March 20) hangs at atapci0
In-Reply-To: <p04310103b5056e16548a@[10.0.0.20]>
Message-ID: <Pine.BSF.4.21.0003271319410.25575-100000@workhorse.iMach.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Mon, 27 Mar 2000, David Kelly wrote:

> ata0: at 0x1f0 irq 14 on atapci0
> 
> Its been there for at least 30 minutes.

In the 3.x world, it is fairly common for it to hang right there (or
shortly after) because of some other conflict.   Can't speak for 4.0 for
sure....

Not to ask the obvious, but have you removed all of the unneccessary
devices from the visual configuration screen at boot?

- Forrest W. Christian (forrestc@imach.com) KD7EHZ
----------------------------------------------------------------------
iMach, Ltd., P.O. Box 5749, Helena, MT 59604      http://www.imach.com
Solutions for your high-tech problems.                  (406)-442-6648
----------------------------------------------------------------------



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


From owner-freebsd-stable  Mon Mar 27 12:50: 9 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from account.abs.net (account.abs.net [207.114.5.70])
	by hub.freebsd.org (Postfix) with ESMTP id 65F1F37BA7A
	for <freebsd-stable@FreeBSD.ORG>; Mon, 27 Mar 2000 12:50:05 -0800 (PST)
	(envelope-from howardl@account.abs.net)
Received: (from howardl@localhost)
	by account.abs.net (8.9.3/8.9.3+RBL+DUL+RSS+ORBS) id PAA04829;
	Mon, 27 Mar 2000 15:48:43 -0500 (EST)
	(envelope-from howardl)
From: Howard Leadmon <howardl@account.abs.net>
Message-Id: <200003272048.PAA04829@account.abs.net>
Subject: Re: Troubles with network & buffers..  Any Ideas??
In-Reply-To: <3.0.5.32.20000327130927.01b3d5e0@marble.sentex.ca> from Mike Tancsa
 at "Mar 27, 2000 01:09:27 pm"
To: Mike Tancsa <mike@sentex.ca>
Date: Mon, 27 Mar 2000 15:48:43 -0500 (EST)
Cc: freebsd-stable@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL72 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


  Thanks for the fast reply.. :)

 Needless to say the machine has been rebooted since the last time it
died, but I'll try and keep an eye on it and next time it locks if I can
get to the console I'll see if I can grab a snapshot at that time.  If a
current running snapshot is of any use just let me know..


> > I have also set MNBCLUSTERS to 20480, and when I do a netstat I see in
> >general plenty of free clusters, but suspect I must be running out of some
> >other resource.  If I do a netstat -m, I see info like this:
> 
> What does vmstat -m show you in terms of memory hitting Limits ?
> 
> 	---Mike


---
Howard Leadmon - howardl@abs.net - http://www.abs.net
ABSnet Internet Services - Phone: 410-361-8160 - FAX: 410-361-8162



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


From owner-freebsd-stable  Mon Mar 27 13: 5:20 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from vinyl.sentex.ca (vinyl.sentex.ca [209.112.4.14])
	by hub.freebsd.org (Postfix) with ESMTP id B6AEB37BD41
	for <freebsd-stable@FreeBSD.ORG>; Mon, 27 Mar 2000 13:05:16 -0800 (PST)
	(envelope-from mike@sentex.ca)
Received: from simoeon (simeon.sentex.ca [209.112.4.47])
	by vinyl.sentex.ca (8.9.3/8.9.3) with SMTP id QAA67001;
	Mon, 27 Mar 2000 16:05:03 -0500 (EST)
	(envelope-from mike@sentex.ca)
Message-Id: <3.0.5.32.20000327160242.02248880@marble.sentex.ca>
X-Sender: mdtpop@marble.sentex.ca
X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32)
Date: Mon, 27 Mar 2000 16:02:42 -0500
To: Howard Leadmon <howardl@account.abs.net>
From: Mike Tancsa <mike@sentex.ca>
Subject: Re: Troubles with network & buffers..  Any Ideas??
Cc: freebsd-stable@FreeBSD.ORG
In-Reply-To: <200003272048.PAA04829@account.abs.net>
References: <3.0.5.32.20000327130927.01b3d5e0@marble.sentex.ca>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

At 03:48 PM 3/27/00 -0500, Howard Leadmon wrote:
>
>  Thanks for the fast reply.. :)
>
> Needless to say the machine has been rebooted since the last time it
>died, but I'll try and keep an eye on it and next time it locks if I can
>get to the console I'll see if I can grab a snapshot at that time.  If a
>current running snapshot is of any use just let me know..


Perhaps just setup a cronjob...

vmstat -m >> /var/log/vm.out

But have a look at your busier times to see if the High Use is getting
dagerously close to the limit.  Do you have a lot of aliased IPs on this
box by any chance ?  As its an IRC server, its no doubt subject to various
attacks.  Check to see if there is any ICMP funny business being blasted at
you like a few million ICMP redirects.  ipfw and sysctl can be your friend
here.

	---Mike
------------------------------------------------------------------------
Mike Tancsa,                          	          tel +1 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  Mon Mar 27 13:13:13 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from web204.mail.yahoo.com (web204.mail.yahoo.com [128.11.68.104])
	by hub.freebsd.org (Postfix) with SMTP id BF64337BF87
	for <stable@freebsd.org>; Mon, 27 Mar 2000 13:13:05 -0800 (PST)
	(envelope-from ianjhart@yahoo.com)
Received: (qmail 16648 invoked by uid 60001); 27 Mar 2000 21:13:04 -0000
Message-ID: <20000327211304.16647.qmail@web204.mail.yahoo.com>
Received: from [212.139.131.135] by web204.mail.yahoo.com; Mon, 27 Mar 2000 13:13:04 PST
Date: Mon, 27 Mar 2000 13:13:04 -0800 (PST)
From: Ian Hart <ianjhart@yahoo.com>
Subject: Re: tun0 lost in 4.0
To: stable@freebsd.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Brian Somers wrote:
> 
> > Walter Brameld wrote:
> > >
> > > On Sun, 19 Mar 2000, in a never-ending search
for
> > enlightenment, Sergei Vyshenski wrote:
> > > > Can not revive tun0 interface after moving to
4.0
> > from 3.4
> > > > in a way that src/UPDATING teaches.
> > > >
> > > > Kernel file has "pseudo-device   tun     1",
> > kernel builds ok;
> > > > ./MAKEDEV tun0 in /dev does not complain;
> > > > bbut ifconfig says: "interface tun0 does not
> > exist"
> > > >
> > > > Actually, I need tun0 to accept incoming
user-ppp,
> > > > and would be happy to hear of workaround at
least.
> > > >
> > > > Thank you in advance.
> > > > Sergei
> > >
> > > Believe it should only be "pseudo-device tun"
with
> > no "1".
> > >
> > > --
> > > Walter Brameld
> >
> > Sergei, did you fix your problem?
> >
> > A bit late on this thread I know. The reason being
-
> > no modem for over a week. When I ran ppp and went
to
> > terminal mode there was no response at all from
the
> > modem. I was running 4.0-STABLE. Was A1 under
> > 3.4-STABLE. I managed to get online (very) early
> > Saturday morning to cvsup. Sometime during the
power
> > down/make world/reading of 500+ emails it broke
again.
> > It's currently working (obviously), but I'm too
> > paranoid to do anything in case I break it again.
I
> > have set pseudo-device tun 1, contrary to GENERIC
> > setting.
> 
> You shouldn't even need this line.  Ppp(8) will load
the module if it
> needs to.  The fact that ppp actually started means
that there are no
> tun(4) related problems.  If you're getting no
response from the
> modem, then you really need to look in that
direction.
> 

If terminal mode passes through tun0 then it needs to
be considered. Otherwise not. I'm in the dark here.

> > The modem is a no-name (ORIGO) 56k6 Rockwell
Voice,
> > ISA with jumpers, set to COM 4 IRQ 9. Tried in the
two
> > machines I have at home. One with PNP COM ports,
the
> > other not. Could be broken hardware of course.
> 
> Hmm, I tend to avoid irq 2/9....

I've tried all the _normal_ settings with the same
result. Ppp loads fine, but there is no response to
any input in terminal mode. In order to get the modem
to work I had to trash my NT partition and install
Win95. Even then the normally reliable setup failed to
detect the modem. It was only when I set the CMOS to
PNP O/S and did find new hardware that the modem
revived. Is FreeBSD now a PNP O/S? Now I didn't want
to mention this before, due to the flame war, but...
This modem was designed to be PNP or jumpered. The
jumper has been bridged to disable PNP at the factory.
(Doesn't work?) I don't suppose that this could be
confusing the start up probes in some way. This is a
genuine suggestion please don't flame me! Just tell me
how I can make the probe more verbose?

I know I won't get much help without logs, but if I
break the modem again I could be off line some time. I
need as much information as I can get before I reboot.

> 
> > I also find I can no longer authenticate on
freeserve
> > (UK). X-stream is okay. Can someone who uses
freeserve
> > confirm/deny connection with 4.0-STABLE. Could be
> > broken ISP of course.
> 
> Have you built ppp with DES ?  You should see be a
-DHAVE_DES option on
> the cc line when building.  Also, make sure you
haven't got any #
> characters in you password - if you have, you'll
need to quote ("")
> the password string or escape the #.
> 

This is a secondry issue as I can at least connect via
x-stream. AFAIK I have a _stock_ system, whatever that
means. My understanding is that if the crypto sources
are present make world sucks them in automatically.
Please correct me if I am wrong. I did discover that
mergemaster -s -v does what I thought mergemaster -s
did. RTFM. What cruft there was looks harmless to me.
I do have USA_RESIDENT = NO set in /etc/make.conf.
What do I need to add to make the build behave as
setting USA_RESIDENT= YES would do. The comment in
make.conf suggests that this is only for ports.
/etc/defaults/make.conf seems to enable all crypto
stuff unless you uncomment the NOxxx= true lines.
HAVE_DES is not mentioned there.

If all my mailing lists wren't sent to freeserve I'd
just swap ISP's and forget it. FYI x-stream is PAP.

> > Any assistance would be most welcome. I can
provide
> > dmesg or whatever, but I'm not sure that will help
as
> > it's currently okay. Could be broken 'userware' of
> > course :-)
> >
> > On a positive note, at least I now know how to set
up
> > a gateway host and DNS servers. Next step - packet
> > filtering and proxy servers. Joy Joy Joy.
> >
> > ian j hart
> >
> > PS. The upgrade 3.4-4.0 went more or less without
a
> > hitch. Slightly sweaty palms I couldn't remount /
> > single user. Fixed that once I realised it was
still
> > on wd0 not ad0.
> >
> > PPS. This probably will not attach to the thread.
I
> > find I cannot send mail (ISP firewall?). Thank God
for
> > Yahoo in emergencies.
> >
> > __________________________________________________
> > Do You Yahoo!?
> > Talk to your friends online with Yahoo! Messenger.
> > http://im.yahoo.com
> 
> --
> Brian <brian@Awfulhak.org>                       
<brian@[uk.]FreeBSD.org>
>       <http://www.Awfulhak.org>                  
<brian@[uk.]OpenBSD.org>
> Don't _EVER_ lose your sense of humour !

Thanks for your reply BTW, I thought everyone had gone
fishin' or something

TIA ian j hart

sending via Yahoo for previously stated reason.
Doesn't seem to be forwarding so please REPLY TO:

 ianjhart@freeloader.freeserve.co.uk


__________________________________________________
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
http://im.yahoo.com


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


From owner-freebsd-stable  Mon Mar 27 13:17:36 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from tristo.netinc.ca (primary.2gen.net [209.240.46.188])
	by hub.freebsd.org (Postfix) with ESMTP id 458A137B807
	for <freebsd-stable@FreeBSD.ORG>; Mon, 27 Mar 2000 13:17:24 -0800 (PST)
	(envelope-from mike@2gen.net)
Received: from demutis (demutis.2gen.net [209.240.46.189])
	by tristo.netinc.ca (8.9.3/8.9.1) with SMTP id RAA00309
	for <freebsd-stable@FreeBSD.ORG>; Mon, 27 Mar 2000 17:31:01 -0500 (EST)
Message-Id: <3.0.3.32.20000327142623.0088ce90@tristo.netinc.ca>
X-Sender: mike@tristo.netinc.ca
X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32)
Date: Mon, 27 Mar 2000 14:26:23 -0500
To: freebsd-stable@FreeBSD.ORG
From: Michael DeMutis <mike@2gen.net>
Subject: CVSUp, MakeWorld, uname -a reports 3.3-RELEASE #0, Why?
In-Reply-To: <Pine.BSF.4.10.10003271709330.44309-100000@elwood.akitanet.
 co.uk>
References: <200003271352.FAA01289@web1.allunix.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

I posted earlier about my cvsupfile.

Here it is again:

Here is my "cvsupfile"

*default  host=cvsup2.FreeBSD.org
*default  base=/usr
*default  prefix=/usr
*default  release=cvs
*default  tag=RELENG_3
*default  delete use-rel-suffix

src-all
src-crypto
src-secure
*default tag=.
ports-all
doc-all


I download all the sources, and run a make world.

After compiling all and installing all, my uname -a reports:

FreeBSD tristo.netinc.ca 3.3-RELEASE FreeBSD 3.3-RELEASE #0: Thu Sep 16
23:40:35 GMT 1999     jkh@highwing.cdrom.com:/usr/src/sys/compile/GENERIC
i386

Is there something I'm doing wrong?

Shouldn't it be reporting 3.4-STABLE and shouldn't the date be somewhere in
the year 2000?

-mike


----------------------------------------------------------------------------
Michael DeMutis       
System's Administrator
2GEN.Inc.
email: mike@2gen.net   website: http://www.2gen.net/
Phone: 905-308-9155   Fax: 905-308-9519   ICQ UIN: 1257176
"Merging Media & Idea To Bring Internet Exposure to Innovative Businesses"


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


From owner-freebsd-stable  Mon Mar 27 13:22:51 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from Gloria.CAM.ORG (Gloria.CAM.ORG [205.151.116.34])
	by hub.freebsd.org (Postfix) with ESMTP
	id BAC0937BE6A; Mon, 27 Mar 2000 13:22:39 -0800 (PST)
	(envelope-from intmktg@CAM.ORG)
Received: from localhost (intmktg@localhost)
	by Gloria.CAM.ORG (8.9.3/8.9.3) with ESMTP id QAA00357;
	Mon, 27 Mar 2000 16:15:12 -0500
Date: Mon, 27 Mar 2000 16:15:12 -0500 (EST)
From: Marc Tardif <intmktg@CAM.ORG>
To: freebsd-stable@freebsd.org
Cc: freebsd-ports@freebsd.org
Subject: no ports work anymore
Message-ID: <Pine.LNX.4.10.10003271559010.32595-100000@Gloria.CAM.ORG>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

I have cvsup'ed my freebsd box to stable from a very recent installation,
making sure I downloaded all the source code and the appropriate port
subdirectories for what I need (including devel for dependencies). Both
the make buildworld and make installworld went well and so did the
compilation of the new kernel, everything done word for word as specified
in the freebsd handbook. After rebooting, I tried to install some ports
but none seem to work. I have only tried 3 ports, but all failed so there
must be something wrong somewhere. I have included my supfile as well as
the error messages I get by typing "make install" in the respective port
directories. Please let me know if there's anything wrong with the
particular ports, with the release or with my installation (though I
suspect the later is the most probable).

This is the supfile I used to update my installation of freebsd to
-stable (I installed cvsup-bin from packages):

*default tag=RELENG_3
*default host=cvsup5.FreeBSD.org
*default base=/usr/local/etc/cvsup
*default prefix=/usr
*default release=cvs delete use-rel-suffix

src-all
cvs-crypto
ports-base
ports-databases tag=.
ports-devel tag=.
ports-mail tag=.
ports-security tag=.
ports-www tag=.

These are the error messages I get for OpenSSH, Postfix and PostgreSQL (I 
had to install gmake from packages also, that didn't compile either):

----- OpenSSH -----
/usr/ports/security/openssh/work/ssh/lib/../authfd.c:439: `key' undeclared (first use this function)
/usr/ports/security/openssh/work/ssh/lib/../authfd.c:448: `auth' undeclared (first use this function)
*** Error code 1

Stop.
*** Error code 1

----- Postfix -----
You already have a user "postfix", so I will use it.
root:wheel: not founc
*** Error code 127

Stop.
*** Error code 1

----- PostgreSQL -----
===>  Generating temporary packing list
-R: not found
** Error code 127

Stop.
*** Error code 1



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


From owner-freebsd-stable  Mon Mar 27 13:28:38 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from Kirk.NetUnlimited.net (Kirk.netunlimited.net [208.128.132.1])
	by hub.freebsd.org (Postfix) with ESMTP id E62B237BB89
	for <stable@FreeBSD.ORG>; Mon, 27 Mar 2000 13:28:34 -0800 (PST)
	(envelope-from arc@twinds.com)
Received: from seahawk.twinds.com (seahawk.twinds.com [208.165.2.226])
	by Kirk.NetUnlimited.net (8.9.3/8.9.3) with ESMTP id QAA12526;
	Mon, 27 Mar 2000 16:32:21 -0500 (EST)
Date: Mon, 27 Mar 2000 16:26:10 -0500 (EST)
From: Arley Carter <arc@twinds.com>
To: Doug White <dwhite@resnet.uoregon.edu>
Cc: Andreas Klemm <andreas@klemm.gtn.com>, stable@FreeBSD.ORG
Subject: Re: syslogd problems in 4.0: rejected in rule 0 due to port mismatch.
In-Reply-To: <Pine.BSF.4.21.0003261613370.67760-100000@resnet.uoregon.edu>
Message-ID: <Pine.BSF.4.21.0003271619190.15946-100000@seahawk.twinds.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG



On Sun, 26 Mar 2000, Doug White wrote:

> What port is the cisco sending the syslog updates from?  The default -a
> requires it to be sent *from* the syslogd port.  A tcpdump is probably in
> order.

Set debug on the router and you will find that cisco likes to talk on
port 4600.  At least it does in my version of IOS 12. Tell me if you find
different. According to some this is more secure than 514.  But udp is
udp. YMMV

Cheers:
-arc

Arley Carter				arc@twinds.com
Tradewinds Technologies, Inc.		www.twinds.com
Winston-Salem, NC  USA			Network Engineering & Security	

Email for an evaluation copy of Network Flight Recorder.   



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


From owner-freebsd-stable  Mon Mar 27 13:45:41 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from picalon.gun.de (picalon.gun.de [192.109.159.1])
	by hub.freebsd.org (Postfix) with ESMTP id 5F1DF37BCE1
	for <stable@freebsd.org>; Mon, 27 Mar 2000 13:45:32 -0800 (PST)
	(envelope-from andreas@klemm.gtn.com)
Received: (from uucp@localhost)
	by picalon.gun.de (8.9.3/8.9.3) id XAA16796
	for stable@freebsd.org; Mon, 27 Mar 2000 23:45:14 +0200 (MET DST)
>Received: (from andreas@localhost)
	by klemm.gtn.com (8.9.3/8.9.3) id XAA99250
	for stable@freebsd.org; Mon, 27 Mar 2000 23:33:41 +0200 (CEST)
	(envelope-from andreas)
Date: Mon, 27 Mar 2000 23:33:41 +0200
From: Andreas Klemm <andreas@klemm.gtn.com>
To: stable@freebsd.org
Subject: can I mount a Linux ext2fs from an extended partition ?
Message-ID: <20000327233341.A98997@titan.klemm.gtn.com>
Reply-To: andreas@klemm.gtn.com, andreas.klemm.ak@bayer-ag.de,
	stable@freebsd.org
Mime-Version: 1.0
X-Mailer: Mutt 1.0.1i
X-Operating-System: FreeBSD 4.0-STABLE SMP
X-Disclaimer: A free society is one where it is safe to be unpopular
Content-Type: text/plain; charset=us-ascii
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hi !

Am migrating a customer from Linux to Unix.
His user data are on an extended partition.
How can I mount it under FreeBSD 4.0 ?

	Andreas ///


-- 
Andreas Klemm                               http://people.FreeBSD.ORG/~andreas
                                     http://www.freebsd.org/~fsmp/SMP/SMP.html
                                   powered by Symmetric MultiProcessor FreeBSD
New APSFILTER 520 and songs from our band - http://people.freebsd.org/~andreas



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


From owner-freebsd-stable  Mon Mar 27 13:50:32 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from pan.ch.intel.com (pan.ch.intel.com [143.182.246.24])
	by hub.freebsd.org (Postfix) with ESMTP id 3FD8337BB89
	for <stable@freebsd.org>; Mon, 27 Mar 2000 13:50:29 -0800 (PST)
	(envelope-from jreynold@sedona.ch.intel.com)
Received: from sedona.intel.com (sedona.ch.intel.com [143.182.218.21])
	by pan.ch.intel.com (8.9.1a+p1/8.9.1/d: relay.m4,v 1.19 2000/01/29 00:15:43 dmccart Exp $) with ESMTP id OAA22022;
	Mon, 27 Mar 2000 14:50:27 -0700 (MST)
Received: from hip186.ch.intel.com (hip186.ch.intel.com [143.182.225.68])
	by sedona.intel.com (8.9.1a/8.9.1/d: sendmail.cf,v 1.10 2000/02/10 21:38:16 steved Exp $) with ESMTP id OAA22174;
	Mon, 27 Mar 2000 14:49:21 -0700 (MST)
X-Envelope-From: jreynold@sedona.ch.intel.com
Received: (from jreynold@localhost)
	by hip186.ch.intel.com (8.9.1a/8.9.1/d: client.m4,v 1.3 1998/09/29 16:36:11 sedayao Exp sedayao $) id QAA26955;
	Mon, 27 Mar 2000 16:50:26 -0500 (EST)
X-Authentication-Warning: hip186.ch.intel.com: jreynold set sender to jreynold@sedona.ch.intel.com using -f
From: John Reynolds~ <jreynold@sedona.ch.intel.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <14559.55202.523180.943476@hip186.ch.intel.com>
Date: Mon, 27 Mar 2000 14:50:26 -0700 (MST)
To: andreas@klemm.gtn.com, andreas.klemm.ak@bayer-ag.de,
	stable@freebsd.org
Subject: Re: can I mount a Linux ext2fs from an extended partition ?
In-Reply-To: <20000327233341.A98997@titan.klemm.gtn.com>
References: <20000327233341.A98997@titan.klemm.gtn.com>
X-Mailer: VM 6.75 under Emacs 20.3.11
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


[ On Monday, March 27, Andreas Klemm wrote: ]
> Hi !
> 
> Am migrating a customer from Linux to Unix.
> His user data are on an extended partition.
> How can I mount it under FreeBSD 4.0 ?
> 
> 	Andreas ///
> 
> 

should just be:

 mount -t ex2fs /dev/whatever /mnt

See "man 8 mount_ext2fs" (which plain "mount" calls for a -t arg).

-Jr

-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
| John Reynolds               WCCG, CCE, Higher Levels of Abstraction       |
| Intel Corporation   MS: CH6-210   Phone: 480-554-9092   pgr: 602-868-6512 |
| jreynold@sedona.ch.intel.com  http://www-aec.ch.intel.com/~jreynold/      |
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=


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


From owner-freebsd-stable  Mon Mar 27 14:57:12 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from melete.ch.intel.com (melete.ch.intel.com [143.182.246.25])
	by hub.freebsd.org (Postfix) with ESMTP id 2CE1137B887
	for <freebsd-stable@freebsd.org>; Mon, 27 Mar 2000 14:57:09 -0800 (PST)
	(envelope-from jreynold@sedona.ch.intel.com)
Received: from sedona.intel.com (sedona.ch.intel.com [143.182.218.21])
	by melete.ch.intel.com (8.9.1a+p1/8.9.1/d: relay.m4,v 1.19 2000/01/29 00:15:43 dmccart Exp $) with ESMTP id WAA02536;
	Mon, 27 Mar 2000 22:58:00 GMT
Received: from hip186.ch.intel.com (hip186.ch.intel.com [143.182.225.68])
	by sedona.intel.com (8.9.1a/8.9.1/d: sendmail.cf,v 1.10 2000/02/10 21:38:16 steved Exp $) with ESMTP id PAA29243;
	Mon, 27 Mar 2000 15:55:42 -0700 (MST)
X-Envelope-From: jreynold@sedona.ch.intel.com
Received: (from jreynold@localhost)
	by hip186.ch.intel.com (8.9.1a/8.9.1/d: client.m4,v 1.3 1998/09/29 16:36:11 sedayao Exp sedayao $) id RAA00152;
	Mon, 27 Mar 2000 17:56:47 -0500 (EST)
X-Authentication-Warning: hip186.ch.intel.com: jreynold set sender to jreynold@sedona.ch.intel.com using -f
From: John Reynolds~ <jreynold@sedona.ch.intel.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <14559.59183.562406.530021@hip186.ch.intel.com>
Date: Mon, 27 Mar 2000 15:56:47 -0700 (MST)
To: Michael DeMutis <mike@2gen.net>
Cc: freebsd-stable@freebsd.org
Subject: Re: CVSUp, MakeWorld, uname -a reports 3.3-RELEASE #0, Why?
In-Reply-To: <3.0.3.32.20000327142623.0088ce90@tristo.netinc.ca>
References: <200003271352.FAA01289@web1.allunix.com>
	<3.0.3.32.20000327142623.0088ce90@tristo.netinc.ca>
X-Mailer: VM 6.75 under Emacs 20.3.11
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


[ On Monday, March 27, Michael DeMutis wrote: ]
> I posted earlier about my cvsupfile.
> 
> Here it is again:
> 
> Here is my "cvsupfile"
> 
> I download all the sources, and run a make world.
> 
> After compiling all and installing all, my uname -a reports:
> 
> FreeBSD tristo.netinc.ca 3.3-RELEASE FreeBSD 3.3-RELEASE #0: Thu Sep 16
> 23:40:35 GMT 1999     jkh@highwing.cdrom.com:/usr/src/sys/compile/GENERIC
> i386
> 
> Is there something I'm doing wrong?
> 
> Shouldn't it be reporting 3.4-STABLE and shouldn't the date be somewhere in
> the year 2000?

cvsup file looks good for 3.x-STABLE, but ... did you config and remake
your kernel (silly question but you didn't explicitly say it).

Just doing "make buildworld; make installworld" will not affect what
uname -a prints. You must rebuild and install the kernel:

 cd /usr/src/sys/i386/conf
 config MYKERNEL
 cd ../../compile/MYKERNEL
 make depend && make && make install

reboot :)

-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
| John Reynolds               WCCG, CCE, Higher Levels of Abstraction       |
| Intel Corporation   MS: CH6-210   Phone: 480-554-9092   pgr: 602-868-6512 |
| jreynold@sedona.ch.intel.com  http://www-aec.ch.intel.com/~jreynold/      |
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=


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


From owner-freebsd-stable  Mon Mar 27 15: 0:11 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from rhenium.btinternet.com (rhenium.btinternet.com [194.73.73.93])
	by hub.freebsd.org (Postfix) with ESMTP
	id 26C8E37BD67; Mon, 27 Mar 2000 15:00:03 -0800 (PST)
	(envelope-from mark@ukug.uk.freebsd.org)
Received: from [213.1.109.173] (helo=parish.my.domain)
	by rhenium.btinternet.com with esmtp (Exim 2.05 #1)
	id 12ZiUC-00020q-00; Mon, 27 Mar 2000 23:59:52 +0100
Received: (from mark@localhost)
	by parish.my.domain (8.9.3/8.9.3) id XAA01437;
	Mon, 27 Mar 2000 23:59:57 +0100 (BST)
	(envelope-from mark)
Date: Mon, 27 Mar 2000 23:59:56 +0100
From: Mark Ovens <mark@ukug.uk.freebsd.org>
To: Marc Tardif <intmktg@CAM.ORG>
Cc: freebsd-stable@freebsd.org, freebsd-ports@freebsd.org
Subject: Re: no ports work anymore
Message-ID: <20000327235956.E233@parish>
References: <Pine.LNX.4.10.10003271559010.32595-100000@Gloria.CAM.ORG>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0.1i
In-Reply-To: <Pine.LNX.4.10.10003271559010.32595-100000@Gloria.CAM.ORG>; from intmktg@CAM.ORG on Mon, Mar 27, 2000 at 04:15:12PM -0500
Organization: Total lack of
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Mon, Mar 27, 2000 at 04:15:12PM -0500, Marc Tardif wrote:
> I have cvsup'ed my freebsd box to stable from a very recent installation,
> making sure I downloaded all the source code and the appropriate port
> subdirectories for what I need (including devel for dependencies). Both
> the make buildworld and make installworld went well and so did the
> compilation of the new kernel, everything done word for word as specified
> in the freebsd handbook. After rebooting, I tried to install some ports
> but none seem to work. I have only tried 3 ports, but all failed so there
> must be something wrong somewhere. I have included my supfile as well as
> the error messages I get by typing "make install" in the respective port
> directories. Please let me know if there's anything wrong with the
> particular ports, with the release or with my installation (though I
> suspect the later is the most probable).
> 
> This is the supfile I used to update my installation of freebsd to
> -stable (I installed cvsup-bin from packages):
> 
> *default tag=RELENG_3
> *default host=cvsup5.FreeBSD.org
> *default base=/usr/local/etc/cvsup
> *default prefix=/usr
> *default release=cvs delete use-rel-suffix
> 
> src-all
> cvs-crypto
> ports-base
  ^^^^^^^^^^^^^^^^
Just a guess, but does this not mean that ports-base is being cvsup'd
with the RELENG_3 tag instead of ``.''?

> ports-databases tag=.
> ports-devel tag=.
> ports-mail tag=.
> ports-security tag=.
> ports-www tag=.
> 
> These are the error messages I get for OpenSSH, Postfix and PostgreSQL (I 
> had to install gmake from packages also, that didn't compile either):
> 
> ----- OpenSSH -----
> /usr/ports/security/openssh/work/ssh/lib/../authfd.c:439: `key' undeclared (first use this function)
> /usr/ports/security/openssh/work/ssh/lib/../authfd.c:448: `auth' undeclared (first use this function)
> *** Error code 1
> 
> Stop.
> *** Error code 1
> 
> ----- Postfix -----
> You already have a user "postfix", so I will use it.
> root:wheel: not founc
> *** Error code 127
> 
> Stop.
> *** Error code 1
> 
> ----- PostgreSQL -----
> ===>  Generating temporary packing list
> -R: not found
> ** Error code 127
> 
> Stop.
> *** Error code 1
> 
> 
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-ports" in the body of the message

-- 
Seminars, n.:
       From "semi" and "arse", hence, any half-assed discussion.
________________________________________________________________
      FreeBSD - The Power To Serve http://www.freebsd.org
      My Webpage http://ukug.uk.freebsd.org/~mark/
mailto:mark@ukug.uk.freebsd.org             http://www.radan.com



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


From owner-freebsd-stable  Mon Mar 27 15: 1:34 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from sstar.com (sstar.com [209.102.160.1])
	by hub.freebsd.org (Postfix) with ESMTP id AD1FD37BF4B
	for <freebsd-stable@FreeBSD.ORG>; Mon, 27 Mar 2000 15:01:29 -0800 (PST)
	(envelope-from king@sstar.com)
Received: from jking ([134.132.75.164]) by sstar.com
	with SMTP (IPAD 2.52) id 4110100; Mon, 27 Mar 2000 17:01:08 -0600 
Message-ID: <004101bf9840$56a38870$a44b8486@jking>
From: "Jim King" <king@sstar.com>
To: <freebsd-stable@FreeBSD.ORG>, "Michael DeMutis" <mike@2gen.net>
References: <200003271352.FAA01289@web1.allunix.com> <3.0.3.32.20000327142623.0088ce90@tristo.netinc.ca>
Subject: Re: CVSUp, MakeWorld, uname -a reports 3.3-RELEASE #0, Why?
Date: Mon, 27 Mar 2000 17:01:08 -0600
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.6700
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> I posted earlier about my cvsupfile.
>
> Here it is again:
>
> Here is my "cvsupfile"
>
> *default  host=cvsup2.FreeBSD.org
> *default  base=/usr
> *default  prefix=/usr
> *default  release=cvs
> *default  tag=RELENG_3
> *default  delete use-rel-suffix
>
> src-all
> src-crypto
> src-secure
> *default tag=.
> ports-all
> doc-all
>
>
> I download all the sources, and run a make world.
>
> After compiling all and installing all, my uname -a reports:
>
> FreeBSD tristo.netinc.ca 3.3-RELEASE FreeBSD 3.3-RELEASE #0: Thu Sep 16
> 23:40:35 GMT 1999     jkh@highwing.cdrom.com:/usr/src/sys/compile/GENERIC
> i386
>
> Is there something I'm doing wrong?
>
> Shouldn't it be reporting 3.4-STABLE and shouldn't the date be somewhere
in
> the year 2000?

Did you build and install a new kernel?  It sounds like you built/installed
world, but you're still running off the GENERIC kernel that got installed
when you installed 3.3.

Jim




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


From owner-freebsd-stable  Mon Mar 27 15: 3:35 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from gadolinium.btinternet.com (gadolinium.btinternet.com [194.73.73.111])
	by hub.freebsd.org (Postfix) with ESMTP id 9C6C437B7CA
	for <freebsd-stable@freebsd.org>; Mon, 27 Mar 2000 15:03:30 -0800 (PST)
	(envelope-from mark@ukug.uk.freebsd.org)
Received: from [213.1.109.173] (helo=parish.my.domain)
	by gadolinium.btinternet.com with esmtp (Exim 2.05 #1)
	id 12ZiY4-0003gq-00; Tue, 28 Mar 2000 00:03:52 +0100
Received: (from mark@localhost)
	by parish.my.domain (8.9.3/8.9.3) id AAA01484;
	Tue, 28 Mar 2000 00:03:20 +0100 (BST)
	(envelope-from mark)
Date: Tue, 28 Mar 2000 00:03:20 +0100
From: Mark Ovens <mark@ukug.uk.freebsd.org>
To: Michael DeMutis <mike@2gen.net>
Cc: freebsd-stable@freebsd.org
Subject: Re: CVSUp, MakeWorld, uname -a reports 3.3-RELEASE #0, Why?
Message-ID: <20000328000319.F233@parish>
References: <200003271352.FAA01289@web1.allunix.com> <Pine.BSF.4.10.10003271709330.44309-100000@elwood.akitanet. co.uk> <3.0.3.32.20000327142623.0088ce90@tristo.netinc.ca>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0.1i
In-Reply-To: <3.0.3.32.20000327142623.0088ce90@tristo.netinc.ca>; from mike@2gen.net on Mon, Mar 27, 2000 at 02:26:23PM -0500
Organization: Total lack of
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Mon, Mar 27, 2000 at 02:26:23PM -0500, Michael DeMutis wrote:
> I posted earlier about my cvsupfile.
> 
> Here it is again:
> 
> Here is my "cvsupfile"
> 
> *default  host=cvsup2.FreeBSD.org
> *default  base=/usr
> *default  prefix=/usr
> *default  release=cvs
> *default  tag=RELENG_3
> *default  delete use-rel-suffix
> 
> src-all
> src-crypto
> src-secure
> *default tag=.
> ports-all
> doc-all
> 
> 
> I download all the sources, and run a make world.
> 
> After compiling all and installing all, my uname -a reports:
> 
> FreeBSD tristo.netinc.ca 3.3-RELEASE FreeBSD 3.3-RELEASE #0:
> Thu Sep 16 23:40:35 GMT 1999
  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

You have to rebuild your kernel as well as make world.

>     jkh@highwing.cdrom.com:/usr/src/sys/compile/GENERIC
> i386
> 
> Is there something I'm doing wrong?
> 
> Shouldn't it be reporting 3.4-STABLE and shouldn't the date be somewhere in
> the year 2000?
> 
> -mike
> 
> 
> ----------------------------------------------------------------------------
> Michael DeMutis       
> System's Administrator
> 2GEN.Inc.
> email: mike@2gen.net   website: http://www.2gen.net/
> Phone: 905-308-9155   Fax: 905-308-9519   ICQ UIN: 1257176
> "Merging Media & Idea To Bring Internet Exposure to Innovative Businesses"
> 
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-stable" in the body of the message

-- 
Seminars, n.:
       From "semi" and "arse", hence, any half-assed discussion.
________________________________________________________________
      FreeBSD - The Power To Serve http://www.freebsd.org
      My Webpage http://ukug.uk.freebsd.org/~mark/
mailto:mark@ukug.uk.freebsd.org             http://www.radan.com



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


From owner-freebsd-stable  Mon Mar 27 15:14:31 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from freeway.dcfinc.com (cx74889-a.phnx3.az.home.com [24.1.193.157])
	by hub.freebsd.org (Postfix) with ESMTP id 8ABD737B841
	for <freebsd-stable@FreeBSD.ORG>; Mon, 27 Mar 2000 15:14:28 -0800 (PST)
	(envelope-from chad@freeway.dcfinc.com)
Received: (from chad@localhost)
	by freeway.dcfinc.com (8.8.8/8.8.8) id QAA10471;
	Mon, 27 Mar 2000 16:14:20 -0700 (MST)
	(envelope-from chad)
From: "Chad R. Larson" <chad@DCFinc.com>
Message-Id: <200003272314.QAA10471@freeway.dcfinc.com>
Subject: Re: CVSUp, MakeWorld, uname -a reports 3.3-RELEASE #0, Why?
In-Reply-To: <3.0.3.32.20000327142623.0088ce90@tristo.netinc.ca> from Michael DeMutis at "Mar 27, 0 02:26:23 pm"
To: mike@2gen.net (Michael DeMutis)
Date: Mon, 27 Mar 2000 16:14:20 -0700 (MST)
Cc: freebsd-stable@FreeBSD.ORG
Reply-To: chad@DCFinc.com
X-Mailer: ELM [version 2.4ME+ PL40 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

As I recall, Michael DeMutis wrote:
> I download all the sources, and run a make world.
> 
> After compiling all and installing all, my uname -a reports:
> 
> FreeBSD tristo.netinc.ca 3.3-RELEASE FreeBSD 3.3-RELEASE #0: Thu Sep 16
> 23:40:35 GMT 1999     jkh@highwing.cdrom.com:/usr/src/sys/compile/GENERIC
> i386
> 
> Is there something I'm doing wrong?

Yes.

You didn't make (or perhaps install) a new kernel.  The kernel
you're running is the GENERIC one built by Jordan Hubbard (jkh) as
part of the 3.3 release process.  You can tell from the above
message.


The handbook can lead you through the process.

Approximately, however, you'd:

1)  cd /sys/i386/conf
2)  config GENERIC
3)  cd /sys/compile/GENERIC
4)  make
5)  su root
6)  make install
7)  reboot

Once you feel comfortable about that, you might want to customize
the kernel for your machine.  You can remove all the drivers for
devices you don't have, making the kernel leaner and meaner.  In
/sys/i386/conf/LINT is very well documented kernel config file that
will help you understand what lines you'd want in your custom file.
You'd probably want to make a copy of the GENERIC file (the one you
just built), named something that makes sense to you.  Then edit it
to delete stuff you don't need, config and make and install.

Have fun!

	-crl
--
Chad R. Larson (CRL15)   602-953-1392   Brother, can you paradigm?
chad@dcfinc.com         chad@larsons.org          larson1@home.net   
DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207


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


From owner-freebsd-stable  Mon Mar 27 15:23:29 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from gluttony.peregrine.com (nat-385.peregrine.com [63.82.231.131])
	by hub.freebsd.org (Postfix) with ESMTP id C984A37BC1F
	for <freebsd-stable@FreeBSD.ORG>; Mon, 27 Mar 2000 15:23:22 -0800 (PST)
	(envelope-from erich@peregrine.com)
Received: from peregrine.com (sys461.peregrine.com [172.18.1.61])
	by gluttony.peregrine.com (8.9.3/8.9.3) with ESMTP id OAA31155;
	Mon, 27 Mar 2000 14:52:07 -0800 (PST)
	(envelope-from erich@peregrine.com)
Message-ID: <38DFE69A.B118215F@peregrine.com>
Date: Mon, 27 Mar 2000 14:54:18 -0800
From: Eric Hedstrom <erich@peregrine.com>
X-Mailer: Mozilla 4.7 [ja] (WinNT; U)
X-Accept-Language: ja
MIME-Version: 1.0
To: Michael DeMutis <mike@2gen.net>
Cc: freebsd-stable@FreeBSD.ORG
Subject: Re: CVSUp, MakeWorld, uname -a reports 3.3-RELEASE #0, Why?
References: <200003271352.FAA01289@web1.allunix.com> <3.0.3.32.20000327142623.0088ce90@tristo.netinc.ca>
Content-Type: text/plain; charset=iso-2022-jp
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

After making & installing world, you also have to configure, compile, and
install a new kernel. See section 18.4.9 in
<http://www.freebsd.org/handbook/makeworld.html>. uname reports the build
information for your kernel.

Eric


Michael DeMutis wrote:
> 
> I posted earlier about my cvsupfile.
> 
> Here it is again:
> 
> Here is my "cvsupfile"
> 
> *default  host=cvsup2.FreeBSD.org
> *default  base=/usr
> *default  prefix=/usr
> *default  release=cvs
> *default  tag=RELENG_3
> *default  delete use-rel-suffix
> 
> src-all
> src-crypto
> src-secure
> *default tag=.
> ports-all
> doc-all
> 
> I download all the sources, and run a make world.
> 
> After compiling all and installing all, my uname -a reports:
> 
> FreeBSD tristo.netinc.ca 3.3-RELEASE FreeBSD 3.3-RELEASE #0: Thu Sep 16
> 23:40:35 GMT 1999     jkh@highwing.cdrom.com:/usr/src/sys/compile/GENERIC
> i386
> 
> Is there something I'm doing wrong?
> 
> Shouldn't it be reporting 3.4-STABLE and shouldn't the date be somewhere in
> the year 2000?
> 
> -mike
> 
> ----------------------------------------------------------------------------
> Michael DeMutis
> System's Administrator
> 2GEN.Inc.
> email: mike@2gen.net   website: http://www.2gen.net/
> Phone: 905-308-9155   Fax: 905-308-9519   ICQ UIN: 1257176
> "Merging Media & Idea To Bring Internet Exposure to Innovative Businesses"
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-stable" in the body of the message


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


From owner-freebsd-stable  Mon Mar 27 15:33:47 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from mailserver.netexp.com (MAILOUT.NETEXP.COM [209.131.28.20])
	by hub.freebsd.org (Postfix) with ESMTP id 6F30037B9ED
	for <stable@FreeBSD.org>; Mon, 27 Mar 2000 15:33:44 -0800 (PST)
	(envelope-from bbommarito@netexp.com)
Received: from SIMBA ([209.69.216.56]) by mailserver.netexp.com
          (Post.Office MTA v3.5.3 release 223 ID# 0-65002U2000L200S0V35)
          with SMTP id com for <stable@FreeBSD.org>;
          Mon, 27 Mar 2000 18:30:49 -0500
Message-ID: <000a01bf9844$de109510$0100a8c0@SIMBA>
From: bbommarito@netexp.com (Bommarito, Brian)
To: <stable@FreeBSD.org>
Subject: 
Date: Mon, 27 Mar 2000 18:33:13 -0500
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0007_01BF981A.E914F660"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.6700
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

This is a multi-part message in MIME format.

------=_NextPart_000_0007_01BF981A.E914F660
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable



------=_NextPart_000_0007_01BF981A.E914F660
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2920.0" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV>&nbsp;</DIV></BODY></HTML>

------=_NextPart_000_0007_01BF981A.E914F660--



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


From owner-freebsd-stable  Mon Mar 27 15:40:18 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from isabase.philol.msu.ru (isabase.philol.msu.ru [195.208.217.73])
	by hub.freebsd.org (Postfix) with ESMTP id 452B037B9ED
	for <stable@FreeBSD.ORG>; Mon, 27 Mar 2000 15:40:13 -0800 (PST)
	(envelope-from grg@isabase.philol.msu.ru)
Received: (from grg@localhost)
	by isabase.philol.msu.ru (8.9.3/8.9.2) id DAA21785
	for stable@FreeBSD.ORG; Tue, 28 Mar 2000 03:40:11 +0400 (MSD)
	(envelope-from grg)
Date: Tue, 28 Mar 2000 03:40:11 +0400
From: Grigoriy Strokin <grg@philol.msu.ru>
To: stable@FreeBSD.ORG
Subject: Re: can I mount a Linux ext2fs from an extended partition ?
Message-ID: <20000328034011.A21720@isabase.philol.msu.ru>
References: <20000327233341.A98997@titan.klemm.gtn.com> <14559.55202.523180.943476@hip186.ch.intel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0i
In-Reply-To: <14559.55202.523180.943476@hip186.ch.intel.com>; from jreynold@sedona.ch.intel.com on Mon, Mar 27, 2000 at 02:50:26PM -0700
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Mon, Mar 27, 2000 at 02:50:26PM -0700, John Reynolds~ wrote:
> 
> [ On Monday, March 27, Andreas Klemm wrote: ]
> > Hi !
> > 
> > Am migrating a customer from Linux to Unix.
> > His user data are on an extended partition.
> > How can I mount it under FreeBSD 4.0 ?
> > 
> > 	Andreas ///
> > 
> > 
> 
> should just be:
> 
>  mount -t ex2fs /dev/whatever /mnt
> 

Oh, could you please eloborate on this? Namely, which 'whatever'
should one specify for the first 'logical' partition
of the extended partition on wd0, primary master hard drive?


-- 
=== Grigoriy Strokin, Lomonosov University (MGU), Moscow ===
=== contact info: http://isabase.philol.msu.ru/~grg/     ===


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


From owner-freebsd-stable  Mon Mar 27 15:49:54 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from Hydro.CAM.ORG (Hydro.CAM.ORG [198.168.100.7])
	by hub.freebsd.org (Postfix) with ESMTP
	id BE40137B65F; Mon, 27 Mar 2000 15:49:49 -0800 (PST)
	(envelope-from intmktg@CAM.ORG)
Received: from cam.org (Dialup-1089.HIP.CAM.ORG [205.205.139.140])
          by Hydro.CAM.ORG (8.8.8/8.8.4) with ESMTP
	  id SAA08434; Mon, 27 Mar 2000 18:48:02 -0500 (EST)
Message-ID: <38DFF040.3CD7CD92@cam.org>
Date: Mon, 27 Mar 2000 18:35:28 -0500
From: Claude Tardif <intmktg@CAM.ORG>
X-Mailer: Mozilla 4.05 [en] (Win95; I)
MIME-Version: 1.0
To: Mark Ovens <mark@dogma.freebsd-uk.eu.org>
Cc: freebsd-stable@freebsd.org, freebsd-ports@freebsd.org
Subject: Re: no ports work anymore
References: <Pine.LNX.4.10.10003271559010.32595-100000@Gloria.CAM.ORG> <20000327235956.E233@parish>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> > This is the supfile I used to update my installation of freebsd to
> > -stable (I installed cvsup-bin from packages):
> >
> > *default tag=RELENG_3
> > *default host=cvsup5.FreeBSD.org
> > *default base=/usr/local/etc/cvsup
> > *default prefix=/usr
> > *default release=cvs delete use-rel-suffix
> >
> > src-all
> > cvs-crypto
> > ports-base
>   ^^^^^^^^^^^^^^^^
> Just a guess, but does this not mean that ports-base is being cvsup'd
> with the RELENG_3 tag instead of ``.''?

Yes, but doesn't it make more sense to download the base directory which is same as my release? Problem is,
if I do specify tag=. for ports-base, I am asked to do a fresh make world or get a port upgrade kit.
Considering I have made world already, only yesterday, does that mean I need to make world AFTER
downloading the ports? Considering I'm on a 486, does simply making buildworld do the same (that would save
me alot of time)?

Marc



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


From owner-freebsd-stable  Mon Mar 27 15:59:39 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from wallace.i.nutt.net.au (dogbert.nutt.net.au [203.32.153.145])
	by hub.freebsd.org (Postfix) with ESMTP id 1645237B79E
	for <freebsd-stable@FreeBSD.ORG>; Mon, 27 Mar 2000 15:59:33 -0800 (PST)
	(envelope-from jarrod@nutt.net.au)
Received: from localhost (jarrod@localhost)
	by wallace.i.nutt.net.au (8.9.3/8.9.3) with ESMTP id IAA73164;
	Tue, 28 Mar 2000 08:22:34 +0930 (CST)
	(envelope-from jarrod@nutt.net.au)
Date: Tue, 28 Mar 2000 08:22:32 +0930 (CST)
From: Jarrod <jarrod@nutt.net.au>
X-Sender: jarrod@wallace.i.nutt.net.au
To: Michael DeMutis <mike@2gen.net>
Cc: freebsd-stable@FreeBSD.ORG
Subject: Re: CVSUp, MakeWorld, uname -a reports 3.3-RELEASE #0, Why?
In-Reply-To: <3.0.3.32.20000327142623.0088ce90@tristo.netinc.ca>
Message-ID: <Pine.BSF.4.21.0003280821080.73162-100000@wallace.i.nutt.net.au>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Mon, 27 Mar 2000, Michael DeMutis wrote:

> Date: Mon, 27 Mar 2000 14:26:23 -0500
> From: Michael DeMutis <mike@2gen.net>
> To: freebsd-stable@FreeBSD.ORG
> Subject: CVSUp, MakeWorld, uname -a reports 3.3-RELEASE #0, Why?
> 
> I download all the sources, and run a make world.
> 
> After compiling all and installing all, my uname -a reports:
> 
> FreeBSD tristo.netinc.ca 3.3-RELEASE FreeBSD 3.3-RELEASE #0: Thu Sep 16
> 23:40:35 GMT 1999     jkh@highwing.cdrom.com:/usr/src/sys/compile/GENERIC
> i386
> 
> Is there something I'm doing wrong?

Did you compile and install the kernel?

cd /usr/src/sys/i386/conf
config GENERIC
cd ../../compile/GENERIC
make depend
make
make install
reboot


-Jarrod

-- 
Jarrod Sayers (jarrod@nutt.net.au)

"That's it, no point, just boasting."
 (Jack Gallo, Just Shoot Me)



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


From owner-freebsd-stable  Mon Mar 27 16:10:10 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from melete.ch.intel.com (melete.ch.intel.com [143.182.246.25])
	by hub.freebsd.org (Postfix) with ESMTP id 40B4937B87D
	for <stable@freebsd.org>; Mon, 27 Mar 2000 16:10:06 -0800 (PST)
	(envelope-from jreynold@sedona.ch.intel.com)
Received: from sedona.intel.com (sedona.ch.intel.com [143.182.218.21])
	by melete.ch.intel.com (8.9.1a+p1/8.9.1/d: relay.m4,v 1.19 2000/01/29 00:15:43 dmccart Exp $) with ESMTP id AAA06539;
	Tue, 28 Mar 2000 00:11:12 GMT
Received: from hip186.ch.intel.com (hip186.ch.intel.com [143.182.225.68])
	by sedona.intel.com (8.9.1a/8.9.1/d: sendmail.cf,v 1.10 2000/02/10 21:38:16 steved Exp $) with ESMTP id RAA07994;
	Mon, 27 Mar 2000 17:08:55 -0700 (MST)
X-Envelope-From: jreynold@sedona.ch.intel.com
Received: (from jreynold@localhost)
	by hip186.ch.intel.com (8.9.1a/8.9.1/d: client.m4,v 1.3 1998/09/29 16:36:11 sedayao Exp sedayao $) id TAA03975;
	Mon, 27 Mar 2000 19:10:00 -0500 (EST)
X-Authentication-Warning: hip186.ch.intel.com: jreynold set sender to jreynold@sedona.ch.intel.com using -f
From: John Reynolds~ <jreynold@sedona.ch.intel.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <14559.63574.826460.351449@hip186.ch.intel.com>
Date: Mon, 27 Mar 2000 17:09:58 -0700 (MST)
To: Grigoriy Strokin <grg@philol.msu.ru>
Cc: stable@freebsd.org
Subject: Re: can I mount a Linux ext2fs from an extended partition ?
In-Reply-To: <20000328034011.A21720@isabase.philol.msu.ru>
References: <20000327233341.A98997@titan.klemm.gtn.com>
	<14559.55202.523180.943476@hip186.ch.intel.com>
	<20000328034011.A21720@isabase.philol.msu.ru>
X-Mailer: VM 6.75 under Emacs 20.3.11
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


[ On Tuesday, March 28, Grigoriy Strokin wrote: ]
> On Mon, Mar 27, 2000 at 02:50:26PM -0700, John Reynolds~ wrote:
>
> > > Am migrating a customer from Linux to Unix.
> > > His user data are on an extended partition.
> > > How can I mount it under FreeBSD 4.0 ?
> > > 
> > 
> > should just be:
> > 
> >  mount -t ex2fs /dev/whatever /mnt
> 
> Oh, could you please eloborate on this? Namely, which 'whatever'
> should one specify for the first 'logical' partition
> of the extended partition on wd0, primary master hard drive?
> 

OH! That's the info you were looking for ... I thought you were just looking
for the "ext2fs" option to "mount" ...

 http://www.freebsd.org/handbook/disks-naming.html

that might help a bit ... I have not done this myself, but I believe I 
remember from Greg Lehey's "The Complete FreeBSD" book that the 1st logical
drive is slice 5. So, under 4.0 "whatever" might be:

  /dev/ad0s5

give it a whirl. Can anybody else verify or disprove the above (I'm just
guessing and trying to remember from broken memory :).

-Jr

-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
| John Reynolds               WCCG, CCE, Higher Levels of Abstraction       |
| Intel Corporation   MS: CH6-210   Phone: 480-554-9092   pgr: 602-868-6512 |
| jreynold@sedona.ch.intel.com  http://www-aec.ch.intel.com/~jreynold/      |
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=


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


From owner-freebsd-stable  Mon Mar 27 16:36:29 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from rock.ghis.net (rock.ghis.net [209.222.164.7])
	by hub.freebsd.org (Postfix) with ESMTP
	id 0701737B990; Mon, 27 Mar 2000 16:36:25 -0800 (PST)
	(envelope-from will@blackdawn.com)
Received: from argon.blackdawn.com ([209.69.196.194])
	by rock.ghis.net (8.9.3/8.9.3) with ESMTP id QAA45130;
	Mon, 27 Mar 2000 16:33:07 -0800 (PST)
Received: by argon.blackdawn.com (Postfix, from userid 1000)
	id 6BE771A48; Mon, 27 Mar 2000 19:31:37 -0500 (EST)
Date: Mon, 27 Mar 2000 19:31:37 -0500
From: Will Andrews <andrews@technologist.com>
To: Claude Tardif <intmktg@CAM.ORG>
Cc: Mark Ovens <mark@dogma.freebsd-uk.eu.org>,
	freebsd-stable@FreeBSD.ORG, freebsd-ports@FreeBSD.ORG
Subject: Re: no ports work anymore
Message-ID: <20000327193137.R73880@argon.blackdawn.com>
References: <Pine.LNX.4.10.10003271559010.32595-100000@Gloria.CAM.ORG> <20000327235956.E233@parish> <38DFF040.3CD7CD92@cam.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0i
In-Reply-To: <38DFF040.3CD7CD92@cam.org>; from intmktg@CAM.ORG on Mon, Mar 27, 2000 at 06:35:28PM -0500
X-Operating-System: FreeBSD 5.0-CURRENT i386
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Mon, Mar 27, 2000 at 06:35:28PM -0500, Claude Tardif wrote:
> Yes, but doesn't it make more sense to download the base directory which is same as my release? Problem is,
> if I do specify tag=. for ports-base, I am asked to do a fresh make world or get a port upgrade kit.
> Considering I have made world already, only yesterday, does that mean I need to make world AFTER
> downloading the ports? Considering I'm on a 486, does simply making buildworld do the same (that would save
> me alot of time)?

pkg_add -r 34upgrade

-- 
Will Andrews <andrews@technologist.com>
GCS/E/S @d- s+:+>+:- a--->+++ C++ UB++++ P+ L- E--- W+++ !N !o ?K w---
?O M+ V-- PS+ PE++ Y+ PGP+>+++ t++ 5 X++ R+ tv+ b++>++++ DI+++ D+ 
G++>+++ e->++++ h! r-->+++ y?


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


From owner-freebsd-stable  Mon Mar 27 16:39:43 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13])
	by hub.freebsd.org (Postfix) with ESMTP id 0361F37B9F9
	for <stable@freebsd.org>; Mon, 27 Mar 2000 16:39:39 -0800 (PST)
	(envelope-from ben@scientia.demon.co.uk)
Received: from strontium.scientia.demon.co.uk ([192.168.91.36] ident=exim)
	by scientia.demon.co.uk with esmtp (Exim 3.12 #1)
	id 12ZiGg-000Cxb-00; Mon, 27 Mar 2000 23:45:54 +0100
Received: (from ben) by strontium.scientia.demon.co.uk (Exim 3.12 #7)
	id 12ZiGg-0001d1-00; Mon, 27 Mar 2000 23:45:54 +0100
Date: Mon, 27 Mar 2000 23:45:53 +0100
From: Ben Smithurst <ben@scientia.demon.co.uk>
To: andreas@klemm.gtn.com, andreas.klemm.ak@bayer-ag.de,
	stable@freebsd.org
Subject: Re: can I mount a Linux ext2fs from an extended partition ?
Message-ID: <20000327234553.A86036@strontium.scientia.demon.co.uk>
References: <20000327233341.A98997@titan.klemm.gtn.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0i
In-Reply-To: <20000327233341.A98997@titan.klemm.gtn.com>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Andreas Klemm wrote:

> Am migrating a customer from Linux to Unix.
> His user data are on an extended partition.
> How can I mount it under FreeBSD 4.0 ?

I think you can access extended partitions as slices 5-8, if you mean
what I think you mean.

-- 
Ben Smithurst / ben@scientia.demon.co.uk / PGP: 0x99392F7D


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


From owner-freebsd-stable  Mon Mar 27 17: 0:24 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from xxx.video-collage.com (xxx.video-collage.com [209.122.149.226])
	by hub.freebsd.org (Postfix) with ESMTP id 3F4D637B596
	for <stable@freebsd.org>; Mon, 27 Mar 2000 17:00:19 -0800 (PST)
	(envelope-from mi@video-collage.com)
X-Relay-IP: ‚ 
Received: from video-collage.com (dufus [10.222.222.77])
	by xxx.video-collage.com (8.9.1a/8.9.1) with ESMTP id UAA12045
	for <stable@freebsd.org>; Mon, 27 Mar 2000 20:00:00 -0500 (EST)
Message-Id: <200003280100.UAA12045@xxx.video-collage.com>
Date: Mon, 27 Mar 2000 19:59:58 -0500 (EST)
From: mi@video-collage.com
Reply-To: Mikhail Teterin <mi@aldan.algebra.com>
Subject: top, systat )-: (all rebuilt!)
To: stable@freebsd.org
MIME-Version: 1.0
Content-Type: TEXT/plain; CHARSET=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hello!  I did  the entire  procedure described  in UPDATING  to go  from
3.4-STABLE to 4.0-STABLE last night.

Most of the things work, but the  top, and systat. And Xaccel (from XiG)
can not  find a  single free  terminal to run  anymore. Although,  all 8
gettys are running fine.

Here is an attempt to proof my sanity:

	root@rtfm:/usr/src (114) ls -l `which top`
	-r-xr-sr-x  1 root  kmem  32224 Mar 27 18:14 /usr/bin/top
	root@rtfm:/usr/src (115) ldd !$
	ldd `which top`
	/usr/bin/top:
		libncurses.so.5 => /usr/lib/libncurses.so.5 (0x1806b000)
		libm.so.2 => /usr/lib/libm.so.2 (0x180aa000)
		libkvm.so.2 => /usr/lib/libkvm.so.2 (0x180c6000)
		libc.so.4 => /usr/lib/libc.so.4 (0x180cc000)
	root@rtfm:/usr/src (116) ls -l /usr/lib/libncurses.so.5 \
		/usr/lib/libm.so.2 /usr/lib/libkvm.so.2 /usr/lib/libc.so.4
	-r--r--r--  1 root  wheel  539604 Mar 27 18:10 /usr/lib/libc.so.4
	-r--r--r--  1 root  wheel   18196 Mar 27 18:10 /usr/lib/libkvm.so.2
	-r--r--r--  1 root  wheel  117180 Mar 27 18:09 /usr/lib/libm.so.2
	-r--r--r--  1 root  wheel  246712 Mar 27 18:09 /usr/lib/libncurses.so.5
	root@rtfm:/usr/src (117) uname -a
	FreeBSD rtfm.newton 4.0-STABLE FreeBSD 4.0-STABLE #1: \
		Mon Mar 27 05:13:38 EST 2000
		mi@rtfm.newton:/4G/src/sys/compile/RTFM2  i386
	root@rtfm:/usr/src (118) top
	top: nlist failed
	root@rtfm:/usr/src (119) ls -l /kernel
	-r-xr-xr-x  1 root  wheel  2358025 Mar 27 05:16 /kernel
	root@rtfm:/usr/src (120) sysctl kern.bootfile
	kern.bootfile: /kernel
	root@rtfm:/usr/src (121) ls -lt /4G/src/sys/compile/RTFM2 | tail -1
	-rw-rw-r--  1 mi  wheel     5893 Mar 27 04:58 ioconf.c

systat dies similarly:

	systat: nlist: can't find following symbols:
	_bufspace
	_numvnodes
	_freevnodes
	_numdirtybuffers

but w and uptime work just fine...

I   did    the   buildworld,   the   installed    mknod   and   modules.
build/installkernel,  reboot to  single-user. Installed  world again  as
prescribed,  rebooted to  multiuser. The  Xaccel was  working, but  top,
systat were not.  I rebuilt the kernel again, rebooted.  Xaccel does not
come up,  neither does top or  systat. I rebuilt and  re-installed world
and top and systat still don't work :(

Any ideas? Thanks!

	-mi




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


From owner-freebsd-stable  Mon Mar 27 17:13:34 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from netcom.com (netcom16.netcom.com [199.183.9.116])
	by hub.freebsd.org (Postfix) with ESMTP id BE20837B848
	for <freebsd-stable@freebsd.org>; Mon, 27 Mar 2000 17:13:31 -0800 (PST)
	(envelope-from stanb@netcom.com)
Received: (from stanb@localhost)
	by netcom.com (8.9.3/8.9.3) id RAA29060
	for freebsd-stable@freebsd.org; Mon, 27 Mar 2000 17:01:29 -0800 (PST)
From: Stan Brown <stanb@netcom.com>
Message-Id: <200003280101.RAA29060@netcom.com>
Subject: 4.0 STABLE make world failure
To: freebsd-stable@freebsd.org (FreeBSD Stable List)
Date: Mon, 27 Mar 2000 20:01:28 -0500 (EST)
X-Mailer: ELM [version 2.5 PL3]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

	OK, it failed this morning, so I re-cvsuped and it fails again.

	in ppp/chap_ms.c trying to include openssl/des.h 

	Anyone know what I am doing wrong?

-- 
Stan Brown     stanb@netcom.com                                    404-996-6955
Factory Automation Systems
Atlanta Ga.
-- 
Look, look, see Windows 95.  Buy, lemmings, buy!   
Pay no attention to that cliff ahead...            Henry Spencer
(c) 1998 Stan Brown.  Redistribution via the Microsoft Network is prohibited.


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


From owner-freebsd-stable  Mon Mar 27 17:55:19 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32])
	by hub.freebsd.org (Postfix) with ESMTP id A63CD37B7F1
	for <stable@FreeBSD.ORG>; Mon, 27 Mar 2000 17:55:17 -0800 (PST)
	(envelope-from dwhite@resnet.uoregon.edu)
Received: from localhost (dwhite@localhost)
	by resnet.uoregon.edu (8.9.3/8.9.3) with ESMTP id RAA70782;
	Mon, 27 Mar 2000 17:48:07 -0800 (PST)
	(envelope-from dwhite@resnet.uoregon.edu)
Date: Mon, 27 Mar 2000 17:48:06 -0800 (PST)
From: Doug White <dwhite@resnet.uoregon.edu>
To: Mike Nowlin <mike@argos.org>
Cc: Andreas Klemm <andreas@klemm.gtn.com>, stable@FreeBSD.ORG
Subject: Re: HEADS-UP please: syslogd problems in 4.0: rejected in rule 0
 due to port mismatch.
In-Reply-To: <Pine.LNX.4.05.10003270155310.15121-100000@jason.argos.org>
Message-ID: <Pine.BSF.4.21.0003271747160.75021-100000@resnet.uoregon.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Mon, 27 Mar 2000, Mike Nowlin wrote:

> 
> > What port is the cisco sending the syslog updates from?  The default -a
> > requires it to be sent *from* the syslogd port.  A tcpdump is probably in
> > order.
> 
> Is this "the right way" to do it?  I'm just wondering why the requirement
> that the messages come from the syslog port.  My Linux & DEC UNIX machines
> don't require this, although they're not using any kind of allowed_peer
> restrictions - just "remote logging enabled".  

You'll have to ask Joerg, he wrote the patch :)

rev 1.25 in src/sys/usr.sbin/syslogd.c

Doug White                    |  FreeBSD: The Power to Serve
dwhite@resnet.uoregon.edu     |  www.FreeBSD.org



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


From owner-freebsd-stable  Mon Mar 27 18:11:32 2000
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 5BDE437BC8E
	for <stable@freebsd.org>; Mon, 27 Mar 2000 18:11:29 -0800 (PST)
	(envelope-from jdp@polstra.com)
Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13])
	by wall.polstra.com (8.9.3/8.9.3) with ESMTP id SAA05642;
	Mon, 27 Mar 2000 18:11:28 -0800 (PST)
	(envelope-from jdp@polstra.com)
From: John Polstra <jdp@polstra.com>
Received: (from jdp@localhost)
	by vashon.polstra.com (8.9.3/8.9.1) id SAA03086;
	Mon, 27 Mar 2000 18:11:27 -0800 (PST)
	(envelope-from jdp@polstra.com)
Date: Mon, 27 Mar 2000 18:11:27 -0800 (PST)
Message-Id: <200003280211.SAA03086@vashon.polstra.com>
To: aa8vb@ipass.net
Subject: Re: Dynamic linker bug in 3.4-RELEASE (I think)
In-Reply-To: <20000317195156.A24243@ipass.net>
References: <20000317195156.A24243@ipass.net>
Organization: Polstra & Co., Seattle, WA
Cc: stable@freebsd.org
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

In article <20000317195156.A24243@ipass.net>,
Randall Hopper  <aa8vb@ipass.net> wrote:
> I have a small program I wrote that uses sigwait and takes about 1 second
> to complete.  
> 
> If I run it over-and-over many times repeatedly, occasionally the dynamic
> linker will fail to resolve the "sigwait" symbol.

Is your program multi-threaded?  There are some known problems in
connection with that.

Try setting LD_BIND_NOW=1 in the environment and see if that changes
the behavior.

John
-- 
  John Polstra                                               jdp@polstra.com
  John D. Polstra & Co., Inc.                        Seattle, Washington USA
  "Disappointment is a good sign of basic intelligence."  -- Chögyam Trungpa



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


From owner-freebsd-stable  Mon Mar 27 18:28:35 2000
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 6DCC737B82A
	for <stable@freebsd.org>; Mon, 27 Mar 2000 18:28:32 -0800 (PST)
	(envelope-from jdp@polstra.com)
Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13])
	by wall.polstra.com (8.9.3/8.9.3) with ESMTP id SAA05699;
	Mon, 27 Mar 2000 18:28:30 -0800 (PST)
	(envelope-from jdp@polstra.com)
From: John Polstra <jdp@polstra.com>
Received: (from jdp@localhost)
	by vashon.polstra.com (8.9.3/8.9.1) id SAA03136;
	Mon, 27 Mar 2000 18:28:29 -0800 (PST)
	(envelope-from jdp@polstra.com)
Date: Mon, 27 Mar 2000 18:28:29 -0800 (PST)
Message-Id: <200003280228.SAA03136@vashon.polstra.com>
To: manek@ecst.csuchico.edu
Subject: Re: unusual cvsup message
In-Reply-To: <NDBBKDINCKINCMKCHGCIAEONCIAA.manek@ecst.csuchico.edu>
References: <NDBBKDINCKINCMKCHGCIAEONCIAA.manek@ecst.csuchico.edu>
Organization: Polstra & Co., Seattle, WA
Cc: stable@freebsd.org
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

In article <NDBBKDINCKINCMKCHGCIAEONCIAA.manek@ecst.csuchico.edu>,
Sameer R. Manek <manek@ecst.csuchico.edu> wrote:
> I got this message on a cvsup performed today, at about Sun Mar 19 15:07:18
> PST 2000, anyone else get a similar message? and should i be concerned about
> it?
...
>  Edit src/sys/contrib/dev/oltr/trlld.h
> src/sys/contrib/dev/oltr/trlld.h: Cannot get edited text: "d" edit command
> specifies line past end of base delta -- will transfer entire file

This kind of message indicates that the file was corrupted prior to
the update, either on your end or on the server's end.  At this point
in time, it's hard to say which was the case.  It happened when I was
on vacation, and all the evidence is probably gone by now.  The CVSup
client has an option "-k" which will make it save the bad version of
the file for later analysis, but it's too late for that now.

Anyway, you needn't worry, because this later step fetched the whole
file from the server:

> Applying fixups for collection src-all/cvs
>  Fixup src/sys/contrib/dev/oltr/trlld.h

John
-- 
  John Polstra                                               jdp@polstra.com
  John D. Polstra & Co., Inc.                        Seattle, Washington USA
  "Disappointment is a good sign of basic intelligence."  -- Chögyam Trungpa



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


From owner-freebsd-stable  Mon Mar 27 18:32:15 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from jade.chc-chimes.com (jade.chc-chimes.com [216.28.46.6])
	by hub.freebsd.org (Postfix) with ESMTP
	id 6782737B6B7; Mon, 27 Mar 2000 18:32:09 -0800 (PST)
	(envelope-from billf@jade.chc-chimes.com)
Received: by jade.chc-chimes.com (Postfix, from userid 1001)
	id AB4FE1C5D; Mon, 27 Mar 2000 21:32:07 -0500 (EST)
Date: Mon, 27 Mar 2000 21:32:07 -0500
From: Bill Fumerola <billf@chc-chimes.com>
To: Claude Tardif <intmktg@CAM.ORG>
Cc: Mark Ovens <mark@dogma.freebsd-uk.eu.org>,
	freebsd-stable@freebsd.org, freebsd-ports@freebsd.org
Subject: Re: no ports work anymore
Message-ID: <20000327213207.E23367@jade.chc-chimes.com>
References: <Pine.LNX.4.10.10003271559010.32595-100000@Gloria.CAM.ORG> <20000327235956.E233@parish> <38DFF040.3CD7CD92@cam.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0i
In-Reply-To: <38DFF040.3CD7CD92@cam.org>; from intmktg@CAM.ORG on Mon, Mar 27, 2000 at 06:35:28PM -0500
X-Operating-System: FreeBSD 3.2-RELEASE i386
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Mon, Mar 27, 2000 at 06:35:28PM -0500, Claude Tardif wrote:

> Yes, but doesn't it make more sense to download the base directory which is same as my release? Problem is,
> if I do specify tag=. for ports-base, I am asked to do a fresh make world or get a port upgrade kit.
> Considering I have made world already, only yesterday, does that mean I need to make world AFTER
> downloading the ports? Considering I'm on a 486, does simply making buildworld do the same (that would save
> me alot of time)?

For the umpteenith time:

	PORTS ARE NOT BRANCHED.

There is no RELENG_3 of ports-base. There is a RELENG_3_0_RELEASE or however 
the hell they're tagged (http://www.FreeBSD.org/cgi/cvsweb.cgi or `cvs log' for
the answer).

You are asking cvsup for something that does not exist.

-- 
Bill Fumerola - Network Architect
Computer Horizons Corp - CVM
e-mail: billf@chc-chimes.com / billf@FreeBSD.org
Office: 800-252-2421 x128 / Cell: 248-761-7272





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


From owner-freebsd-stable  Mon Mar 27 18:55:31 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from charon.ipass.net (charon.ipass.net [198.79.53.8])
	by hub.freebsd.org (Postfix) with ESMTP id 576D737B71F
	for <stable@freebsd.org>; Mon, 27 Mar 2000 18:55:28 -0800 (PST)
	(envelope-from rhh@ipass.net)
Received: from stealth.ipass.net. (ppp-1-159.dialup.rdu.ipass.net [209.170.132.159])
	by charon.ipass.net (8.9.3/8.9.3) with ESMTP id VAA21753;
	Mon, 27 Mar 2000 21:55:26 -0500 (EST)
Received: (from rhh@localhost)
	by stealth.ipass.net. (8.9.3/8.8.8) id VAA64237;
	Mon, 27 Mar 2000 21:58:04 -0500 (EST)
	(envelope-from rhh)
Date: Mon, 27 Mar 2000 21:58:04 -0500
From: Randall Hopper <aa8vb@ipass.net>
To: John Polstra <jdp@polstra.com>
Cc: stable@freebsd.org
Subject: Re: Dynamic linker bug in 3.4-RELEASE (I think)
Message-ID: <20000327215804.A64173@ipass.net>
References: <20000317195156.A24243@ipass.net> <200003280211.SAA03086@vashon.polstra.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0.1i
In-Reply-To: <200003280211.SAA03086@vashon.polstra.com>; from jdp@polstra.com on Mon, Mar 27, 2000 at 06:11:27PM -0800
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

John Polstra:
 |In article <20000317195156.A24243@ipass.net>,
 |Randall Hopper  <aa8vb@ipass.net> wrote:
 |> I have a small program I wrote that uses sigwait and takes about 1 second
 |> to complete.  
 |> 
 |> If I run it over-and-over many times repeatedly, occasionally the dynamic
 |> linker will fail to resolve the "sigwait" symbol.
 |
 |Is your program multi-threaded?  There are some known problems in
 |connection with that.

This program isn't threaded, though I compiled it with -pthread (another
util in that dir is threaded, and I'd used the same CFLAGS for both).

 |Try setting LD_BIND_NOW=1 in the environment and see if that changes
 |the behavior.

That seemed to clear it up.  (Though, it happens so rarely it's hard to be
sure.)

Randall


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


From owner-freebsd-stable  Mon Mar 27 19:29:51 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from mail.pd.chel.ru (ras.pd.chel.ru [212.57.133.29])
	by hub.freebsd.org (Postfix) with SMTP id 0F59837B6B7
	for <freebsd-stable@freebsd.org>; Mon, 27 Mar 2000 19:29:32 -0800 (PST)
	(envelope-from lw@pd.chel.ru)
Received: (qmail 14168 invoked from network); 28 Mar 2000 03:28:48 -0000
Received: from lw.uvd.chel.su (192.168.200.123)
  by mail.uvd.chel.su with SMTP; 28 Mar 2000 03:28:48 -0000
Date: Tue, 28 Mar 2000 09:26:44 +0500
From: "Sergey A. Ivanov" <lw@pd.chel.ru>
X-Mailer: The Bat! (v1.41) UNREG / CD5BF9353B3B7091
Reply-To: "Sergey A. Ivanov" <lw@pd.chel.ru>
X-Priority: 3 (Normal)
Message-ID: <5393.000328@pd.chel.ru>
To: freebsd-stable@freebsd.org
Subject: FreeBSD4 & IP v.6
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!

   I'm just upgraded from 3.4s to 4.0s and now my machine appears to
have IP6 addresses. But really there are none of them, and i have no
any routers around theat support IP6. Is IP6 mandatory for FreeBSD4 or
i can safely removed them? Is commenting appropriate entries in kernel
enought for doing that?

Best regards,
 Sergey                           mailto:lw@pd.chel.ru
                                      ICQ UIN: 49432691
                                      http://lw.narod.ru




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


From owner-freebsd-stable  Mon Mar 27 19:43: 9 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from rover.village.org (rover.village.org [204.144.255.49])
	by hub.freebsd.org (Postfix) with ESMTP id A9D8837B99B
	for <stable@FreeBSD.ORG>; Mon, 27 Mar 2000 19:43:05 -0800 (PST)
	(envelope-from imp@harmony.village.org)
Received: from harmony.village.org (harmony.village.org [10.0.0.6])
	by rover.village.org (8.9.3/8.9.3) with ESMTP id UAA56865;
	Mon, 27 Mar 2000 20:43:03 -0700 (MST)
	(envelope-from imp@harmony.village.org)
Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id UAA02290; Mon, 27 Mar 2000 20:42:45 -0700 (MST)
Message-Id: <200003280342.UAA02290@harmony.village.org>
To: Mikhail Teterin <mi@aldan.algebra.com>
Subject: Re: top, systat )-: (all rebuilt!) 
Cc: stable@FreeBSD.ORG
In-reply-to: Your message of "Mon, 27 Mar 2000 19:59:58 EST."
		<200003280100.UAA12045@xxx.video-collage.com> 
References: <200003280100.UAA12045@xxx.video-collage.com>  
Date: Mon, 27 Mar 2000 20:42:45 -0700
From: Warner Losh <imp@village.org>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

In message <200003280100.UAA12045@xxx.video-collage.com> mi@video-collage.com writes:
: systat were not.  I rebuilt the kernel again, rebooted.  Xaccel does not
: come up,  neither does top or  systat. I rebuilt and  re-installed world
: and top and systat still don't work :(

What's uname -a say?  Maybe you've not booted the new kernel.

Warner
 


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


From owner-freebsd-stable  Mon Mar 27 19:52: 0 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from fgwmail7.fujitsu.co.jp (fgwmail7.fujitsu.co.jp [192.51.44.37])
	by hub.freebsd.org (Postfix) with ESMTP id A54FC37BD5C
	for <freebsd-stable@FreeBSD.ORG>; Mon, 27 Mar 2000 19:51:53 -0800 (PST)
	(envelope-from shin@nd.net.fujitsu.co.jp)
Received: from m5.gw.fujitsu.co.jp by fgwmail7.fujitsu.co.jp (8.9.3/3.7W-MX0002-Fujitsu Gateway)
	id MAA20679; Tue, 28 Mar 2000 12:51:54 +0900 (JST)
	(envelope-from shin@nd.net.fujitsu.co.jp)
Received: from chisato.nd.net.fujitsu.co.jp by m5.gw.fujitsu.co.jp (8.9.3/3.7W-0003-Fujitsu Domain Master)
	id MAA04434; Tue, 28 Mar 2000 12:51:49 +0900 (JST)
Received: from localhost (dhcp7173.nd.net.fujitsu.co.jp [10.18.7.173]) by chisato.nd.net.fujitsu.co.jp (8.8.5+2.7Wbeta5/3.3W8chisato-970826) with ESMTP id MAA26212; Tue, 28 Mar 2000 12:51:48 +0900 (JST)
To: lw@pd.chel.ru
Cc: freebsd-stable@FreeBSD.ORG
Subject: Re: FreeBSD4 & IP v.6
In-Reply-To: <5393.000328@pd.chel.ru>
References: <5393.000328@pd.chel.ru>
X-Mailer: Mew version 1.94 on Emacs 20.4 / Mule 4.0 (HANANOEN)
X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <20000328125248K.shin@nd.net.fujitsu.co.jp>
Date: Tue, 28 Mar 2000 12:52:48 +0900
From: Yoshinobu Inoue <shin@nd.net.fujitsu.co.jp>
X-Dispatcher: imput version 990905(IM130)
Lines: 30
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> Hello!
> 
>    I'm just upgraded from 3.4s to 4.0s and now my machine appears to
> have IP6 addresses. But really there are none of them, and i have no
> any routers around theat support IP6. Is IP6 mandatory for FreeBSD4 or
> i can safely removed them? Is commenting appropriate entries in kernel
> enought for doing that?

It is not mandatory, so you can remove the support by removing
INET6 option from your kernel config file.

But even if you don't have direct IPv6 neighbor, you can play
with it by IPv6 over IPv4 tunneling.

Here is some info about such tunneling,

http://www.kame.net/newsletter/19990513/

And also now there is 6to4 which gives you some global IPv6
addr block and IPv6 connectivity immediately.
It is described in draft-ietf-ngtrans-6to4-0*.txt,
and you can use it via interface stf.

The stf usage is written in `man stf` and you can setup it
easily by adding
  stf_interface_ipv4addr="your ipv4 addr"
in your /etc/rc.conf.

Cheers,
Yoshinobu Inoue


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


From owner-freebsd-stable  Mon Mar 27 19:55:49 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from xxx.video-collage.com (xxx.video-collage.com [209.122.149.226])
	by hub.freebsd.org (Postfix) with ESMTP id D6CD737BE63
	for <stable@FreeBSD.ORG>; Mon, 27 Mar 2000 19:55:33 -0800 (PST)
	(envelope-from mi@video-collage.com)
X-Relay-IP: ‚ 
Received: from video-collage.com (dufus [10.222.222.77])
	by xxx.video-collage.com (8.9.1a/8.9.1) with ESMTP id WAA12333;
	Mon, 27 Mar 2000 22:55:19 -0500 (EST)
Message-Id: <200003280355.WAA12333@xxx.video-collage.com>
Date: Mon, 27 Mar 2000 22:55:16 -0500 (EST)
From: mi@video-collage.com
Reply-To: Mikhail Teterin <mi@aldan.algebra.com>
Subject: Re: top, systat )-: (all rebuilt!) 
To: Warner Losh <imp@village.org>
Cc: stable@FreeBSD.ORG
In-Reply-To: <200003280342.UAA02290@harmony.village.org>
MIME-Version: 1.0
Content-Type: TEXT/plain; CHARSET=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On 27 Mar, Warner Losh wrote:
= In message <200003280100.UAA12045@xxx.video-collage.com>
=	mi@video-collage.com writes:
= : systat were not.  I rebuilt the kernel again,  rebooted. Xaccel does
= : not come up, neither does top  or systat. I rebuilt and re-installed
= : world and top and systat still don't work :(
= 
= What's uname -a say?  Maybe you've not booted the new kernel.

Oh, as I put into my lengthy posting:

	root@rtfm:/usr/src (131) ls -l /kernel
	-r-xr-xr-x  1 root  wheel  2358025 Mar 27 05:16 /kernel
	root@rtfm:/usr/src (132) uname -a
		FreeBSD rtfm.newton 4.0-STABLE FreeBSD 4.0-STABLE #1:
		Mon Mar 27 05:13:38 EST 2000
		mi@rtfm.newton:/4G/src/sys/compile/RTFM2  i386
	root@rtfm:/usr/src (133) sysctl kern.bootfile
	kern.bootfile: /kernel

		-mi




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


From owner-freebsd-stable  Mon Mar 27 20: 1:43 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from xxx.video-collage.com (xxx.video-collage.com [209.122.149.226])
	by hub.freebsd.org (Postfix) with ESMTP id 1D95137BDB7
	for <stable@freebsd.org>; Mon, 27 Mar 2000 20:01:36 -0800 (PST)
	(envelope-from mi@video-collage.com)
X-Relay-IP: ‚ 
Received: from video-collage.com (dufus [10.222.222.77])
	by xxx.video-collage.com (8.9.1a/8.9.1) with ESMTP id XAA12345
	for <stable@freebsd.org>; Mon, 27 Mar 2000 23:01:29 -0500 (EST)
Message-Id: <200003280401.XAA12345@xxx.video-collage.com>
Date: Mon, 27 Mar 2000 23:01:26 -0500 (EST)
From: mi@video-collage.com
Reply-To: Mikhail Teterin <mi@aldan.algebra.com>
Subject: panic on a flaky SCSI CD
To: stable@freebsd.org
MIME-Version: 1.0
Content-Type: TEXT/plain; CHARSET=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

I have this flaky SCSI CD, which works sometimes :)
When it fails, I see something like the following
popping up:

Creating DISK cd0
(cd0:ncr1:0:6:0): got CAM status 0x4a
(cd0:ncr1:0:6:0): fatal error, failed to attach to device
(cd0:ncr1:0:6:0): lost device
(cd0:ncr1:0:6:0): removing device entry

Under 3.4, if I was to try to mount a CD in this drive,
when it was in the bad mood, I'd simply get an error. Now,
with 4.0 the thing panics :(

	-mi



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


From owner-freebsd-stable  Mon Mar 27 20: 8:21 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from xxx.video-collage.com (xxx.video-collage.com [209.122.149.226])
	by hub.freebsd.org (Postfix) with ESMTP id AD90D37BA1F
	for <stable@freebsd.org>; Mon, 27 Mar 2000 20:08:16 -0800 (PST)
	(envelope-from mi@video-collage.com)
X-Relay-IP: ‚ 
Received: from video-collage.com (dufus [10.222.222.77])
	by xxx.video-collage.com (8.9.1a/8.9.1) with ESMTP id XAA12357
	for <stable@freebsd.org>; Mon, 27 Mar 2000 23:08:12 -0500 (EST)
Message-Id: <200003280408.XAA12357@xxx.video-collage.com>
Date: Mon, 27 Mar 2000 23:08:09 -0500 (EST)
From: mi@video-collage.com
Reply-To: Mikhail Teterin <mi@aldan.algebra.com>
Subject: attempts to save the blocks on the MFS on panic
To: stable@freebsd.org
MIME-Version: 1.0
Content-Type: TEXT/plain; CHARSET=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

With the  flaky CD related  panic I just  described I noticed  one other
thing. When the  panic strikes, the blocks are being  written out to the
file-systems as usual. Except that in the case of MFS it makes no sense.
It never  succeeds with  it either and  ends up "giving  up" on  all the
blocks from MFS only (I boot with -v and see the file-system type of the
blocks given up upon).

Does not  really bother me --  it is already  a panic, but it  may start
causing a double panic some time in the future...

This is on 4.0, the MFS is created at boot time by the following line in
/etc/fstab:

	/dev/null  /tmp   mfs  rw,async,-Tqp120at,-s512000

		-mi




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


From owner-freebsd-stable  Mon Mar 27 20:23:15 2000
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 895CB37B99A
	for <stable@FreeBSD.ORG>; Mon, 27 Mar 2000 20:23:11 -0800 (PST)
	(envelope-from dcs@newsguy.com)
Received: from newsguy.com (p29-dn03kiryunisiki.gunma.ocn.ne.jp [210.232.224.158])
	by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id NAA19164;
	Tue, 28 Mar 2000 13:23:07 +0900 (JST)
Message-ID: <38E03333.1CF8B87E@newsguy.com>
Date: Tue, 28 Mar 2000 13:21:07 +0900
From: "Daniel C. Sobral" <dcs@newsguy.com>
X-Mailer: Mozilla 4.7 [en] (Win98; I)
X-Accept-Language: en,pt-BR,ja
MIME-Version: 1.0
To: Jerry Bell <jerry@bellnetworks.net>
Cc: stable@FreeBSD.ORG
Subject: Re: ps, w, top and netstat problem
References: <XFMail.000326095323.mike@rbc.ru> <015801bf96cc$14f8fce0$f7bbb1d0@netrex.com> <20000326163457.O86036@strontium.scientia.demon.co.uk> <38DE9C8F.3F9D6246@pocketscience.com> <022001bf9724$44358c00$f7bbb1d0@netrex.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Jerry Bell wrote:
> 
> Yes sir, this is how I've been doing it.  Everything with this problem looks
> to be an inconsistency between the kernel and the binaries, but I'm pretty
> certain this is not the case.

It might be a bogus cvsup file resulting in the problem.

Try the following:

1) use 4.x-stable-supfile, if you weren't.
2) Remove your make.conf, just in case it's preventing something from
being built/installed.
3) Verify the version of the files of ps and libkvm through cvsweb to
ensure they are the latest ones.
4) Use buildkernel/installkernel target in /usr/src, instead of manual
config step (this will build you a GENERIC, which is also in order, just
in case your kernel configuration is somehow screwed).

-- 
Daniel C. Sobral			(8-DCS)
dcs@newsguy.com
dcs@freebsd.org
capo@zurichgnomes.bsdconspiracy.net

	One Unix to rule them all, One Resolver to find them,
        One IP to bring them all and in the zone bind them.



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


From owner-freebsd-stable  Mon Mar 27 20:23:19 2000
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 DA9ED37B99B
	for <freebsd-stable@FreeBSD.ORG>; Mon, 27 Mar 2000 20:23:14 -0800 (PST)
	(envelope-from dcs@newsguy.com)
Received: from newsguy.com (p29-dn03kiryunisiki.gunma.ocn.ne.jp [210.232.224.158])
	by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id NAA19149;
	Tue, 28 Mar 2000 13:23:05 +0900 (JST)
Message-ID: <38E030AD.921A90B4@newsguy.com>
Date: Tue, 28 Mar 2000 13:10:21 +0900
From: "Daniel C. Sobral" <dcs@newsguy.com>
X-Mailer: Mozilla 4.7 [en] (Win98; I)
X-Accept-Language: en,pt-BR,ja
MIME-Version: 1.0
To: Stan Brown <stanb@netcom.com>
Cc: FreeBSD Stable List <freebsd-stable@FreeBSD.ORG>
Subject: Re: 4.0 STABLE CVSUP tags?
References: <200003261510.HAA01165@netcom.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Stan Brown wrote:
> 
>         Building my first 4.0 machine.
> 
>         Could someone please give me the tags for 4.0 STABLE, and the ports
>         tree for it. Probably need the 4.0 security set tag also.
> 
>         Also, I have a CD subscrbtion to SATBLE. Will I automaticly start
>         recieveing the 4.0 branch, or do I need to call?

Try 4.x-stable-supfile and 4.x-secure-stable-supfile.

-- 
Daniel C. Sobral			(8-DCS)
dcs@newsguy.com
dcs@freebsd.org
capo@zurichgnomes.bsdconspiracy.net

	One Unix to rule them all, One Resolver to find them,
        One IP to bring them all and in the zone bind them.




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


From owner-freebsd-stable  Mon Mar 27 20:42:11 2000
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 560D437B51F
	for <freebsd-stable@FreeBSD.ORG>; Mon, 27 Mar 2000 20:42:07 -0800 (PST)
	(envelope-from Cy.Schubert@uumail.gov.bc.ca)
Received: (from daemon@localhost)
	by point.osg.gov.bc.ca (8.8.7/8.8.8) id UAA16882;
	Mon, 27 Mar 2000 20:41:55 -0800
Received: from passer.osg.gov.bc.ca(142.32.110.29)
 via SMTP by point.osg.gov.bc.ca, id smtpda16880; Mon Mar 27 20:41:54 2000
Received: (from uucp@localhost)
	by passer.osg.gov.bc.ca (8.9.3/8.9.1) id UAA04770;
	Mon, 27 Mar 2000 20:41:54 -0800 (PST)
Received: from cwsys9.cwsent.com(10.2.2.1), claiming to be "cwsys.cwsent.com"
 via SMTP by passer9.cwsent.com, id smtpdJU4768; Mon Mar 27 20:40:55 2000
Received: (from uucp@localhost)
	by cwsys.cwsent.com (8.9.3/8.9.1) id UAA07738;
	Mon, 27 Mar 2000 20:40:54 -0800 (PST)
Message-Id: <200003280440.UAA07738@cwsys.cwsent.com>
Received: from localhost.cwsent.com(127.0.0.1), claiming to be "cwsys"
 via SMTP by localhost.cwsent.com, id smtpdit7734; Mon Mar 27 20:40:49 2000
X-Mailer: exmh version 2.1.1 10/15/1999
Reply-To: Cy Schubert - ITSD Open Systems Group <Cy.Schubert@uumail.gov.bc.ca>
From: Cy Schubert - ITSD Open Systems Group <Cy.Schubert@uumail.gov.bc.ca>
X-OS: FreeBSD 3.4-RELEASE
X-Sender: cy
To: David Gilbert <dgilbert@velocet.ca>
Cc: freebsd-stable@FreeBSD.ORG
Subject: Re: 4.0-STABLE dhcp conflicts. 
In-reply-to: Your message of "Mon, 27 Mar 2000 12:44:34 EST."
             <14559.40450.544687.51037@trooper.velocet.net> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 27 Mar 2000 20:40:48 -0800
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

n message <14559.40450.544687.51037@trooper.velocet.net>, David Gilbert 
writes
:
> It appears that when I run two (not sure if one does it) tcpdumps on
> the dhcp server, the dhcp clients don't get any responses to their
> queries.  Is there some flaw in the dhcpd bpf rules?

I suspect that the dhcp server set the interface to promiscuous mode so 
it can listen for broadcasts.  Tcpdump sets up an interface for 
promiscuous opertion and when you exit tcpdump it returns it to 
non-promiscuous operation.  Killing and restarting your dhcp server 
after exiting tcpdump should solve your problem, as it will set the 
interface up for promiscuous operation again.


Regards,                       Phone:  (250)387-8437
Cy Schubert                      Fax:  (250)387-5766
Team Leader, Sun/DEC Team   Internet:  Cy.Schubert@osg.gov.bc.ca
Open Systems Group, ITSD, ISTA
Province of BC

I



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


From owner-freebsd-stable  Mon Mar 27 20:53:29 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from jking1.lgc.com (jking1.lgc.com [134.132.228.2])
	by hub.freebsd.org (Postfix) with ESMTP id 9AA0F37B96B
	for <freebsd-stable@FreeBSD.ORG>; Mon, 27 Mar 2000 20:53:26 -0800 (PST)
	(envelope-from king@sstar.com)
Received: from marble (marble [134.132.228.8])
	by jking1.lgc.com (8.9.3/8.9.3) with SMTP id WAA04931;
	Mon, 27 Mar 2000 22:53:09 -0600 (CST)
	(envelope-from king@sstar.com)
Message-ID: <004f01bf9871$848e7c00$08e48486@marble>
From: "Jim King" <king@sstar.com>
To: "Cy Schubert - ITSD Open Systems Group" <Cy.Schubert@uumail.gov.bc.ca>,
	"David Gilbert" <dgilbert@velocet.ca>
Cc: <freebsd-stable@FreeBSD.ORG>
References: <200003280440.UAA07738@cwsys.cwsent.com>
Subject: Re: 4.0-STABLE dhcp conflicts. 
Date: Mon, 27 Mar 2000 22:53:09 -0600
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.6700
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Monday, March 27, 2000 10:40 PM, Cy Schubert - ITSD Open Systems Group
wrote:
> n message <14559.40450.544687.51037@trooper.velocet.net>, David Gilbert
> writes
> :
> > It appears that when I run two (not sure if one does it) tcpdumps on
> > the dhcp server, the dhcp clients don't get any responses to their
> > queries.  Is there some flaw in the dhcpd bpf rules?
>
> I suspect that the dhcp server set the interface to promiscuous mode so
> it can listen for broadcasts.  Tcpdump sets up an interface for
> promiscuous opertion and when you exit tcpdump it returns it to
> non-promiscuous operation.  Killing and restarting your dhcp server
> after exiting tcpdump should solve your problem, as it will set the
> interface up for promiscuous operation again.

I regularly run (and exit) tcpdump and it doesn't affect my DHCP server
(isc-dhcp2).  dhcpd keeps on handing out leases after tcpdump has exited.

syslog has "promiscuous mode enabled" and "promiscuous mode disabled" when I
start and exit tcpdump, which is a bit confusing.  I'm guessing that
promiscuous mode is on the entire time and the messages really mean
something like "promiscuous mode reference count incremented/decremented".

Jim




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


From owner-freebsd-stable  Mon Mar 27 21: 1:48 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from vinyl.sentex.ca (vinyl.sentex.ca [209.112.4.14])
	by hub.freebsd.org (Postfix) with ESMTP id 4303737BBEB
	for <freebsd-stable@FreeBSD.ORG>; Mon, 27 Mar 2000 21:01:45 -0800 (PST)
	(envelope-from mike@sentex.net)
Received: from granite.sentex.net (granite-atm.sentex.ca [209.112.4.1])
	by vinyl.sentex.ca (8.9.3/8.9.3) with ESMTP id AAA94551
	for <freebsd-stable@FreeBSD.ORG>; Tue, 28 Mar 2000 00:01:41 -0500 (EST)
	(envelope-from mike@sentex.net)
Received: from chimp (ospf-mdt.sentex.net [205.211.164.81]) by granite.sentex.net (8.8.8/8.6.9) with ESMTP id AAA18320 for <freebsd-stable@FreeBSD.ORG>; Tue, 28 Mar 2000 00:01:40 -0500 (EST)
Message-Id: <4.2.2.20000327235718.035e5de8@mail.sentex.net>
X-Sender: mdtancsa@mail.sentex.net
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 
Date: Tue, 28 Mar 2000 00:01:57 -0500
To: freebsd-stable@FreeBSD.ORG
From: Mike Tancsa <mike@sentex.net>
Subject: DHCP at install time (was Re: 4.0-STABLE dhcp conflicts. )
In-Reply-To: <200003280440.UAA07738@cwsys.cwsent.com>
References: <Your message of "Mon, 27 Mar 2000 12:44:34 EST." <14559.40450.544687.51037@trooper.velocet.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


Actually, while on the topic of DHCP, (I didnt have a chance to double 
check this), but as I was installing a new 4.0R box today via a net 
install, I accidentally chose "Shall I try DHCP" to get the initial IP 
address.  After it failed, I tried to manually specify it, but to no 
avail.  Looking at the debug screen, it said the interface had gone 
down.  It was an Intel NIC.  Has anyone else seen this behaviour ?  I have 
another machine to put together with the same hardware later this week and 
I will see if I can repeat the problem consistently.

	---Mike



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


From owner-freebsd-stable  Mon Mar 27 21: 4:21 2000
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 8792C37BA08
	for <freebsd-stable@FreeBSD.ORG>; Mon, 27 Mar 2000 21:04:19 -0800 (PST)
	(envelope-from Cy.Schubert@uumail.gov.bc.ca)
Received: (from daemon@localhost)
	by point.osg.gov.bc.ca (8.8.7/8.8.8) id VAA16963;
	Mon, 27 Mar 2000 21:04:16 -0800
Received: from passer.osg.gov.bc.ca(142.32.110.29)
 via SMTP by point.osg.gov.bc.ca, id smtpda16961; Mon Mar 27 21:03:56 2000
Received: (from uucp@localhost)
	by passer.osg.gov.bc.ca (8.9.3/8.9.1) id VAA04869;
	Mon, 27 Mar 2000 21:03:56 -0800 (PST)
Received: from cwsys9.cwsent.com(10.2.2.1), claiming to be "cwsys.cwsent.com"
 via SMTP by passer9.cwsent.com, id smtpdaw4853; Mon Mar 27 21:02:56 2000
Received: (from uucp@localhost)
	by cwsys.cwsent.com (8.9.3/8.9.1) id VAA07911;
	Mon, 27 Mar 2000 21:02:54 -0800 (PST)
Message-Id: <200003280502.VAA07911@cwsys.cwsent.com>
Received: from localhost.cwsent.com(127.0.0.1), claiming to be "cwsys"
 via SMTP by localhost.cwsent.com, id smtpdiF7900; Mon Mar 27 21:02:40 2000
X-Mailer: exmh version 2.1.1 10/15/1999
Reply-To: Cy Schubert - ITSD Open Systems Group <Cy.Schubert@uumail.gov.bc.ca>
From: Cy Schubert - ITSD Open Systems Group <Cy.Schubert@uumail.gov.bc.ca>
X-OS: FreeBSD 3.4-RELEASE
X-Sender: cy
To: "Jim King" <king@sstar.com>
Cc: "Cy Schubert - ITSD Open Systems Group" <Cy.Schubert@uumail.gov.bc.ca>,
	"David Gilbert" <dgilbert@velocet.ca>, freebsd-stable@FreeBSD.ORG
Subject: Re: 4.0-STABLE dhcp conflicts. 
In-reply-to: Your message of "Mon, 27 Mar 2000 22:53:09 CST."
             <004f01bf9871$848e7c00$08e48486@marble> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 27 Mar 2000 21:02:40 -0800
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

In message <004f01bf9871$848e7c00$08e48486@marble>, "Jim King" writes:
> On Monday, March 27, 2000 10:40 PM, Cy Schubert - ITSD Open Systems Group
> wrote:
> > n message <14559.40450.544687.51037@trooper.velocet.net>, David Gilbert
> > writes
> > :
> > > It appears that when I run two (not sure if one does it) tcpdumps on
> > > the dhcp server, the dhcp clients don't get any responses to their
> > > queries.  Is there some flaw in the dhcpd bpf rules?
> >
> > I suspect that the dhcp server set the interface to promiscuous mode so
> > it can listen for broadcasts.  Tcpdump sets up an interface for
> > promiscuous opertion and when you exit tcpdump it returns it to
> > non-promiscuous operation.  Killing and restarting your dhcp server
> > after exiting tcpdump should solve your problem, as it will set the
> > interface up for promiscuous operation again.
> 
> I regularly run (and exit) tcpdump and it doesn't affect my DHCP server
> (isc-dhcp2).  dhcpd keeps on handing out leases after tcpdump has exited.
> 
> syslog has "promiscuous mode enabled" and "promiscuous mode disabled" when I
> start and exit tcpdump, which is a bit confusing.  I'm guessing that
> promiscuous mode is on the entire time and the messages really mean
> something like "promiscuous mode reference count incremented/decremented".

It was just a guess.  I've been wrong before and this wasn't the last 
time.


Regards,                       Phone:  (250)387-8437
Cy Schubert                      Fax:  (250)387-5766
Team Leader, Sun/DEC Team   Internet:  Cy.Schubert@osg.gov.bc.ca
Open Systems Group, ITSD, ISTA
Province of BC





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


From owner-freebsd-stable  Mon Mar 27 22:32:38 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169])
	by hub.freebsd.org (Postfix) with ESMTP id 35CA837B5CF
	for <stable@FreeBSD.ORG>; Mon, 27 Mar 2000 22:32:34 -0800 (PST)
	(envelope-from ken@panzer.kdm.org)
Received: (from ken@localhost)
	by panzer.kdm.org (8.9.3/8.9.1) id XAA02171;
	Mon, 27 Mar 2000 23:31:51 -0700 (MST)
	(envelope-from ken)
Date: Mon, 27 Mar 2000 23:31:51 -0700
From: "Kenneth D. Merry" <ken@kdm.org>
To: Mikhail Teterin <mi@aldan.algebra.com>
Cc: stable@FreeBSD.ORG
Subject: Re: panic on a flaky SCSI CD
Message-ID: <20000327233150.A2097@panzer.kdm.org>
References: <200003280401.XAA12345@xxx.video-collage.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0i
In-Reply-To: <200003280401.XAA12345@xxx.video-collage.com>; from mi@video-collage.com on Mon, Mar 27, 2000 at 11:01:26PM -0500
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Mon, Mar 27, 2000 at 23:01:26 -0500, mi@video-collage.com wrote:
> I have this flaky SCSI CD, which works sometimes :)
> When it fails, I see something like the following
> popping up:
> 
> Creating DISK cd0
> (cd0:ncr1:0:6:0): got CAM status 0x4a
> (cd0:ncr1:0:6:0): fatal error, failed to attach to device
> (cd0:ncr1:0:6:0): lost device
> (cd0:ncr1:0:6:0): removing device entry

That is caused by a selection timeout.  There's not a whole lot we can do
about that.

> Under 3.4, if I was to try to mount a CD in this drive,
> when it was in the bad mood, I'd simply get an error. Now,
> with 4.0 the thing panics :(

That's not good.  In order to find the problem, we'll need a little more
information.  Take a look at the handbook section on kernel debugging:

http://www.freebsd.org/handbook/kerneldebug.html

Configure your system to make a crash dump, and then get a stack trace from
gdb.  That should provide enough information to find the problem.

Thanks,

Ken
-- 
Kenneth Merry
ken@kdm.org


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


From owner-freebsd-stable  Mon Mar 27 22:39:16 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from proxy.outblaze.com (proxy.outblaze.com [202.77.223.120])
	by hub.freebsd.org (Postfix) with SMTP id A4B9137B8DA
	for <freebsd-stable@freebsd.org>; Mon, 27 Mar 2000 22:39:12 -0800 (PST)
	(envelope-from yusufg@outblaze.com)
Received: (qmail 16479 invoked from network); 28 Mar 2000 06:39:04 -0000
Received: from unknown (HELO yusufg.portal2.com) (202.77.181.217)
  by proxy.outblaze.com with SMTP; 28 Mar 2000 06:39:04 -0000
Received: (qmail 4736 invoked by uid 500); 28 Mar 2000 06:39:03 -0000
Date: 28 Mar 2000 06:39:03 -0000
Message-ID: <20000328063903.4735.qmail@yusufg.portal2.com>
From: Yusuf Goolamabbas <yusufg@outblaze.com>
To: freebsd-stable@freebsd.org
Subject: sysinstall doesn't seem to enable network properly
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hi, I downloaded the 4.0-RELEASE iso and after verifying MD5 checksum,
burned a CD Whilst installing FreeBSD 4.0 on an Intel 2U rack mount
platform, I observe that after configuring the network interface
(onboard eepro100 listed as fxp0) and saying yes to the question
"Shall I bring the network interface up now", installation hangs with
a blank screen. The only way out is to press Ctrl-C which aborts the
entire installation
  
However, if I switch to a different virtual console and do a ping to
the gateway specified earlier, it works

I did an install without configuring networking and after a reboot,
started /stand/sysinstall and configured the network. After saying yes
to the question "Shall I bring up the network interface up now", I did
a ifconfig -a and didn't see the IP address listed nor the default
route setup

Is anybody else seeing similar behaviour. I have done various installs
with/without crypto and it still is the same

-- 
Yusuf Goolamabbas
yusufg@outblaze.com


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


From owner-freebsd-stable  Mon Mar 27 23:17:57 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from relay.ucb.crimea.ua (UCB-Async4-CRISCO.CRIS.NET [212.110.129.130])
	by hub.freebsd.org (Postfix) with ESMTP id 5085D37BD65
	for <freebsd-stable@FreeBSD.ORG>; Mon, 27 Mar 2000 23:17:49 -0800 (PST)
	(envelope-from ru@ucb.crimea.ua)
Received: (from ru@localhost)
	by relay.ucb.crimea.ua (8.9.3/8.9.3/UCB) id KAA12097;
	Tue, 28 Mar 2000 10:09:32 +0300 (EEST)
	(envelope-from ru)
Date: Tue, 28 Mar 2000 10:09:32 +0300
From: Ruslan Ermilov <ru@ucb.crimea.ua>
To: Stan Brown <stanb@netcom.com>
Cc: FreeBSD Stable List <freebsd-stable@FreeBSD.ORG>
Subject: Re: 4.0 STABLE make world failure
Message-ID: <20000328100932.C7725@relay.ucb.crimea.ua>
Mail-Followup-To: Stan Brown <stanb@netcom.com>,
	FreeBSD Stable List <freebsd-stable@FreeBSD.ORG>
References: <200003280101.RAA29060@netcom.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.3i
In-Reply-To: <200003280101.RAA29060@netcom.com>; from Stan Brown on Mon, Mar 27, 2000 at 08:01:28PM -0500
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Mon, Mar 27, 2000 at 08:01:28PM -0500, Stan Brown wrote:
> 	OK, it failed this morning, so I re-cvsuped and it fails again.
> 
> 	in ppp/chap_ms.c trying to include openssl/des.h 
> 
> 	Anyone know what I am doing wrong?
> 
Your supfile worth showing...

-- 
Ruslan Ermilov		Sysadmin and DBA of the
ru@ucb.crimea.ua	United Commercial Bank,
ru@FreeBSD.org		FreeBSD committer,
+380.652.247.647	Simferopol, Ukraine

http://www.FreeBSD.org	The Power To Serve
http://www.oracle.com	Enabling The Information Age


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


From owner-freebsd-stable  Mon Mar 27 23:18: 7 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from relay.ucb.crimea.ua (UCB-Async4-CRISCO.CRIS.NET [212.110.129.130])
	by hub.freebsd.org (Postfix) with ESMTP id 4861937BD80
	for <stable@FreeBSD.ORG>; Mon, 27 Mar 2000 23:17:57 -0800 (PST)
	(envelope-from ru@ucb.crimea.ua)
Received: (from ru@localhost)
	by relay.ucb.crimea.ua (8.9.3/8.9.3/UCB) id KAA12091;
	Tue, 28 Mar 2000 10:08:41 +0300 (EEST)
	(envelope-from ru)
Date: Tue, 28 Mar 2000 10:08:40 +0300
From: Ruslan Ermilov <ru@ucb.crimea.ua>
To: Mikhail Teterin <mi@aldan.algebra.com>
Cc: stable@FreeBSD.ORG
Subject: Re: top, systat )-: (all rebuilt!)
Message-ID: <20000328100840.B7725@relay.ucb.crimea.ua>
Mail-Followup-To: Mikhail Teterin <mi@aldan.algebra.com>,
	stable@FreeBSD.ORG
References: <200003280100.UAA12045@xxx.video-collage.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.3i
In-Reply-To: <200003280100.UAA12045@xxx.video-collage.com>; from mi@video-collage.com on Mon, Mar 27, 2000 at 07:59:58PM -0500
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Do you use loader(8), or directly boot your kernel from boot blocks?

On Mon, Mar 27, 2000 at 07:59:58PM -0500, mi@video-collage.com wrote:
> Hello!  I did  the entire  procedure described  in UPDATING  to go  from
> 3.4-STABLE to 4.0-STABLE last night.
> 
> Most of the things work, but the  top, and systat. And Xaccel (from XiG)
> can not  find a  single free  terminal to run  anymore. Although,  all 8
> gettys are running fine.
> 
> Here is an attempt to proof my sanity:
> 
> 	root@rtfm:/usr/src (114) ls -l `which top`
> 	-r-xr-sr-x  1 root  kmem  32224 Mar 27 18:14 /usr/bin/top
> 	root@rtfm:/usr/src (115) ldd !$
> 	ldd `which top`
> 	/usr/bin/top:
> 		libncurses.so.5 => /usr/lib/libncurses.so.5 (0x1806b000)
> 		libm.so.2 => /usr/lib/libm.so.2 (0x180aa000)
> 		libkvm.so.2 => /usr/lib/libkvm.so.2 (0x180c6000)
> 		libc.so.4 => /usr/lib/libc.so.4 (0x180cc000)
> 	root@rtfm:/usr/src (116) ls -l /usr/lib/libncurses.so.5 \
> 		/usr/lib/libm.so.2 /usr/lib/libkvm.so.2 /usr/lib/libc.so.4
> 	-r--r--r--  1 root  wheel  539604 Mar 27 18:10 /usr/lib/libc.so.4
> 	-r--r--r--  1 root  wheel   18196 Mar 27 18:10 /usr/lib/libkvm.so.2
> 	-r--r--r--  1 root  wheel  117180 Mar 27 18:09 /usr/lib/libm.so.2
> 	-r--r--r--  1 root  wheel  246712 Mar 27 18:09 /usr/lib/libncurses.so.5
> 	root@rtfm:/usr/src (117) uname -a
> 	FreeBSD rtfm.newton 4.0-STABLE FreeBSD 4.0-STABLE #1: \
> 		Mon Mar 27 05:13:38 EST 2000
> 		mi@rtfm.newton:/4G/src/sys/compile/RTFM2  i386
> 	root@rtfm:/usr/src (118) top
> 	top: nlist failed
> 	root@rtfm:/usr/src (119) ls -l /kernel
> 	-r-xr-xr-x  1 root  wheel  2358025 Mar 27 05:16 /kernel
> 	root@rtfm:/usr/src (120) sysctl kern.bootfile
> 	kern.bootfile: /kernel
> 	root@rtfm:/usr/src (121) ls -lt /4G/src/sys/compile/RTFM2 | tail -1
> 	-rw-rw-r--  1 mi  wheel     5893 Mar 27 04:58 ioconf.c
> 
> systat dies similarly:
> 
> 	systat: nlist: can't find following symbols:
> 	_bufspace
> 	_numvnodes
> 	_freevnodes
> 	_numdirtybuffers
> 
> but w and uptime work just fine...
> 
> I   did    the   buildworld,   the   installed    mknod   and   modules.
> build/installkernel,  reboot to  single-user. Installed  world again  as
> prescribed,  rebooted to  multiuser. The  Xaccel was  working, but  top,
> systat were not.  I rebuilt the kernel again, rebooted.  Xaccel does not
> come up,  neither does top or  systat. I rebuilt and  re-installed world
> and top and systat still don't work :(
> 
> Any ideas? Thanks!
> 
> 	-mi

-- 
Ruslan Ermilov		Sysadmin and DBA of the
ru@ucb.crimea.ua	United Commercial Bank,
ru@FreeBSD.org		FreeBSD committer,
+380.652.247.647	Simferopol, Ukraine

http://www.FreeBSD.org	The Power To Serve
http://www.oracle.com	Enabling The Information Age


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


From owner-freebsd-stable  Tue Mar 28  0:42:38 2000
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 693E337BAD3
	for <FreeBSD-Stable@FreeBSD.ORG>; Tue, 28 Mar 2000 00:42:34 -0800 (PST)
	(envelope-from dcs@newsguy.com)
Received: from newsguy.com (p14-dn01kiryunisiki.gunma.ocn.ne.jp [211.0.245.15])
	by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id RAA19428;
	Tue, 28 Mar 2000 17:40:38 +0900 (JST)
Message-ID: <38E065C5.418DA948@newsguy.com>
Date: Tue, 28 Mar 2000 16:56:53 +0900
From: "Daniel C. Sobral" <dcs@newsguy.com>
X-Mailer: Mozilla 4.7 [en] (Win98; I)
X-Accept-Language: en,pt-BR,ja
MIME-Version: 1.0
To: Alexandr Listopad <laa@ZGIA.zp.ua>
Cc: Kuzak <kuzak@kuzak.net>, FreeBSD-Stable@FreeBSD.ORG
Subject: Re: 4.0 Kernel
References: <Pine.BSF.4.10.10003271228100.48901-100000@Eagle.ZGIA.zp.ua>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Alexandr Listopad wrote:
> 
> # -- sysinstall generated deltas -- #
> userconfig_script_load="NO"
> autoboot_delay="0"
> 
> splash_bmp_load="YES"
> bitmap_load="YES"
> bitmap_name="/boot/daemon.bmp"  # Set this to the name of
> the bmp or pcx file
> bitmap_type="splash_image_data"
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
This line is not necessary, as it is already set by default.

-- 
Daniel C. Sobral			(8-DCS)
dcs@newsguy.com
dcs@freebsd.org
capo@zurichgnomes.bsdconspiracy.net

	The size of the pizza is inversely proportional to the intensity of the
hunger.




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


From owner-freebsd-stable  Tue Mar 28  1:32:10 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from ipamzlx.physik.uni-mainz.de (ipamzlx.Physik.Uni-Mainz.DE [134.93.180.54])
	by hub.freebsd.org (Postfix) with ESMTP
	id 6E03E37BDDF; Tue, 28 Mar 2000 01:32:04 -0800 (PST)
	(envelope-from ohartman@ipamzlx.physik.uni-mainz.de)
Received: from ipamzlx.Physik.Uni-Mainz.DE (ipamzlx.Physik.Uni-Mainz.DE [134.93.180.54])
	by ipamzlx.physik.uni-mainz.de (8.9.3/8.9.3) with ESMTP id LAA30361;
	Tue, 28 Mar 2000 11:32:03 +0200 (CEST)
	(envelope-from ohartman@ipamzlx.physik.uni-mainz.de)
Date: Tue, 28 Mar 2000 11:32:02 +0200 (CEST)
From: "O. Hartmann" <ohartman@ipamzlx.physik.uni-mainz.de>
To: freebsd-smp@freebsd.org
Cc: freebsd-stable@freebsd.org
Subject: FBSD 4.0 on ALR Revolution Q-SMP
Message-ID: <Pine.BSF.4.10.10003281120340.30095-100000@ipamzlx.physik.uni-mainz.de>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Dear Sirs.
We own two Siemens/Nixdorf PCE-5Smp machines, originally relabeled
ALR Revolution Q-SMP. 
The Phoenix BIOS Revision is 4.04.3.
The system has 256 MB of RAM, three CPUs (the other  one has only two),
Mylex DAC960PD RAID 5. FreeBSD only runs in UP kernel, trying mptable
to figure out the MP tables and configuration shows messed up things.
In BIOS SMP specifications are switched to MP Spec (it is said that this
machine is then compliant to MP Spec 1.4). 

Now I fell into trouble! On the one hand, SMP won't work! So I thought about a
BIOS update and at Gateway's site I found a newer one. Preparing a bootdisk for
installation of the flash BIOS was easy, I can boot the machine. Then I was asked
to press RESET and release it for updating the BIOS. I pushed all the butoons on the
front panel (execpt power on and power down) on the right panel, but nothing happend.
Where is the RESET button? has anyone successfully installed FBSD on this type of SMP
system?

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

Klimadatenserver des IPA, Universitaet Mainz
Netzwerk- und Systembetreuung



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


From owner-freebsd-stable  Tue Mar 28  1:37: 1 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from knight.cons.org (knight.cons.org [194.233.237.86])
	by hub.freebsd.org (Postfix) with ESMTP id EDB7037BDF0
	for <freebsd-stable@freebsd.org>; Tue, 28 Mar 2000 01:36:39 -0800 (PST)
	(envelope-from cracauer@knight.cons.org)
Received: (from cracauer@localhost)
	by knight.cons.org (8.9.3/8.9.3) id LAA28198
	for freebsd-stable@freebsd.org; Tue, 28 Mar 2000 11:36:35 +0200 (CEST)
Date: Tue, 28 Mar 2000 11:36:34 +0200
From: Martin Cracauer <cracauer@cons.org>
To: freebsd-stable@freebsd.org
Subject: Let 3.x die ASAP?
Message-ID: <20000328113633.A28085@cons.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0.1i
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

A bit of a controvesical question, for sure. 

I am so impressed with the results of upgrading my more important
machines to 4.0 or 4-stable that I could imagine not to produce any
more 3.x releases.

Let us consider what happens when we release 3.5 before or at the same
time as 4.1:
- People will publish reviews based on 3.5 instead of 4.1. As usual,
  an unadaequate number of them running on SMP machines.
- People will run into inferious hardware support, especially they
  will have trouble with large IDE disks and/or IDE PCI controller.
  Similar issues for Laptop users.
- People will continue to run with inferiour NFS, Linux emulator etc.
  The same applies to networking fixes against attacks, especially
  DOS.
- People will choose 3.5 over 4.1 and will later go through an
  3.x->4.x upgrade for no good reason.
- The remaining issues in 4.x (especially hardware) aren't addressed
  as fast. There will be some issues with "unclean" usage that the
  core userbase doesn't use that don't come up until the masses jump
  on them.

For me, the real reason is that I now hate the latest 3.x after seeing
the improvements. It is near to junk, IMHO.

Several machine of mine had gone instable while moving from 3.[01] to
3.4-stable and I suspected hardware trouble. I didn't debug it because
I didn't want to mess with 3.x anymore. Now after upgrading to 4.x the
same machines are rock-stable again. It is my impression that the 3.x
branch lost the required testing when the core committers moved to
4.0-current. Higher releases of 3.x are just not polished/tested
enough anymore, beside the undoubted concrete bug fixes.

Speaking of testing by committers, I also hate to have machines for
three branches running to develop bugfixes that apply to more than
-current. In fact my last 3.x machine (besides a 3.1 machine that
doesn't have the IDE troubles I have with 3.4-stable) is now a
production machine of my employer that I'd like to upgrade as well. I
couldn't think of a good reason to delay that upgrade for 3 or 6
months if my boss asked me. When i upgrade, I had to commit userland
bugfixes to 3.x with only testing them on a newer branch. Kernel
bugfixes would be impossible unless I find someone to test them for
me.

I assume that I'm not alone here. That many bug-fixing committers will
not move with 3 machines along the current branches and that 3.5 will
not be a worthy successor to our previous *.5 releases.

Opinions?

Martin
-- 
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
Martin Cracauer <cracauer@cons.org> http://www.cons.org/cracauer/
  Tel.: (private) +4940 5221829 Fax.: (private) +4940 5228536


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


From owner-freebsd-stable  Tue Mar 28  2:56:41 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from front7.grolier.fr (front7.grolier.fr [194.158.96.57])
	by hub.freebsd.org (Postfix) with ESMTP id DB97537B956
	for <stable@freebsd.org>; Tue, 28 Mar 2000 02:56:18 -0800 (PST)
	(envelope-from pushf@club-internet.fr)
Received: (from mnet@localhost)
	by front7.grolier.fr (8.9.3/No_Relay+No_Spam_MGC990224) id MAA22616
	for stable@freebsd.org; Tue, 28 Mar 2000 12:56:16 +0200 (MET DST)
Date: Tue, 28 Mar 2000 12:56:16 +0200 (MET DST)
From: pushf@club-internet.fr
To: stable@freebsd.org
X-Mailer: Medianet/v1.13
Message-Id: <mnet1.954240976.21608.pushf@club-internet.fr>
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

unsubscribe stable


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


From owner-freebsd-stable  Tue Mar 28  5: 8:52 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from support.euronet.nl (support.euronet.nl [194.134.32.134])
	by hub.freebsd.org (Postfix) with ESMTP id 4076B37BE26
	for <stable@FreeBSD.ORG>; Tue, 28 Mar 2000 05:08:48 -0800 (PST)
	(envelope-from pieterw@support.euronet.nl)
Received: (from pieterw@localhost)
	by support.euronet.nl (8.10.0/8.10.0) id e2SD7E916515;
	Tue, 28 Mar 2000 15:07:14 +0200 (CEST)
Date: Tue, 28 Mar 2000 15:07:14 +0200
From: Pieter Westland <pieterw@euronet.nl>
To: Mark Ovens <mark@dogma.freebsd-uk.eu.org>
Cc: stable@FreeBSD.ORG
Subject: Re: HEADS UP: 3.x -> 4.0-STABLE upgrade instructions
Message-ID: <20000328150714.A23199@support.euronet.nl>
References: <20000315174557.C40984@relay.ucb.crimea.ua> <200003151903.MAA88473@harmony.village.org> <005701bf8eb3$b02b2150$a44b8486@jking> <20000315210705.A244@parish>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0i
In-Reply-To: <20000315210705.A244@parish>; from mark@dogma.freebsd-uk.eu.org on Wed, Mar 15, 2000 at 09:07:05PM +0000
X-OS: FreeBSD support.euronet.nl 2.2.8-STABLE FreeBSD 2.2.8-STABLE 
X-URL: http://support.euronet.nl/~pieterw
X-Editor: vim
X-Quote: Economics is fun!
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Wed, Mar 15, 2000 at 09:07:05PM +0000, Mark Ovens wrote:
[snip]
> This message appeared 166 times during ``make buildworld'':
> 	/usr/libexec/ld-elf.so.1: Shared object "libc.so.4" not found
> It also caused config(8) on the new kernel to fail, but
> 	ldconfig -R /usr/obj/usr/src/lib/libc
> cured that.


Hi there,

A few hours ago I moved my machine from 3.4-STABLE to 4.0 . I also got
that errormessages about libc.so.4 during make buildworld. A ldconfig, as
mentioned by Mark, solved the problem. Will this command be included in
the make buildworld-process?

The rest of the upgrade went almost fine. I got into trouble when trying to 
do a 'make -j4 installworld', but that was because staring at the console had
tired me... It caused the machine to be unable to find some files.

The other problem is that X does not want to let me log in; getting the 
following message in the log when trying to log in (starting xdm works,
but after entering login en password it displays a 'Incorrect
password'-message and logs):

Mar 28 09:07:50 dustpuppy -:0: unable to dlopen(/usr/lib/pam_unix.so)
Mar 28 09:07:50 dustpuppy -:0: [dlerror: /usr/lib/libutil.so.3: Undefined
symbol "freeaddrinfo"]
Mar 28 09:07:50 dustpuppy -:0: adding faulty module: /usr/lib/pam_unix.so

At this moment I'm recompiling XFree86 (3.3.6), I hope the problem will be
solved after this.

Pieter
--
Finagle's Creed:
	Science is true.  Don't be misled by facts.


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


From owner-freebsd-stable  Tue Mar 28  5:39:20 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from storm.FreeBSD.org.uk (storm.freebsd.org.uk [194.242.139.170])
	by hub.freebsd.org (Postfix) with ESMTP id 0964937B54E
	for <stable@FreeBSD.ORG>; Tue, 28 Mar 2000 05:39:12 -0800 (PST)
	(envelope-from brian@Awfulhak.org)
Received: from hak.lan.Awfulhak.org (hak.nat.Awfulhak.org [172.31.0.12])
	by storm.FreeBSD.org.uk (8.9.3/8.9.3) with ESMTP id OAA64954;
	Tue, 28 Mar 2000 14:39:08 +0100 (BST)
	(envelope-from brian@Awfulhak.org)
Received: from hak.lan.Awfulhak.org (localhost [127.0.0.1])
	by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id OAA16573;
	Tue, 28 Mar 2000 14:39:06 +0100 (BST)
	(envelope-from brian@hak.lan.Awfulhak.org)
Message-Id: <200003281339.OAA16573@hak.lan.Awfulhak.org>
X-Mailer: exmh version 2.1.1 10/15/1999
To: Ian Hart <ianjhart@yahoo.com>
Cc: stable@FreeBSD.ORG, brian@hak.lan.Awfulhak.org
Subject: Re: tun0 lost in 4.0 
In-Reply-To: Message from Ian Hart <ianjhart@yahoo.com> 
   of "Mon, 27 Mar 2000 13:13:04 -0800." <20000327211304.16647.qmail@web204.mail.yahoo.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Tue, 28 Mar 2000 14:39:06 +0100
From: Brian Somers <brian@Awfulhak.org>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> Brian Somers wrote:
> > 
> > > Walter Brameld wrote:
> > > >
> > > > On Sun, 19 Mar 2000, in a never-ending search
> for
> > > enlightenment, Sergei Vyshenski wrote:
> > > > > Can not revive tun0 interface after moving to
> 4.0
> > > from 3.4
> > > > > in a way that src/UPDATING teaches.
> > > > >
> > > > > Kernel file has "pseudo-device   tun     1",
> > > kernel builds ok;
> > > > > ./MAKEDEV tun0 in /dev does not complain;
> > > > > bbut ifconfig says: "interface tun0 does not
> > > exist"
> > > > >
> > > > > Actually, I need tun0 to accept incoming
> user-ppp,
> > > > > and would be happy to hear of workaround at
> least.
> > > > >
> > > > > Thank you in advance.
> > > > > Sergei
> > > >
> > > > Believe it should only be "pseudo-device tun"
> with
> > > no "1".
> > > >
> > > > --
> > > > Walter Brameld
> > >
> > > Sergei, did you fix your problem?
> > >
> > > A bit late on this thread I know. The reason being
> -
> > > no modem for over a week. When I ran ppp and went
> to
> > > terminal mode there was no response at all from
> the
> > > modem. I was running 4.0-STABLE. Was A1 under
> > > 3.4-STABLE. I managed to get online (very) early
> > > Saturday morning to cvsup. Sometime during the
> power
> > > down/make world/reading of 500+ emails it broke
> again.
> > > It's currently working (obviously), but I'm too
> > > paranoid to do anything in case I break it again.
> I
> > > have set pseudo-device tun 1, contrary to GENERIC
> > > setting.
> > 
> > You shouldn't even need this line.  Ppp(8) will load
> the module if it
> > needs to.  The fact that ppp actually started means
> that there are no
> > tun(4) related problems.  If you're getting no
> response from the
> > modem, then you really need to look in that
> direction.

Euch... your mailer is wrapping lines horribly.....

> If terminal mode passes through tun0 then it needs to
> be considered. Otherwise not. I'm in the dark here.

Ppp opens the tun device at startup.  It's only used to read and 
write packets to the tun interface.  Talking to the modem is a 
separate thing.

> > > The modem is a no-name (ORIGO) 56k6 Rockwell
> Voice,
> > > ISA with jumpers, set to COM 4 IRQ 9. Tried in the
> two
> > > machines I have at home. One with PNP COM ports,
> the
> > > other not. Could be broken hardware of course.
> > 
> > Hmm, I tend to avoid irq 2/9....
> 
> I've tried all the _normal_ settings with the same
> result. Ppp loads fine, but there is no response to
> any input in terminal mode. In order to get the modem
> to work I had to trash my NT partition and install
> Win95. Even then the normally reliable setup failed to
> detect the modem. It was only when I set the CMOS to
> PNP O/S and did find new hardware that the modem
> revived. Is FreeBSD now a PNP O/S? Now I didn't want
> to mention this before, due to the flame war, but...
> This modem was designed to be PNP or jumpered. The
> jumper has been bridged to disable PNP at the factory.
> (Doesn't work?) I don't suppose that this could be
> confusing the start up probes in some way. This is a
> genuine suggestion please don't flame me! Just tell me
> how I can make the probe more verbose?
> 
> I know I won't get much help without logs, but if I
> break the modem again I could be off line some time. I
> need as much information as I can get before I reboot.

<my understanding>
I'm no expert in this area, but basically, a PnP OS is one that's 
willing to assign resources to PnP cards.  If you tell the BIOS that 
the OS is *not* PnP, the BIOS will assign them itself.

FreeBSD is *not* a PnP OS as it expects the cards to already know 
what resources they're using.

However, FreeBSD needs to know the PnP ID of a given card if it wants 
to do interesting stuff with it.  There are tables of these IDs in 
various places in the source code, so what I suspect you need to do 
is boot with the -v option and get the PnP ID then get someone to 
update the sources.
</my understanding>

> > > I also find I can no longer authenticate on
> freeserve
> > > (UK). X-stream is okay. Can someone who uses
> freeserve
> > > confirm/deny connection with 4.0-STABLE. Could be
> > > broken ISP of course.
> > 
> > Have you built ppp with DES ?  You should see be a
> -DHAVE_DES option on
> > the cc line when building.  Also, make sure you
> haven't got any #
> > characters in you password - if you have, you'll
> need to quote ("")
> > the password string or escape the #.
> > 
> 
> This is a secondry issue as I can at least connect via
> x-stream. AFAIK I have a _stock_ system, whatever that
> means. My understanding is that if the crypto sources
> are present make world sucks them in automatically.
> Please correct me if I am wrong. I did discover that
> mergemaster -s -v does what I thought mergemaster -s
> did. RTFM. What cruft there was looks harmless to me.
> I do have USA_RESIDENT = NO set in /etc/make.conf.
> What do I need to add to make the build behave as
> setting USA_RESIDENT= YES would do. The comment in
> make.conf suggests that this is only for ports.
> /etc/defaults/make.conf seems to enable all crypto
> stuff unless you uncomment the NOxxx= true lines.
> HAVE_DES is not mentioned there.

The DES stuff will build if /usr/src/secure exists.

> If all my mailing lists wren't sent to freeserve I'd
> just swap ISP's and forget it. FYI x-stream is PAP.
> 
> > > Any assistance would be most welcome. I can
> provide
> > > dmesg or whatever, but I'm not sure that will help
> as
> > > it's currently okay. Could be broken 'userware' of
> > > course :-)
> > >
> > > On a positive note, at least I now know how to set
> up
> > > a gateway host and DNS servers. Next step - packet
> > > filtering and proxy servers. Joy Joy Joy.
> > >
> > > ian j hart
> > >
> > > PS. The upgrade 3.4-4.0 went more or less without
> a
> > > hitch. Slightly sweaty palms I couldn't remount /
> > > single user. Fixed that once I realised it was
> still
> > > on wd0 not ad0.
> > >
> > > PPS. This probably will not attach to the thread.
> I
> > > find I cannot send mail (ISP firewall?). Thank God
> for
> > > Yahoo in emergencies.
> > >
> > > __________________________________________________
> > > Do You Yahoo!?
> > > Talk to your friends online with Yahoo! Messenger.
> > > http://im.yahoo.com
> > 
> > --
> > Brian <brian@Awfulhak.org>                       
> <brian@[uk.]FreeBSD.org>
> >       <http://www.Awfulhak.org>                  
> <brian@[uk.]OpenBSD.org>
> > Don't _EVER_ lose your sense of humour !
> 
> Thanks for your reply BTW, I thought everyone had gone
> fishin' or something

Yeah, nobody invited me !

> TIA ian j hart
> 
> sending via Yahoo for previously stated reason.
> Doesn't seem to be forwarding so please REPLY TO:
> 
>  ianjhart@freeloader.freeserve.co.uk
> 
> 
> __________________________________________________
> Do You Yahoo!?
> Talk to your friends online with Yahoo! Messenger.
> http://im.yahoo.com

-- 
Brian <brian@Awfulhak.org>                        <brian@[uk.]FreeBSD.org>
      <http://www.Awfulhak.org>                   <brian@[uk.]OpenBSD.org>
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  Tue Mar 28  6:47:25 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from infos1.casaccia.enea.it (INFOS1.casaccia.enea.it [192.107.71.175])
	by hub.freebsd.org (Postfix) with ESMTP id 5182A37BF2E
	for <freebsd-stable@FreeBSD.ORG>; Tue, 28 Mar 2000 06:47:07 -0800 (PST)
	(envelope-from poggif@casaccia.enea.it)
Received: from studi7106 (STUDI7106.casaccia.enea.it [192.107.77.106])
	by infos1.casaccia.enea.it (8.9.1/8.9.1) with SMTP id PAA20494;
	Tue, 28 Mar 2000 15:40:51 +0200 (MET DST)
Message-Id: <3.0.5.32.20000328154001.00916840@infos1.casaccia.enea.it>
X-Sender: poggif@infos1.casaccia.enea.it
X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32)
Date: Tue, 28 Mar 2000 15:40:01 +0200
To: Martin Cracauer <cracauer@cons.org>
From: Fabrizio Poggi <poggif@casaccia.enea.it>
Subject: Re: Let 3.x die ASAP?
Cc: freebsd-stable@FreeBSD.ORG
In-Reply-To: <20000328113633.A28085@cons.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

At 11.36 28/03/00 +0200, you wrote:
>A bit of a controvesical question, for sure. 
...
>I am so impressed with the results of upgrading my more important
>machines to 4.0 or 4-stable that I could imagine not to produce any
>more 3.x releases.
...
>For me, the real reason is that I now hate the latest 3.x after seeing
>the improvements. It is near to junk, IMHO.
...
>Several machine of mine had gone instable while moving from 3.[01] to
>3.4-stable and I suspected hardware trouble. I didn't debug it because
>I didn't want to mess with 3.x anymore. Now after upgrading to 4.x the
>same machines are rock-stable again. It is my impression that the 3.x
>branch lost the required testing when the core committers moved to
>4.0-current. Higher releases of 3.x are just not polished/tested
>enough anymore, beside the undoubted concrete bug fixes.
...
>Opinions?
>
>Martin

Story of DOS. Some people use DOS3.1 some others DOS5.0; anyone remember
the 4.0? The 4.0 of DOS was the most ugly system ever seen at all. Bugs
like a bee-swarm. Maybe the 3 branch is not the more stable branch of
FreeBSD. If a 4.0 current is better... I use now at home the 3.4 -stable
without *any* problem (I thing the best system I ever had). Maybe under
hard working can give something bad. Maybe it can be a good thing if the
core development gives to people a chart of the more well response branch.
Not as absolute. Just the "suggested by the team" releases for have the
best from FreeBSD. For professionals that count on it. 

Regards, Fabrizio 


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


From owner-freebsd-stable  Tue Mar 28  6:53:29 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from kot.ne.mediaone.net (kot.ne.mediaone.net [24.218.15.190])
	by hub.freebsd.org (Postfix) with ESMTP id A600F37B6BA
	for <stable@freebsd.org>; Tue, 28 Mar 2000 06:53:24 -0800 (PST)
	(envelope-from mi@kot.ne.mediaone.net)
Received: from rtfm.newton (root@rtfm.newton [10.10.0.1])
	by kot.ne.mediaone.net (8.9.3/8.9.1) with ESMTP id JAA69315;
	Tue, 28 Mar 2000 09:53:20 -0500 (EST)
From: Mikhail Teterin <mi@kot.ne.mediaone.net>
X-Relay-IP: 10.10.0.1
Received: (from mi@localhost)
	by rtfm.newton (8.9.3/8.9.3) id JAA01102;
	Tue, 28 Mar 2000 09:53:20 -0500 (EST)
	(envelope-from mi@kot.ne.mediaone.net)
Message-Id: <200003281453.JAA01102@rtfm.newton>
Subject: Re: top, systat )-: (all rebuilt!)
In-Reply-To: <20000328100840.B7725@relay.ucb.crimea.ua> from Ruslan Ermilov at
 "Mar 28, 2000 10:08:40 am"
To: Ruslan Ermilov <ru@ucb.crimea.ua>
Date: Tue, 28 Mar 2000 09:53:20 -0500 (EST)
Cc: stable@freebsd.org
X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w<gv/&E-lL7twZCT8B~/PA4|\t$ti+22K">
	 hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli"<kcG^EOVih
	 y+z3/UR{6SCQ
X-Mailer: ELM [version 2.4ME+ PL60 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Ruslan Ermilov once stated:

=Do you use loader(8), or directly boot your kernel from boot blocks?

Directly... Is that what it is?!?

	-mi

=On Mon, Mar 27, 2000 at 07:59:58PM -0500, mi@video-collage.com wrote:
=> Hello! I  did the entire procedure  described in UPDATING to  go from
=> 3.4-STABLE to 4.0-STABLE last night.
=>
=> Most of  the things work, but  the top, and systat.  And Xaccel (from
=> XiG) can  not find a single  free terminal to run  anymore. Although,
=> all 8 gettys are running fine.
=> 
=> Here is an attempt to proof my sanity:
=> 
=> 	root@rtfm:/usr/src (114) ls -l `which top`
=> 	-r-xr-sr-x  1 root  kmem  32224 Mar 27 18:14 /usr/bin/top
=> 	root@rtfm:/usr/src (115) ldd !$
=> 	ldd `which top`
=> 	/usr/bin/top:
=> 		libncurses.so.5 => /usr/lib/libncurses.so.5 (0x1806b000)
=> 		libm.so.2 => /usr/lib/libm.so.2 (0x180aa000)
=> 		libkvm.so.2 => /usr/lib/libkvm.so.2 (0x180c6000)
=> 		libc.so.4 => /usr/lib/libc.so.4 (0x180cc000)
=> 	root@rtfm:/usr/src (116) ls -l /usr/lib/libncurses.so.5 \
=> 		/usr/lib/libm.so.2 /usr/lib/libkvm.so.2 /usr/lib/libc.so.4
=> 	-r--r--r--  1 root  wheel  539604 Mar 27 18:10 /usr/lib/libc.so.4
=> 	-r--r--r--  1 root  wheel   18196 Mar 27 18:10 /usr/lib/libkvm.so.2
=> 	-r--r--r--  1 root  wheel  117180 Mar 27 18:09 /usr/lib/libm.so.2
=> 	-r--r--r--  1 root  wheel  246712 Mar 27 18:09 /usr/lib/libncurses.so.5
=> 	root@rtfm:/usr/src (117) uname -a
=> 	FreeBSD rtfm.newton 4.0-STABLE FreeBSD 4.0-STABLE #1: \
=> 		Mon Mar 27 05:13:38 EST 2000
=> 		mi@rtfm.newton:/4G/src/sys/compile/RTFM2  i386
=> 	root@rtfm:/usr/src (118) top
=> 	top: nlist failed
=> 	root@rtfm:/usr/src (119) ls -l /kernel
=> 	-r-xr-xr-x  1 root  wheel  2358025 Mar 27 05:16 /kernel
=> 	root@rtfm:/usr/src (120) sysctl kern.bootfile
=> 	kern.bootfile: /kernel
=> 	root@rtfm:/usr/src (121) ls -lt /4G/src/sys/compile/RTFM2 | tail -1
=> 	-rw-rw-r--  1 mi  wheel     5893 Mar 27 04:58 ioconf.c
=> 
=> systat dies similarly:
=> 
=> 	systat: nlist: can't find following symbols:
=> 	_bufspace
=> 	_numvnodes
=> 	_freevnodes
=> 	_numdirtybuffers
=> 
=> but w and uptime work just fine...
=> 
=> I   did   the   buildworld,   the  installed   mknod   and   modules.
=> build/installkernel, reboot to single-user.  Installed world again as
=> prescribed, rebooted to  multiuser. The Xaccel was  working, but top,
=> systat were  not. I rebuilt  the kernel again, rebooted.  Xaccel does
=> not come up,  neither does top or systat. I  rebuilt and re-installed
=> world and top and systat still don't work :(
=> 
=> Any ideas? Thanks!


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


From owner-freebsd-stable  Tue Mar 28  7: 6:52 2000
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 4923C37BE7E
	for <freebsd-stable@FreeBSD.ORG>; Tue, 28 Mar 2000 07:06:47 -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.3/8.9.3) with ESMTP id RAA23047
	for <freebsd-stable@FreeBSD.ORG>; Tue, 28 Mar 2000 17:06:45 +0200 (MET DST)
Received: (from jesse@localhost)
	by knecht.cs.uni-magdeburg.de (8.8.8+Sun/8.8.8) id RAA20003;
	Tue, 28 Mar 2000 17:05:44 +0200 (MET DST)
X-Authentication-Warning: knecht.cs.uni-magdeburg.de: jesse set sender to jesse@cs.uni-magdeburg.de using -f
To: freebsd-stable@FreeBSD.ORG
Subject: Re: Let 3.x die ASAP?
References: <3.0.5.32.20000328154001.00916840@infos1.casaccia.enea.it>
From: Roland Jesse <jesse@mail.CS.Uni-Magdeburg.De>
In-Reply-To: Fabrizio Poggi's message of "Tue, 28 Mar 2000 15:40:01 +0200"
Date: 28 Mar 2000 17:05:44 +0200
Message-ID: <0v7lenqgmv.fsf@cs.uni-magdeburg.de>
Lines: 9
User-Agent: Gnus/5.0803 (Gnus v5.8.3) Emacs/20.4
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Fabrizio Poggi <poggif@casaccia.enea.it> writes:

> If a 4.0 current is better... I use now at home the 3.4 -stable
> without *any* problem

And you can continue doing so. Moving the -stable development from 3.x
to 4.x doesn't mean that RELENG_3 will no  longer be available.

        Roland


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


From owner-freebsd-stable  Tue Mar 28  7:13:20 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from pooh.elsevier.nl (pooh.elsevier.nl [145.36.13.27])
	by hub.freebsd.org (Postfix) with ESMTP id DC4AF37BFC9
	for <stable@freebsd.org>; Tue, 28 Mar 2000 07:13:04 -0800 (PST)
	(envelope-from steve@pooh.elsevier.nl)
Received: (from steve@localhost)
	by pooh.elsevier.nl (8.9.3/8.9.3) id QAA04381;
	Tue, 28 Mar 2000 16:17:30 +0100 (IST)
	(envelope-from steve)
Message-ID: <XFMail.000328161729.steveo@eircom.net>
X-Mailer: XFMail 1.4.0 on FreeBSD
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <200003281453.JAA01102@rtfm.newton>
Date: Tue, 28 Mar 2000 16:17:29 +0100 (IST)
From: "Steve O'Hara-Smith" <steveo@eircom.net>
To: Mikhail Teterin <mi@kot.ne.mediaone.net>
Subject: Re: top, systat )-: (all rebuilt!)
Cc: stable@freebsd.org, Ruslan Ermilov <ru@ucb.crimea.ua>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


On 28-Mar-00 Mikhail Teterin wrote:
> Ruslan Ermilov once stated:
> 
> =Do you use loader(8), or directly boot your kernel from boot blocks?
> 
> Directly... Is that what it is?!?

        Oh what a great time for a me too!

        I am seeing the same problems with top and systat (I hadn't noticed
until now). I am also loading direct to /kernel instead of using loader (I just
tried loader and got some troubles - another thread maybe).

        FWIW I am using 4.0-stable cvsupped about two days ago on a Compaq
PRESARIO 1690 laptop with an AMD K6-II.



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


From owner-freebsd-stable  Tue Mar 28  7:16:25 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from relay.ucb.crimea.ua (relay.ucb.crimea.ua [212.110.138.1])
	by hub.freebsd.org (Postfix) with ESMTP
	id BF84237BF60; Tue, 28 Mar 2000 07:15:03 -0800 (PST)
	(envelope-from ru@ucb.crimea.ua)
Received: (from ru@localhost)
	by relay.ucb.crimea.ua (8.9.3/8.9.3/UCB) id SAA44626;
	Tue, 28 Mar 2000 18:14:30 +0300 (EEST)
	(envelope-from ru)
Date: Tue, 28 Mar 2000 18:14:30 +0300
From: Ruslan Ermilov <ru@ucb.crimea.ua>
To: Mikhail Teterin <mi@kot.ne.mediaone.net>
Cc: stable@freebsd.org, Bruce Evans <bde@freebsd.org>
Subject: Re: top, systat )-: (all rebuilt!)
Message-ID: <20000328181430.A41307@relay.ucb.crimea.ua>
Mail-Followup-To: Mikhail Teterin <mi@kot.ne.mediaone.net>,
	stable@freebsd.org, Bruce Evans <bde@FreeBSD.org>
References: <20000328100840.B7725@relay.ucb.crimea.ua> <200003281453.JAA01102@rtfm.newton>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="tThc/1wpZn/ma/RB"
X-Mailer: Mutt 0.95.3i
In-Reply-To: <200003281453.JAA01102@rtfm.newton>; from Mikhail Teterin on Tue, Mar 28, 2000 at 09:53:20AM -0500
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


--tThc/1wpZn/ma/RB
Content-Type: text/plain; charset=us-ascii

On Tue, Mar 28, 2000 at 09:53:20AM -0500, Mikhail Teterin wrote:
> Ruslan Ermilov once stated:
>
> =Do you use loader(8), or directly boot your kernel from boot blocks?
>
> Directly... Is that what it is?!?
>
Yes, starting from the following files/revisions:

peter       1999/12/26 23:14:59 PST

  Modified files:
    lib/libkvm           kvm.c kvm_alpha.c kvm_file.c
                         kvm_getloadavg.c kvm_getswapinfo.c
                         kvm_i386.c kvm_nlist.3 kvm_private.h
                         kvm_proc.c kvm_sparc.c
  Log:
  Use kldsym(2) to lookup symbol values.  This avoids the kvm_mkdb juggling
  and is module aware.  Yes, this means that kvm_nlist(3) will find symbols
  in loaded modules.  The emulation of the nlist struct is pretty crude but
  seems to work well enough for all the users in the tree that I found.

  Revision  Changes    Path
  1.12      +22 -113   src/lib/libkvm/kvm.c
  1.4       +1 -2      src/lib/libkvm/kvm_alpha.c
  1.9       +5 -0      src/lib/libkvm/kvm_file.c
  1.3       +5 -1      src/lib/libkvm/kvm_getloadavg.c
  1.10      +1 -2      src/lib/libkvm/kvm_getswapinfo.c
  1.11      +5 -1      src/lib/libkvm/kvm_i386.c
  1.5       +7 -9      src/lib/libkvm/kvm_nlist.3
  1.5       +1 -1      src/lib/libkvm/kvm_private.h
  1.25      +7 -2      src/lib/libkvm/kvm_proc.c
  1.3       +5 -1      src/lib/libkvm/kvm_sparc.c


Could you please try the following two patches (kindly provided by
Bruce Evans), and tell us whether they help you.

There is a kern/17422 on this issue, please follow-up to it.



Cheers,
--
Ruslan Ermilov		Sysadmin and DBA of the
ru@ucb.crimea.ua	United Commercial Bank,
ru@FreeBSD.org		FreeBSD committer,
+380.652.247.647	Simferopol, Ukraine

http://www.FreeBSD.org	The Power To Serve
http://www.oracle.com	Enabling The Information Age

--tThc/1wpZn/ma/RB
Content-Type: message/rfc822

Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16])
	by relay.ucb.crimea.ua (8.9.3/8.9.3/UCB) with ESMTP id EAA76938
	for <ru@ucb.crimea.ua>; Tue, 14 Mar 2000 04:52:39 +0200 (EET)
	(envelope-from bde@zeta.org.au)
Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102])
	by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id NAA05065;
	Tue, 14 Mar 2000 13:58:35 +1100
Date: Tue, 14 Mar 2000 13:51:49 +1100 (EST)
From: Bruce Evans <bde@zeta.org.au>
X-Sender: bde@alphplex.bde.org
To: Ruslan Ermilov <ru@ucb.crimea.ua>
cc: Jordan Hubbard <jkh@FreeBSD.org>, committers@FreeBSD.org
Subject: Re: [4.0-ERRATA candidate?] loader(8)/kvm(3) interoperability issue
In-Reply-To: <20000313194345.A52651@relay.ucb.crimea.ua>
Message-ID: <Pine.BSF.4.21.0003141325520.2522-100000@alphplex.bde.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Mon, 13 Mar 2000, Ruslan Ermilov wrote:

> One thing that should IMHO be pointed out in the upcoming 4.0-RELEASE's
> ERRATA (or some more appropriate place), is the fact that the loader(8)
> is now a prerequisite for certain programs using kvm(3) interface.
> Obvious examples are top(1) and swapinfo(8).
> 
> If you boot your kernel without loader(8), directly through bootblocks,
> these programs will not work.

I don't user loader(8), and finally got around to fixing this.  The
problem is that the kernel linker wants module data for the kernel.
It defaults to using incomplete data if none is present.  The following
supplies slightly less incomplete data:

diff -c2 machdep.c~ machdep.c
*** machdep.c~	Tue Feb 29 19:18:29 2000
--- machdep.c	Mon Mar  6 10:05:52 2000
***************
*** 1809,1812 ****
--- 1799,1816 ----
  		preload_metadata = (caddr_t)bootinfo.bi_modulep + KERNBASE;
  		preload_bootstrap_relocate(KERNBASE);
+ 	} else {
+ 		static u_int32_t oldmoduledata[] = {
+ 			1, sizeof("kernel"), 0, 0,
+ 			2, sizeof("elf kernel"), 0, 0, 0,
+ 			0x8004, 4, 0,
+ 			0x8003, 4, 0,
+ 			0, 0,
+ 		};
+ 
+ 		preload_metadata = (caddr_t)&oldmoduledata[0];
+ 		strcpy((char *)&oldmoduledata[2], "kernel");
+ 		strcpy((char *)&oldmoduledata[6], "elf kernel");
+ 		oldmoduledata[11] = roundup2(bootinfo.bi_esymtab, 4);
+ 		oldmoduledata[14] = bootinfo.bi_symtab;
  	}
  	if (bootinfo.bi_envp)

Bruce


--tThc/1wpZn/ma/RB
Content-Type: message/rfc822

Received: from gidora.zeta.org.au (gidora.zeta.org.au [203.26.10.25])
	by relay.ucb.crimea.ua (8.9.3/8.9.3/UCB) with SMTP id QAA33103
	for <ru@ucb.crimea.ua>; Wed, 22 Mar 2000 16:34:11 +0200 (EET)
	(envelope-from bde@zeta.org.au)
Received: (qmail 25547 invoked from network); 22 Mar 2000 14:33:30 -0000
Received: from bde.zeta.org.au (203.2.228.102)
  by gidora.zeta.org.au with SMTP; 22 Mar 2000 14:33:30 -0000
Date: Thu, 23 Mar 2000 01:33:15 +1100 (EST)
From: Bruce Evans <bde@zeta.org.au>
X-Sender: bde@alphplex.bde.org
To: Ruslan Ermilov <ru@ucb.crimea.ua>
Subject: Re: [4.0-ERRATA candidate?] loader(8)/kvm(3) interoperability issue
In-Reply-To: <20000321213700.A64137@relay.ucb.crimea.ua>
Message-ID: <Pine.BSF.4.21.0003230126570.275-100000@alphplex.bde.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

> Hmm, the kernel with this patch panics with fatal trap 12 earlier,
> right after it reports the amount of available memory, if I boot
> without loader(8), but works perfectly, if I do use loader(8).

The symbol addresses in struct bootinfo were garbage when the symbol
table was loaded but DDB was not configured.

diff -c2 locore.s~ locore.s
*** locore.s~	Mon Dec  6 11:12:51 1999
--- locore.s	Thu Mar 23 01:11:57 2000
***************
*** 45,51 ****
  
  #include "opt_bootp.h"
- #include "opt_ddb.h"
  #include "opt_nfsroot.h"
- #include "opt_userconfig.h"
  
  #include <sys/syscall.h>
--- 45,49 ----
***************
*** 751,756 ****
  	movl	$R(_end),%esi
  
! /* include symbols if loaded and useful */
! #ifdef DDB
  	movl	R(_bootinfo+BI_ESYMTAB),%edi
  	testl	%edi,%edi
--- 749,753 ----
  	movl	$R(_end),%esi
  
! /* Include symbols, if any. */
  	movl	R(_bootinfo+BI_ESYMTAB),%edi
  	testl	%edi,%edi
***************
*** 761,765 ****
  	addl	%edi,R(_bootinfo+BI_ESYMTAB)
  over_symalloc:
- #endif
  
  /* If we are told where the end of the kernel space is, believe it. */
--- 758,761 ----

Bruce


--tThc/1wpZn/ma/RB--


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


From owner-freebsd-stable  Tue Mar 28  7:43:16 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from pooh.elsevier.nl (pooh.elsevier.nl [145.36.13.27])
	by hub.freebsd.org (Postfix) with ESMTP
	id D433F37BF35; Tue, 28 Mar 2000 07:43:11 -0800 (PST)
	(envelope-from steve@pooh.elsevier.nl)
Received: (from steve@localhost)
	by pooh.elsevier.nl (8.9.3/8.9.3) id QAA00220;
	Tue, 28 Mar 2000 16:48:00 +0100 (IST)
	(envelope-from steve)
Message-ID: <XFMail.000328164759.steveo@eircom.net>
X-Mailer: XFMail 1.4.0 on FreeBSD
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <20000328181430.A41307@relay.ucb.crimea.ua>
Date: Tue, 28 Mar 2000 16:47:59 +0100 (IST)
From: "Steve O'Hara-Smith" <steveo@eircom.net>
To: Ruslan Ermilov <ru@ucb.crimea.ua>
Subject: Re: top, systat )-: (all rebuilt!)
Cc: Bruce Evans <bde@freebsd.org>, stable@freebsd.org,
	Mikhail Teterin <mi@kot.ne.mediaone.net>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


On 28-Mar-00 Ruslan Ermilov wrote:
> Could you please try the following two patches (kindly provided by
> Bruce Evans), and tell us whether they help you.
> 
> There is a kern/17422 on this issue, please follow-up to it.

        Works for me.



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


From owner-freebsd-stable  Tue Mar 28  7:43:39 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from loki.ideaglobal.com (loki.ideaglobal.com [194.36.20.54])
	by hub.freebsd.org (Postfix) with ESMTP id 17C4D37BF38
	for <freebsd-stable@freebsd.org>; Tue, 28 Mar 2000 07:43:27 -0800 (PST)
	(envelope-from kiril@loki.ideaglobal.com)
Received: (from kiril@localhost)
	by loki.ideaglobal.com (8.9.3/8.9.3) id PAA69054
	for freebsd-stable@freebsd.org; Tue, 28 Mar 2000 15:49:01 GMT
	(envelope-from kiril)
From: Kiril Mitev <kiril@ideaglobal.com>
Message-Id: <200003281549.PAA69054@loki.ideaglobal.com>
Subject: q to Warner Losh wrt his PCI modem patch
To: freebsd-stable@freebsd.org
Date: Tue, 28 Mar 2000 15:49:01 +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

I found something on deja... posted by Warner Losh

==================================================
*IF* it isn't a win modem, soft modem, etc, then you can apply the following patch, rebuild your kernel and create /dev/cua4, et al in /dev.

If it is a win modem, you lose.  Sell it to some sucker and buy a real pci modem.

Patch: http://www.freebsd.org/~imp/Psio

Warner
==================================================

Can anyone PLEASE confirm/deny whether that patch is safe to use
with fbsd-4 ?


TIA


-- 
Kiril Mitev, IT Operations Mgr, London
IDEAglobal.com
Standard Corporate Disclaimer applies, see
http://www.ideaglobal.com/email-disclaimer.html
for details.


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


From owner-freebsd-stable  Tue Mar 28  7:49:43 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from axl.ops.uunet.co.za (axl.ops.uunet.co.za [196.31.1.175])
	by hub.freebsd.org (Postfix) with ESMTP id 1BB4837BD5C
	for <freebsd-stable@freebsd.org>; Tue, 28 Mar 2000 07:49:35 -0800 (PST)
	(envelope-from sheldonh@axl.ops.uunet.co.za)
Received: from sheldonh (helo=axl.ops.uunet.co.za)
	by axl.ops.uunet.co.za with local-esmtp (Exim 3.13 #1)
	id 12ZyEx-000AqH-00; Tue, 28 Mar 2000 17:49:11 +0200
From: Sheldon Hearn <sheldonh@uunet.co.za>
To: Martin Cracauer <cracauer@cons.org>
Cc: freebsd-stable@FreeBSD.ORG
Subject: Re: Let 3.x die ASAP? 
In-reply-to: Your message of "Tue, 28 Mar 2000 11:36:34 +0200."
             <20000328113633.A28085@cons.org> 
Date: Tue, 28 Mar 2000 17:49:11 +0200
Message-ID: <41680.954258551@axl.ops.uunet.co.za>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG



On Tue, 28 Mar 2000 11:36:34 +0200, Martin Cracauer wrote:

> I am so impressed with the results of upgrading my more important
> machines to 4.0 or 4-stable that I could imagine not to produce any
> more 3.x releases.

I must admit, during the 3.4-RELEASE code slush, I somehow got the
impression that 3.4-RELEASE would be the last release on the RELENG_3
branch.  I was happy with that and I hope it remains true.

The only reasonable argument that I can think of for a 3.5-RELEASE is to
have a kind of "closure" release for people who _must_ stick with the
RELENG_3 branch because they've been advised to by project staff.  Lots
of people are in this position; I've read "then stick with RELENG_3" in
response to quite a range of "but I have old hardware" complaints.

The "closure" release that I envision is one in which there aren't any
more serious bugs that can be fixed without merging back significant
portions of the RELENG_4 branch.  It would basically be the RELENG_3
branch "polished off". :-)

Having said that, I don't like the idea one little bit, for exactly the
reasons you listed in your original message.

Ciao,
Sheldon.


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


From owner-freebsd-stable  Tue Mar 28  7:52: 3 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from isabase.philol.msu.ru (isabase.philol.msu.ru [195.208.217.73])
	by hub.freebsd.org (Postfix) with ESMTP id 529AB37C075
	for <freebsd-stable@freebsd.org>; Tue, 28 Mar 2000 07:51:54 -0800 (PST)
	(envelope-from grg@isabase.philol.msu.ru)
Received: (from grg@localhost)
	by isabase.philol.msu.ru (8.9.3/8.9.2) id TAA30956
	for freebsd-stable@freebsd.org; Tue, 28 Mar 2000 19:50:30 +0400 (MSD)
	(envelope-from grg)
Date: Tue, 28 Mar 2000 19:50:30 +0400
From: Grigoriy Strokin <grg@philol.msu.ru>
To: freebsd-stable@freebsd.org
Subject: New kernel with its ATA drivers damages the filesystem
Message-ID: <20000328195030.A30092@isabase.philol.msu.ru>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0i
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hello,

Three days ago I've performed my first upgrade to FreeBSD 4.0-STABLE from
3.4 on one machine, via CVSUP. Observing the lack of any problems for 3
days (except audio record) I decided to install it to another box, from the
same sources.

Well, buildworld etc., then buildkernel (GENERIC), installkernel,
reboot.

During the boot, I've seen:

Mar 28 17:48:56 koch2 /kernel: ata0: at 0x1f0 irq 14 on atapci0
...
Mar 28 17:49:07 koch2 /kernel: ed0: <Longshine LCS-8634P Ethernet Card
Mar 28 17:49:07 koch2 /kernel: > at port 0x240-0x25f iomem 0xc0000-0xc003f irq 11 on isa0
Mar 28 17:49:07 koch2 /kernel: ed0: supplying EUI64: 08:00:00:ff:fe:00:10:37
Mar 28 17:49:07 koch2 /kernel: ed0: address 08:00:00:00:10:37, type NE2000 (16 bit)
...
Mar 28 17:49:07 koch2 /kernel: ad0: 8063MB <FUJITSU MPD3084AT> [16383/16/63] at ata0-master using UDMA33
Mar 28 17:49:07 koch2 /kernel: acd0: CDROM <TOSHIBA CD-ROM XM-6402B> at ata0-slave using PIO4
...
Mar 28 17:49:07 koch2 /kernel: ed0: device timeout
Mar 28 17:49:07 koch2 /kernel: ed0: device timeout
Mar 28 17:49:07 koch2 /kernel: ata0: resetting devices .. done
Mar 28 17:49:48 koch2 /kernel: ad0: WRITE command timeout - resetting
Mar 28 17:49:48 koch2 /kernel: ata0: resetting devices .. done

The booting process continued. Then I shut down the machine
and turned it off and on again, just in case there were
real problem with HDD.

Second boot:

fsck says about /usr "UNEXPECTED INCONSISTENCY, RUN FSCK MANUALLY".

After running fsck -y several times quite a few files
have been either deleted or moved to lost+found.
/usr/local and my home directory disappeared.

Then I rebooted again in order to turn 'UDMA' off in BIOS.

And again I've seen 'ad0: WRITE command timeout - resetting'
messages, and again /usr became damaged, which resulted
in loss of many other files and directories.

Moreover, despite that fact that ed0 was detected,
"ifconfig ed0" gave "interface does not exist"
(also, note the 'ed0 device timeout' messages above)

Now I think I don't know where to find the source of the problem.


-- 
=== Grigoriy Strokin, Lomonosov University (MGU), Moscow ===
=== contact info: http://isabase.philol.msu.ru/~grg/     ===


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


From owner-freebsd-stable  Tue Mar 28  7:53:25 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from kot.ne.mediaone.net (kot.ne.mediaone.net [24.218.15.190])
	by hub.freebsd.org (Postfix) with ESMTP id A431F37BDE6
	for <stable@FreeBSD.ORG>; Tue, 28 Mar 2000 07:53:14 -0800 (PST)
	(envelope-from mi@kot.ne.mediaone.net)
Received: from rtfm.newton (root@rtfm.newton [10.10.0.1])
	by kot.ne.mediaone.net (8.9.3/8.9.1) with ESMTP id KAA69503;
	Tue, 28 Mar 2000 10:53:13 -0500 (EST)
From: Mikhail Teterin <mi@kot.ne.mediaone.net>
X-Relay-IP: 10.10.0.1
Received: (from mi@localhost)
	by rtfm.newton (8.9.3/8.9.3) id KAA01633;
	Tue, 28 Mar 2000 10:53:12 -0500 (EST)
	(envelope-from mi@kot.ne.mediaone.net)
Message-Id: <200003281553.KAA01633@rtfm.newton>
Subject: Re: panic on a flaky SCSI CD
In-Reply-To: <20000327233150.A2097@panzer.kdm.org> from "Kenneth D. Merry" at
 "Mar 27, 2000 11:31:51 pm"
To: "Kenneth D. Merry" <ken@kdm.org>
Date: Tue, 28 Mar 2000 10:53:12 -0500 (EST)
Cc: stable@FreeBSD.ORG
X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w<gv/&E-lL7twZCT8B~/PA4|\t$ti+22K">
	 hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli"<kcG^EOVih
	 y+z3/UR{6SCQ
X-Mailer: ELM [version 2.4ME+ PL60 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Kenneth D. Merry once stated:

=> I have this flaky SCSI CD, which  works sometimes :) When it fails, I
=> see something like the following popping up:
=> 
=> Creating DISK cd0
=> (cd0:ncr1:0:6:0): got CAM status 0x4a
=> (cd0:ncr1:0:6:0): fatal error, failed to attach to device
=> (cd0:ncr1:0:6:0): lost device
=> (cd0:ncr1:0:6:0): removing device entry
=
=That is caused by  a selection timeout. There's not a  whole lot we can
=do about that.

I think  I found  it. I increased  the SCSI_DELAY to  9 seconds  and the
drive seems happier  now. I also switched  to the new sym  driver for my
NCR-53C875. But this was not my question :) This was:

=> Under 3.4, if I  was to try to mount a CD in  this drive, when it was
=> in the  bad mood, I'd  simply get an error.  Now, with 4.0  the thing
=> panics :(
=
=That's not good.  In order to find the problem, we'll need a little more
=information.  Take a look at the handbook section on kernel debugging:
=
=http://www.freebsd.org/handbook/kerneldebug.html

I'd love  to do  this, but it  I don't  have the time  right now.  I was
hoping,  someone who  knows the  code in  question will  be able  to fix
things quickly.  It bites  me when I  attempt to use  a device  that was
created, but then removed...

	-mi


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


From owner-freebsd-stable  Tue Mar 28  8:16: 8 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from jason05.u.washington.edu (jason05.u.washington.edu [140.142.78.6])
	by hub.freebsd.org (Postfix) with ESMTP id B9B8C37BFCC
	for <freebsd-stable@FreeBSD.ORG>; Tue, 28 Mar 2000 08:15:59 -0800 (PST)
	(envelope-from kraemer@u.washington.edu)
Received: from mead1.u.washington.edu (kraemer@mead1.u.washington.edu [140.142.12.133])
	by jason05.u.washington.edu (8.9.3+UW99.09/8.9.3+UW00.01) with ESMTP id IAA15410;
	Tue, 28 Mar 2000 08:15:52 -0800
Received: from localhost (kraemer@localhost)
	by mead1.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id IAA134532;
	Tue, 28 Mar 2000 08:15:51 -0800
Date: Tue, 28 Mar 2000 08:15:51 -0800 (PST)
From: Brian Kraemer <kraemer@u.washington.edu>
To: David Gilbert <dgilbert@velocet.ca>
Cc: freebsd-stable@FreeBSD.ORG
Subject: Re: 4.0-STABLE dhcp conflicts. 
In-Reply-To: <200003280440.UAA07738@cwsys.cwsent.com>
Message-ID: <Pine.A41.4.21.0003280814300.49840-100000@mead1.u.washington.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

in message <14559.40450.544687.51037@trooper.velocet.net>, David Gilbert writes:

> It appears that when I run two (not sure if one does it) tcpdumps on
> the dhcp server, the dhcp clients don't get any responses to their
> queries.  Is there some flaw in the dhcpd bpf rules?

Do you have enough bpf devices enabled? I imagine each tcpdump will use
one, and dhcpd also uses one if I am not mistaken.

-Brian



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


From owner-freebsd-stable  Tue Mar 28  8:17:18 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from vitaly.vangyzen.net (vitaly.vangyzen.net [205.245.185.194])
	by hub.freebsd.org (Postfix) with ESMTP id 005A737BF38
	for <freebsd-stable@FreeBSD.ORG>; Tue, 28 Mar 2000 08:17:10 -0800 (PST)
	(envelope-from lists@vitaly.vangyzen.net)
Received: (from lists@localhost)
	by vitaly.vangyzen.net (8.9.3/8.9.3) id LAA23401;
	Tue, 28 Mar 2000 11:15:08 -0500 (EST)
Date: Tue, 28 Mar 2000 11:15:08 -0500
From: "Eric S . Van Gyzen" <lists@vangyzen.net>
To: John Reynolds~ <jreynold@sedona.ch.intel.com>
Cc: Grigoriy Strokin <grg@philol.msu.ru>, freebsd-stable@FreeBSD.ORG
Subject: Re: can I mount a Linux ext2fs from an extended partition ?
Message-ID: <20000328111508.A19646@vitaly.vangyzen.net>
References: <20000327233341.A98997@titan.klemm.gtn.com> <14559.55202.523180.943476@hip186.ch.intel.com> <20000328034011.A21720@isabase.philol.msu.ru> <14559.63574.826460.351449@hip186.ch.intel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0.1i
In-Reply-To: <14559.63574.826460.351449@hip186.ch.intel.com>; from jreynold@sedona.ch.intel.com on Mon, Mar 27, 2000 at 05:09:58PM -0700
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> > >  mount -t ex2fs /dev/whatever /mnt
> > 
> > Oh, could you please eloborate on this? Namely, which 'whatever'
> > should one specify for the first 'logical' partition
> > of the extended partition on wd0, primary master hard drive?
> > 
> 
>   /dev/ad0s5
> 
> give it a whirl. Can anybody else verify or disprove the above (I'm just
> guessing and trying to remember from broken memory :).

You're correct.  Slices 1-4 are the four primary partitions, and 5-n are
the logical ones.

Eric


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


From owner-freebsd-stable  Tue Mar 28  8:22:58 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from sabre.velocet.net (sabre.velocet.net [198.96.118.66])
	by hub.freebsd.org (Postfix) with ESMTP id AE0F037BEE5
	for <freebsd-stable@FreeBSD.ORG>; Tue, 28 Mar 2000 08:22:47 -0800 (PST)
	(envelope-from dgilbert@office.tor.velocet.net)
Received: from office.tor.velocet.net (trooper.velocet.net [216.126.82.226])
	by sabre.velocet.net (Postfix) with ESMTP
	id B3306137FFB; Tue, 28 Mar 2000 11:21:20 -0500 (EST)
Received: (from dgilbert@localhost)
	by office.tor.velocet.net (8.9.3/8.9.3) id LAA08207;
	Tue, 28 Mar 2000 11:21:20 -0500 (EST)
	(envelope-from dgilbert)
From: David Gilbert <dgilbert@velocet.ca>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <14560.56319.827242.610802@trooper.velocet.net>
Date: Tue, 28 Mar 2000 11:21:19 -0500 (EST)
To: Brian Kraemer <kraemer@u.washington.edu>
Cc: David Gilbert <dgilbert@velocet.ca>, freebsd-stable@FreeBSD.ORG
Subject: Re: 4.0-STABLE dhcp conflicts. 
In-Reply-To: <Pine.A41.4.21.0003280814300.49840-100000@mead1.u.washington.edu>
References: <200003280440.UAA07738@cwsys.cwsent.com>
	<Pine.A41.4.21.0003280814300.49840-100000@mead1.u.washington.edu>
X-Mailer: VM 6.75 under 20.4 "Emerald" XEmacs  Lucid
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

>>>>> "Brian" == Brian Kraemer <kraemer@u.washington.edu> writes:

Brian> in message <14559.40450.544687.51037@trooper.velocet.net>,
Brian> David Gilbert writes:
>> It appears that when I run two (not sure if one does it) tcpdumps
>> on the dhcp server, the dhcp clients don't get any responses to
>> their queries.  Is there some flaw in the dhcpd bpf rules?

Brian> Do you have enough bpf devices enabled? I imagine each tcpdump
Brian> will use one, and dhcpd also uses one if I am not mistaken.

Well... one not-so-nice "feature" of the dhcpd or bpf interface (don't 
know which) is that it requires one bpf per interface.

Dave.

-- 
============================================================================
|David Gilbert, Velocet Communications.       | Two things can only be     |
|Mail:       dgilbert@velocet.net             |  equal if and only if they |
|http://www.velocet.net/~dgilbert             |   are precisely opposite.  |
=========================================================GLO================


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


From owner-freebsd-stable  Tue Mar 28  8:26:54 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from kot.ne.mediaone.net (kot.ne.mediaone.net [24.218.15.190])
	by hub.freebsd.org (Postfix) with ESMTP id 93B9837BDE6
	for <stable@freebsd.org>; Tue, 28 Mar 2000 08:26:45 -0800 (PST)
	(envelope-from mi@kot.ne.mediaone.net)
Received: from rtfm.newton (root@rtfm.newton [10.10.0.1])
	by kot.ne.mediaone.net (8.9.3/8.9.1) with ESMTP id LAA69580
	for <stable@freebsd.org>; Tue, 28 Mar 2000 11:26:42 -0500 (EST)
From: Mikhail Teterin <mi@kot.ne.mediaone.net>
X-Relay-IP: 10.10.0.1
Received: (from mi@localhost)
	by rtfm.newton (8.9.3/8.9.3) id LAA11876
	for stable@freebsd.org; Tue, 28 Mar 2000 11:26:42 -0500 (EST)
	(envelope-from mi@kot.ne.mediaone.net)
Message-Id: <200003281626.LAA11876@rtfm.newton>
Subject: CFLAGS ingored for a few C files
To: stable@freebsd.org
Date: Tue, 28 Mar 2000 11:26:42 -0500 (EST)
X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w<gv/&E-lL7twZCT8B~/PA4|\t$ti+22K">
	 hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli"<kcG^EOVih
	 y+z3/UR{6SCQ
X-Mailer: ELM [version 2.4ME+ PL60 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Here is a  list of 37 cc  invocations from builworld log,  which did not
have my CFLAGS set (I build everything with -mcpu=686, -march=i686). I'm
not sure if that number should be  0, but I'm certain that some of those
files could be compiled with optimization:

cc -S tmp-dum.c
cc -S tmp-dum.c
cc -c        -DVERSION=\"1.03\"  -DXS_VERSION=\"1.03\" -DPIC -fpic -I/usr/obj/4G/src/gnu/usr.bin/perl/perl -I/usr/obj/4G/src/i386/usr/include DynaLoader.c
cc -c        -DVERSION=\"a5\"  -DXS_VERSION=\"a5\" -DPIC -fpic -I/usr/obj/4G/src/gnu/usr.bin/perl/perl -I/usr/obj/4G/src/i386/usr/include B.c
cc -c        -DVERSION=\"1.65\"  -DXS_VERSION=\"1.65\" -DPIC -fpic -I/usr/obj/4G/src/gnu/usr.bin/perl/perl -I/usr/obj/4G/src/i386/usr/include DB_File.c
cc -c        -DVERSION=\"2.101\"  -DXS_VERSION=\"2.101\" -DPIC -fpic -I/usr/obj/4G/src/gnu/usr.bin/perl/perl -I/usr/obj/4G/src/i386/usr/include Dumper.c
cc -c        -DVERSION=\"1.03\"  -DXS_VERSION=\"1.03\" -DPIC -fpic -I/usr/obj/4G/src/gnu/usr.bin/perl/perl -I/usr/obj/4G/src/i386/usr/include Fcntl.c
cc -c        -DVERSION=\"1.1505\"  -DXS_VERSION=\"1.15\" -DPIC -fpic -I/usr/obj/4G/src/gnu/usr.bin/perl/perl -I/usr/obj/4G/src/i386/usr/include IO.c
cc -c        -DVERSION=\"1.03\"  -DXS_VERSION=\"1.03\" -DPIC -fpic -I/usr/obj/4G/src/gnu/usr.bin/perl/perl -I/usr/obj/4G/src/i386/usr/include SysV.c
cc -c        -DVERSION=\"1.01\"  -DXS_VERSION=\"1.01\" -DPIC -fpic -I/usr/obj/4G/src/gnu/usr.bin/perl/perl -I/usr/obj/4G/src/i386/usr/include NDBM_File.c
cc -c        -DVERSION=\"1.04\"  -DXS_VERSION=\"1.03\" -DPIC -fpic -I/usr/obj/4G/src/gnu/usr.bin/perl/perl -I/usr/obj/4G/src/i386/usr/include Opcode.c
cc -c  -DSTRUCT_TM_HASZONE      -DVERSION=\"1.02\"  -DXS_VERSION=\"1.02\" -DPIC -fpic -I/usr/obj/4G/src/gnu/usr.bin/perl/perl -I/usr/obj/4G/src/i386/usr/include POSIX.c
cc -c -I/usr/obj/4G/src/gnu/usr.bin/perl/perl       -DVERSION=\"0.10\"  -DXS_VERSION=\"0.10\" -DPIC -fpic -I/usr/obj/4G/src/gnu/usr.bin/perl/perl -DSDBM -DDUFF sdbm.c
cc -c -I/usr/obj/4G/src/gnu/usr.bin/perl/perl       -DVERSION=\"0.10\"  -DXS_VERSION=\"0.10\" -DPIC -fpic -I/usr/obj/4G/src/gnu/usr.bin/perl/perl -DSDBM -DDUFF pair.c
cc -c -I/usr/obj/4G/src/gnu/usr.bin/perl/perl       -DVERSION=\"0.10\"  -DXS_VERSION=\"0.10\" -DPIC -fpic -I/usr/obj/4G/src/gnu/usr.bin/perl/perl -DSDBM -DDUFF hash.c
cc -c        -DVERSION=\"1.00\"  -DXS_VERSION=\"1.00\" -DPIC -fpic -I/usr/obj/4G/src/gnu/usr.bin/perl/perl -I/usr/obj/4G/src/i386/usr/include SDBM_File.c
cc -c        -DVERSION=\"1.7\"  -DXS_VERSION=\"1.7\" -DPIC -fpic -I/usr/obj/4G/src/gnu/usr.bin/perl/perl -I/usr/obj/4G/src/i386/usr/include Socket.c
cc -c        -DVERSION=\"1.0\"  -DXS_VERSION=\"1.0\" -DPIC -fpic -I/usr/obj/4G/src/gnu/usr.bin/perl/perl -I/usr/obj/4G/src/i386/usr/include attrs.c
cc -c        -DVERSION=\"0.02\"  -DXS_VERSION=\"0.02\" -DPIC -fpic -I/usr/obj/4G/src/gnu/usr.bin/perl/perl -I/usr/obj/4G/src/i386/usr/include re_exec.c
cc -c        -DVERSION=\"0.02\"  -DXS_VERSION=\"0.02\" -DPIC -fpic -I/usr/obj/4G/src/gnu/usr.bin/perl/perl -I/usr/obj/4G/src/i386/usr/include re_comp.c
cc -c        -DVERSION=\"0.02\"  -DXS_VERSION=\"0.02\" -DPIC -fpic -I/usr/obj/4G/src/gnu/usr.bin/perl/perl -I/usr/obj/4G/src/i386/usr/include re.c
cc -c        -DVERSION=\"1.03\"  -DXS_VERSION=\"1.03\" -DPIC -fpic -I/usr/obj/4G/src/gnu/usr.bin/perl/suidperl -I/usr/obj/4G/src/i386/usr/include DynaLoader.c
cc -fno-builtin -Os -DKZIP   -I/usr/obj/4G/src/i386/usr/include -c /4G/src/sys/boot/i386/kgzldr/boot.c
cc -fno-builtin -Os -DKZIP   -I/usr/obj/4G/src/i386/usr/include -c /4G/src/sys/boot/i386/kgzldr/../../../kern/inflate.c
cc -fno-builtin -Os -DKZIP   -I/usr/obj/4G/src/i386/usr/include -c /4G/src/sys/boot/i386/kgzldr/lib.c
cc -elf -I/4G/src/sys/boot/i386/boot2/../btx/lib -I.  -Os -fno-builtin -fforce-addr -fdata-sections  -malign-functions=0 -malign-jumps=0 -malign-loops=0 -mrtd  -mpreferred-stack-boundary=2  -Wall -Waggregate-return -Wbad-function-cast -Wcast-align  -Wmissing-declarations -Wmissing-prototypes -Wnested-externs  -Wpointer-arith -Wshadow -Wstrict-prototypes -Wwrite-strings   -I/usr/obj/4G/src/i386/usr/include -c /4G/src/sys/boot/i386/boot2/boot2.c
cc -c vers.c
cc -DREAL_DAEMON_DIR=\"/usr/libexec\"  -DSEVERITY=LOG_INFO -DRFC931_TIMEOUT=10  -DHOSTS_DENY=\"/etc/hosts.deny\" -DHOSTS_ALLOW=\"/etc/hosts.allow\" -DINET6 -DUSE_GETIPNODEBY   -I/usr/obj/4G/src/i386/usr/include -c /4G/src/usr.sbin/tcpdchk/../../contrib/tcp_wrappers/tcpdchk.c
cc -DREAL_DAEMON_DIR=\"/usr/libexec\"  -DSEVERITY=LOG_INFO -DRFC931_TIMEOUT=10  -DHOSTS_DENY=\"/etc/hosts.deny\" -DHOSTS_ALLOW=\"/etc/hosts.allow\" -DINET6 -DUSE_GETIPNODEBY   -I/usr/obj/4G/src/i386/usr/include -c /4G/src/usr.sbin/tcpdchk/../../contrib/tcp_wrappers/fakelog.c
cc -DREAL_DAEMON_DIR=\"/usr/libexec\"  -DSEVERITY=LOG_INFO -DRFC931_TIMEOUT=10  -DHOSTS_DENY=\"/etc/hosts.deny\" -DHOSTS_ALLOW=\"/etc/hosts.allow\" -DINET6 -DUSE_GETIPNODEBY   -I/usr/obj/4G/src/i386/usr/include -c /4G/src/usr.sbin/tcpdchk/../../contrib/tcp_wrappers/inetcf.c
cc -DREAL_DAEMON_DIR=\"/usr/libexec\"  -DSEVERITY=LOG_INFO -DRFC931_TIMEOUT=10  -DHOSTS_DENY=\"/etc/hosts.deny\" -DHOSTS_ALLOW=\"/etc/hosts.allow\" -DINET6 -DUSE_GETIPNODEBY   -I/usr/obj/4G/src/i386/usr/include -c /4G/src/usr.sbin/tcpdchk/../../contrib/tcp_wrappers/scaffold.c
cc -DREAL_DAEMON_DIR=\"/usr/libexec\"  -DSEVERITY=LOG_INFO -DRFC931_TIMEOUT=10   -I/usr/obj/4G/src/i386/usr/include -c /4G/src/usr.sbin/tcpdmatch/../../contrib/tcp_wrappers/tcpdmatch.c
cc -DREAL_DAEMON_DIR=\"/usr/libexec\"  -DSEVERITY=LOG_INFO -DRFC931_TIMEOUT=10   -I/usr/obj/4G/src/i386/usr/include -c /4G/src/usr.sbin/tcpdmatch/../../contrib/tcp_wrappers/fakelog.c
cc -DREAL_DAEMON_DIR=\"/usr/libexec\"  -DSEVERITY=LOG_INFO -DRFC931_TIMEOUT=10   -I/usr/obj/4G/src/i386/usr/include -c /4G/src/usr.sbin/tcpdmatch/../../contrib/tcp_wrappers/inetcf.c
cc -DREAL_DAEMON_DIR=\"/usr/libexec\"  -DSEVERITY=LOG_INFO -DRFC931_TIMEOUT=10   -I/usr/obj/4G/src/i386/usr/include -c /4G/src/usr.sbin/tcpdmatch/../../contrib/tcp_wrappers/scaffold.c
cc -O2 -I/usr/obj/4G/src/usr.sbin/pcvt/vgaio -I/4G/src/usr.sbin/pcvt/vgaio   -I/usr/obj/4G/src/i386/usr/include -c vgaio.c
cc -O2 -I/usr/obj/4G/src/usr.sbin/pcvt/vgaio -I/4G/src/usr.sbin/pcvt/vgaio   -I/usr/obj/4G/src/i386/usr/include -c lex.c

	-mi


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


From owner-freebsd-stable  Tue Mar 28  8:39:17 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from vitaly.vangyzen.net (vitaly.vangyzen.net [205.245.185.194])
	by hub.freebsd.org (Postfix) with ESMTP id 315A737BF9A
	for <freebsd-stable@freebsd.org>; Tue, 28 Mar 2000 08:39:08 -0800 (PST)
	(envelope-from lists@vitaly.vangyzen.net)
Received: (from lists@localhost)
	by vitaly.vangyzen.net (8.9.3/8.9.3) id LAA19483
	for freebsd-stable@freebsd.org; Tue, 28 Mar 2000 11:38:21 -0500 (EST)
Date: Tue, 28 Mar 2000 11:38:20 -0500
From: "Eric S . Van Gyzen" <lists@vangyzen.net>
To: freebsd-stable@freebsd.org
Subject: R/W mount of ext2fs fails
Message-ID: <20000328113820.A15302@vitaly.vangyzen.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0.1i
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

I just upgraded from 3.4-STABLE to 4.0-STABLE and am having problems mounting
my Linux partition.  The Linux root filesystem is on /dev/da0s3.  Here's what
happens:

	# mount -t ext2fs /dev/da0s3 /mnt/linux
	ext2fs: /dev/da0s3: Invalid argument
	# ls -l /dev/da0s3
	crw-r-----  1 root  operator   13, 0x00040002 Mar 28 11:35 /dev/da0s3

Syslog reports:
	/kernel: WARNING: R/W mount of #da/0x40002 denied due to
	unsupported optional features

Huh?  To what "unsupported optional features" is it referring?  In case it
matters, the Linux installation is Red Hat 6.1.  And I do have
	options         EXT2FS
in my kernel config.  I thought maybe the filesystem wasn't clean, so I booted
Linux and fsck'ed, only to get the same results.

Thanks for any help, or pointers to documentation that I should have read...

-Eric

FreeBSD 4.0-STABLE #0: Thu Mar 23 15:16:02 EST 2000


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


From owner-freebsd-stable  Tue Mar 28  8:46: 6 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from kot.ne.mediaone.net (kot.ne.mediaone.net [24.218.15.190])
	by hub.freebsd.org (Postfix) with ESMTP id 9214C37C0B8
	for <stable@freebsd.org>; Tue, 28 Mar 2000 08:45:55 -0800 (PST)
	(envelope-from mi@kot.ne.mediaone.net)
Received: from rtfm.newton (root@rtfm.newton [10.10.0.1])
	by kot.ne.mediaone.net (8.9.3/8.9.1) with ESMTP id LAA69627
	for <stable@freebsd.org>; Tue, 28 Mar 2000 11:45:49 -0500 (EST)
From: Mikhail Teterin <mi@kot.ne.mediaone.net>
X-Relay-IP: 10.10.0.1
Received: (from mi@localhost)
	by rtfm.newton (8.9.3/8.9.3) id LAA00313
	for stable@freebsd.org; Tue, 28 Mar 2000 11:45:47 -0500 (EST)
	(envelope-from mi@kot.ne.mediaone.net)
Message-Id: <200003281645.LAA00313@rtfm.newton>
Subject: Re: top, systat )-: (all rebuilt!)
In-Reply-To: <20000328181430.A41307@relay.ucb.crimea.ua> from Ruslan Ermilov
 at "Mar 28, 2000 06:14:30 pm"
To: stable@freebsd.org
Date: Tue, 28 Mar 2000 11:45:47 -0500 (EST)
X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w<gv/&E-lL7twZCT8B~/PA4|\t$ti+22K">
	 hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli"<kcG^EOVih
	 y+z3/UR{6SCQ
X-Mailer: ELM [version 2.4ME+ PL60 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

The patches did the trick for me...

	-mi

=On Tue, Mar 28, 2000 at 09:53:20AM -0500, Mikhail Teterin wrote:
=> Ruslan Ermilov once stated:
=>
=> =Do you use loader(8), or directly boot your kernel from boot blocks?
=>
=> Directly... Is that what it is?!?
=>
=Yes, starting from the following files/revisions:
=
=peter       1999/12/26 23:14:59 PST
=
=  Modified files:
=    lib/libkvm           kvm.c kvm_alpha.c kvm_file.c
=                         kvm_getloadavg.c kvm_getswapinfo.c
=                         kvm_i386.c kvm_nlist.3 kvm_private.h
=                         kvm_proc.c kvm_sparc.c
=  Log:
=  Use kldsym(2) to lookup symbol values.  This avoids the kvm_mkdb juggling
=  and is module aware.  Yes, this means that kvm_nlist(3) will find symbols
=  in loaded modules.  The emulation of the nlist struct is pretty crude but
=  seems to work well enough for all the users in the tree that I found.
=
=  Revision  Changes    Path
=  1.12      +22 -113   src/lib/libkvm/kvm.c
=  1.4       +1 -2      src/lib/libkvm/kvm_alpha.c
=  1.9       +5 -0      src/lib/libkvm/kvm_file.c
=  1.3       +5 -1      src/lib/libkvm/kvm_getloadavg.c
=  1.10      +1 -2      src/lib/libkvm/kvm_getswapinfo.c
=  1.11      +5 -1      src/lib/libkvm/kvm_i386.c
=  1.5       +7 -9      src/lib/libkvm/kvm_nlist.3
=  1.5       +1 -1      src/lib/libkvm/kvm_private.h
=  1.25      +7 -2      src/lib/libkvm/kvm_proc.c
=  1.3       +5 -1      src/lib/libkvm/kvm_sparc.c
=
=
=Could you please try the following two patches (kindly provided by
=Bruce Evans), and tell us whether they help you.
=
=There is a kern/17422 on this issue, please follow-up to it.
=
=
=
=Cheers,
=--
=Ruslan Ermilov		Sysadmin and DBA of the
=ru@ucb.crimea.ua	United Commercial Bank,
=ru@FreeBSD.org		FreeBSD committer,
=+380.652.247.647	Simferopol, Ukraine
=
=http://www.FreeBSD.org	The Power To Serve
=http://www.oracle.com	Enabling The Information Age

-- Start of included mail From:  Bruce Evans <bde@zeta.org.au>

=Date:  Tue, 14 Mar 2000 13:51:49 +1100 (EST)
=X-Sender:  bde@alphplex.bde.org
=To:  Ruslan Ermilov <ru@ucb.crimea.ua>
=cc:  Jordan Hubbard <jkh@FreeBSD.org>, committers@FreeBSD.org
=Subject:  Re: [4.0-ERRATA candidate?] loader(8)/kvm(3) interoperability issue

=On Mon, 13 Mar 2000, Ruslan Ermilov wrote:
=
=> One thing that should IMHO be pointed out in the upcoming 4.0-RELEASE's
=> ERRATA (or some more appropriate place), is the fact that the loader(8)
=> is now a prerequisite for certain programs using kvm(3) interface.
=> Obvious examples are top(1) and swapinfo(8).
=> 
=> If you boot your kernel without loader(8), directly through bootblocks,
=> these programs will not work.
=
=I don't user loader(8), and finally got around to fixing this.  The
=problem is that the kernel linker wants module data for the kernel.
=It defaults to using incomplete data if none is present.  The following
=supplies slightly less incomplete data:
=
=diff -c2 machdep.c~ machdep.c
=*** machdep.c~	Tue Feb 29 19:18:29 2000
=--- machdep.c	Mon Mar  6 10:05:52 2000
=***************
=*** 1809,1812 ****
=--- 1799,1816 ----
=  		preload_metadata = (caddr_t)bootinfo.bi_modulep + KERNBASE;
=  		preload_bootstrap_relocate(KERNBASE);
=+ 	} else {
=+ 		static u_int32_t oldmoduledata[] = {
=+ 			1, sizeof("kernel"), 0, 0,
=+ 			2, sizeof("elf kernel"), 0, 0, 0,
=+ 			0x8004, 4, 0,
=+ 			0x8003, 4, 0,
=+ 			0, 0,
=+ 		};
=+ 
=+ 		preload_metadata = (caddr_t)&oldmoduledata[0];
=+ 		strcpy((char *)&oldmoduledata[2], "kernel");
=+ 		strcpy((char *)&oldmoduledata[6], "elf kernel");
=+ 		oldmoduledata[11] = roundup2(bootinfo.bi_esymtab, 4);
=+ 		oldmoduledata[14] = bootinfo.bi_symtab;
=  	}
=  	if (bootinfo.bi_envp)
=
=Bruce
=
-- End of included mail.

-- Start of included mail From:  Bruce Evans <bde@zeta.org.au>

=Date:  Thu, 23 Mar 2000 01:33:15 +1100 (EST)
=X-Sender:  bde@alphplex.bde.org
=To:  Ruslan Ermilov <ru@ucb.crimea.ua>
=Subject:  Re: [4.0-ERRATA candidate?] loader(8)/kvm(3) interoperability issue

=> Hmm, the kernel with this patch panics with fatal trap 12 earlier,
=> right after it reports the amount of available memory, if I boot
=> without loader(8), but works perfectly, if I do use loader(8).
=
=The symbol addresses in struct bootinfo were garbage when the symbol
=table was loaded but DDB was not configured.
=
=diff -c2 locore.s~ locore.s
=*** locore.s~	Mon Dec  6 11:12:51 1999
=--- locore.s	Thu Mar 23 01:11:57 2000
=***************
=*** 45,51 ****
=  
=  #include "opt_bootp.h"
=- #include "opt_ddb.h"
=  #include "opt_nfsroot.h"
=- #include "opt_userconfig.h"
=  
=  #include <sys/syscall.h>
=--- 45,49 ----
=***************
=*** 751,756 ****
=  	movl	$R(_end),%esi
=  
=! /* include symbols if loaded and useful */
=! #ifdef DDB
=  	movl	R(_bootinfo+BI_ESYMTAB),%edi
=  	testl	%edi,%edi
=--- 749,753 ----
=  	movl	$R(_end),%esi
=  
=! /* Include symbols, if any. */
=  	movl	R(_bootinfo+BI_ESYMTAB),%edi
=  	testl	%edi,%edi
=***************
=*** 761,765 ****
=  	addl	%edi,R(_bootinfo+BI_ESYMTAB)
=  over_symalloc:
=- #endif
=  
=  /* If we are told where the end of the kernel space is, believe it. */
=--- 758,761 ----
=
=Bruce
=
-- End of included mail.



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


From owner-freebsd-stable  Tue Mar 28  8:51:10 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from pi.yip.org (yip.org [199.45.111.121])
	by hub.freebsd.org (Postfix) with ESMTP id 64BF937C14A
	for <freebsd-stable@FreeBSD.ORG>; Tue, 28 Mar 2000 08:50:49 -0800 (PST)
	(envelope-from melange@yip.org)
Received: from localhost (melange@localhost)
	by pi.yip.org (8.9.3/8.9.3) with ESMTP id LAA43813
	for <freebsd-stable@FreeBSD.ORG>; Tue, 28 Mar 2000 11:50:13 -0500 (EST)
	(envelope-from melange@yip.org)
Date: Tue, 28 Mar 2000 11:50:13 -0500 (EST)
From: Bob K <melange@yip.org>
X-Sender: melange@localhost
To: freebsd-stable@FreeBSD.ORG
Subject: Re: 4.0-STABLE dhcp conflicts. 
In-Reply-To: <14560.56319.827242.610802@trooper.velocet.net>
Message-ID: <Pine.BSF.4.21.0003281147160.72136-100000@localhost>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Tue, 28 Mar 2000, David Gilbert wrote:

> >>>>> "Brian" == Brian Kraemer <kraemer@u.washington.edu> writes:
> 
> Brian> in message <14559.40450.544687.51037@trooper.velocet.net>,
> Brian> David Gilbert writes:
> >> It appears that when I run two (not sure if one does it) tcpdumps
> >> on the dhcp server, the dhcp clients don't get any responses to
> >> their queries.  Is there some flaw in the dhcpd bpf rules?
> 
> Brian> Do you have enough bpf devices enabled? I imagine each tcpdump
> Brian> will use one, and dhcpd also uses one if I am not mistaken.
> 
> Well... one not-so-nice "feature" of the dhcpd or bpf interface (don't 
> know which) is that it requires one bpf per interface.

I do believe this was done for security reasons.  (ie, if a box with dhcpd
is compromised but only has 1 bpf interface, it would require stopping of
dhcpd or a recompiled kernel/reboot to run tcpdump, which hopefully would
be noticed)

Bob <melange@yip.org>
"And I had the same fish/pants/jolt/staples/cieling problem you did."
							- John Teffer



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


From owner-freebsd-stable  Tue Mar 28  8:56:31 2000
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 0061737C18E
	for <stable@freebsd.org>; Tue, 28 Mar 2000 08:56:24 -0800 (PST)
	(envelope-from jdp@polstra.com)
Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13])
	by wall.polstra.com (8.9.3/8.9.3) with ESMTP id IAA09650;
	Tue, 28 Mar 2000 08:56:20 -0800 (PST)
	(envelope-from jdp@polstra.com)
From: John Polstra <jdp@polstra.com>
Received: (from jdp@localhost)
	by vashon.polstra.com (8.9.3/8.9.1) id IAA04266;
	Tue, 28 Mar 2000 08:56:20 -0800 (PST)
	(envelope-from jdp@polstra.com)
Date: Tue, 28 Mar 2000 08:56:20 -0800 (PST)
Message-Id: <200003281656.IAA04266@vashon.polstra.com>
To: aa8vb@ipass.net
Subject: Re: Dynamic linker bug in 3.4-RELEASE (I think)
In-Reply-To: <20000327215804.A64173@ipass.net>
References: <20000317195156.A24243@ipass.net> <200003280211.SAA03086@vashon.polstra.com> <20000327215804.A64173@ipass.net>
Organization: Polstra & Co., Seattle, WA
Cc: stable@freebsd.org
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

In article <20000327215804.A64173@ipass.net>,
Randall Hopper  <aa8vb@ipass.net> wrote:
>  |> If I run it over-and-over many times repeatedly, occasionally the dynamic
>  |> linker will fail to resolve the "sigwait" symbol.
>  |
>  |Is your program multi-threaded?  There are some known problems in
>  |connection with that.
> 
> This program isn't threaded, though I compiled it with -pthread (another
> util in that dir is threaded, and I'd used the same CFLAGS for both).
> 
>  |Try setting LD_BIND_NOW=1 in the environment and see if that changes
>  |the behavior.
> 
> That seemed to clear it up.  (Though, it happens so rarely it's hard to be
> sure.)

It may be a race between a signal handler and the mainline code, then.
Or it could be that the pthreads library (libc_r) uses one or more
internal threads which would make your application multi-threaded even
if you didn't intend it to be.  I will have to look again to see where
things stand in the -stable version of the dynamic linker.  I just got
home from vacation, and the warm sunshine seems to have irradiated
away most of my memory cells. :-)

If it's convenient for you, please try using the dynamic linker from
-current or 4.0.  It should cure this problem, and it should build OK
on a 3.4 system.  (You can find it in "src/libexec/rtld-elf".)  A word
of caution: be very careful if you experiment with the dynamic linker.
Almost nothing works if it is broken.  (In particular, you won't be
able to run the compiler to build a new one.)  Make a backup copy
named something like "/usr/libexec/ld-elf.so.1.good" first, so you can
"mv" it back into place if something goes wrong.  The basic utilities
such as "mv" and "cp" are statically linked, so they'll still work
even if the dynamic linker is broken.

John
-- 
  John Polstra                                               jdp@polstra.com
  John D. Polstra & Co., Inc.                        Seattle, Washington USA
  "Disappointment is a good sign of basic intelligence."  -- Chögyam Trungpa



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


From owner-freebsd-stable  Tue Mar 28  9:23:31 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from mail.rdc2.pa.home.com (ha1.rdc2.pa.home.com [24.12.106.194])
	by hub.freebsd.org (Postfix) with ESMTP id 036CE37B838
	for <FreeBSD-Stable@FreeBSD.ORG>; Tue, 28 Mar 2000 09:23:16 -0800 (PST)
	(envelope-from jgowdy@home.com)
Received: from cx443070a ([24.4.93.90]) by mail.rdc2.pa.home.com
          (InterMail v4.01.01.00 201-229-111) with SMTP
          id <20000328172314.DXKR28012.mail.rdc2.pa.home.com@cx443070a>;
          Tue, 28 Mar 2000 09:23:14 -0800
Message-ID: <001901bf98db$9b897580$0100000a@vista1.sdca.home.com>
From: "Jeremiah Gowdy" <jgowdy@home.com>
To: "Daniel C. Sobral" <dcs@newsguy.com>,
	"Alexandr Listopad" <laa@ZGIA.zp.ua>
Cc: "Kuzak" <kuzak@kuzak.net>, <FreeBSD-Stable@FreeBSD.ORG>
References: <Pine.BSF.4.10.10003271228100.48901-100000@Eagle.ZGIA.zp.ua> <38E065C5.418DA948@newsguy.com>
Subject: Re: 4.0 Kernel
Date: Tue, 28 Mar 2000 09:32:34 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.6700
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> Alexandr Listopad wrote:
> >
> > # -- sysinstall generated deltas -- #
> > userconfig_script_load="NO"
> > autoboot_delay="0"
> >
> > splash_bmp_load="YES"
> > bitmap_load="YES"
> > bitmap_name="/boot/daemon.bmp"  # Set this to the name of
> > the bmp or pcx file
> > bitmap_type="splash_image_data"
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> This line is not necessary, as it is already set by default.

I knew there was some kind of splash screen you could do for FreeBSD, I just
didn't know how to do it.  Thanks for enlightening me :)  Now, my question
is, anyone have some good bmps for a splash screen ?  Where can I get that
daemon.bmp ?  Thanks




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


From owner-freebsd-stable  Tue Mar 28  9:29:44 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from mail.rdc2.pa.home.com (ha1.rdc2.pa.home.com [24.12.106.194])
	by hub.freebsd.org (Postfix) with ESMTP id 50C3C37B8DE
	for <freebsd-stable@FreeBSD.ORG>; Tue, 28 Mar 2000 09:29:28 -0800 (PST)
	(envelope-from jgowdy@home.com)
Received: from cx443070a ([24.4.93.90]) by mail.rdc2.pa.home.com
          (InterMail v4.01.01.00 201-229-111) with SMTP
          id <20000328172927.EACK28012.mail.rdc2.pa.home.com@cx443070a>;
          Tue, 28 Mar 2000 09:29:27 -0800
Message-ID: <002301bf98dc$79ed86e0$0100000a@vista1.sdca.home.com>
From: "Jeremiah Gowdy" <jgowdy@home.com>
To: "Martin Cracauer" <cracauer@cons.org>,
	<freebsd-stable@FreeBSD.ORG>
References: <20000328113633.A28085@cons.org>
Subject: Re: Let 3.x die ASAP?
Date: Tue, 28 Mar 2000 09:38:48 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.6700
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

I'll agree with most of the points you made.  When 3.4 was all there was, I
was content with it, because I've known nothing else.  But after seeing how
beautiful 4.0 can be in certain areas, (my favs are new linux emu threads
and ATAPI rather than wd0), I would hate to go back to 3.4.  In fact, I'm
upgrading my work's mission critical computer to 4.0-RELEASE.  I really
think it's _alot_ better (as it should be, since it's a X.0 release).  My
opinion, although what people do with their time is none of my business, is
that it would be best to have everyone concentrate their efforts on 4.0.
Just my little opinion :)




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


From owner-freebsd-stable  Tue Mar 28  9:32: 1 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from mail.rdc2.pa.home.com (ha1.rdc2.pa.home.com [24.12.106.194])
	by hub.freebsd.org (Postfix) with ESMTP id DC2A137C021
	for <stable@FreeBSD.ORG>; Tue, 28 Mar 2000 09:31:57 -0800 (PST)
	(envelope-from jgowdy@home.com)
Received: from cx443070a ([24.4.93.90]) by mail.rdc2.pa.home.com
          (InterMail v4.01.01.00 201-229-111) with SMTP
          id <20000328173144.EBBF28012.mail.rdc2.pa.home.com@cx443070a>;
          Tue, 28 Mar 2000 09:31:44 -0800
Message-ID: <003501bf98dc$cb930420$0100000a@vista1.sdca.home.com>
From: "Jeremiah Gowdy" <jgowdy@home.com>
To: <pushf@club-internet.fr>, <stable@FreeBSD.ORG>
References: <mnet1.954240976.21608.pushf@club-internet.fr>
Subject: Re: 
Date: Tue, 28 Mar 2000 09:41:05 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.6700
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

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

Don't you guys love these messages, where it shows the dude trying to
unsubscribe, and then the tagline ?  It's like someone screaming "What's the
number for 911 ?!"





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


From owner-freebsd-stable  Tue Mar 28  9:35:44 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from everest.overx.com (everest.overx.com [63.93.29.10])
	by hub.freebsd.org (Postfix) with ESMTP id 4465537B697
	for <freebsd-stable@FreeBSD.ORG>; Tue, 28 Mar 2000 09:35:38 -0800 (PST)
	(envelope-from dayton@overx.com)
Received: from polo.overx.com (polo.overx.com [63.93.29.12])
	by everest.overx.com (Postfix) with ESMTP
	id 18B3B2008; Tue, 28 Mar 2000 11:35:37 -0600 (CST)
Received: by polo.overx.com (Postfix, from userid 1001)
	id ED6203F3F; Tue, 28 Mar 2000 11:35:42 -0600 (CST)
From: Soren Dayton <dayton@overx.com>
Reply-To: dayton+freebsd-stable@overx.com
To: "Jeremiah Gowdy" <jgowdy@home.com>
Cc: "Martin Cracauer" <cracauer@cons.org>,
	<freebsd-stable@FreeBSD.ORG>
Subject: Re: Let 3.x die ASAP?
References: <20000328113633.A28085@cons.org> <002301bf98dc$79ed86e0$0100000a@vista1.sdca.home.com>
Date: 28 Mar 2000 11:35:42 -0600
In-Reply-To: "Jeremiah Gowdy"'s message of "Tue, 28 Mar 2000 09:38:48 -0800"
Message-ID: <868zz3m1zl.fsf@polo.overx.com>
Lines: 27
User-Agent: Gnus/5.070099 (Pterodactyl Gnus v0.99) XEmacs/21.1 (Bryce Canyon)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


Is there a good list of improvements?  In particular details of the
NFS improvements?  I tried looking through the CVS logs, but it was
not immediately clear to me.  And doing that for the entire source
tree doesn't seem very efficient.

Thanks,
Soren


"Jeremiah Gowdy" <jgowdy@home.com> writes:

> I'll agree with most of the points you made.  When 3.4 was all there was, I
> was content with it, because I've known nothing else.  But after seeing how
> beautiful 4.0 can be in certain areas, (my favs are new linux emu threads
> and ATAPI rather than wd0), I would hate to go back to 3.4.  In fact, I'm
> upgrading my work's mission critical computer to 4.0-RELEASE.  I really
> think it's _alot_ better (as it should be, since it's a X.0 release).  My
> opinion, although what people do with their time is none of my business, is
> that it would be best to have everyone concentrate their efforts on 4.0.
> Just my little opinion :)
> 
> 
> 
> 
> 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 28  9:40:49 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from mail.rdc1.wa.home.com (ha1.rdc1.wa.home.com [24.0.2.66])
	by hub.freebsd.org (Postfix) with ESMTP id 3B50537B6BE
	for <stable@FreeBSD.ORG>; Tue, 28 Mar 2000 09:40:46 -0800 (PST)
	(envelope-from johnmpurser@home.com)
Received: from c37259a ([24.9.57.64]) by mail.rdc1.wa.home.com
          (InterMail v4.01.01.00 201-229-111) with SMTP
          id <20000328174045.DPAT1875.mail.rdc1.wa.home.com@c37259a>;
          Tue, 28 Mar 2000 09:40:45 -0800
Reply-To: <johnmpurser@home.com>
From: "John Purser" <johnmpurser@home.com>
To: "'Jeremiah Gowdy'" <jgowdy@home.com>, <pushf@club-internet.fr>,
	<stable@FreeBSD.ORG>
Subject: RE: 
Date: Tue, 28 Mar 2000 09:38:56 -0800
Message-ID: <000201bf98dc$7e7224a0$40390918@vncvr1.wa.home.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.2377.0
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
In-Reply-To: <003501bf98dc$cb930420$0100000a@vista1.sdca.home.com>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

I help out the ones trying to subscribe.  I figure Darwin will take care of
the ones who can't figure out how to unsubscribe!

John Purser

***********************************************************************
Currently boycotting Amazon.com
To find out why visit:
http://perl.oreilly.com/cgi-bin/amazon_patent.comments.pl
For an alternative visit:
http://www.fatbrain.com/

-----Original Message-----
From: owner-freebsd-stable@FreeBSD.ORG
[mailto:owner-freebsd-stable@FreeBSD.ORG]On Behalf Of Jeremiah Gowdy
Sent: Tuesday, March 28, 2000 9:41 AM
To: pushf@club-internet.fr; stable@FreeBSD.ORG
Subject: Re:


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

Don't you guys love these messages, where it shows the dude trying to
unsubscribe, and then the tagline ?  It's like someone screaming "What's the
number for 911 ?!"





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 28  9:40:56 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from ktts.kharkov.ua (ktts.kharkov.ua [193.124.57.65])
	by hub.freebsd.org (Postfix) with ESMTP id E99D337B6DD
	for <freebsd-stable@freebsd.org>; Tue, 28 Mar 2000 09:40:46 -0800 (PST)
	(envelope-from greg@Thing-Fish.Kharkov.NET)
Received: from Thing-Fish.Kharkov.NET (greg@Thing-Fish.Kharkov.NET [193.124.57.81])
	by ktts.kharkov.ua (8.9.3/8.9.3) with ESMTP id UAA27405
	for <freebsd-stable@freebsd.org>; Tue, 28 Mar 2000 20:37:56 +0300 (EEST)
Received: (from greg@localhost)
	by Thing-Fish.Kharkov.NET (8.9.0/8.9.0) id UAA01260
	for freebsd-stable@freebsd.org; Tue, 28 Mar 2000 20:37:56 +0300 (EEST)
From: Gregory Edigaroff <greg@Thing-Fish.Kharkov.NET>
Message-Id: <200003281737.UAA01260@Thing-Fish.Kharkov.NET>
Subject: gcc problems
To: freebsd-stable@freebsd.org
Date: Tue, 28 Mar 2000 20:37:54 +0300 (EEST)
X-Mailer: ELM [version 2.4 PL25]
MIME-Version: 1.0
Content-Type: text/plain; charset=koi8-r
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hello!
It seems like gcc-2.95.2 has a leak, which could freeze the compilation.
I experienced this while compile MySQL-3.22.32.
It hangs up on:
c++ -DMYSQL_SERV-DDATADIR="\"/usr/local/var\"" LT_MYSQL_HOME="\"-DSHAREDIR="\"/u
sr/local/share/m-I./../regex                    -I. -I../include -I.. -I.    -D_
LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -O3 -DDBUG_OFF   -
fno-implicit-templates -DMYSQLD_NET_RETRY_COUNT=1000000  -c sql_yacc.cc

and is unable to compile it due to cycling with swap read/swap write.
Here is what top shows now:
last pid:   316;  load averages:  0.78,  0.84,  0.83    up 0+00:32:29  20:36:41
26 processes:  2 running, 24 sleeping
CPU states: 19.2% user,  0.0% nice, 41.7% system,  3.8% interrupt, 35.2% idle
Mem: 20M Active, 396K Inact, 5816K Wired, 1976K Cache, 2761K Buf, 364K Free
Swap: 1286M Total, 157M Used, 1129M Free, 12% Inuse, 2096K In, 140K Out
  PID USERNAME PRI NICE  SIZE    RES STATE    TIME   WCPU    CPU COMMAND
  282 cat       50   0  1820K   296K RUN     11:21 43.75% 43.75% top
  280 cat      -22   0   154M 20632K RUN      7:04  9.72%  9.72% cc1plus

What can I do?
-- 
With best regards,
	Gregory Edigarov


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


From owner-freebsd-stable  Tue Mar 28  9:42:10 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from pan.ch.intel.com (pan.ch.intel.com [143.182.246.24])
	by hub.freebsd.org (Postfix) with ESMTP id 44A2437C087
	for <freebsd-stable@freebsd.org>; Tue, 28 Mar 2000 09:42:07 -0800 (PST)
	(envelope-from jreynold@sedona.ch.intel.com)
Received: from sedona.intel.com (sedona.ch.intel.com [143.182.218.21])
	by pan.ch.intel.com (8.9.1a+p1/8.9.1/d: relay.m4,v 1.19 2000/01/29 00:15:43 dmccart Exp $) with ESMTP id KAA09257;
	Tue, 28 Mar 2000 10:41:59 -0700 (MST)
Received: from hip186.ch.intel.com (hip186.ch.intel.com [143.182.225.68])
	by sedona.intel.com (8.9.1a/8.9.1/d: sendmail.cf,v 1.10 2000/02/10 21:38:16 steved Exp $) with ESMTP id KAA00295;
	Tue, 28 Mar 2000 10:40:54 -0700 (MST)
X-Envelope-From: jreynold@sedona.ch.intel.com
Received: (from jreynold@localhost)
	by hip186.ch.intel.com (8.9.1a/8.9.1/d: client.m4,v 1.3 1998/09/29 16:36:11 sedayao Exp sedayao $) id MAA15790;
	Tue, 28 Mar 2000 12:41:59 -0500 (EST)
X-Authentication-Warning: hip186.ch.intel.com: jreynold set sender to jreynold@sedona.ch.intel.com using -f
From: John Reynolds~ <jreynold@sedona.ch.intel.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <14560.61158.893585.613640@hip186.ch.intel.com>
Date: Tue, 28 Mar 2000 10:41:58 -0700 (MST)
To: dayton+freebsd-stable@overx.com
Cc: "Jeremiah Gowdy" <jgowdy@home.com>,
	"Martin Cracauer" <cracauer@cons.org>, <freebsd-stable@freebsd.org>
Subject: Re: Let 3.x die ASAP?
In-Reply-To: <868zz3m1zl.fsf@polo.overx.com>
References: <20000328113633.A28085@cons.org>
	<002301bf98dc$79ed86e0$0100000a@vista1.sdca.home.com>
	<868zz3m1zl.fsf@polo.overx.com>
X-Mailer: VM 6.75 under Emacs 20.3.11
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


[ On , March 28, Soren Dayton wrote: ]
> 
> Is there a good list of improvements?  In particular details of the
> NFS improvements?  I tried looking through the CVS logs, but it was
> not immediately clear to me.  And doing that for the entire source
> tree doesn't seem very efficient.
> 
> Thanks,
> Soren
> 

  http://www.freebsd.org/releases/4.0R/notes.html

Well, it doesn't go into specifics on what the NFS fixes were. Perhaps
somebody in -current could point you to a list of the "biggies" or point you
to the right keywords to search the mailing list archives for freebsd-current.

-Jr

-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
| John Reynolds               WCCG, CCE, Higher Levels of Abstraction       |
| Intel Corporation   MS: CH6-210   Phone: 480-554-9092   pgr: 602-868-6512 |
| jreynold@sedona.ch.intel.com  http://www-aec.ch.intel.com/~jreynold/      |
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=


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


From owner-freebsd-stable  Tue Mar 28  9:44:33 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from firehouse.net (networkoperations.com [209.42.203.32])
	by hub.freebsd.org (Postfix) with SMTP id 249B737B58E
	for <freebsd-stable@FreeBSD.ORG>; Tue, 28 Mar 2000 09:44:14 -0800 (PST)
	(envelope-from abc@firehouse.net)
Received: (qmail 6624 invoked by uid 1000); 28 Mar 2000 17:43:56 -0000
Date: Tue, 28 Mar 2000 12:43:56 -0500
From: Alan Clegg <abc@bsdi.com>
To: freebsd-stable@FreeBSD.ORG
Subject: Re: Let 3.x die ASAP?
Message-ID: <20000328124356.D5798@ecto.greenpeas.org>
References: <20000328113633.A28085@cons.org> <002301bf98dc$79ed86e0$0100000a@vista1.sdca.home.com> <868zz3m1zl.fsf@polo.overx.com>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-md5;
	protocol="application/pgp-signature"; boundary="0/kgSOzhNoDC5T3a"
X-Mailer: Mutt 1.0.1i
In-Reply-To: <868zz3m1zl.fsf@polo.overx.com>; from dayton@overx.com on Tue, Mar 28, 2000 at 11:35:42AM -0600
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


--0/kgSOzhNoDC5T3a
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable

Out of the ether, Soren Dayton spewed forth the following bitstream:

> Is there a good list of improvements?  In particular details of the
> NFS improvements?  I tried looking through the CVS logs, but it was
> not immediately clear to me.  And doing that for the entire source
> tree doesn't seem very efficient.

This would be a *BIG* help.=20

I'd be happy to keep up something like this, if the developers would e-mail
me what they added to version 4.0 and what win their chunk has over 3.x.

AlanC {assuming this does not already exist}

--0/kgSOzhNoDC5T3a
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 5.0i for non-commercial use
MessageID: bRi1EQ8NV7U433F+/x1wVtCu65tqkLlL

iQA/AwUBOODvW/cyv/gweBpYEQIk1ACfbdqSaV/4e7hQzAbj0QqmDJr8mM4An2V0
n1K2n24Y8L9o9X+f4vt/0UT5
=UWWD
-----END PGP SIGNATURE-----

--0/kgSOzhNoDC5T3a--


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


From owner-freebsd-stable  Tue Mar 28  9:47:39 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from pawn.primelocation.net (pawn.primelocation.net [205.161.238.235])
	by hub.freebsd.org (Postfix) with ESMTP id 239CA37C01E
	for <freebsd-stable@freebsd.org>; Tue, 28 Mar 2000 09:47:34 -0800 (PST)
	(envelope-from cdf.lists@fxp.org)
Received: by pawn.primelocation.net (Postfix, from userid 1016)
	id D33DB9B19; Tue, 28 Mar 2000 12:47:30 -0500 (EST)
Received: from localhost (localhost [127.0.0.1])
	by pawn.primelocation.net (Postfix) with ESMTP
	id CB713BA1D; Tue, 28 Mar 2000 12:47:30 -0500 (EST)
Date: Tue, 28 Mar 2000 12:47:30 -0500 (EST)
From: "Chris D. Faulhaber" <jedgar@fxp.org>
X-Sender: cdf.lists@pawn.primelocation.net
To: Gregory Edigaroff <greg@Thing-Fish.Kharkov.NET>
Cc: freebsd-stable@freebsd.org
Subject: Re: gcc problems
In-Reply-To: <200003281737.UAA01260@Thing-Fish.Kharkov.NET>
Message-ID: <Pine.BSF.4.10.10003281246180.26113-100000@pawn.primelocation.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Tue, 28 Mar 2000, Gregory Edigaroff wrote:

> Hello!
> It seems like gcc-2.95.2 has a leak, which could freeze the compilation.
> I experienced this while compile MySQL-3.22.32.
> It hangs up on:
> c++ -DMYSQL_SERV-DDATADIR="\"/usr/local/var\"" LT_MYSQL_HOME="\"-DSHAREDIR="\"/u
> sr/local/share/m-I./../regex                    -I. -I../include -I.. -I.    -D_
> LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -O3 -DDBUG_OFF   -
> fno-implicit-templates -DMYSQLD_NET_RETRY_COUNT=1000000  -c sql_yacc.cc
> 
> and is unable to compile it due to cycling with swap read/swap write.
> Here is what top shows now:
> last pid:   316;  load averages:  0.78,  0.84,  0.83    up 0+00:32:29  20:36:41
> 26 processes:  2 running, 24 sleeping
> CPU states: 19.2% user,  0.0% nice, 41.7% system,  3.8% interrupt, 35.2% idle
> Mem: 20M Active, 396K Inact, 5816K Wired, 1976K Cache, 2761K Buf, 364K Free
> Swap: 1286M Total, 157M Used, 1129M Free, 12% Inuse, 2096K In, 140K Out
>   PID USERNAME PRI NICE  SIZE    RES STATE    TIME   WCPU    CPU COMMAND
>   282 cat       50   0  1820K   296K RUN     11:21 43.75% 43.75% top
>   280 cat      -22   0   154M 20632K RUN      7:04  9.72%  9.72% cc1plus
> 
> What can I do?
> 

Use the port, which set the optimization to -O0 for that file.  Search the
-ports mailing list for further discussions.

-----
Chris D. Faulhaber - jedgar@fxp.org - jedgar@FreeBSD.org
--------------------------------------------------------
FreeBSD: The Power To Serve   -   http://www.FreeBSD.org



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


From owner-freebsd-stable  Tue Mar 28  9:48: 1 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from hotmail.com (f62.law8.hotmail.com [216.33.241.62])
	by hub.freebsd.org (Postfix) with SMTP id 34B6B37C092
	for <freebsd-stable@freebsd.org>; Tue, 28 Mar 2000 09:47:45 -0800 (PST)
	(envelope-from hjeffrey@hotmail.com)
Received: (qmail 60659 invoked by uid 0); 28 Mar 2000 17:47:44 -0000
Message-ID: <20000328174744.60658.qmail@hotmail.com>
Received: from 130.11.112.22 by www.hotmail.com with HTTP;
	Tue, 28 Mar 2000 09:47:43 PST
X-Originating-IP: [130.11.112.22]
From: "Jeff Hamilton" <hjeffrey@hotmail.com>
To: freebsd-questions@freebsd.org, freebsd-stable@freebsd.org
Subject: /etc/hosts.allow
Date: Tue, 28 Mar 2000 09:47:43 PST
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hi.

I am having a problem with my /etc/hosts.allow - periodically, I get the 
following message:

Mar 28 17:37:54 hostname portmap[154]: warning: /etc/hosts.allow, line 16: 
twist_option: dup: Bad file descriptor

my /etc/hosts.allow (# comments removed):

ALL : PARANOID : RFC931 20 : deny
ALL : .mydomain.com : allow

ALL : ALL \
        : severity auth.info \
        : twist /bin/echo "You are not welcome to use %d from %h."

What am I doing wrong, or is this message expected?

uname -a:

FreeBSD hostname 4.0-STABLE FreeBSD 4.0-STABLE #12: Tue Mar 28 17:34:45 EST 
2000     root@hostname:/usr/src/sys/compile/XXXX  i386

Thanks.

Jeff
hjeffrey@hotmail.com

(Note:  hostname and mydomain have been substituted for the real hostname 
and domain for security reasons.)
______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com



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


From owner-freebsd-stable  Tue Mar 28 10: 4:51 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from postfix1.free.fr (postfix1.free.fr [212.27.32.21])
	by hub.freebsd.org (Postfix) with ESMTP id A547337B56C
	for <freebsd-stable@FreeBSD.ORG>; Tue, 28 Mar 2000 10:04:46 -0800 (PST)
	(envelope-from jaco@titine.fr.eu.org)
Received: from titine.fr.eu.org (unknown [213.228.62.193])
	by postfix1.free.fr (Postfix) with ESMTP
	id 09268281F9; Tue, 28 Mar 2000 20:04:40 +0200 (MEST)
Received: by titine.fr.eu.org (Postfix, from userid 1000)
	id CE0B814987; Tue, 28 Mar 2000 19:45:15 +0200 (CEST)
To: Grigoriy Strokin <grg@philol.msu.ru>
Cc: freebsd-stable@FreeBSD.ORG
Subject: Re: New kernel with its ATA drivers damages the filesystem
References: <20000328195030.A30092@isabase.philol.msu.ru>
From: Eric Jacoboni <jaco@titine.fr.eu.org>
Date: 28 Mar 2000 19:45:15 +0200
In-Reply-To: Grigoriy Strokin's message of "Tue, 28 Mar 2000 19:50:30 +0400"
Message-ID: <87ln33htuc.fsf@titine.fr.eu.org>
Lines: 23
User-Agent: Gnus/5.0803 (Gnus v5.8.3) XEmacs/21.1 (Canyonlands)
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Grigoriy Strokin <grg@philol.msu.ru> writes:


> Mar 28 17:49:07 koch2 /kernel: ed0: device timeout
> Mar 28 17:49:07 koch2 /kernel: ed0: device timeout
> Mar 28 17:49:07 koch2 /kernel: ata0: resetting devices .. done
> Mar 28 17:49:48 koch2 /kernel: ad0: WRITE command timeout - resetting
> Mar 28 17:49:48 koch2 /kernel: ata0: resetting devices .. done

> Now I think I don't know where to find the source of the problem.

Have you tried what the ata manpage suggests ?

I've had the same problem, it's now fixed with the following line
added in my /etc/rc.local :

/sbin/sysctl -w hw.atamodes=pio,pio,pio

(i've 2 ide disks + an ATAPI cdrom).
-- 
---------------------------------------------------------
Éric Jacoboni       « No sport, cigars! »  (W. Churchill)
---------------------------------------------------------


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


From owner-freebsd-stable  Tue Mar 28 10: 5:12 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from firehouse.net (networkoperations.com [209.42.203.32])
	by hub.freebsd.org (Postfix) with SMTP id 7921E37B56C
	for <freebsd-stable@FreeBSD.ORG>; Tue, 28 Mar 2000 10:04:53 -0800 (PST)
	(envelope-from abc@firehouse.net)
Received: (qmail 7026 invoked by uid 1000); 28 Mar 2000 18:04:46 -0000
Date: Tue, 28 Mar 2000 13:04:46 -0500
From: Alan Clegg <abc@firehouse.net>
To: freebsd-stable@FreeBSD.ORG
Subject: Re: Let 3.x die ASAP?
Message-ID: <20000328130446.F5798@ecto.greenpeas.org>
References: <20000328113633.A28085@cons.org> <002301bf98dc$79ed86e0$0100000a@vista1.sdca.home.com> <868zz3m1zl.fsf@polo.overx.com> <20000328124356.D5798@ecto.greenpeas.org>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-md5;
	protocol="application/pgp-signature"; boundary="ni93GHxFvA+th69W"
X-Mailer: Mutt 1.0.1i
In-Reply-To: <20000328124356.D5798@ecto.greenpeas.org>; from abc@BSDI.COM on Tue, Mar 28, 2000 at 12:43:56PM -0500
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


--ni93GHxFvA+th69W
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable

Out of the ether, Alan Clegg spewed forth the following bitstream:
> Out of the ether, Soren Dayton spewed forth the following bitstream:
>=20
> > Is there a good list of improvements?  In particular details of the
> > NFS improvements?  I tried looking through the CVS logs, but it was
> > not immediately clear to me.  And doing that for the entire source
> > tree doesn't seem very efficient.
>=20
> This would be a *BIG* help.=20
>=20
> I'd be happy to keep up something like this, if the developers would e-ma=
il
> me what they added to version 4.0 and what win their chunk has over 3.x.

Forget this... see the URL mentioned elsewhere in this thread.

AlanC

--ni93GHxFvA+th69W
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 5.0i for non-commercial use
MessageID: xf1n7ogEo2u15Ecg+OLBiMRxaiRBCe3Q

iQA/AwUBOOD0Pfcyv/gweBpYEQJPQACeN9CITImyZunmU8SpgbexfhN68GkAoNI0
fDKlTaKALwEHpoIJwAPxRf7d
=Rhb5
-----END PGP SIGNATURE-----

--ni93GHxFvA+th69W--


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


From owner-freebsd-stable  Tue Mar 28 10: 7:41 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from europe.std.com (europe.std.com [199.172.62.20])
	by hub.freebsd.org (Postfix) with ESMTP id 64E5937C0E2
	for <freebsd-stable@freebsd.org>; Tue, 28 Mar 2000 10:07:36 -0800 (PST)
	(envelope-from kwc@world.std.com)
Received: from world.std.com (root@world-f.std.com [199.172.62.5])
	by europe.std.com (8.9.3/8.9.3) with ESMTP id NAA17135;
	Tue, 28 Mar 2000 13:07:23 -0500 (EST)
Received: (from kwc@localhost)
	by world.std.com (8.9.3/8.9.3) id NAA02837;
	Tue, 28 Mar 2000 13:02:18 -0500 (EST)
Date: Tue, 28 Mar 2000 13:02:18 -0500 (EST)
From: Kenneth W Cochran <kwc@world.std.com>
Message-Id: <200003281802.NAA02837@world.std.com>
To: "Eric S . Van Gyzen" <lists@vangyzen.net>
Subject: Re:  R/W mount of ext2fs fails
Cc: freebsd-stable@freebsd.org
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

>From owner-freebsd-stable@FreeBSD.ORG  Tue Mar 28 11:45:55 2000
>Date: Tue, 28 Mar 2000 11:38:20 -0500
>From: "Eric S . Van Gyzen" <lists@vangyzen.net>
>Subject: R/W mount of ext2fs fails
>
>I just upgraded from 3.4-STABLE to 4.0-STABLE and am having
>problems mounting my Linux partition.  The Linux root filesystem
>is on /dev/da0s3.  Here's what happens:
>
>	# mount -t ext2fs /dev/da0s3 /mnt/linux
>	ext2fs: /dev/da0s3: Invalid argument
>	# ls -l /dev/da0s3
>	crw-r-----  1 root  operator   13, 0x00040002 Mar 28 11:35 /dev/da0s3
>
>Syslog reports:
>	/kernel: WARNING: R/W mount of #da/0x40002 denied due to
>	unsupported optional features
>
>Huh?  To what "unsupported optional features" is it referring?

1.  The new "dynamic" version 1 ext2 filesystem.  Previously
    this was version 0.

2.  "sparse_superblock"

>In case it matters, the Linux installation is Red Hat 6.1.  And
>I do have
>	options         EXT2FS
>in my kernel config.  I thought maybe the filesystem wasn't clean,
>so I booted Linux and fsck'ed, only to get the same results.

It also happens with Slackware 7.0 & I'm sure others, effective
with 3.4-STABLE as of a couple of weeks ago...

>Thanks for any help, or pointers to documentation that I should
>have read...
>
>-Eric
>
>FreeBSD 4.0-STABLE #0: Thu Mar 23 15:16:02 EST 2000

Check the archives of this list & freebsd-fs from just a few
days ago...

This (new) behavior of FreeBSD's ext2fs support is really a
bugfix, introduced a couple of weeks ago into RELENG_3.  And
they have Good Reason to have done this...  :)  I have been able
to mount the new ext2 fs readonly, but r/w appears to now only
be supported for the "old" style ext2 fs.

-kc


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


From owner-freebsd-stable  Tue Mar 28 10:10:28 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from europe.std.com (europe.std.com [199.172.62.20])
	by hub.freebsd.org (Postfix) with ESMTP id 814D137C070
	for <freebsd-stable@freebsd.org>; Tue, 28 Mar 2000 10:10:21 -0800 (PST)
	(envelope-from kwc@world.std.com)
Received: from world.std.com (root@world-f.std.com [199.172.62.5])
	by europe.std.com (8.9.3/8.9.3) with ESMTP id NAA18195;
	Tue, 28 Mar 2000 13:10:15 -0500 (EST)
Received: (from kwc@localhost)
	by world.std.com (8.9.3/8.9.3) id NAA05866;
	Tue, 28 Mar 2000 13:05:29 -0500 (EST)
Date: Tue, 28 Mar 2000 13:05:29 -0500 (EST)
From: Kenneth W Cochran <kwc@world.std.com>
Message-Id: <200003281805.NAA05866@world.std.com>
To: dayton+freebsd-stable@overx.com
Subject: Re: Let 3.x die ASAP?
Cc: freebsd-stable@freebsd.org
References: <20000328113633.A28085@cons.org>
    <002301bf98dc$79ed86e0$0100000a@vista1.sdca.home.com>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

>From owner-freebsd-stable@FreeBSD.ORG  Tue Mar 28 12:42:40 2000
>From: Soren Dayton <dayton@overx.com>
>Subject: Re: Let 3.x die ASAP?
>Date: 28 Mar 2000 11:35:42 -0600
>
>Is there a good list of improvements?  In particular details of
>the NFS improvements?  I tried looking through the CVS logs, but
>it was not immediately clear to me.  And doing that for the
>entire source tree doesn't seem very efficient.
>
>Thanks,
>Soren

Perhaps src/UPDATING?  There is a reverse chronological history
log there...

-kc

>"Jeremiah Gowdy" <jgowdy@home.com> writes:
>
>> I'll agree with most of the points you made.  When 3.4 was all there was, I
>> was content with it, because I've known nothing else.  But after seeing how
>> beautiful 4.0 can be in certain areas, (my favs are new linux emu threads
>> and ATAPI rather than wd0), I would hate to go back to 3.4.  In fact, I'm
>> upgrading my work's mission critical computer to 4.0-RELEASE.  I really
>> think it's _alot_ better (as it should be, since it's a X.0 release).  My
>> opinion, although what people do with their time is none of my business, is
>> that it would be best to have everyone concentrate their efforts on 4.0.
>> Just my little opinion :)


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


From owner-freebsd-stable  Tue Mar 28 10:13:39 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from isabase.philol.msu.ru (isabase.philol.msu.ru [195.208.217.73])
	by hub.freebsd.org (Postfix) with ESMTP id 35FF837B60D
	for <freebsd-stable@FreeBSD.ORG>; Tue, 28 Mar 2000 10:13:28 -0800 (PST)
	(envelope-from grg@isabase.philol.msu.ru)
Received: (from grg@localhost)
	by isabase.philol.msu.ru (8.9.3/8.9.2) id WAA32570;
	Tue, 28 Mar 2000 22:13:22 +0400 (MSD)
	(envelope-from grg)
Date: Tue, 28 Mar 2000 22:13:22 +0400
From: Grigoriy Strokin <grg@philol.msu.ru>
To: Eric Jacoboni <jaco@titine.fr.eu.org>
Cc: Grigoriy Strokin <grg@philol.msu.ru>, freebsd-stable@FreeBSD.ORG
Subject: Re: New kernel with its ATA drivers damages the filesystem
Message-ID: <20000328221322.A32478@isabase.philol.msu.ru>
References: <20000328195030.A30092@isabase.philol.msu.ru> <87ln33htuc.fsf@titine.fr.eu.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0i
In-Reply-To: <87ln33htuc.fsf@titine.fr.eu.org>; from jaco@titine.fr.eu.org on Tue, Mar 28, 2000 at 07:45:15PM +0200
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Tue, Mar 28, 2000 at 07:45:15PM +0200, Eric Jacoboni wrote:
> Grigoriy Strokin <grg@philol.msu.ru> writes:
> 
> 
> > Mar 28 17:49:07 koch2 /kernel: ed0: device timeout
> > Mar 28 17:49:07 koch2 /kernel: ed0: device timeout
> > Mar 28 17:49:07 koch2 /kernel: ata0: resetting devices .. done
> > Mar 28 17:49:48 koch2 /kernel: ad0: WRITE command timeout - resetting
> > Mar 28 17:49:48 koch2 /kernel: ata0: resetting devices .. done
> 
> > Now I think I don't know where to find the source of the problem.
> 
> Have you tried what the ata manpage suggests ?
> 
> I've had the same problem, it's now fixed with the following line
> added in my /etc/rc.local :
> 
> /sbin/sysctl -w hw.atamodes=pio,pio,pio
> 
> (i've 2 ide disks + an ATAPI cdrom).

Thanks for the suggestion.

I suspect, however, that this timeouts that result in 
incorrect WRITE operations happen very early and
before going multi-user. So I'll rather try
to add them at the very beginning of /etc/rc.

-- 
=== Grigoriy Strokin, Lomonosov University (MGU), Moscow ===
=== contact info: http://isabase.philol.msu.ru/~grg/     ===


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


From owner-freebsd-stable  Tue Mar 28 10:51:20 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from serenity.mcc.ac.uk (serenity.mcc.ac.uk [130.88.200.93])
	by hub.freebsd.org (Postfix) with ESMTP id 6855C37B59F
	for <stable@freebsd.org>; Tue, 28 Mar 2000 10:51:13 -0800 (PST)
	(envelope-from jcm@dogma.freebsd-uk.eu.org)
Received: from dogma.freebsd-uk.eu.org ([130.88.200.97])
	by serenity.mcc.ac.uk with esmtp (Exim 1.92 #3)
	for stable@freebsd.org
	id 12a0kX-000BsO-00; Tue, 28 Mar 2000 19:29:57 +0100
Received: (from jcm@localhost)
	by dogma.freebsd-uk.eu.org (8.9.3/8.9.3) id TAA05925
	for stable@freebsd.org; Tue, 28 Mar 2000 19:29:53 +0100 (BST)
	(envelope-from jcm)
Date: Tue, 28 Mar 2000 19:29:53 +0100
From: J McKitrick <jcm@freebsd-uk.eu.org>
To: stable@freebsd.org
Subject: parallel port zip support on laptops
Message-ID: <20000328192953.A5840@dogma.freebsd-uk.eu.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0.1i
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

I really hate to harp on this, but i've heard people talking about
closing the 3.x tree because 4.0 is so great.  Well, i hate to say it,
but i'm stuck in 3.4 because my zip drive will not work with 4.0.
This is not ijust a bug, but may be a sign of a more serious problem deep in
the newbus code that may come back to haunt us in an unforeseen manner in
the future.

I hope this is considered an important issue, because there are a lot
of laptop users that rely on parallel port zip drives for general
storage and backups.  Parallel port zips (especially the 250 meg
version like mine) are not old technology, and they need to work under
4.0.  So, before we consider closing 3.x, it would make sense to make
sure all of these outstanding issues are resolved.

I realize that zip drives for laptops may pale in importance next to
network features and NFS improvements, and i certainly don't want to
get in the way of progress.  But zip drives are current technology
that needs to be supported for years to come.  Especially if we still
want to be considered cutting edge.  

If there were *any* way for me to fix this myself, i would be glad to.
If i can *help* in any way, i would be glad to.  As it stands, as much
as i hate the thought, i have to spend an hour or two this
week reinstalling 3.4 and reassembling my system from scratch because
my zip drive is important to getting my work done.  And that is a
truly sad reason to have to roll back such an awesome release of a
fantastic OS. 


jm
-- 
--------------------------------------------
Jonathon McKitrick -- jcm@freebsd-uk.eu.org 
The spice must flow....
--------------------------------------------


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


From owner-freebsd-stable  Tue Mar 28 10:52:23 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from jade.chc-chimes.com (jade.chc-chimes.com [216.28.46.6])
	by hub.freebsd.org (Postfix) with ESMTP id 0C90137BBDD
	for <freebsd-stable@freebsd.org>; Tue, 28 Mar 2000 10:52:07 -0800 (PST)
	(envelope-from billf@jade.chc-chimes.com)
Received: by jade.chc-chimes.com (Postfix, from userid 1001)
	id A739A1C5D; Tue, 28 Mar 2000 13:52:05 -0500 (EST)
Date: Tue, 28 Mar 2000 13:52:05 -0500
From: Bill Fumerola <billf@chc-chimes.com>
To: Martin Cracauer <cracauer@cons.org>
Cc: freebsd-stable@freebsd.org
Subject: Re: Let 3.x die ASAP?
Message-ID: <20000328135205.K23367@jade.chc-chimes.com>
References: <20000328113633.A28085@cons.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0i
In-Reply-To: <20000328113633.A28085@cons.org>; from cracauer@cons.org on Tue, Mar 28, 2000 at 11:36:34AM +0200
X-Operating-System: FreeBSD 3.2-RELEASE i386
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Tue, Mar 28, 2000 at 11:36:34AM +0200, Martin Cracauer wrote:

> I assume that I'm not alone here. That many bug-fixing committers will
> not move with 3 machines along the current branches and that 3.5 will
> not be a worthy successor to our previous *.5 releases.

Speaking as someone who sometimes ventures into src/ : I have no intention of 
mergeing down to RELENG_3 unless specifically requested to by PR/e-mail.

-- 
Bill Fumerola - Network Architect
Computer Horizons Corp - CVM
e-mail: billf@chc-chimes.com / billf@FreeBSD.org
Office: 800-252-2421 x128 / Cell: 248-761-7272





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


From owner-freebsd-stable  Tue Mar 28 10:59:12 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from everest.overx.com (everest.overx.com [63.93.29.10])
	by hub.freebsd.org (Postfix) with ESMTP id 2E72E37BEDF
	for <freebsd-stable@freebsd.org>; Tue, 28 Mar 2000 10:59:09 -0800 (PST)
	(envelope-from dayton@overx.com)
Received: from polo.overx.com (polo.overx.com [63.93.29.12])
	by everest.overx.com (Postfix) with ESMTP
	id E69F41FED; Tue, 28 Mar 2000 12:59:07 -0600 (CST)
Received: by polo.overx.com (Postfix, from userid 1001)
	id 599E53F3F; Tue, 28 Mar 2000 12:59:32 -0600 (CST)
From: Soren Dayton <dayton@overx.com>
Reply-To: dayton+freebsd-stable@overx.com
To: Kenneth W Cochran <kwc@world.std.com>
Cc: freebsd-stable@freebsd.org
Subject: Re: Let 3.x die ASAP?
References: <20000328113633.A28085@cons.org> <002301bf98dc$79ed86e0$0100000a@vista1.sdca.home.com> <200003281805.NAA05866@world.std.com>
Date: 28 Mar 2000 12:59:32 -0600
In-Reply-To: Kenneth W Cochran's message of "Tue, 28 Mar 2000 13:05:29 -0500 (EST)"
Message-ID: <86hfdqly3v.fsf@polo.overx.com>
Lines: 23
User-Agent: Gnus/5.070099 (Pterodactyl Gnus v0.99) XEmacs/21.1 (Bryce Canyon)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Kenneth W Cochran <kwc@world.std.com> writes:

> >From owner-freebsd-stable@FreeBSD.ORG  Tue Mar 28 12:42:40 2000
> >From: Soren Dayton <dayton@overx.com>
> >Subject: Re: Let 3.x die ASAP?
> >Date: 28 Mar 2000 11:35:42 -0600
> >
> >Is there a good list of improvements?  In particular details of
> >the NFS improvements?  I tried looking through the CVS logs, but
> >it was not immediately clear to me.  And doing that for the
> >entire source tree doesn't seem very efficient.
> >
> >Thanks,
> >Soren
> 
> Perhaps src/UPDATING?  There is a reverse chronological history
> log there...

errrr.  For _updating_, not generally.  Nor specifically.  The notes
on the website seem like a reasonable approximation of what I'm
looking for.  (except the NFS details).  Thanks everybody!

Soren


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


From owner-freebsd-stable  Tue Mar 28 11:39:12 2000
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 6B6E837BFB5
	for <freebsd-stable@FreeBSD.org>; Tue, 28 Mar 2000 11:37:51 -0800 (PST)
	(envelope-from fjoe@iclub.nsu.ru)
Received: from localhost (fjoe@localhost)
	by iclub.nsu.ru (8.9.3/8.9.3) with ESMTP id CAA71071;
	Wed, 29 Mar 2000 02:37:26 +0700 (NSS)
	(envelope-from fjoe@iclub.nsu.ru)
Date: Wed, 29 Mar 2000 02:37:26 +0700 (NSS)
From: Max Khon <fjoe@iclub.nsu.ru>
To: Gregory Edigaroff <greg@Thing-Fish.Kharkov.NET>
Cc: freebsd-stable@FreeBSD.org
Subject: Re: gcc problems
In-Reply-To: <200003281737.UAA01260@Thing-Fish.Kharkov.NET>
Message-ID: <Pine.BSF.4.21.0003290233160.70800-100000@iclub.nsu.ru>
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 Tue, 28 Mar 2000, Gregory Edigaroff wrote:

> Hello!
> It seems like gcc-2.95.2 has a leak, which could freeze the compilation.
> I experienced this while compile MySQL-3.22.32.
> It hangs up on:
> c++ -DMYSQL_SERV-DDATADIR="\"/usr/local/var\"" LT_MYSQL_HOME="\"-DSHAREDIR="\"/u
> sr/local/share/m-I./../regex                    -I. -I../include -I.. -I.    -D_
> LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -O3 -DDBUG_OFF   -
> fno-implicit-templates -DMYSQLD_NET_RETRY_COUNT=1000000  -c sql_yacc.cc

[...]

> What can I do?

look at /usr/ports/databases/mysql322-server/patches/patch-aq

/fjoe



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


From owner-freebsd-stable  Tue Mar 28 12: 9:54 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from freeway.dcfinc.com (cx74889-a.phnx3.az.home.com [24.1.193.157])
	by hub.freebsd.org (Postfix) with ESMTP id 5A33637B9AC
	for <freebsd-stable@FreeBSD.ORG>; Tue, 28 Mar 2000 12:09:47 -0800 (PST)
	(envelope-from chad@freeway.dcfinc.com)
Received: (from chad@localhost)
	by freeway.dcfinc.com (8.8.8/8.8.8) id NAA13130;
	Tue, 28 Mar 2000 13:09:30 -0700 (MST)
	(envelope-from chad)
From: "Chad R. Larson" <chad@DCFinc.com>
Message-Id: <200003282009.NAA13130@freeway.dcfinc.com>
Subject: Re: 4.0-STABLE dhcp conflicts.
In-Reply-To: <200003280440.UAA07738@cwsys.cwsent.com> from Cy Schubert - ITSD Open Systems Group at "Mar 27, 0 08:40:48 pm"
To: Cy.Schubert@uumail.gov.bc.ca
Date: Tue, 28 Mar 2000 13:09:30 -0700 (MST)
Cc: dgilbert@velocet.ca, freebsd-stable@FreeBSD.ORG
Reply-To: chad@DCFinc.com
X-Mailer: ELM [version 2.4ME+ PL40 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

As I recall, Cy Schubert - ITSD Open Systems Group wrote:
> I suspect that the dhcp server set the interface to promiscuous mode
> so it can listen for broadcasts.  Tcpdump sets up an interface for
> promiscuous opertion and when you exit tcpdump it returns it to
> non-promiscuous operation.  Killing and restarting your dhcp server
> after exiting tcpdump should solve your problem, as it will set the
> interface up for promiscuous operation again.

Isn't that what the '-p' switch is for?

	-crl
--
Chad R. Larson (CRL15)   602-953-1392   Brother, can you paradigm?
chad@dcfinc.com         chad@larsons.org          larson1@home.net   
DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207


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


From owner-freebsd-stable  Tue Mar 28 12:14:23 2000
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 0999537B61B; Tue, 28 Mar 2000 12:14:15 -0800 (PST)
	(envelope-from dwmalone@maths.tcd.ie)
Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP
          id <aa33728@salmon>; 28 Mar 2000 21:14:12 +0100 (BST)
Date: Tue, 28 Mar 2000 21:14:12 +0100
From: David Malone <dwmalone@maths.tcd.ie>
To: Jeff Hamilton <hjeffrey@hotmail.com>
Cc: freebsd-questions@freebsd.org, freebsd-stable@freebsd.org
Subject: Re: /etc/hosts.allow
Message-ID: <20000328211412.A4625@walton.maths.tcd.ie>
References: <20000328174744.60658.qmail@hotmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0.1i
In-Reply-To: <20000328174744.60658.qmail@hotmail.com>; from hjeffrey@hotmail.com on Tue, Mar 28, 2000 at 09:47:43AM -0800
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Tue, Mar 28, 2000 at 09:47:43AM -0800, Jeff Hamilton wrote:

> Mar 28 17:37:54 hostname portmap[154]: warning: /etc/hosts.allow, line 16: 
> twist_option: dup: Bad file descriptor
> 
> What am I doing wrong, or is this message expected?

My guess is that the portmapper is getting a tcp connection, which the
remote end closes almost immediately. Then when the wrapping code goes
to to dup the discriptor which is supposed to be connected it finds it
is unconnected.

I don't think you need to worry about it anyway.

	David.


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


From owner-freebsd-stable  Tue Mar 28 12:23:12 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from kot.ne.mediaone.net (kot.ne.mediaone.net [24.218.15.190])
	by hub.freebsd.org (Postfix) with ESMTP id A092D37C05B
	for <freebsd-stable@FreeBSD.ORG>; Tue, 28 Mar 2000 12:23:08 -0800 (PST)
	(envelope-from mi@kot.ne.mediaone.net)
Received: from rtfm.newton (root@rtfm.newton [10.10.0.1])
	by kot.ne.mediaone.net (8.9.3/8.9.1) with ESMTP id PAA70067;
	Tue, 28 Mar 2000 15:23:06 -0500 (EST)
From: Mikhail Teterin <mi@kot.ne.mediaone.net>
X-Relay-IP: 10.10.0.1
Received: (from mi@localhost)
	by rtfm.newton (8.9.3/8.9.3) id PAA01992;
	Tue, 28 Mar 2000 15:23:06 -0500 (EST)
	(envelope-from mi@kot.ne.mediaone.net)
Message-Id: <200003282023.PAA01992@rtfm.newton>
Subject: Re: gcc problems
In-Reply-To: <Pine.BSF.4.21.0003290233160.70800-100000@iclub.nsu.ru> from Max
 Khon at "Mar 29, 2000 02:37:26 am"
To: Max Khon <fjoe@iclub.nsu.ru>
Date: Tue, 28 Mar 2000 15:23:06 -0500 (EST)
Cc: Gregory Edigaroff <greg@Thing-Fish.Kharkov.NET>,
	freebsd-stable@FreeBSD.ORG
X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w<gv/&E-lL7twZCT8B~/PA4|\t$ti+22K">
	 hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli"<kcG^EOVih
	 y+z3/UR{6SCQ
X-Mailer: ELM [version 2.4ME+ PL60 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Max Khon once stated:

=[...]
=
=> What can I do?
=
=look at /usr/ports/databases/mysql322-server/patches/patch-aq

But is not  this, where the optimization can be  quite desirable? Is not
this the query parsing code? If it  identifies a bug in CXX it should be
this should only be considered  a workaround. If the compiler eventually
succeeds  -- just  brace-up and  wait :)  May be,  add a  -nopipe option
explicitly.

	-mi

+++ sql/Makefile.in     Wed Jan  5 20:28:17 2000
@@ -317,6 +317,10 @@
        else :; fi
 sql_yacc.hh: sql_yacc.cc

+# gcc takes a lot of memory and cpu time if it compiles sql_yacc.cc with -O
+sql_yacc.o: sql_yacc.cc
+	$(CXXCOMPILE) -O0 -c $<
+



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


From owner-freebsd-stable  Tue Mar 28 12:31:13 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from rhenium.btinternet.com (rhenium.btinternet.com [194.73.73.93])
	by hub.freebsd.org (Postfix) with ESMTP id 1FE9F37B617
	for <stable@freebsd.org>; Tue, 28 Mar 2000 12:31:07 -0800 (PST)
	(envelope-from mark@ukug.uk.freebsd.org)
Received: from [213.1.108.115] (helo=parish.my.domain)
	by rhenium.btinternet.com with esmtp (Exim 2.05 #1)
	id 12a2db-0005jI-00; Tue, 28 Mar 2000 21:30:56 +0100
Received: (from mark@localhost)
	by parish.my.domain (8.9.3/8.9.3) id VAA00834;
	Tue, 28 Mar 2000 21:30:52 +0100 (BST)
	(envelope-from mark)
Date: Tue, 28 Mar 2000 21:30:52 +0100
From: Mark Ovens <mark@ukug.uk.freebsd.org>
To: Pieter Westland <pieterw@euronet.nl>
Cc: stable@FreeBSD.ORG
Subject: Re: HEADS UP: 3.x -> 4.0-STABLE upgrade instructions
Message-ID: <20000328213052.B234@parish>
References: <20000315174557.C40984@relay.ucb.crimea.ua> <200003151903.MAA88473@harmony.village.org> <005701bf8eb3$b02b2150$a44b8486@jking> <20000315210705.A244@parish> <20000328150714.A23199@support.euronet.nl>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0.1i
In-Reply-To: <20000328150714.A23199@support.euronet.nl>; from pieterw@euronet.nl on Tue, Mar 28, 2000 at 03:07:14PM +0200
Organization: Total lack of
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Tue, Mar 28, 2000 at 03:07:14PM +0200, Pieter Westland wrote:
> On Wed, Mar 15, 2000 at 09:07:05PM +0000, Mark Ovens wrote:
> [snip]
> > This message appeared 166 times during ``make buildworld'':
> > 	/usr/libexec/ld-elf.so.1: Shared object "libc.so.4" not found
> > It also caused config(8) on the new kernel to fail, but
> > 	ldconfig -R /usr/obj/usr/src/lib/libc
> > cured that.
> 
> 
> Hi there,
> 
> A few hours ago I moved my machine from 3.4-STABLE to 4.0 . I also got
> that errormessages about libc.so.4 during make buildworld. A ldconfig, as
> mentioned by Mark, solved the problem. Will this command be included in
> the make buildworld-process?
> 

It goes away once you've done ``make installworld'' libc.so.3 was in
3.x but 4.x uses libc.so.4 and while you're doing ``make buildworld''
and building a new kernel you've got a sort of hybrid system. I maybe
wrong here, but ISTR recall that the new compiler (2.95) gets built
with the old compiler and then immediately re-builds itself using
itself :-/

> The rest of the upgrade went almost fine. I got into trouble when trying to 
> do a 'make -j4 installworld', but that was because staring at the console had
> tired me... It caused the machine to be unable to find some files.
> 
> The other problem is that X does not want to let me log in; getting the 
> following message in the log when trying to log in (starting xdm works,
> but after entering login en password it displays a 'Incorrect
> password'-message and logs):
> 
> Mar 28 09:07:50 dustpuppy -:0: unable to dlopen(/usr/lib/pam_unix.so)
> Mar 28 09:07:50 dustpuppy -:0: [dlerror: /usr/lib/libutil.so.3: Undefined
> symbol "freeaddrinfo"]
> Mar 28 09:07:50 dustpuppy -:0: adding faulty module: /usr/lib/pam_unix.so
> 

Not exactly the same errors I saw, but it looks as if you built XFree
with PAM support. When you re-build XFree answer 'no' to the PAM
question.

HTH.


> At this moment I'm recompiling XFree86 (3.3.6), I hope the problem will be
> solved after this.
> 
> Pieter
> --
> Finagle's Creed:
> 	Science is true.  Don't be misled by facts.

-- 
Seminars, n.:
       From "semi" and "arse", hence, any half-assed discussion.
________________________________________________________________
      FreeBSD - The Power To Serve http://www.freebsd.org
      My Webpage http://ukug.uk.freebsd.org/~mark/
mailto:mark@ukug.uk.freebsd.org             http://www.radan.com



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


From owner-freebsd-stable  Tue Mar 28 12:32: 8 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from netcom.com (netcom4.netcom.com [199.183.9.104])
	by hub.freebsd.org (Postfix) with ESMTP id 1A33F37BB45
	for <freebsd-stable@freebsd.org>; Tue, 28 Mar 2000 12:31:56 -0800 (PST)
	(envelope-from stanb@netcom.com)
Received: (from stanb@localhost)
	by netcom.com (8.9.3/8.9.3) id MAA02766
	for freebsd-stable@freebsd.org; Tue, 28 Mar 2000 12:26:08 -0800 (PST)
From: Stan Brown <stanb@netcom.com>
Message-Id: <200003282026.MAA02766@netcom.com>
Subject: Still can't get 4.0 make world to work :-(
To: freebsd-stable@freebsd.org (FreeBSD Stable List)
Date: Tue, 28 Mar 2000 15:26:07 -0500 (EST)
X-Mailer: ELM [version 2.5 PL3]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

	I posted about this yesterday. But I still have not made it work, so I
	am sending more details.

	I installed a brand new 4.0 machine from the ftp site this weekend.
	Built the cvsup port, asked for cvsup tags, and cvsuped using the
	following cvsut_files


# $Id: ports-supfile,v 1.14.2.1 1999/02/11 20:14:51 jdp Exp $
#
# This file contains all of the "CVSup collections" that make up the
# FreeBSD-current ports collection.
#
# CVSup (CVS Update Protocol) allows you to download the latest CVS
# tree (or any branch of development therefrom) to your system easily
# and efficiently (far more so than with sup, which CVSup is aimed
# at replacing).  If you're running CVSup interactively, and are
# currently using an X display server, you should run CVSup as follows
# to keep your CVS tree up-to-date:
#
#	cvsup ports-supfile
#
# If not running X, or invoking cvsup from a non-interactive script, then
# run it as follows:
#
#	cvsup -g -L 2 ports-supfile
#
# You may wish to change some of the settings in this file to better
# suit your system:
#
# host=CHANGE_THIS.FreeBSD.org
#		This specifies the server host which will supply the
#		file updates.  You must change it to one of the CVSup
#		mirror sites listed in the FreeBSD Handbook at
#		http://www.freebsd.org/handbook/mirrors.html.
#		You can	override this setting on the command line
#		with cvsup's "-h host" option.
#
# base=/usr
#		This specifies the root where CVSup will store information
#		about the collections you have transferred to your system.
#		A setting of "/usr" will generate this information in
#		/usr/sup.  Even if you are CVSupping a large number of
#		collections, you will be hard pressed to generate more than
#		~1MB of data in this directory.  You can override the
#		"base" setting on the command line with cvsup's "-b base"
#		option.  This directory must exist in order to run CVSup.
#
# prefix=/usr
#		This specifies where to place the requested files.  A
#		setting of "/usr" will place all of the files requested
#		in "/usr/ports" (e.g., "/usr/ports/devel", "/usr/ports/lang").
#		The prefix directory must exist in order to run CVSup.

# Defaults that apply to all the collections
#
# IMPORTANT: Change the next line to use one of the CVSup mirror sites
# listed at http://www.freebsd.org/handbook/mirrors.html.
*default host=cvsup.FreeBSD.org
*default base=/usr
*default prefix=/usr
*default release=cvs tag=.
*default delete use-rel-suffix

# If your network link is a T1 or faster, comment out the following line.
*default compress

## Ports Collection.
#
# The easiest way to get the ports tree is to use the "ports-all"
# mega-collection.  It includes all of the individual "ports-*"
# collections,
# ports-all

# These are the individual collections that make up "ports-all".  If you
# use these, be sure to comment out "ports-all" above.
ports-archivers
ports-astro
ports-audio
ports-base
ports-benchmarks
ports-biology
ports-cad
#ports-chinese
ports-comms
ports-converters
ports-databases
ports-deskutils
ports-devel
ports-editors
ports-emulators
ports-games
#ports-german
ports-graphics
#ports-japanese
#ports-korean
ports-lang
ports-mail
ports-math
ports-mbone
ports-misc
ports-net
ports-news
ports-plan9
ports-print
#ports-russian
ports-security
ports-shells
ports-sysutils
ports-textproc
#ports-vietnamese
ports-www
ports-x11
ports-x11-clocks
ports-x11-fm
ports-x11-fonts
ports-x11-toolkits
ports-x11-wm

# $Id: secure-stable-supfile,v 1.9.2.2 1999/02/11 20:14:51 jdp Exp $
#
# This file contains all of the "CVSup collections" that make up the
# source tree of the FreeBSD-stable international secure distribution.
# If you are outside the USA or Canada, use this file.
#
# CVSup (CVS Update Protocol) allows you to download the latest CVS
# tree (or any branch of development therefrom) to your system easily
# and efficiently (far more so than with sup, which CVSup is aimed
# at replacing).  If you're running CVSup interactively, and are
# currently using an X display server, you should run CVSup as follows
# to keep your CVS tree up-to-date:
#
#	cvsup secure-stable-supfile
#
# If not running X, or invoking cvsup from a non-interactive script, then
# run it as follows:
#
#	cvsup -g -L 2 secure-stable-supfile
#
# You may wish to change some of the settings in this file to better
# suit your system:
#
# base=/usr
#		This specifies the root where CVSup will store information
#		about the collections you have transferred to your system.
#		A setting of "/usr" will generate this information in
#		/usr/sup.  Even if you are CVSupping a large number of
#		collections, you will be hard pressed to generate more than
#		~1MB of data in this directory.  You can override the
#		"base" setting on the command line with cvsup's "-b base"
#		option.  This directory must exist in order to run CVSup.
#
# prefix=/usr
#		This specifies where to place the requested files.  A
#		setting of "/usr" will place all of the files requested
#		in "/usr/src" (i.e., "/usr/src/eBones" and "/usr/src/secure").
#		The prefix directory must exist in order to run CVSup.

# Defaults that apply to all the collections
*default host=cvsup.FreeBSD.org
*default base=/usr
*default prefix=/usr
# The following line is for 3-stable.  If you want 2.2-stable, change
# "RELENG_3" to "RELENG_2_2".
*default release=cvs tag=RELENG_4
*default delete use-rel-suffix

# If your network link is a T1 or faster, comment out the following line.
*default compress

## The international secure collections.
src-all


# $Id: secure-stable-supfile,v 1.9.2.2 1999/02/11 20:14:51 jdp Exp $
#
# This file contains all of the "CVSup collections" that make up the
# source tree of the FreeBSD-stable international secure distribution.
# If you are outside the USA or Canada, use this file.
#
# CVSup (CVS Update Protocol) allows you to download the latest CVS
# tree (or any branch of development therefrom) to your system easily
# and efficiently (far more so than with sup, which CVSup is aimed
# at replacing).  If you're running CVSup interactively, and are
# currently using an X display server, you should run CVSup as follows
# to keep your CVS tree up-to-date:
#
#	cvsup secure-stable-supfile
#
# If not running X, or invoking cvsup from a non-interactive script, then
# run it as follows:
#
#	cvsup -g -L 2 secure-stable-supfile
#
# You may wish to change some of the settings in this file to better
# suit your system:
#
# base=/usr
#		This specifies the root where CVSup will store information
#		about the collections you have transferred to your system.
#		A setting of "/usr" will generate this information in
#		/usr/sup.  Even if you are CVSupping a large number of
#		collections, you will be hard pressed to generate more than
#		~1MB of data in this directory.  You can override the
#		"base" setting on the command line with cvsup's "-b base"
#		option.  This directory must exist in order to run CVSup.
#
# prefix=/usr
#		This specifies where to place the requested files.  A
#		setting of "/usr" will place all of the files requested
#		in "/usr/src" (i.e., "/usr/src/eBones" and "/usr/src/secure").
#		The prefix directory must exist in order to run CVSup.

# Defaults that apply to all the collections
*default host=cvsup.FreeBSD.org
*default base=/usr
*default prefix=/usr
# The following line is for 3-stable.  If you want 2.2-stable, change
# "RELENG_3" to "RELENG_2_2".
*default release=cvs tag=RELENG_3
*default delete use-rel-suffix

# If your network link is a T1 or faster, comment out the following line.
*default compress

## The international secure collections.
src-crypto
src-eBones
src-secure


	The resultant make world dies as follows:

rm -f .depend
mkdep -f .depend -a    -DHAVE_DES -I/usr/obj/usr/src/i386/usr/include  /usr/src/
usr.sbin/ppp/acf.c /usr/src/usr.sbin/ppp/arp.c /usr/src/usr.sbin/ppp/async.c /us
r/src/usr.sbin/ppp/auth.c /usr/src/usr.sbin/ppp/bundle.c /usr/src/usr.sbin/ppp/c
bcp.c /usr/src/usr.sbin/ppp/ccp.c /usr/src/usr.sbin/ppp/chap.c /usr/src/usr.sbin
/ppp/chat.c /usr/src/usr.sbin/ppp/command.c /usr/src/usr.sbin/ppp/datalink.c /us
r/src/usr.sbin/ppp/deflate.c /usr/src/usr.sbin/ppp/defs.c /usr/src/usr.sbin/ppp/
exec.c /usr/src/usr.sbin/ppp/filter.c /usr/src/usr.sbin/ppp/fsm.c /usr/src/usr.s
bin/ppp/hdlc.c /usr/src/usr.sbin/ppp/id.c /usr/src/usr.sbin/ppp/iface.c /usr/src
/usr.sbin/ppp/ip.c /usr/src/usr.sbin/ppp/ipcp.c /usr/src/usr.sbin/ppp/iplist.c /
usr/src/usr.sbin/ppp/lcp.c /usr/src/usr.sbin/ppp/link.c /usr/src/usr.sbin/ppp/lo
g.c /usr/src/usr.sbin/ppp/lqr.c /usr/src/usr.sbin/ppp/main.c /usr/src/usr.sbin/p
pp/mbuf.c /usr/src/usr.sbin/ppp/mp.c /usr/src/usr.sbin/ppp/pap.c /usr/src/usr.sb
in/ppp/physical.c /usr/src/usr.sbin/ppp/pred.c /usr/src/usr.sbin/ppp/probe.c /us
r/src/usr.sbin/ppp/prompt.c /usr/src/usr.sbin/ppp/proto.c /usr/src/usr.sbin/ppp/
route.c /usr/src/usr.sbin/ppp/server.c /usr/src/usr.sbin/ppp/sig.c /usr/src/usr.
sbin/ppp/slcompress.c /usr/src/usr.sbin/ppp/sync.c /usr/src/usr.sbin/ppp/systems
.c /usr/src/usr.sbin/ppp/tcp.c /usr/src/usr.sbin/ppp/throughput.c /usr/src/usr.s
bin/ppp/timer.c /usr/src/usr.sbin/ppp/tty.c /usr/src/usr.sbin/ppp/tun.c /usr/src
/usr.sbin/ppp/udp.c /usr/src/usr.sbin/ppp/vjcomp.c /usr/src/usr.sbin/ppp/nat_cmd
.c /usr/src/usr.sbin/ppp/chap_ms.c /usr/src/usr.sbin/ppp/radius.c /usr/src/usr.s
bin/ppp/i4b.c /usr/src/usr.sbin/ppp/ether.c
/usr/src/usr.sbin/ppp/chap_ms.c:30: openssl/des.h: No such file or directory
mkdep: compile failed
*** Error code 1

Stop in /usr/src/usr.sbin/ppp.
*** Error code 1

Stop in /usr/src/usr.sbin.
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.
test# 

	I am thinking I may have a problem with the security related cvsup
	tags. Does this make senes? If so what tags should I be using?

	I have re cvsuped, with no sucess. If anyone thinks I should delete
	somethign before cvsup'ing. please sugest what.

	I am trying to solve a problem with the 3c509 driver from 3.4 with
	this, and I really need to get to a point where I can test to see if
	this bug is fixed.

	Thanks for the help.

-- 
Stan Brown     stanb@netcom.com                                    404-996-6955
Factory Automation Systems
Atlanta Ga.
-- 
Look, look, see Windows 95.  Buy, lemmings, buy!   
Pay no attention to that cliff ahead...            Henry Spencer
(c) 1998 Stan Brown.  Redistribution via the Microsoft Network is prohibited.


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


From owner-freebsd-stable  Tue Mar 28 13: 7: 3 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from mail.hcisp.net (Stargate.hcisp.net [208.60.89.18])
	by hub.freebsd.org (Postfix) with SMTP id 587F037B59F
	for <freebsd-stable@FreeBSD.ORG>; Tue, 28 Mar 2000 13:07:00 -0800 (PST)
	(envelope-from tim@mysql.com)
Received: (qmail 1292 invoked from network); 28 Mar 2000 21:12:53 -0000
Received: from modem10.hcisp.net (HELO threads.polyesthetic.msg) (208.60.89.76)
  by stargate.hcisp.net with SMTP; 28 Mar 2000 21:12:53 -0000
Received: (qmail 3326 invoked by uid 1001); 28 Mar 2000 21:04:43 -0000
From: "Thimble Smith" <tim@mysql.com>
Date: Tue, 28 Mar 2000 16:04:42 -0500
To: Mikhail Teterin <mi@kot.ne.mediaone.net>
Cc: freebsd-stable@FreeBSD.ORG
Subject: Re: gcc problems
Message-ID: <20000328160442.S1135@threads.polyesthetic.msg>
References: <Pine.BSF.4.21.0003290233160.70800-100000@iclub.nsu.ru> <200003282023.PAA01992@rtfm.newton>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0.1i
In-Reply-To: <200003282023.PAA01992@rtfm.newton>; from mi@kot.ne.mediaone.net on Tue, Mar 28, 2000 at 03:23:06PM -0500
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Tue, Mar 28, 2000 at 03:23:06PM -0500, Mikhail Teterin wrote:

[ sql_yacc.cc has to be compiled with -O0 ]

>But is not  this, where the optimization can be  quite desirable? Is not
>this the query parsing code?

You can do it with -O -fno-inline.  Just add some more swap space
and then go for a walk while it compiles.  It's spring - nice
weather, right?

Tim
-- 
Tim Smith   < tim@mysql.com >  :MySQL Development Team:  Boone, NC  USA.


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


From owner-freebsd-stable  Tue Mar 28 13:22: 3 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from mailhub.unibe.ch (mailhub.unibe.ch [130.92.254.109])
	by hub.freebsd.org (Postfix) with ESMTP id 163C537B714
	for <stable@FreeBSD.ORG>; Tue, 28 Mar 2000 13:21:49 -0800 (PST)
	(envelope-from roth@iamexwi.unibe.ch)
Received: from iamexwi.unibe.ch (haegar.unibe.ch [130.92.71.10])
 by mailhub.unibe.ch (PMDF V5.2-32 #42480)
 with ESMTP id <0FS500BBIHVVQ6@mailhub.unibe.ch> for stable@FreeBSD.ORG; Tue,
 28 Mar 2000 23:19:07 +0200 (MET DST)
Received: from giger.unibe.ch (giger [130.92.63.40])
	by iamexwi.unibe.ch (8.8.8+Sun/8.8.8) with ESMTP id XAA19740; Tue,
 28 Mar 2000 23:21:49 +0200 (MET DST)
Received: from localhost (roth@localhost)	by giger.unibe.ch (8.9.1b+Sun/8.9.1)
 with ESMTP id XAA27656; Tue, 28 Mar 2000 23:21:46 +0200 (MET DST)
Date: Tue, 28 Mar 2000 23:21:46 +0200 (MET DST)
From: Tobias Roth <roth@iamexwi.unibe.ch>
Subject: Re: HEADS UP: 3.x -> 4.0-STABLE upgrade instructions
In-reply-to: <20000328213052.B234@parish>
To: Mark Ovens <mark@dogma.freebsd-uk.eu.org>
Cc: Pieter Westland <pieterw@euronet.nl>, stable@FreeBSD.ORG
Message-id: <Pine.GSO.4.10.10003282318010.27642-100000@giger>
MIME-version: 1.0
Content-type: TEXT/PLAIN; charset=US-ASCII
Content-transfer-encoding: 7BIT
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


> > > This message appeared 166 times during ``make buildworld'':
> > > 	/usr/libexec/ld-elf.so.1: Shared object "libc.so.4" not found
> > > It also caused config(8) on the new kernel to fail, but
> > > 	ldconfig -R /usr/obj/usr/src/lib/libc
> > > cured that.
> 
> It goes away once you've done ``make installworld'' libc.so.3 was in
> 3.x but 4.x uses libc.so.4 and while you're doing ``make buildworld''
> and building a new kernel you've got a sort of hybrid system. I maybe
> wrong here, but ISTR recall that the new compiler (2.95) gets built
> with the old compiler and then immediately re-builds itself using
> itself :-/

So, does that mean I can skip the ldconfig, just do make buildworld and
make installworld as I always did and everything will work?
Or do I *HAVE* to to the ldconfig?

thx, tobe



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


From owner-freebsd-stable  Tue Mar 28 13:24:23 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from hotmail.com (f200.law8.hotmail.com [216.33.241.200])
	by hub.freebsd.org (Postfix) with SMTP id E010237B914
	for <freebsd-stable@freebsd.org>; Tue, 28 Mar 2000 13:24:19 -0800 (PST)
	(envelope-from hjeffrey@hotmail.com)
Received: (qmail 44270 invoked by uid 0); 28 Mar 2000 21:24:18 -0000
Message-ID: <20000328212418.44269.qmail@hotmail.com>
Received: from 130.11.112.22 by www.hotmail.com with HTTP;
	Tue, 28 Mar 2000 13:24:18 PST
X-Originating-IP: [130.11.112.22]
From: "Jeff Hamilton" <hjeffrey@hotmail.com>
To: dwmalone@maths.tcd.ie
Cc: freebsd-questions@freebsd.org, freebsd-stable@freebsd.org
Subject: Re: /etc/hosts.allow
Date: Tue, 28 Mar 2000 13:24:18 PST
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

>From: David Malone <dwmalone@maths.tcd.ie>
>To: Jeff Hamilton <hjeffrey@hotmail.com>
>CC: freebsd-questions@freebsd.org, freebsd-stable@freebsd.org
>Subject: Re: /etc/hosts.allow
>Date: Tue, 28 Mar 2000 21:14:12 +0100
>
>On Tue, Mar 28, 2000 at 09:47:43AM -0800, Jeff Hamilton wrote:
>
> > Mar 28 17:37:54 hostname portmap[154]: warning: /etc/hosts.allow, line 
>16:
> > twist_option: dup: Bad file descriptor
> >
> > What am I doing wrong, or is this message expected?
>
>My guess is that the portmapper is getting a tcp connection, which the
>remote end closes almost immediately. Then when the wrapping code goes
>to to dup the discriptor which is supposed to be connected it finds it
>is unconnected.

Could this possibly be an indicator of a port scan or other exploit attempt? 
  Is there anyway to trace the IP address that originated the connection?

Thanks.

Jeff
hjeffrey@hotmail.com
______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com



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


From owner-freebsd-stable  Tue Mar 28 13:56:51 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from aragorn.neomedia.it (aragorn.neomedia.it [195.103.207.6])
	by hub.freebsd.org (Postfix) with ESMTP id 3A75437BFBD
	for <freebsd-stable@FreeBSD.ORG>; Tue, 28 Mar 2000 13:56:47 -0800 (PST)
	(envelope-from bartequi@neomedia.it)
Received: from bartequi.ottodomain.org (ppp4-pa5.neomedia.it [195.103.207.116])
	by aragorn.neomedia.it (8.9.3/8.9.3) with SMTP id XAA22569;
	Tue, 28 Mar 2000 23:55:05 +0200 (CEST)
From: Salvo Bartolotta <bartequi@neomedia.it>
Date: Tue, 28 Mar 2000 22:56:59 GMT
Message-ID: <20000328.22565900@bartequi.ottodomain.org>
Subject: Re: HEADS UP: 3.x -> 4.0-STABLE upgrade instructions
To: Pieter Westland <pieterw@euronet.nl>, freebsd-stable@FreeBSD.ORG
In-Reply-To: <20000328150714.A23199@support.euronet.nl>
References: <20000315174557.C40984@relay.ucb.crimea.ua> <200003151903.MAA88473@harmony.village.org> <005701bf8eb3$b02b2150$a44b8486@jking> <20000315210705.A244@parish> <20000328150714.A23199@support.euronet.nl>
X-Mailer: SuperCalifragilis
X-Priority: 3 (Normal)
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

<snip>

> The other problem is that X does not want to let me log in; getting=20
the
> following message in the log when trying to log in (starting xdm=20
works,
> but after entering login en password it displays a 'Incorrect
> password'-message and logs):

> Mar 28 09:07:50 dustpuppy -:0: unable to dlopen(/usr/lib/pam_unix.so)
> Mar 28 09:07:50 dustpuppy -:0: [dlerror: /usr/lib/libutil.so.3:=20
Undefined
> symbol "freeaddrinfo"]
> Mar 28 09:07:50 dustpuppy -:0: adding faulty module:=20
/usr/lib/pam_unix.so

> At this moment I'm recompiling XFree86 (3.3.6), I hope the problem=20
will be
> solved after this.

> Pieter


Dear Pieter Westland,

**if** your config files (e.g. pam.conf) are all right, recompiling=20
XFree86  should make it work again. I did exactly so when I upgraded to =

4-(then)CURRENT. I shall upgrade to 4-STABLE ASAP <pant,pant> :-)

Best regards,
Salvo
=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 28 14: 5:57 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from smtp1.medianstrip.net (host30.thirteen.net [206.113.38.30])
	by hub.freebsd.org (Postfix) with ESMTP id A7D3637BE60
	for <stable@freebsd.org>; Tue, 28 Mar 2000 14:05:54 -0800 (PST)
	(envelope-from mike@medianstrip.net)
Received: by smtp1.medianstrip.net (Postfix, from userid 1000)
	id 59DCB59A4; Tue, 28 Mar 2000 17:05:41 -0500 (EST)
Date: Tue, 28 Mar 2000 17:05:41 -0500
From: mike ryan <mikeryan@post.harvard.edu>
To: stable@freebsd.org
Subject: dhclient failure due to timeout limit on select
Message-ID: <20000328170541.A25874@medianstrip.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0i
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

observed on 4-stable, though this appears to be equally relevant on
3-stable and current:

select() returns EINVAL on timeouts of more than 100 million seconds
due to an apparently arbitrary limit in itimerfix().  this causes
dhclient to bail after obtaining a lease exceeding that limit.  my
rcn cable modem service, for example, sets a renewal time of
1073741823 seconds.  while this pretty much means "don't bother
renewing", it'd still be nice if dhclient didn't give up.

is there a reason why there needs to be a 100000000 second limit in
select and/or itimerfix?


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


From owner-freebsd-stable  Tue Mar 28 14:17: 9 2000
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 B80EF37B7DC; Tue, 28 Mar 2000 14:17:01 -0800 (PST)
	(envelope-from dwmalone@maths.tcd.ie)
Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP
          id <aa41773@salmon>; 28 Mar 2000 23:16:59 +0100 (BST)
Date: Tue, 28 Mar 2000 23:16:57 +0100
From: David Malone <dwmalone@maths.tcd.ie>
To: Jeff Hamilton <hjeffrey@hotmail.com>
Cc: freebsd-questions@freebsd.org, freebsd-stable@freebsd.org
Subject: Re: /etc/hosts.allow
Message-ID: <20000328231657.A9744@walton.maths.tcd.ie>
References: <20000328212418.44269.qmail@hotmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0.1i
In-Reply-To: <20000328212418.44269.qmail@hotmail.com>; from hjeffrey@hotmail.com on Tue, Mar 28, 2000 at 01:24:18PM -0800
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Tue, Mar 28, 2000 at 01:24:18PM -0800, Jeff Hamilton wrote:

> >My guess is that the portmapper is getting a tcp connection, which the
> >remote end closes almost immediately. Then when the wrapping code goes
> >to to dup the discriptor which is supposed to be connected it finds it
> >is unconnected.
> 
> Could this possibly be an indicator of a port scan or other exploit attempt? 
>   Is there anyway to trace the IP address that originated the connection?

If my guess was right, there is a good chance it could be a portscan.
Tracing the IP address is probably a bit harder. I'll experiment at
home and see if I can reproduce this.

	David.


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


From owner-freebsd-stable  Tue Mar 28 14:31:41 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from picalon.gun.de (picalon.gun.de [192.109.159.1])
	by hub.freebsd.org (Postfix) with ESMTP id 21ADC37BF6D
	for <stable@freebsd.org>; Tue, 28 Mar 2000 14:31:24 -0800 (PST)
	(envelope-from andreas@klemm.gtn.com)
Received: (from uucp@localhost)
	by picalon.gun.de (8.9.3/8.9.3) id AAA24006;
	Wed, 29 Mar 2000 00:30:13 +0200 (MET DST)
>Received: (from andreas@localhost)
	by klemm.gtn.com (8.9.3/8.9.3) id IAA20476;
	Tue, 28 Mar 2000 08:17:46 +0200 (CEST)
	(envelope-from andreas)
Date: Tue, 28 Mar 2000 08:17:46 +0200
From: Andreas Klemm <andreas@klemm.gtn.com>
To: Ben Smithurst <ben@scientia.demon.co.uk>
Cc: andreas@klemm.gtn.com, andreas.klemm.ak@bayer-ag.de,
	stable@freebsd.org
Subject: Re: can I mount a Linux ext2fs from an extended partition ?
Message-ID: <20000328081746.A20458@titan.klemm.gtn.com>
References: <20000327233341.A98997@titan.klemm.gtn.com> <20000327234553.A86036@strontium.scientia.demon.co.uk>
Mime-Version: 1.0
X-Mailer: Mutt 1.0.1i
In-Reply-To: <20000327234553.A86036@strontium.scientia.demon.co.uk>; from ben@scientia.demon.co.uk on Mon, Mar 27, 2000 at 11:45:53PM +0100
X-Operating-System: FreeBSD 4.0-STABLE SMP
X-Disclaimer: A free society is one where it is safe to be unpopular
Content-Type: text/plain; charset=us-ascii
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Mon, Mar 27, 2000 at 11:45:53PM +0100, Ben Smithurst wrote:
> Andreas Klemm wrote:
> 
> > Am migrating a customer from Linux to Unix.
> > His user data are on an extended partition.
> > How can I mount it under FreeBSD 4.0 ?
> 
> I think you can access extended partitions as slices 5-8, if you mean
> what I think you mean.

Oh, that would be fine ! Yes I think that's what I mean ;-)

-- 
Andreas Klemm                               http://people.FreeBSD.ORG/~andreas
                                     http://www.freebsd.org/~fsmp/SMP/SMP.html
                                   powered by Symmetric MultiProcessor FreeBSD
New APSFILTER 520 and songs from our band - http://people.freebsd.org/~andreas



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


From owner-freebsd-stable  Tue Mar 28 14:45:19 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from rover.village.org (rover.village.org [204.144.255.49])
	by hub.freebsd.org (Postfix) with ESMTP id 5DB6F37C036
	for <freebsd-stable@FreeBSD.ORG>; Tue, 28 Mar 2000 14:45:15 -0800 (PST)
	(envelope-from imp@harmony.village.org)
Received: from harmony.village.org (harmony.village.org [10.0.0.6])
	by rover.village.org (8.9.3/8.9.3) with ESMTP id PAA60573;
	Tue, 28 Mar 2000 15:45:14 -0700 (MST)
	(envelope-from imp@harmony.village.org)
Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id PAA08985; Tue, 28 Mar 2000 15:44:54 -0700 (MST)
Message-Id: <200003282244.PAA08985@harmony.village.org>
To: Kiril Mitev <kiril@ideaglobal.com>
Subject: Re: q to Warner Losh wrt his PCI modem patch 
Cc: freebsd-stable@FreeBSD.ORG
In-reply-to: Your message of "Tue, 28 Mar 2000 15:49:01 GMT."
		<200003281549.PAA69054@loki.ideaglobal.com> 
References: <200003281549.PAA69054@loki.ideaglobal.com>  
Date: Tue, 28 Mar 2000 15:44:54 -0700
From: Warner Losh <imp@village.org>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

In message <200003281549.PAA69054@loki.ideaglobal.com> Kiril Mitev writes:
: I found something on deja... posted by Warner Losh

Hmm.  That guy doesn't know what he's talking about.  He posts to
mailing lists after all :-)

: Can anyone PLEASE confirm/deny whether that patch is safe to use
: with fbsd-4 ?

That one isn't.  You might try
	http://people.freebsd.org/~imp/sio-current-pci-patch
instead.  It should work on both 4.0 and -current.  Should be
integrated into the mainline sources soon.  Let me know if you have
problems.  I'll commit it once I get a chance to deal with the latest
round of comments for the review.

Warner


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


From owner-freebsd-stable  Tue Mar 28 17:25:30 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from lynx.aba.net.au (lynx.esec.com.au [203.21.84.1])
	by hub.freebsd.org (Postfix) with SMTP id BB58337B50E
	for <freebsd-stable@FreeBSD.ORG>; Tue, 28 Mar 2000 17:25:23 -0800 (PST)
	(envelope-from tim@esec.com.au)
Received: (qmail 29948 invoked from network); 29 Mar 2000 01:22:58 -0000
Received: from feline.esec.com.au (203.21.85.202)
  by lynx.esec.com.au with SMTP; 29 Mar 2000 01:22:58 -0000
Received: from esec.com.au (localhost [127.0.0.1])
	by feline.esec.com.au (8.9.3/8.9.3) with ESMTP id LAA20241;
	Wed, 29 Mar 2000 11:26:18 +1000 (EST)
	(envelope-from tim@esec.com.au)
Message-ID: <38E15BB9.3E3D5AF9@esec.com.au>
Date: Wed, 29 Mar 2000 11:26:17 +1000
From: Tim Liddelow <tim@esec.com.au>
Organization: eSec Ltd
X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.12 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Grigoriy Strokin <grg@philol.msu.ru>
Cc: Eric Jacoboni <jaco@titine.fr.eu.org>, freebsd-stable@FreeBSD.ORG
Subject: Re: New kernel with its ATA drivers damages the filesystem
References: <20000328195030.A30092@isabase.philol.msu.ru> <87ln33htuc.fsf@titine.fr.eu.org> <20000328221322.A32478@isabase.philol.msu.ru>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Grigoriy Strokin wrote:

>
> > I've had the same problem, it's now fixed with the following line
> > added in my /etc/rc.local :
> >
> > /sbin/sysctl -w hw.atamodes=pio,pio,pio
> >
> > (i've 2 ide disks + an ATAPI cdrom).
>

Yes, this is all well and dandy - but this is a _bug_ in the driver.   Is
there a PR for this ?   I am finding similar filesystem corruption - zero length
directories, dup inodes, etc frequently - and I don't get the timeout problems.
I am now falling back to PIO mode like yourselves, but don't really see this
as a long term solution - could it be the PCI IDE chip we use ?
More specifically, I am running on a VIA Apollo chipset.

Cheers
Tim.

--
====================================================================
Tim Liddelow                      *      Firewalls / Security
OneGuard Technical Lead        *    *    Electronic Commerce
eSec Pty Ltd                       *
Phone: +61 3 8341 2463                   C++/UNIX/WIN32/OOP/OOD
mailto:tim@esec.com.au           *       http://www.oneguard.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 28 17:51:42 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from vcnet.com (mail.vcnet.com [209.239.239.15])
	by hub.freebsd.org (Postfix) with SMTP id EA15B37BC8C
	for <stable@FreeBSD.ORG>; Tue, 28 Mar 2000 17:51:35 -0800 (PST)
	(envelope-from jpr@vcnet.com)
Received: (qmail 1541 invoked from network); 29 Mar 2000 01:51:35 -0000
Received: from joff.vc.net (HELO ?209.239.239.22?) (209.239.239.22)
  by mail.vcnet.com with SMTP; 29 Mar 2000 01:51:35 -0000
Mime-Version: 1.0
Message-Id: <p04310129b5071210f139@[209.239.239.22]>
In-Reply-To: <Pine.GSO.4.10.10003282318010.27642-100000@giger>
References: <Pine.GSO.4.10.10003282318010.27642-100000@giger>
Date: Tue, 28 Mar 2000 17:51:34 -0800
To: Tobias Roth <roth@iamexwi.unibe.ch>,
	Mark Ovens <mark@dogma.freebsd-uk.eu.org>
From: Jon Rust <jpr@vcnet.com>
Subject: Re: HEADS UP: 3.x -> 4.0-STABLE upgrade instructions
Cc: Pieter Westland <pieterw@euronet.nl>, stable@FreeBSD.ORG
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

At 11:21 PM +0200 3/28/00, Tobias Roth wrote:
>So, does that mean I can skip the ldconfig, just do make buildworld and
>make installworld as I always did and everything will work?
>Or do I *HAVE* to to the ldconfig?
>
>thx, tobe

I skipped it, and it worked just fine.

jon


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


From owner-freebsd-stable  Tue Mar 28 18: 2:25 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from chupacabras.flash.net (chupacabras.flash.net [209.30.2.16])
	by hub.freebsd.org (Postfix) with ESMTP id 5EA0E37B5D1
	for <freebsd-stable@freebsd.org>; Tue, 28 Mar 2000 18:02:11 -0800 (PST)
	(envelope-from wotan@fosburgh.org)
Received: from gw.fosburgh.org (p68.amax37.dialup.hou1.flash.net [209.30.72.68])
	by chupacabras.flash.net (8.9.3/Pro-8.9.3) with ESMTP id UAA02691
	for <freebsd-stable@freebsd.org>; Tue, 28 Mar 2000 20:02:00 -0600 (CST)
Received: by gw.fosburgh.org (8.9.3/8.9.3) id UAA12602
	for freebsd-stable@freebsd.org; Tue, 28 Mar 2000 20:01:38 -0600 (CST)
	(envelope-from wotan)
From: Jonathan E Fosburgh <wotan@fosburgh.org>
Reply-To: fosburgh@flash.net
To: freebsd-stable@freebsd.org
Subject: Fwd: ppbus problems with 4.0-RELEASE
Date: Tue, 28 Mar 2000 20:00:08 -0600
X-Mailer: KMail [version 1.0.28]
Content-Type: text/plain
MIME-Version: 1.0
Message-Id: <00032820010100.10764@gw.fosburgh.org>
Content-Transfer-Encoding: 8bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

I sent this to -questions last week and have received no responses.  Thought
I'd give it a shot here.

----------  Forwarded Message  ----------
Subject: ppbus problems with 4.0-RELEASE
Date: Fri, 24 Mar 2000 15:31:58 -0600 (CST)
From: Jonathan E Fosburgh <wotan@gw.fosburgh.org>


I am having problems with my new 4.0-RELEASE system correctly starting up my
ppbus devices. I used the GENERIC config to create my new config, and none
of the ppc stuff changed.  Under 3.4-STABLE ppc worked.  Now, when I boot
(with the -v option) I receive  the following messages:

ppc0: parallel port found at 0x3bc
ppc0: cannot reserve I/O port range
 and I cannot print.  Can anyone offer any help with this, or have I found a
bug?

Jonathan Fosburgh
Jr. UNIX Systems Administrator
MD Anderson Cancer Center
Houston, TX
Home Page:
http://www.fosburgh.org
Manager, FreeBSD Webring:
http://www.geocities.com/vienna/1498/computer/freebsdring.html
ICQ: 32742908
AIM: Namthorien
-------------------------------------------------------

-- 
Jonathan Fosburgh
Jr. UNIX Systems Administrator
MD Anderson Cancer Center
Houston, TX
Home Page:
http://www.fosburgh.org
Manager, FreeBSD Webring:
http://www.geocities.com/vienna/1498/computer/freebsdring.html
ICQ: 32742908
AIM: Namthorien


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


From owner-freebsd-stable  Tue Mar 28 18: 9:26 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from xxx.video-collage.com (xxx.video-collage.com [209.122.149.226])
	by hub.freebsd.org (Postfix) with ESMTP id 3462037B523
	for <freebsd-stable@FreeBSD.ORG>; Tue, 28 Mar 2000 18:09:21 -0800 (PST)
	(envelope-from mi@video-collage.com)
X-Relay-IP: ‚ 
Received: from dufus.video-collage.com (dufus [10.222.222.77])
	by xxx.video-collage.com (8.9.1a/8.9.1) with ESMTP id VAA00760;
	Tue, 28 Mar 2000 21:09:18 -0500 (EST)
From: Mikhail Teterin <mi@video-collage.com>
Received: (from mi@localhost)
	by dufus.video-collage.com (8.9.3/8.9.3) id VAA95858;
	Tue, 28 Mar 2000 21:09:17 -0500 (EST)
	(envelope-from mi@xxx)
Message-Id: <200003290209.VAA95858@dufus.video-collage.com>
Subject: Re: gcc problems
In-Reply-To: <20000328160442.S1135@threads.polyesthetic.msg> from Thimble Smith
 at "Mar 28, 2000 04:04:42 pm"
To: Thimble Smith <tim@mysql.com>
Date: Tue, 28 Mar 2000 21:09:16 -0500 (EST)
Cc: freebsd-stable@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL68 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> On Tue, Mar 28, 2000 at 03:23:06PM -0500, Mikhail Teterin wrote:
> 
> [ sql_yacc.cc has to be compiled with -O0 ]
> 
> >But is  not this, where the  optimization can be quite  desirable? Is
> >not this the query parsing code?
> 
> You can do it with -O -fno-inline.  Just add some more swap space
> and then go for a walk while it compiles.  It's spring - nice
> weather, right?

Well, with ``-O -fexpensive-optimizations -pipe -mcpu=i686 -march=i686''
compiling sql/sql_yacc.cc only took 26 minutes of one of the two PII-300
cpus I have. The machine has 320Mb of  RAM and it did not even touch the
swap.

This is on 4.0, mysql-3.22.32 server port, patches/patch-aq removed...

The source file is huge --  414615 bytes... The resulting object file --
424040.

	-mi


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


From owner-freebsd-stable  Tue Mar 28 19:34:33 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from got.wedgie.org (got.wedgie.org [216.181.169.146])
	by hub.freebsd.org (Postfix) with ESMTP id BABF637BEC0
	for <freebsd-stable@FreeBSD.ORG>; Tue, 28 Mar 2000 19:34:20 -0800 (PST)
	(envelope-from jgarman@got.wedgie.org)
Received: by got.wedgie.org (Postfix, from userid 1000)
	id 3B809D921; Tue, 28 Mar 2000 22:34:20 -0500 (EST)
Date: Tue, 28 Mar 2000 22:34:20 -0500
From: Jason Garman <jgarman@wedgie.org>
To: Tim Liddelow <tim@esec.com.au>
Cc: Grigoriy Strokin <grg@philol.msu.ru>,
	Eric Jacoboni <jaco@titine.fr.eu.org>, freebsd-stable@FreeBSD.ORG
Subject: Re: New kernel with its ATA drivers damages the filesystem
Message-ID: <20000328223420.C10913@got.wedgie.org>
Reply-To: jgarman@wedgie.org
References: <20000328195030.A30092@isabase.philol.msu.ru> <87ln33htuc.fsf@titine.fr.eu.org> <20000328221322.A32478@isabase.philol.msu.ru> <38E15BB9.3E3D5AF9@esec.com.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.4i
In-Reply-To: <38E15BB9.3E3D5AF9@esec.com.au>; from Tim Liddelow on Wed, Mar 29, 2000 at 11:26:17AM +1000
X-Phase-Of-Moon: The Moon is Waning Crescent (42% of Full)
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Wed, Mar 29, 2000 at 11:26:17AM +1000, Tim Liddelow wrote:
> 
> Yes, this is all well and dandy - but this is a _bug_ in the driver.   Is
> there a PR for this ?   I am finding similar filesystem corruption - zero length
> directories, dup inodes, etc frequently - and I don't get the timeout problems.
> I am now falling back to PIO mode like yourselves, but don't really see this
> as a long term solution - could it be the PCI IDE chip we use ?
> More specifically, I am running on a VIA Apollo chipset.
> 
Whats your motherboard?  I just trashed an ASUS P2V (which also has a VIA
chipset on it) -- same problems, under all OSes that used DMA on the
drive.  Unfortunate, really.  Got a new Abit BE6 instead, works like a
dream.  Highly recommended.

enjoy
-- 
Jason Garman                                         http://web.wedgie.org/
Student, University of Maryland                          jgarman@wedgie.org
From fortune(1):                                              Whois: JAG145
  "... Had this been an actual emergency, we would have fled in terror,
   and you would not have been informed."


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


From owner-freebsd-stable  Tue Mar 28 19:52: 3 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from evil.2y.net (ztown1-1-55.adsl.one.net [207.78.254.55])
	by hub.freebsd.org (Postfix) with ESMTP id DBB1237B690
	for <freebsd-stable@FreeBSD.ORG>; Tue, 28 Mar 2000 19:51:48 -0800 (PST)
	(envelope-from cokane@evil.2y.net)
Received: (from cokane@localhost)
	by evil.2y.net (8.9.3/8.9.3) id WAA03858;
	Tue, 28 Mar 2000 22:54:31 -0500 (EST)
	(envelope-from cokane)
Date: Tue, 28 Mar 2000 22:54:31 -0500
From: Coleman Kane <cokane@one.net>
To: Tim Liddelow <tim@esec.com.au>
Cc: Grigoriy Strokin <grg@philol.msu.ru>,
	Eric Jacoboni <jaco@titine.fr.eu.org>, freebsd-stable@FreeBSD.ORG
Subject: Re: New kernel with its ATA drivers damages the filesystem
Message-ID: <20000328225431.B2261@evil.2y.net>
References: <20000328195030.A30092@isabase.philol.msu.ru> <87ln33htuc.fsf@titine.fr.eu.org> <20000328221322.A32478@isabase.philol.msu.ru> <38E15BB9.3E3D5AF9@esec.com.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0.1i
In-Reply-To: <38E15BB9.3E3D5AF9@esec.com.au>; from tim@esec.com.au on Tue, Mar 28, 2000 at 08:26:25PM -0500
X-Vim: vim:tw=70:ts=4:sw=4
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

I am using an Apollo MVP3 and I have not seen any of these problems. At my job,
I have a Dual PII-333 that also does not exhibit this trouble, it is using the
standard PIIX4 440BX chip. Both are running UDMA33 hard drives, mine is a
7200rpm WD Expert 18G, and my work has a 17.2G 5400rpm maxtor. Basically, just
telling what works here. You may want to list some more info about your setup,
like if the hard drives are alone on the chain or if they share it with another
device, which Apollo chipset you are using, and anything else that may help
identify the problem area.

--cokane

Tim Liddelow had the audacity to say:
> Grigoriy Strokin wrote:
> 
> Yes, this is all well and dandy - but this is a _bug_ in the driver.   Is
> there a PR for this ?   I am finding similar filesystem corruption - zero length
> directories, dup inodes, etc frequently - and I don't get the timeout problems.
> I am now falling back to PIO mode like yourselves, but don't really see this
> as a long term solution - could it be the PCI IDE chip we use ?
> More specifically, I am running on a VIA Apollo chipset.
> 
> Cheers
> Tim.
> 


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


From owner-freebsd-stable  Tue Mar 28 19:52:57 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from carbon.btinternet.com (carbon.btinternet.com [194.73.73.92])
	by hub.freebsd.org (Postfix) with ESMTP id EDBB337C019
	for <stable@freebsd.org>; Tue, 28 Mar 2000 19:52:47 -0800 (PST)
	(envelope-from mark@ukug.uk.freebsd.org)
Received: from [213.1.182.156] (helo=parish.my.domain)
	by ruthenium.btinternet.com with esmtp (Exim 2.05 #1)
	id 12a3dB-0005tf-00; Tue, 28 Mar 2000 22:34:37 +0100
Received: (from mark@localhost)
	by parish.my.domain (8.9.3/8.9.3) id WAA01126;
	Tue, 28 Mar 2000 22:31:43 +0100 (BST)
	(envelope-from mark)
Date: Tue, 28 Mar 2000 22:31:40 +0100
From: Mark Ovens <mark@ukug.uk.freebsd.org>
To: Tobias Roth <roth@iamexwi.unibe.ch>
Cc: Pieter Westland <pieterw@euronet.nl>, stable@freebsd.org
Subject: Re: HEADS UP: 3.x -> 4.0-STABLE upgrade instructions
Message-ID: <20000328223140.C234@parish>
References: <20000328213052.B234@parish> <Pine.GSO.4.10.10003282318010.27642-100000@giger>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0.1i
In-Reply-To: <Pine.GSO.4.10.10003282318010.27642-100000@giger>; from roth@iamexwi.unibe.ch on Tue, Mar 28, 2000 at 11:21:46PM +0200
Organization: Total lack of
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Tue, Mar 28, 2000 at 11:21:46PM +0200, Tobias Roth wrote:
> 
> > > > This message appeared 166 times during ``make buildworld'':
> > > > 	/usr/libexec/ld-elf.so.1: Shared object "libc.so.4" not found
> > > > It also caused config(8) on the new kernel to fail, but
> > > > 	ldconfig -R /usr/obj/usr/src/lib/libc
> > > > cured that.
> > 
> > It goes away once you've done ``make installworld'' libc.so.3 was in
> > 3.x but 4.x uses libc.so.4 and while you're doing ``make buildworld''
> > and building a new kernel you've got a sort of hybrid system. I maybe
> > wrong here, but ISTR recall that the new compiler (2.95) gets built
> > with the old compiler and then immediately re-builds itself using
> > itself :-/
> 
> So, does that mean I can skip the ldconfig, just do make buildworld and
> make installworld as I always did and everything will work?
> Or do I *HAVE* to to the ldconfig?
> 

Well no, when you build the 4.x kernel for the first time (before
installworld) it needs the ldconfig in order to find libc.so.4 or the
config will fail. Having said that, ISTR that something is being
changed to remove the need to run ldconfig.

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

-- 
Seminars, n.:
       From "semi" and "arse", hence, any half-assed discussion.
________________________________________________________________
      FreeBSD - The Power To Serve http://www.freebsd.org
      My Webpage http://ukug.uk.freebsd.org/~mark/
mailto:mark@ukug.uk.freebsd.org             http://www.radan.com



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


From owner-freebsd-stable  Tue Mar 28 19:56:25 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from turtle.looksharp.net (cc360882-a.strhg1.mi.home.com [24.2.221.22])
	by hub.freebsd.org (Postfix) with ESMTP id 01E4337BBE3
	for <FreeBSD-STABLE@FreeBSD.ORG>; Tue, 28 Mar 2000 19:56:21 -0800 (PST)
	(envelope-from bandix@looksharp.net)
Received: from localhost (bandix@localhost)
	by turtle.looksharp.net (8.9.3/8.9.3) with ESMTP id WAA63402
	for <FreeBSD-STABLE@FreeBSD.ORG>; Tue, 28 Mar 2000 22:56:58 -0500 (EST)
	(envelope-from bandix@looksharp.net)
Date: Tue, 28 Mar 2000 22:56:57 -0500 (EST)
From: "Brandon D. Valentine" <bandix@looksharp.net>
To: FreeBSD-STABLE <FreeBSD-STABLE@FreeBSD.ORG>
Subject: Re: New kernel with its ATA drivers damages the filesystem
In-Reply-To: <20000328223420.C10913@got.wedgie.org>
Message-ID: <Pine.BSF.4.21.0003282253220.63207-100000@turtle.looksharp.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Tue, 28 Mar 2000, Jason Garman wrote:

>Whats your motherboard?  I just trashed an ASUS P2V (which also has a VIA
>chipset on it) -- same problems, under all OSes that used DMA on the
>drive.  Unfortunate, really.  Got a new Abit BE6 instead, works like a
>dream.  Highly recommended.

Yeah, this is the same reason I'm hesitant to jump into the Athlon
world.  The companies that have been backing AMD's chips are just
horrible at chipsets.  I'd still much prefer a good, solid Intel
chipset, and for IDE/UDMA definitely a PIIX- series controller.  Too
bad, because otherwise the Athlon is a nice platform.

Brandon D. Valentine
-- 
    "...and as for hackers, we note that all of those known to
    The Register are so strapped financially that seizing their
    property would be tantamount to squeezing blood from a stone."
                                     -- The Register, 02/17/2000



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


From owner-freebsd-stable  Tue Mar 28 20:11: 4 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from camelot.bitart.com (BITart-45.BITart.com [206.103.221.45])
	by hub.freebsd.org (Postfix) with SMTP id 5E4AE37BFDC
	for <freebsd-stable@freebsd.org>; Tue, 28 Mar 2000 20:11:01 -0800 (PST)
	(envelope-from gerti@bitart.com)
Received: (qmail 3029 invoked by uid 101); 29 Mar 2000 04:11:04 -0000
Message-ID: <20000329041104.3028.qmail@camelot.bitart.com>
Content-Type: text/plain
MIME-Version: 1.0 (NeXT Mail 4.2mach v148)
X-Nextstep-Mailer: Mail 4.2mach (Enhance 2.2p1)
Received: by NeXT.Mailer (1.148)
From: Gerd Knops <gerti@bitart.com>
Date: Tue, 28 Mar 2000 22:11:04 -0600
To: freebsd-stable@freebsd.org
Subject: Random signal 9 (SIGKILL), please help!
Reply-To: gerti-freebsds@BITart.com
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hello,

I have a large software package running on a lot of machines and several Unixes.

Only on the FreeBSD systems I see that child processes occasionaly get killed by
a signal 9, and I just can't figure out why.

Syslog does not give any indication. The machines do not swap (I know processes may
get killed when the systems run out of swap space). The times at which the processes
are killed does seem to be random, meaning it does not seem dome house keeping code
that causes it.

The processes are spawned from various daemons, and are killed at different points
in their existence, even when just barely started and no resources to mention are
consumed yet.

All processes run as root, so 'limit' should not be the cause.

Is there anything else but the swapper that can trigger a 'signal 9' to be sent to
processes?

The systems in question run a variety of versions, starting from 3.2 Release to a
fairly recent (4 weeks) 3.4 stable.

Any tips and ideas would be more than welcome.

Thanks

Gerd


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


From owner-freebsd-stable  Tue Mar 28 20:12:57 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from evil.2y.net (ztown1-1-55.adsl.one.net [207.78.254.55])
	by hub.freebsd.org (Postfix) with ESMTP id AEC1A37BFB1
	for <FreeBSD-Stable@FreeBSD.ORG>; Tue, 28 Mar 2000 20:12:54 -0800 (PST)
	(envelope-from cokane@evil.2y.net)
Received: (from cokane@localhost)
	by evil.2y.net (8.9.3/8.9.3) id WAA02302;
	Tue, 28 Mar 2000 22:41:58 -0500 (EST)
	(envelope-from cokane)
Date: Tue, 28 Mar 2000 22:41:58 -0500
From: Coleman Kane <cokane@one.net>
To: Jeremiah Gowdy <jgowdy@home.com>
Cc: "Daniel C. Sobral" <dcs@newsguy.com>,
	Alexandr Listopad <laa@ZGIA.zp.ua>, Kuzak <kuzak@kuzak.net>,
	FreeBSD-Stable@FreeBSD.ORG
Subject: Re: 4.0 Kernel
Message-ID: <20000328224158.A2261@evil.2y.net>
References: <Pine.BSF.4.10.10003271228100.48901-100000@Eagle.ZGIA.zp.ua> <38E065C5.418DA948@newsguy.com> <001901bf98db$9b897580$0100000a@vista1.sdca.home.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0.1i
In-Reply-To: <001901bf98db$9b897580$0100000a@vista1.sdca.home.com>; from jgowdy@home.com on Tue, Mar 28, 2000 at 12:27:07PM -0500
X-Vim: vim:tw=70:ts=4:sw=4
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

If you go to http:///www.de.freebsd.org/de/gif/bsd/ there should be a lot of
artwork to look at. They even have the famous nomad daemon on a cliff pic.

--cokane

Jeremiah Gowdy had the audacity to say:
> 
> > Alexandr Listopad wrote:
> > >
> > > # -- sysinstall generated deltas -- #
> > > userconfig_script_load="NO"
> > > autoboot_delay="0"
> > >
> > > splash_bmp_load="YES"
> > > bitmap_load="YES"
> > > bitmap_name="/boot/daemon.bmp"  # Set this to the name of
> > > the bmp or pcx file
> > > bitmap_type="splash_image_data"
> > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> > This line is not necessary, as it is already set by default.
> 
> I knew there was some kind of splash screen you could do for FreeBSD, I just
> didn't know how to do it.  Thanks for enlightening me :)  Now, my question
> is, anyone have some good bmps for a splash screen ?  Where can I get that
> daemon.bmp ?  Thanks
> 
> 
> 


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


From owner-freebsd-stable  Tue Mar 28 20:17:26 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from stingray.ivision.co.uk (avengers.ivision.co.uk [195.50.91.40])
	by hub.freebsd.org (Postfix) with ESMTP id D23BF37C019
	for <freebsd-stable@freebsd.org>; Tue, 28 Mar 2000 20:17:19 -0800 (PST)
	(envelope-from jasper@ivision.co.uk)
Received: from avengers.ivision.co.uk ([195.50.91.40])
	by stingray.ivision.co.uk with esmtp (Exim 2.04 #1)
	id 12a9us-0006kL-00; Wed, 29 Mar 2000 05:17:14 +0100
Date: Wed, 29 Mar 2000 05:17:10 +0100 (BST)
From: Jasper Wallace <jasper@ivision.co.uk>
To: freebsd-stable@freebsd.org
Cc: Nick Ludlam <nick@ivision.co.uk>, sysadmin@ivision.co.uk
Subject: Repeted panics with 3.4
Message-ID: <Pine.GSO.4.21.0003290507040.18891-200000@avengers.ivision.co.uk>
X-NCC-RegID: uk.instant-web
MIME-Version: 1.0
Content-Type: MULTIPART/MIXED; BOUNDARY="-559023410-684387517-954303430=:18891"
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.
  Send mail to mime@docserver.cac.washington.edu for more info.

---559023410-684387517-954303430=:18891
Content-Type: TEXT/PLAIN; charset=US-ASCII


We've got a pair of rackmount webservers, both running 3.4, one has been
fine, the other has just started panic's soon after boot, normally
associated with file system access - i've seen it when trying to mount a
file sys, when trying to run a peice of software amd when doing 'viunm
start':

here is one of the panics: (cut and pasted, the machine has a serial
console).
------------------------------------------------------------------------
# mount /usr/local                                                                                                        
                                                                                                                          
                                                                                                                          
Fatal trap 12: page fault while in kernel mode                                                                            
fault virtual address   = 0x56204e49                                                                                      
fault code              = supervisor read, page not present                                                               
instruction pointer     = 0x8:0xc014b2b8                                                                                  
stack pointer           = 0x10:0xd1bfecb4                                                                                 
frame pointer           = 0x10:0xd1bfecd8                                                                                 
code segment            = base 0x0, limit 0xfffff, type 0x1b                                                              
                        = DPL 0, pres 1, def32 1, gran 1                                                                  
processor eflags        = interrupt enabled, resume, IOPL = 0                                                             
current process         = 57 (mount)                                                                                      
interrupt mask          = net tty bio cam                                                                                 
trap number             = 12                                                                                              
panic: page fault                                                                                                         
                                                                                                                          
syncing disks... done                                                                                                     
Automatic reboot in 15 seconds - press a key on the console to abort                                                      
Rebooting...                                                                                                              
------------------------------------------------------------------------

All the panics have been at instruction pointer 0x8:0xc014b2b8, running nm
on the kernel gives:

# nm /kernel | sort | grep c014b                                                                                          
c014b038 T malloc                                                                                                         
c014b038 t gcc2_compiled.                                                                                                 
c014b348 T free                                                                                                           
c014b488 t kmeminit                                                                                                       

Which dosn't make much sense to me...


questions:

these machines have ecc ram - if the ram fails the ecc checks what does
freebsd do? whould it panic as above?

Is this some irq masking/spl thing caused by using a serial console? (i.e.
is our use of a serial console sufficienty unusual that we are walking
into a less tested area?)

dmesg attached.

-- 
Internet Vision          Internet Consultancy           Tel: 0171 589 4500
60 Albert Court            & Web development            Fax: 0171 589 4522
Prince Consort Road                                   vision@ivision.co.uk
London SW7 2BE                                   http://www.ivision.co.uk/



---559023410-684387517-954303430=:18891
Content-Type: TEXT/PLAIN; charset=US-ASCII; name="ums-web.dmesg"
Content-Transfer-Encoding: BASE64
Content-ID: <Pine.GSO.4.21.0003290517100.18891@avengers.ivision.co.uk>
Content-Description: 
Content-Disposition: attachment; filename="ums-web.dmesg"

Q29weXJpZ2h0IChjKSAxOTkyLTE5OTkgRnJlZUJTRCBJbmMuDQpDb3B5cmln
aHQgKGMpIDE5ODIsIDE5ODYsIDE5ODksIDE5OTEsIDE5OTMNCiAgICAgICAg
VGhlIFJlZ2VudHMgb2YgdGhlIFVuaXZlcnNpdHkgb2YgQ2FsaWZvcm5pYS4g
QWxsIHJpZ2h0cyByZXNlcnZlZC4NCkZyZWVCU0QgMy40LVJFTEVBU0UgIzA6
IEZyaSBNYXIgMTAgMDM6MDg6NTYgR01UIDIwMDANCiAgICByb290QDovdXNy
L3NyYy9zeXMvY29tcGlsZS9VTVMtV0VCDQpUaW1lY291bnRlciAiaTgyNTQi
ICBmcmVxdWVuY3kgMTE5MzE4MiBIeg0KVGltZWNvdW50ZXIgIlRTQyIgIGZy
ZXF1ZW5jeSA1NTEyNTI1OTUgSHoNCkNQVTogUGVudGl1bSBJSUkgKDU1MS4y
NS1NSHogNjg2LWNsYXNzIENQVSkNCiAgT3JpZ2luID0gIkdlbnVpbmVJbnRl
bCIgIElkID0gMHg2NzMgIFN0ZXBwaW5nID0gMw0KICBGZWF0dXJlcz0weDM4
M2ZiZmY8RlBVLFZNRSxERSxQU0UsVFNDLE1TUixQQUUsTUNFLENYOCxBUElD
LFNFUCxNVFJSLFBHRSxNQ0EsQ01PVixQQVQsUFNFMzYsTU1YLEZYU1IsPGIy
NT4+DQpyZWFsIG1lbW9yeSAgPSAxMDczNzQxODI0ICgxMDQ4NTc2SyBieXRl
cykNCmF2YWlsIG1lbW9yeSA9IDEwNDI3ODgzNTIgKDEwMTgzNDhLIGJ5dGVz
KQ0KdmludW06IGxvYWRlZA0KUGVudGl1bSBQcm8gTVRSUiBzdXBwb3J0IGVu
YWJsZWQNClByb2JpbmcgZm9yIGRldmljZXMgb24gUENJIGJ1cyAwOg0KY2hp
cDA6IDxJbnRlbCA4MjQ0M0dYIGhvc3QgdG8gUENJIGJyaWRnZT4gcmV2IDB4
MDAgb24gcGNpMC4wLjANCmNoaXAxOiA8SW50ZWwgODI0NDNHWCBob3N0IHRv
IEFHUCBicmlkZ2U+IHJldiAweDAwIG9uIHBjaTAuMS4wDQpjaGlwMjogPElu
dGVsIDgyMzcxQUIgUENJIHRvIElTQSBicmlkZ2U+IHJldiAweDAyIG9uIHBj
aTAuNy4wDQppZGVfcGNpMDogPEludGVsIFBJSVg0IEJ1cy1tYXN0ZXIgSURF
IGNvbnRyb2xsZXI+IHJldiAweDAxIG9uIHBjaTAuNy4xDQpjaGlwMzogPElu
dGVsIDgyMzcxQUIgUG93ZXIgbWFuYWdlbWVudCBjb250cm9sbGVyPiByZXYg
MHgwMiBvbiBwY2kwLjcuMw0KYWhjMDogPEFkYXB0ZWMgYWljNzg5Ni85NyBV
bHRyYTIgU0NTSSBhZGFwdGVyPiByZXYgMHgwMCBpbnQgYSBpcnEgMTAgb24g
cGNpMC4xMS4wDQphaGMwOiBhaWM3ODk2Lzk3IFdpZGUgQ2hhbm5lbCBBLCBT
Q1NJIElkPTcsIDE2LzI1NSBTQ0JzDQphaGMxOiA8QWRhcHRlYyBhaWM3ODk2
Lzk3IFVsdHJhMiBTQ1NJIGFkYXB0ZXI+IHJldiAweDAwIGludCBhIGlycSAx
MCBvbiBwY2kwLjExLjENCmFoYzE6IGFpYzc4OTYvOTcgV2lkZSBDaGFubmVs
IEIsIFNDU0kgSWQ9NywgMTYvMjU1IFNDQnMNCmZ4cDA6IDxJbnRlbCBFdGhl
ckV4cHJlc3MgUHJvIDEwLzEwMEIgRXRoZXJuZXQ+IHJldiAweDA4IGludCBh
IGlycSAxMSBvbiBwY2kwLjEzLjANCmZ4cDA6IEV0aGVybmV0IGFkZHJlc3Mg
MDA6ZTA6ODE6MTA6ODk6MDUNClByb2JpbmcgZm9yIGRldmljZXMgb24gUENJ
IGJ1cyAxOg0KdmdhMDogPFRyaWRlbnQgbW9kZWwgOTc1MCBWR0EtY29tcGF0
aWJsZSBkaXNwbGF5IGRldmljZT4gcmV2IDB4ZjMgaW50IGEgaXJxIDAgb24g
cGNpMS4wLjANClByb2JpbmcgZm9yIFBuUCBkZXZpY2VzOg0KUHJvYmluZyBm
b3IgZGV2aWNlcyBvbiB0aGUgSVNBIGJ1czoNCnZ0MCBvbiBpc2ENCnZ0MDog
dW5rbm93biB0cmlkZW50LCA4MCBjb2wsIGNvbG9yLCA4IHNjciwgdW5rbm93
biBrYmQsIFtSMy4yMC1iMjRdDQphdGtiZGMwIGF0IDB4NjAtMHg2ZiBvbiBt
b3RoZXJib2FyZA0KYXRrYmQwIGlycSAxIG9uIGlzYQ0KcHNtMCBub3QgZm91
bmQNCnNpbzAgYXQgMHgzZjgtMHgzZmYgaXJxIDQgZmxhZ3MgMHgxMCBvbiBp
c2ENCnNpbzA6IHR5cGUgMTY1NTBBLCBjb25zb2xlDQpzaW8xIGF0IDB4MmY4
LTB4MmZmIGlycSAzIG9uIGlzYQ0Kc2lvMTogdHlwZSAxNjU1MEENCmZkYzAg
YXQgMHgzZjAtMHgzZjcgaXJxIDYgZHJxIDIgb24gaXNhDQpmZGMwOiBGSUZP
IGVuYWJsZWQsIDggYnl0ZXMgdGhyZXNob2xkDQpmZDA6IDEuNDRNQiAzLjVp
bg0Kd2RjMCBub3QgZm91bmQgYXQgMHgxZjANCndkYzEgYXQgMHgxNzAtMHgx
NzcgaXJxIDE1IG9uIGlzYQ0Kd2RjMTogdW5pdCAwIChhdGFwaSk6IDxUT1NI
SUJBIENELVJPTSBYTS02NzAyQi8xMDA1PiwgcmVtb3ZhYmxlLCBhY2NlbCwg
ZG1hLCBpb3JkaXMNCmFjZDA6IGRyaXZlIHNwZWVkIDgyNjhLQi9zZWMsIDEy
OEtCIGNhY2hlDQphY2QwOiBzdXBwb3J0ZWQgcmVhZCB0eXBlczogQ0QtUiwg
Q0QtUlcsIENELURBDQphY2QwOiBBdWRpbzogcGxheSwgMTYgdm9sdW1lIGxl
dmVscw0KYWNkMDogTWVjaGFuaXNtOiBlamVjdGFibGUgdHJheQ0KYWNkMDog
TWVkaXVtOiBuby9ibGFuayBkaXNjIGluc2lkZSwgdW5sb2NrZWQNCnBwYzAg
YXQgMHgzNzggaXJxIDcgZmxhZ3MgMHg0MCBvbiBpc2ENCnBwYzA6IEdlbmVy
aWMgY2hpcHNldCAoTklCQkxFLW9ubHkpIGluIENPTVBBVElCTEUgbW9kZQ0K
cHBpMDogPGdlbmVyaWMgcGFyYWxsZWwgaS9vPiBvbiBwcGJ1cyAwDQp2Z2Ew
IGF0IDB4M2IwLTB4M2RmIG1hZGRyIDB4YTAwMDAgbXNpemUgMTMxMDcyIG9u
IGlzYQ0KbnB4MCBvbiBtb3RoZXJib2FyZA0KbnB4MDogSU5UIDE2IGludGVy
ZmFjZQ0KV2FpdGluZyA1IHNlY29uZHMgZm9yIFNDU0kgZGV2aWNlcyB0byBz
ZXR0bGUNCmNoYW5kYTAgYXQgYWhjMCBidXMgMCB0YXJnZXQgMCBsdW4gMA0K
ZGEwOiA8U0VBR0FURSBTVDM5MTc1TFcgMDAwMT4gRml4ZWQgRGlyZWN0IEFj
Y2VzcyBTQ1NJLTIgZGV2aWNlIA0KZGEwOiA4MC4wMDBNQi9zIHRyYW5zZmVy
cyAoNDAuMDAwTUh6LCBvZmZzZXQgMTUsIDE2Yml0KSwgVGFnZ2VkIFF1ZXVl
aW5nIEVuYWJsZWQNCmRhMDogODY4M01CICgxNzc4MzI0MCA1MTIgYnl0ZSBz
ZWN0b3JzOiAyNTVIIDYzUy9UIDExMDZDKQ0KZGExIGF0IGFoYzAgYnVzIDAg
dGFyZ2V0IDEgbHVuIDANCmRhMTogPFNFQUdBVEUgU1QzOTE3NUxXIDAwMDE+
IEZpeGVkIERpcmVjdCBBY2Nlc3MgU0NTSS0yIGRldmljZSANCmRhMTogODAu
MDAwTUIvcyB0cmFuc2ZlcnMgKDQwLjAwME1Ieiwgb2Zmc2V0IDE1LCAxNmJp
dCksIFRhZ2dlZCBRdWV1ZWluZyBFbmFibGVkDQpkYTE6IDg2ODNNQiAoMTc3
ODMyNDAgNTEyIGJ5dGUgc2VjdG9yczogMjU1SCA2M1MvVCAxMTA2QykNCmdp
bmcgcm9vdCBkZXZpY2UgdG8gZGEwczFhDQpXQVJOSU5HOiAvIHdhcyBub3Qg
cHJvcGVybHkgZGlzbW91bnRlZA0KdmludW06IG5vIGRyaXZlcyBmb3VuZA0K
DQo=
---559023410-684387517-954303430=:18891--


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


From owner-freebsd-stable  Tue Mar 28 20:20:31 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from lynx.aba.net.au (lynx.esec.com.au [203.21.84.1])
	by hub.freebsd.org (Postfix) with SMTP id 5BE9437BF8B
	for <freebsd-stable@FreeBSD.ORG>; Tue, 28 Mar 2000 20:20:22 -0800 (PST)
	(envelope-from tim@esec.com.au)
Received: (qmail 10594 invoked from network); 29 Mar 2000 04:17:55 -0000
Received: from feline.esec.com.au (203.21.85.202)
  by lynx.esec.com.au with SMTP; 29 Mar 2000 04:17:55 -0000
Received: from esec.com.au (localhost [127.0.0.1])
	by feline.esec.com.au (8.9.3/8.9.3) with ESMTP id OAA00302;
	Wed, 29 Mar 2000 14:21:18 +1000 (EST)
	(envelope-from tim@esec.com.au)
Message-ID: <38E184BE.2A1EC450@esec.com.au>
Date: Wed, 29 Mar 2000 14:21:18 +1000
From: Tim Liddelow <tim@esec.com.au>
Organization: eSec Ltd
X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.12 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: jgarman@wedgie.org
Cc: Grigoriy Strokin <grg@philol.msu.ru>,
	Eric Jacoboni <jaco@titine.fr.eu.org>, freebsd-stable@FreeBSD.ORG
Subject: Re: New kernel with its ATA drivers damages the filesystem
References: <20000328195030.A30092@isabase.philol.msu.ru> <87ln33htuc.fsf@titine.fr.eu.org> <20000328221322.A32478@isabase.philol.msu.ru> <38E15BB9.3E3D5AF9@esec.com.au> <20000328223420.C10913@got.wedgie.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Jason Garman wrote:

> >
> Whats your motherboard?  I just trashed an ASUS P2V (which also has a VIA
> chipset on it) -- same problems, under all OSes that used DMA on the
> drive.  Unfortunate, really.  Got a new Abit BE6 instead, works like a
> dream.  Highly recommended.

Well the motherboard is a FIC PA-2011 IIRC - I am running -current, but the
driver is the same AFAIK.   I have put the sysctl in and am waiting to see if
the problems recur.   Changing h/w seems a little heavy handed - I am not
in the positition to do that right now - I'd like to see if there is a perhaps a
software solution to this first.   Do we know for sure it is the hardware ?   Does
Linux have problems on the same hardware ?   If I knew more about the driver
I'd do some hacking, but I don't right now.

If this is a known problem, it should be put in a FAQ somewhere.

Cheers
Tim.

--
====================================================================
Tim Liddelow                      *      Firewalls / Security
OneGuard Technical Lead        *    *    Electronic Commerce
eSec Pty Ltd                       *
Phone: +61 3 8341 2463                   C++/UNIX/WIN32/OOP/OOD
mailto:tim@esec.com.au           *       http://www.oneguard.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 28 20:21:56 2000
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 2E91037B5BB
	for <FreeBSD-Stable@FreeBSD.ORG>; Tue, 28 Mar 2000 20:21:54 -0800 (PST)
	(envelope-from dcs@newsguy.com)
Received: from newsguy.com (p02-dn02kiryunisiki.gunma.ocn.ne.jp [211.0.245.67])
	by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id NAA13099;
	Wed, 29 Mar 2000 13:21:13 +0900 (JST)
Message-ID: <38E18459.46979223@newsguy.com>
Date: Wed, 29 Mar 2000 13:19:37 +0900
From: "Daniel C. Sobral" <dcs@newsguy.com>
X-Mailer: Mozilla 4.7 [en] (Win98; I)
X-Accept-Language: en,pt-BR,ja
MIME-Version: 1.0
To: Jeremiah Gowdy <jgowdy@home.com>
Cc: Alexandr Listopad <laa@ZGIA.zp.ua>, Kuzak <kuzak@kuzak.net>,
	FreeBSD-Stable@FreeBSD.ORG
Subject: Re: 4.0 Kernel
References: <Pine.BSF.4.10.10003271228100.48901-100000@Eagle.ZGIA.zp.ua> <38E065C5.418DA948@newsguy.com> <001901bf98db$9b897580$0100000a@vista1.sdca.home.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Jeremiah Gowdy wrote:
> 
> I knew there was some kind of splash screen you could do for FreeBSD, I just
> didn't know how to do it.  Thanks for enlightening me :)  Now, my question
> is, anyone have some good bmps for a splash screen ?  Where can I get that
> daemon.bmp ?  Thanks

http://www.baldwin.cx/splash/

-- 
Daniel C. Sobral			(8-DCS)
dcs@newsguy.com
dcs@freebsd.org
capo@zurichgnomes.bsdconspiracy.net

	The size of the pizza is inversely proportional to the intensity of the
hunger.


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


From owner-freebsd-stable  Tue Mar 28 20:25:42 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20])
	by hub.freebsd.org (Postfix) with ESMTP id DEF0037BFB1
	for <freebsd-stable@FreeBSD.ORG>; Tue, 28 Mar 2000 20:25:38 -0800 (PST)
	(envelope-from bright@fw.wintelcom.net)
Received: (from bright@localhost)
	by fw.wintelcom.net (8.10.0/8.10.0) id e2T4nnC24985;
	Tue, 28 Mar 2000 20:49:49 -0800 (PST)
Date: Tue, 28 Mar 2000 20:49:49 -0800
From: Alfred Perlstein <bright@wintelcom.net>
To: gerti-freebsds@bitart.com
Cc: freebsd-stable@FreeBSD.ORG
Subject: Re: Random signal 9 (SIGKILL), please help!
Message-ID: <20000328204948.K21029@fw.wintelcom.net>
References: <20000329041104.3028.qmail@camelot.bitart.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0.1i
In-Reply-To: <20000329041104.3028.qmail@camelot.bitart.com>; from gerti@bitart.com on Tue, Mar 28, 2000 at 10:11:04PM -0600
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

* Gerd Knops <gerti@bitart.com> [000328 20:36] wrote:
> Hello,
> 
> I have a large software package running on a lot of machines and
> several Unixes.
> 
> Only on the FreeBSD systems I see that child processes occasionaly
> get killed bya signal 9, and I just can't figure out why.
> 
> Syslog does not give any indication. The machines do not swap (I
> know processes mayget killed when the systems run out of swap
> space). The times at which the processesare killed does seem to
> be random, meaning it does not seem dome house keeping codethat
> causes it.
> 
> The processes are spawned from various daemons, and are killed
> at different pointsin their existence, even when just barely
> started and no resources to mention areconsumed yet.
> 
> All processes run as root, so 'limit' should not be the cause.
> 
> Is there anything else but the swapper that can trigger a 'signal
> 9' to be sent toprocesses?
> 
> The systems in question run a variety of versions, starting from
> 3.2 Release to afairly recent (4 weeks) 3.4 stable.
> 
> Any tips and ideas would be more than welcome.

Please wrap lines at 70 characters.

This is on all the FreeBSD systems?  This is really confusing I've
_never_ heard of this happening, do you have any machines built
with the same _exact_ hardware exibiting the same problems or not?

Have you tried 4.0?  Without some sample code this is going to
be very hard to reproduce.

Are you sure you aren't running out of process slots?  What is
maxusers set to in the kernel?  How many processes typically
run at the same time?

-- 
-Alfred Perlstein - [bright@wintelcom.net|alfred@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 28 20:37:46 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from camelot.bitart.com (BITart-45.BITart.com [206.103.221.45])
	by hub.freebsd.org (Postfix) with SMTP id 9065C37B55A
	for <freebsd-stable@FreeBSD.ORG>; Tue, 28 Mar 2000 20:37:41 -0800 (PST)
	(envelope-from gerti@bitart.com)
Received: (qmail 3095 invoked by uid 101); 29 Mar 2000 04:37:47 -0000
Message-ID: <20000329043747.3094.qmail@camelot.bitart.com>
Content-Type: text/plain
MIME-Version: 1.0 (NeXT Mail 4.2mach v148)
In-Reply-To: <20000328204948.K21029@fw.wintelcom.net>
X-Nextstep-Mailer: Mail 4.2mach (Enhance 2.2p1)
Received: by NeXT.Mailer (1.148)
From: Gerd Knops <gerti@bitart.com>
Date: Tue, 28 Mar 2000 22:37:46 -0600
To: Alfred Perlstein <bright@wintelcom.net>
Subject: Re: Random signal 9 (SIGKILL), please help!
Cc: gerti-freebsds@bitart.com, freebsd-stable@FreeBSD.ORG
Reply-To: gerti-freebsds@BITart.com
References: <20000329041104.3028.qmail@camelot.bitart.com>
	<20000328204948.K21029@fw.wintelcom.net>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Alfred Perlstein wrote:
> * Gerd Knops <gerti@bitart.com> [000328 20:36] wrote:
> > Hello,
> >
> > I have a large software package running on a lot of machines and
> > several Unixes.
> >
> > Only on the FreeBSD systems I see that child processes occasionaly
> > get killed bya signal 9, and I just can't figure out why.
> >
> > Syslog does not give any indication. The machines do not swap (I
> > know processes mayget killed when the systems run out of swap
> > space). The times at which the processesare killed does seem to
> > be random, meaning it does not seem dome house keeping codethat
> > causes it.
> >
> > The processes are spawned from various daemons, and are killed
> > at different pointsin their existence, even when just barely
> > started and no resources to mention areconsumed yet.
> >
> > All processes run as root, so 'limit' should not be the cause.
> >
> > Is there anything else but the swapper that can trigger a 'signal
> > 9' to be sent toprocesses?
> >
> > The systems in question run a variety of versions, starting from
> > 3.2 Release to afairly recent (4 weeks) 3.4 stable.
> >
> > Any tips and ideas would be more than welcome.
>
> Please wrap lines at 70 characters.
>
> This is on all the FreeBSD systems?  This is really confusing I've
> _never_ heard of this happening, do you have any machines built
> with the same _exact_ hardware exibiting the same problems or not?
>
Nope, different hardware, all Intel CPUs, some Pentium Pro, some
Pentium II, ASUS and Gigabyte motherboards.

> Have you tried 4.0?  Without some sample code this is going to
> be very hard to reproduce.
>
The code is >50k lines of perl... No I have not tried 4.0 yet. And
I can not reproduce the problem either, it just randomly appears
at a very low rate. 23 machines running FreeBSD, and I see about 1
to 3 of those a day.

> Are you sure you aren't running out of process slots?  What is
> maxusers set to in the kernel?

64.

> How many processes typically run at the same time?
>
Varying, the busiest machine peaks at about 100 processes, but I
have seen it on machines running only 50 processes.

Thanks for responding!

Gerd


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


From owner-freebsd-stable  Tue Mar 28 21:13:38 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20])
	by hub.freebsd.org (Postfix) with ESMTP id D456D37B95B
	for <freebsd-stable@FreeBSD.ORG>; Tue, 28 Mar 2000 21:13:30 -0800 (PST)
	(envelope-from bright@fw.wintelcom.net)
Received: (from bright@localhost)
	by fw.wintelcom.net (8.10.0/8.10.0) id e2T5bsL26138;
	Tue, 28 Mar 2000 21:37:54 -0800 (PST)
Date: Tue, 28 Mar 2000 21:37:54 -0800
From: Alfred Perlstein <bright@wintelcom.net>
To: gerti-freebsds@bitart.com
Cc: freebsd-stable@FreeBSD.ORG
Subject: Re: Random signal 9 (SIGKILL), please help!
Message-ID: <20000328213754.L21029@fw.wintelcom.net>
References: <20000329041104.3028.qmail@camelot.bitart.com> <20000328204948.K21029@fw.wintelcom.net> <20000329043747.3094.qmail@camelot.bitart.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0.1i
In-Reply-To: <20000329043747.3094.qmail@camelot.bitart.com>; from gerti@bitart.com on Tue, Mar 28, 2000 at 10:37:46PM -0600
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

* Gerd Knops <gerti@bitart.com> [000328 21:03] wrote:
> Alfred Perlstein wrote:
> > * Gerd Knops <gerti@bitart.com> [000328 20:36] wrote:
> > > Only on the FreeBSD systems I see that child processes occasionaly
> > > get killed bya signal 9, and I just can't figure out why.
> > >
> > > Syslog does not give any indication. The machines do not swap (I
> > > know processes mayget killed when the systems run out of swap
> > > space). The times at which the processesare killed does seem to
> > > be random, meaning it does not seem dome house keeping codethat
> > > causes it.
> > >
> > > The processes are spawned from various daemons, and are killed
> > > at different pointsin their existence, even when just barely
> > > started and no resources to mention areconsumed yet.
> > >
> > > All processes run as root, so 'limit' should not be the cause.
> > >
> > > Is there anything else but the swapper that can trigger a 'signal
> > > 9' to be sent toprocesses?
> > >
> > > The systems in question run a variety of versions, starting from
> > > 3.2 Release to afairly recent (4 weeks) 3.4 stable.
> > >
> > This is on all the FreeBSD systems?  This is really confusing I've
> > _never_ heard of this happening, do you have any machines built
> > with the same _exact_ hardware exibiting the same problems or not?
> >
> Nope, different hardware, all Intel CPUs, some Pentium Pro, some
> Pentium II, ASUS and Gigabyte motherboards.
> 
> > Have you tried 4.0?  Without some sample code this is going to
> > be very hard to reproduce.
> >
> The code is >50k lines of perl... No I have not tried 4.0 yet. And
> I can not reproduce the problem either, it just randomly appears
> at a very low rate. 23 machines running FreeBSD, and I see about 1
> to 3 of those a day.
> 
> > Are you sure you aren't running out of process slots?  What is
> > maxusers set to in the kernel?
> 
> 64.

Try maybe 128?

> 
> > How many processes typically run at the same time?
> >
> Varying, the busiest machine peaks at about 100 processes, but I
> have seen it on machines running only 50 processes.
> 
> Thanks for responding!

I've never heard of signal 9 "by accident" and since this problem
happens on a variety of 3.x systems 3.2-3.4 (3.4-stable also?)
it seems really weird.

I don't think I can be of very much help without access to the 
code and the machines running it, as well as how it is being
run, apache+cgi?

-- 
-Alfred Perlstein - [bright@wintelcom.net|alfred@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 28 21:53:54 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from ZGIA.zp.ua (ZGIA.zp.ua [212.35.173.98])
	by hub.freebsd.org (Postfix) with ESMTP id 05ECE37BE1A
	for <FreeBSD-Stable@FreeBSD.ORG>; Tue, 28 Mar 2000 21:51:38 -0800 (PST)
	(envelope-from laa@zgia.zp.ua)
Received: from localhost (laa@localhost)
	by ZGIA.zp.ua (8.9.3/8.9.3) with ESMTP id IAA01220;
	Wed, 29 Mar 2000 08:50:16 +0300 (EEST)
	(envelope-from laa@zgia.zp.ua)
Date: Wed, 29 Mar 2000 08:50:16 +0300 (EEST)
From: Alexandr Listopad <laa@ZGIA.zp.ua>
To: Jeremiah Gowdy <jgowdy@home.com>
Cc: FreeBSD-Stable@FreeBSD.ORG
Subject: Re: 4.0 Kernel
In-Reply-To: <001901bf98db$9b897580$0100000a@vista1.sdca.home.com>
Message-ID: <Pine.BSF.4.10.10003290847300.983-100000@Eagle.ZGIA.zp.ua>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

I find a link to screensavers in handbook. There were also a
instruction about it. It's great! See also splash(3).

Look at handbook before ask a questions about something in
mailing list, handbook is your friend. ;-)

Good Luck!

>> Alexandr Listopad wrote:
>> >
>> > # -- sysinstall generated deltas -- #
>> > userconfig_script_load="NO"
>> > autoboot_delay="0"
>> >
>> > splash_bmp_load="YES"
>> > bitmap_load="YES"
>> > bitmap_name="/boot/daemon.bmp"  # Set this to the name of
>> > the bmp or pcx file
>> > bitmap_type="splash_image_data"
>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>> This line is not necessary, as it is already set by default.
>
>I knew there was some kind of splash screen you could do for FreeBSD, I just
>didn't know how to do it.  Thanks for enlightening me :)  Now, my question
>is, anyone have some good bmps for a splash screen ?  Where can I get that
>daemon.bmp ?  Thanks
>
>
>

--
 Laa.



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


From owner-freebsd-stable  Tue Mar 28 22:11:10 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from web2.sea.nwserv.com (web2.sea.nwserv.com [216.145.16.2])
	by hub.freebsd.org (Postfix) with ESMTP id 1E83237B6DE
	for <freebsd-stable@FreeBSD.ORG>; Tue, 28 Mar 2000 22:11:05 -0800 (PST)
	(envelope-from asaddi@philosophysw.com)
Received: from localhost (asaddi@localhost)
	by web2.sea.nwserv.com (8.9.3/8.9.3) with ESMTP id WAA32564;
	Tue, 28 Mar 2000 22:10:57 -0800 (PST)
	(envelope-from asaddi@philosophysw.com)
Date: Tue, 28 Mar 2000 22:10:57 -0800 (PST)
From: Allan Saddi <asaddi@philosophysw.com>
X-Sender: asaddi@web2.sea.nwserv.com
To: fosburgh@flash.net
Cc: freebsd-stable@FreeBSD.ORG
Subject: Re: Fwd: ppbus problems with 4.0-RELEASE
In-Reply-To: <00032820010100.10764@gw.fosburgh.org>
Message-ID: <Pine.BSF.4.21.0003282156590.31920-100000@web2.sea.nwserv.com>
Organization: Philosophy SoftWorks
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Unfortunately, I can't say that I have a solution. But I have identified
the problem, in case anyone with more knowledge would like to tackle it.

Parallel ports located at 0x3bc conflict with the vga0 device, which
starts at 0x3c0. It appears that the ppc_probe() function in sys/isa/ppc.c
tries to allocate 8 consecutive I/O ports (i.e. 0x3bc-0x3c3) for each
parallel port. Since vga0 already has 0x3c0-0x3c3 allocated, of course
this fails.

I ran into the problem while upgrading my old 486 system to 4.0-STABLE. I
couldn't figure out how to change the port range for the on-board parallel
port. (I couldn't figure out how to get into BIOS!) So I ended up
installing a parallel port card I had laying around...

I suppose a special case can be made for parallel ports at 0x3bc, but that
seems a bit kludgy...

-- 
Allan Saddi                         "The Earth is the cradle of mankind,
asaddi@philosophysw.com              but we cannot live in the cradle
http://www.philosophysw.com/asaddi/  forever." - K.E. Tsiolkovsky

On Tue, 28 Mar 2000, Jonathan E Fosburgh wrote:

> I am having problems with my new 4.0-RELEASE system correctly starting up my
> ppbus devices. I used the GENERIC config to create my new config, and none
> of the ppc stuff changed.  Under 3.4-STABLE ppc worked.  Now, when I boot
> (with the -v option) I receive  the following messages:
> 
> ppc0: parallel port found at 0x3bc
> ppc0: cannot reserve I/O port range
>  and I cannot print.  Can anyone offer any help with this, or have I found a
> bug?



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


From owner-freebsd-stable  Tue Mar 28 22:20:22 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from isabase.philol.msu.ru (isabase.philol.msu.ru [195.208.217.73])
	by hub.freebsd.org (Postfix) with ESMTP id C505D37BB1E
	for <freebsd-stable@FreeBSD.ORG>; Tue, 28 Mar 2000 22:20:16 -0800 (PST)
	(envelope-from grg@isabase.philol.msu.ru)
Received: (from grg@localhost)
	by isabase.philol.msu.ru (8.9.3/8.9.2) id KAA37603
	for freebsd-stable@FreeBSD.ORG; Wed, 29 Mar 2000 10:20:14 +0400 (MSD)
	(envelope-from grg)
Date: Wed, 29 Mar 2000 10:20:14 +0400
From: Grigoriy Strokin <grg@philol.msu.ru>
To: freebsd-stable@FreeBSD.ORG
Subject: Re: New kernel with its ATA drivers damages the filesystem
Message-ID: <20000329102014.A37541@isabase.philol.msu.ru>
References: <20000328195030.A30092@isabase.philol.msu.ru> <87ln33htuc.fsf@titine.fr.eu.org> <20000328221322.A32478@isabase.philol.msu.ru> <38E15BB9.3E3D5AF9@esec.com.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0i
In-Reply-To: <38E15BB9.3E3D5AF9@esec.com.au>; from tim@esec.com.au on Wed, Mar 29, 2000 at 11:26:17AM +1000
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Wed, Mar 29, 2000 at 11:26:17AM +1000, Tim Liddelow wrote:
> Grigoriy Strokin wrote:
> 
> >
> > > I've had the same problem, it's now fixed with the following line
> > > added in my /etc/rc.local :
> > >
> > > /sbin/sysctl -w hw.atamodes=pio,pio,pio
> > >
> > > (i've 2 ide disks + an ATAPI cdrom).
> >
> 
> Yes, this is all well and dandy - but this is a _bug_ in the driver.   Is
> there a PR for this ?   I am finding similar filesystem corruption - zero length
> directories, dup inodes, etc frequently - and I don't get the timeout problems.
> I am now falling back to PIO mode like yourselves, but don't really see this
> as a long term solution - could it be the PCI IDE chip we use ?
> More specifically, I am running on a VIA Apollo chipset.
> 

So am I: 
  pcib2: <VIA 82C598MVP (Apollo MVP3) PCI-PCI (AGP) bridge> at device 1.0 on pci0


I was playing with 4.0 installation all night, 
and found that 
   /sbin/sysctl -w hw.atamodes=pio,pio,pio,pio
should be the first line of /etc/rc,
and if going single-user with boot -s,
I should type this command immediately
after issuing the shell prompt.

Several times I forgot to do that after boot -s, and all times resulted in some
minor or major damage, e.g.  all files in /usr/bin disappeared, and ls /usr/bin
gave file 'at???'.

Now that the system works to me,
I'm afraid for that some day I'll do
do boot -s and forget /sbin/sysctl -w hw.atamodes=pio,pio,pio,pio,
and my filesystems get wiped.


-- 
=== Grigoriy Strokin, Lomonosov University (MGU), Moscow ===
=== contact info: http://isabase.philol.msu.ru/~grg/     ===


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


From owner-freebsd-stable  Tue Mar 28 22:22:22 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from relay.ucb.crimea.ua (relay.ucb.crimea.ua [212.110.138.1])
	by hub.freebsd.org (Postfix) with ESMTP id 6E62F37B598
	for <stable@FreeBSD.ORG>; Tue, 28 Mar 2000 22:21:58 -0800 (PST)
	(envelope-from ru@ucb.crimea.ua)
Received: (from ru@localhost)
	by relay.ucb.crimea.ua (8.9.3/8.9.3/UCB) id JAA26342;
	Wed, 29 Mar 2000 09:20:11 +0300 (EEST)
	(envelope-from ru)
Date: Wed, 29 Mar 2000 09:20:11 +0300
From: Ruslan Ermilov <ru@ucb.crimea.ua>
To: Mark Ovens <mark@dogma.freebsd-uk.eu.org>
Cc: Tobias Roth <roth@iamexwi.unibe.ch>,
	Pieter Westland <pieterw@euronet.nl>, stable@FreeBSD.ORG
Subject: Re: HEADS UP: 3.x -> 4.0-STABLE upgrade instructions
Message-ID: <20000329092011.B24680@relay.ucb.crimea.ua>
Mail-Followup-To: Mark Ovens <mark@dogma.freebsd-uk.eu.org>,
	Tobias Roth <roth@iamexwi.unibe.ch>,
	Pieter Westland <pieterw@euronet.nl>, stable@FreeBSD.ORG
References: <20000328213052.B234@parish> <Pine.GSO.4.10.10003282318010.27642-100000@giger> <20000328223140.C234@parish>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.3i
In-Reply-To: <20000328223140.C234@parish>; from Mark Ovens on Tue, Mar 28, 2000 at 10:31:40PM +0100
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Tue, Mar 28, 2000 at 10:31:40PM +0100, Mark Ovens wrote:
> On Tue, Mar 28, 2000 at 11:21:46PM +0200, Tobias Roth wrote:
> > 
> > > > > This message appeared 166 times during ``make buildworld'':
> > > > > 	/usr/libexec/ld-elf.so.1: Shared object "libc.so.4" not found
> > > > > It also caused config(8) on the new kernel to fail, but
> > > > > 	ldconfig -R /usr/obj/usr/src/lib/libc
> > > > > cured that.
> > > 
> > > It goes away once you've done ``make installworld'' libc.so.3 was in
> > > 3.x but 4.x uses libc.so.4 and while you're doing ``make buildworld''
> > > and building a new kernel you've got a sort of hybrid system. I maybe
> > > wrong here, but ISTR recall that the new compiler (2.95) gets built
> > > with the old compiler and then immediately re-builds itself using
> > > itself :-/
> > 
> > So, does that mean I can skip the ldconfig, just do make buildworld and
> > make installworld as I always did and everything will work?
> > Or do I *HAVE* to to the ldconfig?
> > 
> 
> Well no, when you build the 4.x kernel for the first time (before
> installworld) it needs the ldconfig in order to find libc.so.4 or the
> config will fail. Having said that, ISTR that something is being
> changed to remove the need to run ldconfig.
> 
This is not the case when you build the kernel with buildkernel target.


-- 
Ruslan Ermilov		Sysadmin and DBA of the
ru@ucb.crimea.ua	United Commercial Bank,
ru@FreeBSD.org		FreeBSD committer,
+380.652.247.647	Simferopol, Ukraine

http://www.FreeBSD.org	The Power To Serve
http://www.oracle.com	Enabling The Information Age


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


From owner-freebsd-stable  Tue Mar 28 22:48:30 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from grace.speakeasy.org (grace.speakeasy.org [216.254.0.2])
	by hub.freebsd.org (Postfix) with ESMTP id 3985037BC06
	for <freebsd-stable@FreeBSD.org>; Tue, 28 Mar 2000 22:48:27 -0800 (PST)
	(envelope-from rjoseph@speakeasy.org)
Received: from 11-116.009.popsite.net (11-116.009.popsite.net [207.227.233.116])
	by grace.speakeasy.org (8.10.0/8.10.0) with ESMTP id e2T6m0g07643
	for <freebsd-stable@FreeBSD.org>; Tue, 28 Mar 2000 22:48:15 -0800
Date: Tue, 28 Mar 2000 22:41:29 -0800 (PST)
From: R Joseph Wright <rjoseph@speakeasy.org>
X-Sender: rjoseph@mammalia.sea
To: freebsd-stable@FreeBSD.org
Subject: perl problems with locale
Message-ID: <Pine.BSF.4.21.0003282237350.11296-100000@mammalia.sea>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

I just cvsupped and built world today (4.0-stable) and now I'm getting this
when I run perl:

perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
	LC_ALL = (unset),
	LC_CTYPE = "en_US",
	LANG = (unset)
    are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").

Please CC me in your reply, I'm not subscribed to this list.



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


From owner-freebsd-stable  Tue Mar 28 23:16:10 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from mail.hcisp.net (Stargate.hcisp.net [208.60.89.18])
	by hub.freebsd.org (Postfix) with SMTP id 713CA37BC68
	for <freebsd-stable@FreeBSD.ORG>; Tue, 28 Mar 2000 23:16:07 -0800 (PST)
	(envelope-from tim@mysql.com)
Received: (qmail 4656 invoked from network); 29 Mar 2000 07:22:12 -0000
Received: from modem5.hcisp.net (HELO threads.polyesthetic.msg) (208.60.89.71)
  by stargate.hcisp.net with SMTP; 29 Mar 2000 07:22:12 -0000
Received: (qmail 41968 invoked by uid 1001); 29 Mar 2000 07:15:50 -0000
From: "Thimble Smith" <tim@mysql.com>
Date: Wed, 29 Mar 2000 02:15:50 -0500
To: R Joseph Wright <rjoseph@speakeasy.org>
Cc: freebsd-stable@FreeBSD.ORG
Subject: Re: perl problems with locale
Message-ID: <20000329021550.B39687@threads.polyesthetic.msg>
References: <Pine.BSF.4.21.0003282237350.11296-100000@mammalia.sea>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0.1i
In-Reply-To: <Pine.BSF.4.21.0003282237350.11296-100000@mammalia.sea>; from rjoseph@speakeasy.org on Tue, Mar 28, 2000 at 10:41:29PM -0800
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Tue, Mar 28, 2000 at 10:41:29PM -0800, R Joseph Wright wrote:
>perl: warning: Setting locale failed.

    http://marc.theaimsgroup.com/?m=95393902825999

    >setenv LC_ALL en_US.ISO_8859-1
    >setenv LC_CTYPE en_US.ISO_8859-1
    >setenv LANG en_US.ISO_8859-1

    Of course, this is no problem on a one-user machine, but
    a better (?) way to fix it definitively would be to add
    the vars to the setenv= clause of the default: entry in
    /etc/login.conf .

    -spc

Tim


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


From owner-freebsd-stable  Tue Mar 28 23:18:32 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from evil.2y.net (ztown1-1-55.adsl.one.net [207.78.254.55])
	by hub.freebsd.org (Postfix) with ESMTP id 74E7B37BAAB
	for <FreeBSD-STABLE@FreeBSD.ORG>; Tue, 28 Mar 2000 23:18:23 -0800 (PST)
	(envelope-from cokane@evil.2y.net)
Received: (from cokane@localhost)
	by evil.2y.net (8.9.3/8.9.3) id CAA20153;
	Wed, 29 Mar 2000 02:22:40 -0500 (EST)
	(envelope-from cokane)
Date: Wed, 29 Mar 2000 02:22:40 -0500
From: Coleman Kane <cokane@one.net>
To: "Brandon D. Valentine" <bandix@looksharp.net>
Cc: FreeBSD-STABLE <FreeBSD-STABLE@FreeBSD.ORG>
Subject: Re: New kernel with its ATA drivers damages the filesystem
Message-ID: <20000329022240.B88875@evil.2y.net>
References: <20000328223420.C10913@got.wedgie.org> <Pine.BSF.4.21.0003282253220.63207-100000@turtle.looksharp.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0.1i
In-Reply-To: <Pine.BSF.4.21.0003282253220.63207-100000@turtle.looksharp.net>; from bandix@looksharp.net on Tue, Mar 28, 2000 at 10:57:02PM -0500
X-Vim: vim:tw=70:ts=4:sw=4
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Brandon D. Valentine had the audacity to say:
> On Tue, 28 Mar 2000, Jason Garman wrote:
> 
> Yeah, this is the same reason I'm hesitant to jump into the Athlon
> world.  The companies that have been backing AMD's chips are just
> horrible at chipsets.  I'd still much prefer a good, solid Intel
> chipset, and for IDE/UDMA definitely a PIIX- series controller.  Too
> bad, because otherwise the Athlon is a nice platform.

I really haven't seen any evidence to show that VIA's chipsets are bad, or even
worse than Intel's. I've been able to depend on my FIC VA503+ for about two
years now with no problems at all. Also, if you read about it, the VIA 133A
chipset for the CuMine/Celeron/PII/PIII performs very well when stacked against
even the 820. A good deal of the trouble you may have encountered with mixing
VIA chipsets with P6-based processors is basically that intel still builds their
processors and chipsets for each other, while VIA can only build chipsets for
the chips that are available. Comparing the performance of the VIA chipset vs.
intel chipsets on the P6 platform is a really bad generalization. Comparing the
earlier P5-based offerings, VIA's was best hands down, even over the intel VX/TX
PIIX solutions. I was very impressed with the KX133 and its reviews. You can
most likely look forward to thier next Athlon offering with anticipation. The
AMD 700-series controllers coming out this summer are supposed to be sweet as
well, especially the SMP-capable 770! Basically saying that VIA is bad at making
P6 chipsets compared to Intel is ENTIRELY TRUE, to a point. Intel basically
designs new chipsets along side their next processor core offering, so of course
they have the best solution for their chips, besides the P6 architecture is
extremely coveted by Intel. Maybe try testing the Athlon with KX133 alongside a
PIII with an 820, you may be pleasantly surprised!

As you probably noticed, I do hate FUD. I figured I'd educate you guys on that,
do remember, VIA came out with the first working DMA66 chipset and it had no
problems. My old 430TX board hated DMA...

--cokane
> 
> Brandon D. Valentine


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


From owner-freebsd-stable  Tue Mar 28 23:28:23 2000
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 4EB7437C519
	for <freebsd-stable@FreeBSD.ORG>; Tue, 28 Mar 2000 23:28:21 -0800 (PST)
	(envelope-from jkh@zippy.cdrom.com)
Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1])
	by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id XAA10684;
	Tue, 28 Mar 2000 23:29:18 -0800 (PST)
	(envelope-from jkh@zippy.cdrom.com)
To: Martin Cracauer <cracauer@cons.org>
Cc: freebsd-stable@FreeBSD.ORG
Subject: Re: Let 3.x die ASAP? 
In-reply-to: Your message of "Tue, 28 Mar 2000 11:36:34 +0200."
             <20000328113633.A28085@cons.org> 
Date: Tue, 28 Mar 2000 23:29:18 -0800
Message-ID: <10681.954314958@zippy.cdrom.com>
From: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> I am so impressed with the results of upgrading my more important
> machines to 4.0 or 4-stable that I could imagine not to produce any
> more 3.x releases.

That may be, but we've already promised one more "capstone" for the
3.x branch and I think an equal or greater number of people would be
upset not to get this.  The 3.x branch will end with 3.5 in May 2000.

- Jordan


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


From owner-freebsd-stable  Wed Mar 29  0:16:59 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from support.euronet.nl (support.euronet.nl [194.134.32.134])
	by hub.freebsd.org (Postfix) with ESMTP id 54C2137B97F
	for <freebsd-stable@FreeBSD.ORG>; Wed, 29 Mar 2000 00:16:53 -0800 (PST)
	(envelope-from pieterw@support.euronet.nl)
Received: (from pieterw@localhost)
	by support.euronet.nl (8.10.0/8.10.0) id e2T8GG815655;
	Wed, 29 Mar 2000 10:16:16 +0200 (CEST)
Date: Wed, 29 Mar 2000 10:16:16 +0200
From: Pieter Westland <pieterw@euronet.nl>
To: Salvo Bartolotta <bartequi@neomedia.it>
Cc: freebsd-stable@FreeBSD.ORG
Subject: Re: HEADS UP: 3.x -> 4.0-STABLE upgrade instructions
Message-ID: <20000329101616.A15561@support.euronet.nl>
References: <20000315174557.C40984@relay.ucb.crimea.ua> <200003151903.MAA88473@harmony.village.org> <005701bf8eb3$b02b2150$a44b8486@jking> <20000315210705.A244@parish> <20000328150714.A23199@support.euronet.nl> <20000328.22565900@bartequi.ottodomain.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0i
In-Reply-To: <20000328.22565900@bartequi.ottodomain.org>; from bartequi@neomedia.it on Tue, Mar 28, 2000 at 10:56:59PM +0000
X-OS: FreeBSD support.euronet.nl 2.2.8-STABLE FreeBSD 2.2.8-STABLE 
X-URL: http://support.euronet.nl/~pieterw
X-Editor: vim
X-Quote: Economics is fun!
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hi,

On Tue, Mar 28, 2000 at 10:56:59PM +0000, Salvo Bartolotta wrote:
> > The other problem is that X does not want to let me log in; getting 
> > the following message in the log when trying to log in (starting xdm 
> > works, but after entering login en password it displays a 'Incorrect
> > password'-message and logs):
> > 
> > Mar 28 09:07:50 dustpuppy -:0: unable to dlopen(/usr/lib/pam_unix.so)
> > Mar 28 09:07:50 dustpuppy -:0: [dlerror: /usr/lib/libutil.so.3: 
> > Undefined symbol "freeaddrinfo"] Mar 28 09:07:50 dustpuppy -:0: adding 
> > faulty module: /usr/lib/pam_unix.so
> > 
> > At this moment I'm recompiling XFree86 (3.3.6), I hope the problem 
> > will be solved after this.
> 
> **if** your config files (e.g. pam.conf) are all right, recompiling 
> XFree86  should make it work again. I did exactly so when I upgraded to 
> 4-(then)CURRENT. I shall upgrade to 4-STABLE ASAP <pant,pant> :-)

The configfiles were all right; when I rebuilt XFree86 yesterday a
question passed by about compiling PAM-compatibility or something like
that. I enabled it and X works.

Pieter
--
Any small object that is accidentally dropped will hide under a larger
object.


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


From owner-freebsd-stable  Wed Mar 29  0:21:43 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from infos1.casaccia.enea.it (INFOS1.casaccia.enea.it [192.107.71.175])
	by hub.freebsd.org (Postfix) with ESMTP id B239D37B5DC
	for <freebsd-stable@FreeBSD.ORG>; Wed, 29 Mar 2000 00:21:31 -0800 (PST)
	(envelope-from poggif@casaccia.enea.it)
Received: from studi7106 (STUDI7106.casaccia.enea.it [192.107.77.106])
	by infos1.casaccia.enea.it (8.9.1/8.9.1) with SMTP id KAA14757;
	Wed, 29 Mar 2000 10:21:59 +0200 (MET DST)
Message-Id: <3.0.5.32.20000329102110.00909ec0@infos1.casaccia.enea.it>
X-Sender: poggif@infos1.casaccia.enea.it
X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32)
Date: Wed, 29 Mar 2000 10:21:10 +0200
To: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
From: Fabrizio Poggi <poggif@casaccia.enea.it>
Subject: Re: Let 3.x die ASAP? 
Cc: freebsd-stable@FreeBSD.ORG
In-Reply-To: <10681.954314958@zippy.cdrom.com>
References: <Your message of "Tue, 28 Mar 2000 11:36:34 +0200."             <20000328113633.A28085@cons.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

At 23.29 28/03/00 -0800, you wrote:


>> I am so impressed with the results of upgrading my more important
>> machines to 4.0 or 4-stable that I could imagine not to produce any
>> more 3.x releases.
>
>That may be, but we've already promised one more "capstone" for the
>3.x branch and I think an equal or greater number of people would be
>upset not to get this.  The 3.x branch will end with 3.5 in May 2000.
>
>- Jordan

Mmm... What rumors about the marvellous 4.0! You will I make CVSup huh? I
know I'll try soon or later this wonder, destroing my beautiful 3.4
(curiosity kill the cat)...
;)
At home, during ppp connection, I detect a repeated message "kernel :
overflow of a nfsiod" who nfsiod is a device driver (bad modem?) or a
serial peripherals (from man pages), generally with slow machines. Anyone
has the same problem or can tell if it is a marginal effect of normal loss
of packets (if necessary I can submit the exact log line)?

Regards, Fabrizio


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


From owner-freebsd-stable  Wed Mar 29  0:23:46 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from omnix.net (omnix.net [195.154.168.66])
	by hub.freebsd.org (Postfix) with SMTP id 3000337B609
	for <freebsd-stable@freebsd.org>; Wed, 29 Mar 2000 00:22:18 -0800 (PST)
	(envelope-from didier@omnix.net)
Received: (qmail 7444 invoked by uid 200); 29 Mar 2000 08:22:16 -0000
Received: from localhost (sendmail-bs@127.0.0.1)
  by localhost with SMTP; 29 Mar 2000 08:22:16 -0000
Date: Wed, 29 Mar 2000 08:22:15 +0000 (GMT)
From: Didier Derny <didier@omnix.net>
To: Martin Cracauer <cracauer@cons.org>
Cc: freebsd-stable@freebsd.org
Subject: Re: Let 3.x die ASAP?
In-Reply-To: <20000328113633.A28085@cons.org>
Message-ID: <Pine.BSF.3.96.1000329080220.7123A-100000@omnix.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


why dont you call freebsd freebsd2000 freebsd2001....

freebsd seems running version after version and not stability...

I think that during 1994-1998 I made the right choice to choose FreeBSD
instead of linux.

in 1999 (3.x) I was not so sure at all, no stability too many problems.

In 2000 it's getting worse, for me FreeBSD is not stable at all
the future of FreeBSD is not so clear, version follow after version but
I still have no support for my sound board, realplayer, oracle...
The clients are telling me to install Linux instead of FreeBSD (for
oracle)...
I've just finished uprading the machines to 3.4-release and you are
telling me that there is no future for 3.X...

I'm about to buy a smp machine but I see so many horror stories on
the mailling lists that I'm not sure at all that I should use a smp
machine (or install linux instead of FreeBSD)...

one of our client is running a smp machine with 3.2-BETA without any
probleme...

another client is running 3.4-RELEASE and his machine is rebooting on
heavy load...

with all these problemes the end of 3.x will probably be the end
of FreeBSD for me!

--
Didier Derny
didier@omnix.net

On Tue, 28 Mar 2000, Martin Cracauer wrote:

> A bit of a controvesical question, for sure. 
> 
> I am so impressed with the results of upgrading my more important
> machines to 4.0 or 4-stable that I could imagine not to produce any
> more 3.x releases.
> 
> Let us consider what happens when we release 3.5 before or at the same
> time as 4.1:
> - People will publish reviews based on 3.5 instead of 4.1. As usual,
>   an unadaequate number of them running on SMP machines.
> - People will run into inferious hardware support, especially they
>   will have trouble with large IDE disks and/or IDE PCI controller.
>   Similar issues for Laptop users.
> - People will continue to run with inferiour NFS, Linux emulator etc.
>   The same applies to networking fixes against attacks, especially
>   DOS.
> - People will choose 3.5 over 4.1 and will later go through an
>   3.x->4.x upgrade for no good reason.
> - The remaining issues in 4.x (especially hardware) aren't addressed
>   as fast. There will be some issues with "unclean" usage that the
>   core userbase doesn't use that don't come up until the masses jump
>   on them.
> 
> For me, the real reason is that I now hate the latest 3.x after seeing
> the improvements. It is near to junk, IMHO.
> 
> Several machine of mine had gone instable while moving from 3.[01] to
> 3.4-stable and I suspected hardware trouble. I didn't debug it because
> I didn't want to mess with 3.x anymore. Now after upgrading to 4.x the
> same machines are rock-stable again. It is my impression that the 3.x
> branch lost the required testing when the core committers moved to
> 4.0-current. Higher releases of 3.x are just not polished/tested
> enough anymore, beside the undoubted concrete bug fixes.
> 
> Speaking of testing by committers, I also hate to have machines for
> three branches running to develop bugfixes that apply to more than
> -current. In fact my last 3.x machine (besides a 3.1 machine that
> doesn't have the IDE troubles I have with 3.4-stable) is now a
> production machine of my employer that I'd like to upgrade as well. I
> couldn't think of a good reason to delay that upgrade for 3 or 6
> months if my boss asked me. When i upgrade, I had to commit userland
> bugfixes to 3.x with only testing them on a newer branch. Kernel
> bugfixes would be impossible unless I find someone to test them for
> me.
> 
> I assume that I'm not alone here. That many bug-fixing committers will
> not move with 3 machines along the current branches and that 3.5 will
> not be a worthy successor to our previous *.5 releases.
> 
> Opinions?
> 
> Martin
> -- 
> %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
> Martin Cracauer <cracauer@cons.org> http://www.cons.org/cracauer/
>   Tel.: (private) +4940 5221829 Fax.: (private) +4940 5228536
> 
> 
> 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 29  0:35:57 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from support.euronet.nl (support.euronet.nl [194.134.32.134])
	by hub.freebsd.org (Postfix) with ESMTP id 1514237BD36
	for <freebsd-stable@FreeBSD.ORG>; Wed, 29 Mar 2000 00:35:39 -0800 (PST)
	(envelope-from pieterw@support.euronet.nl)
Received: (from pieterw@localhost)
	by support.euronet.nl (8.10.0/8.10.0) id e2T8ZW516946;
	Wed, 29 Mar 2000 10:35:32 +0200 (CEST)
Date: Wed, 29 Mar 2000 10:35:31 +0200
From: Pieter Westland <pieterw@euronet.nl>
To: Allan Saddi <asaddi@philosophysw.com>
Cc: freebsd-stable@FreeBSD.ORG
Subject: Re: Fwd: ppbus problems with 4.0-RELEASE
Message-ID: <20000329103531.A16372@support.euronet.nl>
References: <00032820010100.10764@gw.fosburgh.org> <Pine.BSF.4.21.0003282156590.31920-100000@web2.sea.nwserv.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0i
In-Reply-To: <Pine.BSF.4.21.0003282156590.31920-100000@web2.sea.nwserv.com>; from asaddi@philosophysw.com on Tue, Mar 28, 2000 at 10:10:57PM -0800
X-OS: FreeBSD support.euronet.nl 2.2.8-STABLE FreeBSD 2.2.8-STABLE 
X-URL: http://support.euronet.nl/~pieterw
X-Editor: vim
X-Quote: Economics is fun!
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hi there,

On Tue, Mar 28, 2000 at 10:10:57PM -0800, Allan Saddi wrote:
> Unfortunately, I can't say that I have a solution. But I have identified
> the problem, in case anyone with more knowledge would like to tackle it.
> Parallel ports located at 0x3bc conflict with the vga0 device, which
> starts at 0x3c0. It appears that the ppc_probe() function in sys/isa/ppc.c
> tries to allocate 8 consecutive I/O ports (i.e. 0x3bc-0x3c3) for each
> parallel port. Since vga0 already has 0x3c0-0x3c3 allocated, of course
> this fails.
> I ran into the problem while upgrading my old 486 system to 4.0-STABLE. I
> couldn't figure out how to change the port range for the on-board parallel
> port. (I couldn't figure out how to get into BIOS!) So I ended up
> installing a parallel port card I had laying around...
> I suppose a special case can be made for parallel ports at 0x3bc, but that
> seems a bit kludgy...

On my machine the same happened after a travel from 3.4 to 4.0; in my logs
I saw this:
Mar 28 23:36:07 dustpuppy /kernel: ppc0: cannot reserve I/O port range

I was just waiting for someone who mailed something about it to the lists
;) Tried to search the mailinglist archives, but they seem not to be
updated to recent mail communication.

However, in the BIOS of my machine I changed the settings for the
parallel port to 378/IRQ 7 and printing is alive again.

Now I see:

Mar 29 10:25:56 dustpuppy /kernel: ppc0: <Parallel port> at port
0x378-0x37f irq 7 flags 0x40 on isa0
Mar 29 10:25:56 dustpuppy /kernel: ppc0: Generic chipset (EPP/NIBBLE) in
COMPATIBLE mode
Mar 29 10:25:56 dustpuppy /kernel: ppbus0: IEEE1284 device found
/NIBBLE/ECP
Mar 29 10:25:56 dustpuppy /kernel: Probing for PnP devices on ppbus0:
Mar 29 10:25:56 dustpuppy /kernel: ppbus0: <DON'T ADVERTISE ON THE
MAILINGLISTS> MLC,PCL,PML
Mar 29 10:25:56 dustpuppy /kernel: lpt0: <Printer> on ppbus0
Mar 29 10:25:56 dustpuppy /kernel: lpt0: Interrupt-driven port

Other question, linked to this: In the bios and in ppc(4) different
parallel port modes are mentioned: EPP, ECP, NIBBLE, with/without DMA,
etc. Which one is preferable? In the docs I cannot find any information
about that.

Pieter
--
Hardware, n.:
        The parts of a computer system that can be kicked.


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


From owner-freebsd-stable  Wed Mar 29  0:38:41 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from epsilon.lucida.qc.ca (epsilon.lucida.qc.ca [216.95.146.6])
	by hub.freebsd.org (Postfix) with SMTP id AD15837B7B4
	for <freebsd-stable@freebsd.org>; Wed, 29 Mar 2000 00:38:36 -0800 (PST)
	(envelope-from matt@ARPA.MAIL.NET)
Received: (qmail 20088 invoked by uid 1000); 29 Mar 2000 08:38:20 -0000
Received: from localhost (sendmail-bs@127.0.0.1)
  by localhost with SMTP; 29 Mar 2000 08:38:20 -0000
Date: Wed, 29 Mar 2000 03:38:17 -0500 (EST)
From: Matt Heckaman <matt@ARPA.MAIL.NET>
X-Sender: matt@epsilon.lucida.qc.ca
To: Didier Derny <didier@omnix.net>
Cc: FreeBSD-STABLE <freebsd-stable@freebsd.org>
Subject: Re: Let 3.x die ASAP?
In-Reply-To: <Pine.BSF.3.96.1000329080220.7123A-100000@omnix.net>
Message-ID: <Pine.BSF.4.21.0003290331400.99462-100000@epsilon.lucida.qc.ca>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Regarding SMP:

I have a dual PIII 550 on an ASUS P3C-D running 3.4-STABLE, the machine is
under **very** high load and has not had a single problem, I think that
the SMP problems reported might be misleading. Also, it is my understanding
that Linux has very poor SMP support.

I have to disagree about the stability going downhill, I started out with
FreeBSD on 3.1-release, and since then I have seen nothing but major
improvement along the version lines. 4.0 is wonderful for me, I have not
had a problem with it excepting the new IDE driver not liking a very old
hard drive of mine, but hey, the wd* drivers are still there.

Likewise, 3.4 is doing fine as well, working away happily on a very high
load machine without the slightest problem, happy as can be. I'm at a loss
to understand where your claims of newer FreeBSD being unstable come from.

Oh, RealPlayer 5 works for me on 3.4-stable and 4.0-stable, Oracle is
reported to work on FreeBSD under Linux emulation but I have not tested
that personally. Please, you owe it to yourself to do some good research
before making a choice.

Regards,
Matt

On Wed, 29 Mar 2000, Didier Derny wrote:

: Date: Wed, 29 Mar 2000 03:22:15 -0500
: From: Didier Derny <didier@omnix.net>
: To: Martin Cracauer <cracauer@cons.org>
: Cc: freebsd-stable@freebsd.org
: Subject: Re: Let 3.x die ASAP?
: 
: 
: why dont you call freebsd freebsd2000 freebsd2001....
: 
: freebsd seems running version after version and not stability...
: 
: I think that during 1994-1998 I made the right choice to choose FreeBSD
: instead of linux.
: 
: in 1999 (3.x) I was not so sure at all, no stability too many problems.
: 
: In 2000 it's getting worse, for me FreeBSD is not stable at all
: the future of FreeBSD is not so clear, version follow after version but
: I still have no support for my sound board, realplayer, oracle...
: The clients are telling me to install Linux instead of FreeBSD (for
: oracle)...
: I've just finished uprading the machines to 3.4-release and you are
: telling me that there is no future for 3.X...
: 
: I'm about to buy a smp machine but I see so many horror stories on
: the mailling lists that I'm not sure at all that I should use a smp
: machine (or install linux instead of FreeBSD)...
: 
: one of our client is running a smp machine with 3.2-BETA without any
: probleme...
: 
: another client is running 3.4-RELEASE and his machine is rebooting on
: heavy load...
: 
: with all these problemes the end of 3.x will probably be the end
: of FreeBSD for me!
: 
: --
: Didier Derny
: didier@omnix.net
: 
: On Tue, 28 Mar 2000, Martin Cracauer wrote:
: 
: > A bit of a controvesical question, for sure. 
: > 
: > I am so impressed with the results of upgrading my more important
: > machines to 4.0 or 4-stable that I could imagine not to produce any
: > more 3.x releases.
: > 
: > Let us consider what happens when we release 3.5 before or at the same
: > time as 4.1:
: > - People will publish reviews based on 3.5 instead of 4.1. As usual,
: >   an unadaequate number of them running on SMP machines.
: > - People will run into inferious hardware support, especially they
: >   will have trouble with large IDE disks and/or IDE PCI controller.
: >   Similar issues for Laptop users.
: > - People will continue to run with inferiour NFS, Linux emulator etc.
: >   The same applies to networking fixes against attacks, especially
: >   DOS.
: > - People will choose 3.5 over 4.1 and will later go through an
: >   3.x->4.x upgrade for no good reason.
: > - The remaining issues in 4.x (especially hardware) aren't addressed
: >   as fast. There will be some issues with "unclean" usage that the
: >   core userbase doesn't use that don't come up until the masses jump
: >   on them.
: > 
: > For me, the real reason is that I now hate the latest 3.x after seeing
: > the improvements. It is near to junk, IMHO.
: > 
: > Several machine of mine had gone instable while moving from 3.[01] to
: > 3.4-stable and I suspected hardware trouble. I didn't debug it because
: > I didn't want to mess with 3.x anymore. Now after upgrading to 4.x the
: > same machines are rock-stable again. It is my impression that the 3.x
: > branch lost the required testing when the core committers moved to
: > 4.0-current. Higher releases of 3.x are just not polished/tested
: > enough anymore, beside the undoubted concrete bug fixes.
: > 
: > Speaking of testing by committers, I also hate to have machines for
: > three branches running to develop bugfixes that apply to more than
: > -current. In fact my last 3.x machine (besides a 3.1 machine that
: > doesn't have the IDE troubles I have with 3.4-stable) is now a
: > production machine of my employer that I'd like to upgrade as well. I
: > couldn't think of a good reason to delay that upgrade for 3 or 6
: > months if my boss asked me. When i upgrade, I had to commit userland
: > bugfixes to 3.x with only testing them on a newer branch. Kernel
: > bugfixes would be impossible unless I find someone to test them for
: > me.
: > 
: > I assume that I'm not alone here. That many bug-fixing committers will
: > not move with 3 machines along the current branches and that 3.5 will
: > not be a worthy successor to our previous *.5 releases.
: > 
: > Opinions?
: > 
: > Martin
: > -- 
: > %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
: > Martin Cracauer <cracauer@cons.org> http://www.cons.org/cracauer/
: >   Tel.: (private) +4940 5221829 Fax.: (private) +4940 5228536
: > 
: > 
: > 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
: 

Matt Heckaman
matt@arpa.mail.net
http://www.lucida.qc.ca

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.1 (FreeBSD)
Comment: http://www.lucida.qc.ca/pgp

iD8DBQE44cD7dMMtMcA1U5ARAk0pAKCY75GOXGPjaIOhBmM8/co2e8wQfACfde4A
d4lr1w7iWxENVSviFtP4Rhk=
=NuUt
-----END PGP SIGNATURE-----




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


From owner-freebsd-stable  Wed Mar 29  0:42:50 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from jason.argos.org (a1-3b058.neo.rr.com [24.93.181.58])
	by hub.freebsd.org (Postfix) with ESMTP id 888E337B689
	for <freebsd-stable@FreeBSD.ORG>; Wed, 29 Mar 2000 00:42:34 -0800 (PST)
	(envelope-from mike@argos.org)
Received: from localhost (mike@localhost)
	by jason.argos.org (8.9.1/8.9.1) with ESMTP id DAA28224;
	Wed, 29 Mar 2000 03:41:45 -0500
Date: Wed, 29 Mar 2000 03:41:45 -0500 (EST)
From: Mike Nowlin <mike@argos.org>
To: Didier Derny <didier@omnix.net>
Cc: Martin Cracauer <cracauer@cons.org>, freebsd-stable@FreeBSD.ORG
Subject: Re: Let 3.x die ASAP?
In-Reply-To: <Pine.BSF.3.96.1000329080220.7123A-100000@omnix.net>
Message-ID: <Pine.LNX.4.05.10003290328060.28083-100000@jason.argos.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


> I'm about to buy a smp machine but I see so many horror stories on
> the mailling lists that I'm not sure at all that I should use a smp
> machine (or install linux instead of FreeBSD)...

Trust me - Linux isn't without it's share of problems with SMP...  I have
a Dual-CPU P2-333 sitting here running Linux 2.2.12 (Intel DK440LX board)
which never fails to create one new brainache after another...  Today,
it's Extace (sound "viewing" program).  Works great when SMP isn't
running, seg faults when both processors are kicking along.

A big chunk of what I like about FreeBSD compared to Linux is that there's
more accountability for specific parts of the system.  Linus takes care of
the Linux kernel, but who knows who does the rest -- depending on what
release, by what distributor (Slackware, Redhat, etc.), finding library X
to update library Y to fix program Z can be a real pain...  With FreeBSD,
you can easily find out who is responsible for various chunks of the
system.  Even if he/she doesn't have a solution for your particular
problem, he'll generally have a good idea where to send you, or be willing
to fix the problem in the tree.


(Don't get me wrong - I love Linux, but FreeBSD is better for a lot of
things...  My "play toy" is a Linux SMP machine, but for reliability at
both of the IT shops I'm in charge of, I'll pick FreeBSD every time...)

--mike




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


From owner-freebsd-stable  Wed Mar 29  0:52:57 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from unix.sim.com.pl (unix.sim.com.pl [195.117.85.26])
	by hub.freebsd.org (Postfix) with ESMTP id 7B2E337B609
	for <freebsd-stable@FreeBSD.ORG>; Wed, 29 Mar 2000 00:52:52 -0800 (PST)
	(envelope-from gawel@sim.com.pl)
Received: from sim.com.pl (pawel [192.168.1.20])
	by unix.sim.com.pl (8.9.3/8.9.3) with ESMTP id KAA11613;
	Wed, 29 Mar 2000 10:43:24 +0200 (CEST)
	(envelope-from gawel@sim.com.pl)
Message-ID: <38E1D32B.F946EEB8@sim.com.pl>
Date: Wed, 29 Mar 2000 11:55:56 +0200
From: Gawel <gawel@sim.com.pl>
X-Mailer: Mozilla 4.72 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Eric Jacoboni <jaco@titine.fr.eu.org>
Cc: Grigoriy Strokin <grg@philol.msu.ru>, freebsd-stable@FreeBSD.ORG
Subject: Re: New kernel with its ATA drivers damages the filesystem
References: <20000328195030.A30092@isabase.philol.msu.ru> <87ln33htuc.fsf@titine.fr.eu.org>
Content-Type: text/plain; charset=iso-8859-2
Content-Transfer-Encoding: 8bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hello,
The same message ( ata0: resetting devices .. done; ad0: WRITE command
timeout - resetting)
has appeared to me but during instalation 4.0R form CDROM.
I have no idea how to install 4.0 on my PC.
Is there any trick to switch on hw.atamodes=pio,pio,pio during instalation
from CD?

With regards,
Gawel

Eric Jacoboni wrote:

> Grigoriy Strokin <grg@philol.msu.ru> writes:
>
> > Mar 28 17:49:07 koch2 /kernel: ed0: device timeout
> > Mar 28 17:49:07 koch2 /kernel: ed0: device timeout
> > Mar 28 17:49:07 koch2 /kernel: ata0: resetting devices .. done
> > Mar 28 17:49:48 koch2 /kernel: ad0: WRITE command timeout - resetting
> > Mar 28 17:49:48 koch2 /kernel: ata0: resetting devices .. done
>
> > Now I think I don't know where to find the source of the problem.
>
> Have you tried what the ata manpage suggests ?
>
> I've had the same problem, it's now fixed with the following line
> added in my /etc/rc.local :
>
> /sbin/sysctl -w hw.atamodes=pio,pio,pio
>
> (i've 2 ide disks + an ATAPI cdrom).
> --
> ---------------------------------------------------------
> Éric Jacoboni       « No sport, cigars! »  (W. Churchill)
> ---------------------------------------------------------
>
> 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 29  1: 2:23 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from io.cts.com (io.cts.com [198.68.174.34])
	by hub.freebsd.org (Postfix) with ESMTP id 7746437BB39
	for <freebsd-stable@freebsd.org>; Wed, 29 Mar 2000 01:01:29 -0800 (PST)
	(envelope-from mdavis@cts.com)
Received: from pluto (voyager.cts.com [198.68.174.38])
	by io.cts.com (8.9.3/8.9.2) with SMTP id BAA13301
	for <freebsd-stable@freebsd.org>; Wed, 29 Mar 2000 01:01:25 -0800 (PST)
	(envelope-from mdavis@cts.com)
From: "Morgan Davis" <mdavis@cts.com>
To: <freebsd-stable@freebsd.org>
Subject: 4.0-stable + SMP + fxp = device timeout
Date: Wed, 29 Mar 2000 01:01:27 -0800
Message-ID: <NABBLJGKKPMOKACIENPPEEGMCKAA.mdavis@cts.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 IMO, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

The subject says it all.  Is this a known problem with SMP and the fxp
driver? (Checked 4.0 errata and searched the mailing lists -- didn't see
anything).

--Morgan



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


From owner-freebsd-stable  Wed Mar 29  1: 6: 0 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from palrel1.hp.com (palrel1.hp.com [156.153.255.242])
	by hub.freebsd.org (Postfix) with ESMTP id 19ED337BBA2
	for <freebsd-stable@freebsd.org>; Wed, 29 Mar 2000 01:05:17 -0800 (PST)
	(envelope-from steve@sse0691.bri.hp.com)
Received: from sse0691.bri.hp.com (sse0691.bri.hp.com [15.144.0.53])
	by palrel1.hp.com (Postfix) with ESMTP
	id A9BAD9FF; Wed, 29 Mar 2000 01:05:03 -0800 (PST)
Received: (from steve@localhost)
	by sse0691.bri.hp.com (8.9.3/8.9.3) id KAA94692;
	Wed, 29 Mar 2000 10:02:03 +0100 (BST)
	(envelope-from steve)
Date: Wed, 29 Mar 2000 10:02:03 +0100
From: Steve Roome <steve@sse0691.bri.hp.com>
To: "Brandon D. Valentine" <bandix@looksharp.net>
Cc: freebsd-stable@freebsd.org
Subject: Re: New kernel with its ATA drivers damages the filesystem
Message-ID: <20000329100203.A94487@moose.bri.hp.com>
References: <20000328223420.C10913@got.wedgie.org> <Pine.BSF.4.21.0003282253220.63207-100000@turtle.looksharp.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0.1i
In-Reply-To: <Pine.BSF.4.21.0003282253220.63207-100000@turtle.looksharp.net>; from bandix@looksharp.net on Tue, Mar 28, 2000 at 10:56:57PM -0500
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Tue, Mar 28, 2000 at 10:56:57PM -0500, Brandon D. Valentine wrote:
> On Tue, 28 Mar 2000, Jason Garman wrote:
> 
> >Whats your motherboard?  I just trashed an ASUS P2V (which also has a VIA
> >chipset on it) -- same problems, under all OSes that used DMA on the
> >drive.  Unfortunate, really.  Got a new Abit BE6 instead, works like a
> >dream.  Highly recommended.
> 
> Yeah, this is the same reason I'm hesitant to jump into the Athlon
> world.  The companies that have been backing AMD's chips are just
> horrible at chipsets.  I'd still much prefer a good, solid Intel
> chipset, and for IDE/UDMA definitely a PIIX- series controller.  Too
> bad, because otherwise the Athlon is a nice platform.

I've had VIA chipsets since as long as I can remember (started with
freebsd on 2.1) and they've been fine, [not withstanding pilot error,
overclocking too far and putting just plain wrong or silly settings in
the BIOS.]


IMHO, on an comparison (using same release times) the VIA chipsets
have performed admirably (often far better, but never far worse) than
the Intel offering. Even the SiS chipsets I started with were
prefectly reliable, and also at least as good performers as their
rivals.

My Athlon500 + FIC SD11 is fine, the only problem being I needed a BIOS upgrade for
my 34Gb IDE disk because I bought the board as soon as it hit the market =(

It runs make worlds (3.4-stable) in about 40 mins, and I can thrash
any part of the hardware just as hard as on any other machine without
causing an FIC-only problem.

All I want now is a -march=athlon gcc/egcs flag in 3.4-stable.

	Steve


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


From owner-freebsd-stable  Wed Mar 29  1:11:47 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161])
	by hub.freebsd.org (Postfix) with ESMTP id B791F37B696
	for <freebsd-stable@freebsd.org>; Wed, 29 Mar 2000 01:11:41 -0800 (PST)
	(envelope-from doconnor@gsoft.com.au)
Received: from cain.gsoft.com.au (doconnor@cain [203.38.152.97])
	by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id SAA29679;
	Wed, 29 Mar 2000 18:41:08 +0930 (CST)
	(envelope-from doconnor@gsoft.com.au)
Message-ID: <XFMail.000329184108.doconnor@gsoft.com.au>
X-Mailer: XFMail 1.4.0 on FreeBSD
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <NABBLJGKKPMOKACIENPPEEGMCKAA.mdavis@cts.com>
Date: Wed, 29 Mar 2000 18:41:08 +0930 (CST)
From: "Daniel O'Connor" <doconnor@gsoft.com.au>
To: Morgan Davis <mdavis@cts.com>
Subject: RE: 4.0-stable + SMP + fxp = device timeout
Cc: freebsd-stable@freebsd.org
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


On 29-Mar-00 Morgan Davis wrote:
>  The subject says it all.  Is this a known problem with SMP and the fxp
>  driver? (Checked 4.0 errata and searched the mailing lists -- didn't see
>  anything).

I had this problem while testing a PCI device of my companies creation..

I didn't have time to look into it further though. (I assumed it was a
driver/card issue).

I was using dual PII-350's on an Epox m/b (the model number which escapes
me..) - BX based.

It was a -current just before the 4/5 switchover.

---
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
"The nice thing about standards is that there
are so many of them to choose from."
  -- Andrew Tanenbaum


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


From owner-freebsd-stable  Wed Mar 29  1:14:28 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from workhorse.iMach.com (workhorse.iMach.com [206.127.77.89])
	by hub.freebsd.org (Postfix) with ESMTP id 4F7D837B52E
	for <freebsd-stable@FreeBSD.ORG>; Wed, 29 Mar 2000 01:14:24 -0800 (PST)
	(envelope-from forrestc@workhorse.iMach.com)
Received: from localhost (forrestc@localhost)
	by workhorse.iMach.com (8.9.3/8.9.3) with ESMTP id CAA19313;
	Wed, 29 Mar 2000 02:14:26 -0700 (MST)
Date: Wed, 29 Mar 2000 02:14:25 -0700 (MST)
From: "Forrest W. Christian" <forrestc@iMach.com>
To: Didier Derny <didier@omnix.net>
Cc: Martin Cracauer <cracauer@cons.org>, freebsd-stable@FreeBSD.ORG
Subject: Re: Let 3.x die ASAP?
In-Reply-To: <Pine.BSF.3.96.1000329080220.7123A-100000@omnix.net>
Message-ID: <Pine.BSF.4.21.0003290146040.18478-100000@workhorse.iMach.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Wed, 29 Mar 2000, Didier Derny wrote:

> freebsd seems running version after version and not stability...

> in 1999 (3.x) I was not so sure at all, no stability too many problems.

hmmm....

# uptime
 1:44AM  up 46 days, 22:36, 1 user, load averages: 0.01, 0.02, 0.00

This is on a 3.4-STABLE box.   Prior to the last reboot (which I made
because I somehow had missed compiling the kernel with an appropriate # of
users), it had been up since 12/21/1999 when I cvsup'd it last.  

Don't let the low load averages fool you - this box is handling around
3000 popmail/imap3 accounts - and 100,000 messages go through it every
day (mostly client relay).

I don't remember the last time a freebsd box crashed around here unless I
had hardware going bad.

> In 2000 it's getting worse, for me FreeBSD is not stable at all
> the future of FreeBSD is not so clear, version follow after version but
> I still have no support for my sound board, realplayer, oracle...
> The clients are telling me to install Linux instead of FreeBSD (for
> oracle)...

Linux Oracle 8.0.5 purportedly runs great on FreeBSD 3.x.  See: 
http://www.lf.net/lf/pi/oracle/install-linux-oracle-on-freebsd

I can't vouch for sound card support.  I gave up using sound cards in
any unix a while back INCLUDING Linux and FreeBSD...  although I might try
a unix box on my desktop for mbone stuff again now that it seems to be
more stable from what I hear.   I will grant that Linux tends to support
more obscure hardware than FreeBSD, although I have found that driver
quality under Linux tends to be spotty.

The key to this whole thing is that in a lot of (if not most) cases,
FreeBSD (in my opinion) runs Linux binaries better than Linux.   Turn on
linux binary compatibility and then use linux stuff to your hearts
content.  

I have had friends which I have been talking to about how freebsd is
better than linux go to web conferences and hearing everyone else say "run
everything on freebsd and use linux emulation where necessary".  This
seems to be the trend at big web sites.

> I've just finished uprading the machines to 3.4-release and you are
> telling me that there is no future for 3.X...

The way I read the whole topic is more like "4.x works great, and is
stable, and people need to move there, so why drag out the lifetime of
3.x".   I don't recommend .0 releases at all for production work, but if
it turns out that 4.1 is at least as stable as 3.4 or 3.5 I don't see why
we'd need a 3.6 or 3.7 or so on.

> I'm about to buy a smp machine but I see so many horror stories on
> the mailling lists that I'm not sure at all that I should use a smp
> machine (or install linux instead of FreeBSD)...

Let me tell you my experience with SMP - stability depends on the
hardware.   I have used SMP on both FreeBSD and on NetWare and on NT,
(actually more NT than the others) and I can say that some hardware just
won't work reliably with SMP.  I've seen Dell Multi-CPU boxes get the
motherboard replaced THREE times before it stabilizes.   I've also seen
machines which just couldn't run it at all.   I've seen hardware where
NetWare blows up on but runs NT in multiprocessor mode fine.  And vice
versa.

I'm curious as to what hardware you're having all these problems
with.  Are you overclocking?  Is the airflow adequate?  What type of
drives/controllers are you using? etc....   I really wonder if you've got
some weird hardware problem which is plaguing (sp?) you.

- Forrest W. Christian (forrestc@imach.com) KD7EHZ
----------------------------------------------------------------------
iMach, Ltd., P.O. Box 5749, Helena, MT 59604      http://www.imach.com
Solutions for your high-tech problems.                  (406)-442-6648
----------------------------------------------------------------------



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


From owner-freebsd-stable  Wed Mar 29  1:18:47 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from io.cts.com (io.cts.com [198.68.174.34])
	by hub.freebsd.org (Postfix) with ESMTP id 099B637BD20
	for <freebsd-stable@freebsd.org>; Wed, 29 Mar 2000 01:18:42 -0800 (PST)
	(envelope-from mdavis@cts.com)
Received: from pluto (psyclops@voyager.cts.com [198.68.174.38])
	by io.cts.com (8.9.3/8.9.2) with SMTP id BAA13319;
	Wed, 29 Mar 2000 01:18:40 -0800 (PST)
	(envelope-from mdavis@cts.com)
From: "Morgan Davis" <mdavis@cts.com>
To: <freebsd-stable@freebsd.org>
Cc: <doconnor@gsoft.com.au>
Subject: RE: 4.0-stable + SMP + fxp = device timeout
Date: Wed, 29 Mar 2000 01:18:42 -0800
Message-ID: <NABBLJGKKPMOKACIENPPIEGMCKAA.mdavis@cts.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
In-Reply-To: <XFMail.000329184108.doconnor@gsoft.com.au>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Well, no experimental PCI cards here.  The same hardware used to run
3.4-stable in SMP mode with no problems.  It runs the 4.0-stable GENERIC
kernel just fine.  But enabling SMP causes the ethernet timeouts.  Here's
all I changed to the GENERIC kernel config:

options         SMP                     # Symmetric MultiProcessor Kernel
options         APIC_IO                 # Symmetric (APIC) I/O

These are exactly the two lines that were uncommented when the hardware ran
3.4-stable.

--Morgan


> -----Original Message-----
> From: doconnor@gsoft.com.au [mailto:doconnor@gsoft.com.au]
> Sent: Wednesday, March 29, 2000 1:11 AM
> To: Morgan Davis
> Cc: freebsd-stable@freebsd.org
> Subject: RE: 4.0-stable + SMP + fxp = device timeout
>
>
>
> On 29-Mar-00 Morgan Davis wrote:
> >  The subject says it all.  Is this a known problem with SMP and the fxp
> >  driver? (Checked 4.0 errata and searched the mailing lists --
> didn't see
> >  anything).
>
> I had this problem while testing a PCI device of my companies creation..
>
> I didn't have time to look into it further though. (I assumed it was a
> driver/card issue).
>
> I was using dual PII-350's on an Epox m/b (the model number which escapes
> me..) - BX based.
>
> It was a -current just before the 4/5 switchover.
>
> ---
> Daniel O'Connor software and network engineer
> for Genesis Software - http://www.gsoft.com.au
> "The nice thing about standards is that there
> are so many of them to choose from."
>   -- Andrew Tanenbaum
>



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


From owner-freebsd-stable  Wed Mar 29  1:33:22 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161])
	by hub.freebsd.org (Postfix) with ESMTP id 9487037BEA2
	for <freebsd-stable@freebsd.org>; Wed, 29 Mar 2000 01:33:13 -0800 (PST)
	(envelope-from doconnor@gsoft.com.au)
Received: from cain.gsoft.com.au (doconnor@cain [203.38.152.97])
	by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id TAA29905;
	Wed, 29 Mar 2000 19:03:04 +0930 (CST)
	(envelope-from doconnor@gsoft.com.au)
Message-ID: <XFMail.000329190304.doconnor@gsoft.com.au>
X-Mailer: XFMail 1.4.0 on FreeBSD
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <NABBLJGKKPMOKACIENPPIEGMCKAA.mdavis@cts.com>
Date: Wed, 29 Mar 2000 19:03:04 +0930 (CST)
From: "Daniel O'Connor" <doconnor@gsoft.com.au>
To: Morgan Davis <mdavis@cts.com>
Subject: RE: 4.0-stable + SMP + fxp = device timeout
Cc: freebsd-stable@freebsd.org
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


On 29-Mar-00 Morgan Davis wrote:
>  Well, no experimental PCI cards here.  The same hardware used to run
>  3.4-stable in SMP mode with no problems.  It runs the 4.0-stable GENERIC
>  kernel just fine.  But enabling SMP causes the ethernet timeouts.  Here's
>  all I changed to the GENERIC kernel config:
>  
>  options         SMP                     # Symmetric MultiProcessor Kernel
>  options         APIC_IO                 # Symmetric (APIC) I/O
>  
>  These are exactly the two lines that were uncommented when the hardware
>  ran
>  3.4-stable.

The system in question hasn't ever run 3.4 so I don't know if it works under
those circumstances..

Hmmm :-/

What other stuff do you have plugged in? Does the fxp share irqs? Tried
swapping cards? Doing BIOS upgrades? etc etc :)

---
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
"The nice thing about standards is that there
are so many of them to choose from."
  -- Andrew Tanenbaum


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


From owner-freebsd-stable  Wed Mar 29  1:34:25 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from infos1.casaccia.enea.it (INFOS1.casaccia.enea.it [192.107.71.175])
	by hub.freebsd.org (Postfix) with ESMTP id A433B37BBA2
	for <freebsd-stable@FreeBSD.ORG>; Wed, 29 Mar 2000 01:33:53 -0800 (PST)
	(envelope-from poggif@casaccia.enea.it)
Received: from studi7106 (STUDI7106.casaccia.enea.it [192.107.77.106])
	by infos1.casaccia.enea.it (8.9.1/8.9.1) with SMTP id LAA26922;
	Wed, 29 Mar 2000 11:34:13 +0200 (MET DST)
Message-Id: <3.0.5.32.20000329113324.00928850@infos1.casaccia.enea.it>
X-Sender: poggif@infos1.casaccia.enea.it
X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32)
Date: Wed, 29 Mar 2000 11:33:24 +0200
To: Didier Derny <didier@omnix.net>
From: Fabrizio Poggi <poggif@casaccia.enea.it>
Subject: Re: Let 3.x die ASAP?
Cc: freebsd-stable@FreeBSD.ORG
In-Reply-To: <Pine.BSF.3.96.1000329080220.7123A-100000@omnix.net>
References: <20000328113633.A28085@cons.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

At 08.22 29/03/00 +0000, you wrote:

>In 2000 it's getting worse, for me FreeBSD is not stable at all
>the future of FreeBSD is not so clear, version follow after version but
>I still have no support for my sound board, realplayer, oracle...
>The clients are telling me to install Linux instead of FreeBSD (for
>oracle)...
>I've just finished uprading the machines to 3.4-release and you are
>telling me that there is no future for 3.X...

Argh, I came freshly from Linux (one month). Sure that Linux is full of
conforts and now has also easy graphical installer, a sort of plug and
play, the organization of "canned" type of installation without problem for
build a 80% configured workstation, but believe me: 

***just opinions

is not more stable as FreeBSD; Mandrake GUI it freeze under some cases,
Slackware is not the same system since a year, shlightly behind respect the
others, Caldera it will become a bussines, RedHat is near to plug and play
and near to become a corporation (in Italy the cd pro version costs more as
Win2000 upgrade), Debian only grants the continuity with GNU ideas. I
cannot detect when a Linux is stable and sure, lot of confusion. I *know*
that FreeBSD run better on my old system (P200mmx, 64MbRam, Sis6326).
Better performances in GUI environment, clearest possibililty of
configuration. 
It's clear also for me that: I hope that some types of software (Oracle)
become soon in FreeBSD or (better) GNU gives us valid alternatives. Hope
that the manifacturers of hardware give more chances to FreeBSD. Someone
tell that the interest of the manifacturers in Linux is justified by a
bussines evolution of Linux system. This is a horror story huh? With
instinct I choose FreeBSD and for now I be content. In the future, if
FreeBSD it fall in the powder (hope no) maybe I'll try Debian with Hurd.
But for now FreeBSD it seems me better!

***end of opinions

Regards, Fabrizio




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


From owner-freebsd-stable  Wed Mar 29  1:35:38 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from napalm.plano.sterling.com (napalm.plano.sterling.com [138.42.1.34])
	by hub.freebsd.org (Postfix) with ESMTP id 1EB9737B696
	for <stable@freebsd.org>; Wed, 29 Mar 2000 01:35:21 -0800 (PST)
	(envelope-from alan.edmonds@sterling.com)
Received: from sterling.com (vpn-215.plano.sterling.com [10.1.66.215])
	by napalm.plano.sterling.com (8.9.1b+Sun/8.9.1) with ESMTP id DAA04530;
	Wed, 29 Mar 2000 03:34:58 -0600 (CST)
Message-ID: <38E1CE23.B076403D@sterling.com>
Date: Wed, 29 Mar 2000 03:34:27 -0600
From: Alan Edmonds <alan.edmonds@sterling.com>
X-Mailer: Mozilla 4.72 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: mike ryan <mikeryan@post.harvard.edu>, stable@freebsd.org
Subject: Re: dhclient failure due to timeout limit on select
References: <20000328170541.A25874@medianstrip.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

I was just going to submit a pr for this.  I think it's a
bug in the select() routine.  At least it's not documented
as having an upper limit.  It's of type time_t or long depending.

We use QIP to manage out IP space and I have a "Manual DHCP"
address (in their terminology).  It's basically a static IP
but delivered via DHCP and an effectively infinite renewal time.

I'd hate to patch the isc-dhcp client just for FreeBSD's select,
but I guess it could be done.

Cheers,
Alan


mike ryan wrote:
> 
> observed on 4-stable, though this appears to be equally relevant on
> 3-stable and current:
> 
> select() returns EINVAL on timeouts of more than 100 million seconds
> due to an apparently arbitrary limit in itimerfix().  this causes
> dhclient to bail after obtaining a lease exceeding that limit.  my
> rcn cable modem service, for example, sets a renewal time of
> 1073741823 seconds.  while this pretty much means "don't bother
> renewing", it'd still be nice if dhclient didn't give up.
> 
> is there a reason why there needs to be a 100000000 second limit in
> select and/or itimerfix?
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-stable" in the body of the message

-- 
Alan Edmonds, KB5ZUY               Sterling Software
                                   M/S 132
Phone: +1-972-801-6485             5800 Tennyson Pkwy.
Email: alan.edmonds@sterling.com   Plano, TX, USA  75024


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


From owner-freebsd-stable  Wed Mar 29  1:40:16 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from knight.cons.org (knight.cons.org [194.233.237.86])
	by hub.freebsd.org (Postfix) with ESMTP id 2B86337C0AB
	for <freebsd-stable@FreeBSD.ORG>; Wed, 29 Mar 2000 01:40:08 -0800 (PST)
	(envelope-from cracauer@knight.cons.org)
Received: (from cracauer@localhost)
	by knight.cons.org (8.9.3/8.9.3) id LAA10114;
	Wed, 29 Mar 2000 11:39:51 +0200 (CEST)
Date: Wed, 29 Mar 2000 11:39:51 +0200
From: Martin Cracauer <cracauer@cons.org>
To: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Cc: Martin Cracauer <cracauer@cons.org>, freebsd-stable@FreeBSD.ORG
Subject: Re: Let 3.x die ASAP?
Message-ID: <20000329113951.A9935@cons.org>
References: <20000328113633.A28085@cons.org> <10681.954314958@zippy.cdrom.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0.1i
In-Reply-To: <10681.954314958@zippy.cdrom.com>; from jkh@zippy.cdrom.com on Tue, Mar 28, 2000 at 11:29:18PM -0800
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

In <10681.954314958@zippy.cdrom.com>, Jordan K. Hubbard wrote: 
> > I am so impressed with the results of upgrading my more important
> > machines to 4.0 or 4-stable that I could imagine not to produce any
> > more 3.x releases.
> 
> That may be, but we've already promised one more "capstone" for the
> 3.x branch and I think an equal or greater number of people would be
> upset not to get this.  The 3.x branch will end with 3.5 in May 2000.

I now :-) I ask you/core/WC to reconsider this decision. I want to
turn public visibility from 3.x to 4.x before any new 3.x release. I
am not against a new 3.x release as such, but "The FreeBSD" as seen by
the public must be 4.x, not 3.x.

New users seeking for their first FreeBSD release (and I count
reviewers here, too) must be directed to 4.x and we can't do that when
a 4.0 and 3.5 are in stores, they will for sure choose those release
that seems more stable.

If 3.5 goes out before or around 4.1, we will get lots of reviews for
3.5 not showing the real strength of FreeBSD, lots of new users on a
3.x system, not getting all the improvements and being forced to go
through an ugly update soon. The improvements of the Linux emulator
alone are worth the effort, since so much new Linux software comes out
these days. Just look at the games Loki has into annoucement today.
People can run most of them on FreeBSD, but inly when they choose the
right release. (BTW, Loki doesn't seem against native FreeBSD stuff as
well, you know whether someone is in contact with them?).

As another datapoint, it seems that all committers taking part in this
discussion would like to stop maintaining 3.x, for one reason or
another, and those are the people doing RELENG_3 commits. I see my
opinion supported that 3.5 will not be a substancial -if at all-
improvement over earlier 3.x releases.

Of course, we cannot ignore that WC earns a lot of money from the
stable releases and that there are quite some users who just want 3.x
and just want it on a CD, but I think that are several compromises
available:
- Release 3.5 quite some time after 4.1 and maybe name it 3.4.1 or
  such so that it is marked only as a slight upgrade for the hardcode
  3.x users.
- Release 3.5 in the lighter packaging like a snapshot CD.
- Clearly visible recommendations on the front of the CD inlet
  regarding 3.5 versus 4.1.

I don't think that WC will loose sales that way and since 3.5 will be
the last 3.x release most people won't mind a September release, IMHO.

P.S. To the other commenters in this discussion. I know that there are
a lot of very stable 3.x machines (with SMP too), I didn't doubt that.
I just say that enough parts of the system are rotten that a
substancial number of machines that runs fine unter 4.0 (and 3.[12]
for me) doesn't run well on 3.4+. Hence I think it is a must for our
reputation to turn public attention from 3.x to 4.x. Now.
-- 
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
Martin Cracauer <cracauer@cons.org> http://www.cons.org/cracauer/
  Tel.: (private) +4940 5221829 Fax.: (private) +4940 5228536


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


From owner-freebsd-stable  Wed Mar 29  1:43: 7 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from knight.cons.org (knight.cons.org [194.233.237.86])
	by hub.freebsd.org (Postfix) with ESMTP id BB96E37C158
	for <freebsd-stable@FreeBSD.ORG>; Wed, 29 Mar 2000 01:43:00 -0800 (PST)
	(envelope-from cracauer@knight.cons.org)
Received: (from cracauer@localhost)
	by knight.cons.org (8.9.3/8.9.3) id LAA10157;
	Wed, 29 Mar 2000 11:42:49 +0200 (CEST)
Date: Wed, 29 Mar 2000 11:42:48 +0200
From: Martin Cracauer <cracauer@cons.org>
To: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Cc: Martin Cracauer <cracauer@cons.org>, freebsd-stable@FreeBSD.ORG
Subject: Re: Let 3.x die ASAP?
Message-ID: <20000329114248.C9935@cons.org>
References: <20000328113633.A28085@cons.org> <10681.954314958@zippy.cdrom.com> <20000329113951.A9935@cons.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0.1i
In-Reply-To: <20000329113951.A9935@cons.org>; from cracauer@cons.org on Wed, Mar 29, 2000 at 11:39:51AM +0200
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

In <20000329113951.A9935@cons.org>, Martin Cracauer wrote: 
> In <10681.954314958@zippy.cdrom.com>, Jordan K. Hubbard wrote: 
> > > I am so impressed with the results of upgrading my more important
> > > machines to 4.0 or 4-stable that I could imagine not to produce any
> > > more 3.x releases.
> > 
> > That may be, but we've already promised one more "capstone" for the
> > 3.x branch and I think an equal or greater number of people would be
> > upset not to get this.  The 3.x branch will end with 3.5 in May 2000.
> 
> I now :-) 
    know

Grr, too early in the morning. Good start for a serious posting :-)
-- 
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
Martin Cracauer <cracauer@cons.org> http://www.cons.org/cracauer/
  Tel.: (private) +4940 5221829 Fax.: (private) +4940 5228536


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


From owner-freebsd-stable  Wed Mar 29  1:57:40 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from omnix.net (omnix.net [195.154.168.66])
	by hub.freebsd.org (Postfix) with SMTP id 4F3D837B696
	for <freebsd-stable@FreeBSD.ORG>; Wed, 29 Mar 2000 01:57:27 -0800 (PST)
	(envelope-from didier@omnix.net)
Received: (qmail 9126 invoked by uid 200); 29 Mar 2000 09:57:25 -0000
Received: from localhost (sendmail-bs@127.0.0.1)
  by localhost with SMTP; 29 Mar 2000 09:57:25 -0000
Date: Wed, 29 Mar 2000 09:57:25 +0000 (GMT)
From: Didier Derny <didier@omnix.net>
To: "Forrest W. Christian" <forrestc@iMach.com>
Cc: Martin Cracauer <cracauer@cons.org>, freebsd-stable@FreeBSD.ORG
Subject: Re: Let 3.x die ASAP?
In-Reply-To: <Pine.BSF.4.21.0003290146040.18478-100000@workhorse.iMach.com>
Message-ID: <Pine.BSF.3.96.1000329095628.9124A-100000@omnix.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


now with 3.x I have uptimes between 2/6 weeks!
with 2.x I had uptimbes between 2/6 months!

On Wed, 29 Mar 2000, Forrest W. Christian wrote:

> On Wed, 29 Mar 2000, Didier Derny wrote:
> 
> > freebsd seems running version after version and not stability...
> 
> > in 1999 (3.x) I was not so sure at all, no stability too many problems.
> 
> hmmm....
> 
> # uptime
>  1:44AM  up 46 days, 22:36, 1 user, load averages: 0.01, 0.02, 0.00
> 
> This is on a 3.4-STABLE box.   Prior to the last reboot (which I made
> because I somehow had missed compiling the kernel with an appropriate # of
> users), it had been up since 12/21/1999 when I cvsup'd it last.  
> 
> Don't let the low load averages fool you - this box is handling around
> 3000 popmail/imap3 accounts - and 100,000 messages go through it every
> day (mostly client relay).
> 
> I don't remember the last time a freebsd box crashed around here unless I
> had hardware going bad.
> 
> > In 2000 it's getting worse, for me FreeBSD is not stable at all
> > the future of FreeBSD is not so clear, version follow after version but
> > I still have no support for my sound board, realplayer, oracle...
> > The clients are telling me to install Linux instead of FreeBSD (for
> > oracle)...
> 
> Linux Oracle 8.0.5 purportedly runs great on FreeBSD 3.x.  See: 
> http://www.lf.net/lf/pi/oracle/install-linux-oracle-on-freebsd
> 
> I can't vouch for sound card support.  I gave up using sound cards in
> any unix a while back INCLUDING Linux and FreeBSD...  although I might try
> a unix box on my desktop for mbone stuff again now that it seems to be
> more stable from what I hear.   I will grant that Linux tends to support
> more obscure hardware than FreeBSD, although I have found that driver
> quality under Linux tends to be spotty.
> 
> The key to this whole thing is that in a lot of (if not most) cases,
> FreeBSD (in my opinion) runs Linux binaries better than Linux.   Turn on
> linux binary compatibility and then use linux stuff to your hearts
> content.  
> 
> I have had friends which I have been talking to about how freebsd is
> better than linux go to web conferences and hearing everyone else say "run
> everything on freebsd and use linux emulation where necessary".  This
> seems to be the trend at big web sites.
> 
> > I've just finished uprading the machines to 3.4-release and you are
> > telling me that there is no future for 3.X...
> 
> The way I read the whole topic is more like "4.x works great, and is
> stable, and people need to move there, so why drag out the lifetime of
> 3.x".   I don't recommend .0 releases at all for production work, but if
> it turns out that 4.1 is at least as stable as 3.4 or 3.5 I don't see why
> we'd need a 3.6 or 3.7 or so on.
> 
> > I'm about to buy a smp machine but I see so many horror stories on
> > the mailling lists that I'm not sure at all that I should use a smp
> > machine (or install linux instead of FreeBSD)...
> 
> Let me tell you my experience with SMP - stability depends on the
> hardware.   I have used SMP on both FreeBSD and on NetWare and on NT,
> (actually more NT than the others) and I can say that some hardware just
> won't work reliably with SMP.  I've seen Dell Multi-CPU boxes get the
> motherboard replaced THREE times before it stabilizes.   I've also seen
> machines which just couldn't run it at all.   I've seen hardware where
> NetWare blows up on but runs NT in multiprocessor mode fine.  And vice
> versa.
> 
> I'm curious as to what hardware you're having all these problems
> with.  Are you overclocking?  Is the airflow adequate?  What type of
> drives/controllers are you using? etc....   I really wonder if you've got
> some weird hardware problem which is plaguing (sp?) you.
> 
> - Forrest W. Christian (forrestc@imach.com) KD7EHZ
> ----------------------------------------------------------------------
> iMach, Ltd., P.O. Box 5749, Helena, MT 59604      http://www.imach.com
> Solutions for your high-tech problems.                  (406)-442-6648
> ----------------------------------------------------------------------
> 
> 



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


From owner-freebsd-stable  Wed Mar 29  2: 6:53 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from knight.cons.org (knight.cons.org [194.233.237.86])
	by hub.freebsd.org (Postfix) with ESMTP id 62DE637B6A2
	for <freebsd-stable@FreeBSD.ORG>; Wed, 29 Mar 2000 02:06:46 -0800 (PST)
	(envelope-from cracauer@knight.cons.org)
Received: (from cracauer@localhost)
	by knight.cons.org (8.9.3/8.9.3) id MAA10554;
	Wed, 29 Mar 2000 12:06:38 +0200 (CEST)
Date: Wed, 29 Mar 2000 12:06:38 +0200
From: Martin Cracauer <cracauer@cons.org>
To: Didier Derny <didier@omnix.net>
Cc: "Forrest W. Christian" <forrestc@iMach.com>,
	Martin Cracauer <cracauer@cons.org>, freebsd-stable@FreeBSD.ORG
Subject: Re: Let 3.x die ASAP?
Message-ID: <20000329120638.A10455@cons.org>
References: <Pine.BSF.4.21.0003290146040.18478-100000@workhorse.iMach.com> <Pine.BSF.3.96.1000329095628.9124A-100000@omnix.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0.1i
In-Reply-To: <Pine.BSF.3.96.1000329095628.9124A-100000@omnix.net>; from didier@omnix.net on Wed, Mar 29, 2000 at 09:57:25AM +0000
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

In <Pine.BSF.3.96.1000329095628.9124A-100000@omnix.net>, Didier Derny wrote: 
> 
> now with 3.x I have uptimes between 2/6 weeks!
> with 2.x I had uptimbes between 2/6 months!

I don't think that uptime wars are the right thing to decide over the
issue. 

What counts are the number of case where an upgrade to 4.x had an
instant positive effect. I have several such occasions. In one case,
the IDE hardware that crashed 3.4-stable reproducable worked under 3.1
when directly switching harddisks.

Speaking of reproduceable, why didn't I debug the issues? In all these
cases, the machines were for one reason or another not suitable for
debugging (production machines, fixed frequency monitors, hard hang
with no crashdump etc.). 3.x and especially the old wd driver wasn't
important enough for me to go through the effort on a saturday->sunday
night. It seems that other committers think on the same line and hence
I want 3.x to die soon. (Where "die" means that no new users jump on
it). 

Martin
-- 
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
Martin Cracauer <cracauer@cons.org> http://www.cons.org/cracauer/
  Tel.: (private) +4940 5221829 Fax.: (private) +4940 5228536


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


From owner-freebsd-stable  Wed Mar 29  2:11:33 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from btr0xe.rz.uni-bayreuth.de (btr0xe.rz.uni-bayreuth.de [132.180.15.14])
	by hub.freebsd.org (Postfix) with ESMTP
	id A55FB37B6A2; Wed, 29 Mar 2000 02:11:23 -0800 (PST)
	(envelope-from oliver.helmling@stud.uni-bayreuth.de)
Received: from hal.matof.de (btdial-a-109.dial.uni-bayreuth.de [132.180.246.109]) by btr0xe.rz.uni-bayreuth.de (8.8.8/8.7.3) with ESMTP id MAA11472; Wed, 29 Mar 2000 12:12:13 +0200 (MET DST)
Received: from hal.matof.de (hal.matof.de [192.168.13.2])
	by hal.matof.de (8.9.3/8.9.3) with ESMTP id MAA00494;
	Wed, 29 Mar 2000 12:16:13 +0200 (CEST)
	(envelope-from oliver.helmling@stud.uni-bayreuth.de)
Date: Wed, 29 Mar 2000 12:16:13 +0200 (CEST)
From: Oliver Helmling <oliver.helmling@stud.uni-bayreuth.de>
To: freebsd-stable@freebsd.org
Cc: freebsd-questions@freebsd.org
Subject: src for the www collection
Message-ID: <Pine.BSF.4.21.0003291118140.377-100000@hal.matof.de>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=ISO-8859-1
Content-Transfer-Encoding: 8BIT
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

hi all!

first, sorry for crossposting, but i didn't know where to put it. i've
cvsup'ed the sources for the www collection with this supfile:


# Defaults that apply to all the collections
#
# IMPORTANT: Change the next line to use one of the CVSup mirror sites
# listed at http://www.freebsd.org/handbook/mirrors.html.
*default host=cvsup2.de.FreeBSD.org
*default base=/usr/local/etc/cvsup
*default prefix=/usr
*default release=cvs tag=.
*default delete use-rel-suffix

# If your network link is a T1 or faster, comment out the following line.
*default compress

# This collection retrieves the www/ tree of the FreeBSD repository
www


now of course, i have a directory /usr/www where all the sources
are. but when make a "cd /usr/www; make" i get an error:

cd: can't cd to ../doc/en_US.ISO_8859-1
*** Error code 2

probably the prefix isn't specified correctly, but what to put in
there. i'm running apache, so i thought of /usr/local/share/apache or is
it better to put it in /usr/share

BTW: i also retrieve the doc-all collection with this supfile:

#
# prefix=/usr
#		This specifies where to place the requested files.  A
#		setting of "/usr" will place all of the files requested
#		in "/usr/doc" (e.g., "/usr/doc/en_US.ISO_8859-1").
#		The prefix directory must exist in order to run CVSup.

# Defaults that apply to all the collections
#
# IMPORTANT: Change the next line to use one of the CVSup mirror sites
# listed at http://www.freebsd.org/handbook/mirrors.html.
*default host=cvsup2.de.FreeBSD.org
*default base=/usr/local/etc/cvsup
*default prefix=/usr
*default release=cvs tag=RELENG_3
*default delete use-rel-suffix
#*default list=cvs:RELENG_3

# If your network link is a T1 or faster, comment out the following line.
*default compress

# This will retrieve the entire doc branch of the FreeBSD repository.
# This includes the handbook, FAQ, and translations thereof.
doc-all

but i never get a directory named /usr/doc?

thanks in advance

-- 

Viele Grüße
	Oliver Helmling



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


From owner-freebsd-stable  Wed Mar 29  2:12: 6 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161])
	by hub.freebsd.org (Postfix) with ESMTP id 952A237BBE5
	for <freebsd-stable@FreeBSD.ORG>; Wed, 29 Mar 2000 02:12:01 -0800 (PST)
	(envelope-from doconnor@gsoft.com.au)
Received: from cain.gsoft.com.au (doconnor@cain [203.38.152.97])
	by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id TAA00413;
	Wed, 29 Mar 2000 19:41:20 +0930 (CST)
	(envelope-from doconnor@gsoft.com.au)
Message-ID: <XFMail.000329194120.doconnor@gsoft.com.au>
X-Mailer: XFMail 1.4.0 on FreeBSD
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <Pine.BSF.3.96.1000329095628.9124A-100000@omnix.net>
Date: Wed, 29 Mar 2000 19:41:20 +0930 (CST)
From: "Daniel O'Connor" <doconnor@gsoft.com.au>
To: Didier Derny <didier@omnix.net>
Subject: Re: Let 3.x die ASAP?
Cc: freebsd-stable@FreeBSD.ORG, Martin Cracauer <cracauer@cons.org>,
	"Forrest W. Christian" <forrestc@iMach.com>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


On 29-Mar-00 Didier Derny wrote:
>  now with 3.x I have uptimes between 2/6 weeks!
>  with 2.x I had uptimbes between 2/6 months!

I had a quick look through the PR database and couldn't see your name...

Perhaps if you report your problems people will be able to fix them.

---
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
"The nice thing about standards is that there
are so many of them to choose from."
  -- Andrew Tanenbaum


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


From owner-freebsd-stable  Wed Mar 29  2:16: 9 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from TYO203.gate.nec.co.jp (TYO203.gate.nec.co.jp [202.32.8.211])
	by hub.freebsd.org (Postfix) with ESMTP id 0A42837BEB7
	for <freebsd-stable@freebsd.org>; Wed, 29 Mar 2000 02:16:05 -0800 (PST)
	(envelope-from mihara@prd.fc.nec.co.jp)
Received: from mailsv.nec.co.jp (mailsv-le1 [192.168.1.90])
	by TYO203.gate.nec.co.jp (8.9.3/3.7W00031314) with ESMTP id TAA04706;
	Wed, 29 Mar 2000 19:16:03 +0900 (JST)
Received: from elmer.prd.fc.nec.co.jp (root@elmer.prd.fc.nec.co.jp [10.32.193.1]) by mailsv.nec.co.jp (8.9.3/3.7W-MAILSV-NEC) with ESMTP
	id TAA18317; Wed, 29 Mar 2000 19:16:02 +0900 (JST)
Received: from oz.prd.fc.nec.co.jp (oz.prd.fc.nec.co.jp [10.32.193.3])
	by elmer.prd.fc.nec.co.jp (8.8.8/3.6W-00032121) with ESMTP id TAA14223;
	Wed, 29 Mar 2000 19:16:00 +0900 (JST)
Date: Wed, 29 Mar 2000 19:15:04 +0900
Message-ID: <8666u6m6af.wl@oz.prd.fc.nec.co.jp>
From: Osamu MIHARA <mihara@prd.fc.nec.co.jp>
To: mdavis@cts.com
Cc: freebsd-stable@freebsd.org
Subject: Re: 4.0-stable + SMP + fxp = device timeout
In-Reply-To: In your message of "Wed, 29 Mar 2000 01:01:27 -0800"
	<NABBLJGKKPMOKACIENPPEEGMCKAA.mdavis@cts.com>
References: <NABBLJGKKPMOKACIENPPEEGMCKAA.mdavis@cts.com>
User-Agent: Wanderlust/1.1.0 (Overjoyed) SEMI/1.13.7 (Awazu) FLIM/1.13.2 (Kasanui) MULE XEmacs/21.1 (patch 9) (Canyonlands) (i386-unknown-freebsd3.4)
Organization: NEC Corporation, Tokyo Japan
MIME-Version: 1.0 (generated by SEMI 1.13.7 - "Awazu")
Content-Type: text/plain; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

At Wed, 29 Mar 2000 01:01:27 -0800,
Morgan Davis <mdavis@cts.com> wrote:
> 
> The subject says it all.  Is this a known problem with SMP and the fxp
> driver? (Checked 4.0 errata and searched the mailing lists -- didn't see
> anything).

I have a problem on running SMP kernel on a machine with fxp, but I'm
not sure if it's related to the problem you're facing.

My problem is that while booting SMP kernel (4.0-STABLE), it hangs up
after displaying information about sio ports.  Even if I configured
the kernel removing sio device (and some other devices), the
phenomenon is still the same.  I'm not trying to remove the fxp driver
from the kernel yet...
-- 
  Osamu MIHARA // NEC Printers Division


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


From owner-freebsd-stable  Wed Mar 29  2:16:45 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from knight.cons.org (knight.cons.org [194.233.237.86])
	by hub.freebsd.org (Postfix) with ESMTP id 91E4537BA24
	for <freebsd-stable@FreeBSD.ORG>; Wed, 29 Mar 2000 02:16:41 -0800 (PST)
	(envelope-from cracauer@knight.cons.org)
Received: (from cracauer@localhost)
	by knight.cons.org (8.9.3/8.9.3) id MAA10636;
	Wed, 29 Mar 2000 12:16:32 +0200 (CEST)
Date: Wed, 29 Mar 2000 12:16:32 +0200
From: Martin Cracauer <cracauer@cons.org>
To: "Daniel O'Connor" <doconnor@gsoft.com.au>
Cc: Didier Derny <didier@omnix.net>, freebsd-stable@FreeBSD.ORG,
	Martin Cracauer <cracauer@cons.org>,
	"Forrest W. Christian" <forrestc@iMach.com>
Subject: Re: Let 3.x die ASAP?
Message-ID: <20000329121631.A10614@cons.org>
References: <Pine.BSF.3.96.1000329095628.9124A-100000@omnix.net> <XFMail.000329194120.doconnor@gsoft.com.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0.1i
In-Reply-To: <XFMail.000329194120.doconnor@gsoft.com.au>; from doconnor@gsoft.com.au on Wed, Mar 29, 2000 at 07:41:20PM +0930
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

yIn <XFMail.000329194120.doconnor@gsoft.com.au>, Daniel O'Connor wrote: 
> 
> On 29-Mar-00 Didier Derny wrote:
> >  now with 3.x I have uptimes between 2/6 weeks!
> >  with 2.x I had uptimbes between 2/6 months!
> 
> I had a quick look through the PR database and couldn't see your name...
> 
> Perhaps if you report your problems people will be able to fix them.

Isn't that a bit hard? If the crashes Didier had are anything like my
ide panics or unknown hard hangs I have, it is too hard for a normal
user to collect the data that a useful kernel PR requires. 

Martin
-- 
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
Martin Cracauer <cracauer@cons.org> http://www.cons.org/cracauer/
  Tel.: (private) +4940 5221829 Fax.: (private) +4940 5228536


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


From owner-freebsd-stable  Wed Mar 29  2:20:34 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from camelot.bitart.com (BITart-45.BITart.com [206.103.221.45])
	by hub.freebsd.org (Postfix) with SMTP id 8D88637BE1C
	for <freebsd-stable@FreeBSD.ORG>; Wed, 29 Mar 2000 02:20:29 -0800 (PST)
	(envelope-from gerti@bitart.com)
Received: (qmail 3951 invoked by uid 101); 29 Mar 2000 10:20:24 -0000
Message-ID: <20000329102024.3950.qmail@camelot.bitart.com>
Content-Type: text/plain
MIME-Version: 1.0 (NeXT Mail 4.2mach v148)
In-Reply-To: <20000328213754.L21029@fw.wintelcom.net>
X-Nextstep-Mailer: Mail 4.2mach (Enhance 2.2p1)
Received: by NeXT.Mailer (1.148)
From: Gerd Knops <gerti@bitart.com>
Date: Wed, 29 Mar 2000 04:20:24 -0600
To: Alfred Perlstein <bright@wintelcom.net>
Subject: Re: Random signal 9 (SIGKILL), please help!
Cc: gerti-freebsds@bitart.com, freebsd-stable@FreeBSD.ORG
Reply-To: gerti-freebsds@bitart.com
References: <20000329041104.3028.qmail@camelot.bitart.com>
	<20000328204948.K21029@fw.wintelcom.net>
	<20000329043747.3094.qmail@camelot.bitart.com>
	<20000328213754.L21029@fw.wintelcom.net>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Alfred Perlstein wrote:
> * Gerd Knops <gerti@bitart.com> [000328 21:03] wrote:
> > Alfred Perlstein wrote:
> > > * Gerd Knops <gerti@bitart.com> [000328 20:36] wrote:
> > > > Only on the FreeBSD systems I see that child processes occasionaly
> > > > get killed bya signal 9, and I just can't figure out why.
> > > >
> > > > Syslog does not give any indication. The machines do not swap (I
> > > > know processes mayget killed when the systems run out of swap
> > > > space). The times at which the processesare killed does seem to
> > > > be random, meaning it does not seem dome house keeping codethat
> > > > causes it.
> > > >
> > > > The processes are spawned from various daemons, and are killed
> > > > at different pointsin their existence, even when just barely
> > > > started and no resources to mention areconsumed yet.
> > > >
> > > > All processes run as root, so 'limit' should not be the cause.
> > > >
> > > > Is there anything else but the swapper that can trigger a 'signal
> > > > 9' to be sent toprocesses?
> > > >
> > > > The systems in question run a variety of versions, starting from
> > > > 3.2 Release to afairly recent (4 weeks) 3.4 stable.
> > > >
> > > This is on all the FreeBSD systems?  This is really confusing I've
> > > _never_ heard of this happening, do you have any machines built
> > > with the same _exact_ hardware exibiting the same problems or not?
> > >
> > Nope, different hardware, all Intel CPUs, some Pentium Pro, some
> > Pentium II, ASUS and Gigabyte motherboards.
> >
> > > Have you tried 4.0?  Without some sample code this is going to
> > > be very hard to reproduce.
> > >
> > The code is >50k lines of perl... No I have not tried 4.0 yet. And
> > I can not reproduce the problem either, it just randomly appears
> > at a very low rate. 23 machines running FreeBSD, and I see about 1
> > to 3 of those a day.
> >
> > > Are you sure you aren't running out of process slots?  What is
> > > maxusers set to in the kernel?
> >
> > 64.
>
> Try maybe 128?
>
> >
> > > How many processes typically run at the same time?
> > >
> > Varying, the busiest machine peaks at about 100 processes, but I
> > have seen it on machines running only 50 processes.
> >
> > Thanks for responding!
>
> I've never heard of signal 9 "by accident" and since this problem
> happens on a variety of 3.x systems 3.2-3.4 (3.4-stable also?)
> it seems really weird.
>
Yes, 3.4 stable as well.

> I don't think I can be of very much help without access to the
> code and the machines running it, as well as how it is being
> run, apache+cgi?
>
No, daemons started via a startup script which in turn is started
via rc.local.

I think I found a correlation between pid roll over (from 99999
to 0) and the spurious signals. Some program seems to keep
taps on pids that already went away, and when they 'come back' they
are killed again. I am suspicious of syslogd at the moment (I pipe
syslog output through a filter), one of the very few programs in the
base system that are running on those systems and that uses SIGKILL.

However it will probably take some time before I can wrap my head
around that code, it's not exactly heavily commented... If anyone
with more intimate knowledge could have a look I'd appreciate that.

Gerd


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


From owner-freebsd-stable  Wed Mar 29  2:22:33 2000
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 F37DD37BA24
	for <freebsd-stable@FreeBSD.ORG>; Wed, 29 Mar 2000 02:22:29 -0800 (PST)
	(envelope-from jkh@zippy.cdrom.com)
Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1])
	by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id CAA91905;
	Wed, 29 Mar 2000 02:23:25 -0800 (PST)
	(envelope-from jkh@zippy.cdrom.com)
To: Didier Derny <didier@omnix.net>
Cc: Martin Cracauer <cracauer@cons.org>, freebsd-stable@FreeBSD.ORG
Subject: Re: Let 3.x die ASAP? 
In-reply-to: Your message of "Wed, 29 Mar 2000 08:22:15 GMT."
             <Pine.BSF.3.96.1000329080220.7123A-100000@omnix.net> 
Date: Wed, 29 Mar 2000 02:23:25 -0800
Message-ID: <91902.954325405@zippy.cdrom.com>
From: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

I thought the end came for you after you started spreading the FUD the
last time.  As Winston Churchill said to Neville Chamberlain after
his highly successful trip to Munich:  "For god's sake man, GO!"

- Jordan


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


From owner-freebsd-stable  Wed Mar 29  2:23: 0 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from io.cts.com (io.cts.com [198.68.174.34])
	by hub.freebsd.org (Postfix) with ESMTP id 734B537B5E2
	for <freebsd-stable@freebsd.org>; Wed, 29 Mar 2000 02:22:57 -0800 (PST)
	(envelope-from mdavis@cts.com)
Received: from pluto (voyager.cts.com [198.68.174.38])
	by io.cts.com (8.9.3/8.9.2) with SMTP id CAA13556;
	Wed, 29 Mar 2000 02:22:46 -0800 (PST)
	(envelope-from mdavis@cts.com)
From: "Morgan Davis" <mdavis@cts.com>
To: "Osamu MIHARA" <mihara@prd.fc.nec.co.jp>
Cc: <freebsd-stable@freebsd.org>
Subject: RE: 4.0-stable + SMP + fxp = device timeout
Date: Wed, 29 Mar 2000 02:22:48 -0800
Message-ID: <NABBLJGKKPMOKACIENPPIEGNCKAA.mdavis@cts.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
In-Reply-To: <8666u6m6af.wl@oz.prd.fc.nec.co.jp>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Not the same problem here.  It'll boot up fine (lagging at network startup
items like syslogd, etc., but I can hit Control-C to cancel those and
eventually get a login prompt).  Just no network and lots of "fxp0: device
timeout" messages.  Turn off SMP in the kernel config, reboot, and all works
fine.  Never any trouble with serial ports.

Again, the important point here is that this hardware ran 3.4-stable with
SMP with no problems (for at least a year or so).  Upgraded to 4.0, and no
joy.

--Morgan

> -----Original Message-----
> From: Osamu MIHARA [mailto:mihara@prd.fc.nec.co.jp]
> Sent: Wednesday, March 29, 2000 2:15 AM
> To: mdavis@cts.com
> Cc: freebsd-stable@freebsd.org
> Subject: Re: 4.0-stable + SMP + fxp = device timeout
>
>
> At Wed, 29 Mar 2000 01:01:27 -0800,
> Morgan Davis <mdavis@cts.com> wrote:
> >
> > The subject says it all.  Is this a known problem with SMP and the fxp
> > driver? (Checked 4.0 errata and searched the mailing lists -- didn't see
> > anything).
>
> I have a problem on running SMP kernel on a machine with fxp, but I'm
> not sure if it's related to the problem you're facing.
>
> My problem is that while booting SMP kernel (4.0-STABLE), it hangs up
> after displaying information about sio ports.  Even if I configured
> the kernel removing sio device (and some other devices), the
> phenomenon is still the same.  I'm not trying to remove the fxp driver
> from the kernel yet...
> --
>   Osamu MIHARA // NEC Printers Division
>



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


From owner-freebsd-stable  Wed Mar 29  2:30:20 2000
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 105B337B6E8
	for <freebsd-stable@FreeBSD.ORG>; Wed, 29 Mar 2000 02:30:18 -0800 (PST)
	(envelope-from jkh@zippy.cdrom.com)
Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1])
	by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id CAA92017;
	Wed, 29 Mar 2000 02:31:16 -0800 (PST)
	(envelope-from jkh@zippy.cdrom.com)
To: Martin Cracauer <cracauer@cons.org>
Cc: freebsd-stable@FreeBSD.ORG
Subject: Re: Let 3.x die ASAP? 
In-reply-to: Your message of "Wed, 29 Mar 2000 11:39:51 +0200."
             <20000329113951.A9935@cons.org> 
Date: Wed, 29 Mar 2000 02:31:15 -0800
Message-ID: <92014.954325875@zippy.cdrom.com>
From: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> I now :-) I ask you/core/WC to reconsider this decision. I want to
> turn public visibility from 3.x to 4.x before any new 3.x release. I
> am not against a new 3.x release as such, but "The FreeBSD" as seen by
> the public must be 4.x, not 3.x.

Sorry, but this really isn't something I can do.  3.5 has already
essentially been promised and, as you can see, a lot of people don't
agree with your point of view at all and would view this as a very bad
move on my part.

I should also note that this has nothing whatsoever to do with CDROM
sales since I already told Walnut Creek CDROM awhile back that I would
not be doing a CDROM version of 3.5 - it will be a network-only
release.  We have enough work just placing one line of CD products
into the market and the whole 2.2.8/3.x overlap was really difficult
to map onto our existing customer base.  All customers will simply
receive 4.0, 4.1 .. 4.x.

- Jordan


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


From owner-freebsd-stable  Wed Mar 29  2:32: 8 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161])
	by hub.freebsd.org (Postfix) with ESMTP id 1A74337BBA2
	for <freebsd-stable@FreeBSD.ORG>; Wed, 29 Mar 2000 02:32:04 -0800 (PST)
	(envelope-from doconnor@gsoft.com.au)
Received: from cain.gsoft.com.au (doconnor@cain [203.38.152.97])
	by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id UAA00867;
	Wed, 29 Mar 2000 20:01:40 +0930 (CST)
	(envelope-from doconnor@gsoft.com.au)
Message-ID: <XFMail.000329200140.doconnor@gsoft.com.au>
X-Mailer: XFMail 1.4.0 on FreeBSD
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <20000329121631.A10614@cons.org>
Date: Wed, 29 Mar 2000 20:01:40 +0930 (CST)
From: "Daniel O'Connor" <doconnor@gsoft.com.au>
To: Martin Cracauer <cracauer@cons.org>
Subject: Re: Let 3.x die ASAP?
Cc: "Forrest W. Christian" <forrestc@iMach.com>,
	freebsd-stable@FreeBSD.ORG, Didier Derny <didier@omnix.net>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


On 29-Mar-00 Martin Cracauer wrote:
> > I had a quick look through the PR database and couldn't see your name...
> > Perhaps if you report your problems people will be able to fix them.
>  Isn't that a bit hard? If the crashes Didier had are anything like my
>  ide panics or unknown hard hangs I have, it is too hard for a normal
>  user to collect the data that a useful kernel PR requires. 

Well, maybe so, but if its happening every 2 or 3 weeks, I would think he
could at least create a PR, or ask for information about getting the
information needed.

If your machine IS crashing then you need to be proactive, and try and find
what is causing the problem. Try and write down stuff about the crash if you
can't get a dump etc..

---
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
"The nice thing about standards is that there
are so many of them to choose from."
  -- Andrew Tanenbaum


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


From owner-freebsd-stable  Wed Mar 29  2:35:25 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from knight.cons.org (knight.cons.org [194.233.237.86])
	by hub.freebsd.org (Postfix) with ESMTP id 2FA8F37BDA5
	for <freebsd-stable@FreeBSD.ORG>; Wed, 29 Mar 2000 02:35:22 -0800 (PST)
	(envelope-from cracauer@knight.cons.org)
Received: (from cracauer@localhost)
	by knight.cons.org (8.9.3/8.9.3) id MAA10984;
	Wed, 29 Mar 2000 12:35:16 +0200 (CEST)
Date: Wed, 29 Mar 2000 12:35:15 +0200
From: Martin Cracauer <cracauer@cons.org>
To: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Cc: Martin Cracauer <cracauer@cons.org>, freebsd-stable@FreeBSD.ORG
Subject: Re: Let 3.x die ASAP?
Message-ID: <20000329123514.B10653@cons.org>
References: <20000329113951.A9935@cons.org> <92014.954325875@zippy.cdrom.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0.1i
In-Reply-To: <92014.954325875@zippy.cdrom.com>; from jkh@zippy.cdrom.com on Wed, Mar 29, 2000 at 02:31:15AM -0800
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

In <92014.954325875@zippy.cdrom.com>, Jordan K. Hubbard wrote: 
> I should also note that this has nothing whatsoever to do with CDROM
> sales since I already told Walnut Creek CDROM awhile back that I would
> not be doing a CDROM version of 3.5 - it will be a network-only
> release.  We have enough work just placing one line of CD products
> into the market and the whole 2.2.8/3.x overlap was really difficult
> to map onto our existing customer base.  All customers will simply
> receive 4.0, 4.1 .. 4.x.

No 3.5 CDs in stores? That's all I want. Sorry, I didn't knew that.

Still would prefer a 3.4* name for the network release, but that's not
that important.

Nontheless, I will take this as given and upgrade my last 3.x machine
so that I can't do real testing on RELENG_3 anymore.

Speaking of CDs, I saw that 4.0 will be a full release (not a
snapshot-like CD), is that correct?

Martin
-- 
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
Martin Cracauer <cracauer@cons.org> http://www.cons.org/cracauer/
  Tel.: (private) +4940 5221829 Fax.: (private) +4940 5228536


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


From owner-freebsd-stable  Wed Mar 29  2:37:36 2000
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 B2F8637B539
	for <freebsd-stable@FreeBSD.ORG>; Wed, 29 Mar 2000 02:37:34 -0800 (PST)
	(envelope-from jkh@zippy.cdrom.com)
Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1])
	by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id CAA92111;
	Wed, 29 Mar 2000 02:38:25 -0800 (PST)
	(envelope-from jkh@zippy.cdrom.com)
To: Martin Cracauer <cracauer@cons.org>
Cc: freebsd-stable@FreeBSD.ORG
Subject: Re: Let 3.x die ASAP? 
In-reply-to: Your message of "Wed, 29 Mar 2000 12:35:15 +0200."
             <20000329123514.B10653@cons.org> 
Date: Wed, 29 Mar 2000 02:38:25 -0800
Message-ID: <92108.954326305@zippy.cdrom.com>
From: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> Speaking of CDs, I saw that 4.0 will be a full release (not a
> snapshot-like CD), is that correct?

It will be a full release for both the x86 and alpha architectures.

- Jordan


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


From owner-freebsd-stable  Wed Mar 29  2:44:31 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from workhorse.iMach.com (workhorse.iMach.com [206.127.77.89])
	by hub.freebsd.org (Postfix) with ESMTP id D492437B9F6
	for <freebsd-stable@FreeBSD.ORG>; Wed, 29 Mar 2000 02:44:27 -0800 (PST)
	(envelope-from forrestc@workhorse.iMach.com)
Received: from localhost (forrestc@localhost)
	by workhorse.iMach.com (8.9.3/8.9.3) with ESMTP id DAA20288;
	Wed, 29 Mar 2000 03:44:40 -0700 (MST)
Date: Wed, 29 Mar 2000 03:44:39 -0700 (MST)
From: "Forrest W. Christian" <forrestc@iMach.com>
To: Didier Derny <didier@omnix.net>
Cc: Martin Cracauer <cracauer@cons.org>, freebsd-stable@FreeBSD.ORG
Subject: Re: Let 3.x die ASAP?
In-Reply-To: <Pine.BSF.3.96.1000329095628.9124A-100000@omnix.net>
Message-ID: <Pine.BSF.4.21.0003290339320.20067-100000@workhorse.iMach.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Wed, 29 Mar 2000, Didier Derny wrote:

> now with 3.x I have uptimes between 2/6 weeks!
> with 2.x I had uptimbes between 2/6 months!

Yes and I have a box which is running 2.2.2-RELEASE and has uptimes of
between 5 and 10 days because I have a scsi drive which has decided that
it needs a power cycle every week or so. 

Could you please respond to the following part of my original message?

> > I'm curious as to what hardware you're having all these problems
> > with.  Are you overclocking?  Is the airflow adequate?  What type of
> > drives/controllers are you using? etc....   I really wonder if you've got
> > some weird hardware problem which is plaguing (sp?) you.

Maybe if you'd provide some information instead of just whining you'd find
that not only is freebsd stable, but that it's support is miles ahead of
anything else.

- Forrest W. Christian (forrestc@imach.com) KD7EHZ
----------------------------------------------------------------------
iMach, Ltd., P.O. Box 5749, Helena, MT 59604      http://www.imach.com
Solutions for your high-tech problems.                  (406)-442-6648
----------------------------------------------------------------------



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


From owner-freebsd-stable  Wed Mar 29  2:57:41 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from trinity.skynet.be (trinity.skynet.be [195.238.2.38])
	by hub.freebsd.org (Postfix) with ESMTP id 16E4E37B619
	for <freebsd-stable@FreeBSD.ORG>; Wed, 29 Mar 2000 02:57:36 -0800 (PST)
	(envelope-from blk@skynet.be)
Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121])
	by trinity.skynet.be (Postfix) with ESMTP
	id E7E7B181F2; Wed, 29 Mar 2000 12:57:00 +0200 (MET DST)
Mime-Version: 1.0
X-Sender: blk@pop.skynet.be
Message-Id: <v04220803b5078dbe3c8c@[195.238.20.81]>
In-Reply-To: <NABBLJGKKPMOKACIENPPEEGMCKAA.mdavis@cts.com>
References: <NABBLJGKKPMOKACIENPPEEGMCKAA.mdavis@cts.com>
Date: Wed, 29 Mar 2000 12:39:47 +0200
To: "Morgan Davis" <mdavis@cts.com>, <freebsd-stable@FreeBSD.ORG>
From: Brad Knowles <blk@skynet.be>
Subject: Re: 4.0-stable + SMP + fxp = device timeout
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

At 1:01 AM -0800 2000/3/29, Morgan Davis wrote:

>  The subject says it all.  Is this a known problem with SMP and the fxp
>  driver? (Checked 4.0 errata and searched the mailing lists -- didn't see
>  anything).

	Nope, this is the exact same configuration as I'm running on the 
machine that is slated to become our new USENET news spool server, 
and the machine itself seems to be completely fine.

	What I'm having problems with is the external Comparex D1400 
(Hitachi DF400) drive array....

--
   These are my opinions -- not to be taken as official Skynet policy
======================================================================
Brad Knowles, <blk@skynet.be>                || Belgacom Skynet SA/NV
Systems Architect, Mail/News/FTP/Proxy Admin || Rue Colonel Bourg, 124
Phone/Fax: +32-2-706.13.11/12.49             || B-1140 Brussels
http://www.skynet.be                         || Belgium


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


From owner-freebsd-stable  Wed Mar 29  3: 4:14 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from spiral.inspiral.net (spiral.inspiral.net [194.204.49.249])
	by hub.freebsd.org (Postfix) with ESMTP
	id 71F3237C044; Wed, 29 Mar 2000 03:03:50 -0800 (PST)
	(envelope-from mauri@inspiral.net)
Received: from aquarius (aquarius.inspiral.net [194.204.49.250])
	by spiral.inspiral.net (8.9.3/8.9.3) with ESMTP id NAA69311;
	Wed, 29 Mar 2000 13:02:52 +0300 (EEST)
	(envelope-from mauri@inspiral.net)
From: "Lauri Laupmaa" <mauri@inspiral.net>
Organization: Inspiral.Net
To: stable@freebsd.org, current@freebsd.org
Date: Wed, 29 Mar 2000 14:03:14 +0200
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: timezones/zoneinfo
Cc: support@redhat.com, support@debian.org
Message-ID: <38E20D22.17581.4939BA1@localhost>
X-mailer: Pegasus Mail for Win32 (v3.12c)
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hi

Who and when should update/fix subj. ?
Our parliament decided that estonia does not change to DST 
anymore and forgot to mention it to MS and other OS 
manufacturers :) 

so info for Europe/Tallinn is wrong and our little state is full of 
computers with wrong time :(

Help!
_____________
Lauri Laupmaa
+3725013369


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


From owner-freebsd-stable  Wed Mar 29  3:23: 5 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from infos1.casaccia.enea.it (INFOS1.casaccia.enea.it [192.107.71.175])
	by hub.freebsd.org (Postfix) with ESMTP id 67E9637B6DF
	for <freebsd-stable@FreeBSD.ORG>; Wed, 29 Mar 2000 03:22:59 -0800 (PST)
	(envelope-from poggif@casaccia.enea.it)
Received: from studi7106 (STUDI7106.casaccia.enea.it [192.107.77.106])
	by infos1.casaccia.enea.it (8.9.1/8.9.1) with SMTP id NAA12984;
	Wed, 29 Mar 2000 13:23:05 +0200 (MET DST)
Message-Id: <3.0.5.32.20000329132216.0091a1c0@infos1.casaccia.enea.it>
X-Sender: poggif@infos1.casaccia.enea.it
X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32)
Date: Wed, 29 Mar 2000 13:22:16 +0200
To: Martin Cracauer <cracauer@cons.org>
From: Fabrizio Poggi <poggif@casaccia.enea.it>
Subject: Re: Let 3.x die ASAP?
Cc: freebsd-stable@FreeBSD.ORG
In-Reply-To: <20000329113951.A9935@cons.org>
References: <10681.954314958@zippy.cdrom.com>
 <20000328113633.A28085@cons.org>
 <10681.954314958@zippy.cdrom.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 11.39 29/03/00 +0200, you wrote:


Martin says:

>- Release 3.5 in the lighter packaging like a snapshot CD.

In Italy, the movements of FreeBsd are delayed. Just now my e-mail reseller
has announced 3.4 availability as the newest release. Maybe something
lighter or not complete (like a "dependency pack") can miss at all from the
shelf. Linux is in journal stores as gift cd or in commercial libraries
near to Stephen King best seller. FreeBsd is more hard to find&buy. Bill
transactions with Walnut Creek directly, I have never experienced.

Regards, Fabrizio.


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


From owner-freebsd-stable  Wed Mar 29  3:25:10 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from smtp2.vnet.net (smtp2.vnet.net [166.82.1.32])
	by hub.freebsd.org (Postfix) with ESMTP id 4780937B6DF
	for <freebsd-stable@FreeBSD.ORG>; Wed, 29 Mar 2000 03:25:06 -0800 (PST)
	(envelope-from rivers@dignus.com)
Received: from dignus.com (ponds.vnet.net [166.82.177.48])
	by smtp2.vnet.net (8.9.1a/8.9.1) with ESMTP id GAA11793;
	Wed, 29 Mar 2000 06:24:49 -0500 (EST)
Received: from lakes.dignus.com (lakes.dignus.com [10.0.0.3])
	by dignus.com (8.9.2/8.8.5) with ESMTP id GAA20767;
	Wed, 29 Mar 2000 06:24:48 -0500 (EST)
Received: (from rivers@localhost) by lakes.dignus.com (8.9.3/8.6.9) id GAA92451; Wed, 29 Mar 2000 06:24:48 -0500 (EST)
Date: Wed, 29 Mar 2000 06:24:48 -0500 (EST)
From: Thomas David Rivers <rivers@dignus.com>
Message-Id: <200003291124.GAA92451@lakes.dignus.com>
To: cracauer@cons.org, jkh@zippy.cdrom.com
Subject: Re: Let 3.x die ASAP?
Cc: freebsd-stable@FreeBSD.ORG
In-Reply-To: <92014.954325875@zippy.cdrom.com>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> 
> > I now :-) I ask you/core/WC to reconsider this decision. I want to
> > turn public visibility from 3.x to 4.x before any new 3.x release. I
> > am not against a new 3.x release as such, but "The FreeBSD" as seen by
> > the public must be 4.x, not 3.x.
> 
> Sorry, but this really isn't something I can do.  3.5 has already
> essentially been promised and, as you can see, a lot of people don't
> agree with your point of view at all and would view this as a very bad
> move on my part.
> 
> I should also note that this has nothing whatsoever to do with CDROM
> sales since I already told Walnut Creek CDROM awhile back that I would
> not be doing a CDROM version of 3.5 - it will be a network-only
> release.  We have enough work just placing one line of CD products
> into the market and the whole 2.2.8/3.x overlap was really difficult
> to map onto our existing customer base.  All customers will simply
> receive 4.0, 4.1 .. 4.x.
> 
> - Jordan
> 

 Oh - I didn't realize things had changed again - I was expecting
 (as a subscriber) to receive a 3.5 CD-ROM...   [And, I wanted a 4.0
 CD-ROM as well...]

 So - what does one do to get a 3.5 CD-ROM?  Particularly in the
 reality of less-than-stellar network connectivity.

	- Dave Rivers -


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


From owner-freebsd-stable  Wed Mar 29  3:43: 0 2000
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 8AF1037B619
	for <freebsd-stable@FreeBSD.ORG>; Wed, 29 Mar 2000 03:42:59 -0800 (PST)
	(envelope-from jkh@zippy.cdrom.com)
Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1])
	by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id DAA92330;
	Wed, 29 Mar 2000 03:43:47 -0800 (PST)
	(envelope-from jkh@zippy.cdrom.com)
To: Thomas David Rivers <rivers@dignus.com>
Cc: cracauer@cons.org, freebsd-stable@FreeBSD.ORG
Subject: Re: Let 3.x die ASAP? 
In-reply-to: Your message of "Wed, 29 Mar 2000 06:24:48 EST."
             <200003291124.GAA92451@lakes.dignus.com> 
Date: Wed, 29 Mar 2000 03:43:47 -0800
Message-ID: <92327.954330227@zippy.cdrom.com>
From: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

>  So - what does one do to get a 3.5 CD-ROM?  Particularly in the
>  reality of less-than-stellar network connectivity.

Make one yourself, I guess. :-)  Sorry, but I simply have no plans
to create such a set myself.  The single-CD ISO is probably the
most I'll do.

- Jordan


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


From owner-freebsd-stable  Wed Mar 29  3:59:30 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from morpheus.skynet.be (morpheus.skynet.be [195.238.2.39])
	by hub.freebsd.org (Postfix) with ESMTP id 2610E37BFF7
	for <freebsd-stable@FreeBSD.ORG>; Wed, 29 Mar 2000 03:59:27 -0800 (PST)
	(envelope-from blk@skynet.be)
Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121])
	by morpheus.skynet.be (Postfix) with ESMTP
	id AD0B1DC6A; Wed, 29 Mar 2000 13:57:47 +0200 (MET DST)
Mime-Version: 1.0
X-Sender: blk@pop.skynet.be
Message-Id: <v04220809b5079d84f087@[195.238.1.121]>
In-Reply-To: <8666u6m6af.wl@oz.prd.fc.nec.co.jp>
References: <NABBLJGKKPMOKACIENPPEEGMCKAA.mdavis@cts.com>
 <8666u6m6af.wl@oz.prd.fc.nec.co.jp>
Date: Wed, 29 Mar 2000 13:47:18 +0200
To: Osamu MIHARA <mihara@prd.fc.nec.co.jp>, mdavis@cts.com
From: Brad Knowles <blk@skynet.be>
Subject: Re: 4.0-stable + SMP + fxp = device timeout
Cc: freebsd-stable@FreeBSD.ORG
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

At 7:15 PM +0900 2000/3/29, Osamu MIHARA wrote:

>  My problem is that while booting SMP kernel (4.0-STABLE), it hangs up
>  after displaying information about sio ports.  Even if I configured
>  the kernel removing sio device (and some other devices), the
>  phenomenon is still the same.

	IIRC, sio is the serial driver.  At least on first glance, this 
problem would appear to be unrelated to the fxp driver, and perhaps 
some misconfiguration of your motherboard or perhaps the BIOS or 
IRQs, etc....

--
   These are my opinions -- not to be taken as official Skynet policy
======================================================================
Brad Knowles, <blk@skynet.be>                || Belgacom Skynet SA/NV
Systems Architect, Mail/News/FTP/Proxy Admin || Rue Colonel Bourg, 124
Phone/Fax: +32-2-706.13.11/12.49             || B-1140 Brussels
http://www.skynet.be                         || Belgium


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


From owner-freebsd-stable  Wed Mar 29  4: 1:15 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from morpheus.skynet.be (morpheus.skynet.be [195.238.2.39])
	by hub.freebsd.org (Postfix) with ESMTP id 13B2937C11B
	for <freebsd-stable@FreeBSD.ORG>; Wed, 29 Mar 2000 04:01:01 -0800 (PST)
	(envelope-from blk@skynet.be)
Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121])
	by morpheus.skynet.be (Postfix) with ESMTP
	id 619B4DAE4; Wed, 29 Mar 2000 13:57:53 +0200 (MET DST)
Mime-Version: 1.0
X-Sender: blk@pop.skynet.be
Message-Id: <v0422080ab5079de206d6@[195.238.1.121]>
In-Reply-To: <20000329121631.A10614@cons.org>
References: <Pine.BSF.3.96.1000329095628.9124A-100000@omnix.net>
 <XFMail.000329194120.doconnor@gsoft.com.au>
 <20000329121631.A10614@cons.org>
Date: Wed, 29 Mar 2000 13:55:52 +0200
To: Martin Cracauer <cracauer@cons.org>,
	"Daniel O'Connor" <doconnor@gsoft.com.au>
From: Brad Knowles <blk@skynet.be>
Subject: Re: Let 3.x die ASAP?
Cc: Didier Derny <didier@omnix.net>, freebsd-stable@FreeBSD.ORG,
	Martin Cracauer <cracauer@cons.org>,
	"Forrest W. Christian" <forrestc@iMach.com>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

At 12:16 PM +0200 2000/3/29, Martin Cracauer wrote:

>  Isn't that a bit hard? If the crashes Didier had are anything like my
>  ide panics or unknown hard hangs I have, it is too hard for a normal
>  user to collect the data that a useful kernel PR requires.

	What other solution would you have us implement?!?

	Do you really honestly expect us to go around reading everyone's 
mind?  Do you really honestly expect us to fly out on a moment's 
notice with a brand-new replacement system that has been completely 
tested in an exact replica of your configuration and confirmed as 
working perfectly and will result in multi-century uptimes if you let 
it, so that we can then take the offending machine back and figure 
out what we did wrong?


	Just how exactly do you propose that we actually fix your problem 
if you don't bloody tell us about it?!?


	Thank you, we're just a bunch of unpaid volunteers here, and no 
commercial vendor on the planet I know of could do any better with 
fixing your problem if you don't tell them about it.

	You've already got access to a support network that (IMO) is 
superior in virtually every way to any support you'd get from a 
commercial vendor, but this support network does require a certain 
minimum amount of effort on your part -- you have to tell us about 
the problem.

	And while you're at it, please keep in mind that you're not 
paying a single penny for this support network that you're 
complaining about.

--
   These are my opinions -- not to be taken as official Skynet policy
======================================================================
Brad Knowles, <blk@skynet.be>                || Belgacom Skynet SA/NV
Systems Architect, Mail/News/FTP/Proxy Admin || Rue Colonel Bourg, 124
Phone/Fax: +32-2-706.13.11/12.49             || B-1140 Brussels
http://www.skynet.be                         || Belgium


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


From owner-freebsd-stable  Wed Mar 29  4:13: 7 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from knight.cons.org (knight.cons.org [194.233.237.86])
	by hub.freebsd.org (Postfix) with ESMTP id 65AA837BCF9
	for <freebsd-stable@FreeBSD.ORG>; Wed, 29 Mar 2000 04:13:01 -0800 (PST)
	(envelope-from cracauer@knight.cons.org)
Received: (from cracauer@localhost)
	by knight.cons.org (8.9.3/8.9.3) id OAA12047;
	Wed, 29 Mar 2000 14:12:54 +0200 (CEST)
Date: Wed, 29 Mar 2000 14:12:53 +0200
From: Martin Cracauer <cracauer@cons.org>
To: Thomas David Rivers <rivers@dignus.com>
Cc: cracauer@cons.org, freebsd-stable@FreeBSD.ORG
Subject: Re: Let 3.x die ASAP?
Message-ID: <20000329141253.A12012@cons.org>
References: <92014.954325875@zippy.cdrom.com> <200003291124.GAA92451@lakes.dignus.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0.1i
In-Reply-To: <200003291124.GAA92451@lakes.dignus.com>; from rivers@dignus.com on Wed, Mar 29, 2000 at 06:24:48AM -0500
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

In <200003291124.GAA92451@lakes.dignus.com>, Thomas David Rivers wrote: 
>  So - what does one do to get a 3.5 CD-ROM?  Particularly in the
>  reality of less-than-stellar network connectivity.

I would highly prefer to build'n'burn a 3.5 CD for you than to be
forced to maintain RELENG_3 by a widespread CD release.

[I'm serious, remind me when the time comes]

Martin
-- 
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
Martin Cracauer <cracauer@cons.org> http://www.cons.org/cracauer/
  Tel.: (private) +4940 5221829 Fax.: (private) +4940 5228536


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


From owner-freebsd-stable  Wed Mar 29  4:32:57 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from paprika.michvhf.com (paprika.michvhf.com [209.103.136.12])
	by hub.freebsd.org (Postfix) with SMTP id A19F037B619
	for <freebsd-stable@FreeBSD.ORG>; Wed, 29 Mar 2000 04:32:49 -0800 (PST)
	(envelope-from vev@michvhf.com)
Received: (qmail 5581 invoked by uid 1001); 29 Mar 2000 12:32:49 -0000
Date: Wed, 29 Mar 2000 07:32:49 -0500 (EST)
From: Vince Vielhaber <vev@michvhf.com>
To: freebsd-stable@FreeBSD.ORG
Cc: jkh@zippy.cdrom.com
Subject: Re: Let 3.x die ASAP?
In-Reply-To: <200003291124.GAA92451@lakes.dignus.com>
Message-ID: <Pine.BSF.4.05.10003290731130.5357-100000@paprika.michvhf.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


> > I should also note that this has nothing whatsoever to do with CDROM
> > sales since I already told Walnut Creek CDROM awhile back that I would
> > not be doing a CDROM version of 3.5 - it will be a network-only
> > release.  We have enough work just placing one line of CD products
> > into the market and the whole 2.2.8/3.x overlap was really difficult
> > to map onto our existing customer base.  All customers will simply
> > receive 4.0, 4.1 .. 4.x.

What about another toolkit release?   Say 3.5, 4.snap and 5.snap?

Vince.
-- 
==========================================================================
Vince Vielhaber -- KA8CSH    email: vev@michvhf.com    http://www.pop4.net
   128K ISDN: $24.95/mo or less - 56K Dialup: $17.95/mo or less at Pop4
        Online Campground Directory    http://www.camping-usa.com
       Online Giftshop Superstore    http://www.cloudninegifts.com
==========================================================================





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


From owner-freebsd-stable  Wed Mar 29  4:43:58 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from smtp1.vnet.net (smtp1.vnet.net [166.82.1.31])
	by hub.freebsd.org (Postfix) with ESMTP id 695F537BE1C
	for <freebsd-stable@FreeBSD.ORG>; Wed, 29 Mar 2000 04:43:44 -0800 (PST)
	(envelope-from rivers@dignus.com)
Received: from dignus.com (ponds.vnet.net [166.82.177.48])
	by smtp1.vnet.net (8.9.1a/8.9.1) with ESMTP id HAA26468;
	Wed, 29 Mar 2000 07:43:38 -0500 (EST)
Received: from lakes.dignus.com (lakes.dignus.com [10.0.0.3])
	by dignus.com (8.9.2/8.8.5) with ESMTP id HAA20901;
	Wed, 29 Mar 2000 07:43:36 -0500 (EST)
Received: (from rivers@localhost) by lakes.dignus.com (8.9.3/8.6.9) id HAA92704; Wed, 29 Mar 2000 07:43:31 -0500 (EST)
Date: Wed, 29 Mar 2000 07:43:31 -0500 (EST)
From: Thomas David Rivers <rivers@dignus.com>
Message-Id: <200003291243.HAA92704@lakes.dignus.com>
To: jkh@zippy.cdrom.com, rivers@dignus.com
Subject: Re: Let 3.x die ASAP?
Cc: cracauer@cons.org, freebsd-stable@FreeBSD.ORG
In-Reply-To: <92327.954330227@zippy.cdrom.com>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> 
> >  So - what does one do to get a 3.5 CD-ROM?  Particularly in the
> >  reality of less-than-stellar network connectivity.
> 
> Make one yourself, I guess. :-)  Sorry, but I simply have no plans
> to create such a set myself.  The single-CD ISO is probably the
> most I'll do.
> 
> - Jordan
> 

 That's fine.. I suppose...

 Except, of course, the entire reason I subscribe to the CDs is because
 I can't (easily) make them myself.   I'm sure there is a (possibly small)
 percentage of subscribers who would be in a similar situation.

 Which, for me, probably means there is no 3.5 and I need to investigate
 moving to 4.x sooner.

 That's not necessarily bad, by any means - you should probably
 make an announcement of some kind so others in situations similar to
 mine can be informed and make reasonable decisions.

	- Dave Rivers -


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


From owner-freebsd-stable  Wed Mar 29  4:53:14 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from omnix.net (omnix.net [195.154.168.66])
	by hub.freebsd.org (Postfix) with SMTP id B4EEC37BC81
	for <freebsd-stable@FreeBSD.ORG>; Wed, 29 Mar 2000 04:53:11 -0800 (PST)
	(envelope-from didier@omnix.net)
Received: (qmail 11411 invoked by uid 200); 29 Mar 2000 12:53:10 -0000
Received: from localhost (sendmail-bs@127.0.0.1)
  by localhost with SMTP; 29 Mar 2000 12:53:10 -0000
Date: Wed, 29 Mar 2000 12:53:09 +0000 (GMT)
From: Didier Derny <didier@omnix.net>
To: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Cc: Martin Cracauer <cracauer@cons.org>, freebsd-stable@FreeBSD.ORG
Subject: Re: Let 3.x die ASAP? 
In-Reply-To: <91902.954325405@zippy.cdrom.com>
Message-ID: <Pine.BSF.3.96.1000329125255.11404A-100000@omnix.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

I stuck with freebsd for at least a year

On Wed, 29 Mar 2000, Jordan K. Hubbard wrote:

> I thought the end came for you after you started spreading the FUD the
> last time.  As Winston Churchill said to Neville Chamberlain after
> his highly successful trip to Munich:  "For god's sake man, GO!"
> 
> - Jordan
> 



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


From owner-freebsd-stable  Wed Mar 29  5: 8: 0 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from TYO202.gate.nec.co.jp (TYO202.gate.nec.co.jp [202.247.6.41])
	by hub.freebsd.org (Postfix) with ESMTP id 6E7CC37BB99
	for <freebsd-stable@FreeBSD.ORG>; Wed, 29 Mar 2000 05:07:56 -0800 (PST)
	(envelope-from mihara@prd.fc.nec.co.jp)
Received: from mailsv4.nec.co.jp (mailsv4-le1 [192.168.1.93])
	by TYO202.gate.nec.co.jp (8.9.3/3.7W00031314) with ESMTP id WAA04055;
	Wed, 29 Mar 2000 22:07:53 +0900 (JST)
Received: from elmer.prd.fc.nec.co.jp (root@elmer.prd.fc.nec.co.jp [10.32.193.1]) by mailsv4.nec.co.jp (8.9.3/3.7W-MAILSV4-NEC) with ESMTP
	id WAA12775; Wed, 29 Mar 2000 22:07:53 +0900 (JST)
Received: from oz.prd.fc.nec.co.jp (oz.prd.fc.nec.co.jp [10.32.193.3])
	by elmer.prd.fc.nec.co.jp (8.8.8/3.6W-00032121) with ESMTP id WAA16265;
	Wed, 29 Mar 2000 22:07:52 +0900 (JST)
Date: Wed, 29 Mar 2000 22:06:55 +0900
Message-ID: <86snxaexhs.wl@oz.prd.fc.nec.co.jp>
From: Osamu MIHARA <mihara@prd.fc.nec.co.jp>
To: blk@skynet.be
Cc: mdavis@cts.com, freebsd-stable@FreeBSD.ORG
Subject: Re: 4.0-stable + SMP + fxp = device timeout
In-Reply-To: In your message of "Wed, 29 Mar 2000 13:47:18 +0200"
	<v04220809b5079d84f087@[195.238.1.121]>
References: <NABBLJGKKPMOKACIENPPEEGMCKAA.mdavis@cts.com>
	<8666u6m6af.wl@oz.prd.fc.nec.co.jp>
	<v04220809b5079d84f087@[195.238.1.121]>
User-Agent: Wanderlust/1.1.0 (Overjoyed) SEMI/1.13.7 (Awazu) FLIM/1.13.2 (Kasanui) MULE XEmacs/21.1 (patch 9) (Canyonlands) (i386-unknown-freebsd3.4)
Organization: NEC Corporation, Tokyo Japan
MIME-Version: 1.0 (generated by SEMI 1.13.7 - "Awazu")
Content-Type: text/plain; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

At Wed, 29 Mar 2000 13:47:18 +0200,
Brad Knowles <blk@skynet.be> wrote:
> 
> At 7:15 PM +0900 2000/3/29, Osamu MIHARA wrote:
> 
> >  My problem is that while booting SMP kernel (4.0-STABLE), it hangs up
> >  after displaying information about sio ports.  Even if I configured
> >  the kernel removing sio device (and some other devices), the
> >  phenomenon is still the same.
> 
> 	IIRC, sio is the serial driver.  At least on first glance, this 
> problem would appear to be unrelated to the fxp driver, and perhaps 
> some misconfiguration of your motherboard or perhaps the BIOS or 
> IRQs, etc....

UP Kernel works just fine, so I'm thinking that it's not a
configuration problem.

Is there any good guide for running SMP kernel (or  for debugging
SMP kernel?)  I know the FreeBSD's SMP page, but couldn't find
solutions yet.
-- 
  Osamu MIHARA // NEC Printers Division


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


From owner-freebsd-stable  Wed Mar 29  5:13: 9 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from servo.ccr.org (servo.ccr.org [198.3.0.2])
	by hub.freebsd.org (Postfix) with ESMTP id 7002D37B615
	for <freebsd-stable@FreeBSD.ORG>; Wed, 29 Mar 2000 05:12:55 -0800 (PST)
	(envelope-from mo@servo.ccr.org)
Received: from servo.ccr.org (localhost [127.0.0.1])
	by servo.ccr.org (8.9.2/8.9.2) with ESMTP id IAA26646;
	Wed, 29 Mar 2000 08:12:45 -0500 (EST)
	(envelope-from mo@servo.ccr.org)
Message-Id: <200003291312.IAA26646@servo.ccr.org>
To: Martin Cracauer <cracauer@cons.org>
Cc: Didier Derny <didier@omnix.net>,
	"Forrest W. Christian" <forrestc@iMach.com>,
	freebsd-stable@FreeBSD.ORG
Subject: Re: Let 3.x die ASAP? 
In-reply-to: Your message of "Wed, 29 Mar 2000 12:06:38 +0200."
             <20000329120638.A10455@cons.org> 
Date: Wed, 29 Mar 2000 08:12:44 -0500
From: "Mike O'Dell" <mo@servo.ccr.org>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


the number of cases where things get worse going to 4.0 is
even more important than the number of systems that get better.

an old but reliable rule in business: 1 bad user experience is more
powerful that 10 good user experiences

or

It takes 10 happy users to repair the damage done by one unhappy user.

it's very true.

what I'd like to see is to stop "improving" FreeBSD and
get it stable, and get it working on the real hardware
in the field.  all these answers of "gee, it must be your
hardware - buy a new computer" isn't gonna fly with the
people you wish to impress.

if this effort doesn't stop rocketing along, utterly out of control,
and focus on getting the thing ROCK SOLID on the hardware that's out
there, this effort is utterly doomed to a long, painful, flaming
death.

yes, I'll get flamed for this reality check, but you're
just in denial and screaming at the messenger.

This effort has been breathing its own gas for way too long
and denying the efforts and successes of others out
of raw religiosity.

so the life you save may be your own.

stop polishing a smaller and smaller doorknob,
focus on getting the system stable on the hardware
that's out there, and stop making excuses about how
unworthy so many of the supplicants are.

Otherwise, this is going to be relegated to a
very small footnote in history.

And in the words of Dennis Miller,
"It's just my opinion - I might be wrong."

	-mo


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


From owner-freebsd-stable  Wed Mar 29  5:31:53 2000
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 E5EA637B726
	for <freebsd-stable@freebsd.org>; Wed, 29 Mar 2000 05:31:49 -0800 (PST)
	(envelope-from dwmalone@maths.tcd.ie)
Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP
          id <aa00207@salmon>; 29 Mar 2000 14:31:48 +0100 (BST)
Date: Wed, 29 Mar 2000 14:31:48 +0100
From: David Malone <dwmalone@maths.tcd.ie>
To: gerti-freebsds@bitart.com
Cc: Alfred Perlstein <bright@wintelcom.net>,
	freebsd-stable@FreeBSD.ORG
Subject: Re: Random signal 9 (SIGKILL), please help!
Message-ID: <20000329143148.A25616@walton.maths.tcd.ie>
References: <20000329041104.3028.qmail@camelot.bitart.com> <20000328204948.K21029@fw.wintelcom.net> <20000329043747.3094.qmail@camelot.bitart.com> <20000328213754.L21029@fw.wintelcom.net> <20000329102024.3950.qmail@camelot.bitart.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0.1i
In-Reply-To: <20000329102024.3950.qmail@camelot.bitart.com>; from gerti@bitart.com on Wed, Mar 29, 2000 at 04:20:24AM -0600
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Wed, Mar 29, 2000 at 04:20:24AM -0600, Gerd Knops wrote:

> I think I found a correlation between pid roll over (from 99999
> to 0) and the spurious signals. Some program seems to keep
> taps on pids that already went away, and when they 'come back' they
> are killed again. I am suspicious of syslogd at the moment (I pipe
> syslog output through a filter), one of the very few programs in the
> base system that are running on those systems and that uses SIGKILL.

You could try doing:

	ktrace -t s -p $pid

on syslogd and then checking to see if the signals it sends corrisponds
to the SIGKILL your processes get. (Providing you have times for them).

	David.


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


From owner-freebsd-stable  Wed Mar 29  5:47: 6 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from techpower.net (techpower.net [205.133.231.1])
	by hub.freebsd.org (Postfix) with ESMTP id BB18037B68F
	for <freebsd-stable@FreeBSD.ORG>; Wed, 29 Mar 2000 05:47:02 -0800 (PST)
	(envelope-from hometeam@techpower.net)
Received: from localhost (hometeam@localhost)
	by techpower.net (8.9.3/8.9.3) with ESMTP id IAA03542;
	Wed, 29 Mar 2000 08:53:38 -0500 (EST)
	(envelope-from hometeam@techpower.net)
Date: Wed, 29 Mar 2000 08:53:38 -0500 (EST)
From: hometeam <hometeam@techpower.net>
To: Gawel <gawel@sim.com.pl>
Cc: Eric Jacoboni <jaco@titine.fr.eu.org>,
	Grigoriy Strokin <grg@philol.msu.ru>, freebsd-stable@FreeBSD.ORG
Subject: Re: New kernel with its ATA drivers damages the filesystem
In-Reply-To: <38E1D32B.F946EEB8@sim.com.pl>
Message-ID: <Pine.BSF.4.21.0003290849210.3533-100000@techpower.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=X-UNKNOWN
Content-Transfer-Encoding: QUOTED-PRINTABLE
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


I agree this really should be fix ...I notcied this straight away and sent
mail to the group...Now it is damaging file Systems after the fact and
wiping out file systems... I mean change the
hardware ??? Why not fix the driver ?

Not everyone has a big money tree growing in there back yard..


On Wed, 29 Mar 2000, Gawel wrote:

> Hello,
> The same message ( ata0: resetting devices .. done; ad0: WRITE command
> timeout - resetting)
> has appeared to me but during instalation 4.0R form CDROM.
> I have no idea how to install 4.0 on my PC.
> Is there any trick to switch on hw.atamodes=3Dpio,pio,pio during instalat=
ion
> from CD?
>=20
> With regards,
> Gawel
>=20
> Eric Jacoboni wrote:
>=20
> > Grigoriy Strokin <grg@philol.msu.ru> writes:
> >
> > > Mar 28 17:49:07 koch2 /kernel: ed0: device timeout
> > > Mar 28 17:49:07 koch2 /kernel: ed0: device timeout
> > > Mar 28 17:49:07 koch2 /kernel: ata0: resetting devices .. done
> > > Mar 28 17:49:48 koch2 /kernel: ad0: WRITE command timeout - resetting
> > > Mar 28 17:49:48 koch2 /kernel: ata0: resetting devices .. done
> >
> > > Now I think I don't know where to find the source of the problem.
> >
> > Have you tried what the ata manpage suggests ?
> >
> > I've had the same problem, it's now fixed with the following line
> > added in my /etc/rc.local :
> >
> > /sbin/sysctl -w hw.atamodes=3Dpio,pio,pio
> >
> > (i've 2 ide disks + an ATAPI cdrom).
> > --
> > ---------------------------------------------------------
> > =C9ric Jacoboni       =AB No sport, cigars! =BB  (W. Churchill)
> > ---------------------------------------------------------
> >
> > To Unsubscribe: send mail to majordomo@FreeBSD.org
> > with "unsubscribe freebsd-stable" in the body of the message
>=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 29  5:50: 3 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from mail.rdc1.wa.home.com (ha1.rdc1.wa.home.com [24.0.2.66])
	by hub.freebsd.org (Postfix) with ESMTP id 7803A37B55A
	for <freebsd-stable@FreeBSD.ORG>; Wed, 29 Mar 2000 05:49:56 -0800 (PST)
	(envelope-from drunkle@home.com)
Received: from xb.fiddi.com ([24.0.234.124]) by mail.rdc1.wa.home.com
          (InterMail v4.01.01.00 201-229-111) with ESMTP
          id <20000329134956.CTB1875.mail.rdc1.wa.home.com@xb.fiddi.com>
          for <freebsd-stable@FreeBSD.ORG>; Wed, 29 Mar 2000 05:49:56 -0800
Received: from localhost (dave@localhost)
	by xb.fiddi.com (8.9.3/8.9.3) with ESMTP id FAA94885
	for <freebsd-stable@FreeBSD.ORG>; Wed, 29 Mar 2000 05:57:17 -0800 (PST)
X-Authentication-Warning: xb.fiddi.com: dave owned process doing -bs
Date: Wed, 29 Mar 2000 05:57:17 -0800 (PST)
From: Dave Runkle <drunkle@home.com>
X-Sender: dave@xb.fiddi.com
To: freebsd-stable@FreeBSD.ORG
Subject: RELENG_4 'make -DNOINFO installworld' SIGNAL 12 on install of 'test'
In-Reply-To: <20000328.22565900@bartequi.ottodomain.org>
Message-ID: <Pine.BSF.4.10.10003281941380.92115-100000@xb.fiddi.com>
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 did a successful 3.2 to 3.4 last week, now on a 4.0 build
I've been Stopped at the make -DNOINFO installworld' stage. I
followed UPDATING with the exception of doing a '/bin/sh MAKEDEV
all', and the other exception is doing a 'mergemaster' of /etc.

The kernel process went well, although it seems that contrary to
UPDATING saying to manually do the kernel install, it was done by
'installkernel' as part of that script. So I did not have to do that
part. The new kernel is sitting, ready to boot.

I've supped src-all, cvs-crypto, ports-all, doc-all for this.

Now I am sitting in single, afraid to reboot, not knowing what to do
next.

Notice the 
"/usr/src/Makefile", line 101: warning: "LC_TIME=C date" returned non-zero status
. I tried to do the installworld again and it returned that warning.
I've got a screwy clock on this box, timekeeping is very slow,
behind. I set the clock ahead so that there might not be a problem
of trying to write something if time was 'backward'.

I've found another fellow in here that had the same problem, failure
at 'test'. He said that he could boot his 4 kernel but his 3.4
kernel would not boot. So I am not sure that I can boot 3.4 and be
using some of the 4. resources that were installed.

How far am I through the installworld at this point? Could I have
enough of /bin installed that I can boot 4.0, get going in that and
then track RELENG_4 again to finish off the install? I have merged
/etc, as stated above, as well as done a 'MAKEDEV all'.

Please, any ideas and/or help will be appreciated!
Thanks,
Dave

--------
here are excerpts from the script. (There may be typos as I typed
this in by hand.)
--

# cd /usr/src
# make -DNOINFO installworld
cd /usr/src: MAKEOBJDIRPREFIX=/usr/obj  COMPILER_PATH=/usr/obj/usr/src/i386/usr/
libexec:/usr/obj/usr/src/i386/usr/bin  LIBRARY_PATH=/usr/obj/usr/src/i386/usr/li
b:/usr/obj/usr/src/i386/usr/lib  OBJFORMAT_PATH=/usr/obj/usr/src/i386/usr/libexe
c  PERL5LIB=/usr/obj/usr/src/i386/usr/libdata/perl/5.00503 make -f Makefile.inc1
 reinstall
--------------------------------------------------------------
>>> Making hierarchy
--------------------------------------------------------------
cd /usr/src/: make -f Makefile.inc1 hierarchy

  [ snip ]

--------------------------------------------------------------
>>> Installing everything..
--------------------------------------------------------------
cd /usr/src: make -f Makefile.inc1 install
===> share/info
===> include

  [ snip ]

===> bin/pwd
install -c -s -o root -g wheel -m 555   pwd /bin
install -c -o root -g wheel -m 444 pwd.1.gz  /usr/share/man/man1
===> bin/rcp
install -c -s -o root -g wheel -m 4555  -fschg rcp /bin
install -c -o root -g wheel -m 444 rcp.1.gz  /usr/share/man/man1
===> bin/rm
install -c -s -o root -g wheel -m 555   rm /bin
/bin/unlink -> /bin/rm
install -c -o root -g wheel -m 444 rm.1.gz  /usr/share/man/man1
/usr/share/man/man1/unlink.1.gz -> /usr/share/man/man1/rm.1.gz
===> bin/rmdir
install -c -s -o root -g wheel -m 555   rmdir /bin
install -c -o root -g wheel -m 444 rmdir.1.gz  /usr/share/man/man1
===> bin/sh
install -c -s -o root -g wheel -m 555   sh /bin
install -c -o root -g wheel -m 444 sh.1.gz  /usr/share/man/man1
===> bin/sleep
install -c -s -o root -g wheel -m 555   sleep /bin
install -c -o root -g wheel -m 444 sleep.1.gz  /usr/share/man/man1
===> bin/stty
install -c -s -o root -g wheel -m 555   stty /bin
install -c -o root -g wheel -m 444 stty.1.gz  /usr/share/man/man1
===> bin/sync
install -c -s -o root -g wheel -m 555   sync /bin
install -c -o root -g wheel -m 444 sync.8.gz  /usr/share/man/man8
===> bin/test
install -c -s -o root -g wheel -m 555   test /bin
*** Signal 12

Stop.
*** Error code 1

Stop.
*** Error code 1

Stop.
*** Error code 1

Stop.
*** Error code 1

Stop.
*** Error code 1

Stop.
# make -DNOINFO installworld
pid 57994 (sh), uid 0: exited on signal 12 (core dumped)
"/usr/src/Makefile", line 101: warning: "LC_TIME=C date" returned non-zero status
pid 57995 (sh), uid 0: exited on signal 12 (core dumped)
*** Signal 12

Stop.
#uname -a
FreeBSD vmbsd32.fiddi.com 3.4-STABLE FreeBSD 3.4-STABLE #0: Fri Mar 24 04:55:07
PST 2000     root@vmbsd32.fiddi.com:/usr/src/sys/compile/VMFIDDI i386
#
# ps
ps: proc size mismatch (6408 total, 1044 chunks)
# ls -l /usr/obj/usr/src/bin/test
total 564
-rw-r--r--  1 root  wheel    1052 Mar 26 19:25 .depend
-rw-------  1 root  wheel  212992 Mar 27 22:56 sh.core
-rwxr-xr-x  1 root  wheel   54349 Mar 26 19:57 test
-rw-r--r--  1 root  wheel    2635 Mar 26 19:57 test.1.gz
-rw-r--r--  1 root  wheel    6428 Mar 26 19:57 test.o
#








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


From owner-freebsd-stable  Wed Mar 29  5:54:34 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from www.kpi.com.au (www.kpi.com.au [203.39.132.210])
	by hub.freebsd.org (Postfix) with ESMTP id 009BE37B692
	for <FreeBSD-Stable@FreeBSD.ORG>; Wed, 29 Mar 2000 05:54:29 -0800 (PST)
	(envelope-from johnsa@kpi.com.au)
Received: from sleek (pAc6.hbt.southcom.com.au [203.60.23.199])
	by www.kpi.com.au (8.9.3/8.9.3) with SMTP id XAA40183
	for <FreeBSD-Stable@FreeBSD.ORG>; Wed, 29 Mar 2000 23:57:01 +1000 (EST)
	(envelope-from johnsa@kpi.com.au)
Message-ID: <006a01bf9986$6cba9da0$b564a8c0@sleek>
From: "Andrew Johns" <johnsa@kpi.com.au>
To: <FreeBSD-Stable@FreeBSD.ORG>
References: <200003291312.IAA26646@servo.ccr.org>
Subject: Re: Let 3.x die ASAP? 
Date: Wed, 29 Mar 2000 23:48:02 +1000
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.6600
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

<rant>
I know it's (loosely) about stable, but can't you guys swing
this to -chat?  I am **sick** of instantly deleting this junk
from my mailbox.

If anything useful to the rest of us comes out of it, post
back here then.
</rant>

My 5c worth (no 1c or 2c currency in Aust :))

Regards to all developers for such a decent product.
--
Andrew Johns BSc.
Principal Consultant
KPI Logistics Pty. Ltd.




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


From owner-freebsd-stable  Wed Mar 29  6: 2:11 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13])
	by hub.freebsd.org (Postfix) with ESMTP id 4216937C1B3
	for <freebsd-stable@freebsd.org>; Wed, 29 Mar 2000 06:02:02 -0800 (PST)
	(envelope-from ben@scientia.demon.co.uk)
Received: from strontium.scientia.demon.co.uk ([192.168.91.36] ident=exim)
	by scientia.demon.co.uk with esmtp (Exim 3.12 #1)
	id 12aHih-000F7P-00; Wed, 29 Mar 2000 13:37:11 +0100
Received: (from ben) by strontium.scientia.demon.co.uk (Exim 3.12 #7)
	id 12aHig-0008Dc-00; Wed, 29 Mar 2000 13:37:10 +0100
Date: Wed, 29 Mar 2000 13:37:10 +0100
From: Ben Smithurst <ben@scientia.demon.co.uk>
To: gerti-freebsds@bitart.com
Cc: Alfred Perlstein <bright@wintelcom.net>,
	freebsd-stable@FreeBSD.ORG
Subject: Re: Random signal 9 (SIGKILL), please help!
Message-ID: <20000329133710.E96553@strontium.scientia.demon.co.uk>
References: <20000329041104.3028.qmail@camelot.bitart.com> <20000328204948.K21029@fw.wintelcom.net> <20000329043747.3094.qmail@camelot.bitart.com> <20000328213754.L21029@fw.wintelcom.net> <20000329102024.3950.qmail@camelot.bitart.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0i
In-Reply-To: <20000329102024.3950.qmail@camelot.bitart.com>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Gerd Knops wrote:

> I think I found a correlation between pid roll over (from 99999
> to 0) and the spurious signals. Some program seems to keep
> taps on pids that already went away, and when they 'come back' they
> are killed again. I am suspicious of syslogd at the moment (I pipe
> syslog output through a filter), one of the very few programs in the
> base system that are running on those systems and that uses SIGKILL.
> 
> However it will probably take some time before I can wrap my head
> around that code, it's not exactly heavily commented... If anyone
> with more intimate knowledge could have a look I'd appreciate that.

Apparently syslogd could do this, I think a fix was commited recently,
before RELENG_4 was branched, and it was fixed in RELENG_3 as well
(possibly RELENG_2_2 even).

-- 
Ben Smithurst / ben@scientia.demon.co.uk / PGP: 0x99392F7D


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


From owner-freebsd-stable  Wed Mar 29  6:46:11 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from lunatic.oneinsane.net (lunatic.oneinsane.net [207.113.133.231])
	by hub.freebsd.org (Postfix) with ESMTP id 8B33F37C042
	for <freebsd-stable@freebsd.org>; Wed, 29 Mar 2000 06:46:08 -0800 (PST)
	(envelope-from insane@lunatic.oneinsane.net)
Received: by lunatic.oneinsane.net (Postfix, from userid 1000)
	id 65E59197; Wed, 29 Mar 2000 06:46:07 -0800 (PST)
Date: Wed, 29 Mar 2000 06:46:07 -0800
From: Ron 'The InSaNe One' Rosson <insane@lunatic.oneinsane.net>
To: freebsd-stable@freebsd.org
Subject: Mainatain a Local CVSUP Server
Message-ID: <20000329064607.A49954@lunatic.oneinsane.net>
Reply-To: Ron Rosson <insane@lunatic.oneinsane.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0i
X-Operating-System: FreeBSD lunatic.oneinsane.net 3.4-STABLE
X-Moon: The Moon is Waning Crescent (36% of Full)
X-Opinion: What you read here is my IMHO 
X-Disclaimer: I am a firm believer in RTFM 
X-WWW: http://www.oneinsane.net
X-PGP-KEY: http://www.oneinsane.net/~insane/insane2-pgp5i.txt
X-Uptime: 6:44AM  up 6 days,  8:38, 1 user, load averages: 0.00, 0.00, 0.00
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Times are a changing for me......

I just have been tasked with what are the requirements to maintain a
local cvsup server for our personal use. Is there a guide/link/? to show
one how to go about this.

TIA
-- 
-------------------------------------------------------------------
Ron Rosson              	... and a UNIX user said ...
The InSaNe One                 		   rm -rf *
insane@oneinsane.net      	and all was /dev/null and *void()
-------------------------------------------------------------------
"Programming is like sex: One mistake and you support it a lifetime."


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


From owner-freebsd-stable  Wed Mar 29  6:49:21 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from smtp8.xs4all.nl (smtp8.xs4all.nl [194.109.127.51])
	by hub.freebsd.org (Postfix) with ESMTP id 862CC37B6ED
	for <freebsd-stable@FreeBSD.ORG>; Wed, 29 Mar 2000 06:49:17 -0800 (PST)
	(envelope-from arnout@tomcat.xs4all.nl)
Received: from tomcat.xs4all.nl (tomcat.xs4all.nl [194.109.15.187])
	by smtp8.xs4all.nl (8.9.3/8.9.3) with ESMTP id QAA13003;
	Wed, 29 Mar 2000 16:49:12 +0200 (CEST)
Received: (from arnout@localhost)
	by tomcat.xs4all.nl (8.9.3/8.9.1) id QAA05580;
	Wed, 29 Mar 2000 16:43:49 +0200 (CEST)
Date: Wed, 29 Mar 2000 16:43:49 +0200
From: Arnout Boer <arnout@xs4all.nl>
To: Brad Knowles <blk@skynet.be>
Cc: Morgan Davis <mdavis@cts.com>, freebsd-stable@FreeBSD.ORG
Subject: Re: 4.0-stable + SMP + fxp = device timeout
Message-ID: <20000329164349.A5311@tomcat.xs4all.nl>
References: <NABBLJGKKPMOKACIENPPEEGMCKAA.mdavis@cts.com> <v04220803b5078dbe3c8c@[195.238.20.81]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0.1i
In-Reply-To: <v04220803b5078dbe3c8c@[195.238.20.81]>; from blk@skynet.be on Wed, Mar 29, 2000 at 12:39:47PM +0200
X-Operating-System: FreeBSD 4.0-STABLE i386
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Wed, Mar 29, 2000 at 12:39:47PM +0200, Brad Knowles wrote:
> >  The subject says it all.  Is this a known problem with SMP and the fxp
> >  driver? (Checked 4.0 errata and searched the mailing lists -- didn't see
> >  anything).

Hmmmm works fine for me - 
dual proc P200 (1 overclocked from 166)
on a gigabyte HX board...
No SMP problems with fxp0 on 3.X release and also
not on RELENG4 (7/3 - till now)

dmesg says---
FreeBSD 4.0-STABLE #0: Tue Mar 28 16:37:33 CEST 2000
    root@tomcat.xs4all.nl:/usr/src/sys/compile/TOMCAT
Timecounter "i8254"  frequency 1193182 Hz
CPU: Pentium/P55C (200.46-MHz 586-class CPU)
  Origin = "GenuineIntel"  Id = 0x544  Stepping = 4
  Features=0x8003bf<FPU,VME,DE,PSE,TSC,MSR,MCE,CX8,APIC,MMX>
real memory  = 134217728 (131072K bytes)
avail memory = 127406080 (124420K bytes)
Programming 24 pins in IOAPIC #0
IOAPIC #0 intpin 2 -> irq 0
FreeBSD/SMP: Multiprocessor motherboard
 cpu0 (BSP): apic id:  0, version: 0x00030010, at 0xfee00000
 cpu1 (AP):  apic id:  1, version: 0x00030010, at 0xfee00000
 io0 (APIC): apic id:  2, version: 0x00170011, at 0xfec00000
[cut]
fxp0: <Intel EtherExpress Pro 10/100B Ethernet> port 0x6500-0x653f mem 0xe100000
0-0xe10fffff,0xe1100000-0xe1100fff irq 18 at device 10.0 on pci0
fxp0: Ethernet address 00:90:27:42:d9:b7
fxp0: supplying EUI64: 00:90:27:ff:fe:42:d9:b7
----

Greetz,

Arnout




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


From owner-freebsd-stable  Wed Mar 29  7: 2:52 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from axl.ops.uunet.co.za (axl.ops.uunet.co.za [196.31.1.175])
	by hub.freebsd.org (Postfix) with ESMTP id 2422C37B619
	for <freebsd-stable@freebsd.org>; Wed, 29 Mar 2000 07:02:47 -0800 (PST)
	(envelope-from sheldonh@axl.ops.uunet.co.za)
Received: from sheldonh (helo=axl.ops.uunet.co.za)
	by axl.ops.uunet.co.za with local-esmtp (Exim 3.13 #1)
	id 12aJzN-0008by-00; Wed, 29 Mar 2000 17:02:33 +0200
From: Sheldon Hearn <sheldonh@uunet.co.za>
To: Ron Rosson <insane@lunatic.oneinsane.net>
Cc: freebsd-stable@FreeBSD.ORG
Subject: Re: Mainatain a Local CVSUP Server 
In-reply-to: Your message of "Wed, 29 Mar 2000 06:46:07 PST."
             <20000329064607.A49954@lunatic.oneinsane.net> 
Date: Wed, 29 Mar 2000 17:02:33 +0200
Message-ID: <33105.954342153@axl.ops.uunet.co.za>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG



On Wed, 29 Mar 2000 06:46:07 PST, "Ron 'The InSaNe One' Rosson" wrote:

> I just have been tasked with what are the requirements to maintain a
> local cvsup server for our personal use. Is there a guide/link/? to show
> one how to go about this.

You mean other than the CVSup web page?

	grep ^WWW /usr/ports/net/cvsup/pkg/DESCR

:-)

Ciao,
Sheldon.


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


From owner-freebsd-stable  Wed Mar 29  7: 8:26 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from mostgraveconcern.com (mostgraveconcern.com [216.82.145.240])
	by hub.freebsd.org (Postfix) with ESMTP id 49AF337C1AF
	for <freebsd-stable@FreeBSD.ORG>; Wed, 29 Mar 2000 07:08:11 -0800 (PST)
	(envelope-from dan@mostgraveconcern.com)
Received: from danco (danco.mostgraveconcern.com [10.0.0.2])
	by mostgraveconcern.com (8.9.3/8.9.3) with SMTP id HAA03339;
	Wed, 29 Mar 2000 07:07:50 -0800 (PST)
	(envelope-from dan@mostgraveconcern.com)
Message-ID: <007001bf9990$8d866a00$0200000a@danco>
Reply-To: "Dan O'Connor" <dan@mostgraveconcern.com>
From: "Dan O'Connor" <dan@mostgraveconcern.com>
To: "Didier Derny" <didier@omnix.net>,
	"Martin Cracauer" <cracauer@cons.org>
Cc: <freebsd-stable@FreeBSD.ORG>
Subject: Re: Let 3.x die ASAP?
Date: Wed, 29 Mar 2000 07:07:50 -0800
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.3155.0
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

>in 1999 (3.x) I was not so sure at all, no stability too many problems.


Well, I've been running 3.x since upgrading from 2.2.8 to 3.1 early last
year, and I haven't had a single crash to date...

>In 2000 it's getting worse, for me FreeBSD is not stable at all
>the future of FreeBSD is not so clear, version follow after version but


It's called progress. BTW, Microsoft also releases version after version,
they just don't tell anybody about it until they get to the point where they
charge you $100 for it.

>I still have no support for my sound board, realplayer, oracle...


Yes, this is sad. But since FreeBSD is a volunteer effort, it's going to be
impossible to support *everything*, especially for items that are
proprietory and have to be reverse-engineered.

Of course, *you* could help out and write that driver too...

>The clients are telling me to install Linux instead of FreeBSD (for
>oracle)...


I hear a FreeBSD-native version of Oracle is in the works...

>I've just finished uprading the machines to 3.4-release and you are
>telling me that there is no future for 3.X...


Well, 3.4's been out for 3 months already. If you'd installed it earlier,
you would have gotten your money's worth out of it. BTW, there will be a 3.5
before we're all urged to move to 4.1...

>I'm about to buy a smp machine but I see so many horror stories on
>the mailling lists that I'm not sure at all that I should use a smp
>machine (or install linux instead of FreeBSD)...


Ah, the beauty of mailing lists. Remember, for every complaint, there's
50-100 people that are having no problems at all, and thus have no reason to
complain to the list.

>one of our client is running a smp machine with 3.2-BETA without any
>probleme...
>
>another client is running 3.4-RELEASE and his machine is rebooting on
>heavy load...


This is most likely a hardware problem.

And why are these people not running -STABLE? Are they still using Windows
3.0 too?


--Dan

--
Dan O'Connor
On Matters of Most Grave Concern
http://www.mostgraveconcern.com




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


From owner-freebsd-stable  Wed Mar 29  7:11:28 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from thehousleys.net (frenchknot.ne.mediaone.net [24.147.224.201])
	by hub.freebsd.org (Postfix) with ESMTP id 6548837C1DD
	for <freebsd-stable@FreeBSD.ORG>; Wed, 29 Mar 2000 07:11:15 -0800 (PST)
	(envelope-from jim@thehousleys.net)
Received: from thehousleys.net (baby.int.thehousleys.net [192.168.0.24])
	by thehousleys.net (8.9.3/8.9.3) with ESMTP id KAA81791;
	Wed, 29 Mar 2000 10:10:59 -0500 (EST)
Message-ID: <38E21D03.9DA9E0B6@thehousleys.net>
Date: Wed, 29 Mar 2000 10:10:59 -0500
From: James Housley <jim@thehousleys.net>
Organization: The Housleys dot Net
X-Mailer: Mozilla 4.72 [en] (X11; U; FreeBSD 3.4-STABLE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Ron Rosson <insane@lunatic.oneinsane.net>
Cc: freebsd-stable@FreeBSD.ORG
Subject: Re: Mainatain a Local CVSUP Server
References: <20000329064607.A49954@lunatic.oneinsane.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Ron 'The InSaNe One' Rosson wrote:
> 
> Times are a changing for me......
> 
> I just have been tasked with what are the requirements to maintain a
> local cvsup server for our personal use. Is there a guide/link/? to show
> one how to go about this.
> 
I think I followed the man page and looked in the cvs source tree, but
this what I have and more importantly it WORKS (hehehehe)

The default base dir is /usr/local/etc/cvsupd


housley@cat:/usr/local/etc/cvsup {3} ll -R 
total 2
-rw-rw-r--  1 root  wheel   49 May 13  1999 cvsupd.access
drwxrwxr-x  3 root  wheel  512 Oct 26  1998 sup/

./sup:
total 1
drwxrwxr-x  2 root  wheel  512 Oct 26  1998 MONITORS_CVS/

./sup/MONITORS_CVS:
total 2
-rw-rw-r--  1 housley  develop  147 Nov 17 21:10 list.cvs
-rw-rw-r--  1 housley  develop  424 Nov 17 21:11 releases

housley@cat:/usr/local/etc/cvsup {4} cat cvsupd.access 
+someone.com 1
+192.168.0.0/16 3

This is the list of hosts and how many session they may have active.

housley@cat:.../etc/cvsup/sup/MONITORS_CVS {9} cat list.cvs 
upgrade monitors
upgrade NotePage
upgrade healthd
omitany RTEMS/*
omitany */#cvs.*
omitany CVSROOT/*
omitany WATCOM/*
omitany */,*
omitany */.nfs*
housley@cat:.../etc/cvsup/sup/MONITORS_CVS {10} cat releases 
cvs             list=list.cvs prefix=/usr/home/MONITORS_CVS
keywordprefix=/home/ncvs norsync
monitors        list=list.cvs prefix=/usr/home/MONITORS_CVS
keywordprefix=/home/ncvs norsync
NotePage        list=list.cvs prefix=/usr/home/MONITORS_CVS
keywordprefix=/home/ncvs norsync
healthd         list=list.cvs prefix=/usr/home/MONITORS_CVS
keywordprefix=/home/ncvs norsync
RTEMS           list=list.cvs prefix=/usr/home/MONITORS_CVS
keywordprefix=/home/ncvs norsync

Then on the client end I modified an existing FreeBSD cvsup file to
match the local server config.

Jim
-- 
The wise man built his network upon U*nx.
    The foolish man built his network upon Windows.


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


From owner-freebsd-stable  Wed Mar 29  7:14:10 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from omnix.net (omnix.net [195.154.168.66])
	by hub.freebsd.org (Postfix) with SMTP id 068D537B619
	for <freebsd-stable@FreeBSD.ORG>; Wed, 29 Mar 2000 07:14:06 -0800 (PST)
	(envelope-from didier@omnix.net)
Received: (qmail 13842 invoked by uid 200); 29 Mar 2000 15:14:04 -0000
Received: from localhost (sendmail-bs@127.0.0.1)
  by localhost with SMTP; 29 Mar 2000 15:14:04 -0000
Date: Wed, 29 Mar 2000 15:14:04 +0000 (GMT)
From: Didier Derny <didier@omnix.net>
To: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Cc: Martin Cracauer <cracauer@cons.org>, freebsd-stable@FreeBSD.ORG
Subject: Re: Let 3.x die ASAP? 
In-Reply-To: <91902.954325405@zippy.cdrom.com>
Message-ID: <Pine.BSF.3.96.1000329145706.13503A-100000@omnix.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


the problem is really simple, I' WORKING with FreeBSD not PLAYING
you are like 3 years boys you are trowing their old toys each time 
they have an new one.

I can't an many people can't upgrade the system on their machine
at the actual rythm of FreeBSD version (each one supposed to be the best
one and solve most of the problems :-))) )

without a real stability (like the one with 2.x) this product
has no more value than linux or solaris, sco...

even If I have a great hope for FreeBSD 4.x, I consider that actually
4.0 is just bullshit (I mean a developper's toy but I wanted a strong
word [perhaps too strong I fear]) and you are already
throwing the old one (3.x). 

A I told you before, I'm preparing a way to be able to choose between
FreeBSD and something else (netbsd, openbsd, linux...) but not before
next year.

perhaps that the abandon of FreeBSD 3.x is simply the first effect
of what I was saying in my previous mails ?

  +-----------+
  |           |
  |  FreeBSD  |
  |    RIP    |
  |           |
~~~~~~~~~~~~~~~~~~

-- 
Didier Derny
didier@omnix.net


On Wed, 29 Mar 2000, Jordan K. Hubbard wrote:

> I thought the end came for you after you started spreading the FUD the
> last time.  As Winston Churchill said to Neville Chamberlain after
> his highly successful trip to Munich:  "For god's sake man, GO!"
> 
> - Jordan
> 



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


From owner-freebsd-stable  Wed Mar 29  7:16:40 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from knight.cons.org (knight.cons.org [194.233.237.86])
	by hub.freebsd.org (Postfix) with ESMTP id 1508037C11E
	for <freebsd-stable@FreeBSD.ORG>; Wed, 29 Mar 2000 07:16:36 -0800 (PST)
	(envelope-from cracauer@knight.cons.org)
Received: (from cracauer@localhost)
	by knight.cons.org (8.9.3/8.9.3) id RAA14280;
	Wed, 29 Mar 2000 17:16:09 +0200 (CEST)
Date: Wed, 29 Mar 2000 17:16:09 +0200
From: Martin Cracauer <cracauer@cons.org>
To: "Dan O'Connor" <dan@mostgraveconcern.com>
Cc: Didier Derny <didier@omnix.net>,
	Martin Cracauer <cracauer@cons.org>, freebsd-stable@FreeBSD.ORG
Subject: Re: Let 3.x die ASAP?
Message-ID: <20000329171609.A14243@cons.org>
References: <007001bf9990$8d866a00$0200000a@danco>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0.1i
In-Reply-To: <007001bf9990$8d866a00$0200000a@danco>; from dan@mostgraveconcern.com on Wed, Mar 29, 2000 at 07:07:50AM -0800
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Folk,

I really don't see a need to go into flamewars here. You won't reach
any conclusion in uptime wars and/or in must/non-need-to support of
old hardware.

There are perfectly stable 3.x machines out there and *there* are
enough hints that kernel instability raised somewhere between 3.1 and
3.4 for some and only some machines and that those are fixed in 4.0.

As things stand now, there will be a 3.5 release with lowered public
visibilty so that no new users jump on it and those who want 3.x can
get it. If neccessary, a privately-burned CD can be shipped to them.

So far I didn't see anything that isn't compatible with this way to
proceed. 

Martin
-- 
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
Martin Cracauer <cracauer@cons.org> http://www.cons.org/cracauer/
  Tel.: (private) +4940 5221829 Fax.: (private) +4940 5228536


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


From owner-freebsd-stable  Wed Mar 29  7:25:17 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from knight.cons.org (knight.cons.org [194.233.237.86])
	by hub.freebsd.org (Postfix) with ESMTP id 93F3537C15D
	for <freebsd-stable@FreeBSD.ORG>; Wed, 29 Mar 2000 07:25:13 -0800 (PST)
	(envelope-from cracauer@knight.cons.org)
Received: (from cracauer@localhost)
	by knight.cons.org (8.9.3/8.9.3) id RAA14339;
	Wed, 29 Mar 2000 17:25:10 +0200 (CEST)
Date: Wed, 29 Mar 2000 17:25:09 +0200
From: Martin Cracauer <cracauer@cons.org>
To: Didier Derny <didier@omnix.net>
Cc: freebsd-stable@FreeBSD.ORG
Subject: Re: Let 3.x die ASAP?
Message-ID: <20000329172509.B14243@cons.org>
References: <91902.954325405@zippy.cdrom.com> <Pine.BSF.3.96.1000329145706.13503A-100000@omnix.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0.1i
In-Reply-To: <Pine.BSF.3.96.1000329145706.13503A-100000@omnix.net>; from didier@omnix.net on Wed, Mar 29, 2000 at 03:14:04PM +0000
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

OK, I have to retract my opinion that there is no need to go into
flamewars here. My apologies to anyone who attacked Didier and was
approched by me.

Didier, you don't like newer 3.x and you don't like 4.0. Why don't you
just run 3.1, 3.2 or 2.2.8 and leave us alone, please?

In <Pine.BSF.3.96.1000329145706.13503A-100000@omnix.net>, Didier Derny wrote: 
> 
> the problem is really simple, I' WORKING with FreeBSD not PLAYING
> you are like 3 years boys you are trowing their old toys each time 
> they have an new one.
[...]

Martin
-- 
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
Martin Cracauer <cracauer@cons.org> http://www.cons.org/cracauer/
  Tel.: (private) +4940 5221829 Fax.: (private) +4940 5228536


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


From owner-freebsd-stable  Wed Mar 29  7:47:54 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from TK147108.tuwien.teleweb.at (TK147108.tuwien.teleweb.at [195.34.147.108])
	by hub.freebsd.org (Postfix) with ESMTP id 61E7A37B6D0
	for <freebsd-stable@freebsd.org>; Wed, 29 Mar 2000 07:47:46 -0800 (PST)
	(envelope-from satyr@TK147108.tuwien.teleweb.at)
Received: from satyr by TK147108.tuwien.teleweb.at with local (Exim 2.12 #1)
	id 12aKjb-0002FN-00
	for freebsd-stable@freebsd.org; Wed, 29 Mar 2000 17:50:19 +0200
Date: Wed, 29 Mar 2000 17:50:18 +0200
From: "Marinos J . Yannikos" <mjy@pobox.com>
To: freebsd-stable@freebsd.org
Subject: 3.4-RELEASE; panic while paging
Message-ID: <20000329175018.V15889@TK147108.telekabel.at>
Reply-To: nino@inode.at
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.5i
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

I am using 3.4-RELEASE (no patches) on an Athlon 600 / FIC SD11 system.
So far I have experienced:
- 1 spontaneous reboot
- several sig 10/sig 11 errors while compiling the kernel
- 2 kernel panics while paging, the message was "supervisor read - page not
  present, IIRC". Apparently the kernel ran out of swap, but I doubt that
  this was the only reason. 3.4-RELEASE seems rock-stable on my K6-3/400
  system.

Does anyone use the above configuration without problems? I am using very
conservative SDRAM timings and brand 6ns PC100 SDRAM. Could this be a sign
of a bad power supply, or do these things happen with 3.4-RELEASE because
of a bug?

Thanks,
-mjy
-- 
***==> Marinos J. Yannikos <mjy@pobox.com>
***==> http://pobox.com/~mjy


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


From owner-freebsd-stable  Wed Mar 29  7:56:46 2000
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 EE23837C10B
	for <freebsd-stable@FreeBSD.ORG>; Wed, 29 Mar 2000 07:56:41 -0800 (PST)
	(envelope-from Cy.Schubert@uumail.gov.bc.ca)
Received: (from daemon@localhost)
	by point.osg.gov.bc.ca (8.8.7/8.8.8) id HAA23525;
	Wed, 29 Mar 2000 07:54:33 -0800
Received: from passer.osg.gov.bc.ca(142.32.110.29)
 via SMTP by point.osg.gov.bc.ca, id smtpda23523; Wed Mar 29 07:54:22 2000
Received: (from uucp@localhost)
	by passer.osg.gov.bc.ca (8.9.3/8.9.1) id HAA19895;
	Wed, 29 Mar 2000 07:53:25 -0800 (PST)
Received: from cwsys9.cwsent.com(10.2.2.1), claiming to be "cwsys.cwsent.com"
 via SMTP by passer9.cwsent.com, id smtpdm19878; Wed Mar 29 07:52:49 2000
Received: (from uucp@localhost)
	by cwsys.cwsent.com (8.9.3/8.9.1) id HAA18098;
	Wed, 29 Mar 2000 07:52:47 -0800 (PST)
Message-Id: <200003291552.HAA18098@cwsys.cwsent.com>
Received: from localhost.cwsent.com(127.0.0.1), claiming to be "cwsys"
 via SMTP by localhost.cwsent.com, id smtpdW18092; Wed Mar 29 07:52:09 2000
X-Mailer: exmh version 2.1.1 10/15/1999
Reply-To: Cy Schubert - ITSD Open Systems Group <Cy.Schubert@uumail.gov.bc.ca>
From: Cy Schubert - ITSD Open Systems Group <Cy.Schubert@uumail.gov.bc.ca>
X-OS: FreeBSD 3.4-RELEASE
X-Sender: cy
To: Mike Nowlin <mike@argos.org>
Cc: Didier Derny <didier@omnix.net>,
	Martin Cracauer <cracauer@cons.org>, freebsd-stable@FreeBSD.ORG
Subject: Re: Let 3.x die ASAP? 
In-reply-to: Your message of "Wed, 29 Mar 2000 03:41:45 EST."
             <Pine.LNX.4.05.10003290328060.28083-100000@jason.argos.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 29 Mar 2000 07:52:09 -0800
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

In message <Pine.LNX.4.05.10003290328060.28083-100000@jason.argos.org>, 
Mike No
wlin writes:
> A big chunk of what I like about FreeBSD compared to Linux is that there's
> more accountability for specific parts of the system.  Linus takes care of
> the Linux kernel, but who knows who does the rest -- depending on what
> release, by what distributor (Slackware, Redhat, etc.), finding library X
> to update library Y to fix program Z can be a real pain...  With FreeBSD,
> you can easily find out who is responsible for various chunks of the
> system.  Even if he/she doesn't have a solution for your particular
> problem, he'll generally have a good idea where to send you, or be willing
> to fix the problem in the tree.

That's one of the two reasons I switched from Linux to FreeBSD about 
five years ago.  It looks like some things never change.


Regards,                       Phone:  (250)387-8437
Cy Schubert                      Fax:  (250)387-5766
Team Leader, Sun/DEC Team   Internet:  Cy.Schubert@osg.gov.bc.ca
Open Systems Group, ITSD, ISTA
Province of BC





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


From owner-freebsd-stable  Wed Mar 29  8:11:24 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from got.wedgie.org (got.wedgie.org [216.181.169.146])
	by hub.freebsd.org (Postfix) with ESMTP id E54C937B619
	for <freebsd-stable@FreeBSD.ORG>; Wed, 29 Mar 2000 08:11:18 -0800 (PST)
	(envelope-from jgarman@got.wedgie.org)
Received: by got.wedgie.org (Postfix, from userid 1000)
	id 3E329D905; Wed, 29 Mar 2000 11:11:13 -0500 (EST)
Date: Wed, 29 Mar 2000 11:11:13 -0500
From: Jason Garman <jgarman@wedgie.org>
To: Tim Liddelow <tim@esec.com.au>
Cc: Grigoriy Strokin <grg@philol.msu.ru>,
	Eric Jacoboni <jaco@titine.fr.eu.org>, freebsd-stable@FreeBSD.ORG
Subject: Re: New kernel with its ATA drivers damages the filesystem
Message-ID: <20000329111113.A14294@got.wedgie.org>
Reply-To: jgarman@wedgie.org
References: <20000328195030.A30092@isabase.philol.msu.ru> <87ln33htuc.fsf@titine.fr.eu.org> <20000328221322.A32478@isabase.philol.msu.ru> <38E15BB9.3E3D5AF9@esec.com.au> <20000328223420.C10913@got.wedgie.org> <38E184BE.2A1EC450@esec.com.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.4i
In-Reply-To: <38E184BE.2A1EC450@esec.com.au>; from Tim Liddelow on Wed, Mar 29, 2000 at 02:21:18PM +1000
X-Phase-Of-Moon: The Moon is Waning Crescent (35% of Full)
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Wed, Mar 29, 2000 at 02:21:18PM +1000, Tim Liddelow wrote:
> 
> Well the motherboard is a FIC PA-2011 IIRC - I am running -current, but the
> driver is the same AFAIK.   I have put the sysctl in and am waiting to see if
> the problems recur.   Changing h/w seems a little heavy handed - I am not
> in the positition to do that right now - I'd like to see if there is a perhaps a
> software solution to this first.   Do we know for sure it is the hardware ?   Does
> Linux have problems on the same hardware ?   If I knew more about the driver
> I'd do some hacking, but I don't right now.
> 
Yes. Same symptoms under Linux, in fact much worse. Checksums of
recently ftp'ed files would routinely mismatch the original, and other
such bogons.  System was reasonably stable with DMA turned off.

I suppose everyone has a bad experience with hardware that taints their
future views, and this is mine :) I know that avoiding a VIA chipset was a
very conscious decision when i rushed out and purchased a replacement 
motherboard.

enjoy
-- 
Jason Garman                                         http://web.wedgie.org/
Student, University of Maryland                          jgarman@wedgie.org
From fortune(1):                                              Whois: JAG145
  "... Had this been an actual emergency, we would have fled in terror,
   and you would not have been informed."


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


From owner-freebsd-stable  Wed Mar 29  8:40:28 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from loki.ideaglobal.com (loki.ideaglobal.com [194.36.20.54])
	by hub.freebsd.org (Postfix) with ESMTP id A2F5737C0EC
	for <freebsd-stable@FreeBSD.ORG>; Wed, 29 Mar 2000 08:40:18 -0800 (PST)
	(envelope-from kiril@loki.ideaglobal.com)
Received: (from kiril@localhost)
	by loki.ideaglobal.com (8.9.3/8.9.3) id QAA71873;
	Wed, 29 Mar 2000 16:45:47 GMT
	(envelope-from kiril)
From: Kiril Mitev <kiril@ideaglobal.com>
Message-Id: <200003291645.QAA71873@loki.ideaglobal.com>
Subject: Re: q to Warner Losh wrt his PCI modem patch
In-Reply-To: <200003282244.PAA08985@harmony.village.org> from Warner Losh at "Mar 28, 2000  3:44:54 pm"
To: imp@village.org (Warner Losh)
Date: Wed, 29 Mar 2000 16:45:47 +0000 (GMT)
Cc: kiril@ideaglobal.com, 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

> In message <200003281549.PAA69054@loki.ideaglobal.com> Kiril Mitev writes:
> : I found something on deja... posted by Warner Losh
> 
> Hmm.  That guy doesn't know what he's talking about.  He posts to
> mailing lists after all :-)
> 
> : Can anyone PLEASE confirm/deny whether that patch is safe to use
> : with fbsd-4 ?
> 
> That one isn't.  You might try
> 	http://people.freebsd.org/~imp/sio-current-pci-patch
> instead.  It should work on both 4.0 and -current.  Should be
> integrated into the mainline sources soon.  Let me know if you have
> problems.  I'll commit it once I get a chance to deal with the latest
> round of comments for the review.

Thank you, will do :)

> Warner


-- 
Kiril Mitev, IT Operations Mgr, London
IDEAglobal.com
Standard Corporate Disclaimer applies, see
http://www.ideaglobal.com/email-disclaimer.html
for details.


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


From owner-freebsd-stable  Wed Mar 29  9: 4:22 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
	by hub.freebsd.org (Postfix) with ESMTP
	id DB5E337B79B; Wed, 29 Mar 2000 09:04:11 -0800 (PST)
	(envelope-from kris@FreeBSD.org)
Received: from localhost (kris@localhost)
	by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id JAA02708;
	Wed, 29 Mar 2000 09:04:11 -0800 (PST)
	(envelope-from kris@FreeBSD.org)
X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs
Date: Wed, 29 Mar 2000 09:04:10 -0800 (PST)
From: Kris Kennaway <kris@FreeBSD.org>
To: Dave Runkle <drunkle@home.com>
Cc: freebsd-stable@FreeBSD.ORG
Subject: Re: RELENG_4 'make -DNOINFO installworld' SIGNAL 12 on install of
 'test'
In-Reply-To: <Pine.BSF.4.10.10003281941380.92115-100000@xb.fiddi.com>
Message-ID: <Pine.BSF.4.21.0003290902490.99292-100000@freefall.freebsd.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Wed, 29 Mar 2000, Dave Runkle wrote:

> The kernel process went well, although it seems that contrary to
> UPDATING saying to manually do the kernel install, it was done by
> 'installkernel' as part of that script. So I did not have to do that
> part. The new kernel is sitting, ready to boot.

YOu should have booted the kernel before doing installworld. It probably
should work correctly if you do this now, assuming you followed the rest
of the instructions in UPDATING properly :-) The important one is to do
the wd -> ad renaming, or you wont be able to boot.

Kris



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


From owner-freebsd-stable  Wed Mar 29  9:59:42 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from freeway.dcfinc.com (cx74889-a.phnx3.az.home.com [24.1.193.157])
	by hub.freebsd.org (Postfix) with ESMTP id 33AD637C110
	for <freebsd-stable@FreeBSD.ORG>; Wed, 29 Mar 2000 09:58:44 -0800 (PST)
	(envelope-from chad@freeway.dcfinc.com)
Received: (from chad@localhost)
	by freeway.dcfinc.com (8.8.8/8.8.8) id KAA16393;
	Wed, 29 Mar 2000 10:58:28 -0700 (MST)
	(envelope-from chad)
From: "Chad R. Larson" <chad@DCFinc.com>
Message-Id: <200003291758.KAA16393@freeway.dcfinc.com>
Subject: Re: Let 3.x die ASAP?
In-Reply-To: <20000329113951.A9935@cons.org> from Martin Cracauer at "Mar 29, 0 11:39:51 am"
To: cracauer@cons.org (Martin Cracauer)
Date: Wed, 29 Mar 2000 10:58:28 -0700 (MST)
Cc: jkh@zippy.cdrom.com, cracauer@cons.org,
	freebsd-stable@FreeBSD.ORG
Reply-To: chad@DCFinc.com
X-Mailer: ELM [version 2.4ME+ PL40 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

As I recall, Martin Cracauer wrote:
> P.S. To the other commenters in this discussion. I know that there are
> a lot of very stable 3.x machines (with SMP too), I didn't doubt that.
> I just say that enough parts of the system are rotten that a
> substancial number of machines that runs fine unter 4.0 (and 3.[12]
> for me) doesn't run well on 3.4+. Hence I think it is a must for our
> reputation to turn public attention from 3.x to 4.x. Now.

Then you don't even want to hear about my 2.2-STABLE systems running
revenue generating production stuff.

They're rock solid.  Never had a panic, or unplanned reboot.  Do
what I want them to.  I have =no= (repeat, no) reason to upgrade.

New systems we build are going up as 3.4-STABLE, and I, for one,
want the 3.5 closure release.

I can understand wanting to play with the newer stuff.  But I'm not
committing bread-n-butter to anything not cooked in the field for a
while.  I'll let others pioneer.  So when I see the raft of "I just
upgraded my 3.x machine to 4.0" messages, my first reaction is
"Why?" and my second is "better you than me" and my third is "I hope
you uncover some obscure bug so it can be fixed before I get there."

	-crl
--
Chad R. Larson (CRL15)   602-953-1392   Brother, can you paradigm?
chad@dcfinc.com         chad@larsons.org          larson1@home.net   
DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207


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


From owner-freebsd-stable  Wed Mar 29 10:12:38 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from freeway.dcfinc.com (cx74889-a.phnx3.az.home.com [24.1.193.157])
	by hub.freebsd.org (Postfix) with ESMTP id 7790E37B787
	for <freebsd-stable@FreeBSD.ORG>; Wed, 29 Mar 2000 10:11:34 -0800 (PST)
	(envelope-from chad@freeway.dcfinc.com)
Received: (from chad@localhost)
	by freeway.dcfinc.com (8.8.8/8.8.8) id LAA16497;
	Wed, 29 Mar 2000 11:11:06 -0700 (MST)
	(envelope-from chad)
From: "Chad R. Larson" <chad@DCFinc.com>
Message-Id: <200003291811.LAA16497@freeway.dcfinc.com>
Subject: Re: Let 3.x die ASAP?
In-Reply-To: <92014.954325875@zippy.cdrom.com> from "Jordan K. Hubbard" at "Mar 29, 0 02:31:15 am"
To: jkh@zippy.cdrom.com (Jordan K. Hubbard)
Date: Wed, 29 Mar 2000 11:11:06 -0700 (MST)
Cc: cracauer@cons.org, freebsd-stable@FreeBSD.ORG
Reply-To: chad@DCFinc.com
X-Mailer: ELM [version 2.4ME+ PL40 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

As I recall, Jordan K. Hubbard wrote:
> 
> I should also note that this has nothing whatsoever to do with CDROM
> sales since I already told Walnut Creek CDROM awhile back that I would
> not be doing a CDROM version of 3.5 - it will be a network-only
> release.  We have enough work just placing one line of CD products
> into the market and the whole 2.2.8/3.x overlap was really difficult
> to map onto our existing customer base.  All customers will simply
> receive 4.0, 4.1 .. 4.x.

Boy, I must not be paying attention in the right places.  The last
pronouncement I thought I saw said that unless I contacted Walnut
Creek and requested otherwise, I'd get 3.5 and then 4.1 on my
subscription.  Which is just what I wanted (kinda like the
2.2.8->3.1 transition) so I didn't peep up.

Too late to vote?

	-crl
--
Chad R. Larson (CRL15)   602-953-1392   Brother, can you paradigm?
chad@dcfinc.com         chad@larsons.org          larson1@home.net   
DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207


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


From owner-freebsd-stable  Wed Mar 29 10:16: 2 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from mail.rdc1.ne.home.com (ha1.rdc1.ne.home.com [24.2.4.66])
	by hub.freebsd.org (Postfix) with ESMTP id 4210937B575
	for <FreeBSD-Stable@FreeBSD.ORG>; Wed, 29 Mar 2000 10:15:32 -0800 (PST)
	(envelope-from jgowdy@home.com)
Received: from cx443070a ([24.4.93.90]) by mail.rdc1.ne.home.com
          (InterMail v4.01.01.00 201-229-111) with SMTP
          id <20000329181531.PHVZ14878.mail.rdc1.ne.home.com@cx443070a>;
          Wed, 29 Mar 2000 10:15:31 -0800
Message-ID: <006201bf99ac$15649080$0100000a@vista1.sdca.home.com>
From: "Jeremiah Gowdy" <jgowdy@home.com>
To: "Coleman Kane" <cokane@one.net>
Cc: "Daniel C. Sobral" <dcs@newsguy.com>,
	"Alexandr Listopad" <laa@ZGIA.zp.ua>, "Kuzak" <kuzak@kuzak.net>,
	<FreeBSD-Stable@FreeBSD.ORG>
References: <Pine.BSF.4.10.10003271228100.48901-100000@Eagle.ZGIA.zp.ua> <38E065C5.418DA948@newsguy.com> <001901bf98db$9b897580$0100000a@vista1.sdca.home.com> <20000328224158.A2261@evil.2y.net>
Subject: Re: 4.0 Kernel
Date: Wed, 29 Mar 2000 10:24:55 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.6700
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> If you go to http:///www.de.freebsd.org/de/gif/bsd/ there should be a lot
of
> artwork to look at. They even have the famous nomad daemon on a cliff pic.
>
> --cokane

For some reason my name server cannot resolve that hostname.  Can you give
me the IP ?




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


From owner-freebsd-stable  Wed Mar 29 10:19:25 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from rock.ghis.net (rock.ghis.net [209.222.164.7])
	by hub.freebsd.org (Postfix) with ESMTP id 2CEB637B937
	for <freebsd-stable@FreeBSD.ORG>; Wed, 29 Mar 2000 10:19:16 -0800 (PST)
	(envelope-from will@blackdawn.com)
Received: from argon.blackdawn.com (03-181.dial.008.popsite.net [209.69.196.181])
	by rock.ghis.net (8.9.3/8.9.3) with ESMTP id KAA20242;
	Wed, 29 Mar 2000 10:19:00 -0800 (PST)
Received: by argon.blackdawn.com (Postfix, from userid 1000)
	id 59D3E1A5C; Wed, 29 Mar 2000 13:18:42 -0500 (EST)
Date: Wed, 29 Mar 2000 13:18:42 -0500
From: Will Andrews <andrews@technologist.com>
To: "Ron 'The InSaNe One' Rosson" <insane@lunatic.oneinsane.net>
Cc: freebsd-stable@FreeBSD.ORG
Subject: Re: Mainatain a Local CVSUP Server
Message-ID: <20000329131842.B55527@argon.blackdawn.com>
References: <20000329064607.A49954@lunatic.oneinsane.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0i
In-Reply-To: <20000329064607.A49954@lunatic.oneinsane.net>; from insane@lunatic.oneinsane.net on Wed, Mar 29, 2000 at 06:46:07AM -0800
X-Operating-System: FreeBSD 5.0-CURRENT i386
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Wed, Mar 29, 2000 at 06:46:07AM -0800, Ron 'The InSaNe One' Rosson wrote:
> Times are a changing for me......
> 
> I just have been tasked with what are the requirements to maintain a
> local cvsup server for our personal use. Is there a guide/link/? to show
> one how to go about this.

Easiest way to install a cvsup mirror is with cvsup-mirror in ports.

-- 
Will Andrews <andrews@technologist.com>
GCS/E/S @d- s+:+>+:- a--->+++ C++ UB++++ P+ L- E--- W+++ !N !o ?K w---
?O M+ V-- PS+ PE++ Y+ PGP+>+++ t++ 5 X++ R+ tv+ b++>++++ DI+++ D+ 
G++>+++ e->++++ h! r-->+++ y?


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


From owner-freebsd-stable  Wed Mar 29 10:22:25 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from freeway.dcfinc.com (cx74889-a.phnx3.az.home.com [24.1.193.157])
	by hub.freebsd.org (Postfix) with ESMTP id 4E09F37B644
	for <freebsd-stable@FreeBSD.ORG>; Wed, 29 Mar 2000 10:21:24 -0800 (PST)
	(envelope-from chad@freeway.dcfinc.com)
Received: (from chad@localhost)
	by freeway.dcfinc.com (8.8.8/8.8.8) id LAA16584;
	Wed, 29 Mar 2000 11:21:04 -0700 (MST)
	(envelope-from chad)
From: "Chad R. Larson" <chad@DCFinc.com>
Message-Id: <200003291821.LAA16584@freeway.dcfinc.com>
Subject: Re: Let 3.x die ASAP?
In-Reply-To: <Pine.BSF.3.96.1000329145706.13503A-100000@omnix.net> from Didier Derny at "Mar 29, 0 03:14:04 pm"
To: didier@omnix.net (Didier Derny)
Date: Wed, 29 Mar 2000 11:21:04 -0700 (MST)
Cc: jkh@zippy.cdrom.com, cracauer@cons.org,
	freebsd-stable@FreeBSD.ORG
Reply-To: chad@DCFinc.com
X-Mailer: ELM [version 2.4ME+ PL40 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

As I recall, Didier Derny wrote:
> I can't an many people can't upgrade the system on their machine
> at the actual rythm of FreeBSD version (each one supposed to be the best
> one and solve most of the problems :-))) )
> without a real stability (like the one with 2.x) this product
> has no more value than linux or solaris, sco...

So, is there some feature in the 3.x line that isn't in 2.2.x that
you can't live without?  If not, your course is clear.  Put up a
2.2-STABLE system and quit worrying about stability.


	-crl
--
Chad R. Larson (CRL15)   602-953-1392   Brother, can you paradigm?
chad@dcfinc.com         chad@larsons.org          larson1@home.net   
DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207


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


From owner-freebsd-stable  Wed Mar 29 10:26:34 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from ptavv.es.net (ptavv.es.net [198.128.4.29])
	by hub.freebsd.org (Postfix) with ESMTP id DDAD237C153
	for <freebsd-stable@FreeBSD.ORG>; Wed, 29 Mar 2000 10:25:22 -0800 (PST)
	(envelope-from oberman@ptavv.es.net)
Received: from ptavv.es.net (localhost [127.0.0.1])
	by ptavv.es.net (8.9.3/8.8.8) with ESMTP id KAA25639;
	Wed, 29 Mar 2000 10:25:18 -0800 (PST)
Message-Id: <200003291825.KAA25639@ptavv.es.net>
To: nino@inode.at
Cc: freebsd-stable@FreeBSD.ORG
Subject: Re: 3.4-RELEASE; panic while paging 
In-reply-to: Your message of "Wed, 29 Mar 2000 17:50:18 +0200."
             <20000329175018.V15889@TK147108.telekabel.at> 
Date: Wed, 29 Mar 2000 10:25:17 -0800
From: "Kevin Oberman" <oberman@es.net>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Marinos,

In my experience with these things, such errors are almost invariably
hardware problems. In the case you are seeing, I'd bet on a memory
problem. The VM system in FreeBSD can really pound memory and bring
out bugs.

If you have more than one memory board, try moving them around and see
if the errors change. Try pulling one and then another to see if
things clear up when the bad board is pulled. This is how I isolated
the same problem with my new K6-3/450.

Power supplies can also cause this, but I'd bet on a flaky DIMM.

R. Kevin Oberman, Network Engineer
Energy Sciences Network (ESnet)
Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
E-mail: oberman@es.net			Phone: +1 510 486-8634


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


From owner-freebsd-stable  Wed Mar 29 10:28: 2 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from freeway.dcfinc.com (cx74889-a.phnx3.az.home.com [24.1.193.157])
	by hub.freebsd.org (Postfix) with ESMTP id 536CF37BC59
	for <freebsd-stable@FreeBSD.ORG>; Wed, 29 Mar 2000 10:27:44 -0800 (PST)
	(envelope-from chad@freeway.dcfinc.com)
Received: (from chad@localhost)
	by freeway.dcfinc.com (8.8.8/8.8.8) id LAA16641;
	Wed, 29 Mar 2000 11:27:35 -0700 (MST)
	(envelope-from chad)
From: "Chad R. Larson" <chad@DCFinc.com>
Message-Id: <200003291827.LAA16641@freeway.dcfinc.com>
Subject: Re: 4.0-stable + SMP + fxp = device timeout
In-Reply-To: <NABBLJGKKPMOKACIENPPIEGNCKAA.mdavis@cts.com> from Morgan Davis at "Mar 29, 0 02:22:48 am"
To: mdavis@cts.com (Morgan Davis)
Date: Wed, 29 Mar 2000 11:27:35 -0700 (MST)
Cc: mihara@prd.fc.nec.co.jp, freebsd-stable@FreeBSD.ORG
Reply-To: chad@DCFinc.com
X-Mailer: ELM [version 2.4ME+ PL40 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

As I recall, Morgan Davis wrote:
> Again, the important point here is that this hardware ran 3.4-stable
> with SMP with no problems (for at least a year or so).  Upgraded to
> 4.0, and no joy.

I'm sure I'm starting to sound like the crusty curmudgen old fart
that I am, but could you please tell me why you upgraded?

I'm not trying to be glib here, I'm really interested.  What was the
motive for the upgrade?

	-crl
--
Chad R. Larson (CRL15)   602-953-1392   Brother, can you paradigm?
chad@dcfinc.com         chad@larsons.org          larson1@home.net   
DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207


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


From owner-freebsd-stable  Wed Mar 29 10:43:17 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from mass.cdrom.com (mg134-053.ricochet.net [204.179.134.53])
	by hub.freebsd.org (Postfix) with ESMTP id 9FA9E37B575
	for <freebsd-stable@freebsd.org>; Wed, 29 Mar 2000 10:42:14 -0800 (PST)
	(envelope-from msmith@mass.cdrom.com)
Received: from mass.cdrom.com (localhost [127.0.0.1])
	by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id KAA00946
	for <freebsd-stable@freebsd.org>; Wed, 29 Mar 2000 10:45:10 -0800 (PST)
	(envelope-from msmith@mass.cdrom.com)
Message-Id: <200003291845.KAA00946@mass.cdrom.com>
X-Mailer: exmh version 2.1.1 10/15/1999
To: freebsd-stable@freebsd.org
Subject: Re: Let 3.x die ASAP? 
In-reply-to: Your message of "Wed, 29 Mar 2000 08:22:15 GMT."
             <Pine.BSF.3.96.1000329080220.7123A-100000@omnix.net> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 29 Mar 2000 10:45:09 -0800
From: Mike Smith <msmith@freebsd.org>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> 
> why dont you call freebsd freebsd2000 freebsd2001....
> 
> freebsd seems running version after version and not stability...

Is "Didier" French for "Dennis"?

-- 
\\ Give a man a fish, and you feed him for a day. \\  Mike Smith
\\ Tell him he should learn how to fish himself,  \\  msmith@freebsd.org
\\ and he'll hate you for a lifetime.             \\  msmith@cdrom.com




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


From owner-freebsd-stable  Wed Mar 29 10:53:51 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from androcles.com (androcles.com [204.57.240.10])
	by hub.freebsd.org (Postfix) with ESMTP
	id 3CB2937BFE1; Wed, 29 Mar 2000 10:52:19 -0800 (PST)
	(envelope-from alex@androcles.com)
Received: (from dhh@localhost)
	by androcles.com (8.9.3/8.9.3) id KAA60763;
	Wed, 29 Mar 2000 10:51:12 -0800 (PST)
Message-ID: <XFMail.000329105111.dhh@androcles.com>
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: <38E20D22.17581.4939BA1@localhost>
Date: Wed, 29 Mar 2000 10:51:11 -0800 (PST)
Reply-To: dhh@androcles.com
From: "Duane H. Hesser" <dhh@androcles.com>
To: Lauri Laupmaa <mauri@inspiral.net>
Subject: RE: timezones/zoneinfo
Cc: support@debian.org, support@redhat.com, current@FreeBSD.ORG,
	stable@FreeBSD.ORG
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


On 29-Mar-00 Lauri Laupmaa wrote:
> Hi
> 
> Who and when should update/fix subj. ?
> Our parliament decided that estonia does not change to DST 
> anymore and forgot to mention it to MS and other OS 
> manufacturers :) 
> 
> so info for Europe/Tallinn is wrong and our little state is full of 
> computers with wrong time :(
> 
> Help!
> _____________
> Lauri Laupmaa
> +3725013369
> 
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-stable" in the body of the message
>

A quick search of Google/BSD reveals that NetBSD is current on
zoneinfo data.  At least 5 country files (africa, asia, australasia,
europe, northamerica, southamerica) were updated in the NetBSD
zoneinfo sources on March 18, 2000.  It appears that FreeBSD has
not picked up these changes yet (don't know about Debian or RedHat),
and does not distribute the zoneinfo data sources in any case (at
least, they don't seem to be on my machine).

The source file for europe (containing Estonia) may be found at

 ftp://ftp.netbsd.org/pub/NetBSD/NetBSD-current/src/share/zoneinfo/

Here is the excerpt from that file for Estonia:

------ cut here -------
# Estonia
# From Peter Ilieve <peter@memex.co.uk> (1994-10-15):
# A relative in Tallinn confirms the accuracy of the data for 1989 onwards
# [through 1994] and gives the legal authority for it,
# a regulation of the Government of Estonia, No. 111 of 1989....
#
# From Peter Ilieve <peter@aldie.co.uk> (1996-10-28):
# [IATA SSIM (1992/1996) claims that the Baltic republics switch at 01:00s,
# but a relative confirms that Estonia still switches at 02:00s, writing:]
# ``I do not [know] exactly but there are some little different
# (confusing) rules for International Air and Railway Transport Schedules
# conversion in Sunday connected with end of summer time in Estonia....
# A discussion is running about the summer time efficiency and effect on
# human physiology.  It seems that Estonia maybe will not change to
# summer time next spring.''

# From Peter Ilieve <peter@aldie.co.uk> (1998-11-04), heavily edited:
# <a href="http://trip.rk.ee/cgi-bin/thw?${BASE}=akt&${OOHTML}=rtd&TA=1998&TO=1&AN=1390">
# The 1998-09-22 Estonian time law
# </a>
# refers to the Eighth Directive and cites the association agreement between
# the EU and Estonia, ratified by the Estonian law (RT II 1995, 22--27, 120).
#
# I also asked [my relative] whether they use any standard abbreviation
# for their standard and summer times. He says no, they use "suveaeg"
# (summer time) and "talveaeg" (winter time).

# From <a href="http://www.baltictimes.com/">The Baltic Times</a> (1999-09-09)
# via Steffen Thorsen:
# This year will mark the last time Estonia shifts to summer time,
# a council of the ruling coalition announced Sept. 6....
# But what this could mean for Estonia's chances of joining the European
# Union are still unclear.  In 1994, the EU declared summer time compulsory
# for all member states until 2001.  Brussels has yet to decide what to do
# after that. 

# From Mart Oruaas (2000-01-29):
# Regulation no. 301 (1999-10-12) obsoletes previous regulation
# no. 206 (1998-09-22) and thus sticks Estonia to +02:00 GMT for all
# the year round.  The regulation is effective 1999-11-01.

# Zone  NAME            GMTOFF  RULES   FORMAT  [UNTIL]
Zone    Europe/Tallinn  1:39:00 -       LMT     1880
                        1:39:00 -       TMT     1918 Feb # Tallinn Mean Time
                        1:00    C-Eur   CE%sT   1919 Jul
                        1:39:00 -       TMT     1921 May
                        2:00    -       EET     1940 Aug  6
                        3:00    -       MSK     1941 Sep 15
                        1:00    C-Eur   CE%sT   1944 Sep 22
                        3:00    Russia  MSK/MSD 1989 Mar 26 2:00s
                        2:00    1:00    EEST    1989 Sep 24 2:00s
                        2:00    C-Eur   EE%sT   1998 Sep 22
                        2:00    EU      EE%sT   1999 Nov  1
                        2:00    -       EET

-------- end cut -------

You will note the addition for Estonia's new regulation effective
Nov 1 last year.

Machines which use "zoneinfo" need a 'compiled' form of the file.
You should be able to grab the data source file from the ftp URL
above, run 'zic' on it to produce a new compiled file for Tallinn
for each system type, and distribute the new files for a quick fix
on machines to which you have access.

'zic' is in section 8 of the manuals.

--------------
Duane H. Hesser
dhh@androcles.com


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


From owner-freebsd-stable  Wed Mar 29 10:54:20 2000
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 646F737C167
	for <freebsd-stable@freebsd.org>; Wed, 29 Mar 2000 10:53:56 -0800 (PST)
	(envelope-from dwmalone@maths.tcd.ie)
Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP
          id <aa45153@salmon>; 29 Mar 2000 19:53:55 +0100 (BST)
Date: Wed, 29 Mar 2000 19:53:54 +0100
From: David Malone <dwmalone@maths.tcd.ie>
To: nino@inode.at
Cc: freebsd-stable@freebsd.org
Subject: Re: 3.4-RELEASE; panic while paging
Message-ID: <20000329195354.A40356@walton.maths.tcd.ie>
References: <20000329175018.V15889@TK147108.telekabel.at>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0.1i
In-Reply-To: <20000329175018.V15889@TK147108.telekabel.at>; from mjy@pobox.com on Wed, Mar 29, 2000 at 05:50:18PM +0200
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Wed, Mar 29, 2000 at 05:50:18PM +0200, Marinos J . Yannikos wrote:

> - 1 spontaneous reboot
> - several sig 10/sig 11 errors while compiling the kernel
> - 2 kernel panics while paging, the message was "supervisor read - page not
>   present, IIRC". Apparently the kernel ran out of swap, but I doubt that
>   this was the only reason. 3.4-RELEASE seems rock-stable on my K6-3/400
>   system.

Sounds like a regular "sig 11" problem. It probably means one of:

	1) Your processor is overheating. We had a dual PIII 600
	which came with fans which weren't up to the job and them
	machine would lock up after a few minutes.

	2) Your motherboard is sick. We had a motherboard which
	was causing every 8th byte of a 4k page to be corrupted
	once every few weeks.  The new version of the MB had added
	a heat sync to the memory controler, and works perfectly.

	3) Your memory is sick. Don't trust the BIOS test - I've
	seen SIMMs pass the BIOS test that have a blob of solder
	stuck across a few pins on the ram chips.

The only way to find out is to swap parts until the machine becomes
stable.

	David.


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


From owner-freebsd-stable  Wed Mar 29 11:11:10 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
	by hub.freebsd.org (Postfix) with ESMTP
	id C907B37BA5E; Wed, 29 Mar 2000 11:11:08 -0800 (PST)
	(envelope-from kris@FreeBSD.org)
Received: from localhost (kris@localhost)
	by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id LAA26193;
	Wed, 29 Mar 2000 11:11:08 -0800 (PST)
	(envelope-from kris@FreeBSD.org)
X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs
Date: Wed, 29 Mar 2000 11:11:07 -0800 (PST)
From: Kris Kennaway <kris@FreeBSD.org>
To: nino@inode.at
Cc: freebsd-stable@freebsd.org
Subject: Re: 3.4-RELEASE; panic while paging
In-Reply-To: <20000329175018.V15889@TK147108.telekabel.at>
Message-ID: <Pine.BSF.4.21.0003291110080.25674-100000@freefall.freebsd.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Wed, 29 Mar 2000, Marinos J . Yannikos wrote:

> I am using 3.4-RELEASE (no patches) on an Athlon 600 / FIC SD11 system.
> So far I have experienced:
> - 1 spontaneous reboot
> - several sig 10/sig 11 errors while compiling the kernel
> - 2 kernel panics while paging, the message was "supervisor read - page not
>   present, IIRC". Apparently the kernel ran out of swap, but I doubt that
>   this was the only reason. 3.4-RELEASE seems rock-stable on my K6-3/400
>   system.
> 
> Does anyone use the above configuration without problems? I am using very
> conservative SDRAM timings and brand 6ns PC100 SDRAM. Could this be a sign
> of a bad power supply, or do these things happen with 3.4-RELEASE because
> of a bug?

It's almost certainly a hardware problem, given the random nature of your
problems. Try running a make buildworld -j16 or something stressful - if
it can't handle the load, it's probably bad hardware.

Kris



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


From owner-freebsd-stable  Wed Mar 29 11:13:15 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
	by hub.freebsd.org (Postfix) with ESMTP
	id DF33437B575; Wed, 29 Mar 2000 11:12:50 -0800 (PST)
	(envelope-from kris@FreeBSD.org)
Received: from localhost (kris@localhost)
	by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id LAA26499;
	Wed, 29 Mar 2000 11:12:50 -0800 (PST)
	(envelope-from kris@FreeBSD.org)
X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs
Date: Wed, 29 Mar 2000 11:12:49 -0800 (PST)
From: Kris Kennaway <kris@FreeBSD.org>
To: hometeam <hometeam@techpower.net>
Cc: Gawel <gawel@sim.com.pl>, Eric Jacoboni <jaco@titine.fr.eu.org>,
	Grigoriy Strokin <grg@philol.msu.ru>, freebsd-stable@FreeBSD.ORG
Subject: Re: New kernel with its ATA drivers damages the filesystem
In-Reply-To: <Pine.BSF.4.21.0003290849210.3533-100000@techpower.net>
Message-ID: <Pine.BSF.4.21.0003291111580.25674-100000@freefall.freebsd.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Wed, 29 Mar 2000, hometeam wrote:

> I agree this really should be fix ...I notcied this straight away and sent
> mail to the group...Now it is damaging file Systems after the fact and
> wiping out file systems... I mean change the
> hardware ??? Why not fix the driver ?

Perhaps you should drop back to 3.4 until the bug is fixed. These things
aren't easy to spot and fix..

Have you spoken directly with the maintainer (sos@freebsd.org)?

Kris

----
In God we Trust -- all others must submit an X.509 certificate.
    -- Charles Forsythe <forsythe@alum.mit.edu>



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


From owner-freebsd-stable  Wed Mar 29 11:27:17 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from twizors.rug.ac.be (twizors.rug.ac.be [157.193.55.153])
	by hub.freebsd.org (Postfix) with ESMTP id CF1EF37B59C
	for <freebsd-stable@FreeBSD.ORG>; Wed, 29 Mar 2000 11:26:59 -0800 (PST)
	(envelope-from ageorges@twizors.rug.ac.be)
Received: from localhost (ageorges@localhost)
	by twizors.rug.ac.be (8.9.3/8.9.3) with ESMTP id VAA13310;
	Wed, 29 Mar 2000 21:33:08 +0200 (CEST)
	(envelope-from ageorges@twizors.rug.ac.be)
Date: Wed, 29 Mar 2000 21:33:08 +0200 (CEST)
From: Andy Georges <ageorges@twizors.rug.ac.be>
To: Martin Cracauer <cracauer@cons.org>
Cc: freebsd-stable@FreeBSD.ORG
Subject: Re: Let 3.x die ASAP?
In-Reply-To: <20000329171609.A14243@cons.org>
Message-ID: <Pine.BSF.4.10.10003292130540.13304-100000@twizors.rug.ac.be>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hello,

> As things stand now, there will be a 3.5 release with lowered public
> visibilty so that no new users jump on it and those who want 3.x can
> get it. If neccessary, a privately-burned CD can be shipped to them.

that sounds just sensibly to me. so people, stop shouting what you'd like
and what you don't and let the working people do their jobs and we'll all
get happy using fbsd. 

andy

==========================================================================
Dept. of Applied Mathematics and Computer Science, University of Ghent
Krijgslaan 281 - S9, B - 9000 Ghent, Belgium
Phone: +32-9-264.47.66, Fax: +32-9-264.49.95
E-mail: andy.georges@rug.ac.be 
==========================================================================



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


From owner-freebsd-stable  Wed Mar 29 11:55:57 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from pinhead.parag.codegen.com (207-44-235-154.CodeGen.COM [207.44.235.154])
	by hub.freebsd.org (Postfix) with ESMTP id E348537B8CB
	for <freebsd-stable@FreeBSD.ORG>; Wed, 29 Mar 2000 11:55:38 -0800 (PST)
	(envelope-from parag@pinhead.parag.codegen.com)
Received: from pinhead.parag.codegen.com (localhost.parag.codegen.com [127.0.0.1])
	by pinhead.parag.codegen.com (8.9.3/8.9.3) with ESMTP id LAA26713;
	Wed, 29 Mar 2000 11:55:26 -0800 (PST)
	(envelope-from parag@pinhead.parag.codegen.com)
To: "Morgan Davis" <mdavis@cts.com>
Cc: freebsd-stable@FreeBSD.ORG
Subject: Re: 4.0-stable + SMP + fxp = device timeout 
In-Reply-To: Message from "Morgan Davis" <mdavis@cts.com> 
   of "Wed, 29 Mar 2000 01:01:27 PST." <NABBLJGKKPMOKACIENPPEEGMCKAA.mdavis@cts.com> 
X-Image-URL: http://www.codegen.com/images/CG-logo-only.gif
X-URL: http://www.codegen.com
X-Face: =O'Kj74icvU|oS*<7gS/8'\Pbpm}okVj*@UC!IgkmZQAO!W[|iBiMs*|)n*`X
        ]pW%m>Oz_mK^Gdazsr.Z0/JsFS1uF8gBVIoChGwOy{EK=<6g?aHE`[\S]C]T0Wm
Date: Wed, 29 Mar 2000 11:55:26 -0800
Message-ID: <26709.954359726@pinhead.parag.codegen.com>
From: Parag Patel <parag@cgt.com>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Wed, 29 Mar 2000 01:01:27 PST, "Morgan Davis" wrote:
>
>The subject says it all.  Is this a known problem with SMP and the fxp
>driver? (Checked 4.0 errata and searched the mailing lists -- didn't see
>anything).

Works just fine here on my dual PII/300 ASUS P97-DS motherboard.  dmesg
output appended below.  The machine has been up since Sunday and
survived a "make -j8 buildworld", plays audio fine (tho' recording seems
to have problems), and in short seems pretty happy.


	-- Parag Patel

Copyright (c) 1992-2000 The FreeBSD Project.
Copyright (c) 1982, 1986, 1989, 1991, 1993
	The Regents of the University of California. All rights reserved.
FreeBSD 4.0-STABLE #10: Sun Mar 26 15:12:51 PST 2000
    parag@pinhead.parag.codegen.com:/usr/src4/src/sys/compile/PINHEAD
Timecounter "i8254"  frequency 1193182 Hz
CPU: Pentium II/Pentium II Xeon/Celeron (300.68-MHz 686-class CPU)
  Origin = "GenuineIntel"  Id = 0x634  Stepping = 4
  Features=0x80fbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,MMX>
real memory  = 268423168 (262132K bytes)
avail memory = 257011712 (250988K bytes)
Programming 24 pins in IOAPIC #0
IOAPIC #0 intpin 2 -> irq 0
FreeBSD/SMP: Multiprocessor motherboard
 cpu0 (BSP): apic id:  1, version: 0x00040011, at 0xfee00000
 cpu1 (AP):  apic id:  0, version: 0x00040011, at 0xfee00000
 io0 (APIC): apic id:  2, version: 0x00170011, at 0xfec00000
Preloaded elf kernel "kernel" at 0xc034a000.
Pentium Pro MTRR support enabled
npx0: <math processor> on motherboard
npx0: INT 16 interface
pcib0: <Intel 82443LX (440 LX) host to PCI bridge> on motherboard
pci0: <PCI bus> on pcib0
pcib1: <Intel 82443LX (440 LX) PCI-PCI (AGP) bridge> at device 1.0 on pci0
pci1: <PCI bus> on pcib1
pci1: <Matrox MGA Millennium II 2164WA-B AG graphics accelerator> at 0.0 irq 16
isab0: <Intel 82371AB PCI to ISA bridge> at device 4.0 on pci0
isa0: <ISA bus> on isab0
atapci0: <Intel PIIX4 ATA33 controller> port 0xd800-0xd80f at device 4.1 on pci0
ata0: at 0x1f0 irq 14 on atapci0
ata1: at 0x170 irq 15 on atapci0
pci0: <Intel 82371AB/EB (PIIX4) USB controller> at 4.2 irq 19
Timecounter "PIIX"  frequency 3579545 Hz
chip1: <Intel 82371AB Power management controller> port 0xe800-0xe80f at device 4.3 on pci0
ahc0: <Adaptec aic7880 Ultra SCSI adapter> port 0xd000-0xd0ff mem 0xe0000000-0xe0000fff irq 19 at device 6.0 on pci0
ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs
sym0: <810a> port 0xb800-0xb8ff mem 0xdf800000-0xdf8000ff irq 18 at device 10.0 on pci0
sym0: No NVRAM, ID 7, Fast-10, SE, parity checking
fxp0: <Intel EtherExpress Pro 10/100B Ethernet> port 0xb400-0xb41f mem 0xdf000000-0xdf0fffff,0xe2000000-0xe2000fff irq 17 at device 11.0 on pci0
fxp0: Ethernet address 00:a0:c9:da:98:26
pcm0: <AudioPCI ES1371> port 0xb000-0xb03f irq 16 at device 12.0 on pci0
fdc0: <NEC 72065B or clone> at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0
fdc0: FIFO enabled, 8 bytes threshold
fd0: <1440-KB 3.5" drive> on fdc0 drive 0
joy0 at port 0x201 on isa0
atkbdc0: <keyboard controller (i8042)> at port 0x60-0x6f on isa0
atkbd0: <AT Keyboard> irq 1 on atkbdc0
psm0: <PS/2 Mouse> irq 12 on atkbdc0
psm0: model MouseMan+, device ID 0
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
sc0: <System console> on isa0
sc0: VGA <16 virtual consoles, flags=0x200>
sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
sio0: type 16550A
sio1 at port 0x2f8-0x2ff irq 3 on isa0
sio1: type 16550A
sio2 at port 0x3e8-0x3ef irq 5 on isa0
sio2: type 16550A
sio3 at port 0x2e8-0x2ef irq 9 on isa0
sio3: type 16550A
ppc0: <Parallel port> at port 0x378-0x37f irq 7 on isa0
ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode
ppc0: FIFO with 16/16/9 bytes threshold
ppi0: <Parallel I/O> on ppbus0
lpt0: <Printer> on ppbus0
lpt0: Interrupt-driven port
APIC_IO: Testing 8254 interrupt delivery
APIC_IO: routing 8254 via IOAPIC #0 intpin 2
SMP: AP CPU #1 Launched!
ad2: 17206MB <IBM-DJNA-371800> [34960/16/63] at ata1-master using UDMA33
acd0: CDROM <TOSHIBA CD-ROM XM-6202B> at ata0-master using PIO4
Waiting 3 seconds for SCSI devices to settle
pass4 at sym0 bus 0 target 6 lun 0
pass4: <UMAX Astra 600S V1.6> Fixed Scanner SCSI-2 device 
pass4: 3.300MB/s transfers
da2 at ahc0 bus 0 target 2 lun 0
da2: <QUANTUM XP34550W LYK8> Fixed Direct Access SCSI-2 device 
da2: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled
da2: 4341MB (8890760 512 byte sectors: 255H 63S/T 553C)
Mounting root from ufs:/dev/da0s2a
cd0 at sym0 bus 0 target 4 lun 0
cd0: <SONY CD-R   CDU926S 1.1e> Removable Worm SCSI-2 device 
cd0: 10.000MB/s transfers (10.000MHz, offset 8)
cd0: Attempt to query device size failed: NOT READY, Medium not present
da1 at ahc0 bus 0 target 1 lun 0
da1: <IBM DCAS-34330W S65A> Fixed Direct Access SCSI-2 device 
da1: 40.000MB/s transfers (20.000MHz, offset 8, 16bit)
da1: 4134MB (8467200 512 byte sectors: 255H 63S/T 527C)
da0 at ahc0 bus 0 target 0 lun 0
da0: <IBM DCAS-34330W S65A> Fixed Direct Access SCSI-2 device 
da0: 40.000MB/s transfers (20.000MHz, offset 8, 16bit)
da0: 4134MB (8467200 512 byte sectors: 255H 63S/T 527C)


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


From owner-freebsd-stable  Wed Mar 29 12: 8:26 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from praseodumium.btinternet.com (praseodumium.btinternet.com [194.73.73.82])
	by hub.freebsd.org (Postfix) with ESMTP id 36F4037B6CF
	for <stable@freebsd.org>; Wed, 29 Mar 2000 12:08:07 -0800 (PST)
	(envelope-from mark@ukug.uk.freebsd.org)
Received: from [213.1.72.90] (helo=parish.my.domain)
	by praseodumium.btinternet.com with esmtp (Exim 2.05 #1)
	id 12aOk6-0004qp-00; Wed, 29 Mar 2000 21:07:06 +0100
Received: (from mark@localhost)
	by parish.my.domain (8.9.3/8.9.3) id VAA01303;
	Wed, 29 Mar 2000 21:07:36 +0100 (BST)
	(envelope-from mark)
Date: Wed, 29 Mar 2000 21:07:35 +0100
From: Mark Ovens <mark@ukug.uk.freebsd.org>
To: Ruslan Ermilov <ru@ucb.crimea.ua>
Cc: Tobias Roth <roth@iamexwi.unibe.ch>,
	Pieter Westland <pieterw@euronet.nl>, stable@freebsd.org
Subject: Re: HEADS UP: 3.x -> 4.0-STABLE upgrade instructions
Message-ID: <20000329210735.F237@parish>
References: <20000328213052.B234@parish> <Pine.GSO.4.10.10003282318010.27642-100000@giger> <20000328223140.C234@parish> <20000329092011.B24680@relay.ucb.crimea.ua>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0.1i
In-Reply-To: <20000329092011.B24680@relay.ucb.crimea.ua>; from ru@ucb.crimea.ua on Wed, Mar 29, 2000 at 09:20:11AM +0300
Organization: Total lack of
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Wed, Mar 29, 2000 at 09:20:11AM +0300, Ruslan Ermilov wrote:
> On Tue, Mar 28, 2000 at 10:31:40PM +0100, Mark Ovens wrote:
> > On Tue, Mar 28, 2000 at 11:21:46PM +0200, Tobias Roth wrote:
> > > 
> > > > > > This message appeared 166 times during ``make buildworld'':
> > > > > > 	/usr/libexec/ld-elf.so.1: Shared object "libc.so.4" not found
> > > > > > It also caused config(8) on the new kernel to fail, but
> > > > > > 	ldconfig -R /usr/obj/usr/src/lib/libc
> > > > > > cured that.
> > > > 
> > > > It goes away once you've done ``make installworld'' libc.so.3 was in
> > > > 3.x but 4.x uses libc.so.4 and while you're doing ``make buildworld''
> > > > and building a new kernel you've got a sort of hybrid system. I maybe
> > > > wrong here, but ISTR recall that the new compiler (2.95) gets built
> > > > with the old compiler and then immediately re-builds itself using
> > > > itself :-/
> > > 
> > > So, does that mean I can skip the ldconfig, just do make buildworld and
> > > make installworld as I always did and everything will work?
> > > Or do I *HAVE* to to the ldconfig?
> > > 
> > 
> > Well no, when you build the 4.x kernel for the first time (before
> > installworld) it needs the ldconfig in order to find libc.so.4 or the
> > config will fail. Having said that, ISTR that something is being
> > changed to remove the need to run ldconfig.
> > 
> This is not the case when you build the kernel with buildkernel target.

Ah yes, that was the "something" I was thinking of. Thanks.

> 
> 
> -- 
> Ruslan Ermilov		Sysadmin and DBA of the
> ru@ucb.crimea.ua	United Commercial Bank,
> ru@FreeBSD.org		FreeBSD committer,
> +380.652.247.647	Simferopol, Ukraine
> 
> http://www.FreeBSD.org	The Power To Serve
> http://www.oracle.com	Enabling The Information Age
> 
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-stable" in the body of the message

-- 
Seminars, n.:
       From "semi" and "arse", hence, any half-assed discussion.
________________________________________________________________
      FreeBSD - The Power To Serve http://www.freebsd.org
      My Webpage http://ukug.uk.freebsd.org/~mark/
mailto:mark@ukug.uk.freebsd.org             http://www.radan.com



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


From owner-freebsd-stable  Wed Mar 29 12:56:38 2000
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 69ADB37C171
	for <freebsd-stable@FreeBSD.ORG>; Wed, 29 Mar 2000 12:56:31 -0800 (PST)
	(envelope-from jkh@zippy.cdrom.com)
Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1])
	by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id MAA89165;
	Wed, 29 Mar 2000 12:57:23 -0800 (PST)
	(envelope-from jkh@zippy.cdrom.com)
To: Didier Derny <didier@omnix.net>
Cc: Martin Cracauer <cracauer@cons.org>, freebsd-stable@FreeBSD.ORG
Subject: Re: Let 3.x die ASAP? 
In-reply-to: Your message of "Wed, 29 Mar 2000 15:14:04 GMT."
             <Pine.BSF.3.96.1000329145706.13503A-100000@omnix.net> 
Date: Wed, 29 Mar 2000 12:57:23 -0800
Message-ID: <89162.954363443@zippy.cdrom.com>
From: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Goodbye, Mr Derny.  Don't let the door hit you on the ass on your
way out.


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


From owner-freebsd-stable  Wed Mar 29 13:11: 4 2000
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 3B30537BA0E
	for <freebsd-stable@FreeBSD.ORG>; Wed, 29 Mar 2000 13:10:16 -0800 (PST)
	(envelope-from jkh@zippy.cdrom.com)
Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1])
	by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id NAA89256;
	Wed, 29 Mar 2000 13:11:26 -0800 (PST)
	(envelope-from jkh@zippy.cdrom.com)
To: chad@DCFinc.com
Cc: cracauer@cons.org, freebsd-stable@FreeBSD.ORG
Subject: Re: Let 3.x die ASAP? 
In-reply-to: Your message of "Wed, 29 Mar 2000 11:11:06 MST."
             <200003291811.LAA16497@freeway.dcfinc.com> 
Date: Wed, 29 Mar 2000 13:11:26 -0800
Message-ID: <89253.954364286@zippy.cdrom.com>
From: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> Boy, I must not be paying attention in the right places.  The last
> pronouncement I thought I saw said that unless I contacted Walnut
> Creek and requested otherwise, I'd get 3.5 and then 4.1 on my
> subscription.  Which is just what I wanted (kinda like the
> 2.2.8->3.1 transition) so I didn't peep up.

This operational plan was simply changed when we saw that
circumstances were playing out differently.  Sorry for the confusion!

- Jordan


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


From owner-freebsd-stable  Wed Mar 29 13:11: 6 2000
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 14AF837BDD2
	for <freebsd-stable@FreeBSD.ORG>; Wed, 29 Mar 2000 13:10:17 -0800 (PST)
	(envelope-from jkh@zippy.cdrom.com)
Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1])
	by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id NAA89243;
	Wed, 29 Mar 2000 13:10:44 -0800 (PST)
	(envelope-from jkh@zippy.cdrom.com)
To: chad@DCFinc.com
Cc: cracauer@cons.org (Martin Cracauer), freebsd-stable@FreeBSD.ORG
Subject: Re: Let 3.x die ASAP? 
In-reply-to: Your message of "Wed, 29 Mar 2000 10:58:28 MST."
             <200003291758.KAA16393@freeway.dcfinc.com> 
Date: Wed, 29 Mar 2000 13:10:44 -0800
Message-ID: <89240.954364244@zippy.cdrom.com>
From: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> I can understand wanting to play with the newer stuff.  But I'm not
> committing bread-n-butter to anything not cooked in the field for a
> while.  I'll let others pioneer.  So when I see the raft of "I just
> upgraded my 3.x machine to 4.0" messages, my first reaction is
> "Why?" and my second is "better you than me" and my third is "I hope
> you uncover some obscure bug so it can be fixed before I get there."

And you know what?  For production shops, this is *exactly* the right
attitude to have. :)

- Jordan


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


From owner-freebsd-stable  Wed Mar 29 13:14:46 2000
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 CE95637B758; Wed, 29 Mar 2000 13:13:56 -0800 (PST)
	(envelope-from jkh@zippy.cdrom.com)
Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1])
	by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id NAA89325;
	Wed, 29 Mar 2000 13:15:13 -0800 (PST)
	(envelope-from jkh@zippy.cdrom.com)
To: Mike Smith <msmith@FreeBSD.ORG>
Cc: freebsd-stable@FreeBSD.ORG
Subject: Re: Let 3.x die ASAP? 
In-reply-to: Your message of "Wed, 29 Mar 2000 10:45:09 PST."
             <200003291845.KAA00946@mass.cdrom.com> 
Date: Wed, 29 Mar 2000 13:15:13 -0800
Message-ID: <89322.954364513@zippy.cdrom.com>
From: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> > 
> > why dont you call freebsd freebsd2000 freebsd2001....
> > 
> > freebsd seems running version after version and not stability...
> 
> Is "Didier" French for "Dennis"?

ROTFL.  Thanks Mike.  That's been the only laugh of the day so far!

- Jordan


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


From owner-freebsd-stable  Wed Mar 29 13:17: 4 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from got.wedgie.org (got.wedgie.org [216.181.169.146])
	by hub.freebsd.org (Postfix) with ESMTP id C751937B71D
	for <freebsd-stable@FreeBSD.ORG>; Wed, 29 Mar 2000 13:16:54 -0800 (PST)
	(envelope-from jgarman@got.wedgie.org)
Received: by got.wedgie.org (Postfix, from userid 1000)
	id A7199D905; Wed, 29 Mar 2000 16:16:49 -0500 (EST)
Date: Wed, 29 Mar 2000 16:16:49 -0500
From: Jason Garman <jgarman@wedgie.org>
To: hometeam <hometeam@techpower.net>
Cc: Gawel <gawel@sim.com.pl>, Eric Jacoboni <jaco@titine.fr.eu.org>,
	Grigoriy Strokin <grg@philol.msu.ru>, freebsd-stable@FreeBSD.ORG
Subject: Re: New kernel with its ATA drivers damages the filesystem
Message-ID: <20000329161649.A15367@got.wedgie.org>
Reply-To: jgarman@wedgie.org
References: <38E1D32B.F946EEB8@sim.com.pl> <Pine.BSF.4.21.0003290849210.3533-100000@techpower.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.4i
In-Reply-To: <Pine.BSF.4.21.0003290849210.3533-100000@techpower.net>; from hometeam on Wed, Mar 29, 2000 at 08:53:38AM -0500
X-Phase-Of-Moon: The Moon is Waning Crescent (33% of Full)
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Wed, Mar 29, 2000 at 08:53:38AM -0500, hometeam wrote:
> 
> I agree this really should be fix ...I notcied this straight away and sent
> mail to the group...Now it is damaging file Systems after the fact and
> wiping out file systems... I mean change the
> hardware ??? Why not fix the driver ?
> 
Because in my experience at least it is a hardware problem, not unlike the
old cmd640 and rz1000 bugs.  Granted there should be an easy way to
disable dma in the kernel config (so that you can disable it early on,
before bootup and also during installation)

enjoy
-- 
Jason Garman                                         http://web.wedgie.org/
Student, University of Maryland                          jgarman@wedgie.org
From fortune(1):                                              Whois: JAG145
  "... Had this been an actual emergency, we would have fled in terror,
   and you would not have been informed."


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


From owner-freebsd-stable  Wed Mar 29 13:22:37 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from kci.kciLink.com (kci.kciLink.com [204.117.82.1])
	by hub.freebsd.org (Postfix) with ESMTP id 8391837B775
	for <stable@FreeBSD.ORG>; Wed, 29 Mar 2000 13:21:45 -0800 (PST)
	(envelope-from khera@kciLink.com)
Received: from onceler.kcilink.com (onceler.kciLink.com [204.117.82.2])
	by kci.kciLink.com (Postfix) with ESMTP
	id 4DA04E897; Wed, 29 Mar 2000 16:21:43 -0500 (EST)
Received: (from khera@localhost)
	by onceler.kcilink.com (8.9.3/8.9.3) id QAA48607;
	Wed, 29 Mar 2000 16:21:43 -0500 (EST)
	(envelope-from khera@kci.kcilink.com)
From: Vivek Khera <khera@kciLink.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <14562.29670.896409.578807@onceler.kcilink.com>
Date: Wed, 29 Mar 2000 16:21:42 -0500 (EST)
To: Cy Schubert - ITSD Open Systems Group <Cy.Schubert@uumail.gov.bc.ca>
Cc: stable@FreeBSD.ORG
Subject: Re: "dangerously dedicated" 
In-Reply-To: <200003231358.FAA01112@cwsys.cwsent.com>
References: <14553.22411.265795.429126@onceler.kcilink.com>
	<200003231358.FAA01112@cwsys.cwsent.com>
X-Mailer: VM 6.72 under 21.1 (patch 8) "Bryce Canyon" XEmacs Lucid
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

>>>>> "CS" == Cy Schubert <- ITSD Open Systems Group <Cy.Schubert@uumail.gov.bc.ca>> writes:

>> Linux requires it to run, but doesn't hang forever if it doesn't
>> exist.  FreeBSD is the only system I've encountered so far that will
>> lock up (ie, does not respond to any keyboard requests or terminate

CS> What's there to scan?  The MBR always lives on the first sector of the 
CS> disk.  If it hung it was the BIOS that hung because it had nothing else 
CS> to do.

So, your telling me that on this one box I have, that Linux will boot
and recognize the disks, BSD/OS will boot and install, FreeDOS will
boot and recognize the disks but FreeBSD will boot but WON'T recognize
the disks (until I install an FDISK partition table) is the fault of
the BIOS?  Why on earth would the FreeBSD kernel be using the BIOS to
access the disk?

We must be speaking different languages, because I just can't seem to
explain it well enough to you.  So I guess I'll just go away because
it is way to hostile around here.  I really hope that the BSD/OS
engineers bring a more civilized tone to this FreeBSD arena.  They
sure are much nicer even when your not paying them.

-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Vivek Khera, Ph.D.                Khera Communications, Inc.
Internet: khera@kciLink.com       Rockville, MD       +1-301-545-6996
PGP & MIME spoken here            http://www.kciLink.com/home/khera/


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


From owner-freebsd-stable  Wed Mar 29 13:40:54 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from xxx.video-collage.com (xxx.video-collage.com [209.122.149.226])
	by hub.freebsd.org (Postfix) with ESMTP id 5FCE537B5BB
	for <stable@FreeBSD.ORG>; Wed, 29 Mar 2000 13:40:49 -0800 (PST)
	(envelope-from mi@video-collage.com)
X-Relay-IP: ‚ 
Received: from dufus.video-collage.com (dufus [10.222.222.77])
	by xxx.video-collage.com (8.9.1a/8.9.1) with ESMTP id QAA03224;
	Wed, 29 Mar 2000 16:40:47 -0500 (EST)
From: Mikhail Teterin <mi@video-collage.com>
Received: (from mi@localhost)
	by dufus.video-collage.com (8.9.3/8.9.3) id QAA98443;
	Wed, 29 Mar 2000 16:40:46 -0500 (EST)
	(envelope-from mi@xxx)
Message-Id: <200003292140.QAA98443@dufus.video-collage.com>
Subject: Re: "dangerously dedicated"
In-Reply-To: <14562.29670.896409.578807@onceler.kcilink.com> from Vivek Khera
 at "Mar 29, 2000 04:21:42 pm"
To: Vivek Khera <khera@kciLink.com>
Date: Wed, 29 Mar 2000 16:40:46 -0500 (EST)
Cc: Cy Schubert - ITSD Open Systems Group <Cy.Schubert@uumail.gov.bc.ca>,
	stable@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL68 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> We must be speaking different languages,  because I just can't seem to
> explain it well enough to you. So I guess I'll just go away because it
> is way to hostile around here. I really hope that the BSD/OS engineers
> bring a more civilized tone to  this FreeBSD arena. They sure are much
> nicer even when your not paying them.

FAAAR not  everyone on  this list  is a  "BSD/OS engineer".  Niceness, I
guess,  comes with  professionalism  (unfortunate,  but rare  exceptions
aside).

	-mi


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


From owner-freebsd-stable  Wed Mar 29 13:42:17 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from germanium.xtalwind.net (germanium.xtalwind.net [205.160.242.5])
	by hub.freebsd.org (Postfix) with ESMTP
	id 454EA37B6B0; Wed, 29 Mar 2000 13:41:51 -0800 (PST)
	(envelope-from jack@germanium.xtalwind.net)
Received: from localhost (jack@localhost)
	by germanium.xtalwind.net (8.9.3/8.9.3) with ESMTP id QAA29418;
	Wed, 29 Mar 2000 16:41:37 -0500 (EST)
Date: Wed, 29 Mar 2000 16:41:37 -0500 (EST)
From: jack <jack@germanium.xtalwind.net>
To: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Cc: Mike Smith <msmith@FreeBSD.ORG>, freebsd-stable@FreeBSD.ORG
Subject: Re: Let 3.x die ASAP? 
In-Reply-To: <89322.954364513@zippy.cdrom.com>
Message-ID: <Pine.BSF.4.21.0003291640150.29019-100000@germanium.xtalwind.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Today Jordan K. Hubbard wrote:

> > > why dont you call freebsd freebsd2000 freebsd2001....
> > > 
> > > freebsd seems running version after version and not stability...
> > 
> > Is "Didier" French for "Dennis"?
> 
> ROTFL.  Thanks Mike.  That's been the only laugh of the day so far!

Yeah, but he owes me a keyboard.  This one has a mouthful of
Coca-Cola all over it.  :)

--------------------------------------------------------------------------
Jack O'Neill                    Systems Administrator / Systems Analyst
jack@germanium.xtalwind.net     Crystal Wind Communications, Inc.
          Finger jack@germanium.xtalwind.net for my PGP key.
   PGP Key fingerprint = F6 C4 E6 D4 2F 15 A7 67   FD 09 E9 3C 5F CC EB CD
               enriched, vcard, HTML messages > /dev/null
--------------------------------------------------------------------------




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


From owner-freebsd-stable  Wed Mar 29 13:52:51 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from anvil.gatech.edu (anvil.gatech.edu [130.207.165.41])
	by hub.freebsd.org (Postfix) with ESMTP id 23BD837B7B0
	for <freebsd-stable@FreeBSD.org>; Wed, 29 Mar 2000 13:52:44 -0800 (PST)
	(envelope-from gte970m@prism.gatech.edu)
Received: from prism.gatech.edu (r45h34.res.gatech.edu [128.61.45.34])
	by anvil.gatech.edu (8.9.2/8.9.2) with ESMTP id QAA16790
	for <freebsd-stable@FreeBSD.org>; Wed, 29 Mar 2000 16:52:42 -0500 (EST)
Message-ID: <38E27AE5.76004F6B@prism.gatech.edu>
Date: Wed, 29 Mar 2000 16:51:33 -0500
From: Ralusp <gte970m@prism.gatech.edu>
Reply-To: ralusp@mail.com
Organization: Georgia Institute of Technology
X-Mailer: Mozilla 4.72 [en] (X11; U; FreeBSD 4.0-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: freebsd-stable@FreeBSD.org
Subject: subscribe
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

subscribe ralusp@mail.com


-- 
david raeman, ralusp@mail.com, icq 11799442  { just say yes you
georgia institute of technology, cs major    { little arsonist.
http://www.ralusp.net                        {      --tori amos


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


From owner-freebsd-stable  Wed Mar 29 13:59:23 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from smtp03.mrf.mail.rcn.net (smtp03.mrf.mail.rcn.net [207.172.4.62])
	by hub.freebsd.org (Postfix) with ESMTP id F3B9437B7AD
	for <freebsd-stable@freebsd.org>; Wed, 29 Mar 2000 13:59:15 -0800 (PST)
	(envelope-from lee@lcremeans.erols.com)
Received: from lcremeans.erols.com ([216.164.87.29])
	by smtp03.mrf.mail.rcn.net with esmtp (Exim 2.12 #3)
	id 12aQUa-0005tU-00; Wed, 29 Mar 2000 16:59:13 -0500
Received: (from lee@localhost)
	by lcremeans.erols.com (8.9.3/8.9.3) id QAA08468;
	Wed, 29 Mar 2000 16:59:04 -0500 (EST)
	(envelope-from lee)
Date: Wed, 29 Mar 2000 16:59:03 -0500
From: Lee Cremeans <lcremeans@erols.com>
To: Jason Garman <jgarman@wedgie.org>
Cc: hometeam <hometeam@techpower.net>, Gawel <gawel@sim.com.pl>,
	Eric Jacoboni <jaco@titine.fr.eu.org>,
	Grigoriy Strokin <grg@philol.msu.ru>, freebsd-stable@FreeBSD.ORG
Subject: Re: New kernel with its ATA drivers damages the filesystem
Message-ID: <20000329165903.B7857@lcremeans.erols.com>
References: <38E1D32B.F946EEB8@sim.com.pl> <Pine.BSF.4.21.0003290849210.3533-100000@techpower.net> <20000329161649.A15367@got.wedgie.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0i
In-Reply-To: <20000329161649.A15367@got.wedgie.org>; from jgarman@wedgie.org on Wed, Mar 29, 2000 at 04:16:49PM -0500
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 Wed, Mar 29, 2000 at 04:16:49PM -0500, Jason Garman wrote:
> On Wed, Mar 29, 2000 at 08:53:38AM -0500, hometeam wrote:
> > 
> > I agree this really should be fix ...I notcied this straight away and sent
> > mail to the group...Now it is damaging file Systems after the fact and
> > wiping out file systems... I mean change the
> > hardware ??? Why not fix the driver ?
> > 
> Because in my experience at least it is a hardware problem, not unlike the
> old cmd640 and rz1000 bugs.  Granted there should be an easy way to
> disable dma in the kernel config (so that you can disable it early on,
> before bootup and also during installation)

Some things I've noticed about all this:

1) My machine is running FreeBSD 3.4-STABLE (soon to be 4.0-STABLE) on a
Soyo SY-5EHM board (using an ETEQ chipset, really a relabelled VIA MVP3)
board, and in the time I've had it (over a year now), I've not seen any
serious problems or filesystem corruption in DMA mode, and I've done
stressful things like make buildworld on it many times without trouble. Just
FYI, I have a Seagate Medalist Pro 9.1GB, a Toshiba 32x CDROM and an LS-120
drive hooked up (HD's on the primary channel, CD-ROM and floppy on the
second).

2) Here's the weird bit...I cut an ISO of 4.0-RELEASE...uh, last Friday I
think? and I decided to play with it on an Intel SE440BX2 board. (Celeron
300A processor, I think). I was noticing all sorts of weird
filesystem-corruption problems while it was installing ("panic: dup alloc"
was one of them), and it also had trouble seeing the hard drive I had hooked
up (an old (1997) JTS Champion 3.2GB). Changing out the memory, of all
things, seemed to make it work. THis drive also worked without a problem
once I connected it to my machine (to check out 4.0 without having to pull
the trigger on my main disk).

PS: IDE unfortunately still sucks when you have two devices on the same
channel (the LS-120 lags the CD-ROM horribly when I try to use both at
once), but that's not a FreeBSD problem, that's a "I need a SCSI LS-120"
problem (they're hard to find, but they're out there). :)

-lee

-- 
+--------------------------------------------------------------------+
|      Lee Cremeans -- Manassas, VA, USA  (WakkyMouse on WTnet)      |  
|         lcremeans@erols.com | http://wakky.dyndns.org/~lee         |


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


From owner-freebsd-stable  Wed Mar 29 14: 0:42 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from xxx.video-collage.com (xxx.video-collage.com [209.122.149.226])
	by hub.freebsd.org (Postfix) with ESMTP id 6B88737C06F
	for <stable@FreeBSD.ORG>; Wed, 29 Mar 2000 14:00:32 -0800 (PST)
	(envelope-from mi@video-collage.com)
X-Relay-IP: ‚ 
Received: from dufus.video-collage.com (dufus [10.222.222.77])
	by xxx.video-collage.com (8.9.1a/8.9.1) with ESMTP id RAA03299
	for <stable@FreeBSD.ORG>; Wed, 29 Mar 2000 17:00:30 -0500 (EST)
From: Mikhail Teterin <mi@video-collage.com>
Received: (from mi@localhost)
	by dufus.video-collage.com (8.9.3/8.9.3) id RAA00270
	for stable@FreeBSD.ORG; Wed, 29 Mar 2000 17:00:30 -0500 (EST)
	(envelope-from mi@xxx)
Message-Id: <200003292200.RAA00270@dufus.video-collage.com>
Subject: Re: "dangerously dedicated" (Corrected)
In-Reply-To: <200003292140.QAA98443@dufus.video-collage.com> from Mikhail Teterin
 at "Mar 29, 2000 04:40:46 pm"
To: stable@FreeBSD.ORG
Date: Wed, 29 Mar 2000 17:00:30 -0500 (EST)
X-Mailer: ELM [version 2.4ME+ PL68 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> FAAAR not  everyone on this list  is a "BSD/OS engineer".  Niceness, I
> guess, comes  with professionalism  (unfortunate, but  rare exceptions
> aside).

That  was meant  to  say "``not  everyone  on this  list  is a  "FreeBSD
engineer"''. Sorry, everyone,

	-mi


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


From owner-freebsd-stable  Wed Mar 29 14:17:10 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from kci.kciLink.com (kci.kciLink.com [204.117.82.1])
	by hub.freebsd.org (Postfix) with ESMTP
	id 7025737BC61; Wed, 29 Mar 2000 14:17:07 -0800 (PST)
	(envelope-from khera@kciLink.com)
Received: from onceler.kcilink.com (onceler.kciLink.com [204.117.82.2])
	by kci.kciLink.com (Postfix) with ESMTP
	id 45B6DE897; Wed, 29 Mar 2000 17:17:06 -0500 (EST)
Received: (from khera@localhost)
	by onceler.kcilink.com (8.9.3/8.9.3) id RAA76496;
	Wed, 29 Mar 2000 17:17:06 -0500 (EST)
	(envelope-from khera@kci.kcilink.com)
From: Vivek Khera <khera@kciLink.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <14562.32994.82948.656128@onceler.kcilink.com>
Date: Wed, 29 Mar 2000 17:17:06 -0500 (EST)
To: Kris Kennaway <kris@FreeBSD.org>
Cc: "Geoffrey T. Cheshire" <gches@goodnet.com>,
	freebsd-stable <freebsd-stable@FreeBSD.ORG>
Subject: Re: What cruft to remove after 3.4 -> 4.0?
In-Reply-To: <Pine.BSF.4.21.0003231224090.11927-100000@freefall.freebsd.org>
References: <Pine.GSO.4.05.10003212338500.25557-100000@goodguy.goodnet.com>
	<Pine.BSF.4.21.0003231224090.11927-100000@freefall.freebsd.org>
X-Mailer: VM 6.72 under 21.1 (patch 8) "Bryce Canyon" XEmacs Lucid
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

>>>>> "KK" == Kris Kennaway <kris@FreeBSD.org> writes:

KK> On Thu, 23 Mar 2000, Geoffrey T. Cheshire wrote:
>> Is there a canonical list of things like this to pare?  Should I use
>> pkg_delete?

KK> Here's the canonical list:

KK> openssl
KK> openssh

What about ntp?


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


From owner-freebsd-stable  Wed Mar 29 14:31: 7 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from ravel.n2.net (ravel.n2.net [207.113.132.20])
	by hub.freebsd.org (Postfix) with ESMTP id 05B1437B700
	for <freebsd-stable@FreeBSD.ORG>; Wed, 29 Mar 2000 14:31:04 -0800 (PST)
	(envelope-from jgibbons@nike.relcast.com)
Received: from nike.relcast.com (nike.relcast.com [207.113.133.19])
	by ravel.n2.net (8.9.1/8.9.1) with ESMTP id OAA06181
	for <freebsd-stable@FreeBSD.ORG>; Wed, 29 Mar 2000 14:31:02 -0800 (PST)
Received: (from jgibbons@localhost)
	by nike.relcast.com (8.9.3/8.9.3) id OAA04257
	for freebsd-stable@FreeBSD.ORG; Wed, 29 Mar 2000 14:31:12 -0800 (PST)
	(envelope-from jgibbons)
Date: Wed, 29 Mar 2000 14:31:12 -0800
From: Jeff Gibbons <jgibbons@protogate.com>
To: freebsd-stable@FreeBSD.ORG
Subject: Re: Mainatain a Local CVSUP Server
Message-ID: <20000329143111.E4148@nike.relcast.com>
References: <20000329064607.A49954@lunatic.oneinsane.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.6i
In-Reply-To: <20000329064607.A49954@lunatic.oneinsane.net>; from Ron 'The InSaNe One' Rosson on Wed, Mar 29, 2000 at 06:46:07AM -0800
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

The easiest way to get started is:

   # cd /usr/ports/net/cvsup-mirror
   # make
   # make install

Then look to see what it did (for instance, it will put a command
into /etc/crontab to cvsup periodically; and it will put a cvsupd.sh
script into /usr/local/etc/rc.d, to start the cvsupd daemon.).

The port makes it really easy to set this up.

Jeff
-- 
Jeff Gibbons           jeff@protogate.com
Protogate              (858) 571-1501


On Wed, Mar 29, 2000 at 06:46:07AM -0800, Ron 'The InSaNe One' Rosson wrote:
> Times are a changing for me......
> 
> I just have been tasked with what are the requirements to maintain a
> local cvsup server for our personal use. Is there a guide/link/? to show
> one how to go about this.
> 


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


From owner-freebsd-stable  Wed Mar 29 14:33:38 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from ants.pocketscience.com (gateway1.pocketscience.com [209.24.64.3])
	by hub.freebsd.org (Postfix) with ESMTP id 2FE7237BE34
	for <freebsd-stable@freebsd.org>; Wed, 29 Mar 2000 14:33:30 -0800 (PST)
	(envelope-from brian@pocketscience.com)
Received: from pocketscience.com (southpark.i.pocketscience.com [10.10.4.2]) by ants.pocketscience.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2448.0)
	id HXB8F6YZ; Wed, 29 Mar 2000 14:33:29 -0800
Message-ID: <38E284B9.8A14D1D2@pocketscience.com>
Date: Wed, 29 Mar 2000 14:33:29 -0800
From: Brian Nelson <brian@pocketscience.com>
Organization: PocketScience, Inc
X-Mailer: Mozilla 4.72 [en] (X11; U; FreeBSD 4.0-STABLE i386)
X-Accept-Language: en, pdf
MIME-Version: 1.0
To: freebsd-stable@freebsd.org
Subject: Re: Let 3.x die ASAP?
References: <Pine.BSF.3.96.1000329080220.7123A-100000@omnix.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

This message can be summed up with:

"I am a whiner, and I just want to complain.  I don't have any real
issues I want to brung up, but I'll 'not stable' a bunch of times. 
Granted I have never read the docs on keeping up with -STABLE, and I
hardly know what /usr/src/etc is for, but all these machines I have
pgraded form 3.1 to 3.4 sucks."

Didier Derny wrote:
> 
> why dont you call freebsd freebsd2000 freebsd2001....
> 
> freebsd seems running version after version and not stability...
> 
> I think that during 1994-1998 I made the right choice to choose FreeBSD
> instead of linux.
> 
> in 1999 (3.x) I was not so sure at all, no stability too many problems.
> 
> In 2000 it's getting worse, for me FreeBSD is not stable at all
> the future of FreeBSD is not so clear, version follow after version but
> I still have no support for my sound board, realplayer, oracle...
> The clients are telling me to install Linux instead of FreeBSD (for
> oracle)...
> I've just finished uprading the machines to 3.4-release and you are
> telling me that there is no future for 3.X...
> 
> I'm about to buy a smp machine but I see so many horror stories on
> the mailling lists that I'm not sure at all that I should use a smp
> machine (or install linux instead of FreeBSD)...
> 
> one of our client is running a smp machine with 3.2-BETA without any
> probleme...
> 
> another client is running 3.4-RELEASE and his machine is rebooting on
> heavy load...
> 
> with all these problemes the end of 3.x will probably be the end
> of FreeBSD for me!
> 
> --
> Didier Derny
> didier@omnix.net
> 
> On Tue, 28 Mar 2000, Martin Cracauer wrote:
> 
> > A bit of a controvesical question, for sure.
> >
> > I am so impressed with the results of upgrading my more important
> > machines to 4.0 or 4-stable that I could imagine not to produce any
> > more 3.x releases.
> >
> > Let us consider what happens when we release 3.5 before or at the same
> > time as 4.1:
> > - People will publish reviews based on 3.5 instead of 4.1. As usual,
> >   an unadaequate number of them running on SMP machines.
> > - People will run into inferious hardware support, especially they
> >   will have trouble with large IDE disks and/or IDE PCI controller.
> >   Similar issues for Laptop users.
> > - People will continue to run with inferiour NFS, Linux emulator etc.
> >   The same applies to networking fixes against attacks, especially
> >   DOS.
> > - People will choose 3.5 over 4.1 and will later go through an
> >   3.x->4.x upgrade for no good reason.
> > - The remaining issues in 4.x (especially hardware) aren't addressed
> >   as fast. There will be some issues with "unclean" usage that the
> >   core userbase doesn't use that don't come up until the masses jump
> >   on them.
> >
> > For me, the real reason is that I now hate the latest 3.x after seeing
> > the improvements. It is near to junk, IMHO.
> >
> > Several machine of mine had gone instable while moving from 3.[01] to
> > 3.4-stable and I suspected hardware trouble. I didn't debug it because
> > I didn't want to mess with 3.x anymore. Now after upgrading to 4.x the
> > same machines are rock-stable again. It is my impression that the 3.x
> > branch lost the required testing when the core committers moved to
> > 4.0-current. Higher releases of 3.x are just not polished/tested
> > enough anymore, beside the undoubted concrete bug fixes.
> >
> > Speaking of testing by committers, I also hate to have machines for
> > three branches running to develop bugfixes that apply to more than
> > -current. In fact my last 3.x machine (besides a 3.1 machine that
> > doesn't have the IDE troubles I have with 3.4-stable) is now a
> > production machine of my employer that I'd like to upgrade as well. I
> > couldn't think of a good reason to delay that upgrade for 3 or 6
> > months if my boss asked me. When i upgrade, I had to commit userland
> > bugfixes to 3.x with only testing them on a newer branch. Kernel
> > bugfixes would be impossible unless I find someone to test them for
> > me.
> >
> > I assume that I'm not alone here. That many bug-fixing committers will
> > not move with 3 machines along the current branches and that 3.5 will
> > not be a worthy successor to our previous *.5 releases.
> >
> > Opinions?
> >
> > Martin
> > --
> > %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
> > Martin Cracauer <cracauer@cons.org> http://www.cons.org/cracauer/
> >   Tel.: (private) +4940 5221829 Fax.: (private) +4940 5228536
> >
> >
> > To Unsubscribe: send mail to majordomo@FreeBSD.org
> > with "unsubscribe freebsd-stable" in the body of the message
> >
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-stable" in the body of the message


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


From owner-freebsd-stable  Wed Mar 29 14:35: 9 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
	by hub.freebsd.org (Postfix) with ESMTP
	id C73E337BB00; Wed, 29 Mar 2000 14:34:54 -0800 (PST)
	(envelope-from kris@FreeBSD.org)
Received: from localhost (kris@localhost)
	by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id OAA64807;
	Wed, 29 Mar 2000 14:34:54 -0800 (PST)
	(envelope-from kris@FreeBSD.org)
X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs
Date: Wed, 29 Mar 2000 14:34:54 -0800 (PST)
From: Kris Kennaway <kris@FreeBSD.org>
To: Vivek Khera <khera@kciLink.com>
Cc: "Geoffrey T. Cheshire" <gches@goodnet.com>,
	freebsd-stable <freebsd-stable@FreeBSD.ORG>
Subject: Re: What cruft to remove after 3.4 -> 4.0?
In-Reply-To: <14562.32994.82948.656128@onceler.kcilink.com>
Message-ID: <Pine.BSF.4.21.0003291434080.64546-100000@freefall.freebsd.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Wed, 29 Mar 2000, Vivek Khera wrote:

> >> Is there a canonical list of things like this to pare?  Should I use
> >> pkg_delete?
> 
> KK> Here's the canonical list:
> 
> KK> openssl
> KK> openssh
> 
> What about ntp?

Hmm, could be. I'm not sure which versions we have in ports, 3.x and 4.x.

Kris

----
In God we Trust -- all others must submit an X.509 certificate.
    -- Charles Forsythe <forsythe@alum.mit.edu>



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


From owner-freebsd-stable  Wed Mar 29 14:59:21 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13])
	by hub.freebsd.org (Postfix) with ESMTP id 5F2CD37B696
	for <FreeBSD-Stable@freebsd.org>; Wed, 29 Mar 2000 14:58:57 -0800 (PST)
	(envelope-from ben@scientia.demon.co.uk)
Received: from strontium.scientia.demon.co.uk ([192.168.91.36] ident=exim)
	by scientia.demon.co.uk with esmtp (Exim 3.12 #1)
	id 12aRQ8-000Hma-00; Wed, 29 Mar 2000 23:58:40 +0100
Received: (from ben) by strontium.scientia.demon.co.uk (Exim 3.12 #7)
	id 12aRQ8-00075p-00; Wed, 29 Mar 2000 23:58:40 +0100
Date: Wed, 29 Mar 2000 23:58:40 +0100
From: Ben Smithurst <ben@scientia.demon.co.uk>
To: Jeremiah Gowdy <jgowdy@home.com>
Cc: FreeBSD-Stable@FreeBSD.ORG
Subject: Re: 4.0 Kernel
Message-ID: <20000329235840.F50487@strontium.scientia.demon.co.uk>
References: <Pine.BSF.4.10.10003271228100.48901-100000@Eagle.ZGIA.zp.ua> <38E065C5.418DA948@newsguy.com> <001901bf98db$9b897580$0100000a@vista1.sdca.home.com> <20000328224158.A2261@evil.2y.net> <006201bf99ac$15649080$0100000a@vista1.sdca.home.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0i
In-Reply-To: <006201bf99ac$15649080$0100000a@vista1.sdca.home.com>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Jeremiah Gowdy wrote:

>> If you go to http:///www.de.freebsd.org/de/gif/bsd/ there should be a lot
> of
>> artwork to look at. They even have the famous nomad daemon on a cliff pic.
>>
>> --cokane
> 
> For some reason my name server cannot resolve that hostname.  Can you give
> me the IP ?

Name:    baerenklau.de.freebsd.org
Address:  195.185.195.14
Aliases:  www.de.freebsd.org

-- 
Ben Smithurst / ben@scientia.demon.co.uk / PGP: 0x99392F7D


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


From owner-freebsd-stable  Wed Mar 29 15:13:41 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from mail4s.biglobe.ne.jp (mail4s.biglobe.ne.jp [210.147.14.249])
	by hub.freebsd.org (Postfix) with ESMTP id 1003A37B745
	for <freebsd-stable@freebsd.org>; Wed, 29 Mar 2000 15:11:10 -0800 (PST)
	(envelope-from ushida@msa.biglobe.ne.jp)
Received: from mail-gw.biglobe.ne.jp (mailsv18.biglobe.ne.jp [133.205.12.240])
	by mail4s.biglobe.ne.jp (8.9.1+3.1W/3.7W-99081617) with ESMTP id IAA16791
	for <freebsd-stable@freebsd.org>; Thu, 30 Mar 2000 08:11:06 +0900 (JST)
Received: from mail-relay.biglobe.ne.jp by mail-gw.biglobe.ne.jp (3.7W-INET_GW)
	id AAA23339 for <freebsd-stable@freebsd.org>; Tue, 28 Mar 2000 00:32:44 +0900 (JST)
Received: from pop215.biglobe.ne.jp by mail-relay.biglobe.ne.jp (3.7W-BIGLOBE-relay)
	id AAA01047 for <freebsd-stable@freebsd.org>; Tue, 28 Mar 2000 00:32:26 +0900 (JST)
Date: Tue, 28 Mar 2000 00:29:31 +0900
Message-Id: <1000328002931.414EE703.1022002@msa.biglobe.ne.jp>
X-Biglobe-Sender: ushida@msa.biglobe.ne.jp
X-Biglobe-Date: Tue, 28 Mar 2000 00:29:31 +0900
Posted-Date: Tue, 28 Mar 2000 00:29:26 +0900 (JST)
From: Jun USHIDA <ushida@msa.biglobe.ne.jp>
To: freebsd-stable@freebsd.org
Subject: Re: Compiling FORTRAN code on -stable
In-Reply-To: Your message of "Sun, 26 Mar 2000 22:30:26 -0500".
	<20000326223026.A46836@ipass.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
X-Mailer: mnews [version 1.22PL2] 2000-02/25(Fri)
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

In article <20000326223026.A46836@ipass.net> aa8vb@ipass.net wrote:

|Apparently f77 compilers will eat this, but our f77 (from bin or ports)
|will not.

RELNOTES.TXT of FreeBSD 4.0-RELEASE says,
> The f77 emulation via f2c has been replaced by a native F77 compiler.

In my 4.0-STABLE,
/usr/bin/f77         (g77 v0.5.24)
/usr/local/bin/fc    (/usr/ports/lang/{f77,f2c},/usr/ports/devel/fpp)

Your example FORTRAN code can be compiled with /usr/bin/f77(g77).

It would seem that /usr/bin/f77(g77) shows slightly better performance than 
/usr/local/bin/fc. I think that's why f2c is replased in 4.0-RELEASE or later.
Is this recognition right ?
--
Jun Ushida
PGP finger print =  E2 03 93 99 0B C4 C0 35  80 BC FF A3 CE 5C 96 C7


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


From owner-freebsd-stable  Wed Mar 29 15:26:39 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from set.spradley.org (set.spradley.tmi.net [207.170.107.99])
	by hub.freebsd.org (Postfix) with ESMTP id 0E4E737BC50
	for <freebsd-stable@FreeBSD.ORG>; Wed, 29 Mar 2000 15:26:33 -0800 (PST)
	(envelope-from tsprad@set.spradley.org)
Received: from set.spradley.org (localhost.spradley.tmi.net [127.0.0.1])
	by set.spradley.org (8.9.3/8.9.2) with ESMTP id LAA54114;
	Sun, 26 Mar 2000 11:27:36 -0600 (CST)
	(envelope-from tsprad@set.spradley.org)
Message-Id: <200003261727.LAA54114@set.spradley.org>
X-Mailer: exmh version 2.1.1 10/15/1999
To: "Jerry Bell" <jerry@bellnetworks.net>
Cc: "Ben Smithurst" <ben@scientia.demon.co.uk>,
	freebsd-stable@FreeBSD.ORG
Subject: Re: ps, w, top and netstat problem 
In-reply-to: Your message of "Sat, 25 Mar 2000 23:25:37 EST."
             <01b001bf96db$55ee0650$f7bbb1d0@netrex.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sun, 26 Mar 2000 11:27:36 -0600
From: Ted Spradley <tsprad@set.spradley.org>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> Yep, I did.  Sorry for not mentioning that (I did include the uname -a,
> though).  I'm kind of at a loss as well.

One more thing:  Are you sure that the ps and top, etc. you're running 
are the new ones you built and installed?  Might there be an old version 
somewhere else in your $PATH?  Try "which ps", or "/bin/ps".

> 
> Jerry
> 
> ----- Original Message -----
> From: Ben Smithurst <ben@scientia.demon.co.uk>
> To: Jerry Bell <jerry@bellnetworks.net>
> Cc: <freebsd-stable@FreeBSD.ORG>
> Sent: Sunday, March 26, 2000 10:34 AM
> Subject: Re: ps, w, top and netstat problem
> 
> 
> > Jerry Bell wrote:
> >
> > > I just tried removing the 'options PROCFS' from the kernel config and
> > > recompiled.  After a reboot, I get the same thing.
> > >
> > > I ran another make buildworld and make installworld, so the ps, w, top
> and
> > > netstat binaries are _definately_ in sync with the kernel.  I removed
> all
> > > compiler options during this make world.
> >
> > ok, I hate to ask questions which imply you're stupid, but you *did* do
> > 'make install' in the kernel compile directory, didn't you? It's just
> > that you've never explicitly mentioned that, and I don't know what else
> > would cause these problems.
> >
> > --
> > Ben Smithurst / ben@scientia.demon.co.uk / PGP: 0x99392F7D
> >
> 
> 
> 
> 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 29 15:26:53 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from set.spradley.org (set.spradley.tmi.net [207.170.107.99])
	by hub.freebsd.org (Postfix) with ESMTP id D062137BC9D
	for <stable@FreeBSD.ORG>; Wed, 29 Mar 2000 15:26:36 -0800 (PST)
	(envelope-from tsprad@set.spradley.org)
Received: from set.spradley.org (localhost.spradley.tmi.net [127.0.0.1])
	by set.spradley.org (8.9.3/8.9.2) with ESMTP id WAA52534;
	Sat, 25 Mar 2000 22:24:32 -0600 (CST)
	(envelope-from tsprad@set.spradley.org)
Message-Id: <200003260424.WAA52534@set.spradley.org>
X-Mailer: exmh version 2.1.1 10/15/1999
To: chad@DCFinc.com
Cc: winter@jurai.net (Matthew N. Dodd), stable@FreeBSD.ORG
Subject: Re: FIXED --> Thanks! Re: ep0 eeprom failed to come ready... 
In-reply-to: Your message of "Sat, 25 Mar 2000 21:06:57 MST."
             <200003260406.VAA04621@freeway.dcfinc.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sat, 25 Mar 2000 22:24:32 -0600
From: Ted Spradley <tsprad@set.spradley.org>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


> This makes me wary.  One of the reasons I like UNIX is the
> assumptions implicit in its organization that the users might
> actually know what they're doing.
> 
> Every time Microsoft and the PC industry have tried to remove the
> responsibility and control from the users (EISA--no jumpers,
> Plug-n-Pray--no config program), they've generally made things worse.
[...]
> Bah!  This, to me, isn't progress.

Amen, brother!  Right on!

> 
> 	-crl
> --
> Chad R. Larson (CRL15)   602-953-1392   Brother, can you paradigm?
> chad@dcfinc.com         chad@larsons.org          larson1@home.net   
> DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207




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


From owner-freebsd-stable  Wed Mar 29 15:41:29 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from mass.cdrom.com (mg135-034.ricochet.net [204.179.135.34])
	by hub.freebsd.org (Postfix) with ESMTP id D201537B696
	for <stable@FreeBSD.ORG>; Wed, 29 Mar 2000 15:41:22 -0800 (PST)
	(envelope-from msmith@mass.cdrom.com)
Received: from mass.cdrom.com (localhost [127.0.0.1])
	by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id PAA02677;
	Wed, 29 Mar 2000 15:43:28 -0800 (PST)
	(envelope-from msmith@mass.cdrom.com)
Message-Id: <200003292343.PAA02677@mass.cdrom.com>
X-Mailer: exmh version 2.1.1 10/15/1999
To: Ted Spradley <tsprad@set.spradley.org>
Cc: chad@DCFinc.com, winter@jurai.net (Matthew N. Dodd),
	stable@FreeBSD.ORG
Subject: Re: FIXED --> Thanks! Re: ep0 eeprom failed to come ready... 
In-reply-to: Your message of "Sat, 25 Mar 2000 22:24:32 CST."
             <200003260424.WAA52534@set.spradley.org> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 29 Mar 2000 15:43:27 -0800
From: Mike Smith <msmith@freebsd.org>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> 
> > This makes me wary.  One of the reasons I like UNIX is the
> > assumptions implicit in its organization that the users might
> > actually know what they're doing.
> > 
> > Every time Microsoft and the PC industry have tried to remove the
> > responsibility and control from the users (EISA--no jumpers,
> > Plug-n-Pray--no config program), they've generally made things worse.
> [...]
> > Bah!  This, to me, isn't progress.
> 
> Amen, brother!  Right on!

I'm not sure what planet you're on, but it's not this one.

-- 
\\ Give a man a fish, and you feed him for a day. \\  Mike Smith
\\ Tell him he should learn how to fish himself,  \\  msmith@freebsd.org
\\ and he'll hate you for a lifetime.             \\  msmith@cdrom.com




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


From owner-freebsd-stable  Wed Mar 29 16:29:25 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from jking1.lgc.com (jking1.lgc.com [134.132.228.2])
	by hub.freebsd.org (Postfix) with ESMTP id 9D65637B6DD
	for <FreeBSD-Stable@FreeBSD.ORG>; Wed, 29 Mar 2000 16:29:20 -0800 (PST)
	(envelope-from king@sstar.com)
Received: from marble (marble [134.132.228.8])
	by jking1.lgc.com (8.9.3/8.9.3) with SMTP id SAA19270;
	Wed, 29 Mar 2000 18:28:54 -0600 (CST)
	(envelope-from king@sstar.com)
Message-ID: <002101bf99de$ef5a5f90$08e48486@marble>
From: "Jim King" <king@sstar.com>
To: "Ben Smithurst" <ben@scientia.demon.co.uk>,
	"Jeremiah Gowdy" <jgowdy@home.com>
Cc: <FreeBSD-Stable@FreeBSD.ORG>
References: <Pine.BSF.4.10.10003271228100.48901-100000@Eagle.ZGIA.zp.ua> <38E065C5.418DA948@newsguy.com> <001901bf98db$9b897580$0100000a@vista1.sdca.home.com> <20000328224158.A2261@evil.2y.net> <006201bf99ac$15649080$0100000a@vista1.sdca.home.com> <20000329235840.F50487@strontium.scientia.demon.co.uk>
Subject: Re: 4.0 Kernel
Date: Wed, 29 Mar 2000 18:28:54 -0600
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.6700
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> Jeremiah Gowdy wrote:
>
> >> If you go to http:///www.de.freebsd.org/de/gif/bsd/ there should be a
lot
> > of
> >> artwork to look at. They even have the famous nomad daemon on a cliff
pic.
> >>
> >> --cokane
> >
> > For some reason my name server cannot resolve that hostname.  Can you
give
> > me the IP ?
>
> Name:    baerenklau.de.freebsd.org
> Address:  195.185.195.14
> Aliases:  www.de.freebsd.org
>
> --
> Ben Smithurst / ben@scientia.demon.co.uk / PGP: 0x99392F7D

There's three slashes in the URL above, which IE (and Netscape?) chokes on.
http://www.de.freebsd.org/de/gif/bsd/ works better for me.

Jim




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


From owner-freebsd-stable  Wed Mar 29 17: 2:46 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from mail1.rdc3.on.home.com (mail1.rdc3.on.home.com [24.2.9.40])
	by hub.freebsd.org (Postfix) with ESMTP id 2157237B7EA
	for <freebsd-stable@FreeBSD.ORG>; Wed, 29 Mar 2000 17:02:38 -0800 (PST)
	(envelope-from cwass99@home.com)
Received: from tristan.net ([24.114.108.234]) by mail1.rdc3.on.home.com
          (InterMail v4.01.01.00 201-229-111) with ESMTP
          id <20000330010236.FBNA22349.mail1.rdc3.on.home.com@tristan.net>;
          Wed, 29 Mar 2000 17:02:36 -0800
Content-Length: 2030
Message-ID: <XFMail.000329195714.cwass99@home.com>
X-Mailer: XFMail 1.4.0 on FreeBSD
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <92014.954325875@zippy.cdrom.com>
Date: Wed, 29 Mar 2000 19:57:14 -0500 (EST)
From: Colin <cwass99@home.com>
To: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Subject: Re: Let 3.x die ASAP?
Cc: freebsd-stable@FreeBSD.ORG
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

    I realize Jordan doesn't need my help to defend his stand on this issue ;),
but I think there's a reasonable compromise happening here that should be
pointed out.  With a network only 3.5 coming out and 4.0 through cd
distribution, it should not be a great challenge to ensure the 'new' public
focus is on 4.0.  I really suspect reviewers and new users would take a cd over
the reqirement of installing an older release (3.4) then doing a source upgrade
to check out 3.5.  This would, IMHO, pretty much ensure 'the public' seeing the
latest and greatest.
     Having said that, for a variety of reasons I will probably need 3.5 and I
suspect there is a large (albeit silent) group that shares my reasoning:  I
have older equipment that works marvelously with 3.4 but chokes horribly on
4.0, especially during the install.  This relates (I suspect, but I'm still
investigating) back to the ATA issues discussed elsewhere in this list.  I see
no reason to spend the money on an upgrade for a machine that does it's job
perfectly well (it's a spare P133, older drives, etc, running some services for
my home network) with a perfectly acceptable OS. 
     I also look forward to 4.1, as I have a newer box running 4.0 ;)

cheers,
Colin


On 29-Mar-00 Jordan K. Hubbard wrote:
>> I now :-) I ask you/core/WC to reconsider this decision. I want to

> 
> Sorry, but this really isn't something I can do.  3.5 has already
> essentially been promised and, as you can see, a lot of people don't
> agree with your point of view at all and would view this as a very bad
> move on my part.
> 
> I should also note that this has nothing whatsoever to do with CDROM
> sales since I already told Walnut Creek CDROM awhile back that I would
> not be doing a CDROM version of 3.5 - it will be a network-only
> release.  We have enough work just placing one line of CD products
> into the market and the whole 2.2.8/3.x overlap was really difficult
> to map onto our existing customer base.  All customers will simply
> receive 4.0, 4.1 .. 4.x.


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


From owner-freebsd-stable  Wed Mar 29 17:13:45 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161])
	by hub.freebsd.org (Postfix) with ESMTP id 1ED2537B71D
	for <freebsd-stable@FreeBSD.ORG>; Wed, 29 Mar 2000 17:13:42 -0800 (PST)
	(envelope-from doconnor@gsoft.com.au)
Received: from cain.gsoft.com.au (doconnor@cain [203.38.152.97])
	by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id KAA19850;
	Thu, 30 Mar 2000 10:43:29 +0930 (CST)
	(envelope-from doconnor@gsoft.com.au)
Message-ID: <XFMail.000330104329.doconnor@gsoft.com.au>
X-Mailer: XFMail 1.4.0 on FreeBSD
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <20000329164349.A5311@tomcat.xs4all.nl>
Date: Thu, 30 Mar 2000 10:43:29 +0930 (CST)
From: "Daniel O'Connor" <doconnor@gsoft.com.au>
To: Arnout Boer <arnout@xs4all.nl>
Subject: Re: 4.0-stable + SMP + fxp = device timeout
Cc: freebsd-stable@FreeBSD.ORG, Morgan Davis <mdavis@cts.com>,
	Brad Knowles <blk@skynet.be>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


On 29-Mar-00 Arnout Boer wrote:
>  [cut]
>  fxp0: <Intel EtherExpress Pro 10/100B Ethernet> port 0x6500-0x653f mem
>  0xe100000
>  0-0xe10fffff,0xe1100000-0xe1100fff irq 18 at device 10.0 on pci0
>  fxp0: Ethernet address 00:90:27:42:d9:b7
>  fxp0: supplying EUI64: 00:90:27:ff:fe:42:d9:b7

Does anything else live on that irq?

---
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
"The nice thing about standards is that there
are so many of them to choose from."
  -- Andrew Tanenbaum


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


From owner-freebsd-stable  Wed Mar 29 17:49:14 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from mail2.rdc3.on.home.com (mail2.rdc3.on.home.com [24.2.9.41])
	by hub.freebsd.org (Postfix) with ESMTP id 7F05F37B722
	for <freebsd-stable@FreeBSD.ORG>; Wed, 29 Mar 2000 17:48:57 -0800 (PST)
	(envelope-from cwass99@home.com)
Received: from tristan.net ([24.114.108.234]) by mail2.rdc3.on.home.com
          (InterMail v4.01.01.00 201-229-111) with ESMTP
          id <20000330014855.EYML1049.mail2.rdc3.on.home.com@tristan.net>;
          Wed, 29 Mar 2000 17:48:55 -0800
Content-Length: 1082
Message-ID: <XFMail.000329204332.cwass99@home.com>
X-Mailer: XFMail 1.4.0 on FreeBSD
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <38E1D32B.F946EEB8@sim.com.pl>
Date: Wed, 29 Mar 2000 20:43:32 -0500 (EST)
From: Colin <cwass99@home.com>
To: Gawel <gawel@sim.com.pl>
Subject: Re: New kernel with its ATA drivers damages the filesystem
Cc: freebsd-stable@FreeBSD.ORG, Grigoriy Strokin <grg@philol.msu.ru>,
	Eric Jacoboni <jaco@titine.fr.eu.org>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

     I had the same problem during the install.  I managed to work around it by
doing the install with only one drive and the cd on the primary IDE channel,
nothing on the secondary.  I then had no difficulty adding the second drive back
into the mix.  I tried this only because I seem to remember a comment about this
during the RC stages, but I honestly can't remeber the context or list (I
searched the lists for 2 days but couldn't find it).  The kernel (GENERIC, I
haven't had time to build a custom yet) even managed to figure out the second
disk required pio without any prodding from me.
     I should mention that the single drive I used for the install was capable
of DMA modes, so this might not help.

cheers,
Colin

On 29-Mar-00 Gawel wrote:
> Hello,
> The same message ( ata0: resetting devices .. done; ad0: WRITE command
> timeout - resetting)
> has appeared to me but during instalation 4.0R form CDROM.
> I have no idea how to install 4.0 on my PC.
> Is there any trick to switch on hw.atamodes=pio,pio,pio during instalation
> from CD?
> 
> With regards,
> Gawel


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


From owner-freebsd-stable  Wed Mar 29 17:55:54 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from weeble.dyndns.org (ubppp234-173.dialin.buffalo.edu [128.205.234.173])
	by hub.freebsd.org (Postfix) with ESMTP id 702C637B6E8
	for <freebsd-stable@FreeBSD.ORG>; Wed, 29 Mar 2000 17:55:34 -0800 (PST)
	(envelope-from cjm2@earthling.net)
Received: from shithead (shithead.weeble.dyndns.org [10.0.0.2])
	by weeble.dyndns.org (8.9.3/8.9.3) with SMTP id UAA24660;
	Wed, 29 Mar 2000 20:54:36 -0500 (EST)
	(envelope-from cjm2@earthling.net)
From: "C J Michaels" <cjm2@earthling.net>
To: "Didier Derny" <didier@omnix.net>,
	"Jordan K. Hubbard" <jkh@zippy.cdrom.com>,
	"Martin Cracauer" <cracauer@cons.org>, <mo@servo.ccr.org>
Cc: <freebsd-stable@FreeBSD.ORG>
Subject: RE: Let 3.x die ASAP?
Date: Wed, 29 Mar 2000 20:54:34 -0500
Message-ID: <NDBBILKDCLLECBCLPMBICEBJCAAA.cjm2@earthling.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 IMO, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
In-reply-to: <Pine.BSF.3.96.1000329145706.13503A-100000@omnix.net>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Ok, I'm sorry if this is long, and off topic for the list, this will be my
only posting.  I've condensed all of my replies to this discussion into this
one message, so please skim through the whole thing.

===== Didier (and others):
I for one, have been running 3.x-STABLE since it came out.  I have had _1_
kernel panic in that whole time, and that kernel panic was _my_ fault.  I
have had nothing but stability with my 3.x-STABLE system.  You'll find that
there are MANY people who have had nothing but stability from their
3.X-STABLE systems.

Judging the stability of 3.x by the postings in this list is inaccurate.
The purpose of this list is to help with problems/questions/etc...  Of
course people aren't going to post daily "my 3.x system works great,
thanks!".  It's a waste of bandwidth.

You're complaining that a given release of 3.x isn't stable, but yet you
complain that it is in constant development.  If a given release of -STABLE
has a genuine stability issue, it gets fixed, and committed.  So yes it is
constantly developing.  Would you prefer that bug fixes were just boxed up
and released only once a year?  Would you prefer that they were not fixed at
all?

There are several small points that several people in this discussion need
to come to terms with:
   1. No OS is ever 100% bug free.  It's not humanly possible.
   2. STABLE != STATIC.  Given #1 -STABLE needs to be in a constant state of
change because as bugs are found, they are fixed and committed.  This
doesn't mean untested developmental code, just (mainly) fixes.
   3. -CURRENT is where the new and developmental code goes.  It is a
testing ground for new features and developements, it is not for those
looking for stability.
   4. No one is forcing anyone to do anything.  If you are happy with 2.1.2
then keep running it.  If your 3.2-BETA is as solid as a rock, keep running
it.  If you install an x.0 release of _ANY_ software and expect it to be
perfect in every way, you are deluding yourself.

===== Developers:
Yes, this is a FREE OS, that is FREEly available, and is developed (mainly)
by people giving their FREE time.  Despite that, if 90% of users want the
log messages in pig-latin, but the core team feels it's a stupid idea, how
do you think users will react?  They will eventually find an OS that allow
them to have log messages in pig-latin.  Just shrugging your shoulders and
saying "The OS is FREE, so deal with it" isn't going to keep that user base
around.


===== Martin:
An addendum to the above note.  I realize that developement on the 3.x
branch many not be interesting or exciting anymore, and you would like to
move on.  You do need to consider your users here as well.  It stands to
reason that a good number of active FreeBSD users are still on the 3.x
branch.  I would venture to guess more than 50%.  When I say active, I do
not mean those people that are still running 2.2.x on a production machine
that hasn't been rebootedn 2 years.

Do you truly expect the majority (50% or more) of said users to jump to 4.0
as soon as it's released?  Just because someone (anyone) says it's good.  I
realize that 4.0 is probably one of the most stable x.0 releases of ANYTHING
in the world (I've read Jordan's posts).  But it's still a x.0 release, and
shouldn't (in my mind) hold the title of -STABLE until the shake down
leading up to 4.1.  Until such time 3.x-STABLE should be actively supported.
If you force people down a path they don't want to go, they will resist.
You will be driving more people away than you will be helping.

=====
Please don't take this as a complaint, just a comment.  I am very happy with
the direction FreeBSD is going right now and actively promote it.  For the
record I am running 3.4-STABLE on my "production" machine and am currenlty
playing/learning/testing/beating/breaking RELENG_4 on a spare machine.  I
may move to 4.x before 4.1 comes out, I may not, only time will tell.

-Chris

-----Original Message-----
From: owner-freebsd-stable@FreeBSD.ORG
[mailto:owner-freebsd-stable@FreeBSD.ORG]On Behalf Of Didier Derny
Sent: Wednesday, March 29, 2000 10:14 AM
To: Jordan K. Hubbard
Cc: Martin Cracauer; freebsd-stable@FreeBSD.ORG
Subject: Let 3.x die ASAP?



the problem is really simple, I' WORKING with FreeBSD not PLAYING
you are like 3 years boys you are trowing their old toys each time
they have an new one.

I can't an many people can't upgrade the system on their machine
at the actual rythm of FreeBSD version (each one supposed to be the best
one and solve most of the problems :-))) )

without a real stability (like the one with 2.x) this product
has no more value than linux or solaris, sco...

even If I have a great hope for FreeBSD 4.x, I consider that actually
4.0 is just bullshit (I mean a developper's toy but I wanted a strong
word [perhaps too strong I fear]) and you are already
throwing the old one (3.x).

A I told you before, I'm preparing a way to be able to choose between
FreeBSD and something else (netbsd, openbsd, linux...) but not before
next year.

perhaps that the abandon of FreeBSD 3.x is simply the first effect
of what I was saying in my previous mails ?

  +-----------+
  |           |
  |  FreeBSD  |
  |    RIP    |
  |           |
~~~~~~~~~~~~~~~~~~

--
Didier Derny
didier@omnix.net


On Wed, 29 Mar 2000, Jordan K. Hubbard wrote:

> I thought the end came for you after you started spreading the FUD the
> last time.  As Winston Churchill said to Neville Chamberlain after
> his highly successful trip to Munich:  "For god's sake man, GO!"
>
> - Jordan
>



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


From owner-freebsd-stable  Wed Mar 29 19:47:12 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from vms2.isc.rit.edu (vms2.isc.rit.edu [129.21.3.9])
	by hub.freebsd.org (Postfix) with ESMTP id D7F6237BA11
	for <stable@FreeBSD.ORG>; Wed, 29 Mar 2000 19:47:05 -0800 (PST)
	(envelope-from djr8620@ritvax.isc.rit.edu)
Received: from rit.edu ([129.21.145.13])
 by ritvax.isc.rit.edu (PMDF V5.2-32 #41784)
 with ESMTPA id <01JNMEA58XI6FX574W@ritvax.isc.rit.edu> for stable@FreeBSD.ORG;
 Wed, 29 Mar 2000 22:46:58 EST
Date: Wed, 29 Mar 2000 22:44:06 -0500
From: Dale Robson <djr8620@ritvax.isc.rit.edu>
Subject: 4.0 stable upgrade trouble
To: stable <stable@FreeBSD.ORG>
Message-id: <38E2CD86.594A7335@rit.edu>
MIME-version: 1.0
X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.0.36 i386)
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
X-Accept-Language: en
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

To anyone who can help,
	I've been trying to upgrade from 3.3 stable to 4.0 stable and I've been
having trouble getting it to work.  I have run make buildworld and that
worked.  Then during make installworld I got an error so that only half
the files were installed.  
	The trouble that I now have is that the newly upgraded 'make' links
with the old versions of several libraries.  When I try to run make it
says: "Bad sytem call".  Is there a way to fix make without being able
to use make?  I've made a couple attempts at running a staticly linked
version on make compiled on other boxes but they all argue about the
".include <bsd.prog.mk>" lines in the make files.  Thank you for any
help.

Dale Robson


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


From owner-freebsd-stable  Wed Mar 29 19:54: 2 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38])
	by hub.freebsd.org (Postfix) with ESMTP
	id 7AB6137BACB; Wed, 29 Mar 2000 19:53:59 -0800 (PST)
	(envelope-from obrien@NUXI.ucdavis.edu)
Received: from dragon.nuxi.com (root@d60-024.leach.ucdavis.edu [169.237.60.24])
	by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id TAA11711;
	Wed, 29 Mar 2000 19:53:59 -0800 (PST)
	(envelope-from obrien@dragon.nuxi.com)
Received: (from obrien@localhost)
	by dragon.nuxi.com (8.9.3/8.9.1) id TAA27062;
	Wed, 29 Mar 2000 19:53:58 -0800 (PST)
	(envelope-from obrien)
Date: Wed, 29 Mar 2000 19:53:58 -0800
From: "David O'Brien" <obrien@NUXI.ucdavis.edu>
To: stable@freebsd.org, current@freebsd.org
Subject: build broken for libobjc on RELENG_4
Message-ID: <20000329195358.A27052@dragon.nuxi.com>
Reply-To: obrien@NUXI.ucdavis.edu
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0.1i
X-Operating-System: FreeBSD 4.0-CURRENT
Organization: The NUXI BSD group
X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3  90 76 5D 69 58 D9 98 7A
X-Pgp-Keyid: 34F9F9D5
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

I know that the build is broken when installing libobjc on RELENG_4.
I did a fat fingered typo and now need some bits to catch up to me via
cvsup, but I have to leave for an hour or so.  Very sorry for this.

-- 
-- David    (obrien@NUXI.com)


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


From owner-freebsd-stable  Wed Mar 29 20: 7:29 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from samhouston.kingwoodcable.com (samhouston.kingwoodcable.com [208.223.8.78])
	by hub.freebsd.org (Postfix) with ESMTP id B159D37B604
	for <freebsd-stable@FreeBSD.org>; Wed, 29 Mar 2000 20:07:24 -0800 (PST)
	(envelope-from bobmabry@kingwoodcable.com)
Received: from kingwoodcable.com (alpha1490.kingwoodcable.com [208.223.14.90]) by samhouston.kingwoodcable.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21)
	id H8HW4542; Wed, 29 Mar 2000 21:57:46 -0600
Message-ID: <38E2D2EE.5C764054@kingwoodcable.com>
Date: Wed, 29 Mar 2000 22:07:10 -0600
From: Bob Mabry <bobmabry@kingwoodcable.com>
X-Mailer: Mozilla 4.72 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: freebsd-stable@FreeBSD.org
Subject: subscribe
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

 


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


From owner-freebsd-stable  Wed Mar 29 22:23:10 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from ns.binep.ac.ru (ns.binep.ac.ru [193.233.37.5])
	by hub.freebsd.org (Postfix) with ESMTP
	id 5AFBD37B5EE; Wed, 29 Mar 2000 22:22:58 -0800 (PST)
	(envelope-from goshik@binep.ac.ru)
Received: from serv2.binep.ac.ru (serv2 [193.233.44.77])
	by ns.binep.ac.ru (8.9.3/8.9.3) with SMTP id KAA05951;
	Thu, 30 Mar 2000 10:33:22 +0400 (MSD)
	(envelope-from goshik@binep.ac.ru)
Reply-To: "Igor B. Bykhalo" <goshik@binep.ac.ru>
From: "Igor B. Bykhalo" <goshik@binep.ac.ru>
To: "-questions@FreeBSD" <freebsd-questions@freebsd.org>
Cc: "-stable@FreeBSD" <freebsd-stable@freebsd.org>
Subject: Doing math - need advice (was: Compiling FORTRAN code on -stable)
Date: Thu, 30 Mar 2000 09:12:59 +0300
Message-ID: <01bf9a0e$ffb5fe00$0000e9c1@serv2.binep.ac.ru>
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.0913.2206
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.0913.2200
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

We are going to use mathematical package
(EPR spectra simulation). Program relies
on BLAS, LAPACK and ARPACK libraries - all
in Fortran 77. Program itself can be built
using gcc, egcs or pgcc.

Questions:

1. What is the recommended way to build
   f77 libraries to get maximum performance?
   Should we use g77 from 4.0-Release, or
   we can stay on 3-Stable and use f2c + pgcc
   (from ports)?

2. Does anyone know incarnations of the mentioned
   libraries in C language?

3. Where to read some general advices on the optimization
   of math perfomance (under FreeBSD)? :)

TIA,
Igor

P.S. Sorry for cross-post, I _really_ need your advice...





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


From owner-freebsd-stable  Wed Mar 29 22:31:45 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from knight.cons.org (knight.cons.org [194.233.237.86])
	by hub.freebsd.org (Postfix) with ESMTP id 8E23A37B779
	for <freebsd-stable@FreeBSD.ORG>; Wed, 29 Mar 2000 22:31:40 -0800 (PST)
	(envelope-from cracauer@knight.cons.org)
Received: (from cracauer@localhost)
	by knight.cons.org (8.9.3/8.9.3) id IAA23652;
	Thu, 30 Mar 2000 08:31:35 +0200 (CEST)
Date: Thu, 30 Mar 2000 08:31:34 +0200
From: Martin Cracauer <cracauer@cons.org>
To: C J Michaels <cjm2@earthling.net>
Cc: freebsd-stable@FreeBSD.ORG
Subject: Re: Let 3.x die ASAP?
Message-ID: <20000330083133.A23540@cons.org>
References: <Pine.BSF.3.96.1000329145706.13503A-100000@omnix.net> <NDBBILKDCLLECBCLPMBICEBJCAAA.cjm2@earthling.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0.1i
In-Reply-To: <NDBBILKDCLLECBCLPMBICEBJCAAA.cjm2@earthling.net>; from cjm2@earthling.net on Wed, Mar 29, 2000 at 08:54:34PM -0500
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

You're summary is a bad one at least as my attributions are concerned.
I don't care for "sexy" branches, I just don't want want to maintain
*three* branch-tracking machines and the other developers seem to
think on the same line.  It doesn't really matter whether that
3.x-untested symptom already affected 3.4, it will for sure affect
every 3.x work after the creation of RELENG_4.

I'm an idiot I even started the thread, shooting an already dead CD
release of 3.5, but I didn't know that.  I think my summary is better
that the way things turned out is not only a good compromise but make
most people happy.

In <NDBBILKDCLLECBCLPMBICEBJCAAA.cjm2@earthling.net>, C J Michaels wrote: 
> Ok, I'm sorry if this is long, and off topic for the list, this will be my
> only posting.  I've condensed all of my replies to this discussion into this
> one message, so please skim through the whole thing.
> 
> ===== Didier (and others):
> I for one, have been running 3.x-STABLE since it came out.  I have had _1_
> kernel panic in that whole time, and that kernel panic was _my_ fault.  I
> have had nothing but stability with my 3.x-STABLE system.  You'll find that
> there are MANY people who have had nothing but stability from their
> 3.X-STABLE systems.
> 
> Judging the stability of 3.x by the postings in this list is inaccurate.
> The purpose of this list is to help with problems/questions/etc...  Of
> course people aren't going to post daily "my 3.x system works great,
> thanks!".  It's a waste of bandwidth.
> 
> You're complaining that a given release of 3.x isn't stable, but yet you
> complain that it is in constant development.  If a given release of -STABLE
> has a genuine stability issue, it gets fixed, and committed.  So yes it is
> constantly developing.  Would you prefer that bug fixes were just boxed up
> and released only once a year?  Would you prefer that they were not fixed at
> all?
> 
> There are several small points that several people in this discussion need
> to come to terms with:
>    1. No OS is ever 100% bug free.  It's not humanly possible.
>    2. STABLE != STATIC.  Given #1 -STABLE needs to be in a constant state of
> change because as bugs are found, they are fixed and committed.  This
> doesn't mean untested developmental code, just (mainly) fixes.
>    3. -CURRENT is where the new and developmental code goes.  It is a
> testing ground for new features and developements, it is not for those
> looking for stability.
>    4. No one is forcing anyone to do anything.  If you are happy with 2.1.2
> then keep running it.  If your 3.2-BETA is as solid as a rock, keep running
> it.  If you install an x.0 release of _ANY_ software and expect it to be
> perfect in every way, you are deluding yourself.
> 
> ===== Developers:
> Yes, this is a FREE OS, that is FREEly available, and is developed (mainly)
> by people giving their FREE time.  Despite that, if 90% of users want the
> log messages in pig-latin, but the core team feels it's a stupid idea, how
> do you think users will react?  They will eventually find an OS that allow
> them to have log messages in pig-latin.  Just shrugging your shoulders and
> saying "The OS is FREE, so deal with it" isn't going to keep that user base
> around.
> 
> 
> ===== Martin:
> An addendum to the above note.  I realize that developement on the 3.x
> branch many not be interesting or exciting anymore, and you would like to
> move on.  You do need to consider your users here as well.  It stands to
> reason that a good number of active FreeBSD users are still on the 3.x
> branch.  I would venture to guess more than 50%.  When I say active, I do
> not mean those people that are still running 2.2.x on a production machine
> that hasn't been rebootedn 2 years.
> 
> Do you truly expect the majority (50% or more) of said users to jump to 4.0
> as soon as it's released?  Just because someone (anyone) says it's good.  I
> realize that 4.0 is probably one of the most stable x.0 releases of ANYTHING
> in the world (I've read Jordan's posts).  But it's still a x.0 release, and
> shouldn't (in my mind) hold the title of -STABLE until the shake down
> leading up to 4.1.  Until such time 3.x-STABLE should be actively supported.
> If you force people down a path they don't want to go, they will resist.
> You will be driving more people away than you will be helping.
> 
> =====
> Please don't take this as a complaint, just a comment.  I am very happy with
> the direction FreeBSD is going right now and actively promote it.  For the
> record I am running 3.4-STABLE on my "production" machine and am currenlty
> playing/learning/testing/beating/breaking RELENG_4 on a spare machine.  I
> may move to 4.x before 4.1 comes out, I may not, only time will tell.
> 
> -Chris
> 
> -----Original Message-----
> From: owner-freebsd-stable@FreeBSD.ORG
> [mailto:owner-freebsd-stable@FreeBSD.ORG]On Behalf Of Didier Derny
> Sent: Wednesday, March 29, 2000 10:14 AM
> To: Jordan K. Hubbard
> Cc: Martin Cracauer; freebsd-stable@FreeBSD.ORG
> Subject: Let 3.x die ASAP?
> 
> 
> 
> the problem is really simple, I' WORKING with FreeBSD not PLAYING
> you are like 3 years boys you are trowing their old toys each time
> they have an new one.
> 
> I can't an many people can't upgrade the system on their machine
> at the actual rythm of FreeBSD version (each one supposed to be the best
> one and solve most of the problems :-))) )
> 
> without a real stability (like the one with 2.x) this product
> has no more value than linux or solaris, sco...
> 
> even If I have a great hope for FreeBSD 4.x, I consider that actually
> 4.0 is just bullshit (I mean a developper's toy but I wanted a strong
> word [perhaps too strong I fear]) and you are already
> throwing the old one (3.x).
> 
> A I told you before, I'm preparing a way to be able to choose between
> FreeBSD and something else (netbsd, openbsd, linux...) but not before
> next year.
> 
> perhaps that the abandon of FreeBSD 3.x is simply the first effect
> of what I was saying in my previous mails ?
> 
>   +-----------+
>   |           |
>   |  FreeBSD  |
>   |    RIP    |
>   |           |
> ~~~~~~~~~~~~~~~~~~
> 
> --
> Didier Derny
> didier@omnix.net
> 
> 
> On Wed, 29 Mar 2000, Jordan K. Hubbard wrote:
> 
> > I thought the end came for you after you started spreading the FUD the
> > last time.  As Winston Churchill said to Neville Chamberlain after
> > his highly successful trip to Munich:  "For god's sake man, GO!"
> >
> > - Jordan
> >
> 
> 
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-stable" in the body of the message

-- 
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
Martin Cracauer <cracauer@cons.org> http://www.cons.org/cracauer/
  Tel.: (private) +4940 5221829 Fax.: (private) +4940 5228536


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


From owner-freebsd-stable  Wed Mar 29 22:33:44 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
	by hub.freebsd.org (Postfix) with ESMTP
	id C377237B694; Wed, 29 Mar 2000 22:33:41 -0800 (PST)
	(envelope-from kris@FreeBSD.org)
Received: from localhost (kris@localhost)
	by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id WAA77794;
	Wed, 29 Mar 2000 22:33:41 -0800 (PST)
	(envelope-from kris@FreeBSD.org)
X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs
Date: Wed, 29 Mar 2000 22:33:41 -0800 (PST)
From: Kris Kennaway <kris@FreeBSD.org>
To: Dale Robson <djr8620@ritvax.isc.rit.edu>
Cc: stable <stable@FreeBSD.ORG>
Subject: Re: 4.0 stable upgrade trouble
In-Reply-To: <38E2CD86.594A7335@rit.edu>
Message-ID: <Pine.BSF.4.21.0003292233001.66563-100000@freefall.freebsd.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

You should have read the UPDATING file before attempting this. It explains
the hoops you need to jump through. I don't know whether you can easily
recover from where you are now, it might be best to restore the system
directories from a backup and start again.

Kris

On Wed, 29 Mar 2000, Dale Robson wrote:

> To anyone who can help,
> 	I've been trying to upgrade from 3.3 stable to 4.0 stable and I've been
> having trouble getting it to work.  I have run make buildworld and that
> worked.  Then during make installworld I got an error so that only half
> the files were installed.  
> 	The trouble that I now have is that the newly upgraded 'make' links
> with the old versions of several libraries.  When I try to run make it
> says: "Bad sytem call".  Is there a way to fix make without being able
> to use make?  I've made a couple attempts at running a staticly linked
> version on make compiled on other boxes but they all argue about the
> ".include <bsd.prog.mk>" lines in the make files.  Thank you for any
> help.
> 
> Dale Robson
> 
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-stable" in the body of the message
> 

----
In God we Trust -- all others must submit an X.509 certificate.
    -- Charles Forsythe <forsythe@alum.mit.edu>



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


From owner-freebsd-stable  Wed Mar 29 22:36:54 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from jason.argos.org (a1-3b058.neo.rr.com [24.93.181.58])
	by hub.freebsd.org (Postfix) with ESMTP
	id 2EA6037B7D7; Wed, 29 Mar 2000 22:36:51 -0800 (PST)
	(envelope-from mike@argos.org)
Received: from localhost (mike@localhost)
	by jason.argos.org (8.9.1/8.9.1) with ESMTP id BAA07786;
	Thu, 30 Mar 2000 01:36:49 -0500
Date: Thu, 30 Mar 2000 01:36:49 -0500 (EST)
From: Mike Nowlin <mike@argos.org>
To: Mike Smith <msmith@FreeBSD.ORG>
Cc: Ted Spradley <tsprad@set.spradley.org>, stable@FreeBSD.ORG
Subject: Re: FIXED --> Thanks! Re: ep0 eeprom failed to come ready... 
In-Reply-To: <200003292343.PAA02677@mass.cdrom.com>
Message-ID: <Pine.LNX.4.05.10003300135180.7709-100000@jason.argos.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


> > Amen, brother!  Right on!
> 
> I'm not sure what planet you're on, but it's not this one.

Must have mistakenly left that mail pre-processor on that calls
ports/misc/jive...  :)

(Actually, not a bad idea.....  Hmmm...............)

mike




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


From owner-freebsd-stable  Wed Mar 29 22:44:59 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from noc.mainstreet.net (noc.mainstreet.net [207.5.0.45])
	by hub.freebsd.org (Postfix) with ESMTP
	id 1530437BB6B; Wed, 29 Mar 2000 22:44:54 -0800 (PST)
	(envelope-from mark@noc.mainstreet.net)
Received: (from mark@localhost)
	by noc.mainstreet.net (8.9.2/8.9.2) id WAA14635;
	Wed, 29 Mar 2000 22:44:44 -0800 (PST)
Date: Wed, 29 Mar 2000 22:44:44 -0800 (PST)
Message-Id: <200003300644.WAA14635@noc.mainstreet.net>
From: Mark Kent <mark@noc.mainstreet.net>
To: goshik@binep.ac.ru
Cc: freebsd-questions@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG
In-reply-to: <01bf9a0e$ffb5fe00$0000e9c1@serv2.binep.ac.ru>
	(goshik@binep.ac.ru)
Subject: Re: Doing math - need advice (was: Compiling FORTRAN code on -stable)
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

2. Does anyone know incarnations of the mentioned
   libraries in C language?

I know they exist, but cannot point to a source.
The place to start looking is right here:

   http://netlib2.cs.utk.edu/

You may even find the answers to your other two questions
there.

-mark


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


From owner-freebsd-stable  Thu Mar 30  0:12:49 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38])
	by hub.freebsd.org (Postfix) with ESMTP
	id A371937B66C; Thu, 30 Mar 2000 00:12:44 -0800 (PST)
	(envelope-from obrien@NUXI.ucdavis.edu)
Received: from dragon.nuxi.com (root@d60-024.leach.ucdavis.edu [169.237.60.24])
	by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id AAA12694;
	Thu, 30 Mar 2000 00:12:12 -0800 (PST)
	(envelope-from obrien@dragon.nuxi.com)
Received: (from obrien@localhost)
	by dragon.nuxi.com (8.9.3/8.9.1) id AAA27757;
	Thu, 30 Mar 2000 00:12:12 -0800 (PST)
	(envelope-from obrien)
Date: Thu, 30 Mar 2000 00:12:12 -0800
From: "David O'Brien" <obrien@freebsd.org>
To: stable@freebsd.org, current@freebsd.org
Subject: BUILD FIXED  (was: build broken for libobjc on RELENG_4)
Message-ID: <20000330001211.A27737@dragon.nuxi.com>
Reply-To: obrien@freebsd.org
References: <20000329195358.A27052@dragon.nuxi.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0.1i
In-Reply-To: <20000329195358.A27052@dragon.nuxi.com>; from obrien@NUXI.ucdavis.edu on Wed, Mar 29, 2000 at 07:53:58PM -0800
X-Operating-System: FreeBSD 4.0-CURRENT
Organization: The NUXI BSD group
X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3  90 76 5D 69 58 D9 98 7A
X-Pgp-Keyid: 34F9F9D5
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

build breakage due to libobjc has been fixed.


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


From owner-freebsd-stable  Thu Mar 30  1:10:51 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from carlton.innotts.co.uk (carlton.innotts.co.uk [212.56.32.2])
	by hub.freebsd.org (Postfix) with ESMTP id 14B9637B711
	for <freebsd-stable@FreeBSD.ORG>; Thu, 30 Mar 2000 01:10:47 -0800 (PST)
	(envelope-from robmel@innotts.co.uk)
Received: from muffin.highwire.local (pool-1-p9.innotts.co.uk [212.56.33.9])
	by carlton.innotts.co.uk (8.9.3/8.9.3) with ESMTP id KAA13464;
	Thu, 30 Mar 2000 10:10:32 +0100
Received: from [172.16.17.20] (robsmac.highwire.local [172.16.17.20])
	by muffin.highwire.local (8.9.3/8.9.3) with ESMTP id KAA00569;
	Thu, 30 Mar 2000 10:05:53 +0100 (BST)
	(envelope-from robmel@innotts.co.uk)
Mime-Version: 1.0
X-Sender: robmel@wrcmail (Unverified)
Message-Id: <v04220802b508c4d650ae@[172.16.17.20]>
In-Reply-To: <Pine.BSF.4.21.0003290146040.18478-100000@workhorse.iMach.com>
References: <Pine.BSF.4.21.0003290146040.18478-100000@workhorse.iMach.com>
Date: Thu, 30 Mar 2000 10:05:44 +0100
To: Didier Derny <didier@omnix.net>
From: Robin Melville <robmel@innotts.co.uk>
Subject: Re: Let 3.x die ASAP?
Cc: freebsd-stable@FreeBSD.ORG
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

>  > In 2000 it's getting worse, for me FreeBSD is not stable at all
>  > the future of FreeBSD is not so clear, version follow after version but
>  > I still have no support for my sound board, realplayer, oracle...
>  > The clients are telling me to install Linux instead of FreeBSD (for
>  > oracle)...

Whoa, this is an astonishing claim. We've been running all versions 
of FreeBSD since 2.1.0 on heavily laden garage-sale departmental 
servers. I've never come across such a reliable and cost-effective 
(in hardware and administration cost terms) OS in 23 years of IT 
management. Even 4.0 has turned out to be solid for the services we 
offer despite the anxieties expressed here and elsewhere.

If you analyse the welter of traffic on this list (particularly after 
a new *.0 release) 90% or more is people who didn't follow the 
instructions, haven't found the handbook yet, have faulty hardware or 
wish to debate endlessly the version numbering/obsolescence 
strategies of the FreeBSD team.

The vast majority of users silently continue to use this excellent 
system and offer prayers of thanks to the people who make it possible 
to continue to run reliable and exceptionally efficient services for 
our users in a world dominated by bloated and mediocre software.

My 2 British pence.

Best wishes

Robin.

----------------------------------------------------------------------
Robin Melville, Addiction Information Services 
Nottingham Alcohol & Drug Team
Tel:  +44 (0)115 952 9478       Fax:  +44 (0)115 952 9421
work: robmel@nadt.org.uk        home: robmel@innotts.co.uk
Pages: http://www.nadt.org.uk/
----------------------------------------------------------------------


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


From owner-freebsd-stable  Thu Mar 30  1:56: 6 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from ns2.x-link.za.net (ns2.x-link.za.net [163.195.1.237])
	by hub.freebsd.org (Postfix) with ESMTP id 71F1437BB8D
	for <stable@freebsd.org>; Thu, 30 Mar 2000 01:55:49 -0800 (PST)
	(envelope-from swhite@gov.za)
Received: from localhost (swhite@localhost)
	by ns2.x-link.za.net (8.8.8/8.8.7) with SMTP id LAA14310
	for <stable@freebsd.org>; Thu, 30 Mar 2000 11:55:50 +0200 (SAST)
	(envelope-from swhite@gov.za)
Date: Thu, 30 Mar 2000 11:55:50 +0200 (SAST)
From: <swhite@gov.za>
X-Sender: swhite@ns2.x-link.za.net
To: stable@freebsd.org
Subject: Custom boot disks
Message-ID: <Pine.BSF.3.96.1000330114803.14243B-100000@ns2.x-link.za.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


Hi!

Forgive me if this is the wrong place to ask this but I need help with a
sticky problem.

I have several systems with broken PCI chipsets that I need to upgrade to
3.4-R from 2.2.7-R. I've patched 'pcibus.c' to fix the problem on these
systems (reversed the config mode probe order) but now I need to build
boot/install stiffies to get these machines up and running. Is there any
quick/simple way to do this without going through a 'make release'
process?

As a side issue, any chance of this patch making it into the standard
distribution? I've tested it on as many different systems as I can,
ranging from 486 to P-II and it's not broken on any of them.

Regards,
- Sean.




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


From owner-freebsd-stable  Thu Mar 30  2: 7: 5 2000
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 E6ED437BCF5
	for <stable@FreeBSD.ORG>; Thu, 30 Mar 2000 02:07:03 -0800 (PST)
	(envelope-from jkh@zippy.cdrom.com)
Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1])
	by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id CAA94090;
	Thu, 30 Mar 2000 02:08:07 -0800 (PST)
	(envelope-from jkh@zippy.cdrom.com)
To: swhite@gov.za
Cc: stable@FreeBSD.ORG
Subject: Re: Custom boot disks 
In-reply-to: Your message of "Thu, 30 Mar 2000 11:55:50 +0200."
             <Pine.BSF.3.96.1000330114803.14243B-100000@ns2.x-link.za.net> 
Date: Thu, 30 Mar 2000 02:08:06 -0800
Message-ID: <94087.954410886@zippy.cdrom.com>
From: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> I have several systems with broken PCI chipsets that I need to upgrade to
> 3.4-R from 2.2.7-R. I've patched 'pcibus.c' to fix the problem on these
> systems (reversed the config mode probe order) but now I need to build
> boot/install stiffies to get these machines up and running. Is there any
> quick/simple way to do this without going through a 'make release'
> process?

Just make a kernel and make sure you keep "options MFS" and "options
MFS_ROOT" in there.  Then whap it over the kernel on kern.flp, which
you can mount as a normal floppy.

- Jordan


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


From owner-freebsd-stable  Thu Mar 30  2:17:11 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from ns2.x-link.za.net (ns2.x-link.za.net [163.195.1.237])
	by hub.freebsd.org (Postfix) with ESMTP id B068B37BCE7
	for <stable@FreeBSD.ORG>; Thu, 30 Mar 2000 02:17:06 -0800 (PST)
	(envelope-from swhite@gov.za)
Received: from localhost (swhite@localhost)
	by ns2.x-link.za.net (8.8.8/8.8.7) with SMTP id MAA14347;
	Thu, 30 Mar 2000 12:16:56 +0200 (SAST)
	(envelope-from swhite@gov.za)
Date: Thu, 30 Mar 2000 12:16:56 +0200 (SAST)
From: <swhite@gov.za>
X-Sender: swhite@ns2.x-link.za.net
To: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Cc: stable@FreeBSD.ORG
Subject: Re: Custom boot disks 
In-Reply-To: <94087.954410886@zippy.cdrom.com>
Message-ID: <Pine.BSF.3.96.1000330121619.14243C-100000@ns2.x-link.za.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


On Thu, 30 Mar 2000, Jordan K. Hubbard wrote:

> Just make a kernel and make sure you keep "options MFS" and "options
> MFS_ROOT" in there.  Then whap it over the kernel on kern.flp, which
> you can mount as a normal floppy.

Wow! Super-speedy response... thanks! :)

Regards,
- Sean.




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


From owner-freebsd-stable  Thu Mar 30  2:20:36 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from cache1.telkomsel.co.id (cache1.telkomsel.co.id [202.155.14.251])
	by hub.freebsd.org (Postfix) with ESMTP id 7F33537BCBC
	for <freebsd-stable@freebsd.org>; Thu, 30 Mar 2000 02:20:11 -0800 (PST)
	(envelope-from denisz@iName.com)
Received: from dumb.hq.telkomsel.co.id (dumb.HQ.Telkomsel.co.id [10.1.80.217])
	by cache1.telkomsel.co.id (8.9.3/8.9.3) with SMTP id RAA83423
	for <freebsd-stable@freebsd.org>; Thu, 30 Mar 2000 17:19:18 +0700 (JAVT)
	(envelope-from denisz@iName.com)
Received: (qmail 24715 invoked from network); 30 Mar 2000 10:19:17 -0000
Received: from localhost.telkomsel.co.id (HELO iName.com) (127.0.0.1)
  by localhost.telkomsel.co.id with SMTP; 30 Mar 2000 10:19:17 -0000
Message-ID: <38E32A25.40C9C244@iName.com>
Date: Thu, 30 Mar 2000 17:19:17 +0700
From: denisz <denisz@iName.com>
X-Mailer: Mozilla 4.72 [en] (X11; U; SunOS 5.6 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: freebsd-stable@freebsd.org
Subject: 4.0-install.iso with rsync dist site
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hi,

Is there any rsync site which provides 4.0-install.iso (image of 4.0-REL
CD)?
Did freeBSD has any plan in the future to add rsync besides ftp service
?

-denisz-



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


From owner-freebsd-stable  Thu Mar 30  5:40:54 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from cutter.wantabe.com (cutter.wantabe.com [209.16.8.8])
	by hub.freebsd.org (Postfix) with ESMTP id EE20937BB5F
	for <freebsd-stable@FreeBSD.ORG>; Thu, 30 Mar 2000 05:40:49 -0800 (PST)
	(envelope-from jeffrl@wantabe.com)
Received: from cutter.wantabe.com (cutter.wantabe.com [209.16.8.8])
	by cutter.wantabe.com (8.9.3/8.9.3) with ESMTP id HAA05839
	for <freebsd-stable@FreeBSD.ORG>; Thu, 30 Mar 2000 07:40:45 -0600 (CST)
Date: Thu, 30 Mar 2000 07:40:45 -0600 (CST)
From: "Jeffrey J. Libman" <jeffrl@wantabe.com>
To: freebsd-stable@FreeBSD.ORG
Subject: re: my 3.4 stable system crashed and i have no clue
Message-ID: <Pine.BSF.4.21.0003300738020.5461-100000@cutter.wantabe.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

running freeBSD 3.4-stable:

FreeBSD cutter.wantabe.com 3.4-STABLE FreeBSD 3.4-STABLE #8: Wed Feb 23
08:13:03 CST 2000     jeffrl@cutter.wantabe.com:/usr/src/sys/compile/CUTTER  i386

it panic'd yesterday with:

	panic: double fault

gdb -k session output:

Script started on Thu Mar 30 07:28:24 2000
Thu Mar 30 07:28:24
/var/crash# gdb -k
GNU gdb 4.18
Copyright 1998 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you
are
welcome to change it and/or distribute copies of it under certain
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for
details.
This GDB was configured as "i386-unknown-freebsd".
(kgdb) symbol-file /sys/compile/CUTTER/kernel.debug
Reading symbols from /sys/compile/CUTTER/kernel.debug...done.
(kgdb) exec-file /var/crash/kernel.0
(kgdb) core-file /var/crash/vmcore.0
IdlePTD 2928640
initial pcb at 25da10
panicstr: double fault
panic messages:
---
panic: double fault

syncing disks... 19 19 19 19 19 19 19 19 19 19 19 19 19 19 19 19 19 19 19
19 giving up

dumping to dev 20001, offset 262144
dump 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 8
5 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=256) at ../../kern/kern_shutdown.c:285
285                     dumppcb.pcb_cr3 = rcr3();
(kgdb) where
#0  boot (howto=256) at ../../kern/kern_shutdown.c:285
#1  0xc014b45c in at_shutdown (
    function=0xc023e08e <__set_sysinit_set_sym_memdev_sys_init+910>,
    arg=0xc023e497, queue=-921403224) at ../../kern/kern_shutdown.c:446
#2  0xc020e2ef in dblfault_handler () at ../../i386/i386/trap.c:972
(kgdb) quit
Thu Mar 30 07:37:12
/var/crash# exit

Script done on Thu Mar 30 07:37:13 2000

can anyone help me with this? 

thanks in advance.

cheers,
jeff
--
                                |
                                |\            +------------------------------+
Jeffrey J. Libman, ops. mgr.    | \           |  Wantabe Internet Services   |
Wantabe, Inc.                   |__\          +------------------------------+
jeffrl@wantabe.com        <-----|------>      | access web cgi ftp news mail |
(281) 493-0718       __,.-=\'`^`'~=-../__,.-= +------------------------------+



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


From owner-freebsd-stable  Thu Mar 30  5:47: 6 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from hecky.it.northwestern.edu (hecky.acns.nwu.edu [129.105.16.51])
	by hub.freebsd.org (Postfix) with ESMTP id 3436D37BBDA
	for <freebsd-stable@freebsd.org>; Thu, 30 Mar 2000 05:47:03 -0800 (PST)
	(envelope-from djkanter@nwu.edu)
Received: (from mailnull@localhost)
	by hecky.it.northwestern.edu (8.8.7/8.8.7) id HAA00544
	for <freebsd-stable@freebsd.org>; Thu, 30 Mar 2000 07:47:01 -0600 (CST)
Received: from localhost.localdomain (areca-6-028074.nuts.nwu.edu [165.124.28.74]) by hecky.acns.nwu.edu via smap (V2.0)
	id xmaa00488; Thu, 30 Mar 00 07:46:47 -0600
Received: (from david@localhost)
	by localhost.localdomain (8.9.3/8.9.3) id FAA09904
	for freebsd-stable@freebsd.org; Thu, 30 Mar 2000 05:06:34 -0600 (CST)
	(envelope-from david)
Date: Thu, 30 Mar 2000 05:06:34 -0600
From: "David J. Kanter" <djkanter@nwu.edu>
To: FreeBSD stable <freebsd-stable@freebsd.org>
Subject: Is 3.4-release to 3.4-stable recommended?
Message-ID: <20000330050634.A9886@localhost.localdomain>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0i
X-Organization: Northwestern University
X-Operating-System: FreeBSD localhost.localdomain 3.4-RELEASE FreeBSD 3.4-RELEASE
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

I already asked this question in the -questions list, but figured I should
get a second opinion...

I recently bought the 4-CD set of 3.4-release and wonder if it's recommended
to cvsup the source tree to 3.4-stable and the ports tree to current. I'm
hesitant because, once stable, don't the packages and ports on the 4-CD set
become null? It's a lot easier to install off CDs than rely on downloads
over a modem.

But, if my home PC will be that much better being stable, then perhaps I
should make the plunge.

Thanks for any suggestions.
-- 
David Kanter
djkanter@nwu.edu


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


From owner-freebsd-stable  Thu Mar 30  6:17:54 2000
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 3C70437BC46
	for <freebsd-stable@freebsd.org>; Thu, 30 Mar 2000 06:17:49 -0800 (PST)
	(envelope-from Cy.Schubert@uumail.gov.bc.ca)
Received: (from daemon@localhost)
	by point.osg.gov.bc.ca (8.8.7/8.8.8) id GAA27201
	for <freebsd-stable@freebsd.org>; Thu, 30 Mar 2000 06:17:48 -0800
Received: from passer.osg.gov.bc.ca(142.32.110.29)
 via SMTP by point.osg.gov.bc.ca, id smtpda27199; Thu Mar 30 06:17:46 2000
Received: (from uucp@localhost)
	by passer.osg.gov.bc.ca (8.9.3/8.9.1) id GAA27003
	for <freebsd-stable@freebsd.org>; Thu, 30 Mar 2000 06:17:46 -0800 (PST)
Received: from cwsys9.cwsent.com(10.2.2.1), claiming to be "cwsys.cwsent.com"
 via SMTP by passer9.cwsent.com, id smtpdn27001; Thu Mar 30 06:17:07 2000
Received: (from uucp@localhost)
	by cwsys.cwsent.com (8.9.3/8.9.1) id GAA22155
	for <freebsd-stable@freebsd.org>; Thu, 30 Mar 2000 06:17:07 -0800 (PST)
Message-Id: <200003301417.GAA22155@cwsys.cwsent.com>
Received: from localhost.cwsent.com(127.0.0.1), claiming to be "cwsys"
 via SMTP by localhost.cwsent.com, id smtpdi22151; Thu Mar 30 06:16:58 2000
X-Mailer: exmh version 2.1.1 10/15/1999
Reply-To: Cy Schubert - ITSD Open Systems Group <Cy.Schubert@uumail.gov.bc.ca>
From: Cy Schubert - ITSD Open Systems Group <Cy.Schubert@uumail.gov.bc.ca>
X-OS: FreeBSD 3.4-RELEASE
X-Sender: cy
To: freebsd-stable@freebsd.org
Subject: Re: Let 3.x die ASAP? 
In-reply-to: Your message of "Wed, 29 Mar 2000 20:54:34 EST."
             <NDBBILKDCLLECBCLPMBICEBJCAAA.cjm2@earthling.net> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 30 Mar 2000 06:16:58 -0800
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

If I may add my 1.36 cents (2 cents Canadian) worth here, my general 
impression has been that FreeBSD has become more stable over the years. 
 I've been using FreeBSD since 2.0.5 and have experienced fewer 
problems and have had better stability with 3.4 than with any other 
release.  Generally FreeBSD has become more stable over time, though 
there have been some times where stability did suffer, e.g. 2.0.5, 
which was more stable than Linux at the time, and early releases of 2.2 
and 3.1.  There have also been times when stability really shone, e.g. 
2.1.6 (sorry, 2.1.7 was less stable in my opinion), 2.2.8, and 3.4.

It is unfortunate that some have had less than stellar stability.  
Could it be hardware as some say?  Could it be software?  In some cases 
we'll never know -- too bad most PC's don't have ECC memory or even 
parity memory.  Not all PC's are made to the same standard.

I think that a poll should be taken, and PLEASE not on this list or in 
direct response to my ramblings here, to inventory the hardware that is 
running FreeBSD, what it's being used for, and the level of 
satisfaction or the types of problems experienced.  We might be 
surprised to find some correlation between certain configurations of 
hardware and types of problems experienced.  This information could be 
used to:

1.  Prepare a list of recommended configurations, or

2.  Prepare a list of what works and what doesn't, or

3.  Help us focus in on where most of the problems are where to put 
most of
    our effort.

How can we collect this information?  The Web and postcards shipped 
with each CDROM set might be a start.  Maybe we should collect the 
statistics from the PR database and if the problem is not in the PR 
database it doesn't exist.  (That's what I tell my customers:  If they 
haven't called the Customer Service Centre to open an Alert, I don't 
know that the problem exists and as far as I'm concerned it doesn't 
exist).  People should then be encouraged to submit PR's for problems 
that have already been documented (duplicates) in the PR database to 
add weight to the selection of which problem is solved next.  Three 
workable ideas.  We just have to choose one.

Occasionally on this list we get into discussions like this where one 
or a few say "I have a problem here and it sucks badly" which starts 
yet another huge argument.  On the other hand the developers are doing 
a terrific job with the variety of hardware that they have, not to 
mention the fact that we have a limited pool of developers.  Having the 
commercial backing of BSDI will IMO help in this area of concern, 
however a few statistics might go a long way in telling us which might 
be the high impact (HIPER) problems to work on.

That's my 1.36 cents worth.


Regards,                       Phone:  (250)387-8437
Cy Schubert                      Fax:  (250)387-5766
Team Leader, Sun/DEC Team   Internet:  Cy.Schubert@osg.gov.bc.ca
Open Systems Group, ITSD, ISTA
Province of BC




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


From owner-freebsd-stable  Thu Mar 30  6:29: 3 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from sr14.nsw-remote.bigpond.net.au (sr14.nsw-remote.bigpond.net.au [24.192.3.29])
	by hub.freebsd.org (Postfix) with ESMTP id 39A5E37B91E
	for <freebsd-stable@FreeBSD.ORG>; Thu, 30 Mar 2000 06:28:58 -0800 (PST)
	(envelope-from areilly@nsw.bigpond.net.au)
Received: from areilly.bpc-users.org (CPE-144-132-171-71.nsw.bigpond.net.au [144.132.171.71])
	by sr14.nsw-remote.bigpond.net.au (Pro-8.9.3/8.9.3) with SMTP id RAA01081
	for <freebsd-stable@FreeBSD.ORG>; Thu, 30 Mar 2000 17:09:17 +1000 (EST)
Received: (qmail 7772 invoked by uid 1000); 30 Mar 2000 07:09:16 -0000
From: "Andrew Reilly" <areilly@nsw.bigpond.net.au>
Date: Thu, 30 Mar 2000 17:09:16 +1000
To: "Igor B. Bykhalo" <goshik@binep.ac.ru>
Cc: "-questions@FreeBSD" <freebsd-questions@FreeBSD.ORG>,
	"-stable@FreeBSD" <freebsd-stable@FreeBSD.ORG>
Subject: Re: Doing math - need advice
Message-ID: <20000330170916.A5632@gurney.reilly.home>
References: <01bf9a0e$ffb5fe00$0000e9c1@serv2.binep.ac.ru>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0pre2i
In-Reply-To: <01bf9a0e$ffb5fe00$0000e9c1@serv2.binep.ac.ru>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Thu, Mar 30, 2000 at 09:12:59AM +0300, Igor B. Bykhalo wrote:
> We are going to use mathematical package
> (EPR spectra simulation). Program relies
> on BLAS, LAPACK and ARPACK libraries - all
> in Fortran 77. Program itself can be built
> using gcc, egcs or pgcc.
> 
> Questions:
> 
> 1. What is the recommended way to build
>    f77 libraries to get maximum performance?
>    Should we use g77 from 4.0-Release, or
>    we can stay on 3-Stable and use f2c + pgcc
>    (from ports)?

cd /usr/ports/math/blas; make install
cd /usr/ports/math/lapack....

> 2. Does anyone know incarnations of the mentioned
>    libraries in C language?

There's a clapack on netlib.org, so there's probably a c blas
behind that somewhere.  Dunno about ARPACK.

> 3. Where to read some general advices on the optimization
>    of math perfomance (under FreeBSD)? :)

There are a few generic pentium optimisation pages on the
network.  These may or may not be relevant to P6 based machines.

Up to a certain level of performance, and for many code
structures, memory system behaviour, and therefore data layout
and access will dominate the application performance.  You're
therefore best served by getting things right, and studying
locality of reference, rather than compiler optimisations.

Compiler optimisations (and even assembly language tweaking) can
come last, after some thorough profiling.  (Yes, FreeBSD supports
profiling.)

-- 
Andrew


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


From owner-freebsd-stable  Thu Mar 30  7:36:56 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from kci.kciLink.com (kci.kciLink.com [204.117.82.1])
	by hub.freebsd.org (Postfix) with ESMTP id 6921937BCE0
	for <freebsd-stable@freebsd.org>; Thu, 30 Mar 2000 07:36:52 -0800 (PST)
	(envelope-from khera@kciLink.com)
Received: from onceler.kcilink.com (onceler.kciLink.com [204.117.82.2])
	by kci.kciLink.com (Postfix) with ESMTP
	id 2C7F8E897; Thu, 30 Mar 2000 10:36:50 -0500 (EST)
Received: (from khera@localhost)
	by onceler.kcilink.com (8.9.3/8.9.3) id KAA01715;
	Thu, 30 Mar 2000 10:36:50 -0500 (EST)
	(envelope-from khera@kci.kcilink.com)
From: Vivek Khera <khera@kciLink.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <14563.29842.27770.463734@onceler.kcilink.com>
Date: Thu, 30 Mar 2000 10:36:50 -0500 (EST)
To: Gregory Edigaroff <greg@Thing-Fish.Kharkov.NET>
Cc: freebsd-stable@freebsd.org
Subject: Re: gcc problems
In-Reply-To: <200003281737.UAA01260@Thing-Fish.Kharkov.NET>
References: <200003281737.UAA01260@Thing-Fish.Kharkov.NET>
X-Mailer: VM 6.72 under 21.1 (patch 8) "Bryce Canyon" XEmacs Lucid
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

>>>>> "GE" == Gregory Edigaroff <greg@Thing-Fish.Kharkov.NET> writes:

GE> It seems like gcc-2.95.2 has a leak, which could freeze the compilation.
GE> I experienced this while compile MySQL-3.22.32.
GE> It hangs up on:
 [ ... ]
GE> What can I do?

You can do the same thing every one does when compiling that file in
mysql: increase your resource limits (per-process, per-user,
and/or system-wide), or turn off the optimizations when compiling that
file.  This is documented in the MySQL manual, even.

-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Vivek Khera, Ph.D.                Khera Communications, Inc.
Internet: khera@kciLink.com       Rockville, MD       +1-301-545-6996
PGP & MIME spoken here            http://www.kciLink.com/home/khera/


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


From owner-freebsd-stable  Thu Mar 30  7:39:11 2000
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 AB59937BCB2
	for <stable@freebsd.org>; Thu, 30 Mar 2000 07:39:06 -0800 (PST)
	(envelope-from jdp@polstra.com)
Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13])
	by wall.polstra.com (8.9.3/8.9.3) with ESMTP id HAA21606;
	Thu, 30 Mar 2000 07:39:03 -0800 (PST)
	(envelope-from jdp@polstra.com)
From: John Polstra <jdp@polstra.com>
Received: (from jdp@localhost)
	by vashon.polstra.com (8.9.3/8.9.1) id HAA07006;
	Thu, 30 Mar 2000 07:39:03 -0800 (PST)
	(envelope-from jdp@polstra.com)
Date: Thu, 30 Mar 2000 07:39:03 -0800 (PST)
Message-Id: <200003301539.HAA07006@vashon.polstra.com>
To: ben@scientia.demon.co.uk
Subject: Re: Random signal 9 (SIGKILL), please help!
In-Reply-To: <20000329133710.E96553@strontium.scientia.demon.co.uk>
References: <20000329041104.3028.qmail@camelot.bitart.com> <20000328213754.L21029@fw.wintelcom.net> <20000329102024.3950.qmail@camelot.bitart.com> <20000329133710.E96553@strontium.scientia.demon.co.uk>
Organization: Polstra & Co., Seattle, WA
Cc: stable@freebsd.org, gerti-freebsds@bitart.com
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

In article <20000329133710.E96553@strontium.scientia.demon.co.uk>,
Ben Smithurst  <ben@scientia.demon.co.uk> wrote:
> Gerd Knops wrote:
> 
> > I think I found a correlation between pid roll over (from 99999
> > to 0) and the spurious signals. Some program seems to keep
> > taps on pids that already went away, and when they 'come back' they
> > are killed again. I am suspicious of syslogd at the moment (I pipe
> > syslog output through a filter), one of the very few programs in the
> > base system that are running on those systems and that uses SIGKILL.
> > 
> > However it will probably take some time before I can wrap my head
> > around that code, it's not exactly heavily commented... If anyone
> > with more intimate knowledge could have a look I'd appreciate that.
> 
> Apparently syslogd could do this, I think a fix was commited recently,
> before RELENG_4 was branched, and it was fixed in RELENG_3 as well
> (possibly RELENG_2_2 even).

Yes, I bet Ben is right.  Here's part of the log message for the
fix ("src/usr.sbin/syslogd/syslogd.c"):

  revision 1.58
  date: 2000/02/28 17:49:43;  author: joerg;  state: Exp;  lines: +97 -36
  Fix a serious bug in syslogd regarding the handling of pipes.  The bug
  would cause syslogd to eventually kill innocent processes in the
  system over time (note: not `could' but `would').  Many thanks to my
  colleague Mirko for digging into the kernel structures and providing
  me with the debugging framework to find out about the nature of this
  bug (and to isolate that syslogd was the culprit) in a rather large
  set of distributed machines at client sites where this happened
  occasionally.

  Whenever a child process was no longer responsive, or when syslogd
  receives a SIGHUP so it closes all its logging file descriptors, for
  any descriptor that refers to a pipe syslogd enters the data about the
  old logging child process into a `dead queue', where it is being
  removed from (and the status of the dead kitten being fetched) upon
  receipt of a SIGCHLD.  However, there's a high probability that the
  SIGCHLD already arrives before the child's data are actually entered
  into the dead queue inside the SIGHUP handler, so the SIGCHLD handler
  has nothing to fetch and remove and simply continues.  Whenever this
  happens, the process'es data remain on the dead queue forever, and
  since domark() tried to get rid of totally unresponsive children by
  first sending a SIGTERM and later a SIGKILL, it was only a matter of
  time until the system had recycled enough PIDs so an innocent process
  got shot to death.

  Fix the race by masking SIGHUP and SIGCHLD from both handlers mutually.

  Add additional bandaids ``just in case'', i. e. don't enter a process
  into the dead queue if we can't signal it (this should only happen in
  case it is already dead by that time so we can fetch the status
  immediately instead of deferring this to the SIGCHLD handler); for the
  kill(2) inside domark(), check for an error status (/* Can't happen */
  :) and remove it from the dead queue in this case (which if it would
  have been there in the first place would have reduced the problem to a
  statistically minimal likelihood so i certainly would never have
  noticed the bug at all :).

John
-- 
  John Polstra                                               jdp@polstra.com
  John D. Polstra & Co., Inc.                        Seattle, Washington USA
  "Disappointment is a good sign of basic intelligence."  -- Chögyam Trungpa



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


From owner-freebsd-stable  Thu Mar 30  8:20:17 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from loki.ideaglobal.com (loki.ideaglobal.com [194.36.20.54])
	by hub.freebsd.org (Postfix) with ESMTP id 5EAD637B5E7
	for <freebsd-stable@FreeBSD.ORG>; Thu, 30 Mar 2000 08:20:12 -0800 (PST)
	(envelope-from kiril@loki.ideaglobal.com)
Received: (from kiril@localhost)
	by loki.ideaglobal.com (8.9.3/8.9.3) id QAA76045;
	Thu, 30 Mar 2000 16:25:18 GMT
	(envelope-from kiril)
From: Kiril Mitev <kiril@ideaglobal.com>
Message-Id: <200003301625.QAA76045@loki.ideaglobal.com>
Subject: Re: Let 3.x die ASAP?
In-Reply-To: <200003291821.LAA16584@freeway.dcfinc.com> from "Chad R. Larson" at "Mar 29, 2000 11:21: 4 am"
To: chad@DCFinc.com
Date: Thu, 30 Mar 2000 16:25:18 +0000 (GMT)
Cc: didier@omnix.net, jkh@zippy.cdrom.com, cracauer@cons.org,
	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

> As I recall, Didier Derny wrote:
> > I can't an many people can't upgrade the system on their machine
> > at the actual rythm of FreeBSD version (each one supposed to be the best
> > one and solve most of the problems :-))) )
> > without a real stability (like the one with 2.x) this product
> > has no more value than linux or solaris, sco...
> 
> So, is there some feature in the 3.x line that isn't in 2.2.x that
> you can't live without?  If not, your course is clear.  Put up a
> 2.2-STABLE system and quit worrying about stability.

*ahem*

In other words "do not use anything newer than 2.2 if you 
worry about stability"...

In other words "nothing in FreeBSD has improved stability
since 2.2"

In other words "2.2 is our most stable version"

(ever?)

In other words ..... you get the drift .......

OUCH

*off to downgrade all those servers ASAP*

*oh, and replace them with 486's, after all 486's with
2.2 on them have years of uptime*

> 	-crl
> --
> Chad R. Larson (CRL15)   602-953-1392   Brother, can you paradigm?
> chad@dcfinc.com         chad@larsons.org          larson1@home.net   
> DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207

ok, I _might_ be exaggerating a bit .... but this reply *DOES*
come as a bit of a shock ..... <insert grinning noises here>


-- 
Kiril Mitev, IT Operations Mgr, London
IDEAglobal.com
Standard Corporate Disclaimer applies, see
http://www.ideaglobal.com/email-disclaimer.html
for details.


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


From owner-freebsd-stable  Thu Mar 30  8:35:50 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from shell.tsoft.com (shell.tsoft.com [198.144.192.5])
	by hub.freebsd.org (Postfix) with ESMTP id 5825737BCAC
	for <freebsd-stable@FreeBSD.ORG>; Thu, 30 Mar 2000 08:35:47 -0800 (PST)
	(envelope-from siewsim@prismedia.com)
Received: from prismedia.com (m205-186.dsl.tsoft.com [198.144.205.186])
	by shell.tsoft.com (8.8.7/8.8.7) with ESMTP id IAA14113
	for <freebsd-stable@FreeBSD.ORG>; Thu, 30 Mar 2000 08:35:46 -0800 (PST)
Message-ID: <38E3833D.A57695F0@prismedia.com>
Date: Thu, 30 Mar 2000 08:39:26 -0800
From: Siew Sim <siewsim@prismedia.com>
Reply-To: siewsim@prismedia.com
Organization: PRISMedia
X-Mailer: Mozilla 4.6 [en] (X11; I; FreeBSD 3.2-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: freebsd-stable@FreeBSD.ORG
Subject: please help - thread-safe mysql client link problem
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hi,

    I'm using FreeBSD 3.2, and mysql 3.22.30.  I'm trying to build a
thread-safe mysql client with pthread.

    Following the mysql spec,  I defined THREAD_SAFE_CLIENT before
running configure, and still get these warnings while building mysql:

g++ -pthread -DUNDEF_THREADS_HACK -I./../include -I../include     -I./..
-I.. -I..  -DTHREAD_SAFE_CLIENT  -D_LARGEFILE_SOURCE
-D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -O3 -DDBUG_OFF
-fno-implicit-templates -DMYSQLD_NET_RETRY_COUNT=1000000 -c
completion_hash.cc
/bin/sh ../libtool --mode=link g++ -pthread  -D_LARGEFILE_SOURCE
-D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -O3 -DDBUG_OFF
-fno-implicit-templates -DMYSQLD_NET_RETRY_COUNT=1000000  -o mysql
mysql.o readline.o sql_string.o completion_hash.o
../readline/libreadline.a -lncurses libmysqlclient.la -lm   -lz -lcrypt
g++ -pthread -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE
-D_FILE_OFFSET_BITS=64 -O3 -DDBUG_OFF -fno-implicit-templates
-DMYSQLD_NET_RETRY_COUNT=1000000 -o .libs/mysql mysql.o readline.o
sql_string.o completion_hash.o ../readline/libreadline.a -lncurses
.libs/libmysqlclient.so -lm -lz -lcrypt -lm -lz -lcrypt -Wl,--rpath
-Wl,/usr/local/lib/mysql
/usr/lib/libc.so.3: warning: this program uses gets(), which is unsafe.
/usr/lib/libc.so.3: WARNING!  setkey(3) not present in the system!
/usr/lib/libc.so.3: WARNING!  des_setkey(3) not present in the system!
/usr/lib/libc.so.3: WARNING!  encrypt(3) not present in the system!
/usr/lib/libc.so.3: WARNING!  des_cipher(3) not present in the system!
/usr/lib/libc.so.3: warning: this program uses f_prealloc(), which is
stupid.
creating mysql

    According to the gcc man page, gcc uses libc_r instead of libc if
-pthread option is used.  This build seems to use libc, can someone tell
me what I'm missing?

Thanks!

Siew



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


From owner-freebsd-stable  Thu Mar 30  8:36: 9 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from pooh.elsevier.nl (pooh.elsevier.nl [145.36.13.27])
	by hub.freebsd.org (Postfix) with ESMTP id 6605937BD8D
	for <freebsd-stable@FreeBSD.ORG>; Thu, 30 Mar 2000 08:36:06 -0800 (PST)
	(envelope-from steve@pooh.elsevier.nl)
Received: (from steve@localhost)
	by pooh.elsevier.nl (8.9.3/8.9.3) id RAA01426;
	Thu, 30 Mar 2000 17:41:24 +0100 (IST)
	(envelope-from steve)
Message-ID: <XFMail.000330174124.steveo@eircom.net>
X-Mailer: XFMail 1.4.0 on FreeBSD
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <200003301625.QAA76045@loki.ideaglobal.com>
Date: Thu, 30 Mar 2000 17:41:24 +0100 (IST)
From: "Steve O'Hara-Smith" <steveo@eircom.net>
To: Kiril Mitev <kiril@ideaglobal.com>
Subject: Re: Let 3.x die ASAP?
Cc: freebsd-stable@FreeBSD.ORG, cracauer@cons.org,
	jkh@zippy.cdrom.com, didier@omnix.net, chad@DCFinc.com
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


On 30-Mar-00 Kiril Mitev wrote:
> In other words "do not use anything newer than 2.2 if you 
> worry about stability"...
> 
> In other words "nothing in FreeBSD has improved stability
> since 2.2"

        Not quite:

        In other words - 'Didier Derny please continue to use 2.2 if that is
what you like best and please do not bother the rest of us who find 3.x and 4.x
to be at least as good as 2.x'.

        This because Didier Derny is moaning without content.



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


From owner-freebsd-stable  Thu Mar 30  8:47:23 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
	by hub.freebsd.org (Postfix) with ESMTP
	id 02DD737B73E; Thu, 30 Mar 2000 08:47:22 -0800 (PST)
	(envelope-from kris@FreeBSD.org)
Received: from localhost (kris@localhost)
	by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id IAA40390;
	Thu, 30 Mar 2000 08:47:21 -0800 (PST)
	(envelope-from kris@FreeBSD.org)
X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs
Date: Thu, 30 Mar 2000 08:47:21 -0800 (PST)
From: Kris Kennaway <kris@FreeBSD.org>
To: "David J. Kanter" <djkanter@nwu.edu>
Cc: FreeBSD stable <freebsd-stable@freebsd.org>
Subject: Re: Is 3.4-release to 3.4-stable recommended?
In-Reply-To: <20000330050634.A9886@localhost.localdomain>
Message-ID: <Pine.BSF.4.21.0003300842000.34979-100000@freefall.freebsd.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Thu, 30 Mar 2000, David J. Kanter wrote:

> I recently bought the 4-CD set of 3.4-release and wonder if it's recommended
> to cvsup the source tree to 3.4-stable and the ports tree to current. I'm
> hesitant because, once stable, don't the packages and ports on the 4-CD set
> become null? It's a lot easier to install off CDs than rely on downloads
> over a modem.

Ports tend to get upgraded pretty quickly, so chances are there are newer
versions available of a lot of your ports. If you dont mind not having the
absolute latest versions of everything, and only upgrade a port when you
need to or theres a security advisory, etc, it's fine.

> But, if my home PC will be that much better being stable, then perhaps I
> should make the plunge.

Not all that much has changed from 3.4-R to 3.4-S, really. The 3.x branch
is winding down now that 4.0 is out. So basically unless there's something
you cant do with 3.4, by all means stick with it! :-)

Kris

----
In God we Trust -- all others must submit an X.509 certificate.
    -- Charles Forsythe <forsythe@alum.mit.edu>



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


From owner-freebsd-stable  Thu Mar 30  8:54: 9 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from ptavv.es.net (ptavv.es.net [198.128.4.29])
	by hub.freebsd.org (Postfix) with ESMTP id B243D37B820
	for <stable@FreeBSD.ORG>; Thu, 30 Mar 2000 08:54:01 -0800 (PST)
	(envelope-from oberman@ptavv.es.net)
Received: from ptavv.es.net (localhost [127.0.0.1])
	by ptavv.es.net (8.9.3/8.8.8) with ESMTP id IAA25027;
	Thu, 30 Mar 2000 08:53:48 -0800 (PST)
Message-Id: <200003301653.IAA25027@ptavv.es.net>
To: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Cc: swhite@gov.za, stable@FreeBSD.ORG
Subject: Re: Custom boot disks 
In-reply-to: Your message of "Thu, 30 Mar 2000 02:08:06 PST."
             <94087.954410886@zippy.cdrom.com> 
Date: Thu, 30 Mar 2000 08:53:48 -0800
From: "Kevin Oberman" <oberman@es.net>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> Date: Thu, 30 Mar 2000 02:08:06 -0800
> From: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
> Sender: owner-freebsd-stable@FreeBSD.ORG
> 
> > I have several systems with broken PCI chipsets that I need to upgrade to
> > 3.4-R from 2.2.7-R. I've patched 'pcibus.c' to fix the problem on these
> > systems (reversed the config mode probe order) but now I need to build
> > boot/install stiffies to get these machines up and running. Is there any
> > quick/simple way to do this without going through a 'make release'
> > process?
> 
> Just make a kernel and make sure you keep "options MFS" and "options
> MFS_ROOT" in there.  Then whap it over the kernel on kern.flp, which
> you can mount as a normal floppy.

One step Jordan forgot to mention is that you need to gzip the kernel
file before trying to move it to the floppy or it will never fit!

Of course this is pretty obvious from the name of the kernel file on the
floppy...kernel.gz. 

R. Kevin Oberman, Network Engineer
Energy Sciences Network (ESnet)
Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
E-mail: oberman@es.net			Phone: +1 510 486-8634


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


From owner-freebsd-stable  Thu Mar 30  8:57:25 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
	by hub.freebsd.org (Postfix) with ESMTP
	id 28FFF37B78D; Thu, 30 Mar 2000 08:57:22 -0800 (PST)
	(envelope-from kris@FreeBSD.org)
Received: from localhost (kris@localhost)
	by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id IAA42974;
	Thu, 30 Mar 2000 08:57:22 -0800 (PST)
	(envelope-from kris@FreeBSD.org)
X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs
Date: Thu, 30 Mar 2000 08:57:21 -0800 (PST)
From: Kris Kennaway <kris@FreeBSD.org>
To: Kiril Mitev <kiril@ideaglobal.com>
Cc: chad@DCFinc.com, didier@omnix.net, jkh@zippy.cdrom.com,
	cracauer@cons.org, freebsd-stable@FreeBSD.ORG
Subject: Re: Let 3.x die ASAP?
In-Reply-To: <200003301625.QAA76045@loki.ideaglobal.com>
Message-ID: <Pine.BSF.4.21.0003300849270.34979-100000@freefall.freebsd.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Thu, 30 Mar 2000, Kiril Mitev wrote:

> In other words "2.2 is our most stable version"

I hope you realise that no single person speaks for FreeBSD, especially
people who aren't committers. That said, a lot of people found 2.2 to be a
very stable branch. A lot of people found the same thing about 3.4, but
others didn't. Others complained about 2.2 as well - if a version
doesn't work on your machine for whatever reason then of course you're
going to complain about it being 'unstable' (some people take this to
ridiculous extremes). FreeBSD isn't perfect - it is, I claim, very good,
and better than the competition, but their marketing departments do
everything they can to convince you otherwise.

If for some reason they don't want to go to the 3.x branch because of any
percieved or real problems, staying with 2.2 is a perfectly reasonable
option if it works for you.

This isn't Microsoft where we instantly stop supporting our previous
releases the moment we release an 'upgrade' (true, the ports collection no
longer supports 2.x, but thats for sheer manpower reasons that it's
difficult enough to make ports work on 3 branches, let alone 4). Use the
tool that works for you.

Kris

----
In God we Trust -- all others must submit an X.509 certificate.
    -- Charles Forsythe <forsythe@alum.mit.edu>




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


From owner-freebsd-stable  Thu Mar 30  9:29:33 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from loki.ideaglobal.com (loki.ideaglobal.com [194.36.20.54])
	by hub.freebsd.org (Postfix) with ESMTP
	id E608537B56A; Thu, 30 Mar 2000 09:29:26 -0800 (PST)
	(envelope-from kiril@loki.ideaglobal.com)
Received: (from kiril@localhost)
	by loki.ideaglobal.com (8.9.3/8.9.3) id RAA76279;
	Thu, 30 Mar 2000 17:35:00 GMT
	(envelope-from kiril)
From: Kiril Mitev <kiril@ideaglobal.com>
Message-Id: <200003301735.RAA76279@loki.ideaglobal.com>
Subject: Re: Let 3.x die ASAP?
In-Reply-To: <Pine.BSF.4.21.0003300849270.34979-100000@freefall.freebsd.org> from Kris Kennaway at "Mar 30, 2000  8:57:21 am"
To: kris@FreeBSD.org (Kris Kennaway)
Date: Thu, 30 Mar 2000 17:34:59 +0000 (GMT)
Cc: kiril@ideaglobal.com, chad@DCFinc.com, didier@omnix.net,
	jkh@zippy.cdrom.com, cracauer@cons.org, 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

> On Thu, 30 Mar 2000, Kiril Mitev wrote:
> 
> > In other words "2.2 is our most stable version"
> 
> I hope you realise that no single person speaks for FreeBSD, especially
> people who aren't committers. That said, a lot of people found 2.2 to be a

*sigh* 

yes i do, a "newbie" wont

<snip>

> This isn't Microsoft where we instantly stop supporting our previous
> releases the moment we release an 'upgrade' (true, the ports collection no
> longer supports 2.x, but thats for sheer manpower reasons that it's
> difficult enough to make ports work on 3 branches, let alone 4). Use the
> tool that works for you.

next time I shall remember to put SARCASM somewhere in BIG letters ..
(my fault, yes)

easy on the flame-throwers

> Kris
> 
> ----
> In God we Trust -- all others must submit an X.509 certificate.
>     -- Charles Forsythe <forsythe@alum.mit.edu>

-- 
Kiril Mitev, IT Operations Mgr, London
IDEAglobal.com
Standard Corporate Disclaimer applies, see
http://www.ideaglobal.com/email-disclaimer.html
for details.


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


From owner-freebsd-stable  Thu Mar 30 10: 6: 2 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from unicorn.blackhats.org (unicorn.blackhats.org [194.109.83.155])
	by hub.freebsd.org (Postfix) with ESMTP id 4277637BD4C
	for <freebsd-stable@FreeBSD.ORG>; Thu, 30 Mar 2000 10:05:56 -0800 (PST)
	(envelope-from unicorn@blackhats.org)
Received: by unicorn.blackhats.org (Postfix, from userid 1002)
	id 884B312C39; Thu, 30 Mar 2000 19:13:39 +0200 (CEST)
Date: Thu, 30 Mar 2000 19:13:39 +0200
From: The Unicorn <unicorn@blackhats.org>
To: "Forrest W. Christian" <forrestc@iMach.com>
Cc: Didier Derny <didier@omnix.net>,
	Martin Cracauer <cracauer@cons.org>, freebsd-stable@FreeBSD.ORG
Subject: Re: Let 3.x die ASAP?
Message-ID: <20000330191339.K19913@unicorn.blackhats.org>
References: <Pine.BSF.3.96.1000329080220.7123A-100000@omnix.net> <Pine.BSF.4.21.0003290146040.18478-100000@workhorse.iMach.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0pre4i
In-Reply-To: <Pine.BSF.4.21.0003290146040.18478-100000@workhorse.iMach.com>; from forrestc@iMach.com on Wed, Mar 29, 2000 at 02:14:25AM -0700
X-Files: The Truth Is Out There!
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Wed, 29 Mar 2000, Forrest W. Christian wrote:

> On Wed, 29 Mar 2000, Didier Derny wrote:
> 
> > freebsd seems running version after version and not stability...
> 
> > in 1999 (3.x) I was not so sure at all, no stability too many problems.
> 
> hmmm....
> 
> # uptime
>  1:44AM  up 46 days, 22:36, 1 user, load averages: 0.01, 0.02, 0.00

Not to "compare sizes", but:

 7:05PM  up 101 days,  7:17, 5 users, load averages: 1.35, 1.35, 1.24

A heavier  load and a  very stable  3.4-STABLE machine... I  still don't
know what  you (Didier  that is)  are whining  about... Just  follow the
rules:

1/ Buy reliable hardware
2/ Install a stable OS (FreeBSD)
3/ Use  well  tested applications,  either native  coded for  FreeBSD or
   using its GNU/Linux binary compatibility

Oh, and...

9/ Make  regular  backups and  test them  once-in-a-while. Just  because
   hardware tends to break down when you least expect it... :(

> - Forrest W. Christian (forrestc@imach.com) KD7EHZ

--- End of Quoted Text ---

Ciao,
Unicorn.
-- 
======= _ __,;;;/ TimeWaster ================================================
     ,;( )_, )~\| A Truly Wise Man Never Plays   PGP: 64 07 5D 4C 3F 81 22 73
    ;; //  `--;     Leapfrog With A Unicorn...        52 9D 87 08 51 AA 35 F0
==='= ;\ = | ==== Youth is Not a Time in Life, It is a State of Mind! =======
Echelon Teasers: NSA CIA FBI Mossad BVD MI5 Cocaine Cuba Revolution Espionage 



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


From owner-freebsd-stable  Thu Mar 30 10:10:22 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from infos1.casaccia.enea.it (INFOS1.casaccia.enea.it [192.107.71.175])
	by hub.freebsd.org (Postfix) with ESMTP id B190D37B7FA
	for <freebsd-stable@FreeBSD.ORG>; Thu, 30 Mar 2000 10:10:17 -0800 (PST)
	(envelope-from poggif@casaccia.enea.it)
Received: from studi7106 (STUDI7106.casaccia.enea.it [192.107.77.106])
	by infos1.casaccia.enea.it (8.9.1/8.9.1) with SMTP id UAA09938
	for <freebsd-stable@FreeBSD.ORG>; Thu, 30 Mar 2000 20:11:11 +0200 (MET DST)
Message-Id: <3.0.5.32.20000330201023.009066e0@infos1.casaccia.enea.it>
X-Sender: poggif@infos1.casaccia.enea.it
X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32)
Date: Thu, 30 Mar 2000 20:10:23 +0200
To: freebsd-stable@FreeBSD.ORG
From: Fabrizio Poggi <poggif@casaccia.enea.it>
Subject: Re: Let 3.x die ASAP?
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

At 17.34 30/03/00 +0000, you wrote:

>next time I shall remember to put SARCASM somewhere in BIG letters ..
>(my fault, yes)

Yes Kiril, 
Let's do a little joke huh? Stay in tune and prepare your flames:) I tried
2.2.8, maybe was stable but was also the most ignorant system ever seen.
Rude and pure. It can slash your hands if you type something wrong on the
console. Uuunix Monster! We have now GTK: don't like the evolution? The
first fire on Earth was burning with the courious man that use sparks in
the near to inflammable materials. That man seems be content, don't
worrying so much. Burnt his branches in good & stable flames, in silence,
for 3 hours and 4 minutes. The religious, ritual phrase before the flames
it seems was :"CVSup!" 

:))

Regards, Fabrizio

***
(loosing my head about 3.x. & 4.x. - sorry for disturb)


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


From owner-freebsd-stable  Thu Mar 30 10:44:55 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from wat-border.sentex.ca (waterloo-hespler.sentex.ca [199.212.135.66])
	by hub.freebsd.org (Postfix) with ESMTP id B3E5137B5E0
	for <freebsd-stable@FreeBSD.ORG>; Thu, 30 Mar 2000 10:44:38 -0800 (PST)
	(envelope-from mike@sentex.ca)
Received: from vinyl.sentex.ca (vinyl.sentex.ca [209.112.4.14])
	by wat-border.sentex.ca (8.9.3/8.9.3) with ESMTP id NAA59120
	for <freebsd-stable@FreeBSD.ORG>; Thu, 30 Mar 2000 13:44:36 -0500 (EST)
	(envelope-from mike@sentex.ca)
Received: from simoeon (simeon.sentex.ca [209.112.4.47])
	by vinyl.sentex.ca (8.9.3/8.9.3) with SMTP id NAA14301
	for <freebsd-stable@FreeBSD.ORG>; Thu, 30 Mar 2000 13:44:35 -0500 (EST)
	(envelope-from mike@sentex.ca)
Message-Id: <3.0.5.32.20000330134156.01fc5100@marble.sentex.ca>
X-Sender: mdtpop@marble.sentex.ca
X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32)
Date: Thu, 30 Mar 2000 13:41:56 -0500
To: freebsd-stable@FreeBSD.ORG
From: Mike Tancsa <mike@sentex.ca>
Subject: Is 3.x stable with a small s ? ummm yes... (was Re: Let 3.x
  die ASAP?)
In-Reply-To: <20000330191339.K19913@unicorn.blackhats.org>
References: <Pine.BSF.4.21.0003290146040.18478-100000@workhorse.iMach.com>
 <Pine.BSF.3.96.1000329080220.7123A-100000@omnix.net>
 <Pine.BSF.4.21.0003290146040.18478-100000@workhorse.iMach.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:13 PM 3/30/00 +0200, The Unicorn wrote:
>On Wed, 29 Mar 2000, Forrest W. Christian wrote:
>
>> On Wed, 29 Mar 2000, Didier Derny wrote:
>> 
>> > freebsd seems running version after version and not stability...
>> 
>> > in 1999 (3.x) I was not so sure at all, no stability too many problems.
>> 
>> hmmm....
>> 
>> # uptime
>>  1:44AM  up 46 days, 22:36, 1 user, load averages: 0.01, 0.02, 0.00
>
>Not to "compare sizes", but:
>
> 7:05PM  up 101 days,  7:17, 5 users, load averages: 1.35, 1.35, 1.24

This is a fairly busy SMP PII 450 web server, a pair of LVD 10K drives,
512MB RAM... According to a quick glance at webalizer, they average 2
million hits a day on a heavily perl generated web site.

 1:27PM  up 239 days, 23:08, 4 users, load averages: 1.52, 1.46, 1.17

3.1-STABLE FreeBSD 3.1-STABLE #0: Fri Jul 16 10:27:30 EDT 1999

The only thing I have been keeping upto date on it has been the various
applications like bind and apache for security reasons. The customer has
not paid me to cvsup/rebuild/reboot etc.  They are happy and dont want to
change a thing as its been so stable for them. 

So, is 3.x STABLE a stable system ? Yes, it has been for us, as well as
many other people... I have a few dozen or so other 3.x boxes deployed in
various production sites.  They have done very well for us.  I have also
started deploying 4.x machines slowly into production... Same positive
results.

So how about we let this thread die ASAP ? Or move it to -chat.

	---Mike
------------------------------------------------------------------------
Mike Tancsa,                          	          tel +1 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  Thu Mar 30 10:54: 1 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from TK147108.tuwien.teleweb.at (TK147108.tuwien.teleweb.at [195.34.147.108])
	by hub.freebsd.org (Postfix) with ESMTP id 50EBA37BAA9
	for <freebsd-stable@freebsd.org>; Thu, 30 Mar 2000 10:53:35 -0800 (PST)
	(envelope-from satyr@TK147108.tuwien.teleweb.at)
Received: from satyr by TK147108.tuwien.teleweb.at with local (Exim 2.12 #1)
	id 12ak6w-0007zJ-00
	for freebsd-stable@FreeBSD.ORG; Thu, 30 Mar 2000 20:56:06 +0200
Date: Thu, 30 Mar 2000 20:56:06 +0200
From: "Marinos J . Yannikos" <mjy@pobox.com>
To: freebsd-stable@FreeBSD.ORG
Subject: Re: 3.4-RELEASE; panic while paging
Message-ID: <20000330205606.B15889@TK147108.telekabel.at>
Reply-To: nino@inode.at
References: <20000329175018.V15889@TK147108.telekabel.at> <20000329195354.A40356@walton.maths.tcd.ie>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.5i
In-Reply-To: <20000329195354.A40356@walton.maths.tcd.ie>; from David Malone on Wed, Mar 29, 2000 at 07:53:54PM +0100
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Thanks for all the useful suggestions! I exchanged the board for a Gigabyte
GA-7IXE and the DIMMs for 2 x 256MB PC100 6ns with 5 year warranty, i.e.
supposedly quality parts and I also got a (newer) 650 MHz Athlon. So far
this combination seems to be absolutely stable, not a single process has
died despite very high loads.

What seemed odd with the previous configuration was that with the 128MB
DIMMs in use, the kernel would panic immediately as soon as any swap space 
was touched. This was so predictable that I became worried about the
possibility of there being a problem with 512MB RAM and swapping (and
Athlons). I wonder what caused this...

Regards,
 Marinos

PS. I'd be very interested in helping to build a database of working
    configurations (this has been discussed recently in the mailing lists)
-- 
***==> Marinos J. Yannikos <mjy@pobox.com>
***==> http://pobox.com/~mjy


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


From owner-freebsd-stable  Thu Mar 30 11: 4:34 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from serenity.mcc.ac.uk (serenity.mcc.ac.uk [130.88.200.93])
	by hub.freebsd.org (Postfix) with ESMTP id C885037B8D6
	for <freebsd-stable@freebsd.org>; Thu, 30 Mar 2000 11:04:28 -0800 (PST)
	(envelope-from jcm@dogma.freebsd-uk.eu.org)
Received: from dogma.freebsd-uk.eu.org ([130.88.200.97])
	by serenity.mcc.ac.uk with esmtp (Exim 1.92 #3)
	id 12akEw-0004up-00; Thu, 30 Mar 2000 20:04:22 +0100
Received: (from jcm@localhost)
	by dogma.freebsd-uk.eu.org (8.9.3/8.9.3) id UAA16822;
	Thu, 30 Mar 2000 20:04:22 +0100 (BST)
	(envelope-from jcm)
Date: Thu, 30 Mar 2000 20:04:22 +0100
From: J McKitrick <jcm@freebsd-uk.eu.org>
To: nino@inode.at
Cc: freebsd-stable@freebsd.org
Subject: Re: 3.4-RELEASE; panic while paging
Message-ID: <20000330200422.B16409@dogma.freebsd-uk.eu.org>
References: <20000329175018.V15889@TK147108.telekabel.at> <20000329195354.A40356@walton.maths.tcd.ie> <20000330205606.B15889@TK147108.telekabel.at>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0.1i
In-Reply-To: <20000330205606.B15889@TK147108.telekabel.at>; from mjy@pobox.com on Thu, Mar 30, 2000 at 08:56:06PM +0200
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Just general question about these types of hardware problems.  Do they
occur often under NT or windows as well?  Or does FreeBSD just seem to
push hardware to its limits more?

jm
-- 
--------------------------------------------
Jonathon McKitrick -- jcm@freebsd-uk.eu.org 
The spice must flow....
--------------------------------------------


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


From owner-freebsd-stable  Thu Mar 30 11:12:12 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from cx344940-a.meta1.la.home.com (cx344940-a.meta1.la.home.com [24.6.21.74])
	by hub.freebsd.org (Postfix) with ESMTP id E77E537C067
	for <freebsd-stable@FreeBSD.ORG>; Thu, 30 Mar 2000 11:12:07 -0800 (PST)
	(envelope-from conrads@cx344940-a.meta1.la.home.com)
Received: (from conrads@localhost)
	by cx344940-a.meta1.la.home.com (8.9.3/8.9.3) id NAA39488;
	Thu, 30 Mar 2000 13:12:01 -0600 (CST)
	(envelope-from conrads)
Message-ID: <XFMail.000330131201.conrads@home.com>
X-Mailer: XFMail 1.4.0 on FreeBSD
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <NDBBILKDCLLECBCLPMBICEBJCAAA.cjm2@earthling.net>
Date: Thu, 30 Mar 2000 13:12:01 -0600 (CST)
Organization: @Home Network
From: Conrad Sabatier <conrads@home.com>
To: C J Michaels <cjm2@earthling.net>
Subject: RE: Let 3.x die ASAP?
Cc: freebsd-stable@FreeBSD.ORG, mo@servo.ccr.org,
	Martin Cracauer <cracauer@cons.org>,
	"Jordan K. Hubbard" <jkh@zippy.cdrom.com>,
	Didier Derny <didier@omnix.net>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


On 30-Mar-00 C J Michaels wrote:
> Judging the stability of 3.x by the postings in this list is inaccurate.
> The purpose of this list is to help with problems/questions/etc...  Of
> course people aren't going to post daily "my 3.x system works great,
> thanks!".

My 3.4-STABLE system works great!  Thanks!

>  It's a waste of bandwidth.

Oops. 

-- 
Conrad Sabatier
http://members.home.net/conrads/
ICQ# 1147270



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


From owner-freebsd-stable  Thu Mar 30 11:15:58 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from mass.cdrom.com (mg137-078.ricochet.net [204.179.137.78])
	by hub.freebsd.org (Postfix) with ESMTP id A5DA437BCF9
	for <stable@freebsd.org>; Thu, 30 Mar 2000 11:15:42 -0800 (PST)
	(envelope-from msmith@mass.cdrom.com)
Received: from mass.cdrom.com (localhost [127.0.0.1])
	by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id JAA00391;
	Thu, 30 Mar 2000 09:56:25 -0800 (PST)
	(envelope-from msmith@mass.cdrom.com)
Message-Id: <200003301756.JAA00391@mass.cdrom.com>
X-Mailer: exmh version 2.1.1 10/15/1999
To: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Cc: swhite@gov.za, stable@freebsd.org
Subject: Re: Custom boot disks 
In-reply-to: Your message of "Thu, 30 Mar 2000 02:08:06 PST."
             <94087.954410886@zippy.cdrom.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 30 Mar 2000 09:56:24 -0800
From: Mike Smith <msmith@freebsd.org>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> > I have several systems with broken PCI chipsets that I need to upgrade to
> > 3.4-R from 2.2.7-R. I've patched 'pcibus.c' to fix the problem on these
> > systems (reversed the config mode probe order) but now I need to build
> > boot/install stiffies to get these machines up and running. Is there any
> > quick/simple way to do this without going through a 'make release'
> > process?
> 
> Just make a kernel and make sure you keep "options MFS" and "options
> MFS_ROOT" in there.  Then whap it over the kernel on kern.flp, which
> you can mount as a normal floppy.

Don't forget to gzip it first, as it probably won't fit otherwise.

-- 
\\ Give a man a fish, and you feed him for a day. \\  Mike Smith
\\ Tell him he should learn how to fish himself,  \\  msmith@freebsd.org
\\ and he'll hate you for a lifetime.             \\  msmith@cdrom.com




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


From owner-freebsd-stable  Thu Mar 30 11:19:40 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from mirage.nlink.com.br (mirage.nlink.com.br [200.249.195.3])
	by hub.freebsd.org (Postfix) with SMTP id EE67637BD4C
	for <freebsd-stable@freebsd.org>; Thu, 30 Mar 2000 11:19:12 -0800 (PST)
	(envelope-from paulo@nlink.com.br)
Received: (qmail 18187 invoked by uid 501); 30 Mar 2000 19:18:58 -0000
Received: from localhost (sendmail-bs@127.0.0.1)
  by localhost with SMTP; 30 Mar 2000 19:18:58 -0000
Date: Thu, 30 Mar 2000 16:18:58 -0300 (EST)
From: Paulo Fragoso <paulo@nlink.com.br>
To: freebsd-stable@freebsd.org
Subject: Atapi CDRW
Message-ID: <Pine.BSF.4.10.10003301545290.7756-100000@mirage.nlink.com.br>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hi,

I'm using freebsd 3.4-RELEASE with CREATIVE CD-RW RW4224E:

/kernel: wdc1: unit 0 (atapi): <CREATIVE CD-RW RW4224E/1.36>, removable,
accel, dma, iordis
/kernel: acd0: drive speed 4125KB/sec, 1860KB cache
/kernel: acd0: supported read types: CD-R, CD-RW, CD-DA, packet track
/kernel: acd0: supported write types: CD-R, CD-RW, test write
/kernel: acd0: Audio: play, 255 volume levels
/kernel: acd0: Mechanism: ejectable tray
/kernel: acd0: Medium: no/blank disc inside, unlocked, lock protected

I was burning my cds using wormcontrol, it was working fine. But now I've
changed to 4.0-RELEASE and I'm having some problems. Some times the CDRW
is detected this way:

/kernel: ata1-master: timeout waiting for command=ef s=00 e=00
/kernel: acd0: CD-RW <CREATIVE CD-RW RW4224E> at ata1-master using BIOSPIO

some times this way:

/kernel: acd0: CD-RW <CREATIVE CD-RW RW4224E> at ata1-master using PIO4

And I'm losting several cds using burncd command, my drive freeze and only
work after power cicle. I get this mesage when the CDRW freeze:

/kernel: acd0: READ_TOC - ILLEGAL REQUEST asc=24 ascq=00 error=00
/kernel: acd0: WRITE_BIG - HARDWARE ERROR asc=09 ascq=01 error=00
/kernel: acd0: REQUEST_SENSE command timeout - resetting
/kernel: ata1: resetting devices ..  device dissapeared! 1 ata1-master:
timeout waiting to give command=ef s=90 e=20
/kernel: done
/kernel: ata1-master: timeout waiting to give command=a0 s=90 e=20
/kernel: acd0: failure to send ATAPI packet command
/kernel: acd0: failure to execute ATAPI packet command 

Is this problem solved in freebsd 4.0-STABLE? What is happening?

Thanks,
Paulo Fragoso.

-- 
   __O
 _-\<,_     Why drive when you can bike?
(_)/ (_)




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


From owner-freebsd-stable  Thu Mar 30 12: 2:37 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from evil.2y.net (ztown1-1-55.adsl.one.net [207.78.254.55])
	by hub.freebsd.org (Postfix) with ESMTP
	id C5DB137B890; Thu, 30 Mar 2000 12:02:23 -0800 (PST)
	(envelope-from cokane@evil.2y.net)
Received: (from cokane@localhost)
	by evil.2y.net (8.9.3/8.9.3) id PAA00447;
	Thu, 30 Mar 2000 15:07:14 -0500 (EST)
	(envelope-from cokane)
Date: Thu, 30 Mar 2000 15:07:14 -0500
From: Coleman Kane <cokane@one.net>
To: Kris Kennaway <kris@FreeBSD.org>
Cc: Dale Robson <djr8620@ritvax.isc.rit.edu>,
	stable <stable@FreeBSD.org>
Subject: Re: 4.0 stable upgrade trouble
Message-ID: <20000330150714.A428@evil.2y.net>
References: <38E2CD86.594A7335@rit.edu> <Pine.BSF.4.21.0003292233001.66563-100000@freefall.freebsd.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0.1i
In-Reply-To: <Pine.BSF.4.21.0003292233001.66563-100000@freefall.freebsd.org>; from kris@FreeBSD.org on Thu, Mar 30, 2000 at 01:35:31AM -0500
X-Vim: vim:tw=70:ts=4:sw=4
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

For anyone who'd like to know, I was able to successfully upgrade to 4.0-RELEASE
by downloading the source tarballs, and unpacking them in my /usr/src directory.
I cleared it out of the old 3.4 sources beforehand, and found that you must
first compile a 4.0 kernel and reboot before attempting a make world. After you
reboot, you can drop in to single-user (for safety), and run yoyur make world. 

Since it only installs the new gcc at the end, you may want to re-make world a
second time, or simply make and install gcc, etc. first.
--cokane

Kris Kennaway had the audacity to say:
> You should have read the UPDATING file before attempting this. It explains
> the hoops you need to jump through. I don't know whether you can easily
> recover from where you are now, it might be best to restore the system
> directories from a backup and start again.
> 
> Kris
> 
> On Wed, 29 Mar 2000, Dale Robson wrote:
> 
> > To anyone who can help,
> > 	I've been trying to upgrade from 3.3 stable to 4.0 stable and I've been
> > having trouble getting it to work.  I have run make buildworld and that
> > worked.  Then during make installworld I got an error so that only half
> > the files were installed.  
> > 	The trouble that I now have is that the newly upgraded 'make' links
> > with the old versions of several libraries.  When I try to run make it
> > says: "Bad sytem call".  Is there a way to fix make without being able
> > to use make?  I've made a couple attempts at running a staticly linked
> > version on make compiled on other boxes but they all argue about the
> > ".include <bsd.prog.mk>" lines in the make files.  Thank you for any
> > help.
> > 
> > Dale Robson
> > 
> > 
> > To Unsubscribe: send mail to majordomo@FreeBSD.org
> > with "unsubscribe freebsd-stable" in the body of the message
> > 
> 
> ----
> In God we Trust -- all others must submit an X.509 certificate.
>     -- Charles Forsythe <forsythe@alum.mit.edu>
> 
> 
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-stable" in the body of the message


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


From owner-freebsd-stable  Thu Mar 30 12:55:24 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from rover.village.org (rover.village.org [204.144.255.49])
	by hub.freebsd.org (Postfix) with ESMTP id B4B9837B93F
	for <freebsd-stable@FreeBSD.ORG>; Thu, 30 Mar 2000 12:55:20 -0800 (PST)
	(envelope-from imp@harmony.village.org)
Received: from harmony.village.org (harmony.village.org [10.0.0.6])
	by rover.village.org (8.9.3/8.9.3) with ESMTP id NAA69865;
	Thu, 30 Mar 2000 13:54:52 -0700 (MST)
	(envelope-from imp@harmony.village.org)
Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id NAA26446; Thu, 30 Mar 2000 13:54:24 -0700 (MST)
Message-Id: <200003302054.NAA26446@harmony.village.org>
To: "Steve O'Hara-Smith" <steveo@eircom.net>
Subject: Re: Let 3.x die ASAP? 
Cc: Kiril Mitev <kiril@ideaglobal.com>, freebsd-stable@FreeBSD.ORG,
	cracauer@cons.org, jkh@zippy.cdrom.com, didier@omnix.net,
	chad@DCFinc.com
In-reply-to: Your message of "Thu, 30 Mar 2000 17:41:24 +0100."
		<XFMail.000330174124.steveo@eircom.net> 
References: <XFMail.000330174124.steveo@eircom.net>  
Date: Thu, 30 Mar 2000 13:54:23 -0700
From: Warner Losh <imp@village.org>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

In message <XFMail.000330174124.steveo@eircom.net> "Steve O'Hara-Smith" writes:
: to be at least as good as 2.x'.

... if not better...

Warner


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


From owner-freebsd-stable  Thu Mar 30 13:52:33 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from ants.pocketscience.com (gateway1.pocketscience.com [209.24.64.3])
	by hub.freebsd.org (Postfix) with ESMTP id ACF5937B962
	for <freebsd-stable@FreeBSD.ORG>; Thu, 30 Mar 2000 13:52:27 -0800 (PST)
	(envelope-from brian@pocketscience.com)
Received: from pocketscience.com (southpark.i.pocketscience.com [10.10.4.2]) by ants.pocketscience.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2448.0)
	id HXB8GACW; Thu, 30 Mar 2000 13:52:20 -0800
Message-ID: <38E3CC94.CF08C7D6@pocketscience.com>
Date: Thu, 30 Mar 2000 13:52:20 -0800
From: Brian Nelson <brian@pocketscience.com>
Organization: PocketScience, Inc
X-Mailer: Mozilla 4.72 [en] (X11; U; FreeBSD 4.0-STABLE i386)
X-Accept-Language: en, pdf
MIME-Version: 1.0
To: Kiril Mitev <kiril@ideaglobal.com>
Cc: chad@DCFinc.com, didier@omnix.net, jkh@zippy.cdrom.com,
	cracauer@cons.org, freebsd-stable@FreeBSD.ORG
Subject: Re: Let 3.x die ASAP?
References: <200003301625.QAA76045@loki.ideaglobal.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Well, unless he/she is a member of the FreeBSD team, or WC CD-ROM, then
you should not take their e-mail as the word of god.

Kiril Mitev wrote:
> 
> > As I recall, Didier Derny wrote:
> > > I can't an many people can't upgrade the system on their machine
> > > at the actual rythm of FreeBSD version (each one supposed to be the best
> > > one and solve most of the problems :-))) )
> > > without a real stability (like the one with 2.x) this product
> > > has no more value than linux or solaris, sco...
> >
> > So, is there some feature in the 3.x line that isn't in 2.2.x that
> > you can't live without?  If not, your course is clear.  Put up a
> > 2.2-STABLE system and quit worrying about stability.
> 
> *ahem*
> 
> In other words "do not use anything newer than 2.2 if you
> worry about stability"...
> 
> In other words "nothing in FreeBSD has improved stability
> since 2.2"
> 
> In other words "2.2 is our most stable version"
> 
> (ever?)
> 
> In other words ..... you get the drift .......
> 
> OUCH
> 
> *off to downgrade all those servers ASAP*
> 
> *oh, and replace them with 486's, after all 486's with
> 2.2 on them have years of uptime*
> 
> >       -crl
> > --
> > Chad R. Larson (CRL15)   602-953-1392   Brother, can you paradigm?
> > chad@dcfinc.com         chad@larsons.org          larson1@home.net
> > DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207
> 
> ok, I _might_ be exaggerating a bit .... but this reply *DOES*
> come as a bit of a shock ..... <insert grinning noises here>
> 
> --
> Kiril Mitev, IT Operations Mgr, London
> IDEAglobal.com
> Standard Corporate Disclaimer applies, see
> http://www.ideaglobal.com/email-disclaimer.html
> for details.
> 
> 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 30 14: 5:56 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from isabase.philol.msu.ru (isabase.philol.msu.ru [195.208.217.73])
	by hub.freebsd.org (Postfix) with ESMTP id 950A637B520
	for <freebsd-stable@freebsd.org>; Thu, 30 Mar 2000 14:05:43 -0800 (PST)
	(envelope-from grg@isabase.philol.msu.ru)
Received: (from grg@localhost)
	by isabase.philol.msu.ru (8.9.3/8.9.2) id CAA03807
	for freebsd-stable@freebsd.org; Fri, 31 Mar 2000 02:05:43 +0400 (MSD)
	(envelope-from grg)
Date: Fri, 31 Mar 2000 02:05:42 +0400
From: Grigoriy Strokin <grg@philol.msu.ru>
To: freebsd-stable@freebsd.org
Subject: Re: Audio record problems in 4.0-STABLE: 1. Creative ViBRA16X
Message-ID: <20000331020541.A3613@isabase.philol.msu.ru>
References: <20000326200211.A6863@isabase.philol.msu.ru>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0.1i
In-Reply-To: <20000326200211.A6863@isabase.philol.msu.ru>; from grg@philol.msu.ru on Sun, Mar 26, 2000 at 08:02:11PM +0400
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hello,

While the bug wiping out filesystems on machines with Apollo MVP3 when ATA
driver is in UDMA mode is being fixed, I suppose there at least should be some
note added to /usr/src/UPDATING, so that another users do not loss
all their data and have to reinitialize /usr and restore it from backup, as I
had to do?

Something like that:

    If you use the Apollo MVP3 chipset, it is STRONGLY
    recommended that you disable the use of DMA mode in ATA drivers
    BEFORE you try to boot the system after `make installworld'.
    Add the following line:
      /sbin/sysctl -w hw.atamodes=pio,pio,pio,pio
    to the very beginning of your /etc/rc,
    ~root/.profile and ~root/.login.
    Be warned that if you don't disable the DMA mode,
    all your filesystems may be corrupted because
    of a bug in the driver that is still being fixed.

On Sun, Mar 26, 2000 at 08:02:11PM +0400, Grigoriy Strokin wrote:
> SYNOPSIS: device timeout(?) during the attempt to record anything
> 
> Hello,
> 
> I have two sound cards (only one is inserted into the box at any given
> moment) and am unable to make record properly any of them.
> 
> The FreeBSD sources I use have been CVSUPed on Mar 24.
> 
> FreeBSD isabase.philol.msu.ru 4.0-STABLE FreeBSD 4.0-STABLE #2: Sat Mar 25
> 21:31:20 MSK 2000
> grg@isabase.philol.msu.ru:/usr/src/sys/compile/ISABASE  i386
> 
> Now on the first card, it is ISA, behaves as a PnP card and is detected as
> Creative ViBRA16X.
> 
> kernel config
> -------------
> 
> I have the following lines in my config:
> 
>   # (also tried with the this option commented out)
>   options        PNPBIOS
> 
>   # (also tried as "device pcm0 at isa? irq 5 drq 1 flags 0x15", to 
>   # try forcing the card be detected as non-PnP, with the only
>   # effect of appearing "pcm1" instead of "pcm0" in dmesg)
>   device pcm
> 
>   # (also tried with this device commented out
>   # and also "device sbc0 at isa? port 0x220 irq 5 drq 1 # flags 0x15",
>   # effect of appearing "sbc1" instead of "sbc0" in dmesg)
>   device sbc
> 
> boot loader config
> ------------------
> 
> In FreeBSD 3.4, I had the following command required
> to make my SB work in /boot/kernel.conf:
>    pnp 1 0 os enable port0 0x220 irq0 5 drq0 1 drq1 3
> Now it seems that it is not required and considered as error,
> though "man pnp" states the contrary. So I tried to boot
> with and without this command.
> 
> BIOS setup
> -----------
> 
> All configurations have been tried with both
> "PnP OS installed: Yes" and "PnP OS installed: No",
> without any effect the behaviour of the card.
> 
> dmesg
> -----
> 
> The messages in dmesg related to audio and PnP are as follows:
>    
> 1) With "options PNPBIOS":
> 
> unknown: <PNP0000> can't assign resources
> unknown0: <PNP0200> at port 0-0xf,0x81-0x83,0x87,0x89-0x8b,0x8f-0x91,0xc0-0xdf drq 4 on isa0
> unknown1: <PNP0100> at port 0x40-0x43 irq 0 on isa0
> unknown2: <PNP0b00> at port 0x70-0x71 irq 8 on isa0
> unknown: <PNP0303> can't assign resources
> unknown: <PNP0800> can't assign resources
> unknown3: <PNP0c04> at port 0xf0-0xff irq 13 on isa0
> unknown4: <PNP0c01> at iomem 0-0x9ffff,0xfffe0000-0xffffffff,0x100000-0x3ffffff on isa0
> unknown5: <PNP0c02> at iomem 0xf0000-0xf3fff,0xf4000-0xf7fff,0xf8000-0xfbfff,0xfc000-0xfffff on isa0
> unknown6: <PNP0a03> at port 0x294-0x297,0x4d0-0x4d1,0xcf8-0xcff,0x480-0x48f,0x4000-0x403f,0x5000-0x501f on isa0
> unknown7: <PNP0c02> at port 0x208-0x20f on isa0
> unknown: <PNP0501> can't assign resources
> unknown: <PNP0700> can't assign resources
> unknown: <PNP0401> can't assign resources
> unknown: <PNP0501> can't assign resources
> sbc0: <Creative ViBRA16X> at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5 drq 1,3 on isa0
> sbc0: setting card to irq 5, drq 1, 3
> pcm0: <SB DSP 4.16 (ViBRA16X)> on sbc0
> unknown8: <Game> at port 0x201 on isa0
> 
> 2) Without "options PNPBIOS":
> 
> sbc0: <Creative ViBRA16X> at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5
> drq 1,3 on isa0
> sbc0: setting card to irq 5, drq 1, 3
> pcm0: <SB DSP 4.16 (ViBRA16X)> on sbc0
> unknown0: <Game> at port 0x201 on isa0
> 
> 
> Problems
> ---------
> 
> Playback of .au, .wav, .mp3 works as expected.
> 
> However, when I attempt to record an .au or .wav
> with the 'rec' program from sox, e. g.:
>   grg@isabase.1:~$ rec a.au
>   Send break (control-c) to end recording
> 
> I cant interrupt the recording with pressing
> control-c one or several times: the "^C" is just printed on the terminal,
> and the program won't stop.
> 
> If I press "^\" (quit), "^\" is printed, and
> there is no any effect for more than 3 seconds, and only after that I see
> "Quit - core dumped". The resulting file, a.au has zero length.
> There are no any messages on the console except:
>   /kernel: pid 7403 (sox), uid 1001: exited on signal 3 (core dumped)
> It looks like device timeout for me, but whatever it is,
> I can't record anything.
> 
> I tried to record 16-bit sound instead of default 8-bit,
> with the same effect.
> 
> Also, I try to record using the 'lrecord' command
> from ESPS/waves+, a commercial software equipment
> compiled for Linux (lrecord states for Linux-record). 
> lrecord worked for me
> on FreeBSD 3.4. Now I get the following:
>   grg@isabase.1:~$ lrecord a.sd
>   [then I press ^C]
> 
>   Problems writing samples at sample number 0
>   No samples collected!
> 
> Now what?
> 
> History
> --------
> 
> Both 'rec' and 'lrecord' worked for me for 8-bit and 16-bit
> 8 KHz sound on FreeBSD 3.4-STABLE.
> However, there were a strange message on the console
> just after starting rec or lrecord that looked something like:
>    drq0 and drq1 swap: now 3 and 1
> and just after finishing the recording:
>    drq0 and drq1 swap: now 1 and 3
> I have no idea if this is a problem at all,
> but on other machines with other sound cards
> there is no such a message.
> 
> But also, there WAS another problem on FreeBSD 3.4-STABLE:
> If I recorded 16 KHz sound instead of 8 KHz,
> it seemed to work OK, and the sound was actually recorded.
> However, if I used tools for drawing dynamic spectrograms
> of the sound (such as sound processing tools from ESPS)
> they showed no spectral information above 4 KHz.
> This is the evidence of that the hardware actually
> recorded the audio at the frequency rate of 8KHz,
> though software thought it put the hardware in
> 16KHz mode (when you make a spectrum, for a 8KHz
> sound, you only can see spectral information
> up to 4Khz, for 16KHz sound you can see it up to 8KHz,
> and so on).
> 
> If I recorded a 16KHz sound on another machine
> copied it to my machine and visualized using the same
> tools, I could see spectral information up to 
> 8KHz, as expected.
> 
> So the was apparently pcm driver problem in FreeBSD 3.4-STABLE.
> I have installed 4-STABLE that early in hope that
> new pcm driver would work better, and as result
> I cannot record audio at all.
> 
> What now?
> Please help.
> 
> 
> P.S. I don't know the exact model name of this SB16 Vibra:
> it was preinstalled in that newly bought machine and the only
> documentation for the SB was a four-page paper with intructions
> on how to install Windows drivers for it.
> 
> -- 
> === Grigoriy Strokin, Lomonosov University (MGU), Moscow ===
> === contact info: http://isabase.philol.msu.ru/~grg/     ===

-- 
=== Grigoriy Strokin, Lomonosov University (MGU), Moscow ===
=== contact info: http://isabase.philol.msu.ru/~grg/     ===


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


From owner-freebsd-stable  Thu Mar 30 14:10:55 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from isabase.philol.msu.ru (isabase.philol.msu.ru [195.208.217.73])
	by hub.freebsd.org (Postfix) with ESMTP id 2CC8837BA6D
	for <freebsd-stable@freebsd.org>; Thu, 30 Mar 2000 14:10:48 -0800 (PST)
	(envelope-from grg@isabase.philol.msu.ru)
Received: (from grg@localhost)
	by isabase.philol.msu.ru (8.9.3/8.9.2) id CAA03931
	for freebsd-stable@freebsd.org; Fri, 31 Mar 2000 02:10:44 +0400 (MSD)
	(envelope-from grg)
Date: Fri, 31 Mar 2000 02:10:43 +0400
From: Grigoriy Strokin <grg@philol.msu.ru>
To: freebsd-stable@freebsd.org
Subject: Re: Audio record problems in 4.0-STABLE: 1. Creative ViBRA16X
Message-ID: <20000331021043.A3912@isabase.philol.msu.ru>
References: <20000326200211.A6863@isabase.philol.msu.ru> <20000331020541.A3613@isabase.philol.msu.ru>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0.1i
In-Reply-To: <20000331020541.A3613@isabase.philol.msu.ru>; from grg@philol.msu.ru on Fri, Mar 31, 2000 at 02:05:42AM +0400
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Fri, Mar 31, 2000 at 02:05:42AM +0400, Grigoriy Strokin wrote:
> Hello,
> 
> While the bug wiping out filesystems on machines with Apollo MVP3 when ATA
> driver is in UDMA mode is being fixed, I suppose there at least should be some
> note added to /usr/src/UPDATING, so that another users do not loss
> all their data and have to reinitialize /usr and restore it from backup, as I
> had to do?
> 
> Something like that:
> 
>     If you use the Apollo MVP3 chipset, it is STRONGLY
>     recommended that you disable the use of DMA mode in ATA drivers
>     BEFORE you try to boot the system after `make installworld'.
                                               ^^^^^^^^^^^^^^^^
should be `make installkernel'

>     Add the following line:
>       /sbin/sysctl -w hw.atamodes=pio,pio,pio,pio
>     to the very beginning of your /etc/rc,
>     ~root/.profile and ~root/.login.
>     Be warned that if you don't disable the DMA mode,
>     all your filesystems may be corrupted because
>     of a bug in the driver that is still being fixed.
> 
-- 
=== Grigoriy Strokin, Lomonosov University (MGU), Moscow ===
=== contact info: http://isabase.philol.msu.ru/~grg/     ===


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


From owner-freebsd-stable  Thu Mar 30 14:21:38 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from isabase.philol.msu.ru (isabase.philol.msu.ru [195.208.217.73])
	by hub.freebsd.org (Postfix) with ESMTP id 3C52337B95C
	for <freebsd-stable@freebsd.org>; Thu, 30 Mar 2000 14:21:32 -0800 (PST)
	(envelope-from grg@isabase.philol.msu.ru)
Received: (from grg@localhost)
	by isabase.philol.msu.ru (8.9.3/8.9.2) id CAA04123
	for freebsd-stable@freebsd.org; Fri, 31 Mar 2000 02:21:30 +0400 (MSD)
	(envelope-from grg)
Date: Fri, 31 Mar 2000 02:21:30 +0400
From: Grigoriy Strokin <grg@philol.msu.ru>
To: freebsd-stable@freebsd.org
Subject: Re: New kernel with its ATA drivers damages the filesystem
Message-ID: <20000331022130.A4045@isabase.philol.msu.ru>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0.1i
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

[sorry --- this message has been recently posted with
a wrong subject line]

Hello,

While the bug wiping out filesystems on machines with Apollo MVP3 when ATA
driver is in UDMA mode is being fixed, I suppose there at least should be some
note added to /usr/src/UPDATING, so that another users do not loss
all their data and have to reinitialize /usr and restore it from backup, as I
had to do?

Something like that:

    If you use the Apollo MVP3 chipset, it is STRONGLY
    recommended that you disable the use of DMA mode in ATA drivers
    BEFORE you try to boot the system after `make installkernel'.
    Add the following line:
      /sbin/sysctl -w hw.atamodes=pio,pio,pio,pio
    to the very beginning of your /etc/rc,
    ~root/.profile and ~root/.login.
    Be warned that if you don't disable the DMA mode,
    all your filesystems may be corrupted because
    of a bug in the driver that is still being fixed.

> Hello,
> 
> Three days ago I've performed my first upgrade to FreeBSD 4.0-STABLE from
> 3.4 on one machine, via CVSUP. Observing the lack of any problems for 3
> days (except audio record) I decided to install it to another box, from the
> same sources.
> 
> Well, buildworld etc., then buildkernel (GENERIC), installkernel,
> reboot.
> 
> During the boot, I've seen:
> 
> Mar 28 17:48:56 koch2 /kernel: ata0: at 0x1f0 irq 14 on atapci0
> ...
> Mar 28 17:49:07 koch2 /kernel: ed0: <Longshine LCS-8634P Ethernet Card
> Mar 28 17:49:07 koch2 /kernel: > at port 0x240-0x25f iomem 0xc0000-0xc003f irq 11 on isa0
> Mar 28 17:49:07 koch2 /kernel: ed0: supplying EUI64: 08:00:00:ff:fe:00:10:37
> Mar 28 17:49:07 koch2 /kernel: ed0: address 08:00:00:00:10:37, type NE2000 (16 bit)
> ...
> Mar 28 17:49:07 koch2 /kernel: ad0: 8063MB <FUJITSU MPD3084AT> [16383/16/63] at ata0-master using UDMA33
> Mar 28 17:49:07 koch2 /kernel: acd0: CDROM <TOSHIBA CD-ROM XM-6402B> at ata0-slave using PIO4
> ...
> Mar 28 17:49:07 koch2 /kernel: ed0: device timeout
> Mar 28 17:49:07 koch2 /kernel: ed0: device timeout
> Mar 28 17:49:07 koch2 /kernel: ata0: resetting devices .. done
> Mar 28 17:49:48 koch2 /kernel: ad0: WRITE command timeout - resetting
> Mar 28 17:49:48 koch2 /kernel: ata0: resetting devices .. done
> 
> The booting process continued. Then I shut down the machine
> and turned it off and on again, just in case there were
> real problem with HDD.
> 
> Second boot:
> 
> fsck says about /usr "UNEXPECTED INCONSISTENCY, RUN FSCK MANUALLY".
> 
> After running fsck -y several times quite a few files
> have been either deleted or moved to lost+found.
> /usr/local and my home directory disappeared.
> 
> Then I rebooted again in order to turn 'UDMA' off in BIOS.
> 
> And again I've seen 'ad0: WRITE command timeout - resetting'
> messages, and again /usr became damaged, which resulted
> in loss of many other files and directories.
> 
> Moreover, despite that fact that ed0 was detected,
> "ifconfig ed0" gave "interface does not exist"
> (also, note the 'ed0 device timeout' messages above)
> 
> Now I think I don't know where to find the source of the problem.
> 

-- 
=== Grigoriy Strokin, Lomonosov University (MGU), Moscow ===
=== contact info: http://isabase.philol.msu.ru/~grg/     ===


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


From owner-freebsd-stable  Thu Mar 30 14:38:19 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from dt051n0b.san.rr.com (dt051n0b.san.rr.com [204.210.32.11])
	by hub.freebsd.org (Postfix) with ESMTP id A72BA37BA92
	for <freebsd-stable@FreeBSD.ORG>; Thu, 30 Mar 2000 14:38:16 -0800 (PST)
	(envelope-from Doug@gorean.org)
Received: from slave (doug@slave [10.0.0.1])
	by dt051n0b.san.rr.com (8.9.3/8.9.3) with ESMTP id OAA62248;
	Thu, 30 Mar 2000 14:38:13 -0800 (PST)
	(envelope-from Doug@gorean.org)
Date: Thu, 30 Mar 2000 14:38:13 -0800 (PST)
From: Doug Barton <Doug@gorean.org>
X-Sender: doug@dt051n0b.san.rr.com
To: Siew Sim <siewsim@prismedia.com>
Cc: freebsd-stable@FreeBSD.ORG
Subject: Re: please help - thread-safe mysql client link problem
In-Reply-To: <38E3833D.A57695F0@prismedia.com>
Message-ID: <Pine.BSF.4.21.0003301437030.62168-100000@dt051n0b.san.rr.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Thu, 30 Mar 2000, Siew Sim wrote:

> Hi,
> 
>     I'm using FreeBSD 3.2, and mysql 3.22.30.  I'm trying to build a
> thread-safe mysql client with pthread.

	Before you go any further, I would upgrade to 3.4-Stable. Chances
are good that the thread code is much improved in later versions, and this
will give you a better basis for providing feedback to people who would
like to help you with it.

Good luck,

Doug



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


From owner-freebsd-stable  Thu Mar 30 14:40:59 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from freeway.dcfinc.com (cx74889-a.phnx3.az.home.com [24.1.193.157])
	by hub.freebsd.org (Postfix) with ESMTP id 52AF337B86E
	for <freebsd-stable@FreeBSD.ORG>; Thu, 30 Mar 2000 14:40:55 -0800 (PST)
	(envelope-from chad@freeway.dcfinc.com)
Received: (from chad@localhost)
	by freeway.dcfinc.com (8.8.8/8.8.8) id PAA20522;
	Thu, 30 Mar 2000 15:40:36 -0700 (MST)
	(envelope-from chad)
From: "Chad R. Larson" <chad@DCFinc.com>
Message-Id: <200003302240.PAA20522@freeway.dcfinc.com>
Subject: Re: Let 3.x die ASAP?
In-Reply-To: <200003301625.QAA76045@loki.ideaglobal.com> from Kiril Mitev at "Mar 30, 0 04:25:18 pm"
To: kiril@ideaglobal.com (Kiril Mitev)
Date: Thu, 30 Mar 2000 15:40:35 -0700 (MST)
Cc: didier@omnix.net, jkh@zippy.cdrom.com, cracauer@cons.org,
	freebsd-stable@FreeBSD.ORG
Reply-To: chad@DCFinc.com
X-Mailer: ELM [version 2.4ME+ PL40 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

As I recall, Kiril Mitev wrote:
> > As I recall, Didier Derny wrote:
> > > I can't an many people can't upgrade the system on their machine
> > > at the actual rythm of FreeBSD version (each one supposed to be the best
> > > one and solve most of the problems :-))) )
> > > without a real stability (like the one with 2.x) this product
> > > has no more value than linux or solaris, sco...
> > 
> > So, is there some feature in the 3.x line that isn't in 2.2.x that
> > you can't live without?  If not, your course is clear.  Put up a
> > 2.2-STABLE system and quit worrying about stability.
> 
> *ahem*
> 
> In other words "do not use anything newer than 2.2 if you 
> worry about stability"...
> 
> In other words "nothing in FreeBSD has improved stability
> since 2.2"

Well, not an exact quote.  Didier refered to the "real stability" of
2.2, so I suggested if he felt that way, he should run it.

> In other words "2.2 is our most stable version"
> (ever?)

Might have been...

	-crl
--
Chad R. Larson (CRL15)   602-953-1392   Brother, can you paradigm?
chad@dcfinc.com         chad@larsons.org          larson1@home.net   
DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207


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


From owner-freebsd-stable  Thu Mar 30 15:25:38 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
	by hub.freebsd.org (Postfix) with ESMTP
	id F195837B962; Thu, 30 Mar 2000 15:25:35 -0800 (PST)
	(envelope-from kris@FreeBSD.org)
Received: from localhost (kris@localhost)
	by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id PAA51105;
	Thu, 30 Mar 2000 15:25:35 -0800 (PST)
	(envelope-from kris@FreeBSD.org)
X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs
Date: Thu, 30 Mar 2000 15:25:35 -0800 (PST)
From: Kris Kennaway <kris@FreeBSD.org>
To: Siew Sim <siewsim@prismedia.com>
Cc: freebsd-stable@FreeBSD.ORG
Subject: Re: please help - thread-safe mysql client link problem
In-Reply-To: <38E3833D.A57695F0@prismedia.com>
Message-ID: <Pine.BSF.4.21.0003301524490.49247-100000@freefall.freebsd.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Thu, 30 Mar 2000, Siew Sim wrote:

> Hi,
> 
>     I'm using FreeBSD 3.2, and mysql 3.22.30.  I'm trying to build a
> thread-safe mysql client with pthread.

Use the port.

Kris

----
In God we Trust -- all others must submit an X.509 certificate.
    -- Charles Forsythe <forsythe@alum.mit.edu>



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


From owner-freebsd-stable  Thu Mar 30 17:18: 3 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from hbo.isi.edu (hbo.isi.edu [128.9.160.75])
	by hub.freebsd.org (Postfix) with ESMTP
	id 3210C37B70C; Thu, 30 Mar 2000 17:17:56 -0800 (PST)
	(envelope-from larse@hbo.isi.edu)
Received: (from larse@localhost)
	by hbo.isi.edu (8.9.3/8.9.3) id RAA89658;
	Thu, 30 Mar 2000 17:17:36 GMT
	(envelope-from larse)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <14563.35888.275361.664807@hbo.isi.edu>
Date: Thu, 30 Mar 2000 17:17:36 +0000 (GMT)
From: Lars Eggert <larse@isi.edu>
To: freebsd-atm@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG
Subject: Adaptec-155-ATM at en0 causing amd problem
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

I'm seeing some extremely odd behaviour on a system that runs the amd
automounter and has an Adaptec-155-ATM card at interface en0.

Configuration: The system in question has two Ethernet cards, one of
which (fxp0) connects the system to our LAN, the other is used locally
for experiments (de0). The system also has an Adaptec-155-ATM card at
interface en0, which is *not* connected to anything yet. The system is
currently running 4.0-STABLE, but I've seen the same behavior under
3.2-RELEASE as well:

As long as I leave en0 unconfigured (ifconfig en0 says "en0:
flags=800<SIMPLEX> mtu 9180"), everything is fine.

If I put an ifconfig entry in rc.conf.local (e.g.
ifconfig_en0="10.9.112.211 netmask 255.255.240.0 up"), the automounter
fails to work. Note that amd (like all other network services) uses
the hosts main interface (fxp0). Here's what I see at boot time, as
soon as amd starts:

Mar 30 14:27:12 mul /kernel: atm_rtrequest: RTM_RESOLVE request detected?
Mar 30 14:27:12 mul /kernel: nfs send error 65 for server pid133@mul:/nfs
Mar 30 14:27:12 mul /kernel: nfs send error 65 for server pid133@mul:/home

amd fails, but the rest of the network services seem unaffected.

Even more strange, if I manually configure en0 after the system has
booted (and amd has started), I do not see any problems, i.e. amd
continues to work.

Also, if I replace the Adaptec card with an Efficient Networks
ENI-155p card, amd also works fine; I do not see the messages above.
(Unfortunately, we don't have enough of those.)

Any ideas? Please let me know if you require more information, I'd be
happy to poke around the system a bit.

Thanks,
Lars
________________________________________________________________________
Lars Eggert <larse@isi.edu>               Information Sciences Institute
http://www.isi.edu/~larse/             University of Southern California


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


From owner-freebsd-stable  Thu Mar 30 18: 6:38 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from netcom.com (netcom11.netcom.com [199.183.9.111])
	by hub.freebsd.org (Postfix) with ESMTP id E53F237B87A
	for <freebsd-stable@freebsd.org>; Thu, 30 Mar 2000 18:06:20 -0800 (PST)
	(envelope-from stanb@netcom.com)
Received: (from stanb@localhost)
	by netcom.com (8.9.3/8.9.3) id SAA24830
	for freebsd-stable@freebsd.org; Thu, 30 Mar 2000 18:06:09 -0800 (PST)
From: Stan Brown <stanb@netcom.com>
Message-Id: <200003310206.SAA24830@netcom.com>
Subject: 4.0 make world after cvsup fails, HELP PLEASE
To: freebsd-stable@freebsd.org (FreeBSD Stable List)
Date: Thu, 30 Mar 2000 21:06:09 -0500 (EST)
X-Mailer: ELM [version 2.5 PL3]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

	Sorry about the shouting, but I have been beating my head against this
	since last Saturdy, and I am _not_ making any progress!

	I installed from the ftp sote (4.0), built the cvsup port, and cvsuped
	using the following files:


# $Id: secure-stable-supfile,v 1.9.2.2 1999/02/11 20:14:51 jdp Exp $
#
# This file contains all of the "CVSup collections" that make up the
# source tree of the FreeBSD-stable international secure distribution.
# If you are outside the USA or Canada, use this file.
#
# CVSup (CVS Update Protocol) allows you to download the latest CVS
# tree (or any branch of development therefrom) to your system easily
# and efficiently (far more so than with sup, which CVSup is aimed
# at replacing).  If you're running CVSup interactively, and are
# currently using an X display server, you should run CVSup as follows
# to keep your CVS tree up-to-date:
#
#	cvsup secure-stable-supfile
#
# If not running X, or invoking cvsup from a non-interactive script, then
# run it as follows:
#
#	cvsup -g -L 2 secure-stable-supfile
#
# You may wish to change some of the settings in this file to better
# suit your system:
#
# base=/usr
#		This specifies the root where CVSup will store information
#		about the collections you have transferred to your system.
#		A setting of "/usr" will generate this information in
#		/usr/sup.  Even if you are CVSupping a large number of
#		collections, you will be hard pressed to generate more than
#		~1MB of data in this directory.  You can override the
#		"base" setting on the command line with cvsup's "-b base"
#		option.  This directory must exist in order to run CVSup.
#
# prefix=/usr
#		This specifies where to place the requested files.  A
#		setting of "/usr" will place all of the files requested
#		in "/usr/src" (i.e., "/usr/src/eBones" and "/usr/src/secure").
#		The prefix directory must exist in order to run CVSup.

# Defaults that apply to all the collections
*default host=cvsup.FreeBSD.org
*default base=/usr
*default prefix=/usr
# The following line is for 3-stable.  If you want 2.2-stable, change
# "RELENG_3" to "RELENG_2_2".
*default release=cvs tag=RELENG_3
*default delete use-rel-suffix

# If your network link is a T1 or faster, comment out the following line.
*default compress

## The international secure collections.
src-crypto
src-eBones
src-secure


# $Id: secure-stable-supfile,v 1.9.2.2 1999/02/11 20:14:51 jdp Exp $
#
# This file contains all of the "CVSup collections" that make up the
# source tree of the FreeBSD-stable international secure distribution.
# If you are outside the USA or Canada, use this file.
#
# CVSup (CVS Update Protocol) allows you to download the latest CVS
# tree (or any branch of development therefrom) to your system easily
# and efficiently (far more so than with sup, which CVSup is aimed
# at replacing).  If you're running CVSup interactively, and are
# currently using an X display server, you should run CVSup as follows
# to keep your CVS tree up-to-date:
#
#	cvsup secure-stable-supfile
#
# If not running X, or invoking cvsup from a non-interactive script, then
# run it as follows:
#
#	cvsup -g -L 2 secure-stable-supfile
#
# You may wish to change some of the settings in this file to better
# suit your system:
#
# base=/usr
#		This specifies the root where CVSup will store information
#		about the collections you have transferred to your system.
#		A setting of "/usr" will generate this information in
#		/usr/sup.  Even if you are CVSupping a large number of
#		collections, you will be hard pressed to generate more than
#		~1MB of data in this directory.  You can override the
#		"base" setting on the command line with cvsup's "-b base"
#		option.  This directory must exist in order to run CVSup.
#
# prefix=/usr
#		This specifies where to place the requested files.  A
#		setting of "/usr" will place all of the files requested
#		in "/usr/src" (i.e., "/usr/src/eBones" and "/usr/src/secure").
#		The prefix directory must exist in order to run CVSup.

# Defaults that apply to all the collections
*default host=cvsup.FreeBSD.org
*default base=/usr
*default prefix=/usr
# The following line is for 3-stable.  If you want 2.2-stable, change
# "RELENG_3" to "RELENG_2_2".
*default release=cvs tag=RELENG_4
*default delete use-rel-suffix

# If your network link is a T1 or faster, comment out the following line.
*default compress

## The international secure collections.
src-all

	I have re cvsuped 4 times! All builds fail in the ppp build, with an
	error about not finding an openssh include file.

	I _strongly_ suspect that I have the wrong cvsup tags, probably for the
	security related stuff, but I am unable to figure it out. Geuss I am
	just too stupid!

	I looked in /usr/src/share/examples/cvsup, but these files appear to
	have the same tags as mine.

	I desperatly need 4.0 working to try and determine if it fixes a show
	stoper problem that I have with the 3C509 network cards.

	PLEASE< PLEASE will someone who has this working let me look at thier
	cvsup files!

-- 
Stan Brown     stanb@netcom.com                                    404-996-6955
Factory Automation Systems
Atlanta Ga.
-- 
Look, look, see Windows 95.  Buy, lemmings, buy!   
Pay no attention to that cliff ahead...            Henry Spencer
(c) 1998 Stan Brown.  Redistribution via the Microsoft Network is prohibited.


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


From owner-freebsd-stable  Thu Mar 30 18: 9:48 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from jade.chc-chimes.com (jade.chc-chimes.com [216.28.46.6])
	by hub.freebsd.org (Postfix) with ESMTP id 9844737C212
	for <freebsd-stable@freebsd.org>; Thu, 30 Mar 2000 18:09:39 -0800 (PST)
	(envelope-from billf@jade.chc-chimes.com)
Received: by jade.chc-chimes.com (Postfix, from userid 1001)
	id 4EAAF1C4A; Thu, 30 Mar 2000 21:09:35 -0500 (EST)
Date: Thu, 30 Mar 2000 21:09:35 -0500
From: Bill Fumerola <billf@chc-chimes.com>
To: Stan Brown <stanb@netcom.com>
Cc: FreeBSD Stable List <freebsd-stable@freebsd.org>
Subject: Re: 4.0 make world after cvsup fails, HELP PLEASE
Message-ID: <20000330210935.I23367@jade.chc-chimes.com>
References: <200003310206.SAA24830@netcom.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0i
In-Reply-To: <200003310206.SAA24830@netcom.com>; from stanb@netcom.com on Thu, Mar 30, 2000 at 09:06:09PM -0500
X-Operating-System: FreeBSD 3.2-RELEASE i386
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Thu, Mar 30, 2000 at 09:06:09PM -0500, Stan Brown wrote:

> *default release=cvs tag=RELENG_3
                           ^^^^^^^^
> *default delete use-rel-suffix
> 
> # If your network link is a T1 or faster, comment out the following line.
> *default compress
> 
> ## The international secure collections.
> src-crypto
> src-eBones
> src-secure
> 
> 
> 
> # Defaults that apply to all the collections
> *default host=cvsup.FreeBSD.org
> *default base=/usr
> *default prefix=/usr
> # The following line is for 3-stable.  If you want 2.2-stable, change
> # "RELENG_3" to "RELENG_2_2".
> *default release=cvs tag=RELENG_4
                           ^^^^^^^^
> *default delete use-rel-suffix
> 
> # If your network link is a T1 or faster, comment out the following line.
> *default compress
> 
> ## The international secure collections.
> src-all
> 
> 	I have re cvsuped 4 times! All builds fail in the ppp build, with an
> 	error about not finding an openssh include file.
> 
> 	I _strongly_ suspect that I have the wrong cvsup tags, probably for the
> 	security related stuff, but I am unable to figure it out. Geuss I am
> 	just too stupid!


Duh.

-- 
Bill Fumerola - Network Architect
Computer Horizons Corp - CVM
e-mail: billf@chc-chimes.com / billf@FreeBSD.org
Office: 800-252-2421 x128 / Cell: 248-761-7272





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


From owner-freebsd-stable  Thu Mar 30 18:11:11 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from cfdnet.me.tuns.ca (CFDnet.me.TUNS.Ca [134.190.50.164])
	by hub.freebsd.org (Postfix) with ESMTP id 3E12237C335
	for <freebsd-stable@FreeBSD.ORG>; Thu, 30 Mar 2000 18:11:02 -0800 (PST)
	(envelope-from bbmail@cfdnet.me.tuns.ca)
Received: from localhost (bbmail@localhost)
	by cfdnet.me.tuns.ca (8.9.3/8.9.3) with ESMTP id WAA32519;
	Thu, 30 Mar 2000 22:09:29 -0400 (AST)
	(envelope-from bbmail@cfdnet.me.tuns.ca)
Date: Thu, 30 Mar 2000 22:09:29 -0400 (AST)
From: Bryan Bursey <bbmail@cfdnet.me.tuns.ca>
To: Stan Brown <stanb@netcom.com>
Cc: FreeBSD Stable List <freebsd-stable@FreeBSD.ORG>
Subject: Re: 4.0 make world after cvsup fails, HELP PLEASE
In-Reply-To: <200003310206.SAA24830@netcom.com>
Message-ID: <Pine.BSF.4.10.10003302208010.32517-100000@cfdnet.me.tuns.ca>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Just a thought...  in the first supfile, the RELENG tag is for 3.x-STABLE.

> *default prefix=/usr
> # The following line is for 3-stable.  If you want 2.2-stable, change
> # "RELENG_3" to "RELENG_2_2".
> *default release=cvs tag=RELENG_3
                       ^^^^^^^^^^^^ 

Maybe changing the tag will help??

Bryan
iSpheric.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 30 18:22:40 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from cfdnet.me.tuns.ca (CFDnet.me.TUNS.Ca [134.190.50.164])
	by hub.freebsd.org (Postfix) with ESMTP id C550F37C2EB
	for <freebsd-stable@FreeBSD.ORG>; Thu, 30 Mar 2000 18:22:31 -0800 (PST)
	(envelope-from bbmail@cfdnet.me.tuns.ca)
Received: from localhost (bbmail@localhost)
	by cfdnet.me.tuns.ca (8.9.3/8.9.3) with ESMTP id WAA32552;
	Thu, 30 Mar 2000 22:20:56 -0400 (AST)
	(envelope-from bbmail@cfdnet.me.tuns.ca)
Date: Thu, 30 Mar 2000 22:20:56 -0400 (AST)
From: Bryan Bursey <bbmail@cfdnet.me.tuns.ca>
To: Stan Brown <stanb@netcom.com>
Cc: FreeBSD Stable List <freebsd-stable@FreeBSD.ORG>
Subject: Re: 4.0 make world after cvsup fails, HELP PLEASE
In-Reply-To: <Pine.BSF.4.10.10003302208010.32517-100000@cfdnet.me.tuns.ca>
Message-ID: <Pine.BSF.4.10.10003302219200.32547-100000@cfdnet.me.tuns.ca>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


> Just a thought...  in the first supfile, the RELENG tag is for 3.x-STABLE.
> 
> > *default prefix=/usr
> > # The following line is for 3-stable.  If you want 2.2-stable, change
> > # "RELENG_3" to "RELENG_2_2".
> > *default release=cvs tag=RELENG_3
>                        ^^^^^^^^^^^^ 

To finish what I should have said the first time...  change the tag to
RELENG_4 since you said you were using 4.0.

Cheers,

Bryan
iSpheric.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 30 19: 8:43 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from mail-03-real.cdsnet.net (mail-03-real.cdsnet.net [204.118.244.93])
	by hub.freebsd.org (Postfix) with SMTP id 33B0637C2B5
	for <stable@freebsd.org>; Thu, 30 Mar 2000 19:08:39 -0800 (PST)
	(envelope-from mrcpu@internetcds.com)
Received: (qmail 99589 invoked from network); 31 Mar 2000 03:08:38 -0000
Received: from schizo.cdsnet.net (204.118.244.32)
  by mail-03-real.cdsnet.net with SMTP; 31 Mar 2000 03:08:38 -0000
Date: Thu, 30 Mar 2000 19:04:50 -0800 (PST)
From: Jaye Mathisen <mrcpu@internetcds.com>
X-Sender: mrcpu@schizo.cdsnet.net
To: stable@freebsd.org
Subject: sshd failure from Adding crypto later on -stable?
Message-ID: <Pine.BSF.4.21.0003301902060.26102-100000@schizo.cdsnet.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG



installed a minimal 3.4 system.

Supped 4.0, but forgot crypto.

Upgraded to 4.0.

Supped 4.0 crypto.

Make world.

Reboot.

/usr/sbin/sshd starts, but fails upon connection with:

newsfeed# Mar 30 19:13:12 newsfeed
sshd[490]: fatal: rsa_private_decrypt() failed.
Mar 30 19:13:12 newsfeed sshd[490]: fatal: rsa_private_decrypt() failed.

ls -l /usr/lib/*rsa*
-r--r--r--  1 root  wheel  6358 Mar 30 14:12 /usr/lib/librsaUSA.a
lrwxr-xr-x  1 root  wheel    14 Mar 30 14:12 /usr/lib/librsaUSA.so ->
librsaUSA.so.1
-r--r--r--  1 root  wheel  8080 Mar 30 14:12 /usr/lib/librsaUSA.so.1
-r--r--r--  1 root  wheel  7122 Mar 30 14:12 /usr/lib/librsaUSA_p.a

newsfeed# ldd /usr/sbin/sshd
/usr/sbin/sshd:
        libcrypt.so.2 => /usr/lib/libcrypt.so.2 (0x2807f000)
        libcrypto.so.1 => /usr/lib/libcrypto.so.1 (0x28094000)
        libutil.so.3 => /usr/lib/libutil.so.3 (0x28131000)
        libz.so.2 => /usr/lib/libz.so.2 (0x2813b000)
        libwrap.so.3 => /usr/lib/libwrap.so.3 (0x28148000)
        libc.so.4 => /usr/lib/libc.so.4 (0x2814f000)

newsfeed# ls -ld /usr/lib/*crypt*
lrwxr-xr-x  1 root  wheel       13 Mar 30 14:07 /usr/lib/libcrypt.a ->
libdescrypt.a
lrwxr-xr-x  1 root  wheel       14 Mar 30 14:07 /usr/lib/libcrypt.so ->
libdescrypt.so
lrwxr-xr-x  1 root  wheel       16 Mar 30 14:07 /usr/lib/libcrypt.so.2 ->
libdescrypt.so.2
lrwxr-xr-x  1 root  wheel       15 Mar 30 14:07 /usr/lib/libcrypt_p.a ->
libdescrypt_p.a
-r--r--r--  1 root  wheel  1089776 Mar 30 14:12 /usr/lib/libcrypto.a
lrwxr-xr-x  1 root  wheel       14 Mar 30 14:12 /usr/lib/libcrypto.so ->
libcrypto.so.1
-r--r--r--  1 root  wheel   655796 Mar 30 14:12 /usr/lib/libcrypto.so.1
-r--r--r--  1 root  wheel  1163664 Mar 30 14:12 /usr/lib/libcrypto_p.a
-r--r--r--  1 root  wheel    15640 Mar 30 14:07 /usr/lib/libdescrypt.a
lrwxr-xr-x  1 root  wheel       16 Mar 30 14:07 /usr/lib/libdescrypt.so ->
libdescrypt.so.2
-r--r--r--  1 root  wheel    10296 Mar 30 14:07 /usr/lib/libdescrypt.so.2
-r--r--r--  1 root  wheel    17574 Mar 30 14:07 /usr/lib/libdescrypt_p.a
-r--r--r--  1 root  wheel     8824 Mar 30 14:07 /usr/lib/libscrypt.a
lrwxr-xr-x  1 root  wheel       14 Mar 30 14:07 /usr/lib/libscrypt.so ->
libscrypt.so.2
-r--r--r--  1 root  wheel     5084 Mar 30 14:07 /usr/lib/libscrypt.so.2
-r--r--r--  1 root  wheel     9470 Mar 30 14:07 /usr/lib/libscrypt_p.a


Not sure what's going on.  4.0 systems that have the crypt stuff installed
work fine, it's only this upgraded one that's having trouble.

Any tips appreciated.



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


From owner-freebsd-stable  Thu Mar 30 19:16:26 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from h006097780c24.ne.mediaone.net (h006097780c24.ne.mediaone.net [24.218.250.124])
	by hub.freebsd.org (Postfix) with ESMTP id 76FA737C31C
	for <stable@freebsd.org>; Thu, 30 Mar 2000 19:16:19 -0800 (PST)
	(envelope-from andy@lewman.com)
Received: from lewman.com (localhost [127.0.0.1])
	by h006097780c24.ne.mediaone.net (8.9.3/8.9.3) with ESMTP id WAA00571;
	Thu, 30 Mar 2000 22:15:10 -0500 (EST)
	(envelope-from andy@lewman.com)
Message-ID: <38E41820.4ED5DA9D@lewman.com>
Date: Thu, 30 Mar 2000 22:14:40 -0500
From: Andy <andy@lewman.com>
Organization: Lewman Industries
X-Mailer: Mozilla 4.72 [en] (X11; U; FreeBSD 4.0-STABLE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Jaye Mathisen <mrcpu@internetcds.com>
Cc: stable@freebsd.org
Subject: Re: sshd failure from Adding crypto later on -stable?
References: <Pine.BSF.4.21.0003301902060.26102-100000@schizo.cdsnet.net>
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms517AF219D3273C19E1605C84"
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

This is a cryptographically signed message in MIME format.

--------------ms517AF219D3273C19E1605C84
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Jaye Mathisen wrote:

> newsfeed# Mar 30 19:13:12 newsfeed
> sshd[490]: fatal: rsa_private_decrypt() failed.
> Mar 30 19:13:12 newsfeed sshd[490]: fatal: rsa_private_decrypt() failed.

	Did you explicitly install either OpenSSH or RSAREF2?  I had the same
problem until I installed both from ports (even though OpenSSh isn't
really a port anymore).  I don't know why the system install didn't take
care of it.

-- 

|  Andy   |     e-mail      |      web       |
|         | andy@lewman.com | www.lewman.com |

A very intelligent turtle
Found programming UNIX a hurdle
	The system, you see,
	Ran as slow as did he,
And that's not saying much for the turtle.
--------------ms517AF219D3273C19E1605C84
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIIJkAYJKoZIhvcNAQcCoIIJgTCCCX0CAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC
B10wggQnMIIDkKADAgECAhAXN8ogLRsvAwDJMiA8WgnMMA0GCSqGSIb3DQEBBAUAMIHMMRcw
FQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29y
azFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5
IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRp
dmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkMB4XDTk5MDUxMDAwMDAw
MFoXDTAwMDUwOTIzNTk1OVowggEPMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UE
CxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9y
ZXBvc2l0b3J5L1JQQSBJbmNvcnAuIGJ5IFJlZi4sTElBQi5MVEQoYyk5ODEeMBwGA1UECxMV
UGVyc29uYSBOb3QgVmFsaWRhdGVkMTMwMQYDVQQLEypEaWdpdGFsIElEIENsYXNzIDEgLSBO
ZXRzY2FwZSBGdWxsIFNlcnZpY2UxFjAUBgNVBAMUDUFuZHJldyBMZXdtYW4xHjAcBgkqhkiG
9w0BCQEWD2FuZHlAbGV3bWFuLmNvbTBcMA0GCSqGSIb3DQEBAQUAA0sAMEgCQQC/EaQmMjUQ
gdB4D3aH5as3M8CQY0I1RmgYevC7MoGkHezh80n+0XeGNEYE6LpMtwnAmv4NYPbwktR2EAz1
RaTPAgMBAAGjggEGMIIBAjAJBgNVHRMEAjAAMIGsBgNVHSAEgaQwgaEwgZ4GC2CGSAGG+EUB
BwEBMIGOMCgGCCsGAQUFBwIBFhxodHRwczovL3d3dy52ZXJpc2lnbi5jb20vQ1BTMGIGCCsG
AQUFBwICMFYwFRYOVmVyaVNpZ24sIEluYy4wAwIBARo9VmVyaVNpZ24ncyBDUFMgaW5jb3Jw
LiBieSByZWZlcmVuY2UgbGlhYi4gbHRkLiAoYyk5NyBWZXJpU2lnbjARBglghkgBhvhCAQEE
BAMCB4AwMwYDVR0fBCwwKjAooCagJIYiaHR0cDovL2NybC52ZXJpc2lnbi5jb20vY2xhc3Mx
LmNybDANBgkqhkiG9w0BAQQFAAOBgQBLxOO6fPb6g7wDdf3nyY05xisVS88KGnl3MXhU4Y7N
/rdCNVgoDy4Yj7qrdieJUMLAKZq91PkshncU4Ezzj94H8jmsbwSLOod9biAJ3s58fL6MREdD
vH0Xp0cw9k3JMpi4ipM5DkYfbeiCCczfvgYyY7Jly4cl/Iw08l4yQK239TCCAy4wggKXoAMC
AQICEQDSdi6NFAw9fbKoJV2v7g11MA0GCSqGSIb3DQEBAgUAMF8xCzAJBgNVBAYTAlVTMRcw
FQYDVQQKEw5WZXJpU2lnbiwgSW5jLjE3MDUGA1UECxMuQ2xhc3MgMSBQdWJsaWMgUHJpbWFy
eSBDZXJ0aWZpY2F0aW9uIEF1dGhvcml0eTAeFw05ODA1MTIwMDAwMDBaFw0wODA1MTIyMzU5
NTlaMIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1
c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJ
bmNvcnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3Mg
MSBDQSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkMIGfMA0G
CSqGSIb3DQEBAQUAA4GNADCBiQKBgQC7WkSKBBa7Vf0DeootlE8VeDa4DUqyb5xUv7zodyqd
ufBou5XZMUFweoFLuUgTVi3HCOGEQqvAopKrRFyqQvCCDgLpL/vCO7u+yScKXbawNkIztW5U
iE+HSr8Z2vkV6A+HthzjzMaajn9qJJLj/OBluqexfu/J2zdqyErICQbkmQIDAQABo3wwejAR
BglghkgBhvhCAQEEBAMCAQYwRwYDVR0gBEAwPjA8BgtghkgBhvhFAQcBATAtMCsGCCsGAQUF
BwIBFh93d3cudmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvUlBBMA8GA1UdEwQIMAYBAf8CAQAw
CwYDVR0PBAQDAgEGMA0GCSqGSIb3DQEBAgUAA4GBAIi4Nzvd2pQ3AK2qn+GBAXEekmptL/bx
ndPKZDjcG5gMB4ZbhRVqD7lJhaSV8Rd9Z7R/LSzdmkKewz60jqrlCwbe8lYq+jPHvhnXU0zD
vcjjF7WkSUJj7MKmFw9dWBpJPJBcVaNlIAD9GCDlX4KmsaiSxVhqwY0DPOvDzQWikK5uMYIB
+zCCAfcCAQEwgeEwgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJp
U2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRv
cnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2ln
biBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0
ZWQCEBc3yiAtGy8DAMkyIDxaCcwwCQYFKw4DAhoFAKCBsTAYBgkqhkiG9w0BCQMxCwYJKoZI
hvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0wMDAzMzEwMzE0NDBaMCMGCSqGSIb3DQEJBDEWBBTi
q8JMBdJdEg8rywKiNFKnoyLCYDBSBgkqhkiG9w0BCQ8xRTBDMAoGCCqGSIb3DQMHMA4GCCqG
SIb3DQMCAgIAgDAHBgUrDgMCBzANBggqhkiG9w0DAgIBQDANBggqhkiG9w0DAgIBKDANBgkq
hkiG9w0BAQEFAARAO+moKS3KOYEdVHG0pP5RHIyu/CXVPv5wHLTbaAnyQw0H/9Mm5quGcGS0
3Fn25ZLmUYxRibdTfHfePFLjYAzukg==
--------------ms517AF219D3273C19E1605C84--



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


From owner-freebsd-stable  Thu Mar 30 19:19: 2 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from mobile.gerp.org (caffeine.gerp.org [216.80.26.45])
	by hub.freebsd.org (Postfix) with SMTP id F04D737C462
	for <freebsd-stable@freebsd.org>; Thu, 30 Mar 2000 19:18:58 -0800 (PST)
	(envelope-from kdulzo@mobile.gerp.org)
Received: (qmail 12780 invoked by uid 100); 31 Mar 2000 03:18:58 -0000
Date: Thu, 30 Mar 2000 21:18:57 -0600
From: "Kevin M. Dulzo" <kdulzo@mobile.gerp.org>
To: Jaye Mathisen <mrcpu@internetcds.com>
Cc: freebsd-stable@freebsd.org
Subject: Re: sshd failure from Adding crypto later on -stable?
Message-ID: <20000330211857.A12767@mobile.gerp.org>
References: <Pine.BSF.4.21.0003301902060.26102-100000@schizo.cdsnet.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0.1i
In-Reply-To: <Pine.BSF.4.21.0003301902060.26102-100000@schizo.cdsnet.net>; from mrcpu@internetcds.com on Thu, Mar 30, 2000 at 07:04:50PM -0800
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


I believe the trick is to have the rsaref port installed before building
the crypto libraries -- this has never failed in my case.  If this
requirement has changed I am sure someone will correct me.

-Kevin


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


From owner-freebsd-stable  Thu Mar 30 22:59:35 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from peak.mountin.net (peak.mountin.net [207.227.119.2])
	by hub.freebsd.org (Postfix) with ESMTP id E0AF737B6C3
	for <freebsd-stable@FreeBSD.ORG>; Thu, 30 Mar 2000 22:59:32 -0800 (PST)
	(envelope-from jeff-ml@mountin.net)
Received: (from daemon@localhost)
	by peak.mountin.net (8.9.1/8.9.1) id AAA04322;
	Fri, 31 Mar 2000 00:58:17 -0600 (CST)
	(envelope-from jeff-ml@mountin.net)
Received: from dial-67.max1.wa.cyberlynk.net(207.227.118.67) by peak.mountin.net via smap (V1.3)
	id sma004318; Fri Mar 31 00:58:08 2000
Message-Id: <4.3.2.20000331005528.00b8c790@207.227.119.2>
X-Sender: jeff-ml@207.227.119.2
X-Mailer: QUALCOMM Windows Eudora Version 4.3
Date: Fri, 31 Mar 2000 00:57:35 -0600
To: "Kevin M. Dulzo" <kdulzo@mobile.gerp.org>
From: "Jeffrey J. Mountin" <jeff-ml@mountin.net>
Subject: Re: sshd failure from Adding crypto later on -stable?
Cc: freebsd-stable@FreeBSD.ORG
In-Reply-To: <20000330211857.A12767@mobile.gerp.org>
References: <Pine.BSF.4.21.0003301902060.26102-100000@schizo.cdsnet.net>
 <Pine.BSF.4.21.0003301902060.26102-100000@schizo.cdsnet.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

At 09:18 PM 3/30/00 -0600, Kevin M. Dulzo wrote:

>I believe the trick is to have the rsaref port installed before building
>the crypto libraries -- this has never failed in my case.  If this
>requirement has changed I am sure someone will correct me.

You can add RSAref after installing 4.0 or even after a buildworld.  You 
may need to restart sshd, but know of time I forgot and it worked.  There 
is no need to rebuild any libs.


Jeff Mountin - jeff@mountin.net
Systems/Network Administrator
FreeBSD - the power to serve



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


From owner-freebsd-stable  Thu Mar 30 23: 9:38 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from gateway.mindmaker.com (gateway.mindmaker.com [209.66.98.130])
	by hub.freebsd.org (Postfix) with ESMTP id 3011837B6A1
	for <stable@freebsd.org>; Thu, 30 Mar 2000 23:09:31 -0800 (PST)
	(envelope-from bbeck@mindmaker.com)
Received: (from root@localhost)
	by gateway.mindmaker.com (8.8.8/8.8.7) id XAA05291
	for <stable@freebsd.org>; Thu, 30 Mar 2000 23:09:19 -0800 (PST)
Received: from mail.int.mindmaker.com(192.168.10.10) by gateway.mindmaker.com via smap (V2.0)
	id xma005289; Thu, 30 Mar 00 23:09:09 -0800
Received: from mindmaker.com (auth.int.mindmaker.com [192.168.10.15])
	by mail.int.mindmaker.com (8.9.3/8.9.3) with ESMTP id XAA54164;
	Thu, 30 Mar 2000 23:03:17 -0800 (PST)
Message-ID: <38E44DD8.8BAAE0CE@mindmaker.com>
Date: Thu, 30 Mar 2000 23:03:52 -0800
From: Bernhard Beck <bbeck@mindmaker.com>
X-Mailer: Mozilla 4.6 [en] (Win95; U)
X-Accept-Language: en
MIME-Version: 1.0
To: stable@freebsd.org
Subject: trap 12 / kernel panic in ping with ep0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Not sure if this is the right mailing list. 

One of our test systems (TEST) is running 4.0-RELEASE with a custom
kernel (pretty much stock GENERIC kernel with IDE and most drivers
commented out in configuration). The system has a 3com 509 NIC.
Today we were stress-testing one of our web servers with ab and
http_load generating high network load from TEST. Eventually, TEST
stopped sending packets. I saw this same behaviour in earlier versions
of FreeBSD with 3com cards (2.2 and 3.2). Usually an ifconfig ep0 down
and ifconfig ep0 up was enough the revive the network layer. Not this
time.

I ran ping on TEST without responses. Got back to the command line,
started ping again and got a trap 12: kernel panic. I have all the panic
information written down if anyone is interested in that, but since this
is a custom build kernel I guess the address information won't help a
lot. 
The active process at the time of the panic was ping. 

Did anybody see a crash like this before in 4.0? 

Thanks,
Bernhard


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


From owner-freebsd-stable  Thu Mar 30 23:10:11 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from smtp10.nwnexus.com (smtp10.nwnexus.com [206.63.63.53])
	by hub.freebsd.org (Postfix) with ESMTP
	id 5FE2A37B594; Thu, 30 Mar 2000 23:10:03 -0800 (PST)
	(envelope-from wrsomsky@halcyon.com)
Received: from gramarye (evt-lx100-ip3.nwnexus.net [204.57.235.3])
	by smtp10.nwnexus.com (8.8.8/8.8.8) with ESMTP id XAA04263;
	Thu, 30 Mar 2000 23:09:54 -0800 (PST)
Received: (from wrsomsky@localhost)
	by gramarye (8.9.3/8.9.3) id WAA00406;
	Thu, 30 Mar 2000 22:37:11 -0800 (PST)
	(envelope-from wrsomsky)
Date: Thu, 30 Mar 2000 22:37:11 -0800
From: "William R. Somsky" <wrsomsky@halcyon.com>
To: Kris Kennaway <kris@FreeBSD.ORG>
Cc: robert bowen <robert@braingarage.com>, freebsd-stable@FreeBSD.ORG
Subject: Re: What else to remove after 4.0 upgrade
Message-ID: <20000330223711.A301@gramarye.halcyon.com>
References: <200003232221.OAA03748@smartie.braingarage.com> <Pine.BSF.4.21.0003231534310.33462-100000@freefall.freebsd.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0.1i
In-Reply-To: <Pine.BSF.4.21.0003231534310.33462-100000@freefall.freebsd.org>; from kris@FreeBSD.ORG on Thu, Mar 23, 2000 at 03:36:34PM -0800
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Thu, Mar 23, 2000 at 03:36:34PM -0800, Kris Kennaway wrote:
> On Thu, 23 Mar 2000, robert bowen wrote:
> 
> > Are there any binary files that have changed location or
> > gone away since 3.4-R? I saw the post on "cruft" but I
> > am worried that after a binary 4.0R upgrade there will
> > be some "leftovers" in /bin or /usr/bin that are not
> > overwritten by the new release (because they are not
> > included or changed in location)
> 
> find / -ctime +<#foo> -ls
> 
> where <#foo> is greater than the number of days since you installed 4.0-R
> but less than the time since your previous 3.4-R build.

I often do:

ref=/export/FreeBSD/$date ; mkdir -p $ref
echo -n " @@@@@ Reference start: " ; date "+%y-%m-%d %H:%M:%S"
(cd $src/etc  && make DESTDIR=$ref distrib-dirs distribution )
(cd $src/.    && make DESTDIR=$ref installworld)
echo -n " @@@@@ Reference done:  " ; date "+%y-%m-%d %H:%M:%S"

along w/ the normal "make installworld" so that I can compare
what I have in all my directories w/ the pristine version in $ref

I don't bother to check this each time I make world, but do across
major version changes, and occasionally across minor version changes.

________________________________________________________________________
William R. Somsky                                   wrsomsky@halcyon.com
Physicist, Baritone, Guitarist           http://www.halcyon.com/wrsomsky


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


From owner-freebsd-stable  Fri Mar 31  0:52:35 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from pooh.elsevier.nl (pooh.elsevier.nl [145.36.13.27])
	by hub.freebsd.org (Postfix) with ESMTP id B7F7A37B874
	for <freebsd-stable@freebsd.org>; Fri, 31 Mar 2000 00:52:29 -0800 (PST)
	(envelope-from steve@pooh.elsevier.nl)
Received: (from steve@localhost)
	by pooh.elsevier.nl (8.9.3/8.9.3) id VAA01610;
	Thu, 30 Mar 2000 21:47:05 +0100 (IST)
	(envelope-from steve)
Message-ID: <XFMail.000330214705.steveo@eircom.net>
X-Mailer: XFMail 1.4.0 on FreeBSD
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
Date: Thu, 30 Mar 2000 21:47:05 +0100 (IST)
From: "Steve O'Hara-Smith" <steveo@eircom.net>
To: Kiril Mitev <kiril@ideaglobal.com>
Subject: Stability and versions - was Re: Let 3.x die ASAP?
Cc: freebsd-stable@freebsd.org
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> On 30-Mar-00 Kiril Mitev wrote:
>> In other words "do not use anything newer than 2.2 if you 
>> worry about stability"...

   In other words "If 4-stable isn't stable enough for you try 3-stable, if
that isn't then try 2-stable". Noting that the original poster had done the
first two.

>> In other words "nothing in FreeBSD has improved stability
>> since 2.2"
> 

        That first reply of mine was a bit hasty (perhaps). So pehaps a view
from the edge is in order (perhaps not in which case my apologies). Maybe some
of this verbiage is suitable for a FAQ entry about what -stable means and what
to expect from various stages of a development cycle.

        It may very well be the case that 2.2-stable is currently the most
stable FreeBSD around, the main reason for this is that for quite some
time now it has been getting _only_ bug and security fixes (IIRC only the
latter for some time). It has also been in use for a long time so there has
been plenty of opportunity to diagnose and fix problems. By comparison 3-stable
is full of new(ish) features and support for newer hardware. It has been around
a while and may be approaching or even beating 2.2-stable in stability by now,
or it may never do so. It should reach it's peak of stability soon as it enters
the 'maintenance updates only' phase. 4-stable on the other hand is fresh from
the bleeding edge (via feature freeze, code freeze and beta test) and has only
just begun it's journey to (ultimate) stability.

        If you really want to compare the stability of 2.2-stable and 3-stable
you should either wait until 3-stable hits maintenance (after 3.5) or (maybe
bogus) compare 2.0, 2.1.0, 2.2.0, 3.0 and 4.0. FWIW 1.1.5.1 was I think the most
stable until well into the 2.1's but 2.2-stable leaves it standing on all
counts. It might be interesting to see how 1.1.5.1 fares on some of the quirkier
laptops around :)

        One of the great strengths of FreeBSD has always been the respect with
which the committers treat the -stable line. I cannot recall ever seeing an
X-stable going backwards in quality, discounting a very few really short lived
breakages only visible to those who cvsup at the wrong time (and readers of
this list who get told about it - a lot).

        It is also worth considering that stability is a variable thing. A
system that is rock solid under one pattern of loading may start to fail badly
when called upon to do something new that exposes an untriggered bug or hits a
previously unnoticed limit. Consider that all those who had stability 
problems under 2.2-stable have long since stopped running 2.2-stable on that
hardware (they may be running 3.x or 4.x or Linux or NT or new hardware or
...). The remaining 2.2-stable systems are running on hardware that is proven
to be a good match to the OS.

        Finally if 3-stable or 4-stable crashes on hardware that ran 2-stable
for years consider that the hardware and firmware is very old and the newer code
hasn't had much testing against hardware and firmware that old some of which
may have unexpected quirks not affecting the older code. Not so much a
stability problem as a compatability problem or even a new intolerance to off
spec hardware/firmware problem. It may also be a bug in the newer code.

PS: I am just a user, my opinions have only their own weight to carry them.
PPS: Personally I find 4-stable to be quite stable enough for my needs.
     Thanks and well done to all concerned. (keep doing it).



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


From owner-freebsd-stable  Fri Mar 31  1:36:11 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from ipamzlx.physik.uni-mainz.de (ipamzlx.Physik.Uni-Mainz.DE [134.93.180.54])
	by hub.freebsd.org (Postfix) with ESMTP
	id 415BE37BAD5; Fri, 31 Mar 2000 01:36:00 -0800 (PST)
	(envelope-from ohartman@ipamzlx.physik.uni-mainz.de)
Received: from ipamzlx.Physik.Uni-Mainz.DE (ipamzlx.Physik.Uni-Mainz.DE [134.93.180.54])
	by ipamzlx.physik.uni-mainz.de (8.9.3/8.9.3) with ESMTP id LAA19608;
	Fri, 31 Mar 2000 11:36:01 +0200 (CEST)
	(envelope-from ohartman@ipamzlx.physik.uni-mainz.de)
Date: Fri, 31 Mar 2000 11:36:01 +0200 (CEST)
From: "O. Hartmann" <ohartman@ipamzlx.physik.uni-mainz.de>
To: freebsd-smp@freebsd.org
Cc: freebsd-stable@freebsd.org
Subject: SMP Pproblems ALR Revolution Q-SMP
Message-ID: <Pine.BSF.4.10.10003311058280.16977-100000@ipamzlx.physik.uni-mainz.de>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Well, the show goes on :-(

Today I tried again to bring up an older Siemens/Nixdorf PCE-5Smp
aka ALR Revolution Q-SMP.

Here waht I did:
first upgraded to the newest available BIOS (4.04.6) -> effect: mptable
can have a look on what's in the machine (failed before).

Machine has three CPU boards, P100 with each board's own Cache (MESI)
controler. 

After BIOS update mptables exposes this output:

MPTable, version 2.0.15

 looking for EBDA pointer @ 0x040e, found, searching EBDA @ 0x0009f000

 MP FPS found in Extended BIOS Data Area @ physical addr: 0x0009f0a0

-------------------------------------------------------------------------------

MP Floating Pointer Structure:

  location:                     EBDA
  physical address:             0x0009f0a0
  signature:                    '_MP_'
  length:                       16 bytes
  version:                      1.1
  checksum:                     0x75
  mode:                         PIC

-------------------------------------------------------------------------------

MP Config Table Header:

  physical address:             0x0009f0b5
  signature:                    'PCMP'
  base table length:            256
  version:                      1.1
  checksum:                     0x60
  OEM ID:                       'ALR     '
  Product ID:                   'Revolut QSMP'
  OEM table pointer:            0x00000000
  OEM table size:               0
  entry count:                  22
  local APIC address:           0xfee00000
  extended table length:        0
  extended table checksum:      0

-------------------------------------------------------------------------------

MP Config Base Table Entries:

--
Processors:     APIC ID Version State           Family  Model   Step    Flags
                 0       0x 1    BSP, usable     5       2       5       0x0181
                 1       0x 1    AP, usable      5       2       5       0x0181
                 2       0x 1    AP, usable      5       2       5       0x0181
--
Bus:            Bus ID  Type
                 0       EISA
                 1       PCI
--
I/O APICs:      APIC ID Version State           Address
                 3       0x01    usable          0xfec00000
--
I/O Ints:       Type    Polarity    Trigger     Bus ID   IRQ    APIC ID PIN#
                ExtINT   conforms    conforms        0     0          3    0
                INT      conforms    conforms        0     1          3    1
                INT      conforms    conforms        0     3          3    3
                INT      conforms    conforms        0     4          3    4
                INT      conforms    conforms        0     5          3    5
                INT      conforms    conforms        0     6          3    6
                INT      conforms    conforms        0     7          3    7
                INT      conforms    conforms        0     8          3    8
                INT      conforms    conforms        0     9          3    9
                INT      conforms    conforms        0    10          3   10
                INT      conforms    conforms        0    11          3   11
                INT      conforms    conforms        0    12          3   12
                INT      conforms    conforms        0    14          3   14
                INT      conforms    conforms        0    15          3   15
--
Local Ints:     Type    Polarity    Trigger     Bus ID   IRQ    APIC ID PIN#
                ExtINT   conforms    conforms        0     0        255    0
                NMI      conforms    conforms        0     0        255    1

-------------------------------------------------------------------------------

# SMP kernel config file options:


# Required:
options         SMP                     # Symmetric MultiProcessor Kernel
options         APIC_IO                 # Symmetric (APIC) I/O

# Optional (built-in defaults will work in most cases):
#options                NCPU=3                  # number of CPUs
#options                NBUS=2                  # number of busses
#options                NAPIC=1                 # number of IO APICs
#options                NINTR=24                # number of INTs

===============================================================================

I applyed the suggested kernel config options, once with and once without the 
optional, commented out options.

When booting the machine with SMP kernel, I get first the message:

Warning, using 2 out of 3 CPUs. It seems, that one CPU can notbe used, maybe due the
fact of the odd number of processors. But either 2 or 3 CPUs, it doesn't matter the effect is always
the same. After loading the kernel, I get the message about the available memory, then
some messages about programming APIC pin 0 on IRQ 16 or similar, then EISAINTCONTROL  0000c200.
After this message I get the message: AP# 1 (PHY# 1): failed. panic? (y/n):
When typing 'n' booting goes on up to a stage, when some IO devices, like SIO or parallel port,
should be initialized. Then the machine freezes.

I tried some othe combinations with the interrupts (16 instead of 24 as suggested by 
mptabel), but I have not played yet with all possible combinations. 

Well, I personally accuse the EISA configuration for this failure, but
I'm not an expert. Has anybody any idea or suggestion what to do? I would
appreciate any hint or tip, thanks!



===============================================================================
Kind regards

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

Klimadatenserver des IPA, Universitaet Mainz
Netzwerk- und Systembetreuung



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


From owner-freebsd-stable  Fri Mar 31  1:47:23 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from axl.ops.uunet.co.za (axl.ops.uunet.co.za [196.31.1.175])
	by hub.freebsd.org (Postfix) with ESMTP id 3E93037B50C
	for <freebsd-stable@freebsd.org>; Fri, 31 Mar 2000 01:47:19 -0800 (PST)
	(envelope-from sheldonh@axl.ops.uunet.co.za)
Received: from sheldonh (helo=axl.ops.uunet.co.za)
	by axl.ops.uunet.co.za with local-esmtp (Exim 3.13 #1)
	id 12ay1M-000Mjf-00
	for freebsd-stable@FreeBSD.ORG; Fri, 31 Mar 2000 11:47:16 +0200
From: Sheldon Hearn <sheldonh@uunet.co.za>
To: freebsd-stable@FreeBSD.ORG
Subject: Re: Let 3.x die ASAP? 
Date: Fri, 31 Mar 2000 11:47:16 +0200
Message-ID: <87398.954496036@axl.ops.uunet.co.za>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


I think it's safe to say that nothing useful has come out of this thread
in the last 15 posts.

Ciao,
Sheldon.


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


From owner-freebsd-stable  Fri Mar 31  2:53: 6 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from morpheus.skynet.be (morpheus.skynet.be [195.238.2.39])
	by hub.freebsd.org (Postfix) with ESMTP
	id 32B5037B661; Fri, 31 Mar 2000 02:53:04 -0800 (PST)
	(envelope-from blk@skynet.be)
Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121])
	by morpheus.skynet.be (Postfix) with ESMTP
	id 4D531DBDF; Fri, 31 Mar 2000 12:53:02 +0200 (MET DST)
Mime-Version: 1.0
X-Sender: blk@pop.skynet.be
Message-Id: <v04220803b50a2c090fe1@[195.238.1.121]>
In-Reply-To:
 <Pine.BSF.4.21.0003301524490.49247-100000@freefall.freebsd.org>
References:
 <Pine.BSF.4.21.0003301524490.49247-100000@freefall.freebsd.org>
Date: Fri, 31 Mar 2000 12:21:04 +0200
To: Kris Kennaway <kris@FreeBSD.ORG>
From: Brad Knowles <blk@skynet.be>
Subject: Re: please help - thread-safe mysql client link problem
Cc: Siew Sim <siewsim@prismedia.com>,
	FreeBSD-STABLE Mailing List <freebsd-stable@freebsd.org>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

At 3:25 PM -0800 on 2000/3/30, Kris Kennaway wrote:

>>      I'm using FreeBSD 3.2, and mysql 3.22.30.  I'm trying to build a
>>  thread-safe mysql client with pthread.
>
>  Use the port.

	The last time I tried that, I had a problem in that the port was 
looking for a version of the package that no longer existed on the 
ftp servers, so I was forced to do the whole thing manually.

	Do you know for sure that the current version of the port uses a 
sufficiently recent version of the MySQL package, so that it can be 
found on the ftp servers?  Does it use the latest version of the 
MySQL package, and if not how many revisions back is it, and have 
there been any significant enhancements in the time since?

--
   These are my opinions -- not to be taken as official Skynet policy
======================================================================
Brad Knowles, <blk@skynet.be>                || Belgacom Skynet SA/NV
Systems Architect, Mail/News/FTP/Proxy Admin || Rue Colonel Bourg, 124
Phone/Fax: +32-2-706.13.11/12.49             || B-1140 Brussels
http://www.skynet.be                         || Belgium


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


From owner-freebsd-stable  Fri Mar 31  2:55:21 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
	by hub.freebsd.org (Postfix) with ESMTP
	id 3713E37B661; Fri, 31 Mar 2000 02:55:19 -0800 (PST)
	(envelope-from kris@FreeBSD.org)
Received: from localhost (kris@localhost)
	by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id CAA04471;
	Fri, 31 Mar 2000 02:55:18 -0800 (PST)
	(envelope-from kris@FreeBSD.org)
X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs
Date: Fri, 31 Mar 2000 02:55:18 -0800 (PST)
From: Kris Kennaway <kris@FreeBSD.org>
To: Brad Knowles <blk@skynet.be>
Cc: Siew Sim <siewsim@prismedia.com>,
	FreeBSD-STABLE Mailing List <freebsd-stable@freebsd.org>
Subject: Re: please help - thread-safe mysql client link problem
In-Reply-To: <v04220803b50a2c090fe1@[195.238.1.121]>
Message-ID: <Pine.BSF.4.21.0003310253580.95920-100000@freefall.freebsd.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Fri, 31 Mar 2000, Brad Knowles wrote:

> 	Do you know for sure that the current version of the port uses a 
> sufficiently recent version of the MySQL package, so that it can be 
> found on the ftp servers?  Does it use the latest version of the 
> MySQL package, and if not how many revisions back is it, and have 
> there been any significant enhancements in the time since?

I know it was upgraded in the last month or so because of the security
advisory I wrote about it..probably the previous version was pulled for
the same reason. If it's out of date again you need to contact the
maintainer instead of going your own way :-)

Kris

----
In God we Trust -- all others must submit an X.509 certificate.
    -- Charles Forsythe <forsythe@alum.mit.edu>



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


From owner-freebsd-stable  Fri Mar 31  4:26:59 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from relay.ipf.net (relay.gigabell.net [195.211.211.23])
	by hub.freebsd.org (Postfix) with SMTP id 35F4E37B938
	for <freebsd-stable@freebsd.org>; Fri, 31 Mar 2000 04:26:53 -0800 (PST)
	(envelope-from koellmann@gmx.net)
Received: (qmail 29720 invoked from network); 31 Mar 2000 12:26:49 -0000
Received: from dialin-194-29-33-5.hamburg.gigabell.net (HELO server.home.net) (194.29.33.5)
  by relay.gigabell.net with SMTP; 31 Mar 2000 12:26:49 -0000
Received: (qmail 17878 invoked from network); 31 Mar 2000 12:24:27 -0000
Received: from desk.home.net (192.168.1.2)
  by server.home.net with SMTP; 31 Mar 2000 12:24:27 -0000
Received: by desk.home.net (Postfix, from userid 1002)
	id 8588F934BD; Fri, 31 Mar 2000 14:23:57 +0200 (CEST)
Date: Fri, 31 Mar 2000 14:23:57 +0200
From: =?iso-8859-1?Q?Thomas_K=F6llmann?= <koellmann@gmx.net>
To: Grigoriy Strokin <grg@philol.msu.ru>
Cc: freebsd-stable@freebsd.org
Subject: Re: New kernel with its ATA drivers damages the filesystem
Message-ID: <20000331142357.A1291@home.net>
References: <20000331022130.A4045@isabase.philol.msu.ru>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Mailer: Mutt 1.0.1i
In-Reply-To: <20000331022130.A4045@isabase.philol.msu.ru>; from grg@philol.msu.ru on Fri, Mar 31, 2000 at 02:21:30AM +0400
X-Operating-System: FreeBSD 4.0-STABLE
X-Uptime: 2:17pm  up  4:13, 2 users, load averages: 1.41, 1.35, 1.21
X-PGP-KeyID: 8C45AC01
X-PGP-Fingerprint: C5 F0 DE B2 AD 70 B9 45  B0 F9 0C D3 58 19 48 C8
Organization: =?iso-8859-1?Q?Hamburger_Gesellschaft_mit_beschr=E4nkter_Hoffnung?=
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Grigoriy Strokin wrote/schrieb (Friday, March 31, 2000):

| While the bug wiping out filesystems on machines with Apollo MVP3 when ATA
| driver is in UDMA mode is being fixed, I suppose there at least should be some
| note added to /usr/src/UPDATING, so that another users do not loss
| all their data and have to reinitialize /usr and restore it from backup, as I
| had to do?
| 
| Something like that:
| 
|     If you use the Apollo MVP3 chipset, it is STRONGLY
|     recommended that you disable the use of DMA mode in ATA drivers
|     BEFORE you try to boot the system after `make installkernel'.
|     Add the following line:
|       /sbin/sysctl -w hw.atamodes=pio,pio,pio,pio
|     to the very beginning of your /etc/rc,
|     ~root/.profile and ~root/.login.
|     Be warned that if you don't disable the DMA mode,
|     all your filesystems may be corrupted because
|     of a bug in the driver that is still being fixed.
| 

Please excuse if this was mentioned before (I did not follow this
thread very closely), but isn't _not_ using

	options		ATA_ENABLE_ATAPI_DMA

enough as a measure of precaution?

This is from LINT:

# ATA_ENABLE_ATAPI_DMA: enable DMA on ATAPI device, since many ATAPI
# devices claim to support DMA but doesn't actually work, this is
# not enabled as default.

Gruß
 - Thomas

-- 
I looked in the store windows and there was nothing in the store
windows that I wanted at all.
 - Charles Bukowski, A Rain of Women
# PGP key sent on request / PGP key auf Wunsch per e-mail


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


From owner-freebsd-stable  Fri Mar 31  4:35:25 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from mail0.bna.bellsouth.net (mail0.bna.bellsouth.net [205.152.150.12])
	by hub.freebsd.org (Postfix) with ESMTP id 05F3D37BF8A
	for <freebsd-stable@FreeBSD.ORG>; Fri, 31 Mar 2000 04:35:22 -0800 (PST)
	(envelope-from jim@siteplus.net)
Received: from discover.siteplus.net (host-216-78-83-29.cha.bellsouth.net [216.78.83.29])
	by mail0.bna.bellsouth.net (3.3.5alt/0.75.2) with ESMTP id HAA25916
	for <freebsd-stable@FreeBSD.ORG>; Fri, 31 Mar 2000 07:34:19 -0500 (EST)
Date: Fri, 31 Mar 2000 07:35:21 -0500 (EST)
From: Jim Weeks <jim@siteplus.net>
To: freebsd-stable@FreeBSD.ORG
Subject: Re: Let 3.x die ASAP? 
In-Reply-To: <87398.954496036@axl.ops.uunet.co.za>
Message-ID: <Pine.BSF.4.21.0003310733160.18903-100000@discover.siteplus.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

I think I may have to write a mail filter for this one!

On Fri, 31 Mar 2000, Sheldon Hearn wrote:

> 
> I think it's safe to say that nothing useful has come out of this thread
> in the last 15 posts.
> 
> Ciao,
> Sheldon.



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


From owner-freebsd-stable  Fri Mar 31  4:57:30 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from isabase.philol.msu.ru (isabase.philol.msu.ru [195.208.217.73])
	by hub.freebsd.org (Postfix) with ESMTP id 9375637B81E
	for <freebsd-stable@freebsd.org>; Fri, 31 Mar 2000 04:57:15 -0800 (PST)
	(envelope-from grg@isabase.philol.msu.ru)
Received: (from grg@localhost)
	by isabase.philol.msu.ru (8.9.3/8.9.2) id QAA20029;
	Fri, 31 Mar 2000 16:54:22 +0400 (MSD)
	(envelope-from grg)
Date: Fri, 31 Mar 2000 16:54:22 +0400
From: Grigoriy Strokin <grg@philol.msu.ru>
To: Thomas K?llmann <koellmann@gmx.net>
Cc: freebsd-stable@freebsd.org
Subject: Re: New kernel with its ATA drivers damages the filesystem
Message-ID: <20000331165422.A19782@isabase.philol.msu.ru>
References: <20000331022130.A4045@isabase.philol.msu.ru> <20000331142357.A1291@home.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0.1i
In-Reply-To: <20000331142357.A1291@home.net>; from koellmann@gmx.net on Fri, Mar 31, 2000 at 02:23:57PM +0200
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Fri, Mar 31, 2000 at 02:23:57PM +0200, Thomas K?llmann wrote:
> Grigoriy Strokin wrote/schrieb (Friday, March 31, 2000):
> 
> | While the bug wiping out filesystems on machines with Apollo MVP3 when ATA
> | driver is in UDMA mode is being fixed, I suppose there at least should be some
> | note added to /usr/src/UPDATING, so that another users do not loss
> | all their data and have to reinitialize /usr and restore it from backup, as I
> | had to do?
> | 
> | Something like that:
> | 
> |     If you use the Apollo MVP3 chipset, it is STRONGLY
> |     recommended that you disable the use of DMA mode in ATA drivers
> |     BEFORE you try to boot the system after `make installkernel'.
> |     Add the following line:
> |       /sbin/sysctl -w hw.atamodes=pio,pio,pio,pio
> |     to the very beginning of your /etc/rc,
> |     ~root/.profile and ~root/.login.
> |     Be warned that if you don't disable the DMA mode,
> |     all your filesystems may be corrupted because
> |     of a bug in the driver that is still being fixed.
> | 
> 
> Please excuse if this was mentioned before (I did not follow this
> thread very closely), but isn't _not_ using
> 
> 	options		ATA_ENABLE_ATAPI_DMA
> 
> enough as a measure of precaution?
> 
> This is from LINT:
> 
> # ATA_ENABLE_ATAPI_DMA: enable DMA on ATAPI device, since many ATAPI
> # devices claim to support DMA but doesn't actually work, this is
> # not enabled as default.

Unfortunately, no.
I don't know whether this option affect anything,
because I was using the GENERIC kernel
in which this option is commented out, and nevertheless
dmesg reports using UDMA-33, and 
       $ sysctl hw.atamodes
       hw.atamodes: dma,---,dma,---,
So, the *default* GENERIC kernel could corrupt the disk 
as ever it is being booted for the first time.


-- 
=== Grigoriy Strokin, Lomonosov University (MGU), Moscow ===
=== contact info: http://isabase.philol.msu.ru/~grg/     ===


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


From owner-freebsd-stable  Fri Mar 31  5: 6:21 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from mail.hcisp.net (Stargate.hcisp.net [208.60.89.18])
	by hub.freebsd.org (Postfix) with SMTP id 5EF3C37B6FD
	for <freebsd-stable@FreeBSD.ORG>; Fri, 31 Mar 2000 05:06:17 -0800 (PST)
	(envelope-from tim@mysql.com)
Received: (qmail 17817 invoked from network); 31 Mar 2000 13:12:22 -0000
Received: from modem7.hcisp.net (HELO threads.polyesthetic.msg) (208.60.89.73)
  by stargate.hcisp.net with SMTP; 31 Mar 2000 13:12:22 -0000
Received: (qmail 62429 invoked by uid 1001); 31 Mar 2000 13:03:52 -0000
From: "Thimble Smith" <tim@mysql.com>
Date: Fri, 31 Mar 2000 08:03:52 -0500
To: Kris Kennaway <kris@FreeBSD.ORG>
Cc: Siew Sim <siewsim@prismedia.com>, freebsd-stable@FreeBSD.ORG
Subject: Re: please help - thread-safe mysql client link problem
Message-ID: <20000331080352.G76293@threads.polyesthetic.msg>
References: <38E3833D.A57695F0@prismedia.com> <Pine.BSF.4.21.0003301524490.49247-100000@freefall.freebsd.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0.1i
In-Reply-To: <Pine.BSF.4.21.0003301524490.49247-100000@freefall.freebsd.org>; from kris@FreeBSD.ORG on Thu, Mar 30, 2000 at 03:25:35PM -0800
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Thu, Mar 30, 2000 at 03:25:35PM -0800, Kris Kennaway wrote:
>On Thu, 30 Mar 2000, Siew Sim wrote:
>>     I'm using FreeBSD 3.2, and mysql 3.22.30.  I'm trying to build a
>> thread-safe mysql client with pthread.
>
>Use the port.

The port doesn't have an option for building a thread-safe client,
either (unless it's hidden somewhere that I didn't see it).

Siew Sim, those error messages usually happen when something was
compiled with -lc_r instead of with -pthread.  MySQL's configure
script detects -lc_r and it won't use -pthread by default, so I
am guessing that's where your problem is.

Until that is fixed in MySQL, add this option when you configure:

    --with-mysqld-ldflags=-pthread --with-client-ldflags=-pthread

    $ gmake -k clean; rm config.cache
    $ configure --options
    $ gmake

Let me know if that doesn't solve the problem.

Tim


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


From owner-freebsd-stable  Fri Mar 31  5:52:45 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from sabre.velocet.net (sabre.velocet.net [198.96.118.66])
	by hub.freebsd.org (Postfix) with ESMTP id 8F63937B919
	for <freebsd-stable@freebsd.org>; Fri, 31 Mar 2000 05:52:42 -0800 (PST)
	(envelope-from dgilbert@office.tor.velocet.net)
Received: from office.tor.velocet.net (trooper.velocet.net [216.126.82.226])
	by sabre.velocet.net (Postfix) with ESMTP id A3B88137FDA
	for <freebsd-stable@freebsd.org>; Fri, 31 Mar 2000 08:52:40 -0500 (EST)
Received: (from dgilbert@localhost)
	by office.tor.velocet.net (8.9.3/8.9.3) id IAA33568;
	Fri, 31 Mar 2000 08:52:40 -0500 (EST)
	(envelope-from dgilbert)
From: David Gilbert <dgilbert@velocet.ca>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <14564.44455.794698.35833@trooper.velocet.net>
Date: Fri, 31 Mar 2000 08:52:39 -0500 (EST)
To: freebsd-stable@freebsd.org
Subject: disklabel fails.
X-Mailer: VM 6.75 under 20.4 "Emerald" XEmacs  Lucid
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

I've had two curious disklabel adventures lately.  In both cases,
there was absolutely no way to convince the disk to label.

In the first, I was using fdisk/disklabel on the command line and then 
/stand/sysinstall (out of frustration) on an already installed machine 
with SCSI disks.  The disks probed fine, and the machine is a new
K7/550.  I don't have the motherboard name in front of me, but it's
using the TekRAM 390-F SCSI controller.

When I took the disk to another machine (which had an adaptec 2940
controller) it labelled just fine.

Similarly, I have a new PC-100 System board...  It refuses to let me
label _any_ drive during the standard install with 4.0-RELEASE.  If I
take any of these drives to an old pentium-200 motherboard, they all
install just fine.

The first error I get in the install is the installer claiming that it 
can't swap to ad0s1b.  Other errors follow.

What's up with disklabel?

Dave.

-- 
============================================================================
|David Gilbert, Velocet Communications.       | Two things can only be     |
|Mail:       dgilbert@velocet.net             |  equal if and only if they |
|http://www.velocet.net/~dgilbert             |   are precisely opposite.  |
=========================================================GLO================


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


From owner-freebsd-stable  Fri Mar 31  6:31:50 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from probity.mcc.ac.uk (probity.mcc.ac.uk [130.88.200.94])
	by hub.freebsd.org (Postfix) with ESMTP id 2B5C837B69E
	for <freebsd-stable@freebsd.org>; Fri, 31 Mar 2000 06:31:41 -0800 (PST)
	(envelope-from jcm@dogma.freebsd-uk.eu.org)
Received: from dogma.freebsd-uk.eu.org ([130.88.200.97])
	by probity.mcc.ac.uk with esmtp (Exim 1.92 #3)
	id 12b2SY-0003b3-00; Fri, 31 Mar 2000 15:31:38 +0100
Received: (from jcm@localhost)
	by dogma.freebsd-uk.eu.org (8.9.3/8.9.3) id PAA21804;
	Fri, 31 Mar 2000 15:31:38 +0100 (BST)
	(envelope-from jcm)
Date: Fri, 31 Mar 2000 15:31:37 +0100
From: J McKitrick <jcm@freebsd-uk.eu.org>
To: "Steve O'Hara-Smith" <steveo@eircom.net>
Cc: Kiril Mitev <kiril@ideaglobal.com>, freebsd-stable@freebsd.org
Subject: Re: Stability and versions - was Re: Let 3.x die ASAP?
Message-ID: <20000331153137.C21703@dogma.freebsd-uk.eu.org>
References: <XFMail.000330214705.steveo@eircom.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0.1i
In-Reply-To: <XFMail.000330214705.steveo@eircom.net>; from steveo@eircom.net on Thu, Mar 30, 2000 at 09:47:05PM +0100
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

I think the only thing that needs inserted in the handbook (if it
isn;t there already, i haven't checked) is something that has been
said before:

"STABLE" refers to the code base, NOT the stability of systems running
it.

Simple concept, deep meaning.  Newbies should understand (as is
clearly stated in the handbook) that -current is not a new toy or a
whizbang version with all the newest gadgets.  And they,as well as
intermediate users, should understand that -stable means all the
features that will be included in this branch are done, and now are
being debugged and maintained (post-beta bugs, of course).

jm
-- 
--------------------------------------------
Jonathon McKitrick -- jcm@freebsd-uk.eu.org 
Pure... unrefined... spice....
--------------------------------------------


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


From owner-freebsd-stable  Fri Mar 31  7: 4:19 2000
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 8AF5A37B6B2
	for <freebsd-stable@FreeBSD.ORG>; Fri, 31 Mar 2000 07:04:15 -0800 (PST)
	(envelope-from Cy.Schubert@uumail.gov.bc.ca)
Received: (from daemon@localhost)
	by point.osg.gov.bc.ca (8.8.7/8.8.8) id GAA31125;
	Fri, 31 Mar 2000 06:58:48 -0800
Received: from passer.osg.gov.bc.ca(142.32.110.29)
 via SMTP by point.osg.gov.bc.ca, id smtpda31123; Fri Mar 31 06:58:48 2000
Received: (from uucp@localhost)
	by passer.osg.gov.bc.ca (8.9.3/8.9.1) id GAA34464;
	Fri, 31 Mar 2000 06:58:43 -0800 (PST)
Received: from cwsys9.cwsent.com(10.2.2.1), claiming to be "cwsys.cwsent.com"
 via SMTP by passer9.cwsent.com, id smtpdq34462; Fri Mar 31 06:58:35 2000
Received: (from uucp@localhost)
	by cwsys.cwsent.com (8.9.3/8.9.1) id GAA27848;
	Fri, 31 Mar 2000 06:58:33 -0800 (PST)
Message-Id: <200003311458.GAA27848@cwsys.cwsent.com>
Received: from localhost.cwsent.com(127.0.0.1), claiming to be "cwsys"
 via SMTP by localhost.cwsent.com, id smtpdy27844; Fri Mar 31 06:58:16 2000
X-Mailer: exmh version 2.1.1 10/15/1999
Reply-To: Cy Schubert - ITSD Open Systems Group <Cy.Schubert@uumail.gov.bc.ca>
From: Cy Schubert - ITSD Open Systems Group <Cy.Schubert@uumail.gov.bc.ca>
X-OS: FreeBSD 3.4-RELEASE
X-Sender: cy
To: didier@omnix.net
Cc: chad@DCFinc.com, Kiril Mitev <kiril@ideaglobal.com>,
	jkh@zippy.cdrom.com, cracauer@cons.org, freebsd-stable@FreeBSD.ORG
Subject: Re: Let 3.x die ASAP? 
In-reply-to: Your message of "Thu, 30 Mar 2000 16:25:18 GMT."
             <200003301625.QAA76045@loki.ideaglobal.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 31 Mar 2000 06:58:15 -0800
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

In message <200003301625.QAA76045@loki.ideaglobal.com>, Kiril Mitev 
writes:
> > As I recall, Didier Derny wrote:
> > > I can't an many people can't upgrade the system on their machine
> > > at the actual rythm of FreeBSD version (each one supposed to be the best
> > > one and solve most of the problems :-))) )
> > > without a real stability (like the one with 2.x) this product
> > > has no more value than linux or solaris, sco...
> > 
> > So, is there some feature in the 3.x line that isn't in 2.2.x that
> > you can't live without?  If not, your course is clear.  Put up a
> > 2.2-STABLE system and quit worrying about stability.
> 
> *ahem*
> 
> In other words "do not use anything newer than 2.2 if you 
> worry about stability"...
> 
> In other words "nothing in FreeBSD has improved stability
> since 2.2"
> 
> In other words "2.2 is our most stable version"
> 
> (ever?)
> 
> In other words ..... you get the drift .......
> 
> OUCH
> 
> *off to downgrade all those servers ASAP*
> 
> *oh, and replace them with 486's, after all 486's with
> 2.2 on them have years of uptime*

I think that 2.1.6 was more stable than any 2.2.x and that 3.4 is the 
most stable of them all (haven't used 4.0 extensively so I won't 
comment about it).  IMO he's got a choice:  Upgrade to 3.4 or downgrade 
to 2.1.6.

My point is that if a certain release works for an individual.  Stick 
with it and quit bitching.  I'm sure there are a lot of very happy 
users of 2.0.5, 2.1.[67], and 2.2.8 who are doing just that:  Using an 
old release because it works and not bitching about it.

I for one, rather than bitching and complaining, have rolled up my 
sleeves and submitted patches to fix problems I've had.  Eventually 
somebody either committed them in my original form or as usually was 
the case in a modified form.

FreeBSD is not a commercial effort.  It's a free-ware effort.  All the 
arm-chair quarterbacks have no right to complain until they've either 
contributed to the effort or paid FreeBSD for support.


Regards,                       Phone:  (250)387-8437
Cy Schubert                      Fax:  (250)387-5766
Team Leader, Sun/DEC Team   Internet:  Cy.Schubert@osg.gov.bc.ca
Open Systems Group, ITSD, ISTA
Province of BC





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


From owner-freebsd-stable  Fri Mar 31  7:27:34 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from kci.kciLink.com (kci.kciLink.com [204.117.82.1])
	by hub.freebsd.org (Postfix) with ESMTP id BFF9737B652
	for <freebsd-stable@freebsd.org>; Fri, 31 Mar 2000 07:27:28 -0800 (PST)
	(envelope-from khera@kciLink.com)
Received: from onceler.kcilink.com (onceler.kciLink.com [204.117.82.2])
	by kci.kciLink.com (Postfix) with ESMTP id 256E0E896
	for <freebsd-stable@freebsd.org>; Fri, 31 Mar 2000 10:27:26 -0500 (EST)
Received: (from khera@localhost)
	by onceler.kcilink.com (8.9.3/8.9.3) id KAA65300;
	Fri, 31 Mar 2000 10:27:26 -0500 (EST)
	(envelope-from khera@kci.kcilink.com)
From: Vivek Khera <khera@kciLink.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <14564.50142.22563.853112@onceler.kcilink.com>
Date: Fri, 31 Mar 2000 10:27:26 -0500 (EST)
To: freebsd-stable@freebsd.org
Subject: Re: 3.4-RELEASE; panic while paging
In-Reply-To: <20000330200422.B16409@dogma.freebsd-uk.eu.org>
References: <20000329175018.V15889@TK147108.telekabel.at>
	<20000329195354.A40356@walton.maths.tcd.ie>
	<20000330205606.B15889@TK147108.telekabel.at>
	<20000330200422.B16409@dogma.freebsd-uk.eu.org>
X-Mailer: VM 6.72 under 21.1 (patch 8) "Bryce Canyon" XEmacs Lucid
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

>>>>> "JM" == J McKitrick <jcm@freebsd-uk.eu.org> writes:

JM> Just general question about these types of hardware problems.  Do they
JM> occur often under NT or windows as well?  Or does FreeBSD just seem to
JM> push hardware to its limits more?

I have one box that runs BSD/OS for about a week, then starts killing
random processes for no reason.  It runs Windoze NT for about 10
minutes (of interactive use) before it totally locks up.  It has been
running RH Linux for about a year without a hiccup.  I have not tried
FreeBSD on it.  Every major part in that box has been swapped out
except the case.

Who knows what is causing the problems...  PC hardware is just that
way it seems.  If I get a flaky box, my new rule is that if a memory
exchange doesn't fix it, I get a new box.

-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Vivek Khera, Ph.D.                Khera Communications, Inc.
Internet: khera@kciLink.com       Rockville, MD       +1-301-545-6996
PGP & MIME spoken here            http://www.kciLink.com/home/khera/


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


From owner-freebsd-stable  Fri Mar 31  7:55:56 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from mail.rdc1.il.home.com (ha1.rdc1.il.home.com [24.2.1.66])
	by hub.freebsd.org (Postfix) with ESMTP id 7AEFF37B682
	for <freebsd-stable@freebsd.org>; Fri, 31 Mar 2000 07:55:53 -0800 (PST)
	(envelope-from stephen@math.missouri.edu)
Received: from math.missouri.edu ([24.12.197.197]) by mail.rdc1.il.home.com
          (InterMail v4.01.01.00 201-229-111) with ESMTP
          id <20000331155552.FJNW4993.mail.rdc1.il.home.com@math.missouri.edu>
          for <freebsd-stable@freebsd.org>; Fri, 31 Mar 2000 07:55:52 -0800
Message-ID: <38E4CACD.177A6202@math.missouri.edu>
Date: Fri, 31 Mar 2000 09:57:01 -0600
From: Stephen Montgomery-Smith <stephen@math.missouri.edu>
X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.12 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: freebsd-stable <freebsd-stable@freebsd.org>
Subject: What is needed in /stand
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Now I have upgraded to FreeBSD 4.0, I am finding that I am
getting less and less room in the root mount point / .
(I gave it 32M).

I was looking through / to see what is not needed, and I see
a bunch of old files in /stand.  What is needed and what can
I delete?

# cd /stand
# ls -l
total 22373
-r-xr-xr-x  18 root  wheel  1219512 Oct 17  1998 -sh
-r-xr-xr-x  18 root  wheel  1219512 Oct 17  1998 bad144
-rw-r--r--   1 root  wheel     1030 Oct 17  1998 boot.help
-r-xr-xr-x  18 root  wheel  1219512 Oct 17  1998 boot_crunch
-r-xr-xr-x  18 root  wheel  1219512 Oct 17  1998 cpio
drwx------   2 root  wheel      512 Nov 18  1998 etc
-r-xr-xr-x  18 root  wheel  1219512 Oct 17  1998 find
-r-xr-xr-x  18 root  wheel  1219512 Oct 17  1998 fsck
-r-xr-xr-x  18 root  wheel  1219512 Oct 17  1998 gunzip
-r-xr-xr-x  18 root  wheel  1219512 Oct 17  1998 gzip
drwxr-xr-x   2 root  wheel     1024 Nov 18  1998 help
-r-xr-xr-x  18 root  wheel  1219512 Oct 17  1998 ifconfig
-r-xr-xr-x  18 root  wheel  1219512 Oct 17  1998 minigzip
-r-xr-xr-x  18 root  wheel  1219512 Oct 17  1998 mount_nfs
-r-xr-xr-x  18 root  wheel  1219512 Oct 17  1998 newfs
-r-xr-xr-x  18 root  wheel  1219512 Oct 17  1998 ppp
-r-xr-xr-x  18 root  wheel  1219512 Oct 17  1998 pwd
-r-xr-xr-x  18 root  wheel  1219512 Oct 17  1998 route
-r-xr-xr-x  18 root  wheel  1219512 Oct 17  1998 sh
-r-xr-xr-x  18 root  wheel  1219512 Oct 17  1998 slattach
-rw-r--r--   1 root  wheel      355 Oct 17  1998 symbols
-r-xr-xr-x   1 root  wheel   770116 Mar 31 01:15 sysinstall
-r-xr-xr-x  18 root  wheel  1219512 Oct 17  1998 zcat



-- 

Stephen Montgomery-Smith              stephen@math.missouri.edu
307 Math Science Building             stephen@showme.missouri.edu
Department of Mathematics             stephen@missouri.edu
University of Missouri-Columbia
Columbia, MO 65211
USA

Phone (573) 882 4540
Fax   (573) 882 1869

http://www.math.missouri.edu/~stephen


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


From owner-freebsd-stable  Fri Mar 31  7:59:43 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from serenity.mcc.ac.uk (serenity.mcc.ac.uk [130.88.200.93])
	by hub.freebsd.org (Postfix) with ESMTP id F08B537BAB5
	for <freebsd-stable@freebsd.org>; Fri, 31 Mar 2000 07:59:37 -0800 (PST)
	(envelope-from jcm@dogma.freebsd-uk.eu.org)
Received: from dogma.freebsd-uk.eu.org ([130.88.200.97])
	by serenity.mcc.ac.uk with esmtp (Exim 1.92 #3)
	id 12b3pM-000CFE-00; Fri, 31 Mar 2000 16:59:16 +0100
Received: (from jcm@localhost)
	by dogma.freebsd-uk.eu.org (8.9.3/8.9.3) id QAA22158;
	Fri, 31 Mar 2000 16:59:15 +0100 (BST)
	(envelope-from jcm)
Date: Fri, 31 Mar 2000 16:59:15 +0100
From: J McKitrick <jcm@freebsd-uk.eu.org>
To: Stephen Montgomery-Smith <stephen@math.missouri.edu>
Cc: freebsd-stable <freebsd-stable@freebsd.org>
Subject: Re: What is needed in /stand
Message-ID: <20000331165915.A21909@dogma.freebsd-uk.eu.org>
References: <38E4CACD.177A6202@math.missouri.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0.1i
In-Reply-To: <38E4CACD.177A6202@math.missouri.edu>; from stephen@math.missouri.edu on Fri, Mar 31, 2000 at 09:57:01AM -0600
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Fri, Mar 31, 2000 at 09:57:01AM -0600, Stephen Montgomery-Smith wrote:
> Now I have upgraded to FreeBSD 4.0, I am finding that I am
> getting less and less room in the root mount point / .
> (I gave it 32M).

Stupid question: have you symlinked /var and /tmp to /usr?


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


From owner-freebsd-stable  Fri Mar 31  8:14:57 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20])
	by hub.freebsd.org (Postfix) with ESMTP id 1C2EF37BA1A
	for <freebsd-stable@FreeBSD.ORG>; Fri, 31 Mar 2000 08:14:56 -0800 (PST)
	(envelope-from bright@fw.wintelcom.net)
Received: (from bright@localhost)
	by fw.wintelcom.net (8.10.0/8.10.0) id e2VGdnr29106;
	Fri, 31 Mar 2000 08:39:49 -0800 (PST)
Date: Fri, 31 Mar 2000 08:39:48 -0800
From: Alfred Perlstein <bright@wintelcom.net>
To: Stephen Montgomery-Smith <stephen@math.missouri.edu>
Cc: freebsd-stable <freebsd-stable@FreeBSD.ORG>
Subject: Re: What is needed in /stand
Message-ID: <20000331083948.J21029@fw.wintelcom.net>
References: <38E4CACD.177A6202@math.missouri.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0.1i
In-Reply-To: <38E4CACD.177A6202@math.missouri.edu>; from stephen@math.missouri.edu on Fri, Mar 31, 2000 at 09:57:01AM -0600
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

* Stephen Montgomery-Smith <stephen@math.missouri.edu> [000331 08:21] wrote:
> Now I have upgraded to FreeBSD 4.0, I am finding that I am
> getting less and less room in the root mount point / .
> (I gave it 32M).
> 
> I was looking through / to see what is not needed, and I see
> a bunch of old files in /stand.  What is needed and what can
> I delete?
> 
> # cd /stand
> # ls -l
> total 22373
> -r-xr-xr-x  18 root  wheel  1219512 Oct 17  1998 -sh
> -r-xr-xr-x  18 root  wheel  1219512 Oct 17  1998 bad144
> -rw-r--r--   1 root  wheel     1030 Oct 17  1998 boot.help

Unless you did something weird, all those files are actually
the same file, 'ls -i' will show you they share the same inode,
deleteting or more of them isn't going to help unless you delete
them all and then you'll only free up under a megabyte.

I'd symlink /tmp to /var/tmp instead or look for another place
taking up space.

-- 
-Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org]
"I have the heart of a child, I keep it in a jar on my desk."


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


From owner-freebsd-stable  Fri Mar 31  8:28:23 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from madeline.boneyard.lawrence.ks.us (dv229s48.lawrence.ks.us [24.124.48.229])
	by hub.freebsd.org (Postfix) with ESMTP id C61D637B6B2
	for <freebsd-stable@freebsd.org>; Fri, 31 Mar 2000 08:28:20 -0800 (PST)
	(envelope-from bsd-stable@boneyard.lawrence.ks.us)
Received: from boneyard (boneyard [24.124.26.25])
	by madeline.boneyard.lawrence.ks.us (8.9.3/8.9.3) with ESMTP id KAA05310
	for <freebsd-stable@freebsd.org>; Fri, 31 Mar 2000 10:28:18 -0600 (CST)
	(envelope-from bsd-stable@boneyard.lawrence.ks.us)
Date: Fri, 31 Mar 2000 10:28:18 -0600 (CST)
From: <bsd-stable@boneyard.lawrence.ks.us>
To: freebsd-stable@freebsd.org
Subject: having problems with realtek under 4.0?
Message-ID: <Pine.BSF.4.10.10003311018400.5284-100000@madeline.boneyard.lawrence.ks.us>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


after upgrading my test machine from 3.4 to 4.0 a few days ago, i noticed
that my Ovus NIC (realtek 8139) was having some serious problems passing
data. 

the difference wasn't between 1.5 and 1.2M/sec... more along the lines of
1-2K a second with stalls, etc... remarkably enough, there were no kernel
or driver messages during these tests. 

it appears that the rl driver under 4.0 is having problems with auto-
negotiatiion.  i decided to try hard setting the media type before 
running out to get another intel card.  lo-and-behold... it works 
again.

please note, this problem appeared on a 10Base network.  I haven't test-
ed whether or not the same problem occurs autodetecting in an 100Base
environment yet.

Regards,
Stephen

 "We have enough youth.  How about a fountain of SMART?"
  [message seen on a button]
                                           Stephen D. Spencer - Lawrence, KS




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


From owner-freebsd-stable  Fri Mar 31  8:33:29 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from mail.rdc1.il.home.com (ha1.rdc1.il.home.com [24.2.1.66])
	by hub.freebsd.org (Postfix) with ESMTP id 0826F37BB24
	for <freebsd-stable@freebsd.org>; Fri, 31 Mar 2000 08:33:24 -0800 (PST)
	(envelope-from stephen@math.missouri.edu)
Received: from math.missouri.edu ([24.12.197.197]) by mail.rdc1.il.home.com
          (InterMail v4.01.01.00 201-229-111) with ESMTP
          id <20000331163322.GHIP4993.mail.rdc1.il.home.com@math.missouri.edu>
          for <freebsd-stable@freebsd.org>; Fri, 31 Mar 2000 08:33:22 -0800
Message-ID: <38E4D398.A5392C71@math.missouri.edu>
Date: Fri, 31 Mar 2000 10:34:33 -0600
From: Stephen Montgomery-Smith <stephen@math.missouri.edu>
X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.12 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: freebsd-stable <freebsd-stable@freebsd.org>
Subject: Re: What is needed in /stand
References: <38E4CACD.177A6202@math.missouri.edu> <20000331165915.A21909@dogma.freebsd-uk.eu.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

J McKitrick wrote:
> 
> 
> Stupid question: have you symlinked /var and /tmp to /usr?
> 

Yes.  The stuff on / is real stuff.  Perhaps I like to keep
too much.  I always like to keep a kernel.GENERIC handy for
emergencies, and that takes a lot of space.  The size of 
the kernels has grown with time.

-- 

Stephen Montgomery-Smith              stephen@math.missouri.edu
307 Math Science Building             stephen@showme.missouri.edu
Department of Mathematics             stephen@missouri.edu
University of Missouri-Columbia
Columbia, MO 65211
USA

Phone (573) 882 4540
Fax   (573) 882 1869

http://www.math.missouri.edu/~stephen


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


From owner-freebsd-stable  Fri Mar 31  8:35:42 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from cfdnet.me.tuns.ca (CFDnet.me.TUNS.Ca [134.190.50.164])
	by hub.freebsd.org (Postfix) with ESMTP id 0BED637BE5F
	for <freebsd-stable@FreeBSD.ORG>; Fri, 31 Mar 2000 08:35:39 -0800 (PST)
	(envelope-from bbmail@cfdnet.me.tuns.ca)
Received: from localhost (bbmail@localhost)
	by cfdnet.me.tuns.ca (8.9.3/8.9.3) with ESMTP id MAA33855;
	Fri, 31 Mar 2000 12:08:03 -0400 (AST)
	(envelope-from bbmail@cfdnet.me.tuns.ca)
Date: Fri, 31 Mar 2000 12:08:03 -0400 (AST)
From: Bryan Bursey <bbmail@cfdnet.me.tuns.ca>
To: Stephen Montgomery-Smith <stephen@math.missouri.edu>
Cc: freebsd-stable <freebsd-stable@FreeBSD.ORG>
Subject: Re: What is needed in /stand
In-Reply-To: <20000331165915.A21909@dogma.freebsd-uk.eu.org>
Message-ID: <Pine.BSF.4.10.10003311206140.33817-100000@cfdnet.me.tuns.ca>
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, Mar 31, 2000 at 09:57:01AM -0600, Stephen Montgomery-Smith wrote:
> > Now I have upgraded to FreeBSD 4.0, I am finding that I am
> > getting less and less room in the root mount point / .
> > (I gave it 32M).
               ^^^
	This sounds like it might be a little undersized even if you
	didn't accidentally include some variable size subdirs...

Cheers,

Bryan 
iSpheric.com




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


From owner-freebsd-stable  Fri Mar 31  8:54:40 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from rover.village.org (rover.village.org [204.144.255.49])
	by hub.freebsd.org (Postfix) with ESMTP id 842DF37BB76
	for <stable@FreeBSD.ORG>; Fri, 31 Mar 2000 08:54:37 -0800 (PST)
	(envelope-from imp@harmony.village.org)
Received: from harmony.village.org (harmony.village.org [10.0.0.6])
	by rover.village.org (8.9.3/8.9.3) with ESMTP id JAA73900;
	Fri, 31 Mar 2000 09:54:36 -0700 (MST)
	(envelope-from imp@harmony.village.org)
Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id JAA35682; Fri, 31 Mar 2000 09:54:06 -0700 (MST)
Message-Id: <200003311654.JAA35682@harmony.village.org>
To: Jaye Mathisen <mrcpu@internetcds.com>
Subject: Re: sshd failure from Adding crypto later on -stable? 
Cc: stable@FreeBSD.ORG
In-reply-to: Your message of "Thu, 30 Mar 2000 19:04:50 PST."
		<Pine.BSF.4.21.0003301902060.26102-100000@schizo.cdsnet.net> 
References: <Pine.BSF.4.21.0003301902060.26102-100000@schizo.cdsnet.net>  
Date: Fri, 31 Mar 2000 09:54:06 -0700
From: Warner Losh <imp@village.org>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

In message <Pine.BSF.4.21.0003301902060.26102-100000@schizo.cdsnet.net> Jaye Mathisen writes:
: ls -l /usr/lib/*rsa*
: -r--r--r--  1 root  wheel  6358 Mar 30 14:12 /usr/lib/librsaUSA.a
: lrwxr-xr-x  1 root  wheel    14 Mar 30 14:12 /usr/lib/librsaUSA.so ->
: librsaUSA.so.1
: -r--r--r--  1 root  wheel  8080 Mar 30 14:12 /usr/lib/librsaUSA.so.1
: -r--r--r--  1 root  wheel  7122 Mar 30 14:12 /usr/lib/librsaUSA_p.a

ln -s librsaUSA.so librsaref.so

Fixed this for me.

Warner


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


From owner-freebsd-stable  Fri Mar 31  8:56: 3 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from pebkac.owp.csus.edu (pebkac.owp.csus.edu [130.86.232.245])
	by hub.freebsd.org (Postfix) with ESMTP
	id E91D537B7BE; Fri, 31 Mar 2000 08:55:56 -0800 (PST)
	(envelope-from joseph.scott@owp.csus.edu)
Received: from owp.csus.edu (mail.owp.csus.edu [130.86.232.247])
	by pebkac.owp.csus.edu (8.9.3/8.9.3) with ESMTP id IAA16533;
	Fri, 31 Mar 2000 08:55:40 -0800 (PST)
	(envelope-from joseph.scott@owp.csus.edu)
Message-ID: <38E4D80E.C522DCE4@owp.csus.edu>
Date: Fri, 31 Mar 2000 08:53:34 -0800
From: Joseph Scott <joseph.scott@owp.csus.edu>
X-Mailer: Mozilla 4.72 [en] (X11; I; Linux 2.2.12 i386)
X-Accept-Language: en,pdf
MIME-Version: 1.0
To: Brad Knowles <blk@skynet.be>
Cc: Kris Kennaway <kris@FreeBSD.ORG>,
	Siew Sim <siewsim@prismedia.com>,
	FreeBSD-STABLE Mailing List <freebsd-stable@FreeBSD.ORG>
Subject: Re: please help - thread-safe mysql client link problem
References: <Pine.BSF.4.21.0003301524490.49247-100000@freefall.freebsd.org> <v04220803b50a2c090fe1@[195.238.1.121]>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Brad Knowles wrote:
> 
> At 3:25 PM -0800 on 2000/3/30, Kris Kennaway wrote:
> 
> >>      I'm using FreeBSD 3.2, and mysql 3.22.30.  I'm trying to build a
> >>  thread-safe mysql client with pthread.
> >
> >  Use the port.
> 
>         The last time I tried that, I had a problem in that the port was
> looking for a version of the package that no longer existed on the
> ftp servers, so I was forced to do the whole thing manually.
> 
>         Do you know for sure that the current version of the port uses a
> sufficiently recent version of the MySQL package, so that it can be
> found on the ftp servers?  Does it use the latest version of the
> MySQL package, and if not how many revisions back is it, and have
> there been any significant enhancements in the time since?

	I just installed the port on a system, found everything fine, so that
part works.  I took a look at www.mysql.com where they say the latest
"recommended release" ( I read that to mean like FBSD's -stable branch
) is 3.22.32.  This is the same version that's listed in the Makefile
for ports/databases/mysql322-server.  At least as of about an hour ago
when I last cvsup'd my ports collection.

	There is a newer version ( not in the ports collection ) that is more
bleeding edge that can be found at www.mysql.com

---
Joseph Scott
joseph.scott@owp.csus.edu
The Office Of Water Programs - CSU Sacramento


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


From owner-freebsd-stable  Fri Mar 31  8:56: 4 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from rover.village.org (rover.village.org [204.144.255.49])
	by hub.freebsd.org (Postfix) with ESMTP id 2422037BCD8
	for <freebsd-stable@FreeBSD.ORG>; Fri, 31 Mar 2000 08:56:00 -0800 (PST)
	(envelope-from imp@harmony.village.org)
Received: from harmony.village.org (harmony.village.org [10.0.0.6])
	by rover.village.org (8.9.3/8.9.3) with ESMTP id JAA73912;
	Fri, 31 Mar 2000 09:55:58 -0700 (MST)
	(envelope-from imp@harmony.village.org)
Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id JAA35705; Fri, 31 Mar 2000 09:55:27 -0700 (MST)
Message-Id: <200003311655.JAA35705@harmony.village.org>
To: "Steve O'Hara-Smith" <steveo@eircom.net>
Subject: Re: Stability and versions - was Re: Let 3.x die ASAP? 
Cc: Kiril Mitev <kiril@ideaglobal.com>, freebsd-stable@FreeBSD.ORG
In-reply-to: Your message of "Thu, 30 Mar 2000 21:47:05 +0100."
		<XFMail.000330214705.steveo@eircom.net> 
References: <XFMail.000330214705.steveo@eircom.net>  
Date: Fri, 31 Mar 2000 09:55:27 -0700
From: Warner Losh <imp@village.org>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

In message <XFMail.000330214705.steveo@eircom.net> "Steve O'Hara-Smith" writes:
:         It may very well be the case that 2.2-stable is currently the most
: stable FreeBSD around, the main reason for this is that for quite some
: time now it has been getting _only_ bug and security fixes (IIRC only the
: latter for some time).

And only sometimes.  there are lots of security nasties that haven't
been and never will be fixed in 2.2.x.

Warner


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


From owner-freebsd-stable  Fri Mar 31  8:57:58 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from rover.village.org (rover.village.org [204.144.255.49])
	by hub.freebsd.org (Postfix) with ESMTP id 680DF37BFAD
	for <freebsd-stable@FreeBSD.ORG>; Fri, 31 Mar 2000 08:57:52 -0800 (PST)
	(envelope-from imp@harmony.village.org)
Received: from harmony.village.org (harmony.village.org [10.0.0.6])
	by rover.village.org (8.9.3/8.9.3) with ESMTP id JAA73924;
	Fri, 31 Mar 2000 09:57:48 -0700 (MST)
	(envelope-from imp@harmony.village.org)
Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id JAA35732; Fri, 31 Mar 2000 09:57:19 -0700 (MST)
Message-Id: <200003311657.JAA35732@harmony.village.org>
To: David Gilbert <dgilbert@velocet.ca>
Subject: Re: disklabel fails. 
Cc: freebsd-stable@FreeBSD.ORG
In-reply-to: Your message of "Fri, 31 Mar 2000 08:52:39 EST."
		<14564.44455.794698.35833@trooper.velocet.net> 
References: <14564.44455.794698.35833@trooper.velocet.net>  
Date: Fri, 31 Mar 2000 09:57:19 -0700
From: Warner Losh <imp@village.org>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

In message <14564.44455.794698.35833@trooper.velocet.net> David Gilbert writes:
: What's up with disklabel?

Seems to work great for me.  You might try diskprep from my website
	http://people.freebsd.org/~imp/diskprep
which is  much easier to use than traditional fdisk + frustration +
disklabel + more frustration + goto 0.

Warner


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


From owner-freebsd-stable  Fri Mar 31  9:28:53 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from kibby.au.knfpub.com (kibby.au.knfpub.com [203.38.198.130])
	by hub.freebsd.org (Postfix) with ESMTP id 00A7D37BDCA
	for <freebsd-stable@freebsd.org>; Fri, 31 Mar 2000 09:28:43 -0800 (PST)
	(envelope-from kibbet@kibby.au.knfpub.com)
Received: (from kibbet@localhost)
	by kibby.au.knfpub.com (8.9.3/8.9.3) id CAA02887
	for freebsd-stable@freebsd.org; Sat, 1 Apr 2000 02:58:49 +0930 (CST)
	(envelope-from kibbet)
Message-ID: <XFMail.000401025849.kibbet@knfpub.com>
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
Date: Sat, 01 Apr 2000 02:58:49 +0930 (CST)
From: kibbet <kibbet@knfpub.com>
To: freebsd-stable@freebsd.org
Subject: pnpparse.c
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hi all,

The sys/isa/pnpparse.c MFC today seems to have broken things
here with my AWE64, things were happy before the MFC, apart
from an odd message during boot

With pnpparse.c v1.2, AWE64 installed;

(** blah blah... **)
ukphy0: <Generic IEEE 802.3u media interface> on miibus0
ukphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
dc0: supplying EUI64: 00:a0:cc:ff:fe:5a:6c:4a
isa0: unexpected tag 14                        <--- Odd message :)
(** more blah blah **)
sbc0: <Creative SB AWE64> at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5 drq
    1,5 on isa0
sbc0: setting card to irq 5, drq 1, 5
pcm0: <SB DSP 4.16> on sbc0
unknown0: <Game> at port 0x200-0x207 on isa0
unknown1: <WaveTable> at port 0x620-0x623 on isa0
(** few more blah blah's **)  :)

Boots fine, sound/mixer works, no probs, haven't tried the joystick/wavetable
stuff though.

If I take out the AWE64, the "isa0: unexpected tag 14" line
disappears, and strangly - I don't get sound... :)



With pnpparse.c v1.2.2.1 (the MFC), AWE installed;

(** back with some blah blah **)
ukphy0: <Generic IEEE 802.3u media interface> on miibus0
ukphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
dc0: supplying EUI64: 00:a0:cc:ff:fe:5a:6c:4a
isa0: to many dependant configs (8)

panic: pmap_enter: invalid page directory, pdir=0 va=0xc0b11000

So I drop in the DDB, here's the trace (by hand, I'll get more detail
if anyone wants it - tommorow its 2:40am already *yawn*)

pmap_enter()
kmem_malloc()
malloc()
isa_add_config()
ISA_ADD_CONFIG()
pnp_parse_resources()
pnp_create_devices()
(** couple more, I think thats enuff though (yawn) **)


So I had a look at pnpparse.c, thought I'd get smart and change
MAXDEP to 16, tried that, it got past the "to many dependant configs" bit
but still panic'd.

Take out the card, boots fine, no problem at all, but my speakers complain
that the sound card isn't doing its job when its not in the computer.


Oh well, 'nuff rambling from me, snoze time, i'll send a PR unless anyone
has any idea's.


Cheers,

Kent Ibbetson
KNF Publishing
kibbet@knfpub.com


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


From owner-freebsd-stable  Fri Mar 31  9:41:27 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from firehouse.net (spook.networkoperations.com [209.42.203.59])
	by hub.freebsd.org (Postfix) with SMTP id AB1EB37BB6D
	for <freebsd-stable@FreeBSD.ORG>; Fri, 31 Mar 2000 09:41:22 -0800 (PST)
	(envelope-from abc@firehouse.net)
Received: (qmail 10596 invoked by uid 100); 31 Mar 2000 17:41:19 -0000
Date: Fri, 31 Mar 2000 12:41:19 -0500
From: Alan Clegg <abc@firehouse.net>
To: J McKitrick <jcm@freebsd-uk.eu.org>
Cc: Stephen Montgomery-Smith <stephen@math.missouri.edu>,
	freebsd-stable <freebsd-stable@FreeBSD.ORG>
Subject: Re: What is needed in /stand
Message-ID: <20000331124119.B10520@laptop.firehouse.net>
References: <38E4CACD.177A6202@math.missouri.edu> <20000331165915.A21909@dogma.freebsd-uk.eu.org>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-md5;
	protocol="application/pgp-signature"; boundary="24zk1gE8NUlDmwG9"
X-Mailer: Mutt 1.0.1i
In-Reply-To: <20000331165915.A21909@dogma.freebsd-uk.eu.org>; from jcm@freebsd-uk.eu.org on Fri, Mar 31, 2000 at 04:59:15PM +0100
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


--24zk1gE8NUlDmwG9
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable

Out of the ether, J McKitrick spewed forth the following bitstream:
> On Fri, Mar 31, 2000 at 09:57:01AM -0600, Stephen Montgomery-Smith wrote:
> > Now I have upgraded to FreeBSD 4.0, I am finding that I am
> > getting less and less room in the root mount point / .
> > (I gave it 32M).
>=20
> Stupid question: have you symlinked /var and /tmp to /usr?

/tmp should not be linked anywhere off of the root file system.

I'd recommend mounting an MFS or another filesystem on it, but not=20
symlinking it.

Too many things use it (and depend on it) being there before /usr is
mounted (or if /usr is not available).

AlanC
--=20
                                      \             Alan B. Clegg
         Just because I can            \          abc@firehouse.net
        does not mean I will.           \     <http://www.firehouse.net/>
                                         \

--24zk1gE8NUlDmwG9
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 5.0i for non-commercial use
MessageID: ANFNjNul/+6LKxGVv5S138SInoSGF0d1

iQA/AwUBOOTjPvcyv/gweBpYEQKxtgCfQVsKAMOsPW0SgPnb/R6i9cK7f+QAn24n
9q8EReldTJeDySdQ/P4oy6W5
=JEO/
-----END PGP SIGNATURE-----

--24zk1gE8NUlDmwG9--


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


From owner-freebsd-stable  Fri Mar 31  9:45:48 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from serenity.mcc.ac.uk (serenity.mcc.ac.uk [130.88.200.93])
	by hub.freebsd.org (Postfix) with ESMTP id 633DA37BD0F
	for <freebsd-stable@freebsd.org>; Fri, 31 Mar 2000 09:45:19 -0800 (PST)
	(envelope-from jcm@dogma.freebsd-uk.eu.org)
Received: from dogma.freebsd-uk.eu.org ([130.88.200.97])
	by serenity.mcc.ac.uk with esmtp (Exim 1.92 #3)
	id 12b5Tt-000Ewj-00; Fri, 31 Mar 2000 18:45:13 +0100
Received: (from jcm@localhost)
	by dogma.freebsd-uk.eu.org (8.9.3/8.9.3) id SAA22820;
	Fri, 31 Mar 2000 18:45:13 +0100 (BST)
	(envelope-from jcm)
Date: Fri, 31 Mar 2000 18:45:13 +0100
From: J McKitrick <jcm@freebsd-uk.eu.org>
To: Alan Clegg <abc@firehouse.net>
Cc: Stephen Montgomery-Smith <stephen@math.missouri.edu>,
	freebsd-stable <freebsd-stable@FreeBSD.ORG>
Subject: Re: What is needed in /stand
Message-ID: <20000331184513.A22797@dogma.freebsd-uk.eu.org>
References: <38E4CACD.177A6202@math.missouri.edu> <20000331165915.A21909@dogma.freebsd-uk.eu.org> <20000331124119.B10520@laptop.firehouse.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0.1i
In-Reply-To: <20000331124119.B10520@laptop.firehouse.net>; from abc@firehouse.net on Fri, Mar 31, 2000 at 12:41:19PM -0500
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Fri, Mar 31, 2000 at 12:41:19PM -0500, Alan Clegg wrote:
> > Stupid question: have you symlinked /var and /tmp to /usr?
> 
> /tmp should not be linked anywhere off of the root file system.
> 
> I'd recommend mounting an MFS or another filesystem on it, but not 
> symlinking it.
> 
> Too many things use it (and depend on it) being there before /usr is
> mounted (or if /usr is not available).

Really?  I was under the impression that this was OK, and actually
standard procedure these days for simple installations.

jm
-- 
--------------------------------------------
Jonathon McKitrick -- jcm@freebsd-uk.eu.org 
"You're the guy from the Hambuger Train, right?"
--------------------------------------------


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


From owner-freebsd-stable  Fri Mar 31  9:48:10 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from firehouse.net (spook.networkoperations.com [209.42.203.59])
	by hub.freebsd.org (Postfix) with SMTP id D90B137BB44
	for <freebsd-stable@FreeBSD.ORG>; Fri, 31 Mar 2000 09:48:05 -0800 (PST)
	(envelope-from abc@firehouse.net)
Received: (qmail 10714 invoked by uid 100); 31 Mar 2000 17:48:04 -0000
Date: Fri, 31 Mar 2000 12:48:04 -0500
From: Alan Clegg <abc@firehouse.net>
To: J McKitrick <jcm@freebsd-uk.eu.org>
Cc: Alan Clegg <abc@firehouse.net>,
	Stephen Montgomery-Smith <stephen@math.missouri.edu>,
	freebsd-stable <freebsd-stable@FreeBSD.ORG>
Subject: Re: What is needed in /stand
Message-ID: <20000331124804.D10520@laptop.firehouse.net>
References: <38E4CACD.177A6202@math.missouri.edu> <20000331165915.A21909@dogma.freebsd-uk.eu.org> <20000331124119.B10520@laptop.firehouse.net> <20000331184513.A22797@dogma.freebsd-uk.eu.org>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-md5;
	protocol="application/pgp-signature"; boundary="9l24NVCWtSuIVIod"
X-Mailer: Mutt 1.0.1i
In-Reply-To: <20000331184513.A22797@dogma.freebsd-uk.eu.org>; from jcm@freebsd-uk.eu.org on Fri, Mar 31, 2000 at 06:45:13PM +0100
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


--9l24NVCWtSuIVIod
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable

Out of the ether, J McKitrick spewed forth the following bitstream:
> On Fri, Mar 31, 2000 at 12:41:19PM -0500, Alan Clegg wrote:
> > > Stupid question: have you symlinked /var and /tmp to /usr?
> >=20
> > /tmp should not be linked anywhere off of the root file system.
> >=20
> > I'd recommend mounting an MFS or another filesystem on it, but not=20
> > symlinking it.
> >=20
> > Too many things use it (and depend on it) being there before /usr is
> > mounted (or if /usr is not available).
>=20
> Really?  I was under the impression that this was OK, and actually
> standard procedure these days for simple installations.

Yikes.  Maybe my gray hairs are starting to show... And come to think
about it, that nose & ear hair-trimmer I got for Christmas may be useful
after all. =20

But I'd still not do it myself.  8)

AlanC
--=20
                                      \             Alan B. Clegg
         Just because I can            \          abc@firehouse.net
        does not mean I will.           \     <http://www.firehouse.net/>
                                         \

--9l24NVCWtSuIVIod
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 5.0i for non-commercial use
MessageID: OEIYMYRa1iBiOXSj5tlxaa/PjO2oBjTV

iQA/AwUBOOTk0/cyv/gweBpYEQL2PQCgpjKCrDqj9Fcs1HuZeJJh4ZbyRzkAn1Fz
MOHjJRycimjE8uaj7ISXhVWT
=Xqoy
-----END PGP SIGNATURE-----

--9l24NVCWtSuIVIod--


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


From owner-freebsd-stable  Fri Mar 31 10:41:47 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from grace.speakeasy.org (grace.speakeasy.org [216.254.0.2])
	by hub.freebsd.org (Postfix) with ESMTP id DC4AE37B93A
	for <freebsd-stable@FreeBSD.org>; Fri, 31 Mar 2000 10:41:43 -0800 (PST)
	(envelope-from rjoseph@speakeasy.org)
Received: from 10-098.009.popsite.net (10-098.009.popsite.net [207.227.233.98])
	by grace.speakeasy.org (8.10.0/8.10.0) with ESMTP id e2VIfHg08540
	for <freebsd-stable@FreeBSD.org>; Fri, 31 Mar 2000 10:41:33 -0800
Date: Fri, 31 Mar 2000 10:34:42 -0800 (PST)
From: R Joseph Wright <rjoseph@speakeasy.org>
X-Sender: rjoseph@mammalia.sea
To: freebsd-stable@FreeBSD.org
Subject: make world: indxbib: No such file or directory...
Message-ID: <Pine.BSF.4.21.0003311028440.58863-100000@mammalia.sea>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

I did a make buildworld today from last night's cvsup and got this:

indxbib -c /usr/src/share/doc/papers/memfs/../../../../contrib/groff/indxbib/eign  -o ref.bib /usr/src/share/doc/papers/memfs/ref.bib
indxbib:No such file or directory
*** Error code 1

Stop in /usr/src/share/doc/papers/memfs.

Has anyone else gotten this?  
I'm running 4.0-stable, and I'll gladly provide any more information if
needed.



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


From owner-freebsd-stable  Fri Mar 31 10:50:20 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from tinc-org.com (tinc-org.com [64.6.65.10])
	by hub.freebsd.org (Postfix) with ESMTP id 6756437BA14
	for <freebsd-stable@freebsd.org>; Fri, 31 Mar 2000 10:50:17 -0800 (PST)
	(envelope-from jeff@jeffenstein.org)
Received: (from uucp@localhost)
	by tinc-org.com (8.9.3/8.9.3) with UUCP id MAA95415
	Fri, 31 Mar 2000 12:50:15 -0600 (CST) (envelope-from jeff@jeffenstein.org)
Received: (from uucp@localhost)
	by localhost.jeffnet (8.9.3/8.9.3) id MAA28835
	for <freebsd-stable@freebsd.org>; Fri, 31 Mar 2000 12:49:17 -0600 (CST)
	(envelope-from jeff@jeffenstein.org)
Received: from frogger.jeffnet(192.168.243.1), claiming to be "frogger-int"
 via SMTP by frogger.jeffnet, id smtpdq28830; Fri Mar 31 12:49:12 2000
Date: Fri, 31 Mar 2000 12:49:12 -0600 (CST)
From: Jeff Fisher <jeff@jeffenstein.org>
X-Sender: jeff@localhost
To: freebsd-stable@freebsd.org
Subject: Re: What is needed in /stand
In-Reply-To: <20000331124119.B10520@laptop.firehouse.net>
Message-ID: <Pine.BSF.4.21.0003311244360.28631-100000@localhost>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Fri, 31 Mar 2000, Alan Clegg wrote:

> Out of the ether, J McKitrick spewed forth the following bitstream:
> > On Fri, Mar 31, 2000 at 09:57:01AM -0600, Stephen Montgomery-Smith wrote:
> > > Now I have upgraded to FreeBSD 4.0, I am finding that I am
> > > getting less and less room in the root mount point / .
> > > (I gave it 32M).
> > 
> > Stupid question: have you symlinked /var and /tmp to /usr?
> 
> /tmp should not be linked anywhere off of the root file system.
> 
> I'd recommend mounting an MFS or another filesystem on it, but not 
> symlinking it.
> 
> Too many things use it (and depend on it) being there before /usr is
> mounted (or if /usr is not available).
> 

If it's needed, you could create the /usr/tmp directory on the root
partition, so it will be there before /usr is mounted.  Hopefully it won't
get alot of files that transparently fill up the root.

--
jeff@jeffenstein.org             http://www.jeffenstein.org

Microsoft: Where do you want to go today?
Linux: Where do you want to go tomorrow?
FreeBSD: Are you guys coming or what?




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


From owner-freebsd-stable  Fri Mar 31 11: 4:58 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from frolkin.demon.co.uk (frolkin.demon.co.uk [194.222.100.41])
	by hub.freebsd.org (Postfix) with ESMTP id A2A3E37B693
	for <stable@freebsd.org>; Fri, 31 Mar 2000 11:04:48 -0800 (PST)
	(envelope-from sasha@frolkin.demon.co.uk)
Received: from sasha by frolkin.demon.co.uk with local (Exim 3.12 #1)
	id 12b5la-0001O8-00
	for stable@freebsd.org; Fri, 31 Mar 2000 19:03:30 +0100
Date: Fri, 31 Mar 2000 19:03:29 +0100
From: Alexander Frolkin <alexander@frolkin.demon.co.uk>
To: stable@freebsd.org
Subject: Upgrading to 4.0
Message-ID: <20000331190328.A4215@gamma>
Reply-To: Alexander Frolkin <alexander@frolkin.demon.co.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.5i
X-Operating-System: Linux 2.2.14
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hello,

I'd like to upgrade by FreeBSD laptop to RELENG_4, but I have a question -

AFAIK, it is necessary to install a 4.0 kernel before doing installworld.
According to src/UPDATING, pccardd needs to be recompiled to work with the
new kernel. The problem is that /usr/obj and /usr/src will be NFS mounted,
and the network card is a PCMCIA NE2000. Can I just build and install the
new pccardd and then reboot, or is there something else I will need to do?


Also, I noticed that src/crypto/README says that the stuff is export
restricted. Should it say this, even though I got it from
cvsup.internat.freebsd.org?

TIA,

Alexander.

-- 
... Windows: Just another pane in the glass. ...


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


From owner-freebsd-stable  Fri Mar 31 11:29:54 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from mail.oxfam.org.uk (mail.oxfam.org.uk [195.153.200.167])
	by hub.freebsd.org (Postfix) with ESMTP
	id 5580E37B939; Fri, 31 Mar 2000 11:29:41 -0800 (PST)
	(envelope-from rlake@oxfam.org.pe)
Received: from rlake.oxfam.org.pe (root@[209.45.73.61])
	by mail.oxfam.org.uk (8.9.3/8.8.5) with ESMTP id UAA01545;
	Fri, 31 Mar 2000 20:35:31 GMT
Received: from localhost (rlake@localhost [127.0.0.1])
	by rlake.oxfam.org.pe (8.8.8/8.8.8) with ESMTP id NAA08697;
	Fri, 31 Mar 2000 13:11:07 -0500
Date: Fri, 31 Mar 2000 13:11:06 -0500 (PET)
From: Rici Lake <rlake@oxfam.org.pe>
To: David Malone <dwmalone@maths.tcd.ie>
Cc: Jeff Hamilton <hjeffrey@hotmail.com>,
	freebsd-questions@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG
Subject: portmap in hosts.allow configuration notes. Was Re: /etc/hosts.allow
In-Reply-To: <20000328231657.A9744@walton.maths.tcd.ie>
Message-ID: <Pine.LNX.4.05.10003311059380.8417-100000@rlake.oxfam.org.pe>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

I received this error, too. In the course of investigating it, I found out
a whole lot about FreeBSD. Some of my notes are reproduced here in the
hopes that they might be useful to someone. I don't know if this is an
appropriate forum, but if it's not no doubt someone will flame me :-)

Sorry about the length of the message. There are three parts: first, a
quick answer to Jeff's original question; second, a diagnosis of what's
happening, and third, some recommendations for whoever feels they're
responsible.

The short answer to Jeff is that you did do something wrong: you can't use
twist with portmap. So you can't let portmap "fall through" to the default
rejection line in hosts.allow. You must use either ACCEPT or DENY, and as
the comments in hosts.allow say (but not the example), you cannot use
hostnames.

I think this should be made clearer in the hosts.allow template, FWIW.

The other piece of the puzzle is that this was almost certainly a port
scan, although it could have been an attempted break-in -- in any case,
it would have been unsuccessful.

Finally, I think we can conclude that Jeff is not using portmap and should
not be running the service. :-) (see below)

Here's the diagnosis, in case anyone cares.

Wietse Venema's wonderful tcp wrapper program and library are incredibly
useful, and I don't mean this to be a criticism in any way.

The tcp wrapper library (libwrap) provides an interface to the
/etc/hosts.* configuration files, and this support is used in various
programs, including portmap and sendmail (and probably others.) However,
the tcp wrapper package was originally written to be used in a
"single-fire" mode with inetd, and many of the extended options (enabled
with the -DPROCESS_OPTIONS compile-time flag to the tcp wrappers package,
which seems to be the default setting in FreeBSD, amongst others) are not
going to work other than in this mode. 

The twist option cannot work other than in inetd mode. It causes the
calling process to be replaced (through the execl(3) system call) with an
configured shell process. If the calling process intended to hang around
for a while to answer more requests, it's in for a surprise.

To attempt to prevent this, the tcp wrappers library maintains a count of
the number of times it has been called, and if it's been called more than
once, it won't do the twist. (Call it square :-) )

This check will not be effective if the twist happens on the first call to
the wrappers library after the process starts. This is unlikely but
possible, unless the service is not being legitimately used. So if you run
portmap but don't use it AND you take the portmap lines out of
hosts.allow, leaving only the default ALL : ALL : twist line at the end,
then when someone attempts to connect to portmap, it will call the
wrapper library, the wrapper library will try the twist, and it will fail
with the error message you saw (more on that later.) Having failed to
twist, and having failed to execl(3), the library will call exit(3) and
portmap will be no more.

The reason the twist fails is that it attempts to dup2(3) the fd for the
socket connection prior to the execl(3). However, programs like portmap
which use the simplified wrapper library interface hosts_tcl(see
hosts_access(3)) cannot inform the wrapper library of the fd of the socket
connection (nor, probably, should they), and therefore the wrapper library
will attempt to dup2(3) file descriptor -1. dup2(3) returns EBADF, and the
error you received is generated.

Oddly, the wrapper library will already have syslog(3)ged the twist
attempt, which might have told you the IP number the connection came from,
but you probably won't have seen that. That's because the default logging
facility/level set by the default hosts.allow file is auth.info, and the
default syslog.conf(5) file discards everything in auth under auth.notice.

So, here are some suggestions. Accept, ignore, critique, whatever:

1. The default /etc/hosts.allow should make it clearer that you can't
twist certain services, including portmap and sendmail.

2. Either the default /etc/syslog.conf should log auth.info somewhere, or
the default /etc/hosts.allow should not downgrade the importance of
twists, or some comment somewhere should point out that twists aren't
logged. No doubt there were good reasons for these choices (although they
strike me as curious) so I'd settle for the comment.

3. With respect to Wietse Venema, I think the protection against stupidity
or ignorance in options.c could be improved a little bit. I would suggest
pre-checking the value of fd before trying to use it, for example. This
fairly small patch would at least produce meaningful error messages in
this particular case (and would have saved portmap from having been
terminated, although I don't suppose that that matters much.) 

4. While I was cruising around trying to find the answer to all this
stuff, I noticed that in portmap, hosts_ctl is called with empty strings
for the client host name and user name arguments. In hosts_access(3), it
states that these arguments should be set to the macro STRING_UNKNOWN if
they are invalid. As far as I can see, the manpage is correct: if the
argument is specified as "", the wrapper library will attempt to work it
out if necessary. Since it's clear that you can't do a DNS lookup, much
less an ident, in portmap, it would be better to specify STRING_UNKNOWN to
flag the wrapper library to not bother trying to do the lookups. However,
for the life of me, I can't see how tcpd.h is #included in pmap_check.c; I
suppose it doesn't matter given c's laxity about function prototyping.
STRING_UNKNOWN is, in fact "unknown".


On Tue, 28 Mar 2000, David Malone wrote:

> On Tue, Mar 28, 2000 at 01:24:18PM -0800, Jeff Hamilton wrote:
> 
> > >My guess is that the portmapper is getting a tcp connection, which the
> > >remote end closes almost immediately. Then when the wrapping code goes
> > >to to dup the discriptor which is supposed to be connected it finds it
> > >is unconnected.
> > 
> > Could this possibly be an indicator of a port scan or other exploit attempt? 
> >   Is there anyway to trace the IP address that originated the connection?
> 
> If my guess was right, there is a good chance it could be a portscan.
> Tracing the IP address is probably a bit harder. I'll experiment at
> home and see if I can reproduce this.
> 
> 	David.
> 
> 
> 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 31 11:37:55 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from csla.csl.sri.com (csla.csl.sri.com [192.12.33.2])
	by hub.freebsd.org (Postfix) with ESMTP id AB77A37BF8A
	for <freebsd-stable@FreeBSD.ORG>; Fri, 31 Mar 2000 11:37:51 -0800 (PST)
	(envelope-from gilham@snapdragon.csl.sri.com)
Received: from snapdragon.csl.sri.com (snapdragon.csl.sri.com [130.107.18.20])
	by csla.csl.sri.com (8.9.1/8.9.1) with ESMTP id LAA25957
	for <freebsd-stable@FreeBSD.ORG>; Fri, 31 Mar 2000 11:37:51 -0800 (PST)
Message-Id: <200003311937.LAA25957@csla.csl.sri.com>
To: freebsd-stable@FreeBSD.ORG
Subject: A few STABLE problems
Date: Fri, 31 Mar 2000 11:37:50 -0800
From: Fred Gilham <gilham@snapdragon.csl.sri.com>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


I installed 4.0-STABLE --- works at least as well as 3.4 did (which is
VERY WELL).  Great job.

There are a few persistent problems I thought I'd mention.  By
persistent I mean on-going over many releases (one is from 2.2).  I
have workarounds for all of them but I kind of hate carrying patches
around either in file form or in my PFS (protoplasmic file system).
They tend to get lost or forgotten.

1) AMD with dual-networked file servers

   For some time the stock AMD hasn't worked with our dual homed file
   servers.  There appears to be an nfsv2 vs nfsv3 issue.  At some
   point there were some incompatible changes made to the map options
   and I never got the explanation of how to change our maps to make
   things work again.

   Currently I have an old AMD that I've patched to use the nvsv2
   compatibility mode.  Perhaps some people will recognize this.  It
   causes AMD to print

found compatiblity option "nfsv2": set options vers=2, proto=udp for host sofia

   to the syslog.  However, I have to install this custom AMD every
   time.  This problem (of not working with dual-homed servers) has
   been around (on and off) since 2.2.  If there's a definitive answer
   to this, I still haven't heard it.  Perhaps I wasn't paying
   attention?

2) Our site manages the group file with NIS.  We manage the `wheel'
   group.  As a result, there's no `wheel' entry in the group file
   until after NIS comes up.  But in /etc/rc there's the following:

# Whack the pty perms back into shape.
#
chflags 0 /dev/tty[pqrsPQRS]*
chmod 666 /dev/tty[pqrsPQRS]*
chown root:wheel /dev/tty[pqrsPQRS]*

   This won't work (i.e. it hangs) on my machine because it comes
   before NIS is started.  I have to move this after network_pass2.

   I submitted a PR on this.  Admittedly it's not a big problem, but
   nothing was ever done about it, and the fix would take 30 seconds.

   Perhaps there's a better way of dealing with this, but I don't know
   what it is.

3) I use CMU Lisp.  The version I use has a `threading' system that
   requires the USER_LDT option in the kernel.  There's also a patch
   to the kernel that's required to get this thing to work---some time
   in the 3.X series, someone made some change that caused things to
   hang under certain circumstances.  I have a small patch that I
   apply to the kernel to un-wedge this.  The patch has changed from
   3.4 to 4.0 but it's still necessary.

   In /sys/i386/i386/machdep.c, lines 604 and 605 are commented out.
   These two lines are as follows:

    regs->tf_fs = _udatasel;
    load_gs(_udatasel);

   Apparently smashing these registers is wrong.  I don't know the
   details.  If anyone is interested, there's someone on the CMUCL
   core group that knows about this.


I would appreciate it if I could know what to do about these problems
so I wouldn't have to carry patches around with me.

-Fred Gilham   gilham@csl.sri.com


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


From owner-freebsd-stable  Fri Mar 31 11:53:38 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from anchor-post-33.mail.demon.net (anchor-post-33.mail.demon.net [194.217.242.91])
	by hub.freebsd.org (Postfix) with ESMTP id 6526737B939
	for <freebsd-stable@freebsd.org>; Fri, 31 Mar 2000 11:53:32 -0800 (PST)
	(envelope-from dfr@nlsystems.com)
Received: from nlsys.demon.co.uk ([158.152.125.33] helo=herring.nlsystems.com)
	by anchor-post-33.mail.demon.net with esmtp (Exim 2.12 #1)
	id 12b7Tx-000Ps6-0X; Fri, 31 Mar 2000 20:53:25 +0100
Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3])
	by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id UAA97094;
	Fri, 31 Mar 2000 20:57:33 +0100 (BST)
	(envelope-from dfr@nlsystems.com)
Date: Fri, 31 Mar 2000 21:00:01 +0100 (BST)
From: Doug Rabson <dfr@nlsystems.com>
To: kibbet <kibbet@knfpub.com>
Cc: freebsd-stable@freebsd.org
Subject: Re: pnpparse.c
In-Reply-To: <XFMail.000401025849.kibbet@knfpub.com>
Message-ID: <Pine.BSF.4.21.0003312059240.250-100000@salmon.nlsystems.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Sat, 1 Apr 2000, kibbet wrote:

> Hi all,
> 
> The sys/isa/pnpparse.c MFC today seems to have broken things
> here with my AWE64, things were happy before the MFC, apart
> from an odd message during boot

Sorry about that. Can you try with the latest pnpparse.c.

--
Doug Rabson				Mail:  dfr@nlsystems.com
Nonlinear Systems Ltd.			Phone: +44 181 442 9037




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


From owner-freebsd-stable  Fri Mar 31 11:58:55 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
	by hub.freebsd.org (Postfix) with ESMTP
	id 30E4D37BE49; Fri, 31 Mar 2000 11:58:53 -0800 (PST)
	(envelope-from kris@FreeBSD.org)
Received: from localhost (kris@localhost)
	by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id LAA95999;
	Fri, 31 Mar 2000 11:58:52 -0800 (PST)
	(envelope-from kris@FreeBSD.org)
X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs
Date: Fri, 31 Mar 2000 11:58:51 -0800 (PST)
From: Kris Kennaway <kris@FreeBSD.org>
To: Thimble Smith <tim@mysql.com>
Cc: Siew Sim <siewsim@prismedia.com>, freebsd-stable@FreeBSD.ORG
Subject: Re: please help - thread-safe mysql client link problem
In-Reply-To: <20000331080352.G76293@threads.polyesthetic.msg>
Message-ID: <Pine.BSF.4.21.0003311157440.95920-100000@freefall.freebsd.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Fri, 31 Mar 2000, Thimble Smith wrote:

> The port doesn't have an option for building a thread-safe client,
> either (unless it's hidden somewhere that I didn't see it).

It uses the same options as the server makefile, so
'make NATIVE_THREADS=1 all install clean' should work for the client or
the server.

Kris

----
In God we Trust -- all others must submit an X.509 certificate.
    -- Charles Forsythe <forsythe@alum.mit.edu>



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


From owner-freebsd-stable  Fri Mar 31 12:10:27 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
	by hub.freebsd.org (Postfix) with ESMTP
	id 0F1DD37B652; Fri, 31 Mar 2000 12:10:26 -0800 (PST)
	(envelope-from kris@FreeBSD.org)
Received: from localhost (kris@localhost)
	by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id MAA98191;
	Fri, 31 Mar 2000 12:10:25 -0800 (PST)
	(envelope-from kris@FreeBSD.org)
X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs
Date: Fri, 31 Mar 2000 12:10:24 -0800 (PST)
From: Kris Kennaway <kris@FreeBSD.org>
To: Warner Losh <imp@village.org>
Cc: Jaye Mathisen <mrcpu@internetcds.com>, stable@FreeBSD.ORG
Subject: Re: sshd failure from Adding crypto later on -stable? 
In-Reply-To: <200003311654.JAA35682@harmony.village.org>
Message-ID: <Pine.BSF.4.21.0003311209420.96911-100000@freefall.freebsd.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Fri, 31 Mar 2000, Warner Losh wrote:

> ln -s librsaUSA.so librsaref.so
> 
> Fixed this for me.

I don't see how it could have ;) The rsaref dependency is there for a
reason, you know.

Kris

----
In God we Trust -- all others must submit an X.509 certificate.
    -- Charles Forsythe <forsythe@alum.mit.edu>



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


From owner-freebsd-stable  Fri Mar 31 12:11:16 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from horizon.barak-online.net (horizon.barak.net.il [206.49.94.218])
	by hub.freebsd.org (Postfix) with ESMTP id B021737BF8A
	for <freebsd-stable@FreeBSD.ORG>; Fri, 31 Mar 2000 12:11:10 -0800 (PST)
	(envelope-from bk532@iname.com)
Received: from localhost.local.net ([212.150.12.49])
	by horizon.barak-online.net (8.9.3/8.9.1) with ESMTP id XAA26580;
	Fri, 31 Mar 2000 23:09:41 +0300 (IDT)
Message-ID: <38E4808D.C480B276@iname.com>
Date: Fri, 31 Mar 2000 12:40:13 +0200
From: Boris Karnaukh <bk532@iname.com>
Organization: Private person
X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.4-STABLE i386)
X-Accept-Language: en, ru
MIME-Version: 1.0
To: Tim Liddelow <tim@esec.com.au>
Cc: jgarman@wedgie.org, Grigoriy Strokin <grg@philol.msu.ru>,
	Eric Jacoboni <jaco@titine.fr.eu.org>, freebsd-stable@FreeBSD.ORG
Subject: Re: New kernel with its ATA drivers damages the filesystem
References: <20000328195030.A30092@isabase.philol.msu.ru> <87ln33htuc.fsf@titine.fr.eu.org> <20000328221322.A32478@isabase.philol.msu.ru> <38E15BB9.3E3D5AF9@esec.com.au> <20000328223420.C10913@got.wedgie.org> <38E184BE.2A1EC450@esec.com.au>
Content-Type: text/plain; charset=koi8-r
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Tim Liddelow wrote:
> 
> Jason Garman wrote:
> 
> > >
> > Whats your motherboard?  I just trashed an ASUS P2V (which also has a VIA
> > chipset on it) -- same problems, under all OSes that used DMA on the
> > drive.  Unfortunate, really.  Got a new Abit BE6 instead, works like a
> > dream.  Highly recommended.
> 
> Well the motherboard is a FIC PA-2011 IIRC - I am running -current, but the
> driver is the same AFAIK.   I have put the sysctl in and am waiting to see if
> the problems recur.   Changing h/w seems a little heavy handed - I am not
> in the positition to do that right now - I'd like to see if there is a perhaps a
> software solution to this first.   Do we know for sure it is the hardware ?   Does
> Linux have problems on the same hardware ?   If I knew more about the driver
> I'd do some hacking, but I don't right now.
> 
> If this is a known problem, it should be put in a FAQ somewhere.


Well, it's well known problem. But it's related to Fujitsu hard drives
in DMA mode in case when these drives are used together with hardware
from other manufacturers. 

-- 
<Signed>
Boris Karnaukh 	(mailto:bk532@iname.com)


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


From owner-freebsd-stable  Fri Mar 31 12:56:46 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from peak.mountin.net (peak.mountin.net [207.227.119.2])
	by hub.freebsd.org (Postfix) with ESMTP id CC00337B8F0
	for <freebsd-stable@FreeBSD.ORG>; Fri, 31 Mar 2000 12:56:43 -0800 (PST)
	(envelope-from jeff-ml@mountin.net)
Received: (from daemon@localhost)
	by peak.mountin.net (8.9.1/8.9.1) id OAA08835;
	Fri, 31 Mar 2000 14:56:31 -0600 (CST)
	(envelope-from jeff-ml@mountin.net)
Received: from dial-101.max1.wa.cyberlynk.net(207.227.118.101) by peak.mountin.net via smap (V1.3)
	id sma008829; Fri Mar 31 14:56:27 2000
Message-Id: <4.3.2.20000331145402.00b52100@207.227.119.2>
X-Sender: jeff-ml@207.227.119.2
X-Mailer: QUALCOMM Windows Eudora Version 4.3
Date: Fri, 31 Mar 2000 14:55:50 -0600
To: Vivek Khera <khera@kciLink.com>, freebsd-stable@FreeBSD.ORG
From: "Jeffrey J. Mountin" <jeff-ml@mountin.net>
Subject: Re: 3.4-RELEASE; panic while paging
In-Reply-To: <14564.50142.22563.853112@onceler.kcilink.com>
References: <20000330200422.B16409@dogma.freebsd-uk.eu.org>
 <20000329175018.V15889@TK147108.telekabel.at>
 <20000329195354.A40356@walton.maths.tcd.ie>
 <20000330205606.B15889@TK147108.telekabel.at>
 <20000330200422.B16409@dogma.freebsd-uk.eu.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

At 10:27 AM 3/31/00 -0500, Vivek Khera wrote:
>I have one box that runs BSD/OS for about a week, then starts killing
>random processes for no reason.  It runs Windoze NT for about 10
>minutes (of interactive use) before it totally locks up.  It has been
>running RH Linux for about a year without a hiccup.  I have not tried
>FreeBSD on it.  Every major part in that box has been swapped out
>except the case.

The case has a curse on it then.
Consult with local practitioner for removal.
8-)


Jeff Mountin - jeff@mountin.net
Systems/Network Administrator
FreeBSD - the power to serve



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


From owner-freebsd-stable  Fri Mar 31 13:26:20 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from rover.village.org (rover.village.org [204.144.255.49])
	by hub.freebsd.org (Postfix) with ESMTP
	id 5222C37B9FC; Fri, 31 Mar 2000 13:26:16 -0800 (PST)
	(envelope-from imp@harmony.village.org)
Received: from harmony.village.org (harmony.village.org [10.0.0.6])
	by rover.village.org (8.9.3/8.9.3) with ESMTP id OAA75098;
	Fri, 31 Mar 2000 14:26:13 -0700 (MST)
	(envelope-from imp@harmony.village.org)
Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id OAA37533; Fri, 31 Mar 2000 14:25:42 -0700 (MST)
Message-Id: <200003312125.OAA37533@harmony.village.org>
To: Kris Kennaway <kris@FreeBSD.org>
Subject: Re: sshd failure from Adding crypto later on -stable? 
Cc: Jaye Mathisen <mrcpu@internetcds.com>, stable@FreeBSD.org
In-reply-to: Your message of "Fri, 31 Mar 2000 12:10:24 PST."
		<Pine.BSF.4.21.0003311209420.96911-100000@freefall.freebsd.org> 
References: <Pine.BSF.4.21.0003311209420.96911-100000@freefall.freebsd.org>  
Date: Fri, 31 Mar 2000 14:25:42 -0700
From: Warner Losh <imp@village.org>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

In message <Pine.BSF.4.21.0003311209420.96911-100000@freefall.freebsd.org> Kris Kennaway writes:
: On Fri, 31 Mar 2000, Warner Losh wrote:
: 
: > ln -s librsaUSA.so librsaref.so
: > 
: > Fixed this for me.
: 
: I don't see how it could have ;) The rsaref dependency is there for a
: reason, you know.

Well, the machine that had this problem I was installing only a
limited number of parts of the distribution.

Warner


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


From owner-freebsd-stable  Fri Mar 31 13:29:37 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from got.wedgie.org (got.wedgie.org [216.181.169.146])
	by hub.freebsd.org (Postfix) with ESMTP id C565F37BA60
	for <freebsd-stable@FreeBSD.ORG>; Fri, 31 Mar 2000 13:29:30 -0800 (PST)
	(envelope-from jgarman@got.wedgie.org)
Received: by got.wedgie.org (Postfix, from userid 1000)
	id 83A13D906; Fri, 31 Mar 2000 16:29:28 -0500 (EST)
Date: Fri, 31 Mar 2000 16:29:28 -0500
From: Jason Garman <jgarman@wedgie.org>
To: Boris Karnaukh <bk532@iname.com>
Cc: Tim Liddelow <tim@esec.com.au>,
	Grigoriy Strokin <grg@philol.msu.ru>,
	Eric Jacoboni <jaco@titine.fr.eu.org>, freebsd-stable@FreeBSD.ORG
Subject: Re: New kernel with its ATA drivers damages the filesystem
Message-ID: <20000331162928.A24581@got.wedgie.org>
Reply-To: jgarman@wedgie.org
References: <20000328195030.A30092@isabase.philol.msu.ru> <87ln33htuc.fsf@titine.fr.eu.org> <20000328221322.A32478@isabase.philol.msu.ru> <38E15BB9.3E3D5AF9@esec.com.au> <20000328223420.C10913@got.wedgie.org> <38E184BE.2A1EC450@esec.com.au> <38E4808D.C480B276@iname.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.4i
In-Reply-To: <38E4808D.C480B276@iname.com>; from Boris Karnaukh on Fri, Mar 31, 2000 at 12:40:13PM +0200
X-Phase-Of-Moon: The Moon is Waning Crescent (17% of Full)
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Fri, Mar 31, 2000 at 12:40:13PM +0200, Boris Karnaukh wrote:
> 
> Well, it's well known problem. But it's related to Fujitsu hard drives
> in DMA mode in case when these drives are used together with hardware
> from other manufacturers. 
> 
The hard drives I tested my VIA chipset with were both IBM drives, one a
10gb 7200rpm model and one a 15gb 5400rpm model.  The 15gb is :

ad4: 14664MB <IBM-DJNA-351520> [29795/16/63] at ata2-master using UDMA66

i don't have a model number for the 10gb off hand.  

Data corruption occured on these drives with the VIA chipset, but are
working fine with both the PIIX4 and HighPoint controllers on the BE6
board.

enjoy
-- 
Jason Garman                                         http://web.wedgie.org/
Student, University of Maryland                          jgarman@wedgie.org
From fortune(1):                                              Whois: JAG145
  "... Had this been an actual emergency, we would have fled in terror,
   and you would not have been informed."


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


From owner-freebsd-stable  Fri Mar 31 13:34:41 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
	by hub.freebsd.org (Postfix) with ESMTP
	id 8B73A37BA8F; Fri, 31 Mar 2000 13:34:38 -0800 (PST)
	(envelope-from kris@FreeBSD.org)
Received: from localhost (kris@localhost)
	by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id NAA17347;
	Fri, 31 Mar 2000 13:34:38 -0800 (PST)
	(envelope-from kris@FreeBSD.org)
X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs
Date: Fri, 31 Mar 2000 13:34:37 -0800 (PST)
From: Kris Kennaway <kris@FreeBSD.org>
To: Warner Losh <imp@village.org>
Cc: Jaye Mathisen <mrcpu@internetcds.com>, stable@FreeBSD.org
Subject: Re: sshd failure from Adding crypto later on -stable? 
In-Reply-To: <200003312125.OAA37533@harmony.village.org>
Message-ID: <Pine.BSF.4.21.0003311333500.17071-100000@freefall.freebsd.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Fri, 31 Mar 2000, Warner Losh wrote:

> : I don't see how it could have ;) The rsaref dependency is there for a
> : reason, you know.
> 
> Well, the machine that had this problem I was installing only a
> limited number of parts of the distribution.

Still, ssh would have been nonfunctional with this change :-)

Kris

----
In God we Trust -- all others must submit an X.509 certificate.
    -- Charles Forsythe <forsythe@alum.mit.edu>



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


From owner-freebsd-stable  Fri Mar 31 13:35:34 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from got.wedgie.org (got.wedgie.org [216.181.169.146])
	by hub.freebsd.org (Postfix) with ESMTP id 8CA6A37BDEC
	for <freebsd-stable@FreeBSD.ORG>; Fri, 31 Mar 2000 13:35:29 -0800 (PST)
	(envelope-from jgarman@got.wedgie.org)
Received: by got.wedgie.org (Postfix, from userid 1000)
	id 49856D906; Fri, 31 Mar 2000 16:35:27 -0500 (EST)
Date: Fri, 31 Mar 2000 16:35:27 -0500
From: Jason Garman <jgarman@wedgie.org>
To: =?iso-8859-1?Q?Thomas_K=F6llmann?= <koellmann@gmx.net>
Cc: Grigoriy Strokin <grg@philol.msu.ru>, freebsd-stable@FreeBSD.ORG
Subject: Re: New kernel with its ATA drivers damages the filesystem
Message-ID: <20000331163527.B24581@got.wedgie.org>
Reply-To: jgarman@wedgie.org
References: <20000331022130.A4045@isabase.philol.msu.ru> <20000331142357.A1291@home.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Mailer: Mutt 0.95.4i
In-Reply-To: =?iso-8859-1?Q?=3C20000331142357=2EA1291=40home=2Enet=3E=3B_from_Thomas_?=
 =?iso-8859-1?Q?K=F6llmann_on_Fri=2C_Mar_31=2C_2000_at_02:23:57PM_+0200?=
X-Phase-Of-Moon: The Moon is Waning Crescent (17% of Full)
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Fri, Mar 31, 2000 at 02:23:57PM +0200, Thomas Köllmann wrote:
> 
> Please excuse if this was mentioned before (I did not follow this
> thread very closely), but isn't _not_ using
> 
> 	options		ATA_ENABLE_ATAPI_DMA
> 
> enough as a measure of precaution?
> 
> This is from LINT:
> 
> # ATA_ENABLE_ATAPI_DMA: enable DMA on ATAPI device, since many ATAPI
> # devices claim to support DMA but doesn't actually work, this is
> # not enabled as default.
> 
Note there is a subtle distinction between ATAPI devices and ATA hard
disks. The devices which that option disables DMA for are devices like
CD-ROMs, IDE zip drives, etc. -- NOT normal IDE hard drives -- they use
DMA with the new driver regardless of that setting.

enjoy
-- 
Jason Garman                                         http://web.wedgie.org/
Student, University of Maryland                          jgarman@wedgie.org
From fortune(1):                                              Whois: JAG145
  "... Had this been an actual emergency, we would have fled in terror,
   and you would not have been informed."


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


From owner-freebsd-stable  Fri Mar 31 13:37:40 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from rover.village.org (rover.village.org [204.144.255.49])
	by hub.freebsd.org (Postfix) with ESMTP
	id 4869B37BB05; Fri, 31 Mar 2000 13:37:35 -0800 (PST)
	(envelope-from imp@harmony.village.org)
Received: from harmony.village.org (harmony.village.org [10.0.0.6])
	by rover.village.org (8.9.3/8.9.3) with ESMTP id OAA75161;
	Fri, 31 Mar 2000 14:37:33 -0700 (MST)
	(envelope-from imp@harmony.village.org)
Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id OAA37667; Fri, 31 Mar 2000 14:37:04 -0700 (MST)
Message-Id: <200003312137.OAA37667@harmony.village.org>
To: Kris Kennaway <kris@FreeBSD.org>
Subject: Re: sshd failure from Adding crypto later on -stable? 
Cc: Jaye Mathisen <mrcpu@internetcds.com>, stable@FreeBSD.org
In-reply-to: Your message of "Fri, 31 Mar 2000 13:34:37 PST."
		<Pine.BSF.4.21.0003311333500.17071-100000@freefall.freebsd.org> 
References: <Pine.BSF.4.21.0003311333500.17071-100000@freefall.freebsd.org>  
Date: Fri, 31 Mar 2000 14:37:04 -0700
From: Warner Losh <imp@village.org>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

In message <Pine.BSF.4.21.0003311333500.17071-100000@freefall.freebsd.org> Kris Kennaway writes:
: On Fri, 31 Mar 2000, Warner Losh wrote:
: 
: > : I don't see how it could have ;) The rsaref dependency is there for a
: > : reason, you know.
: > 
: > Well, the machine that had this problem I was installing only a
: > limited number of parts of the distribution.
: 
: Still, ssh would have been nonfunctional with this change :-)

That's what got ssh working.

Warner


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


From owner-freebsd-stable  Fri Mar 31 13:40:41 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from isabase.philol.msu.ru (isabase.philol.msu.ru [195.208.217.73])
	by hub.freebsd.org (Postfix) with ESMTP id 75A4F37C362
	for <freebsd-stable@FreeBSD.ORG>; Fri, 31 Mar 2000 13:40:35 -0800 (PST)
	(envelope-from grg@isabase.philol.msu.ru)
Received: (from grg@localhost)
	by isabase.philol.msu.ru (8.9.3/8.9.2) id BAA48308;
	Sat, 1 Apr 2000 01:39:59 +0400 (MSD)
	(envelope-from grg)
Date: Sat, 1 Apr 2000 01:39:59 +0400
From: Grigoriy Strokin <grg@philol.msu.ru>
To: Jason Garman <jgarman@wedgie.org>
Cc: Thomas K?llmann <koellmann@gmx.net>,
	Grigoriy Strokin <grg@philol.msu.ru>, freebsd-stable@FreeBSD.ORG
Subject: Re: New kernel with its ATA drivers damages the filesystem
Message-ID: <20000401013959.A48268@isabase.philol.msu.ru>
References: <20000331022130.A4045@isabase.philol.msu.ru> <20000331142357.A1291@home.net> <20000331163527.B24581@got.wedgie.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0.1i
In-Reply-To: <20000331163527.B24581@got.wedgie.org>; from jgarman@wedgie.org on Fri, Mar 31, 2000 at 04:35:27PM -0500
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Fri, Mar 31, 2000 at 04:35:27PM -0500, Jason Garman wrote:
> On Fri, Mar 31, 2000 at 02:23:57PM +0200, Thomas K?llmann wrote:
> > 
> > Please excuse if this was mentioned before (I did not follow this
> > thread very closely), but isn't _not_ using
> > 
> > 	options		ATA_ENABLE_ATAPI_DMA
> > 
> > enough as a measure of precaution?
> > 
> > This is from LINT:
> > 
> > # ATA_ENABLE_ATAPI_DMA: enable DMA on ATAPI device, since many ATAPI
> > # devices claim to support DMA but doesn't actually work, this is
> > # not enabled as default.
> > 
> Note there is a subtle distinction between ATAPI devices and ATA hard
> disks. The devices which that option disables DMA for are devices like
> CD-ROMs, IDE zip drives, etc. -- NOT normal IDE hard drives -- they use
> DMA with the new driver regardless of that setting.
> 
Interestingly, commenting out this option doesn't affect the mode for my CD-ROM
either.

   sysctl reports
     hw.atamodes: dma,---,dma,---,

First dma is for ad0, second for acd0.

And dmesg reports using UDMA-33 for CDROM, too.

acd0: CDROM <FX4010M> at ata1-master using UDMA33



-- 
=== Grigoriy Strokin, Lomonosov University (MGU), Moscow ===
=== contact info: http://isabase.philol.msu.ru/~grg/     ===


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


From owner-freebsd-stable  Fri Mar 31 13:50:14 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
	by hub.freebsd.org (Postfix) with ESMTP
	id 51B8437BA8F; Fri, 31 Mar 2000 13:50:11 -0800 (PST)
	(envelope-from kris@FreeBSD.org)
Received: from localhost (kris@localhost)
	by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id NAA21110;
	Fri, 31 Mar 2000 13:50:11 -0800 (PST)
	(envelope-from kris@FreeBSD.org)
X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs
Date: Fri, 31 Mar 2000 13:50:11 -0800 (PST)
From: Kris Kennaway <kris@FreeBSD.org>
To: Warner Losh <imp@village.org>
Cc: Jaye Mathisen <mrcpu@internetcds.com>, stable@FreeBSD.org
Subject: Re: sshd failure from Adding crypto later on -stable? 
In-Reply-To: <200003312137.OAA37667@harmony.village.org>
Message-ID: <Pine.BSF.4.21.0003311348420.20593-100000@freefall.freebsd.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Fri, 31 Mar 2000, Warner Losh wrote:

> : Still, ssh would have been nonfunctional with this change :-)
> 
> That's what got ssh working.

Hrm. I'm at a loss as to how - you did have librsaref installed,
right? dlopen() should have found that one, and if it instead picked up
the symlinked version in /usr/lib it wouldn't be able to call the RSA
functions in rsaref.

Kris

----
In God we Trust -- all others must submit an X.509 certificate.
    -- Charles Forsythe <forsythe@alum.mit.edu>



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


From owner-freebsd-stable  Fri Mar 31 13:54:59 2000
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 7039837BF15; Fri, 31 Mar 2000 13:54:53 -0800 (PST)
	(envelope-from dwmalone@maths.tcd.ie)
Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP
          id <aa61319@salmon>; 31 Mar 2000 22:54:37 +0100 (BST)
To: Rici Lake <rlake@oxfam.org.pe>
Cc: Jeff Hamilton <hjeffrey@hotmail.com>,
	freebsd-questions@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG
Subject: Re: portmap in hosts.allow configuration notes. Was Re: /etc/hosts.allow 
In-reply-to: Your message of "Fri, 31 Mar 2000 13:11:06 CDT."
             <Pine.LNX.4.05.10003311059380.8417-100000@rlake.oxfam.org.pe> 
X-Request-Do: 
Date: Fri, 31 Mar 2000 22:54:37 +0100
From: David Malone <dwmalone@maths.tcd.ie>
Message-ID:  <200003312254.aa61319@salmon.maths.tcd.ie>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> The twist option cannot work other than in inetd mode. It causes the
> calling process to be replaced (through the execl(3) system call) with an
> configured shell process. If the calling process intended to hang around
> for a while to answer more requests, it's in for a surprise.

The wrapper library has a variable "resident". It looks like can
be set to indicate that your are a process like portmap, sshd or
sendmail, who doesn't want to be execed out of existance. I guess 
this should be set in these programs before any wrapper stuff is
called - I haven't checked to see if it is, but I'll have a look.

	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 31 14:19:14 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from mail.oxfam.org.uk (mail.oxfam.org.uk [195.153.200.167])
	by hub.freebsd.org (Postfix) with ESMTP
	id CEAD337B913; Fri, 31 Mar 2000 14:19:05 -0800 (PST)
	(envelope-from rlake@oxfam.org.pe)
Received: from rlake.oxfam.org.pe (root@[209.45.73.61])
	by mail.oxfam.org.uk (8.9.3/8.8.5) with ESMTP id XAA02477;
	Fri, 31 Mar 2000 23:24:50 GMT
Received: from localhost (rlake@localhost [127.0.0.1])
	by rlake.oxfam.org.pe (8.8.8/8.8.8) with ESMTP id RAA00285;
	Fri, 31 Mar 2000 17:13:00 -0500
Date: Fri, 31 Mar 2000 17:12:59 -0500 (PET)
From: Rici Lake <rlake@oxfam.org.pe>
To: David Malone <dwmalone@maths.tcd.ie>
Cc: Jeff Hamilton <hjeffrey@hotmail.com>,
	freebsd-questions@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG
Subject: Re: portmap in hosts.allow configuration notes. Was Re: /etc/hosts.allow
In-Reply-To: <200003312254.aa61319@salmon.maths.tcd.ie>
Message-ID: <Pine.LNX.4.05.10003311652390.245-100000@rlake.oxfam.org.pe>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG



On Fri, 31 Mar 2000, David Malone wrote:

> > The twist option cannot work other than in inetd mode. It causes the
> > calling process to be replaced (through the execl(3) system call) with an
> > configured shell process. If the calling process intended to hang around
> > for a while to answer more requests, it's in for a surprise.
> 
> The wrapper library has a variable "resident". It looks like can
> be set to indicate that your are a process like portmap, sshd or
> sendmail, who doesn't want to be execed out of existance. I guess 
> this should be set in these programs before any wrapper stuff is
> called - I haven't checked to see if it is, but I'll have a look.

Yeah, it does. I think you probably could get away with just setting it to
1... from the code, it looks like that would work.

However, it does that all by itself. The variable starts at -1, and then
it increments it every time it does a check. "Normally", it's called from
inetd, so it's only called once and so resident never ascends beyond 0. If
you're running some long-standing service which calls the wrapper lib more
often, the variable gets incremented past 0 and the library knows that
it's there to stay. Then it bans twists.

However, this is not part of the public interface. So no-one is going to
use that.

If you look more closely at the code, you'll see that the request object
has a fd member (oops, in c-speak, I mean there's an fd in the request
struct. Well, you know what I mean, I hope). That's initialised to -1 when
you create the request. Then you eventually get around to setting it if
you use the full-bore API to the wrapper library, if you want to.
Normally, you wouldn't: I would think that handing the wrapper library the
fd for the socket connection would be an invitation to it to do something
like a twist. In other words, if you give it an fd, you should expect that
it might not return.

However, the simple API doesn't have any way of setting that field, so
it's going to stay -1. Inetd, on the other hand, is always going to set
it.

Now the whole point of doing twist echo "Go away, you're bugging me" is to
stuff that string down the throat of the socket. It only makes sense to
twist if you've got a socket to twist with. So checking the fd for being
-1 before you try to twist has got to be the Right Thing to Do. And that
would go along with all the other socket related options: banner, set
linger, etc.

If you don't have a socket, you should still be able to allow, deny, and
set logging priority.

So I think that would pretty well cover it -- and it would only mean one
check for (fd == -1) in each option.

I'm going to make that change on my machine, anyway -- but I'm not
actually running STABLE any more 'cause I don't feel like upgrading to 4.0
just now (and, to be honest, I've only been FreeBSDing for about a month.)
I'm in the middle of writing a libwrappers map for sendmail, if that makes
any sense, so I'm sort of immersed in the code at the moment.

If there's something I should do with the patch that would be useful to
someone, I'm more than happy to share. But obviously, I'm not a FreeBSD
insider.

R.





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


From owner-freebsd-stable  Fri Mar 31 15:10:40 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from mail.ddg.com (eunuch.ddg.com [216.30.58.66])
	by hub.freebsd.org (Postfix) with ESMTP id 48ED137B53A
	for <freebsd-stable@FreeBSD.ORG>; Fri, 31 Mar 2000 15:10:27 -0800 (PST)
	(envelope-from rkw@dataplex.net)
Received: from nomad.dataplex.net (24.28.73.209) by mail.ddg.com with SMTP
 (Eudora Internet Mail Server 2.1); Fri, 31 Mar 2000 17:10:20 -0600
From: Richard Wackerbarth <rkw@dataplex.net>
To: jcm@freebsd-uk.eu.org
Subject: Re: Stability and versions - was Re: Let 3.x die ASAP?
Date: Fri, 31 Mar 2000 16:43:02 -0600
X-Mailer: KMail [version 1.0.29]
Content-Type: text/plain
Cc: freebsd-stable@FreeBSD.ORG
References: <XFMail.000330214705.steveo@eircom.net> <20000331153137.C21703@dogma.freebsd-uk.eu.org>
In-Reply-To: <20000331153137.C21703@dogma.freebsd-uk.eu.org>
MIME-Version: 1.0
Message-Id: <00033117101800.06684@nomad.dataplex.net>
Content-Transfer-Encoding: 8bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Fri, 31 Mar 2000, J McKitrick wrote:
> "STABLE" refers to the code base, NOT the stability of systems running
> it.
> Simple concept, deep meaning.  Newbies should understand  ...

And therein lies the problem. Newbies don't understand much of anything
about this (or any other) project. The approach with the "common English",
(or French, German, etc.) point of view. If they, for whatever reason, select
an inappropriate branch, they are very likely to conclude that FreeBSD is
a "toy" or otherwise non-serious project and turn their attention to another
system. This further hurts FreeBSD because they will also spread word of
their poor experience to others.

As has often been said, "You only get one chance to make a good first
impression". Unless the developers wake up and realize that "market share"
is important and take steps to improve it, FreeBSD will continue to be a "back
water" inconsequential sand box. We desperately need more companies to 
consider FreeBSD as their first choice for corporate servers.
Market share is significantly affected by first impressions. We need to do
EVERYTHING possible to make that first experience a good one -- 
Especially when it doesn't affect the ultimate performance of the system.

Quit thinking of FreeBSD from the developer's point of view. Think of it
from the new user's viewpoint. Give them what they expect. The developers
are better capable of adapting. And any "fossils" who want to argue "we've
always done it that way" need to move over. OS's today are not what they
were five, much less thirty, years ago. If you want things like they used to be,
stick with BSD 4.4 (if you can still find any hardware to run it) and program
in COBOL.



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


From owner-freebsd-stable  Fri Mar 31 15:16:50 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from serenity.mcc.ac.uk (serenity.mcc.ac.uk [130.88.200.93])
	by hub.freebsd.org (Postfix) with ESMTP id 51AD237B86A
	for <freebsd-stable@freebsd.org>; Fri, 31 Mar 2000 15:16:38 -0800 (PST)
	(envelope-from jcm@dogma.freebsd-uk.eu.org)
Received: from dogma.freebsd-uk.eu.org ([130.88.200.97])
	by serenity.mcc.ac.uk with esmtp (Exim 1.92 #3)
	id 12bAea-000L1o-00; Sat, 1 Apr 2000 00:16:36 +0100
Received: (from jcm@localhost)
	by dogma.freebsd-uk.eu.org (8.9.3/8.9.3) id AAA25467;
	Sat, 1 Apr 2000 00:16:36 +0100 (BST)
	(envelope-from jcm)
Date: Sat, 1 Apr 2000 00:16:36 +0100
From: J McKitrick <jcm@freebsd-uk.eu.org>
To: Richard Wackerbarth <rkw@dataplex.net>
Cc: freebsd-stable@freebsd.org
Subject: Re: Stability and versions - was Re: Let 3.x die ASAP?
Message-ID: <20000401001635.A25259@dogma.freebsd-uk.eu.org>
References: <XFMail.000330214705.steveo@eircom.net> <20000331153137.C21703@dogma.freebsd-uk.eu.org> <00033117101800.06684@nomad.dataplex.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0.1i
In-Reply-To: <00033117101800.06684@nomad.dataplex.net>; from rkw@dataplex.net on Fri, Mar 31, 2000 at 04:43:02PM -0600
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

I think one simple solution is to 'hide' the -current distro, or make
it a little less accessible.  That seems like a good first step.  No
one who can't figure it out needs tobe running it anyway, and it
certainly won't hurt the development effort.  Then, of course, keep
whipping 4.x into shape, tack on a decent, if not graphical, interface
and let it sell itself.  Er, raher, give itself away.

jm
-- 
--------------------------------------------
Jonathon McKitrick -- jcm@freebsd-uk.eu.org 
"You're the guy from the Hambuger Train, right?"
--------------------------------------------


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


From owner-freebsd-stable  Fri Mar 31 16:49:45 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from po4.glue.umd.edu (po4.glue.umd.edu [128.8.10.124])
	by hub.freebsd.org (Postfix) with ESMTP id 4A1B637B6EE
	for <freebsd-stable@FreeBSD.ORG>; Fri, 31 Mar 2000 16:49:41 -0800 (PST)
	(envelope-from bfoz@glue.umd.edu)
Received: from glue.umd.edu (poseidon.student.umd.edu [129.2.220.99])
	by po4.glue.umd.edu (8.9.3/8.9.3) with ESMTP id TAA12176;
	Fri, 31 Mar 2000 19:49:28 -0500 (EST)
Message-ID: <38E54797.42DF0CD3@glue.umd.edu>
Date: Fri, 31 Mar 2000 19:49:27 -0500
From: Brandon Fosdick <bfoz@glue.umd.edu>
X-Mailer: Mozilla 4.7 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Thomas =?iso-8859-1?Q?K=F6llmann?= <koellmann@gmx.net>
Cc: Grigoriy Strokin <grg@philol.msu.ru>, freebsd-stable@FreeBSD.ORG
Subject: Re: New kernel with its ATA drivers damages the filesystem
References: <20000331022130.A4045@isabase.philol.msu.ru> <20000331142357.A1291@home.net>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Thomas Köllmann wrote:
> 
> Grigoriy Strokin wrote/schrieb (Friday, March 31, 2000):
> 
> | While the bug wiping out filesystems on machines with Apollo MVP3 when ATA
> | driver is in UDMA mode is being fixed, I suppose there at least should be some
> | note added to /usr/src/UPDATING, so that another users do not loss
> | all their data and have to reinitialize /usr and restore it from backup, as I
> | had to do?
> |
> | Something like that:
> |
> |     If you use the Apollo MVP3 chipset, it is STRONGLY
> |     recommended that you disable the use of DMA mode in ATA drivers
> |     BEFORE you try to boot the system after `make installkernel'.
> |     Add the following line:
> |       /sbin/sysctl -w hw.atamodes=pio,pio,pio,pio
> |     to the very beginning of your /etc/rc,
> |     ~root/.profile and ~root/.login.
> |     Be warned that if you don't disable the DMA mode,
> |     all your filesystems may be corrupted because
> |     of a bug in the driver that is still being fixed.
> |
> 
> Please excuse if this was mentioned before (I did not follow this
> thread very closely), but isn't _not_ using
> 
>         options         ATA_ENABLE_ATAPI_DMA
> 
> enough as a measure of precaution?
> 
> This is from LINT:
> 
> # ATA_ENABLE_ATAPI_DMA: enable DMA on ATAPI device, since many ATAPI
> # devices claim to support DMA but doesn't actually work, this is
> # not enabled as default.
> 
> Gruß
>  - Thomas


I missed the first part of this thread but I wish I hadn't cause my filesystem
has been trashed twice in as many days. The first time I was doing 'chown -R'
and the kernel paniced, rebooted to lots of fsck errors. Not only was the
directory I was chown'ing trashed, but several others as well (/usr/src,
/usr/ports). Then second time I was doing 'rm -r' and the same thing happened,
but I lost most of my home dir too.

I have a P3-600 on an Asus P3B-F with a Maxtor 20GB HDD(UDMA/33). Everything
worked fine under 3.4.

Thanks,
Brandon

-- 
bfoz@glue.umd.edu
"Lead, follow, or get run over"
"In life there are those who steer, and those who push"
"I'm not impatient, the world is too slow"
"Life is short, so have fun, play hard, and leave a good looking corpse"


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


From owner-freebsd-stable  Fri Mar 31 17:39:56 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from rover.village.org (rover.village.org [204.144.255.49])
	by hub.freebsd.org (Postfix) with ESMTP
	id D45E737BA58; Fri, 31 Mar 2000 17:39:49 -0800 (PST)
	(envelope-from imp@harmony.village.org)
Received: from harmony.village.org (harmony.village.org [10.0.0.6])
	by rover.village.org (8.9.3/8.9.3) with ESMTP id SAA75806;
	Fri, 31 Mar 2000 18:39:44 -0700 (MST)
	(envelope-from imp@harmony.village.org)
Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id SAA38947; Fri, 31 Mar 2000 18:39:10 -0700 (MST)
Message-Id: <200004010139.SAA38947@harmony.village.org>
To: Kris Kennaway <kris@FreeBSD.ORG>
Subject: Re: sshd failure from Adding crypto later on -stable? 
Cc: Jaye Mathisen <mrcpu@internetcds.com>, stable@FreeBSD.ORG
In-reply-to: Your message of "Fri, 31 Mar 2000 13:50:11 PST."
		<Pine.BSF.4.21.0003311348420.20593-100000@freefall.freebsd.org> 
References: <Pine.BSF.4.21.0003311348420.20593-100000@freefall.freebsd.org>  
Date: Fri, 31 Mar 2000 18:39:10 -0700
From: Warner Losh <imp@village.org>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

In message <Pine.BSF.4.21.0003311348420.20593-100000@freefall.freebsd.org> Kris Kennaway writes:
: Hrm. I'm at a loss as to how - you did have librsaref installed,
: right? dlopen() should have found that one, and if it instead picked up
: the symlinked version in /usr/lib it wouldn't be able to call the RSA
: functions in rsaref.

There was no librsaref.so.  Just a librsaUSA.so.  So I created a
symlink from librsaref.so -> librsaUSA.so.  ssh seems to work after
the change.

Warner


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


From owner-freebsd-stable  Fri Mar 31 17:41:17 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from rover.village.org (rover.village.org [204.144.255.49])
	by hub.freebsd.org (Postfix) with ESMTP id 531DC37BF14
	for <stable@FreeBSD.ORG>; Fri, 31 Mar 2000 17:41:09 -0800 (PST)
	(envelope-from imp@harmony.village.org)
Received: from harmony.village.org (harmony.village.org [10.0.0.6])
	by rover.village.org (8.9.3/8.9.3) with ESMTP id SAA75826;
	Fri, 31 Mar 2000 18:41:08 -0700 (MST)
	(envelope-from imp@harmony.village.org)
Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id SAA38998; Fri, 31 Mar 2000 18:40:38 -0700 (MST)
Message-Id: <200004010140.SAA38998@harmony.village.org>
To: Alexander Frolkin <alexander@frolkin.demon.co.uk>
Subject: Re: Upgrading to 4.0 
Cc: stable@FreeBSD.ORG
In-reply-to: Your message of "Fri, 31 Mar 2000 19:03:29 +0100."
		<20000331190328.A4215@gamma> 
References: <20000331190328.A4215@gamma>  
Date: Fri, 31 Mar 2000 18:40:38 -0700
From: Warner Losh <imp@village.org>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

In message <20000331190328.A4215@gamma> Alexander Frolkin writes:
: AFAIK, it is necessary to install a 4.0 kernel before doing installworld.
: According to src/UPDATING, pccardd needs to be recompiled to work with the
: new kernel. The problem is that /usr/obj and /usr/src will be NFS mounted,
: and the network card is a PCMCIA NE2000. Can I just build and install the
: new pccardd and then reboot, or is there something else I will need to do?

Yes.  build and install the new kernel, build and install the new
pccardd (with the new pccard include files, so as part of make
buildworld is the best way to build it).  Then it should be safe to
reboot.  Keep a copy of the old pccardd and old kernel around just in
case you botch something.

Warner


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


From owner-freebsd-stable  Fri Mar 31 17:47: 8 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from rover.village.org (rover.village.org [204.144.255.49])
	by hub.freebsd.org (Postfix) with ESMTP id 0A65437B85D
	for <freebsd-stable@FreeBSD.ORG>; Fri, 31 Mar 2000 17:47:03 -0800 (PST)
	(envelope-from imp@harmony.village.org)
Received: from harmony.village.org (harmony.village.org [10.0.0.6])
	by rover.village.org (8.9.3/8.9.3) with ESMTP id SAA75927;
	Fri, 31 Mar 2000 18:46:58 -0700 (MST)
	(envelope-from imp@harmony.village.org)
Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id SAA39067; Fri, 31 Mar 2000 18:46:28 -0700 (MST)
Message-Id: <200004010146.SAA39067@harmony.village.org>
To: Grigoriy Strokin <grg@philol.msu.ru>
Subject: Re: Audio record problems in 4.0-STABLE: 1. Creative ViBRA16X 
Cc: freebsd-stable@FreeBSD.ORG
In-reply-to: Your message of "Fri, 31 Mar 2000 02:05:42 +0400."
		<20000331020541.A3613@isabase.philol.msu.ru> 
References: <20000331020541.A3613@isabase.philol.msu.ru>  <20000326200211.A6863@isabase.philol.msu.ru> 
Date: Fri, 31 Mar 2000 18:46:28 -0700
From: Warner Losh <imp@village.org>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

In message <20000331020541.A3613@isabase.philol.msu.ru> Grigoriy Strokin writes:
: While the bug wiping out filesystems on machines with Apollo MVP3 when ATA
: driver is in UDMA mode is being fixed, I suppose there at least should be some
: note added to /usr/src/UPDATING, so that another users do not loss
: all their data and have to reinitialize /usr and restore it from backup, as I
: had to do?
: 
: Something like that:
:     If you use the Apollo MVP3 chipset, it is STRONGLY
:     recommended that you disable the use of DMA mode in ATA drivers
:     BEFORE you try to boot the system after `make installworld'.
:     Add the following line:
:       /sbin/sysctl -w hw.atamodes=pio,pio,pio,pio
:     to the very beginning of your /etc/rc,
:     ~root/.profile and ~root/.login.
:     Be warned that if you don't disable the DMA mode,
:     all your filesystems may be corrupted because
:     of a bug in the driver that is still being fixed.

How about

QUIRKS:
	The ata driver has some issues with the Apollo MVP3 chipset.
	Drives work only in pio mode and must be set to pio mode early
	int the boot process.  Do not upgrade.  If you must upgrade
	in the face of this, add
		/sbin/sysctl -w hw.atamodes=pio,pio,pio,pio
	to the start of /etc/rc.conf.  Even if you do this, any and
	all damage to your system is at your own risk.  You have been
	warned.

Warner


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


From owner-freebsd-stable  Fri Mar 31 17:58:33 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from mail.hcisp.net (Stargate.hcisp.net [208.60.89.18])
	by hub.freebsd.org (Postfix) with SMTP id 008AD37BA16
	for <freebsd-stable@FreeBSD.org>; Fri, 31 Mar 2000 17:58:25 -0800 (PST)
	(envelope-from tim@mysql.com)
Received: (qmail 1300 invoked from network); 1 Apr 2000 02:06:54 -0000
Received: from modem1.hcisp.net (HELO threads.polyesthetic.msg) (208.60.89.67)
  by stargate.hcisp.net with SMTP; 1 Apr 2000 02:06:54 -0000
Received: (qmail 52307 invoked by uid 1001); 1 Apr 2000 01:57:28 -0000
From: "Thimble Smith" <tim@mysql.com>
Date: Fri, 31 Mar 2000 20:57:28 -0500
To: Kris Kennaway <kris@FreeBSD.org>, dirk@FreeBSD.org
Cc: freebsd-stable@FreeBSD.org
Subject: Re: please help - thread-safe mysql client link problem
Message-ID: <20000331205728.B15870@threads.polyesthetic.msg>
References: <20000331080352.G76293@threads.polyesthetic.msg> <Pine.BSF.4.21.0003311157440.95920-100000@freefall.freebsd.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0.1i
In-Reply-To: <Pine.BSF.4.21.0003311157440.95920-100000@freefall.freebsd.org>; from kris@FreeBSD.org on Fri, Mar 31, 2000 at 11:58:51AM -0800
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Fri, Mar 31, 2000 at 11:58:51AM -0800, Kris Kennaway wrote:
>On Fri, 31 Mar 2000, Thimble Smith wrote:
>> The port doesn't have an option for building a thread-safe client,
>> either (unless it's hidden somewhere that I didn't see it).
>
>It uses the same options as the server makefile, so
>'make NATIVE_THREADS=1 all install clean' should work for the client or
>the server.

MySQL doesn't make thread-safe client libs unless you pass the
--enable-thread-safe-client flag to configure.  Here'a a patch
to mysql322-server/Makefile that will cause this to happen if
THREAD_SAFE_CLIENT is set in the environment:


--- Makefile.orig	Fri Mar 31 20:17:25 2000
+++ Makefile	Fri Mar 31 20:53:30 2000
@@ -34,11 +34,10 @@
 		INSTALL_SCRIPT="${INSTALL_SCRIPT}" \
 		CONFIGURE_ARGS="${CONFIGURE_ARGS}"
 
-.if !defined(CLIENT_ONLY)
-RUN_DEPENDS=	mysql:${PORTSDIR}/databases/mysql322-client
-
 .include <bsd.port.pre.mk>
 
+.if !defined(CLIENT_ONLY) || defined(THREAD_SAFE_CLIENT)
+
 .if ${OSVERSION} >= 320000
 .if defined(MIT_PTHREADS)
 CONFIGURE_ARGS+=	--with-mit-threads=yes
@@ -90,6 +89,11 @@
 	@${ECHO}
 .endif
 
+.endif # !CLIENT_ONLY || THREAD_SAFE_CLIENT
+
+.if !defined(CLIENT_ONLY)
+RUN_DEPENDS=	mysql:${PORTSDIR}/databases/mysql322-client
+
 post-patch:
 	${MV} ${WRKSRC}/strings/strings-x86.s ${WRKSRC}/strings/strings-x86.S
 	${MV} ${WRKSRC}/strings/longlong2str-x86.s ${WRKSRC}/strings/longlong2str-x86.S
@@ -140,6 +144,17 @@
 .else
 MAN1=		mysql.1
 
+.if defined(THREAD_SAFE_CLIENT)
+CONFIGURE_ARGS+=--enable-thread-safe-client
+.else
+pre-fetch:
+	@${ECHO} ""
+	@${ECHO} "You may set THREAD_SAFE_CLIENT (make THREAD_SAFE_CLIENT=yes)"
+	@${ECHO} "to compile a thread-safe libmysqlclient.  (You should not"
+	@${ECHO} "do this unless you are linking with threaded applications.)"
+	@${ECHO} ""
+.endif
+
 CONFIGURE_ARGS+=--without-server
 MAKE_ENV=	CLIENT_ONLY="${CLIENT_ONLY}"
 
@@ -151,5 +166,5 @@
 
 	${SETENV} OBJFORMAT=${PORTOBJFORMAT} ${LDCONFIG} -m ${PREFIX}/lib/mysql
 
-.include <bsd.port.mk>
+.include <bsd.port.post.mk>
 .endif


I'm not super-familiar with the ports structure, so I may have
botched something.  Dirk, if this looks okay (or can be salvaged
into something that is okay), could you commit it?

Thanks,

Tim
-- 
Tim Smith   < tim@mysql.com >  :MySQL Development Team:  Boone, NC  USA.


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


From owner-freebsd-stable  Fri Mar 31 17:58:44 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from shell.lomag.net (ircd.lomag.net [205.134.180.132])
	by hub.freebsd.org (Postfix) with ESMTP id 6DA6A37B7E3
	for <freebsd-stable@freebsd.org>; Fri, 31 Mar 2000 17:58:28 -0800 (PST)
	(envelope-from mark@lomag.net)
Received: from lomag.net (stevio@ws01.lomag.net [64.19.154.210])
        by shell.lomag.net with ESMTP id UAA28704
	for <freebsd-stable@freebsd.org>; Fri, 31 Mar 2000 20:58:25 -0500 (EST)
	(envelope-from mark@lomag.net)
Message-ID: <38E557DA.31465732@lomag.net>
Date: Fri, 31 Mar 2000 20:58:50 -0500
From: Mark Skurzynski <mark@lomag.net>
Organization: Lomag Internet Services
X-Mailer: Mozilla 4.72 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: freebsd-stable@freebsd.org
Subject: "could not map memory"
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hi,

I've built a new server here, and installed fresh copy of 
FreeBSD 4.0-RELEASE (from Cheap*Bytes). Upon booting, I get this error:

fxp0: <Intel EtherExpress Pro 10/100B Ethernet> at device 9.0 on pci0
fxp0: could not map memory
device_probe_and_attach: fxp0 attach returned 6

Anyone have any ideas on how to fix this? It's running on a Asus P3B-F
motherboard, its always ran fine for me in previous versions. Thanks!

 --Mark


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


From owner-freebsd-stable  Fri Mar 31 18: 6:28 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from cmailg2.svr.pol.co.uk (cmailg2.svr.pol.co.uk [195.92.195.172])
	by hub.freebsd.org (Postfix) with ESMTP id 8819137B7B2
	for <stable@freebsd.org>; Fri, 31 Mar 2000 18:06:19 -0800 (PST)
	(envelope-from ianjhart@freeloader.freeserve.co.uk)
Received: from modem-22.hydrogen.dialup.pol.co.uk ([62.136.0.22] helo=freeloader.freeserve.co.uk)
	by cmailg2.svr.pol.co.uk with esmtp (Exim 3.13 #0)
	id 12bDIn-0000eT-00
	for stable@freebsd.org; Sat, 01 Apr 2000 03:06:18 +0100
Message-ID: <38E559C6.7F5979D3@freeloader.freeserve.co.uk>
Date: Sat, 01 Apr 2000 03:07:02 +0100
From: ian j hart <ianjhart@freeloader.freeserve.co.uk>
X-Mailer: Mozilla 4.61 [en] (X11; I; FreeBSD 4.0-STABLE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: "stable@freebsd.org" <stable@freebsd.org>
Subject: dd reading atapi cdrom
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

I'm used to doing this

#dd if=/dev/acd0c of=image

[followed by vnconfig, mount, share using samba]

This fails under 4.0-STABLE. The error message is Bad address. No data
is transfered. This is reprodusable on three machines. Also fails on
LS120, without error message.

Am I doing something stupid. Don't answer that! Has anyone got a work
around/better method. Compressing the file would be nice :-)

TIA

--
ian j hart




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


From owner-freebsd-stable  Fri Mar 31 18:19:35 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from pmail1.gmx.net (mail.gmx.net [194.221.183.71])
	by hub.freebsd.org (Postfix) with SMTP id 963A837B7B2
	for <freebsd-stable@freebsd.org>; Fri, 31 Mar 2000 18:19:27 -0800 (PST)
	(envelope-from Gerhard.Sittig@gmx.net)
Received: (qmail 11563 invoked by uid 0); 1 Apr 2000 02:19:23 -0000
Received: from pc19f5d6a.dip.t-dialin.net (HELO speedy.gsinet) (193.159.93.106)
  by mail.gmx.net with SMTP; 1 Apr 2000 02:19:23 -0000
Received: (from sittig@localhost)
	by speedy.gsinet (8.8.8/8.8.8) id WAA17908
	for freebsd-stable@freebsd.org; Fri, 31 Mar 2000 22:38:28 +0200
Date: Fri, 31 Mar 2000 22:38:28 +0200
From: Gerhard Sittig <Gerhard.Sittig@gmx.net>
To: freebsd-stable@freebsd.org
Subject: Re: 3.4-RELEASE; panic while paging
Message-ID: <20000331223828.X24822@speedy.gsinet>
Mail-Followup-To: freebsd-stable@freebsd.org
References: <20000329175018.V15889@TK147108.telekabel.at> <20000329195354.A40356@walton.maths.tcd.ie> <20000330205606.B15889@TK147108.telekabel.at> <20000330200422.B16409@dogma.freebsd-uk.eu.org> <14564.50142.22563.853112@onceler.kcilink.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0i
In-Reply-To: <14564.50142.22563.853112@onceler.kcilink.com>; from khera@kciLink.com on Fri, Mar 31, 2000 at 10:27:26AM -0500
Organization: System Defenestrators Inc.
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Fri, Mar 31, 2000 at 10:27 -0500, Vivek Khera wrote:
> 
> I have one box that runs BSD/OS for about a week, then starts
> killing random processes for no reason.  It runs Windoze NT for
> about 10 minutes (of interactive use) before it totally locks
> up.  It has been running RH Linux for about a year without a
> hiccup.  I have not tried FreeBSD on it.  Every major part in
> that box has been swapped out except the case.

Which makes this fact bubble up immediately:  The case holds the
power supply which is quite essential and can cause random
failures when unstable (and yet this part is underestimated and
made cheap to save some pennies -- and cause a lot of time and
money to be wasted on the grief).

And for the uptimes:  Do you remember the thread about which OS
runs coolest?  I guess NT is the one of the above systems with
the most CPU heat.  Do you remember which RedHat it was (i.e.
what Linux kernel) and how you judge the boxes load in terms of
"continously working and thus heating" or "loaded by chance and
just hand warm"?

Just a thought.  Maybe it helps and you can recycle an old(?)
machine which is still fine for serving in the background if it's
too small for a desktop and the bloatware usually found there ...


virtually yours   82D1 9B9C 01DC 4FB4 D7B4  61BE 3F49 4F77 72DE DA76
Gerhard Sittig   true | mail -s "get gpg key" Gerhard.Sittig@gmx.net
-- 
     If you don't understand or are scared by any of the above
             ask your parents or an adult to help you.


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


From owner-freebsd-stable  Fri Mar 31 18:23: 9 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from freeway.dcfinc.com (cx74889-a.phnx3.az.home.com [24.1.193.157])
	by hub.freebsd.org (Postfix) with ESMTP id 9847437B8A7
	for <freebsd-stable@FreeBSD.ORG>; Fri, 31 Mar 2000 18:23:06 -0800 (PST)
	(envelope-from chad@freeway.dcfinc.com)
Received: (from chad@localhost)
	by freeway.dcfinc.com (8.8.8/8.8.8) id TAA24764;
	Fri, 31 Mar 2000 19:23:04 -0700 (MST)
	(envelope-from chad)
From: "Chad R. Larson" <chad@DCFinc.com>
Message-Id: <200004010223.TAA24764@freeway.dcfinc.com>
Subject: Re: "could not map memory"
In-Reply-To: <38E557DA.31465732@lomag.net> from Mark Skurzynski at "Mar 31, 0 08:58:50 pm"
To: mark@lomag.net (Mark Skurzynski)
Date: Fri, 31 Mar 2000 19:23:03 -0700 (MST)
Cc: freebsd-stable@FreeBSD.ORG
Reply-To: chad@DCFinc.com
X-Mailer: ELM [version 2.4ME+ PL40 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

As I recall, Mark Skurzynski wrote:
> I've built a new server here, and installed fresh copy of 
> FreeBSD 4.0-RELEASE (from Cheap*Bytes). 

<nag>
Although it is certainly not required, it is good form to buy your
FreeBSD from Walnut Creek (www.cdrom.com) as some of the money spent
there helps fund the FreeBSD project.
</nag>
	-crl
--
Chad R. Larson (CRL15)   602-953-1392   Brother, can you paradigm?
chad@dcfinc.com         chad@larsons.org          larson1@home.net   
DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207


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


From owner-freebsd-stable  Fri Mar 31 18:27:48 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
	by hub.freebsd.org (Postfix) with ESMTP
	id 1DA4237B997; Fri, 31 Mar 2000 18:27:47 -0800 (PST)
	(envelope-from kris@FreeBSD.org)
Received: from localhost (kris@localhost)
	by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id SAA88503;
	Fri, 31 Mar 2000 18:27:47 -0800 (PST)
	(envelope-from kris@FreeBSD.org)
X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs
Date: Fri, 31 Mar 2000 18:27:46 -0800 (PST)
From: Kris Kennaway <kris@FreeBSD.org>
To: Warner Losh <imp@village.org>
Cc: Jaye Mathisen <mrcpu@internetcds.com>, stable@FreeBSD.ORG
Subject: Re: sshd failure from Adding crypto later on -stable? 
In-Reply-To: <200004010139.SAA38947@harmony.village.org>
Message-ID: <Pine.BSF.4.21.0003311826400.88154-100000@freefall.freebsd.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Fri, 31 Mar 2000, Warner Losh wrote:

> There was no librsaref.so.  Just a librsaUSA.so.  So I created a
> symlink from librsaref.so -> librsaUSA.so.  ssh seems to work after
> the change.

librsaref.so comes from the rsaref port and lives in
/usr/local/lib. librsaUSA.so contains *no* RSA cryptography, so it's quite
unclear to me how ssh can do RSA encryption without it :-)

Kris

> Warner

----
In God we Trust -- all others must submit an X.509 certificate.
    -- Charles Forsythe <forsythe@alum.mit.edu>



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


From owner-freebsd-stable  Fri Mar 31 18:48:23 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from kibby.au.knfpub.com (kibby.au.knfpub.com [203.38.198.130])
	by hub.freebsd.org (Postfix) with ESMTP id 99C4237B6D9
	for <freebsd-stable@freebsd.org>; Fri, 31 Mar 2000 18:48:16 -0800 (PST)
	(envelope-from kibbet@kibby.au.knfpub.com)
Received: (from kibbet@localhost)
	by kibby.au.knfpub.com (8.9.3/8.9.3) id MAA07085;
	Sat, 1 Apr 2000 12:18:08 +0930 (CST)
	(envelope-from kibbet)
Message-ID: <XFMail.000401121808.kibbet@knfpub.com>
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: <Pine.BSF.4.21.0003312059240.250-100000@salmon.nlsystems.com>
Date: Sat, 01 Apr 2000 12:18:08 +0930 (CST)
From: kibbet <kibbet@knfpub.com>
To: Doug Rabson <dfr@nlsystems.com>
Subject: Re: pnpparse.c
Cc: freebsd-stable@freebsd.org
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hi Doug,

On 31-Mar-00 Doug Rabson wrote:
> On Sat, 1 Apr 2000, kibbet wrote:
> 
>> Hi all,
>> 
>> The sys/isa/pnpparse.c MFC today seems to have broken things
>> here with my AWE64, things were happy before the MFC, apart
>> from an odd message during boot
> 
> Sorry about that. Can you try with the latest pnpparse.c.
> 

hehe, no probs, its all in the name of advancement :)

So now I get;

isa0: too many dependant configs (8)
isa0: unexpected small tag 14


Which dosen't bother me - it dosen't panic and I get sound, yay


Now I just gotta fix XFree 4 and shmat()... what fun :)

Cheers,

Kent Ibbetson
KNF Publishing
kibbet@knfpub.com


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


From owner-freebsd-stable  Fri Mar 31 18:57:21 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from TK147108.tuwien.teleweb.at (TK147108.tuwien.teleweb.at [195.34.147.108])
	by hub.freebsd.org (Postfix) with ESMTP id 37E4237B8C6
	for <freebsd-stable@freebsd.org>; Fri, 31 Mar 2000 18:56:56 -0800 (PST)
	(envelope-from satyr@TK147108.tuwien.teleweb.at)
Received: from satyr by TK147108.tuwien.teleweb.at with local (Exim 2.12 #1)
	id 12bE8V-0008Ug-00; Sat, 1 Apr 2000 04:59:43 +0200
Date: Sat, 1 Apr 2000 04:59:43 +0200
From: "Marinos J . Yannikos" <mjy@pobox.com>
To: Gerhard Sittig <Gerhard.Sittig@gmx.net>
Cc: freebsd-stable@freebsd.org
Subject: Re: 3.4-RELEASE; panic while paging
Message-ID: <20000401045943.J31173@TK147108.telekabel.at>
Reply-To: nino@inode.at
References: <20000329175018.V15889@TK147108.telekabel.at> <20000329195354.A40356@walton.maths.tcd.ie> <20000330205606.B15889@TK147108.telekabel.at> <20000330200422.B16409@dogma.freebsd-uk.eu.org> <14564.50142.22563.853112@onceler.kcilink.com> <20000331223828.X24822@speedy.gsinet>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.5i
In-Reply-To: <20000331223828.X24822@speedy.gsinet>; from Gerhard Sittig on Fri, Mar 31, 2000 at 10:38:28PM +0200
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> Which makes this fact bubble up immediately:  The case holds the
> power supply which is quite essential and can cause random
> failures when unstable (and yet this part is underestimated and
> made cheap to save some pennies -- and cause a lot of time and
> money to be wasted on the grief).

Do you have first-hand experience with power supply related problems?
I thought I had fixed all problems with my Athlon box by swapping board,
DIMMs and CPU, but after testing for a longer time I found that processes
would still die with signal 11. The easiest way to cause such failures is
an ApacheBench run with many concurrent dynamic requests (load >50) - after
a while, (usually 30-60 minutes) several apache processes will die in a short
period of time. I also had a prime factorization program crash after several
hours (the "mprime" program from www.mersenne.org/gimps). Does that sound
like a problem that could be related to the power supply? It's not one of
the PSUs recommended by AMD, but rated at 300W.

-mjy
-- 
***==> Marinos J. Yannikos <mjy@pobox.com>
***==> http://pobox.com/~mjy


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


From owner-freebsd-stable  Fri Mar 31 21:12:15 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from weeble.dyndns.org (ubppp248-217.dialin.buffalo.edu [128.205.248.217])
	by hub.freebsd.org (Postfix) with ESMTP id A082F37BAE8
	for <freebsd-stable@FreeBSD.org>; Fri, 31 Mar 2000 21:12:07 -0800 (PST)
	(envelope-from cjm2@earthling.net)
Received: from shithead (shithead.weeble.dyndns.org [10.0.0.2])
	by weeble.dyndns.org (8.9.3/8.9.3) with SMTP id AAA54001
	for <freebsd-stable@FreeBSD.org>; Sat, 1 Apr 2000 00:12:05 -0500 (EST)
	(envelope-from cjm2@earthling.net)
From: "C J Michaels" <cjm2@earthling.net>
To: "FreeBSD Stable" <freebsd-stable@FreeBSD.org>
Subject: 4.0-S 3/31 KERNEL causes reboot on startup
Date: Sat, 1 Apr 2000 00:12:10 -0500
Message-ID: <NDBBILKDCLLECBCLPMBIOEBKCAAA.cjm2@earthling.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 IMO, Build 9.0.2416 (9.0.2910.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Importance: Normal
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hi,
I have a spare machine I've been fooling with trying to learn 4.0-S before I
put it on my main machine.  I thought it might be beneficial to 'make world'
every night on this machine to see if any problems arise so I could report
them.

So, tonight (3/31) I took the following steps.
1. cvsup RELENG_4 (around 6pm EST)
2. make buildworld
3. make installworld
4. build and install a new kernel
5. mergemaster
6. reboot

During the kernel's hardware detection the system just reboots.  No
messages, just reboots.  I rebooted with the kernel.GENERIC (4.0-RC4) and
that did boot ok.  I rebuild and installed the GENERIC kernel.  Same
problem.

I genuinely don't even know how to proceed in troubleshooting this problem.
Yesterday's kernel (3/30) didn't have the problem.  The detection goes so
fast I can't really tell where it's crapping out, the nearest I can tell is
it's either during or right after it detects ed0 (PCI NE2000 card).

Any pointers would be appreciated.

Thanks,
-Chris

P.S.  No optimizations were used for this build.



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


From owner-freebsd-stable  Fri Mar 31 21:39:51 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from evil.2y.net (ztown1-1-55.adsl.one.net [207.78.254.55])
	by hub.freebsd.org (Postfix) with ESMTP id 0BECE37BABC
	for <freebsd-stable@freebsd.org>; Fri, 31 Mar 2000 21:39:48 -0800 (PST)
	(envelope-from cokane@evil.2y.net)
Received: (from cokane@localhost)
	by evil.2y.net (8.9.3/8.9.3) id AAA06924;
	Sat, 1 Apr 2000 00:44:37 -0500 (EST)
	(envelope-from cokane)
Date: Sat, 1 Apr 2000 00:44:37 -0500
From: Coleman Kane <cokane@one.net>
To: Jeff Fisher <jeff@jeffenstein.org>
Cc: freebsd-stable@freebsd.org
Subject: Re: What is needed in /stand
Message-ID: <20000401004437.A6904@evil.2y.net>
References: <20000331124119.B10520@laptop.firehouse.net> <Pine.BSF.4.21.0003311244360.28631-100000@localhost>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0.1i
In-Reply-To: <Pine.BSF.4.21.0003311244360.28631-100000@localhost>; from jeff@jeffenstein.org on Fri, Mar 31, 2000 at 01:50:59PM -0500
X-Vim: vim:tw=70:ts=4:sw=4
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Jeff Fisher had the audacity to say:
> 
> On Fri, 31 Mar 2000, Alan Clegg wrote:
> 
> If it's needed, you could create the /usr/tmp directory on the root
> partition, so it will be there before /usr is mounted.  Hopefully it won't
> get alot of files that transparently fill up the root.
> 

I dunno if this happens or not, but you may run into trouble if there is a file
in /usr/tmp being used before usr gets mounted. Why don't you just make a
seperate /tmp mount, then set it to be one of the early mounted filesystems?

--cokane


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


From owner-freebsd-stable  Fri Mar 31 21:44:35 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from evil.2y.net (ztown1-1-55.adsl.one.net [207.78.254.55])
	by hub.freebsd.org (Postfix) with ESMTP id D34FD37BAF4
	for <freebsd-stable@FreeBSD.ORG>; Fri, 31 Mar 2000 21:44:21 -0800 (PST)
	(envelope-from cokane@evil.2y.net)
Received: (from cokane@localhost)
	by evil.2y.net (8.9.3/8.9.3) id AAA06933;
	Sat, 1 Apr 2000 00:49:01 -0500 (EST)
	(envelope-from cokane)
Date: Sat, 1 Apr 2000 00:49:01 -0500
From: Coleman Kane <cokane@one.net>
To: Grigoriy Strokin <grg@philol.msu.ru>
Cc: Jason Garman <jgarman@wedgie.org>,
	Thomas K?llmann <koellmann@gmx.net>, freebsd-stable@FreeBSD.ORG
Subject: Re: New kernel with its ATA drivers damages the filesystem
Message-ID: <20000401004901.B6904@evil.2y.net>
References: <20000331022130.A4045@isabase.philol.msu.ru> <20000331142357.A1291@home.net> <20000331163527.B24581@got.wedgie.org> <20000401013959.A48268@isabase.philol.msu.ru>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0.1i
In-Reply-To: <20000401013959.A48268@isabase.philol.msu.ru>; from grg@philol.msu.ru on Fri, Mar 31, 2000 at 04:41:22PM -0500
X-Vim: vim:tw=70:ts=4:sw=4
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Grigoriy Strokin had the audacity to say:
> Interestingly, commenting out this option doesn't affect the mode for my CD-ROM
> either.
> 
>    sysctl reports
>      hw.atamodes: dma,---,dma,---,
> 
> First dma is for ad0, second for acd0.
> 
> And dmesg reports using UDMA-33 for CDROM, too.
> 
> acd0: CDROM <FX4010M> at ata1-master using UDMA33
> 

I beleive it only applies to Multi-Word DMA, or MWDMA for short, the predecessor
to UDMA. Although, I could be wrong, but you had two choices back then. They
were mwdma and PIO basically. Each had it's pro's and con's. Now you can do
UDMA, which is drastically different from MWDMA, and should be considered a
different operating mode.

--cokane


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


From owner-freebsd-stable  Fri Mar 31 21:48: 3 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from evil.2y.net (ztown1-1-55.adsl.one.net [207.78.254.55])
	by hub.freebsd.org (Postfix) with ESMTP id 86F3E37BAE4
	for <freebsd-stable@FreeBSD.org>; Fri, 31 Mar 2000 21:47:58 -0800 (PST)
	(envelope-from cokane@evil.2y.net)
Received: (from cokane@localhost)
	by evil.2y.net (8.9.3/8.9.3) id AAA06944;
	Sat, 1 Apr 2000 00:52:54 -0500 (EST)
	(envelope-from cokane)
Date: Sat, 1 Apr 2000 00:52:54 -0500
From: Coleman Kane <cokane@one.net>
To: C J Michaels <cjm2@earthling.net>
Cc: FreeBSD Stable <freebsd-stable@FreeBSD.org>
Subject: Re: 4.0-S 3/31 KERNEL causes reboot on startup
Message-ID: <20000401005254.C6904@evil.2y.net>
References: <NDBBILKDCLLECBCLPMBIOEBKCAAA.cjm2@earthling.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0.1i
In-Reply-To: <NDBBILKDCLLECBCLPMBIOEBKCAAA.cjm2@earthling.net>; from cjm2@earthling.net on Sat, Apr 01, 2000 at 12:12:58AM -0500
X-Vim: vim:tw=70:ts=4:sw=4
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

CJ, if you check /var/log/messages, you can see where the system stopped during
the detection phase to see what hardware may have caused the problem.
/var/log/messages usually has the last three or four boots of kernel messages
in it, providing your syslog.conf is set accordingly...

--cokane

C J Michaels had the audacity to say:
> Hi,
> I have a spare machine I've been fooling with trying to learn 4.0-S before I
> put it on my main machine.  I thought it might be beneficial to 'make world'
> every night on this machine to see if any problems arise so I could report
> them.
> 
> So, tonight (3/31) I took the following steps.
> 1. cvsup RELENG_4 (around 6pm EST)
> 2. make buildworld
> 3. make installworld
> 4. build and install a new kernel
> 5. mergemaster
> 6. reboot
> 
> During the kernel's hardware detection the system just reboots.  No
> messages, just reboots.  I rebooted with the kernel.GENERIC (4.0-RC4) and
> that did boot ok.  I rebuild and installed the GENERIC kernel.  Same
> problem.
> 
> I genuinely don't even know how to proceed in troubleshooting this problem.
> Yesterday's kernel (3/30) didn't have the problem.  The detection goes so
> fast I can't really tell where it's crapping out, the nearest I can tell is
> it's either during or right after it detects ed0 (PCI NE2000 card).
> 
> Any pointers would be appreciated.
> 
> Thanks,
> -Chris
> 
> P.S.  No optimizations were used for this build.
> 


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


From owner-freebsd-stable  Fri Mar 31 22:42:22 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from xxx.video-collage.com (xxx.video-collage.com [209.122.149.226])
	by hub.freebsd.org (Postfix) with ESMTP id 6533237BC03
	for <freebsd-stable@FreeBSD.ORG>; Fri, 31 Mar 2000 22:42:17 -0800 (PST)
	(envelope-from mi@video-collage.com)
X-Relay-IP: ‚ 
Received: from dufus.video-collage.com (dufus [10.222.222.77])
	by xxx.video-collage.com (8.9.1a/8.9.1) with ESMTP id BAA12661;
	Sat, 1 Apr 2000 01:42:04 -0500 (EST)
From: Mikhail Teterin <mi@video-collage.com>
Received: (from mi@localhost)
	by dufus.video-collage.com (8.9.3/8.9.3) id BAA33929;
	Sat, 1 Apr 2000 01:42:08 -0500 (EST)
	(envelope-from mi@xxx)
Message-Id: <200004010642.BAA33929@dufus.video-collage.com>
Subject: Re: "could not map memory"
In-Reply-To: <200004010223.TAA24764@freeway.dcfinc.com> from "Chad R. Larson"
 at "Mar 31, 2000 07:23:03 pm"
To: chad@DCFinc.com
Date: Sat, 1 Apr 2000 01:42:08 -0500 (EST)
Cc: Mark Skurzynski <mark@lomag.net>, freebsd-stable@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL68 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> <nag>
> Although it  is certainly not  required, it is  good form to  buy your
> FreeBSD from Walnut  Creek (www.cdrom.com) as some of  the money spent
> there helps fund the FreeBSD project.
> </nag>

I'm afraid, for a  newbie this would sound like a  refusal _of the whole
mailing list_ to offer any help, because the cd was bought elsewhere.

I know this is  not true at all, but that's what it  sounds like and the
`<nag>' may or may not help it... Just my humble opinion, of course.

Mark, please, wait for someone with a  clue that neither Chad nor I have
to respond...

	-mi


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


From owner-freebsd-stable  Fri Mar 31 23: 9:34 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from frog.nutt.net.au (frog.nutt.net.au [203.25.185.45])
	by hub.freebsd.org (Postfix) with ESMTP id 9705C37BABB
	for <freebsd-stable@FreeBSD.ORG>; Fri, 31 Mar 2000 23:09:28 -0800 (PST)
	(envelope-from jarrod@nutt.net.au)
Received: from wallace.i.nutt.net.au (utopia.nutt.net.au [203.25.185.50])
	by frog.nutt.net.au (8.9.3/8.9.3) with ESMTP id QAA00428
	for <freebsd-stable@FreeBSD.ORG>; Sat, 1 Apr 2000 16:39:23 +0930 (CST)
Received: from localhost (jarrod@localhost)
	by wallace.i.nutt.net.au (8.9.3/8.9.3) with ESMTP id QAA15166
	for <freebsd-stable@FreeBSD.ORG>; Sat, 1 Apr 2000 16:40:08 +0930 (CST)
Date: Sat, 1 Apr 2000 16:40:07 +0930 (CST)
From: Jarrod <jarrod@nutt.net.au>
X-Sender: jarrod@wallace.i.nutt.net.au
To: freebsd-stable@FreeBSD.ORG
Subject: Machine Pausing?
Message-ID: <Pine.BSF.4.21.0004011629150.15153-100000@wallace.i.nutt.net.au>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hi,

Installed 4.0-R on a new server we have just installed, but every so often
the machine pauses.  Web serving stops, users get Connection Timed Out
errors.  ssh users get booted and I get booted from mgetty when the
machine does this.  It was brought up to 4.0-S about 2 days after the
offical release of 4.0 and thismorning I cvsupped src-all and rebuilt only
the kernel and installed that (and yes, it is booting the new one).  Its
still doing it.  Is this a problem that a few people have come across?  
Would a make world fix this?

I'm not doing a make world if I can avoid it.  We did to one of our other
backup machines and 'w' and 'top' come up with nlist errors, 'df' and
'swapinfo' both die, with an error relating to the kernel, sorry, I didnt
get the full error message.  I cant have this to this machine as its now a
semi-primary machine, cant live without it running.

The pauses happen every 40 minutes or so, cpu load sits on 0.10 from the
users logged in, no error messages in /var/log/messages or the console.

CPU Fan / modem / network card (now Netgear FX310) have all been replaced.

m/b, ram, and power supply havent been changed.  Though the system ran
fine here at home without any dramas.  Then it was changed into another
case and power supply where the problem started.

Could this be caused by the power supply?

frog> uname -a
FreeBSD frog.nutt.net.au 4.0-STABLE FreeBSD 4.0-STABLE #0: Sat Apr  1
13:12:20 CST 2000     jarrod@frog.nutt.net.au:/usr/obj/usr/src/sys/GENERIC
i386

TIA,

Jarrod

-- 
Jarrod Sayers (jarrod@nutt.net.au)

"It's not panic, it's a full-blown hysterical fit!"
 (Rimmer, Red Dwarf - Rimmerworld)



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


From owner-freebsd-stable  Sat Apr  1  4:24:27 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from Reineke.Malepartus.DE (reineke.malepartus.de [194.25.4.41])
	by hub.freebsd.org (Postfix) with ESMTP id 5798637B984
	for <freebsd-stable@freebsd.org>; Sat,  1 Apr 2000 04:24:24 -0800 (PST)
	(envelope-from bm@Reineke.Malepartus.DE)
Received: from Reineke.Malepartus.DE (localhost.Malepartus.de [127.0.0.1])
	by Reineke.Malepartus.DE (8.9.3/8.9.3) with ESMTP id OAA37296
	for <freebsd-stable@freebsd.org>; Sat, 1 Apr 2000 14:24:23 +0200 (MEST)
	(envelope-from bm@Reineke.Malepartus.DE)
Message-Id: <200004011224.OAA37296@Reineke.Malepartus.DE>
X-Mailer: exmh version 2.1.1 10/15/1999
From: Burkard Meyendriesch <bm@Malepartus.de>
Subject: problems to get a src-4 tree
To: freebsd-stable@freebsd.org
Reply-To: bm@Malepartus.de
X-organization: The home of Reineke Fuchs
X-GPOS: 52.0844N 7.9081E
X-phone: +49 5484 96097
X-pgp-fingerprint: DF 83 04 CD B5 D1 10 43  57 4C AD 9A B1 02 28 17
X-face: "[-;]oI+8gP9>*J%knDN8d%DuhvJS2Lj4L\bRb7gz(pcT?2Zh6_Vam_6csAum3$<&lhAFd^
 jt|!&Ut1C~Vg*E/q}+#cbFg-GU]c.bB8Ad,L'W$'9{^0y'AzM4#hS[C[F-1'|O;Kg3V<ZJKG3g9Fs-
 kuovqp|S7(.wC"D@/O5xcb^PSDJU#jyt`tp^7Trg239:o9bDVm\{6J,`P<>rq5q6dsU*TmJ@}+QPM\
 b[^<zL1qL^&)o'{%T@Q&p)N$OZ:aDa(r2f5?52HuGmO'm>9Rhd,UoMpRpd5k[X=h.Dom*kbT`cNQ
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Date: Sat, 01 Apr 2000 14:24:23 +0200
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


Hello all,

I failed to build a src-4 tree:

starting with src-4.0000xEmpty.gz I end up with:

    # ctm -v -v /usr/ctm/deltas/src-4.0000xEmpty.gz =

    ctm: warning: .ctm_status not found
    Working on </usr/ctm/deltas/src-4.0000xEmpty.gz>
    Expecting Global MD5 <0a8504be99eff8ed2eb9f97ca0b65dc3>
    Reference Global MD5 <0a8504be99eff8ed2eb9f97ca0b65dc3>
      DR: src doesn't exist.
    ctm: exit(80)

starting at src-cur.4274.gz, removing .ctm-status and then applying
src-4.0000.from-src-cur.4274.gz results in:

    # ctm -v -v /usr/ctm/deltas/src-4.0000.from-src-cur.4274.gz =

    ctm: warning: .ctm_status not found
    Working on </usr/ctm/deltas/src-4.0000.from-src-cur.4274.gz>
    Expecting Global MD5 <086641040d74d131a68592d6f77a927b>
    Reference Global MD5 <086641040d74d131a68592d6f77a927b>
      FS: .ctm_status doesn't exist.
    ctm: exit(72)

What is my mistake? Can anybody help me please?

Thanks
Burkard

-- =

* Burkard Meyendriesch             ___                bm@malepartus.de *
* Hauptstrasse 45           ________|________       tel +49 5484 96097 *
* D-49219 Glandorf-Schwege          0           52 05'05"N  07 54'29"E *
* PGP-Fingerprint     BF 3B 41 DE 15 4D C9 48  15 EF A5 86 BF 6D 68 1A *




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


From owner-freebsd-stable  Sat Apr  1  5:20:11 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from firehouse.net (spook.networkoperations.com [209.42.203.59])
	by hub.freebsd.org (Postfix) with SMTP id 2623D37B721
	for <freebsd-stable@FreeBSD.ORG>; Sat,  1 Apr 2000 05:20:03 -0800 (PST)
	(envelope-from abc@firehouse.net)
Received: (qmail 18398 invoked by uid 100); 1 Apr 2000 13:19:57 -0000
Date: Sat, 1 Apr 2000 08:19:57 -0500
From: Alan Clegg <abc@bsdi.com>
To: Coleman Kane <cokane@one.net>
Cc: C J Michaels <cjm2@earthling.net>,
	FreeBSD Stable <freebsd-stable@FreeBSD.ORG>
Subject: Re: 4.0-S 3/31 KERNEL causes reboot on startup
Message-ID: <20000401081956.K12424@laptop.firehouse.net>
References: <NDBBILKDCLLECBCLPMBIOEBKCAAA.cjm2@earthling.net> <20000401005254.C6904@evil.2y.net>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-md5;
	protocol="application/pgp-signature"; boundary="07FIeBX8hApXX6Bi"
X-Mailer: Mutt 1.0.1i
In-Reply-To: <20000401005254.C6904@evil.2y.net>; from cokane@one.net on Sat, Apr 01, 2000 at 12:52:54AM -0500
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


--07FIeBX8hApXX6Bi
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable

Out of the ether, Coleman Kane spewed forth the following bitstream:
> CJ, if you check /var/log/messages, you can see where the system stopped =
during
> the detection phase to see what hardware may have caused the problem.
> /var/log/messages usually has the last three or four boots of kernel mess=
ages
> in it, providing your syslog.conf is set accordingly...

If his problem is the same as mine, the kernel never gets to the point=20
of starting any system services, thus, no syslog.

AlanC {only seeing the reboot on one machine, oddly enough}

--07FIeBX8hApXX6Bi
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 5.0i for non-commercial use
MessageID: oje11ouJ+kx1ShXTcG6zDtMk4PQphpg1

iQA/AwUBOOX3fPcyv/gweBpYEQLr8ACg8E0iPJulPhLc2vTJs/XDHMQV6zUAnik0
bFUPcHB9eKaAHrDjbMM7lF94
=G6Hg
-----END PGP SIGNATURE-----

--07FIeBX8hApXX6Bi--


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


From owner-freebsd-stable  Sat Apr  1  5:21:39 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from netcom.com (netcom1.netcom.com [199.183.9.101])
	by hub.freebsd.org (Postfix) with ESMTP id 2FF9837B5C5
	for <freebsd-stable@freebsd.org>; Sat,  1 Apr 2000 05:21:37 -0800 (PST)
	(envelope-from stanb@netcom.com)
Received: (from stanb@localhost)
	by netcom.com (8.9.3/8.9.3) id FAA02932
	for freebsd-stable@freebsd.org; Sat, 1 Apr 2000 05:19:34 -0800 (PST)
From: Stan Brown <stanb@netcom.com>
Message-Id: <200004011319.FAA02932@netcom.com>
Subject: What's with make.conf in 4.0 ?
To: freebsd-stable@freebsd.org (FreeBSD Stable List)
Date: Sat, 1 Apr 2000 08:19:34 -0500 (EST)
X-Mailer: ELM [version 2.5 PL3]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

	I am setng up my first 4.0 machine. Started building my ports, and I
	built lestiff, as a prerequsite for ddd.

	Went and looked at /etc/make.conf to enable Motif, and found that it
	contianed only one line. What happend to all the examples there? And
	what do I put in to tell the ports tree, I have lestiff?

	Thanks.

-- 
Stan Brown     stanb@netcom.com                                    404-996-6955
Factory Automation Systems
Atlanta Ga.
-- 
Look, look, see Windows 95.  Buy, lemmings, buy!   
Pay no attention to that cliff ahead...            Henry Spencer
(c) 1998 Stan Brown.  Redistribution via the Microsoft Network is prohibited.


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


From owner-freebsd-stable  Sat Apr  1  5:39:19 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from frog.nutt.net.au (frog.nutt.net.au [203.25.185.45])
	by hub.freebsd.org (Postfix) with ESMTP id 7274037B538
	for <freebsd-stable@FreeBSD.ORG>; Sat,  1 Apr 2000 05:39:03 -0800 (PST)
	(envelope-from jarrod@nutt.net.au)
Received: from wallace.i.nutt.net.au (utopia.nutt.net.au [203.25.185.50])
	by frog.nutt.net.au (8.9.3/8.9.3) with ESMTP id XAA01047;
	Sat, 1 Apr 2000 23:08:53 +0930 (CST)
Received: from localhost (jarrod@localhost)
	by wallace.i.nutt.net.au (8.9.3/8.9.3) with ESMTP id XAA00456;
	Sat, 1 Apr 2000 23:08:34 +0930 (CST)
Date: Sat, 1 Apr 2000 23:08:34 +0930 (CST)
From: Jarrod <jarrod@nutt.net.au>
X-Sender: jarrod@wallace.i.nutt.net.au
To: Stan Brown <stanb@netcom.com>
Cc: FreeBSD Stable List <freebsd-stable@FreeBSD.ORG>
Subject: Re: What's with make.conf in 4.0 ?
In-Reply-To: <200004011319.FAA02932@netcom.com>
Message-ID: <Pine.BSF.4.21.0004012306480.454-100000@wallace.i.nutt.net.au>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Sat, 1 Apr 2000, Stan Brown wrote:

> Went and looked at /etc/make.conf to enable Motif, and found that it
> contianed only one line. What happend to all the examples there? And
> what do I put in to tell the ports tree, I have lestiff?
> 
> Thanks.

The make.conf setup now set up like rc.conf.  A set of defaults are in
/etc/defaults/make.conf and any variables you want to override, you define
in /etc/make.conf

-Jarrod

-- 
Jarrod Sayers (jarrod@nutt.net.au)

"I'll fold up like a cheap tent!"
 (David Letterman)



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


From owner-freebsd-stable  Sat Apr  1  5:47:11 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from ns1.networkiowa.com (ns1.networkiowa.com [209.234.64.192])
	by hub.freebsd.org (Postfix) with ESMTP id 1542A37BA41
	for <freebsd-stable@FreeBSD.org>; Sat,  1 Apr 2000 05:47:09 -0800 (PST)
	(envelope-from johnl@raccoon.com)
Received: from raccoon.com (dsl.72.145.networkiowa.com [209.234.72.145])
	by ns1.networkiowa.com (8.9.3/8.9.3) with ESMTP id HAA03774
	for <freebsd-stable@FreeBSD.org>; Sat, 1 Apr 2000 07:50:06 -0600
Message-ID: <38E5FDD7.4EE2167@raccoon.com>
Date: Sat, 01 Apr 2000 07:47:03 -0600
From: John Lengeling <johnl@raccoon.com>
X-Mailer: Mozilla 4.7 [en] (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
To: freebsd-stable@FreeBSD.org
Subject: (no subject)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

 


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


From owner-freebsd-stable  Sat Apr  1  6:32: 4 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from weeble.dyndns.org (ubppp233-236.dialin.buffalo.edu [128.205.233.236])
	by hub.freebsd.org (Postfix) with ESMTP id 33CD437B9A5
	for <freebsd-stable@FreeBSD.org>; Sat,  1 Apr 2000 06:31:59 -0800 (PST)
	(envelope-from cjm2@earthling.net)
Received: from shithead (shithead.weeble.dyndns.org [10.0.0.2])
	by weeble.dyndns.org (8.9.3/8.9.3) with SMTP id JAA58208;
	Sat, 1 Apr 2000 09:31:56 -0500 (EST)
	(envelope-from cjm2@earthling.net)
From: "C J Michaels" <cjm2@earthling.net>
To: "Coleman Kane" <cokane@one.net>
Cc: "FreeBSD Stable" <freebsd-stable@FreeBSD.org>
Subject: RE: 4.0-S 3/31 KERNEL causes reboot on startup
Date: Sat, 1 Apr 2000 09:31:55 -0500
Message-ID: <NDBBILKDCLLECBCLPMBIIEBLCAAA.cjm2@earthling.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 IMO, Build 9.0.2416 (9.0.2910.0)
In-Reply-To: <20000401005254.C6904@evil.2y.net>
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Importance: Normal
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

OK.. I booted with kernel.GENERIC and looked at /var/log/messages.  There
were only boot messages from my last 2 attempts to boot from the
kernel.GENERIC even though I had tried booting the new kernel inbetween.

Any other ideas?  :P
-Chris

-----Original Message-----
From: Coleman Kane [mailto:cokane@one.net]
Sent: Saturday, April 01, 2000 12:53 AM
To: C J Michaels
Cc: FreeBSD Stable
Subject: Re: 4.0-S 3/31 KERNEL causes reboot on startup


CJ, if you check /var/log/messages, you can see where the system stopped
during
the detection phase to see what hardware may have caused the problem.
/var/log/messages usually has the last three or four boots of kernel
messages
in it, providing your syslog.conf is set accordingly...

--cokane

C J Michaels had the audacity to say:
> Hi,
> I have a spare machine I've been fooling with trying to learn 4.0-S before
I
> put it on my main machine.  I thought it might be beneficial to 'make
world'
> every night on this machine to see if any problems arise so I could report
> them.
>
> So, tonight (3/31) I took the following steps.
> 1. cvsup RELENG_4 (around 6pm EST)
> 2. make buildworld
> 3. make installworld
> 4. build and install a new kernel
> 5. mergemaster
> 6. reboot
>
> During the kernel's hardware detection the system just reboots.  No
> messages, just reboots.  I rebooted with the kernel.GENERIC (4.0-RC4) and
> that did boot ok.  I rebuild and installed the GENERIC kernel.  Same
> problem.
>
> I genuinely don't even know how to proceed in troubleshooting this
problem.
> Yesterday's kernel (3/30) didn't have the problem.  The detection goes so
> fast I can't really tell where it's crapping out, the nearest I can tell
is
> it's either during or right after it detects ed0 (PCI NE2000 card).
>
> Any pointers would be appreciated.
>
> Thanks,
> -Chris
>
> P.S.  No optimizations were used for this build.
>



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


From owner-freebsd-stable  Sat Apr  1  7:39:12 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from kot.ne.mediaone.net (kot.ne.mediaone.net [24.218.15.190])
	by hub.freebsd.org (Postfix) with ESMTP id 31C7C37B9FE
	for <freebsd-stable@FreeBSD.ORG>; Sat,  1 Apr 2000 07:39:09 -0800 (PST)
	(envelope-from mi@kot.ne.mediaone.net)
Received: from rtfm.newton (root@rtfm.newton [10.10.0.1])
	by kot.ne.mediaone.net (8.9.3/8.9.1) with ESMTP id KAA83383
	for <freebsd-stable@FreeBSD.ORG>; Sat, 1 Apr 2000 10:39:07 -0500 (EST)
From: Mikhail Teterin <mi@kot.ne.mediaone.net>
X-Relay-IP: 10.10.0.1
Received: (from mi@localhost)
	by rtfm.newton (8.9.3/8.9.3) id KAA70786
	for freebsd-stable@FreeBSD.ORG; Sat, 1 Apr 2000 10:39:07 -0500 (EST)
	(envelope-from mi@kot.ne.mediaone.net)
Message-Id: <200004011539.KAA70786@rtfm.newton>
Subject: erroneous messages filtering ((no subject))
In-Reply-To: <38E5FDD7.4EE2167@raccoon.com> from John Lengeling at "Apr 1, 2000
 07:47:03 am"
To: freebsd-stable@FreeBSD.ORG
Date: Sat, 1 Apr 2000 10:39:07 -0500 (EST)
X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w<gv/&E-lL7twZCT8B~/PA4|\t$ti+22K">
	 hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli"<kcG^EOVih
	 y+z3/UR{6SCQ
X-Mailer: ELM [version 2.4ME+ PL60 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

How hard is it to reject messages  with blank lines n the body only, or,
if there is  only non-blank line, to check it  for the ``*subscribe''? I
know, the mailing  list software check the number of  crossposts -- this
seems even easier...

	-mi

= 
=
=
=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 Apr  1  7:53: 8 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from weeble.dyndns.org (ubppp234-215.dialin.buffalo.edu [128.205.234.215])
	by hub.freebsd.org (Postfix) with ESMTP id 6AABD37B671
	for <freebsd-stable@FreeBSD.ORG>; Sat,  1 Apr 2000 07:52:59 -0800 (PST)
	(envelope-from cjm2@earthling.net)
Received: from shithead (shithead.weeble.dyndns.org [10.0.0.2])
	by weeble.dyndns.org (8.9.3/8.9.3) with SMTP id KAA58847;
	Sat, 1 Apr 2000 10:52:54 -0500 (EST)
	(envelope-from cjm2@earthling.net)
From: "C J Michaels" <cjm2@earthling.net>
To: "C J Michaels" <cjm2@earthling.net>
Cc: "FreeBSD Stable" <freebsd-stable@FreeBSD.ORG>
Subject: RE: 4.0-S 3/31 KERNEL causes reboot on startup
Date: Sat, 1 Apr 2000 10:52:53 -0500
Message-ID: <NDBBILKDCLLECBCLPMBIMEBMCAAA.cjm2@earthling.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 IMO, Build 9.0.2416 (9.0.2910.0)
In-Reply-To: <NDBBILKDCLLECBCLPMBIIEBLCAAA.cjm2@earthling.net>
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Importance: Normal
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hate to reply to my own postings but the problem is resolved.

I cvsup'ped (as of 12am est), did a config -r, and rebuilt my kernel again.
Works now.

The only change I saw in the cvsup was the pnpparse.c.  Anyway it's fixed so
I won't complain.

For future reference tho, is there any way I can try and debug a problem
such as this so I can make useful bug reports?

Thanks
-Chris

-----Original Message-----
From: owner-freebsd-stable@FreeBSD.ORG
[mailto:owner-freebsd-stable@FreeBSD.ORG]On Behalf Of C J Michaels
Sent: Saturday, April 01, 2000 9:32 AM
To: Coleman Kane
Cc: FreeBSD Stable
Subject: RE: 4.0-S 3/31 KERNEL causes reboot on startup


OK.. I booted with kernel.GENERIC and looked at /var/log/messages.  There
were only boot messages from my last 2 attempts to boot from the
kernel.GENERIC even though I had tried booting the new kernel inbetween.

Any other ideas?  :P
-Chris

-----Original Message-----
From: Coleman Kane [mailto:cokane@one.net]
Sent: Saturday, April 01, 2000 12:53 AM
To: C J Michaels
Cc: FreeBSD Stable
Subject: Re: 4.0-S 3/31 KERNEL causes reboot on startup


CJ, if you check /var/log/messages, you can see where the system stopped
during
the detection phase to see what hardware may have caused the problem.
/var/log/messages usually has the last three or four boots of kernel
messages
in it, providing your syslog.conf is set accordingly...

--cokane

C J Michaels had the audacity to say:
> Hi,
> I have a spare machine I've been fooling with trying to learn 4.0-S before
I
> put it on my main machine.  I thought it might be beneficial to 'make
world'
> every night on this machine to see if any problems arise so I could report
> them.
>
> So, tonight (3/31) I took the following steps.
> 1. cvsup RELENG_4 (around 6pm EST)
> 2. make buildworld
> 3. make installworld
> 4. build and install a new kernel
> 5. mergemaster
> 6. reboot
>
> During the kernel's hardware detection the system just reboots.  No
> messages, just reboots.  I rebooted with the kernel.GENERIC (4.0-RC4) and
> that did boot ok.  I rebuild and installed the GENERIC kernel.  Same
> problem.
>
> I genuinely don't even know how to proceed in troubleshooting this
problem.
> Yesterday's kernel (3/30) didn't have the problem.  The detection goes so
> fast I can't really tell where it's crapping out, the nearest I can tell
is
> it's either during or right after it detects ed0 (PCI NE2000 card).
>
> Any pointers would be appreciated.
>
> Thanks,
> -Chris
>
> P.S.  No optimizations were used for this build.
>



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 Apr  1  8:45:44 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from tinc-org.com (tinc-org.com [64.6.65.10])
	by hub.freebsd.org (Postfix) with ESMTP id 934CD37B9E0
	for <freebsd-stable@freebsd.org>; Sat,  1 Apr 2000 08:45:40 -0800 (PST)
	(envelope-from jeff@jeffenstein.org)
Received: (from uucp@localhost)
	by tinc-org.com (8.9.3/8.9.3) with UUCP id KAA32670
	Sat, 1 Apr 2000 10:45:33 -0600 (CST) (envelope-from jeff@jeffenstein.org)
Received: (from uucp@localhost)
	by localhost.jeffnet (8.9.3/8.9.3) id KAA41498;
	Sat, 1 Apr 2000 10:44:59 -0600 (CST)
	(envelope-from jeff@jeffenstein.org)
Received: from frogger.jeffnet(192.168.243.1), claiming to be "frogger-int"
 via SMTP by frogger.jeffnet, id smtpda41496; Sat Apr  1 10:44:50 2000
Date: Sat, 1 Apr 2000 10:44:49 -0600 (CST)
From: Jeff Fisher <jeff@jeffenstein.org>
X-Sender: jeff@localhost
To: Coleman Kane <cokane@one.net>
Cc: freebsd-stable@freebsd.org
Subject: Re: What is needed in /stand
In-Reply-To: <20000401004437.A6904@evil.2y.net>
Message-ID: <Pine.BSF.4.21.0004011039040.41431-100000@localhost>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Sat, 1 Apr 2000, Coleman Kane wrote:

> Jeff Fisher had the audacity to say:
> > 
> > On Fri, 31 Mar 2000, Alan Clegg wrote:
> > 
> > If it's needed, you could create the /usr/tmp directory on the root
> > partition, so it will be there before /usr is mounted.  Hopefully it won't
> > get alot of files that transparently fill up the root.
> > 
> 
> I dunno if this happens or not, but you may run into trouble if there is a file
> in /usr/tmp being used before usr gets mounted. Why don't you just make a
> seperate /tmp mount, then set it to be one of the early mounted filesystems?

If the file is already open, there won't be a problem.  If another process
tries to open that same file, it won't be able to after /usr is mounted.
A side effect is that the file will take up space on the root partition,
but you won't be able to see it or remove the file, unless you unmount
/usr.

On the systems that I've set up, /tmp has always been a seperate
filesystem.

-----
jeff@jeffenstein.org             http://www.jeffenstein.org

Microsoft: Where do you want to go today?
Linux: Where do you want to go tomorrow?
FreeBSD: Are you guys coming or what?



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


From owner-freebsd-stable  Sat Apr  1  9: 7:57 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from frolkin.demon.co.uk (frolkin.demon.co.uk [194.222.100.41])
	by hub.freebsd.org (Postfix) with ESMTP id 38F2837BBB0
	for <stable@freebsd.org>; Sat,  1 Apr 2000 09:07:54 -0800 (PST)
	(envelope-from sasha@frolkin.demon.co.uk)
Received: from sasha by frolkin.demon.co.uk with local (Exim 3.12 #1)
	id 12bQRW-0001ij-00; Sat, 01 Apr 2000 17:08:10 +0100
Date: Sat, 1 Apr 2000 17:08:10 +0100
From: Alexander Frolkin <alexander@frolkin.demon.co.uk>
To: Warner Losh <imp@village.org>
Cc: stable@freebsd.org
Subject: Re: Upgrading to 4.0
Message-ID: <20000401170809.A6464@gamma>
Reply-To: Alexander Frolkin <alexander@frolkin.demon.co.uk>
References: <20000331190328.A4215@gamma> <200004010140.SAA38998@harmony.village.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.5i
In-Reply-To: <200004010140.SAA38998@harmony.village.org>; from Warner Losh on Fri, Mar 31, 2000 at 06:40:38PM -0700
X-Operating-System: Linux 2.2.14
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Fri, Mar 31, 2000 at 06:40:38PM -0700, Warner Losh wrote:
> Yes.  build and install the new kernel, build and install the new
> pccardd (with the new pccard include files, so as part of make
> buildworld is the best way to build it).  Then it should be safe to
> reboot.  Keep a copy of the old pccardd and old kernel around just in
> case you botch something.

Here's what I did:
- make buildworld
- copied the new pccard[cd] to a temporary directory
- installed a new kernel
- reboot

I have the following lines in my kernel config:

device		card
device		pcic0	at isa? irq 10 port 0x3e0 iomem 0xd0000
device		pcic1	at isa? irq 11 port 0x3e2 iomem 0xd4000

and

device		ed


When I reboot (4.0 kernel) in single user mode, I change to the directory
containing pccardd, but this is what happens:

# ./pccardd -z
code Manufacturer ID ignored
#

I've checked /etc/pccard.conf, and it seems fine. If I try to do:

# ./pccardc enabler 1 ed0

The kernel panics, but I can't tell what it says because right after it
panics, the screen becomes unreadable and the system reboots.

I'm hoping that I've made a stupid mistake in the kernel config, and someone
can point it out...


Is it really necessary to do make installworld with a 4.0 kernel?


Thanks a lot,
Alexander.


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


From owner-freebsd-stable  Sat Apr  1 10: 8:54 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from rover.village.org (rover.village.org [204.144.255.49])
	by hub.freebsd.org (Postfix) with ESMTP id 59AF837B79C
	for <stable@freebsd.org>; Sat,  1 Apr 2000 10:08:51 -0800 (PST)
	(envelope-from imp@harmony.village.org)
Received: from harmony.village.org (harmony.village.org [10.0.0.6])
	by rover.village.org (8.9.3/8.9.3) with ESMTP id LAA80176;
	Sat, 1 Apr 2000 11:08:49 -0700 (MST)
	(envelope-from imp@harmony.village.org)
Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id LAA46711; Sat, 1 Apr 2000 11:08:16 -0700 (MST)
Message-Id: <200004011808.LAA46711@harmony.village.org>
To: Alexander Frolkin <alexander@frolkin.demon.co.uk>
Subject: Re: Upgrading to 4.0 
Cc: stable@freebsd.org
In-reply-to: Your message of "Sat, 01 Apr 2000 17:08:10 +0100."
		<20000401170809.A6464@gamma> 
References: <20000401170809.A6464@gamma>  <20000331190328.A4215@gamma> <200004010140.SAA38998@harmony.village.org> 
Date: Sat, 01 Apr 2000 11:08:16 -0700
From: Warner Losh <imp@village.org>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

In message <20000401170809.A6464@gamma> Alexander Frolkin writes:
: # ./pccardd -z
: code Manufacturer ID ignored

That doesn't look good.  Can you recognize card insert/remove events?
If not, stop right here and either go to polling mode, or change the
irq to one that you can really use.

: I've checked /etc/pccard.conf, and it seems fine. If I try to do:

Hmmmm, looks can be deceiving here. :-).

: The kernel panics, but I can't tell what it says because right after it
: panics, the screen becomes unreadable and the system reboots.

w/o a panic message, I can't tell you what you did wrong with any
certainty.

: I'm hoping that I've made a stupid mistake in the kernel config, and someone
: can point it out...

99% of all pccard problems are misconfigurations.  The other 1% are
really hard to track down.

: Is it really necessary to do make installworld with a 4.0 kernel?

installworld will work with a DESTDIR != /.  However, the install
tools are run out of /usr/bin, et al, and after you install the new
binaries, the new signal interface they use won't be supported by your 
kernel and things will start dying.

Warner


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


From owner-freebsd-stable  Sat Apr  1 10:23:23 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from ns.yogotech.com (ns.yogotech.com [206.127.79.126])
	by hub.freebsd.org (Postfix) with ESMTP id 6CFD237B7C0
	for <stable@FreeBSD.ORG>; Sat,  1 Apr 2000 10:23:20 -0800 (PST)
	(envelope-from nate@yogotech.com)
Received: from nomad.yogotech.com (nomad.yogotech.com [206.127.79.115])
	by ns.yogotech.com (8.9.3/8.9.3) with ESMTP id LAA27762;
	Sat, 1 Apr 2000 11:23:11 -0700 (MST)
	(envelope-from nate@nomad.yogotech.com)
Received: (from nate@localhost)
	by nomad.yogotech.com (8.8.8/8.8.8) id LAA04688;
	Sat, 1 Apr 2000 11:23:10 -0700 (MST)
	(envelope-from nate)
Date: Sat, 1 Apr 2000 11:23:10 -0700 (MST)
Message-Id: <200004011823.LAA04688@nomad.yogotech.com>
From: Nate Williams <nate@yogotech.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: Warner Losh <imp@village.org>
Cc: Alexander Frolkin <alexander@frolkin.demon.co.uk>,
	stable@FreeBSD.ORG
Subject: Re: Upgrading to 4.0 
In-Reply-To: <200004011808.LAA46711@harmony.village.org>
References: <20000401170809.A6464@gamma>
	<20000331190328.A4215@gamma>
	<200004010140.SAA38998@harmony.village.org>
	<200004011808.LAA46711@harmony.village.org>
X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid
Reply-To: nate@yogotech.com (Nate Williams)
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> : # ./pccardd -z
> : code Manufacturer ID ignored
> 
> That doesn't look good.  Can you recognize card insert/remove events?
> If not, stop right here and either go to polling mode, or change the
> irq to one that you can really use.

The insertion/removal IRQ shouldn't matter (yet), since the cards are
read at startup of pccardd.  Otherwise, the system wouldn't be able to
use them until they were removed and re-inserted if you boot with them
inserted.





Nate


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


From owner-freebsd-stable  Sat Apr  1 10:26: 3 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from rover.village.org (rover.village.org [204.144.255.49])
	by hub.freebsd.org (Postfix) with ESMTP id A908D37B762
	for <stable@FreeBSD.ORG>; Sat,  1 Apr 2000 10:25:56 -0800 (PST)
	(envelope-from imp@harmony.village.org)
Received: from harmony.village.org (harmony.village.org [10.0.0.6])
	by rover.village.org (8.9.3/8.9.3) with ESMTP id LAA80278;
	Sat, 1 Apr 2000 11:25:54 -0700 (MST)
	(envelope-from imp@harmony.village.org)
Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id LAA46862; Sat, 1 Apr 2000 11:25:22 -0700 (MST)
Message-Id: <200004011825.LAA46862@harmony.village.org>
To: nate@yogotech.com (Nate Williams)
Subject: Re: Upgrading to 4.0 
Cc: Alexander Frolkin <alexander@frolkin.demon.co.uk>,
	stable@FreeBSD.ORG
In-reply-to: Your message of "Sat, 01 Apr 2000 11:23:10 MST."
		<200004011823.LAA04688@nomad.yogotech.com> 
References: <200004011823.LAA04688@nomad.yogotech.com>  <20000401170809.A6464@gamma> <20000331190328.A4215@gamma> <200004010140.SAA38998@harmony.village.org> <200004011808.LAA46711@harmony.village.org> 
Date: Sat, 01 Apr 2000 11:25:22 -0700
From: Warner Losh <imp@village.org>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

In message <200004011823.LAA04688@nomad.yogotech.com> Nate Williams writes:
: The insertion/removal IRQ shouldn't matter (yet), since the cards are
: read at startup of pccardd.  Otherwise, the system wouldn't be able to
: use them until they were removed and re-inserted if you boot with them
: inserted.

Yes, but it may be fighting the IRQ that is being used by something
else in the system, maybe causign problems.

Warner


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


From owner-freebsd-stable  Sat Apr  1 10:28:42 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from ns.yogotech.com (ns.yogotech.com [206.127.79.126])
	by hub.freebsd.org (Postfix) with ESMTP id B044A37B6D4
	for <stable@FreeBSD.ORG>; Sat,  1 Apr 2000 10:28:37 -0800 (PST)
	(envelope-from nate@yogotech.com)
Received: from nomad.yogotech.com (nomad.yogotech.com [206.127.79.115])
	by ns.yogotech.com (8.9.3/8.9.3) with ESMTP id LAA27817;
	Sat, 1 Apr 2000 11:28:29 -0700 (MST)
	(envelope-from nate@nomad.yogotech.com)
Received: (from nate@localhost)
	by nomad.yogotech.com (8.8.8/8.8.8) id LAA04719;
	Sat, 1 Apr 2000 11:28:28 -0700 (MST)
	(envelope-from nate)
Date: Sat, 1 Apr 2000 11:28:28 -0700 (MST)
Message-Id: <200004011828.LAA04719@nomad.yogotech.com>
From: Nate Williams <nate@yogotech.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: Warner Losh <imp@village.org>
Cc: nate@yogotech.com (Nate Williams),
	Alexander Frolkin <alexander@frolkin.demon.co.uk>, stable@FreeBSD.ORG
Subject: Re: Upgrading to 4.0 
In-Reply-To: <200004011825.LAA46862@harmony.village.org>
References: <200004011823.LAA04688@nomad.yogotech.com>
	<20000401170809.A6464@gamma>
	<20000331190328.A4215@gamma>
	<200004010140.SAA38998@harmony.village.org>
	<200004011808.LAA46711@harmony.village.org>
	<200004011825.LAA46862@harmony.village.org>
X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid
Reply-To: nate@yogotech.com (Nate Williams)
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> : The insertion/removal IRQ shouldn't matter (yet), since the cards are
> : read at startup of pccardd.  Otherwise, the system wouldn't be able to
> : use them until they were removed and re-inserted if you boot with them
> : inserted.
> 
> Yes, but it may be fighting the IRQ that is being used by something
> else in the system, maybe causign problems.

It might be, but that shouldn't effect whether or not the card works, in
my experience.  (I don't believe the new setup is that much different
from the old way of doing things...)

It should only effect the insertion/removal events...




Nate


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


From owner-freebsd-stable  Sat Apr  1 10:31: 0 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from rjk191.rh.psu.edu (RJK191.rh.psu.edu [128.118.193.182])
	by hub.freebsd.org (Postfix) with ESMTP id BEC5B37BBB8
	for <freebsd-stable@freebsd.org>; Sat,  1 Apr 2000 10:30:53 -0800 (PST)
	(envelope-from ray@rjk191.rh.psu.edu)
Received: (from ray@localhost)
	by rjk191.rh.psu.edu (8.9.3/8.9.3) id NAA16051
	for freebsd-stable@freebsd.org; Sat, 1 Apr 2000 13:30:51 -0500 (EST)
	(envelope-from ray)
Date: Sat, 1 Apr 2000 13:30:51 -0500
From: Ray Kohler <ray@rjk191.rh.psu.edu>
To: freebsd-stable@freebsd.org
Subject: INDEX version number of libtool is wrong
Message-ID: <20000401133051.A15989@rjk191.rh.psu.edu>
Reply-To: rjk191@psu.edu
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0.1i
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

The ports INDEX has version 1.3.4 for devel/libtool, but the port
itself is only 1.3.3. What happened here? Is libtool about to be
updated, but hasn't been yet? I find this situation surprising,
since usually the INDEX is behind the ports, but I've never seen it
ahead of them before...

-- 
Ray Kohler <rjk191@psu.edu>
"If you don't want your dog to have bad breath, do what I do:  Pour a little
Lavoris in the toilet."
		-- Jay Leno


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


From owner-freebsd-stable  Sat Apr  1 10:31:42 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from rover.village.org (rover.village.org [204.144.255.49])
	by hub.freebsd.org (Postfix) with ESMTP id 511F737B9FD
	for <stable@FreeBSD.ORG>; Sat,  1 Apr 2000 10:31:38 -0800 (PST)
	(envelope-from imp@harmony.village.org)
Received: from harmony.village.org (harmony.village.org [10.0.0.6])
	by rover.village.org (8.9.3/8.9.3) with ESMTP id LAA80311;
	Sat, 1 Apr 2000 11:31:36 -0700 (MST)
	(envelope-from imp@harmony.village.org)
Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id LAA46923; Sat, 1 Apr 2000 11:31:03 -0700 (MST)
Message-Id: <200004011831.LAA46923@harmony.village.org>
To: nate@yogotech.com (Nate Williams)
Subject: Re: Upgrading to 4.0 
Cc: Alexander Frolkin <alexander@frolkin.demon.co.uk>,
	stable@FreeBSD.ORG
In-reply-to: Your message of "Sat, 01 Apr 2000 11:28:28 MST."
		<200004011828.LAA04719@nomad.yogotech.com> 
References: <200004011828.LAA04719@nomad.yogotech.com>  <200004011823.LAA04688@nomad.yogotech.com> <20000401170809.A6464@gamma> <20000331190328.A4215@gamma> <200004010140.SAA38998@harmony.village.org> <200004011808.LAA46711@harmony.village.org> <200004011825.LAA46862@harmony.village.org> 
Date: Sat, 01 Apr 2000 11:31:03 -0700
From: Warner Losh <imp@village.org>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

In message <200004011828.LAA04719@nomad.yogotech.com> Nate Williams writes:
: It should only effect the insertion/removal events...

99% of the time you are right here.  I helped one person about 3
months ago who had things that had been broken start working when they 
took out the irq XX and did nothing else.  At least that's what they
reported to me.

Warner


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


From owner-freebsd-stable  Sat Apr  1 10:40: 0 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from frolkin.demon.co.uk (frolkin.demon.co.uk [194.222.100.41])
	by hub.freebsd.org (Postfix) with ESMTP id 80BFD37B8AF
	for <stable@freebsd.org>; Sat,  1 Apr 2000 10:39:55 -0800 (PST)
	(envelope-from sasha@frolkin.demon.co.uk)
Received: from sasha by frolkin.demon.co.uk with local (Exim 3.12 #1)
	id 12bRsQ-00026b-00; Sat, 01 Apr 2000 18:40:02 +0100
Date: Sat, 1 Apr 2000 18:40:02 +0100
From: Alexander Frolkin <alexander@frolkin.demon.co.uk>
To: Warner Losh <imp@village.org>
Cc: stable@freebsd.org
Subject: Re: Upgrading to 4.0
Message-ID: <20000401184002.A8017@gamma>
Reply-To: Alexander Frolkin <alexander@frolkin.demon.co.uk>
References: <20000401170809.A6464@gamma> <20000331190328.A4215@gamma> <200004010140.SAA38998@harmony.village.org> <20000401170809.A6464@gamma> <200004011808.LAA46711@harmony.village.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.5i
In-Reply-To: <200004011808.LAA46711@harmony.village.org>; from Warner Losh on Sat, Apr 01, 2000 at 11:08:16AM -0700
X-Operating-System: Linux 2.2.14
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Sat, Apr 01, 2000 at 11:08:16AM -0700, Warner Losh wrote:
> In message <20000401170809.A6464@gamma> Alexander Frolkin writes:
> : # ./pccardd -z
> : code Manufacturer ID ignored
> 
> That doesn't look good.  Can you recognize card insert/remove events?

Yes, the kernels tells me when a card is inserted or removed.


Alexander.


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


From owner-freebsd-stable  Sat Apr  1 10:52: 6 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from evil.2y.net (ztown1-1-55.adsl.one.net [207.78.254.55])
	by hub.freebsd.org (Postfix) with ESMTP id A91CE37B9AE
	for <freebsd-stable@freebsd.org>; Sat,  1 Apr 2000 10:51:58 -0800 (PST)
	(envelope-from cokane@evil.2y.net)
Received: (from cokane@localhost)
	by evil.2y.net (8.9.3/8.9.3) id NAA11369;
	Sat, 1 Apr 2000 13:57:01 -0500 (EST)
	(envelope-from cokane)
Date: Sat, 1 Apr 2000 13:57:01 -0500
From: Coleman Kane <cokane@one.net>
To: Jeff Fisher <jeff@jeffenstein.org>
Cc: Coleman Kane <cokane@one.net>, freebsd-stable@freebsd.org
Subject: Re: What is needed in /stand
Message-ID: <20000401135701.A11341@evil.2y.net>
References: <20000401004437.A6904@evil.2y.net> <Pine.BSF.4.21.0004011039040.41431-100000@localhost>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0.1i
In-Reply-To: <Pine.BSF.4.21.0004011039040.41431-100000@localhost>; from jeff@jeffenstein.org on Sat, Apr 01, 2000 at 11:45:40AM -0500
X-Vim: vim:tw=70:ts=4:sw=4
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Jeff Fisher had the audacity to say:
> 
> If the file is already open, there won't be a problem.  If another process
> tries to open that same file, it won't be able to after /usr is mounted.
> A side effect is that the file will take up space on the root partition,
> but you won't be able to see it or remove the file, unless you unmount
> /usr.
> 
> On the systems that I've set up, /tmp has always been a seperate
> filesystem.
> 

Yeah, same here.

> -----
> jeff@jeffenstein.org             http://www.jeffenstein.org


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


From owner-freebsd-stable  Sat Apr  1 10:55:23 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from evil.2y.net (ztown1-1-55.adsl.one.net [207.78.254.55])
	by hub.freebsd.org (Postfix) with ESMTP id 2F51F37B993
	for <freebsd-stable@FreeBSD.org>; Sat,  1 Apr 2000 10:55:15 -0800 (PST)
	(envelope-from cokane@evil.2y.net)
Received: (from cokane@localhost)
	by evil.2y.net (8.9.3/8.9.3) id OAA11381;
	Sat, 1 Apr 2000 14:00:18 -0500 (EST)
	(envelope-from cokane)
Date: Sat, 1 Apr 2000 14:00:18 -0500
From: Coleman Kane <cokane@one.net>
To: C J Michaels <cjm2@earthling.net>
Cc: Coleman Kane <cokane@one.net>,
	FreeBSD Stable <freebsd-stable@FreeBSD.org>
Subject: Re: 4.0-S 3/31 KERNEL causes reboot on startup
Message-ID: <20000401140018.B11341@evil.2y.net>
References: <20000401005254.C6904@evil.2y.net> <NDBBILKDCLLECBCLPMBIIEBLCAAA.cjm2@earthling.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0.1i
In-Reply-To: <NDBBILKDCLLECBCLPMBIIEBLCAAA.cjm2@earthling.net>; from cjm2@earthling.net on Sat, Apr 01, 2000 at 09:31:58AM -0500
X-Vim: vim:tw=70:ts=4:sw=4
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hmm... you may want to check the gzipped, archived messages. Also you should
probably turn on full debugging in your new kernel. I think it's:
makeoptions	"-g -DDEBUG" or something like that. You should also check
/etc/make.conf to see what your CCOPTFLAGS is set to. I have had kernels that
simply reboot the system when used with -O2 or -O3, I find that -O works fine.

--cokane

C J Michaels had the audacity to say:
> 
> OK.. I booted with kernel.GENERIC and looked at /var/log/messages.  There
> were only boot messages from my last 2 attempts to boot from the
> kernel.GENERIC even though I had tried booting the new kernel inbetween.
> 
> Any other ideas?  :P
> -Chris
> 


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


From owner-freebsd-stable  Sat Apr  1 11:19:12 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from mail2.gmx.net (mail.gmx.net [194.221.183.62])
	by hub.freebsd.org (Postfix) with SMTP id C3C5B37B630
	for <freebsd-stable@freebsd.org>; Sat,  1 Apr 2000 11:19:06 -0800 (PST)
	(envelope-from Gerhard.Sittig@gmx.net)
Received: (qmail 18773 invoked by uid 0); 1 Apr 2000 19:19:04 -0000
Received: from pc19f6037.dip.t-dialin.net (HELO speedy.gsinet) (193.159.96.55)
  by mail.gmx.net with SMTP; 1 Apr 2000 19:19:04 -0000
Received: (from sittig@localhost)
	by speedy.gsinet (8.8.8/8.8.8) id QAA20493
	for freebsd-stable@freebsd.org; Sat, 1 Apr 2000 16:08:25 +0200
Date: Sat, 1 Apr 2000 16:08:25 +0200
From: Gerhard Sittig <Gerhard.Sittig@gmx.net>
To: freebsd-stable@freebsd.org
Subject: Re: 3.4-RELEASE; panic while paging
Message-ID: <20000401160825.A24822@speedy.gsinet>
Mail-Followup-To: freebsd-stable@freebsd.org
References: <20000329175018.V15889@TK147108.telekabel.at> <20000329195354.A40356@walton.maths.tcd.ie> <20000330205606.B15889@TK147108.telekabel.at> <20000330200422.B16409@dogma.freebsd-uk.eu.org> <14564.50142.22563.853112@onceler.kcilink.com> <20000331223828.X24822@speedy.gsinet> <20000401045943.J31173@TK147108.telekabel.at>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0i
In-Reply-To: <20000401045943.J31173@TK147108.telekabel.at>; from mjy@pobox.com on Sat, Apr 01, 2000 at 04:59:43AM +0200
Organization: System Defenestrators Inc.
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Sat, Apr 01, 2000 at 04:59 +0200, Marinos J . Yannikos wrote:
> > Which makes this fact bubble up immediately:  The case holds
> > the power supply which is quite essential and can cause
> > random failures when unstable (and yet this part is
> > underestimated and made cheap to save some pennies -- and
> > cause a lot of time and money to be wasted on the grief).
> 
> Do you have first-hand experience with power supply related
> problems?  [ ... swapped anything, but heavy load still causes
> processes to die erroneously ... ] Does that sound like a
> problem that could be related to the power supply? It's not one
> of the PSUs recommended by AMD, but rated at 300W.

Well, I never had any personnal problems with instable power
supplies (except for some exploded capacitors which will make
problems show up _immediately_:).  But I remember a message in a
list somewhere (if only I knew which one it was):  It's not so
much about the *total* dimension of this device, or at least
that's not all there is to it.  It's also about fitting the needs
of every single voltage provided.  Imagine a power supply with
250W but still unable to serve the 5V needs -- no matter how much
reserve there is at -5/-12/+12V!  Given the consumption of todays
chips and the usual building the systems for "normal" usage will
make these problems arise real soon (within a year or even
earlier).

All I can advise is to look for special load in these machines:
huge RAM modules or many of these?  big fat graphics cards?
overclocked systems?  certain Cyrix/IBM or Athlon CPUs?  many
hard drives or all of them spinning up at once instead of in a
delayed sequence?  too little air flow?

I take it as a hint that it's high computing load (or disk
activity?) increasing the chance for these crashes.  But after
all, I'm more of a software guy than a technician ...


BTW:  I obviously read this list, so I don't need a courtesy
copy.  Seems it's about time to setup a dupe filter unless people
get used to the list-reply functions instead of using
group-reply.  It should always be a clear decision whether to
reply in private or in public and appropriate action should be
the consequence.


virtually yours   82D1 9B9C 01DC 4FB4 D7B4  61BE 3F49 4F77 72DE DA76
Gerhard Sittig   true | mail -s "get gpg key" Gerhard.Sittig@gmx.net
-- 
     If you don't understand or are scared by any of the above
             ask your parents or an adult to help you.


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


From owner-freebsd-stable  Sat Apr  1 11:49:45 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from frolkin.demon.co.uk (frolkin.demon.co.uk [194.222.100.41])
	by hub.freebsd.org (Postfix) with ESMTP id 7481937B655
	for <stable@freebsd.org>; Sat,  1 Apr 2000 11:49:40 -0800 (PST)
	(envelope-from sasha@frolkin.demon.co.uk)
Received: from sasha by frolkin.demon.co.uk with local (Exim 3.12 #1)
	id 12bSzs-0002Pu-00
	for stable@freebsd.org; Sat, 01 Apr 2000 19:51:48 +0100
Date: Sat, 1 Apr 2000 19:51:48 +0100
From: Alexander Frolkin <alexander@frolkin.demon.co.uk>
To: stable@freebsd.org
Subject: Re: Upgrading to 4.0
Message-ID: <20000401195148.A9141@gamma>
Reply-To: Alexander Frolkin <alexander@frolkin.demon.co.uk>
References: <20000401170809.A6464@gamma> <20000331190328.A4215@gamma> <200004010140.SAA38998@harmony.village.org> <200004011808.LAA46711@harmony.village.org> <200004011823.LAA04688@nomad.yogotech.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.5i
In-Reply-To: <200004011823.LAA04688@nomad.yogotech.com>; from Nate Williams on Sat, Apr 01, 2000 at 11:23:10AM -0700
X-Operating-System: Linux 2.2.14
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Some more things I've noticed...

If I do:

# ./pccardc enabler 0 ed0 -m 2000 d4000 16 -a 300 -i 3

It says "device not configured", which leads me to think that I've missed
something out in the kernel config.


After playing around with pccardd etc. under 4.0, I find that the kernels
(4.0 and 3.4) panic when they get to the part where they load the pccard
support, unless I do a cold reboot. The panic message start with "integer
divide", but that's all I could see before the screen becomes unreadable :-(


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


From owner-freebsd-stable  Sat Apr  1 11:58: 0 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from atlrel1.hp.com (atlrel1.hp.com [156.153.255.210])
	by hub.freebsd.org (Postfix) with ESMTP id 5080637BA31
	for <freebsd-stable@FreeBSD.ORG>; Sat,  1 Apr 2000 11:57:58 -0800 (PST)
	(envelope-from marcel@cup.hp.com)
Received: from adlmail.cup.hp.com (adlmail.cup.hp.com [15.0.100.30])
	by atlrel1.hp.com (Postfix) with ESMTP id AABFE91
	for <freebsd-stable@FreeBSD.ORG>; Sat,  1 Apr 2000 14:57:56 -0500 (EST)
Received: from cup.hp.com (gauss.cup.hp.com [15.28.97.152]) by adlmail.cup.hp.com with ESMTP (8.8.6 (PHNE_17135)/8.7.3 TIS 5.0.1) id LAA17646 for <freebsd-stable@FreeBSD.ORG>; Sat, 1 Apr 2000 11:57:55 -0800 (PST)
Message-ID: <38E654C4.E561DE34@cup.hp.com>
Date: Sat, 01 Apr 2000 11:57:56 -0800
From: Marcel Moolenaar <marcel@cup.hp.com>
Organization: Hewlett-Packard
X-Mailer: Mozilla 4.72 [en] (X11; I; Linux 2.2.12 i386)
X-Accept-Language: en
MIME-Version: 1.0
Cc: freebsd-stable@FreeBSD.ORG
Subject: Re: Courtesy copy [Re: 3.4-RELEASE; panic while paging]
References: <20000329175018.V15889@TK147108.telekabel.at> <20000329195354.A40356@walton.maths.tcd.ie> <20000330205606.B15889@TK147108.telekabel.at> <20000330200422.B16409@dogma.freebsd-uk.eu.org> <14564.50142.22563.853112@onceler.kcilink.com> <20000331223828.X24822@speedy.gsinet> <20000401045943.J31173@TK147108.telekabel.at> <20000401160825.A24822@speedy.gsinet>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

\begin{Alternate mail header}
o  Followup to -chat
o  Send courtesy copy (I'm not subscribed to -chat :-)
\end{Alternate mail header}

Gerhard Sittig wrote:

> BTW:  I obviously read this list, so I don't need a courtesy
> copy.

It's not always obvious that people posting on a list are actually
subscribed to it, not to mention reading the mail on it :-)

> It should always be a clear decision whether to
> reply in private or in public and appropriate action should be
> the consequence.

That's the problem: It's not clear. Sometimes it takes too long for mail
to a list to actually reach the person you're replying to that it is a
pain in a hot discussion. Sending to the person directly as well as to
the list speeds up the turnaround time.

Also, I normally route mailinglists to seperate mailboxes and/or
newsgroups. This way I immediately notice when someone is mailing to me
personally. It also allows me to remove/ignore large amounts of mail
without much harm if I happen to need to catch up. I therefore like to
have a courtesy copy at all times even though I may be reading the list.

We obviously have different setups and/or ways of dealing with mail.
This is exactly what makes it unclear for Joe Sender. In this case it's
probably best to follow the general trend on the mailinglist you're
replying to.

FYI,

-- 
Marcel Moolenaar
  mail: marcel@cup.hp.com / marcel@FreeBSD.org
  tel:  (408) 447-4222


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


From owner-freebsd-stable  Sat Apr  1 12:57:12 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from trinity.skynet.be (trinity.skynet.be [195.238.2.38])
	by hub.freebsd.org (Postfix) with ESMTP id 1E7D737BAE7
	for <freebsd-stable@FreeBSD.ORG>; Sat,  1 Apr 2000 12:57:09 -0800 (PST)
	(envelope-from blk@skynet.be)
Received: from [194.78.233.215] (dialup249.brussels.skynet.be [195.238.19.249])
	by trinity.skynet.be (Postfix) with ESMTP
	id 00C8018156; Sat,  1 Apr 2000 22:57:05 +0200 (MET DST)
Mime-Version: 1.0
X-Sender: blk@pop.skynet.be
Message-Id: <v0422080ab50c1240f6d9@[194.78.233.215]>
In-Reply-To: <20000401135701.A11341@evil.2y.net>
References: <20000401004437.A6904@evil.2y.net>
 <Pine.BSF.4.21.0004011039040.41431-100000@localhost>
 <20000401135701.A11341@evil.2y.net>
Date: Sat, 1 Apr 2000 22:56:26 +0200
To: Coleman Kane <cokane@one.net>, Jeff Fisher <jeff@jeffenstein.org>
From: Brad Knowles <blk@skynet.be>
Subject: Re: What is needed in /stand
Cc: Coleman Kane <cokane@one.net>, freebsd-stable@FreeBSD.ORG
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

At 1:57 PM -0500 2000/4/1, Coleman Kane wrote:

>>  On the systems that I've set up, /tmp has always been a seperate
>>  filesystem.
>
>  Yeah, same here.

	If I ever have to set up a system where /tmp needs a lot of disk 
space, or could use an option like softupdates enabled, I always put 
it on a separate filesystem, or perhaps a memory-based filesystem.

	Many years ago I learned that making /tmp a symlink to /usr/tmp 
was a bad idea.

--
   These are my opinions -- not to be taken as official Skynet policy
======================================================================
Brad Knowles, <blk@skynet.be>                || Belgacom Skynet SA/NV
Systems Architect, Mail/News/FTP/Proxy Admin || Rue Colonel Bourg, 124
Phone/Fax: +32-2-706.13.11/12.49             || B-1140 Brussels
http://www.skynet.be                         || Belgium


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


From owner-freebsd-stable  Sat Apr  1 13: 5: 6 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from tv.weeble.dyndns.org (ubppp233-122.dialin.buffalo.edu [128.205.233.122])
	by hub.freebsd.org (Postfix) with ESMTP id 7335C37B589
	for <freebsd-stable@freebsd.org>; Sat,  1 Apr 2000 13:04:55 -0800 (PST)
	(envelope-from cjm2@tv.weeble.dyndns.org)
Received: from localhost (cjm2@localhost)
	by tv.weeble.dyndns.org (8.9.3/8.9.3) with ESMTP id QAA00412
	for <freebsd-stable@freebsd.org>; Sat, 1 Apr 2000 16:04:47 -0500 (EST)
	(envelope-from cjm2@tv.weeble.dyndns.org)
Date: Sat, 1 Apr 2000 16:04:47 -0500 (EST)
From: "Christopher J. Michaels" <cjm2@tv.weeble.dyndns.org>
Reply-To: C J Michaels <cjm2@earthling.net>
To: freebsd-stable@freebsd.org
Subject: Fatal trap 12: page fault while in kernel mode
Message-ID: <Pine.BSF.4.21.0004011548230.391-300000@tv.weeble.dyndns.org>
MIME-Version: 1.0
Content-Type: MULTIPART/MIXED; BOUNDARY="0-288915071-954623087=:391"
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.
  Send mail to mime@docserver.cac.washington.edu for more info.

--0-288915071-954623087=:391
Content-Type: TEXT/PLAIN; charset=US-ASCII

Running 4.0-STABLE cvsupped at 12:00am EST.
Gigabyte GA-7XI w/ Athlon 600 proc.

I get the following panic on bootup when the umass driver is compiled into
the kernel.  It panic's at the point where the root file system would
usually be mounted.  (This is hand typed since it's not getting far enough
to generate a dump):

Fatal trap 12: page fault while in kernel mode
fault virtual address	= 0x70
fault code		= supervisor read, page not present
instruction pointer	= 0x8:0xc0145350
stack pointer		= 0x10:0xc025f680
frame pointer		= 0x10:0xc025f6a8
code segment		= base 0x0, limit 0xfffff, type 0x1b
			= DPL 0, pres 1, def32 1, gran 1
processor eflags	= interrupt enabled, resume, IOPL = 0
current process		= Idle
interrupt mask		= net tty bio cam
kernel: type 12 trap, code=0
Stopped at	tsleep+0x54:	cmpl	$0,0x70(%ebx)


I did compile with -G and also options DDB, but I haven't the slightest
idea what to do at th db> prompt that would be useful.

I'd like to submit a PR on this but this doesn't feel like enough info,
does anyone have any pointers or is this enough information.

I am attaching the DMESG and kernel config of successful boot of the same
kernel with umass commented out.

Thanks for any help
-- 
Chris

--0-288915071-954623087=:391
Content-Type: TEXT/PLAIN; charset=US-ASCII; name=dmesg
Content-Transfer-Encoding: BASE64
Content-ID: <Pine.BSF.4.21.0004011604470.391@tv.weeble.dyndns.org>
Content-Description: 
Content-Disposition: attachment; filename=dmesg

Q29weXJpZ2h0IChjKSAxOTkyLTIwMDAgVGhlIEZyZWVCU0QgUHJvamVjdC4N
CkNvcHlyaWdodCAoYykgMTk4MiwgMTk4NiwgMTk4OSwgMTk5MSwgMTk5Mw0K
CVRoZSBSZWdlbnRzIG9mIHRoZSBVbml2ZXJzaXR5IG9mIENhbGlmb3JuaWEu
IEFsbCByaWdodHMgcmVzZXJ2ZWQuDQpGcmVlQlNEIDQuMC1TVEFCTEUgIzE1
OiBTYXQgQXByICAxIDE1OjU5OjUzIEVTVCAyMDAwDQogICAgcm9vdEBzaGl0
aGVhZC53ZWVibGUuZHluZG5zLm9yZzovdXNyL3NyYy9zeXMvY29tcGlsZS9z
aGl0aGVhZA0KVGltZWNvdW50ZXIgImk4MjU0IiAgZnJlcXVlbmN5IDExOTMx
ODIgSHoNCkNQVTogQU1ELUs3KHRtKSBQcm9jZXNzb3IgKDU5OC44NC1NSHog
Njg2LWNsYXNzIENQVSkNCiAgT3JpZ2luID0gIkF1dGhlbnRpY0FNRCIgIElk
ID0gMHg2MTIgIFN0ZXBwaW5nID0gMg0KICBGZWF0dXJlcz0weDgxZjlmZjxG
UFUsVk1FLERFLFBTRSxUU0MsTVNSLFBBRSxNQ0UsQ1g4LFNFUCxNVFJSLFBH
RSxNQ0EsQ01PVixQQVQsTU1YPg0KICBBTUQgRmVhdHVyZXM9MHhjMDQwMDAw
MDxBTUlFLERTUCwzRE5vdyE+DQpyZWFsIG1lbW9yeSAgPSAxMzQxNTIxOTIg
KDEzMTAwOEsgYnl0ZXMpDQphdmFpbCBtZW1vcnkgPSAxMjcyMjE3NjAgKDEy
NDI0MEsgYnl0ZXMpDQpQZW50aXVtIFBybyBNVFJSIHN1cHBvcnQgZW5hYmxl
ZA0KbWQwOiBNYWxsb2MgZGlzaw0KbnB4MDogPG1hdGggcHJvY2Vzc29yPiBv
biBtb3RoZXJib2FyZA0KbnB4MDogSU5UIDE2IGludGVyZmFjZQ0KYXBtMDog
PEFQTSBCSU9TPiBvbiBtb3RoZXJib2FyZA0KYXBtOiBmb3VuZCBBUE0gQklP
UyB2MS4yLCBjb25uZWN0ZWQgYXQgdjEuMg0KcGNpYjA6IDxBTUQtNzUxIGhv
c3QgdG8gUENJIGJyaWRnZT4gb24gbW90aGVyYm9hcmQNCnBjaTA6IDxQQ0kg
YnVzPiBvbiBwY2liMA0KcGNpYjE6IDxBTUQtNzUxIFBDSS1QQ0kgKEFHUCkg
YnJpZGdlPiBhdCBkZXZpY2UgMS4wIG9uIHBjaTANCnBjaTE6IDxQQ0kgYnVz
PiBvbiBwY2liMQ0KcGNpMTogPE5WaWRpYSBHZUZvcmNlIEREUiBncmFwaGlj
cyBhY2NlbGVyYXRvcj4gYXQgNS4wIGlycSA3DQppc2FiMDogPFBDSSB0byBJ
U0EgYnJpZGdlICh2ZW5kb3I9MTAyMiBkZXZpY2U9NzQwOCk+IGF0IGRldmlj
ZSA3LjAgb24gcGNpMA0KaXNhMDogPElTQSBidXM+IG9uIGlzYWIwDQphdGFw
Y2kwOiA8QU1EIDc1NiBBVEE2NiBjb250cm9sbGVyPiBwb3J0IDB4ZjAwMC0w
eGYwMGYgYXQgZGV2aWNlIDcuMSBvbiBwY2kwDQphdGEwOiBhdCAweDFmMCBp
cnEgMTQgb24gYXRhcGNpMA0KYXRhMTogYXQgMHgxNzAgaXJxIDE1IG9uIGF0
YXBjaTANCmNoaXAxOiA8UENJIHRvIE90aGVyIGJyaWRnZSAodmVuZG9yPTEw
MjIgZGV2aWNlPTc0MGIpPiBhdCBkZXZpY2UgNy4zIG9uIHBjaTANCm9oY2kw
OiA8QU1ELTc1NiBVU0IgQ29udHJvbGxlcj4gbWVtIDB4ZTgwMDEwMDAtMHhl
ODAwMWZmZiBpcnEgNSBhdCBkZXZpY2UgNy40IG9uIHBjaTANCnVzYjA6IE9I
Q0kgdmVyc2lvbiAxLjAsIGxlZ2FjeSBzdXBwb3J0DQp1c2IwOiA8QU1ELTc1
NiBVU0IgQ29udHJvbGxlcj4gb24gb2hjaTANCnVzYjA6IFVTQiByZXZpc2lv
biAxLjANCnVodWIwOiBBTUQgT0hDSSByb290IGh1YiwgY2xhc3MgOS8wLCBy
ZXYgMS4wMC8xLjAwLCBhZGRyIDENCnVodWIwOiA0IHBvcnRzIHdpdGggNCBy
ZW1vdmFibGUsIHNlbGYgcG93ZXJlZA0KdWdlbjA6IENhbm9uIFNjYW5uZXIg
LCByZXYgMS4wMC8xMC4wMSwgYWRkciAyDQp1Z2VuMTogSW9tZWdhIFVTQiBa
aXAgMTAwLCByZXYgMS4wMC8xLjAwLCBhZGRyIDMNCnBjaTA6IDx1bmtub3du
IGNhcmQ+ICh2ZW5kb3I9MHgxMTAyLCBkZXY9MHgwMDAyKSBhdCA4LjAgaXJx
IDEwDQpwY2kwOiA8dW5rbm93biBjYXJkPiAodmVuZG9yPTB4MTEwMiwgZGV2
PTB4NzAwMikgYXQgOC4xDQp4bDA6IDwzQ29tIDNjOTA1LVRYIEZhc3QgRXRo
ZXJsaW5rIFhMPiBwb3J0IDB4ZWMwMC0weGVjM2YgaXJxIDExIGF0IGRldmlj
ZSAxMC4wIG9uIHBjaTANCnhsMDogRXRoZXJuZXQgYWRkcmVzczogMDA6MTA6
NGI6MjI6ODk6ZTgNCm1paWJ1czA6IDxNSUkgYnVzPiBvbiB4bDANCm5zcGh5
MDogPERQODM4NDAgMTAvMTAwIG1lZGlhIGludGVyZmFjZT4gb24gbWlpYnVz
MA0KbnNwaHkwOiAgMTBiYXNlVCwgMTBiYXNlVC1GRFgsIDEwMGJhc2VUWCwg
MTAwYmFzZVRYLUZEWCwgYXV0bw0KeGwwOiBzdXBwbHlpbmcgRVVJNjQ6IDAw
OjEwOjRiOmZmOmZlOjIyOjg5OmU4DQpwY2kwOiA8M0RmeCBWb29kb28gMiBn
cmFwaGljcyBhY2NlbGVyYXRvcj4gYXQgMTIuMA0KZmRjMDogPE5FQyA3MjA2
NUIgb3IgY2xvbmU+IGF0IHBvcnQgMHgzZjAtMHgzZjUsMHgzZjcgaXJxIDYg
ZHJxIDIgb24gaXNhMA0KZmRjMDogRklGTyBlbmFibGVkLCA4IGJ5dGVzIHRo
cmVzaG9sZA0KZmQwOiA8MTQ0MC1LQiAzLjUiIGRyaXZlPiBvbiBmZGMwIGRy
aXZlIDANCmF0a2JkYzA6IDxLZXlib2FyZCBjb250cm9sbGVyIChpODA0Mik+
IGF0IHBvcnQgMHg2MCwweDY0IG9uIGlzYTANCmF0a2JkMDogPEFUIEtleWJv
YXJkPiBpcnEgMSBvbiBhdGtiZGMwDQpwc20wOiA8UFMvMiBNb3VzZT4gaXJx
IDEyIG9uIGF0a2JkYzANCnBzbTA6IG1vZGVsIEdlbmVyaWMgUFMvMiBtb3Vz
ZSwgZGV2aWNlIElEIDANCnZnYTA6IDxHZW5lcmljIElTQSBWR0E+IGF0IHBv
cnQgMHgzYzAtMHgzZGYgaW9tZW0gMHhhMDAwMC0weGJmZmZmIG9uIGlzYTAN
CnNjMDogPFN5c3RlbSBjb25zb2xlPiBvbiBpc2EwDQpzYzA6IFZHQSA8MTYg
dmlydHVhbCBjb25zb2xlcywgZmxhZ3M9MHgyMDA+DQpzaW8wIGF0IHBvcnQg
MHgzZjgtMHgzZmYgaXJxIDQgZmxhZ3MgMHgxMCBvbiBpc2EwDQpzaW8wOiB0
eXBlIDE2NTUwQQ0Kc2lvMSBhdCBwb3J0IDB4MmY4LTB4MmZmIGlycSAzIG9u
IGlzYTANCnNpbzE6IHR5cGUgMTY1NTBBDQpwcGMwOiBwYXJhbGxlbCBwb3J0
IG5vdCBmb3VuZC4NCklQIHBhY2tldCBmaWx0ZXJpbmcgaW5pdGlhbGl6ZWQs
IGRpdmVydCBkaXNhYmxlZCwgcnVsZS1iYXNlZCBmb3J3YXJkaW5nIGRpc2Fi
bGVkLCBkZWZhdWx0IHRvIGFjY2VwdCwgbG9nZ2luZyBsaW1pdGVkIHRvIDEw
MCBwYWNrZXRzL2VudHJ5IGJ5IGRlZmF1bHQNCklQdjYgcGFja2V0IGZpbHRl
cmluZyBpbml0aWFsaXplZCwgZGVmYXVsdCB0byBhY2NlcHQsIGxvZ2dpbmcg
bGltaXRlZCB0byAxMDAgcGFja2V0cy9lbnRyeQ0KYWQwOiA4NjkzTUIgPFNU
MzkxNDBBPiBbMTc2NjIvMTYvNjNdIGF0IGF0YTAtbWFzdGVyIHVzaW5nIFVE
TUEzMw0KYWNkMDogQ0RST00gPEFUQVBJIENEIFJPTSBEUklWRSA1MFggTUFY
PiBhdCBhdGExLW1hc3RlciB1c2luZyBVRE1BMzMNCmFjZDE6IENELVIgPENS
LTQ4MDFURT4gYXQgYXRhMS1zbGF2ZSB1c2luZyBQSU8zDQpNb3VudGluZyBy
b290IGZyb20gdWZzOmFkMHMyYQ0KeGwwOiBzdGFydGluZyBEQUQgZm9yIGZl
ODA6MDAwMTo6MDIxMDo0YmZmOmZlMjI6ODllOA0KeGwwOiBEQUQgY29tcGxl
dGUgZm9yIGZlODA6MDAwMTo6MDIxMDo0YmZmOmZlMjI6ODllOCAtIG5vIGR1
cGxpY2F0ZXMgZm91bmQNCg==
--0-288915071-954623087=:391
Content-Type: TEXT/PLAIN; charset=US-ASCII; name=kernel-config
Content-Transfer-Encoding: BASE64
Content-ID: <Pine.BSF.4.21.0004011604471.391@tv.weeble.dyndns.org>
Content-Description: 
Content-Disposition: attachment; filename=kernel-config

Iw0KIyBTSElUSEVBRCAtLSBHZW5lcmljIGtlcm5lbCBjb25maWd1cmF0aW9u
IGZpbGUgZm9yIEZyZWVCU0QvaTM4Ng0KIw0KIyBGb3IgbW9yZSBpbmZvcm1h
dGlvbiBvbiB0aGlzIGZpbGUsIHBsZWFzZSByZWFkIHRoZSBoYW5kYm9vayBz
ZWN0aW9uIG9uDQojIEtlcm5lbCBDb25maWd1cmF0aW9uIEZpbGVzOg0KIw0K
IyAgICBodHRwOi8vd3d3LmZyZWVic2Qub3JnL2hhbmRib29rL2tlcm5lbGNv
bmZpZy1jb25maWcuaHRtbA0KIw0KIyBUaGUgaGFuZGJvb2sgaXMgYWxzbyBh
dmFpbGFibGUgbG9jYWxseSBpbiAvdXNyL3NoYXJlL2RvYy9oYW5kYm9vaw0K
IyBpZiB5b3UndmUgaW5zdGFsbGVkIHRoZSBkb2MgZGlzdHJpYnV0aW9uLCBv
dGhlcndpc2UgYWx3YXlzIHNlZSB0aGUNCiMgRnJlZUJTRCBXb3JsZCBXaWRl
IFdlYiBzZXJ2ZXIgKGh0dHA6Ly93d3cuRnJlZUJTRC5PUkcvKSBmb3IgdGhl
DQojIGxhdGVzdCBpbmZvcm1hdGlvbi4NCiMNCiMgQW4gZXhoYXVzdGl2ZSBs
aXN0IG9mIG9wdGlvbnMgYW5kIG1vcmUgZGV0YWlsZWQgZXhwbGFuYXRpb25z
IG9mIHRoZQ0KIyBkZXZpY2UgbGluZXMgaXMgYWxzbyBwcmVzZW50IGluIHRo
ZSAuL0xJTlQgY29uZmlndXJhdGlvbiBmaWxlLiBJZiB5b3UgYXJlDQojIGlu
IGRvdWJ0IGFzIHRvIHRoZSBwdXJwb3NlIG9yIG5lY2Vzc2l0eSBvZiBhIGxp
bmUsIGNoZWNrIGZpcnN0IGluIExJTlQuDQojDQojICRGcmVlQlNEOiBzcmMv
c3lzL2kzODYvY29uZi9HRU5FUklDLHYgMS4yNDYgMjAwMC8wMy8wOSAxNjoz
Mjo1NSBqbGVtb24gRXhwICQNCg0KbWFjaGluZQkJaTM4Ng0KY3B1CQlJNjg2
X0NQVQ0KaWRlbnQJCVNISVRIRUFEDQptYXh1c2Vycwk2NA0KDQptYWtlb3B0
aW9ucwlERUJVRz0tZwkJI0J1aWxkIGtlcm5lbCB3aXRoIGdkYigxKSBkZWJ1
ZyBzeW1ib2xzDQoNCm9wdGlvbnMgCU1BVEhfRU1VTEFURQkJI1N1cHBvcnQg
Zm9yIHg4NyBlbXVsYXRpb24NCm9wdGlvbnMgCUlORVQJCQkjSW50ZXJORVR3
b3JraW5nDQpvcHRpb25zIAlJTkVUNgkJCSNJUHY2IGNvbW11bmljYXRpb25z
IHByb3RvY29scw0Kb3B0aW9ucyAJRkZTCQkJI0JlcmtlbGV5IEZhc3QgRmls
ZXN5c3RlbQ0Kb3B0aW9ucyAJRkZTX1JPT1QJCSNGRlMgdXNhYmxlIGFzIHJv
b3QgZGV2aWNlIFtrZWVwIHRoaXMhXQ0Kb3B0aW9ucyAJUFJPQ0ZTCQkJI1By
b2Nlc3MgZmlsZXN5c3RlbQ0Kb3B0aW9ucyAJQ09NUEFUXzQzCQkjQ29tcGF0
aWJsZSB3aXRoIEJTRCA0LjMgW0tFRVAgVEhJUyFdDQpvcHRpb25zIAlVQ09O
U09MRQkJI0FsbG93IHVzZXJzIHRvIGdyYWIgdGhlIGNvbnNvbGUNCm9wdGlv
bnMgCVNZU1ZTSE0JCQkjU1lTVi1zdHlsZSBzaGFyZWQgbWVtb3J5DQpvcHRp
b25zIAlTWVNWTVNHCQkJI1NZU1Ytc3R5bGUgbWVzc2FnZSBxdWV1ZXMNCm9w
dGlvbnMgCVNZU1ZTRU0JCQkjU1lTVi1zdHlsZSBzZW1hcGhvcmVzDQpvcHRp
b25zIAlQMTAwM18xQgkJI1Bvc2l4IFAxMDAzXzFCIHJlYWwtdGltZSBleHRl
bnRpb25zDQpvcHRpb25zIAlfS1BPU0lYX1BSSU9SSVRZX1NDSEVEVUxJTkcN
Cm9wdGlvbnMJCUlDTVBfQkFORExJTQkJI1JhdGUgbGltaXQgYmFkIHJlcGxp
ZXMNCm9wdGlvbnMJCVNDU0lfREVMQVk9MTUwMDAgICAgICAgICNEZWxheSAo
aW4gbXMpIGJlZm9yZSBwcm9iaW5nIFNDU0kNCg0KZGV2aWNlCQlpc2ENCmRl
dmljZQkJcGNpDQoNCiMgRmxvcHB5IGRyaXZlcw0KZGV2aWNlCQlmZGMwCWF0
IGlzYT8gcG9ydCBJT19GRDEgaXJxIDYgZHJxIDINCmRldmljZQkJZmQwCWF0
IGZkYzAgZHJpdmUgMA0KDQojIEFUQSBhbmQgQVRBUEkgZGV2aWNlcw0KZGV2
aWNlCQlhdGEwCWF0IGlzYT8gcG9ydCBJT19XRDEgaXJxIDE0DQpkZXZpY2UJ
CWF0YTEJYXQgaXNhPyBwb3J0IElPX1dEMiBpcnEgMTUNCmRldmljZQkJYXRh
DQpkZXZpY2UJCWF0YWRpc2sJCQkjIEFUQSBkaXNrIGRyaXZlcw0KZGV2aWNl
CQlhdGFwaWNkCQkJIyBBVEFQSSBDRFJPTSBkcml2ZXMNCiNvcHRpb25zIAlB
VEFfU1RBVElDX0lECQkjU3RhdGljIGRldmljZSBudW1iZXJpbmcNCm9wdGlv
bnMgCUFUQV9FTkFCTEVfQVRBUElfRE1BCSNFbmFibGUgRE1BIG9uIEFUQVBJ
IGRldmljZXMNCg0KIyBhdGtiZGMwIGNvbnRyb2xzIGJvdGggdGhlIGtleWJv
YXJkIGFuZCB0aGUgUFMvMiBtb3VzZQ0KZGV2aWNlCQlhdGtiZGMwCWF0IGlz
YT8gcG9ydCBJT19LQkQNCmRldmljZQkJYXRrYmQwCWF0IGF0a2JkYz8gaXJx
IDENCmRldmljZQkJcHNtMAlhdCBhdGtiZGM/IGlycSAxMg0KDQpkZXZpY2UJ
CXZnYTAJYXQgaXNhPw0KDQojIHNwbGFzaCBzY3JlZW4vc2NyZWVuIHNhdmVy
DQpwc2V1ZG8tZGV2aWNlCXNwbGFzaA0KDQojIHN5c2NvbnMgaXMgdGhlIGRl
ZmF1bHQgY29uc29sZSBkcml2ZXIsIHJlc2VtYmxpbmcgYW4gU0NPIGNvbnNv
bGUNCmRldmljZQkJc2MwCWF0IGlzYT8NCg0KIyBGbG9hdGluZyBwb2ludCBz
dXBwb3J0IC0gZG8gbm90IGRpc2FibGUuDQpkZXZpY2UJCW5weDAJYXQgbmV4
dXM/IHBvcnQgSU9fTlBYIGlycSAxMw0KDQojIFBvd2VyIG1hbmFnZW1lbnQg
c3VwcG9ydCAoc2VlIExJTlQgZm9yIG1vcmUgb3B0aW9ucykNCmRldmljZQkJ
YXBtMCAgICBhdCBuZXh1cz8gZmxhZ3MgMHgyMCAjIEFkdmFuY2VkIFBvd2Vy
IE1hbmFnZW1lbnQNCg0KIyBTZXJpYWwgKENPTSkgcG9ydHMNCmRldmljZQkJ
c2lvMAlhdCBpc2E/IHBvcnQgSU9fQ09NMSBmbGFncyAweDEwIGlycSA0DQpk
ZXZpY2UJCXNpbzEJYXQgaXNhPyBwb3J0IElPX0NPTTIgaXJxIDMNCg0KIyBQ
YXJhbGxlbCBwb3J0DQpkZXZpY2UJCXBwYzAJYXQgaXNhPyBpcnEgNw0KZGV2
aWNlCQlwcGJ1cwkJIyBQYXJhbGxlbCBwb3J0IGJ1cyAocmVxdWlyZWQpDQpk
ZXZpY2UJCWxwdAkJIyBQcmludGVyDQpkZXZpY2UJCXBwaQkJIyBQYXJhbGxl
bCBwb3J0IGludGVyZmFjZSBkZXZpY2UNCg0KDQojIFBDSSBFdGhlcm5ldCBO
SUNzIHRoYXQgdXNlIHRoZSBjb21tb24gTUlJIGJ1cyBjb250cm9sbGVyIGNv
ZGUuDQpkZXZpY2UJCW1paWJ1cwkJIyBNSUkgYnVzIHN1cHBvcnQNCmRldmlj
ZQkJeGwJCSMgM0NvbSAzYzkweCAoYGBCb29tZXJhbmcnJywgYGBDeWNsb25l
JycpDQoNCiMgUHNldWRvIGRldmljZXMgLSB0aGUgbnVtYmVyIGluZGljYXRl
cyBob3cgbWFueSB1bml0cyB0byBhbGxvY2F0ZWQuDQpwc2V1ZG8tZGV2aWNl
CWxvb3AJCSMgTmV0d29yayBsb29wYmFjaw0KcHNldWRvLWRldmljZQlldGhl
cgkJIyBFdGhlcm5ldCBzdXBwb3J0DQpwc2V1ZG8tZGV2aWNlCXR1bgkJIyBQ
YWNrZXQgdHVubmVsLg0KcHNldWRvLWRldmljZQlwdHkJCSMgUHNldWRvLXR0
eXMgKHRlbG5ldCBldGMpDQpwc2V1ZG8tZGV2aWNlCW1kCQkjIE1lbW9yeSAi
ZGlza3MiDQpwc2V1ZG8tZGV2aWNlCWdpZgkyCSMgSVB2NiBhbmQgSVB2NCB0
dW5uZWxpbmcNCnBzZXVkby1kZXZpY2UJZmFpdGgJMgkjIElQdjYtdG8tSVB2
NCByZWxheWluZyAodHJhbnNsYXRpb24pDQpwc2V1ZG8tZGV2aWNlCXZuCTIN
CnBzZXVkby1kZXZpY2UJc25wCTINCg0KIyBUaGUgYGJwZicgcHNldWRvLWRl
dmljZSBlbmFibGVzIHRoZSBCZXJrZWxleSBQYWNrZXQgRmlsdGVyLg0KIyBC
ZSBhd2FyZSBvZiB0aGUgYWRtaW5pc3RyYXRpdmUgY29uc2VxdWVuY2VzIG9m
IGVuYWJsaW5nIHRoaXMhDQpwc2V1ZG8tZGV2aWNlCWJwZgkJI0JlcmtlbGV5
IHBhY2tldCBmaWx0ZXINCg0KIyBVU0Igc3VwcG9ydA0KZGV2aWNlCQl1aGNp
CQkjIFVIQ0kgUENJLT5VU0IgaW50ZXJmYWNlDQpkZXZpY2UJCW9oY2kJCSMg
T0hDSSBQQ0ktPlVTQiBpbnRlcmZhY2UNCmRldmljZQkJdXNiCQkjIFVTQiBC
dXMgKHJlcXVpcmVkKQ0KZGV2aWNlCQl1Z2VuCQkjIEdlbmVyaWMNCiNkZXZp
Y2UJCXVoaWQJCSMgIkh1bWFuIEludGVyZmFjZSBEZXZpY2VzIg0KI2Rldmlj
ZQkJdWtiZAkJIyBLZXlib2FyZA0KI2RldmljZQkJdWxwdAkJIyBQcmludGVy
DQojZGV2aWNlCQl1bWFzcwkJIyBEaXNrcy9NYXNzIHN0b3JhZ2UgLSBSZXF1
aXJlcyBzY2J1cyBhbmQgZGENCiNkZXZpY2UJCXVtcwkJIyBNb3VzZQ0KIyBV
U0IgRXRoZXJuZXQsIHJlcXVpcmVzIG1paQ0KI2RldmljZQkJYXVlCQkjIEFE
TXRlayBVU0IgZXRoZXJuZXQNCiNkZXZpY2UJCWN1ZQkJIyBDQVRDIFVTQiBl
dGhlcm5ldA0KI2RldmljZQkJa3VlCQkjIEthd2FzYWtpIExTSSBVU0IgZXRo
ZXJuZXQNCg0Kb3B0aW9ucwkJU09GVFVQREFURVMNCg0Kb3B0aW9ucwkJSVBG
SVJFV0FMTA0Kb3B0aW9ucwkJSVBGSVJFV0FMTF9ERUZBVUxUX1RPX0FDQ0VQ
VA0Kb3B0aW9ucwkJSVBGSVJFV0FMTF9WRVJCT1NFDQpvcHRpb25zCQlJUEZJ
UkVXQUxMX1ZFUkJPU0VfTElNSVQ9MTAwDQoNCm9wdGlvbnMgICAgICAgICBJ
UFY2RklSRVdBTEwNCm9wdGlvbnMgICAgICAgICBJUFY2RklSRVdBTExfREVG
QVVMVF9UT19BQ0NFUFQNCm9wdGlvbnMgICAgICAgICBJUFY2RklSRVdBTExf
VkVSQk9TRQ0Kb3B0aW9ucyAgICAgICAgIElQVjZGSVJFV0FMTF9WRVJCT1NF
X0xJTUlUPTEwMA0KDQpvcHRpb25zCQlTQ19UV09CVVRUT05fTU9VU0UNCm9w
dGlvbnMJCVNDX0hJU1RPUllfU0laRT0xMDAwDQoNCmRldmljZQkJcGNtDQpk
ZXZpY2UJCXNiYw0KDQojU0NTSSBTVFVGRiBGT1IgVVNCIFpJUA0KZGV2aWNl
ICAgICAgICAgIHNjYnVzICAgICAgICAgICAjIFNDU0kgYnVzIChyZXF1aXJl
ZCkNCmRldmljZQkJYWhiDQpkZXZpY2UgICAgICAgICAgZGEgICAgICAgICAg
ICAgICMgRGlyZWN0IEFjY2VzcyAoZGlza3MpDQoNCm9wdGlvbnMJCUREQg0K

--0-288915071-954623087=:391--


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


From owner-freebsd-stable  Sat Apr  1 13:30: 7 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from rover.village.org (rover.village.org [204.144.255.49])
	by hub.freebsd.org (Postfix) with ESMTP id C6BCF37B5E4
	for <stable@FreeBSD.org>; Sat,  1 Apr 2000 13:30:03 -0800 (PST)
	(envelope-from imp@harmony.village.org)
Received: from harmony.village.org (harmony.village.org [10.0.0.6])
	by rover.village.org (8.9.3/8.9.3) with ESMTP id OAA80855;
	Sat, 1 Apr 2000 14:30:02 -0700 (MST)
	(envelope-from imp@harmony.village.org)
Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id OAA47977; Sat, 1 Apr 2000 14:29:29 -0700 (MST)
Message-Id: <200004012129.OAA47977@harmony.village.org>
To: Alexander Frolkin <alexander@frolkin.demon.co.uk>
Subject: Re: Upgrading to 4.0 
Cc: stable@FreeBSD.org
In-reply-to: Your message of "Sat, 01 Apr 2000 18:40:02 +0100."
		<20000401184002.A8017@gamma> 
References: <20000401184002.A8017@gamma>  <20000401170809.A6464@gamma> <20000331190328.A4215@gamma> <200004010140.SAA38998@harmony.village.org> <20000401170809.A6464@gamma> <200004011808.LAA46711@harmony.village.org> 
Date: Sat, 01 Apr 2000 14:29:29 -0700
From: Warner Losh <imp@village.org>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

In message <20000401184002.A8017@gamma> Alexander Frolkin writes:
: Yes, the kernels tells me when a card is inserted or removed.

Then we'll need to get at least part of the panic message.  Can you
enable DDB in the kernel (options DDB) and try again.  Also, before
you insert the ed card, break into the kernel (Ctrl-Alt-Esc) and issue
	w bootverbose 1
	c
so that we get more verbose boot messages.

Make sure that the pccard.conf file specifies only irqs that aren't in 
use.

Warner


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


From owner-freebsd-stable  Sat Apr  1 13:31:37 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from rover.village.org (rover.village.org [204.144.255.49])
	by hub.freebsd.org (Postfix) with ESMTP id 609EC37B569
	for <stable@FreeBSD.ORG>; Sat,  1 Apr 2000 13:31:32 -0800 (PST)
	(envelope-from imp@harmony.village.org)
Received: from harmony.village.org (harmony.village.org [10.0.0.6])
	by rover.village.org (8.9.3/8.9.3) with ESMTP id OAA80863;
	Sat, 1 Apr 2000 14:31:22 -0700 (MST)
	(envelope-from imp@harmony.village.org)
Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id OAA48000; Sat, 1 Apr 2000 14:30:48 -0700 (MST)
Message-Id: <200004012130.OAA48000@harmony.village.org>
To: Alexander Frolkin <alexander@frolkin.demon.co.uk>
Subject: Re: Upgrading to 4.0 
Cc: stable@FreeBSD.ORG
In-reply-to: Your message of "Sat, 01 Apr 2000 19:51:48 +0100."
		<20000401195148.A9141@gamma> 
References: <20000401195148.A9141@gamma>  <20000401170809.A6464@gamma> <20000331190328.A4215@gamma> <200004010140.SAA38998@harmony.village.org> <200004011808.LAA46711@harmony.village.org> <200004011823.LAA04688@nomad.yogotech.com> 
Date: Sat, 01 Apr 2000 14:30:48 -0700
From: Warner Losh <imp@village.org>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

In message <20000401195148.A9141@gamma> Alexander Frolkin writes:
: # ./pccardc enabler 0 ed0 -m 2000 d4000 16 -a 300 -i 3
: 
: It says "device not configured", which leads me to think that I've missed
: something out in the kernel config.

Likely.  I've never ever used enabler in my life.  Don't use it.
pccardd should pick it up all by itself.

Also add
	debuglevel	4
to your pccard.conf file and start syslogd.

Warner


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


From owner-freebsd-stable  Sat Apr  1 14:40: 5 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
	by hub.freebsd.org (Postfix) with ESMTP
	id 0363837BC7E; Sat,  1 Apr 2000 14:40:02 -0800 (PST)
	(envelope-from kris@FreeBSD.org)
Received: from localhost (kris@localhost)
	by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id OAA06725;
	Sat, 1 Apr 2000 14:40:01 -0800 (PST)
	(envelope-from kris@FreeBSD.org)
X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs
Date: Sat, 1 Apr 2000 14:40:01 -0800 (PST)
From: Kris Kennaway <kris@FreeBSD.org>
To: rjk191@psu.edu
Cc: freebsd-stable@freebsd.org, ports@freebsd.org
Subject: Re: INDEX version number of libtool is wrong
In-Reply-To: <20000401133051.A15989@rjk191.rh.psu.edu>
Message-ID: <Pine.BSF.4.21.0004011437330.4346-100000@freefall.freebsd.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Sat, 1 Apr 2000, Ray Kohler wrote:

> The ports INDEX has version 1.3.4 for devel/libtool, but the port
> itself is only 1.3.3. What happened here? Is libtool about to be
> updated, but hasn't been yet? I find this situation surprising,
> since usually the INDEX is behind the ports, but I've never seen it
> ahead of them before...

Yes. Satoshi upgraded the index because it was "about to be committed",
but for some reason it wasn't..it's been like this for a few days now.

Kris

----
In God we Trust -- all others must submit an X.509 certificate.
    -- Charles Forsythe <forsythe@alum.mit.edu>



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


From owner-freebsd-stable  Sat Apr  1 15:29:32 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from mail.rdc1.il.home.com (ha1.rdc1.il.home.com [24.2.1.66])
	by hub.freebsd.org (Postfix) with ESMTP id 58D6D37B795
	for <freebsd-stable@freebsd.org>; Sat,  1 Apr 2000 15:29:29 -0800 (PST)
	(envelope-from stephen@math.missouri.edu)
Received: from math.missouri.edu ([24.12.197.197]) by mail.rdc1.il.home.com
          (InterMail v4.01.01.00 201-229-111) with ESMTP
          id <20000401232927.NETC4993.mail.rdc1.il.home.com@math.missouri.edu>;
          Sat, 1 Apr 2000 15:29:27 -0800
Message-ID: <38E686A2.BC52FBA3@math.missouri.edu>
Date: Sat, 01 Apr 2000 17:30:42 -0600
From: Stephen Montgomery-Smith <stephen@math.missouri.edu>
X-Mailer: Mozilla 4.72 [en] (X11; I; Linux 2.2.12 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Brad Knowles <blk@skynet.be>
Cc: Coleman Kane <cokane@one.net>,
	Jeff Fisher <jeff@jeffenstein.org>, freebsd-stable@freebsd.org
Subject: Re: What is needed in /stand
References: <20000401004437.A6904@evil.2y.net>
	 <Pine.BSF.4.21.0004011039040.41431-100000@localhost>
	 <20000401135701.A11341@evil.2y.net> <v0422080ab50c1240f6d9@[194.78.233.215]>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Brad Knowles wrote:
>
>         Many years ago I learned that making /tmp a symlink to /usr/tmp
> was a bad idea.
>

What was the experience that taught you this lesson?  (I have always
done this.) 

-- 

Stephen Montgomery-Smith              stephen@math.missouri.edu
307 Math Science Building             stephen@showme.missouri.edu
Department of Mathematics             stephen@missouri.edu
University of Missouri-Columbia
Columbia, MO 65211
USA

Phone (573) 882 4540
Fax   (573) 882 1869

http://www.math.missouri.edu/~stephen


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


From owner-freebsd-stable  Sat Apr  1 15:39: 4 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from frolkin.demon.co.uk (frolkin.demon.co.uk [194.222.100.41])
	by hub.freebsd.org (Postfix) with ESMTP id 3FAFB37B7E4
	for <stable@freebsd.org>; Sat,  1 Apr 2000 15:38:57 -0800 (PST)
	(envelope-from sasha@frolkin.demon.co.uk)
Received: from sasha by frolkin.demon.co.uk with local (Exim 3.12 #1)
	id 12bWYo-0003M8-00; Sat, 01 Apr 2000 23:40:06 +0100
Date: Sat, 1 Apr 2000 23:40:05 +0100
From: Alexander Frolkin <alexander@frolkin.demon.co.uk>
To: Warner Losh <imp@village.org>
Cc: stable@freebsd.org
Subject: Re: Upgrading to 4.0
Message-ID: <20000401234004.A12815@gamma>
Reply-To: Alexander Frolkin <alexander@frolkin.demon.co.uk>
References: <20000401195148.A9141@gamma> <20000401170809.A6464@gamma> <20000331190328.A4215@gamma> <200004010140.SAA38998@harmony.village.org> <200004011808.LAA46711@harmony.village.org> <200004011823.LAA04688@nomad.yogotech.com> <20000401195148.A9141@gamma> <200004012130.OAA48000@harmony.village.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.5i
In-Reply-To: <200004012130.OAA48000@harmony.village.org>; from Warner Losh on Sat, Apr 01, 2000 at 02:30:48PM -0700
X-Operating-System: Linux 2.2.14
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Sat, Apr 01, 2000 at 02:30:48PM -0700, Warner Losh wrote:
> In message <20000401195148.A9141@gamma> Alexander Frolkin writes:
> : # ./pccardc enabler 0 ed0 -m 2000 d4000 16 -a 300 -i 3
> : 
> : It says "device not configured", which leads me to think that I've missed
> : something out in the kernel config.
> 
> Likely.  I've never ever used enabler in my life.  Don't use it.
> pccardd should pick it up all by itself.
> 
> Also add
> 	debuglevel	4
> to your pccard.conf file and start syslogd.

I've managed to get it working, I was using the wrong IRQ for
pcic0, so I'm now typing this in 4.0 :-), and everything seems to be working
fine, including the network card.


Thanks,
Alexander.


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


From owner-freebsd-stable  Sat Apr  1 15:45:37 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
	by hub.freebsd.org (Postfix) with ESMTP id 0244E37B9EC
	for <freebsd-stable@freebsd.org>; Sat,  1 Apr 2000 15:45:35 -0800 (PST)
	(envelope-from kris@FreeBSD.org)
Received: from localhost (kris@localhost)
	by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id PAA17383
	for <freebsd-stable@freebsd.org>; Sat, 1 Apr 2000 15:45:34 -0800 (PST)
	(envelope-from kris@FreeBSD.org)
X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs
Date: Sat, 1 Apr 2000 15:45:34 -0800 (PST)
From: Kris Kennaway <kris@FreeBSD.org>
Cc: freebsd-stable@freebsd.org
Subject: Re: 3.4-RELEASE; panic while paging
In-Reply-To: <20000401160825.A24822@speedy.gsinet>
Message-ID: <Pine.BSF.4.21.0004011543310.15957-100000@freefall.freebsd.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Sat, 1 Apr 2000, Gerhard Sittig wrote:

> BTW:  I obviously read this list, so I don't need a courtesy
> copy.  Seems it's about time to setup a dupe filter unless people
> get used to the list-reply functions instead of using
> group-reply.  It should always be a clear decision whether to
> reply in private or in public and appropriate action should be
> the consequence.

As has been pointed out, it's not always obvious. I just use this in my
.procmailrc:

#######################################################
# KEEP AN 8K CACHE OF MESSAGE IDS AND FILTER DUPLICATES
#######################################################

:0 Wh: msgid.lock
| formail -D 8192 msgid.cache

Kris




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


From owner-freebsd-stable  Sat Apr  1 17:12:25 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from thehousleys.net (frenchknot.ne.mediaone.net [24.147.224.201])
	by hub.freebsd.org (Postfix) with ESMTP id 32B9E37B8CD
	for <freebsd-stable@freebsd.org>; Sat,  1 Apr 2000 17:12:22 -0800 (PST)
	(envelope-from jim@thehousleys.net)
Received: from thehousleys.net (baby.int.thehousleys.net [192.168.0.24])
	by thehousleys.net (8.9.3/8.9.3) with ESMTP id UAA36804
	for <freebsd-stable@freebsd.org>; Sat, 1 Apr 2000 20:12:19 -0500 (EST)
Message-ID: <38E69E73.4CFF971C@thehousleys.net>
Date: Sat, 01 Apr 2000 20:12:19 -0500
From: James Housley <jim@thehousleys.net>
Organization: The Housleys dot Net
X-Mailer: Mozilla 4.72 [en] (X11; U; FreeBSD 3.4-STABLE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: freebsd-stable@freebsd.org
Subject: Building 4.x on 3.x
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

I got an old pentium 100 laptop that I want to play around with 4.x on. 
It's disk to too small to hold the source tree, obj tree and useful
programs.  Is it okay to do the buildworld on my 3.4-Stable server with
more memory, speed, disk, etc....  Then nfs mount the src & obj trees to
do the install world and build kernel??

Since this is how a source upgrade would be done my guess is yes, but I
just want to check.

Jim
-- 
In God we Trust -- all others must submit an X.509 certificate.
    -- Charles Forsythe <forsythe@alum.mit.edu>


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


From owner-freebsd-stable  Sat Apr  1 18:45:18 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from rover.village.org (rover.village.org [204.144.255.49])
	by hub.freebsd.org (Postfix) with ESMTP id 3AA2837B65E
	for <freebsd-stable@FreeBSD.ORG>; Sat,  1 Apr 2000 18:45:14 -0800 (PST)
	(envelope-from imp@harmony.village.org)
Received: from harmony.village.org (harmony.village.org [10.0.0.6])
	by rover.village.org (8.9.3/8.9.3) with ESMTP id TAA81878;
	Sat, 1 Apr 2000 19:45:12 -0700 (MST)
	(envelope-from imp@harmony.village.org)
Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id TAA50157; Sat, 1 Apr 2000 19:44:38 -0700 (MST)
Message-Id: <200004020244.TAA50157@harmony.village.org>
To: James Housley <jim@thehousleys.net>
Subject: Re: Building 4.x on 3.x 
Cc: freebsd-stable@FreeBSD.ORG
In-reply-to: Your message of "Sat, 01 Apr 2000 20:12:19 EST."
		<38E69E73.4CFF971C@thehousleys.net> 
References: <38E69E73.4CFF971C@thehousleys.net>  
Date: Sat, 01 Apr 2000 19:44:38 -0700
From: Warner Losh <imp@village.org>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

In message <38E69E73.4CFF971C@thehousleys.net> James Housley writes:
: I got an old pentium 100 laptop that I want to play around with 4.x on. 
: It's disk to too small to hold the source tree, obj tree and useful
: programs.  Is it okay to do the buildworld on my 3.4-Stable server with
: more memory, speed, disk, etc....  Then nfs mount the src & obj trees to
: do the install world and build kernel??
: 
: Since this is how a source upgrade would be done my guess is yes, but I
: just want to check.

I've been able to buildworld on 3.4 the 4.0 sources just before 4.0
was released.

Warner


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


From owner-freebsd-stable  Sat Apr  1 21: 7:14 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from dt051n0b.san.rr.com (dt051n0b.san.rr.com [204.210.32.11])
	by hub.freebsd.org (Postfix) with ESMTP id B2FC437B704
	for <freebsd-stable@FreeBSD.ORG>; Sat,  1 Apr 2000 21:07:11 -0800 (PST)
	(envelope-from Doug@gorean.org)
Received: from gorean.org (doug@master [10.0.0.2])
	by dt051n0b.san.rr.com (8.9.3/8.9.3) with ESMTP id VAA86039;
	Sat, 1 Apr 2000 21:07:08 -0800 (PST)
	(envelope-from Doug@gorean.org)
Message-ID: <38E6D57C.920976F2@gorean.org>
Date: Sat, 01 Apr 2000 21:07:08 -0800
From: Doug Barton <Doug@gorean.org>
Organization: Triborough Bridge & Tunnel Authority
X-Mailer: Mozilla 4.72 [en] (X11; U; FreeBSD 5.0-CURRENT-0325 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Mikhail Teterin <mi@kot.ne.mediaone.net>
Cc: freebsd-stable@FreeBSD.ORG
Subject: Re: erroneous messages filtering ((no subject))
References: <200004011539.KAA70786@rtfm.newton>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Mikhail Teterin wrote:
> 
> How hard is it to reject messages  with blank lines n the body only, or,
> if there is  only non-blank line, to check it  for the ``*subscribe''? I
> know, the mailing  list software check the number of  crossposts -- this
> seems even easier...

	It's actually quite easy. The problem is that those kinds of filters
are either so restrictive that they filter posts that they should not,
or so loose as to not really be of much use. 

Doug
-- 
    "So, the cows were part of a dream that dreamed itself into
existence? Is that possible?" asked the student incredulously.
    The master simply replied, "Mu."


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


From owner-freebsd-stable  Sat Apr  1 22: 7:38 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from xxx.video-collage.com (xxx.video-collage.com [209.122.149.226])
	by hub.freebsd.org (Postfix) with ESMTP id 4B5A037B6AB
	for <freebsd-stable@FreeBSD.ORG>; Sat,  1 Apr 2000 22:07:32 -0800 (PST)
	(envelope-from mi@video-collage.com)
X-Relay-IP: ‚ 
Received: from dufus.video-collage.com (dufus [10.222.222.77])
	by xxx.video-collage.com (8.9.1a/8.9.1) with ESMTP id BAA20629;
	Sun, 2 Apr 2000 01:07:29 -0500 (EST)
From: Mikhail Teterin <mi@video-collage.com>
Received: (from mi@localhost)
	by dufus.video-collage.com (8.9.3/8.9.3) id BAA38557;
	Sun, 2 Apr 2000 01:07:39 -0500 (EST)
	(envelope-from mi@xxx)
Message-Id: <200004020607.BAA38557@dufus.video-collage.com>
Subject: Re: erroneous messages filtering ((no subject))
In-Reply-To: <38E6D57C.920976F2@gorean.org> from Doug Barton at "Apr 1, 2000
 09:07:08 pm"
To: Doug Barton <Doug@gorean.org>
Date: Sun, 2 Apr 2000 01:07:39 -0500 (EST)
Cc: freebsd-stable@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL68 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> Mikhail Teterin wrote:
> > 
> > How  hard is  it to  reject  messages with  blank lines  n the  body
> > only,  or, if  there is  only non-blank  line, to  check it  for the
> > ``*subscribe''? I know,  the mailing list software  check the number
> > of crossposts -- this seems even easier...
>
>  It's actually quite easy. The problem  is that those kinds of filters
> are either so restrictive that they filter posts that they should not,
> or so loose as to not really be of much use.

I'd come up with  a filter to defeat this claim, but  I'm afraid it will
not be employed anyway...

	-mi


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


From owner-freebsd-stable  Sat Apr  1 22:45:13 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from turtle.looksharp.net (cc360882-a.strhg1.mi.home.com [24.2.221.22])
	by hub.freebsd.org (Postfix) with ESMTP id D9F1337B6B6
	for <freebsd-stable@FreeBSD.ORG>; Sat,  1 Apr 2000 22:44:57 -0800 (PST)
	(envelope-from bandix@looksharp.net)
Received: from localhost (bandix@localhost)
	by turtle.looksharp.net (8.9.3/8.9.3) with ESMTP id BAA04324;
	Sun, 2 Apr 2000 01:43:43 -0500 (EST)
	(envelope-from bandix@looksharp.net)
Date: Sun, 2 Apr 2000 01:43:43 -0500 (EST)
From: "Brandon D. Valentine" <bandix@looksharp.net>
To: Mikhail Teterin <mi@video-collage.com>
Cc: Doug Barton <Doug@gorean.org>, freebsd-stable@FreeBSD.ORG
Subject: Re: erroneous messages filtering ((no subject))
In-Reply-To: <200004020607.BAA38557@dufus.video-collage.com>
Message-ID: <Pine.BSF.4.21.0004020141190.4312-100000@turtle.looksharp.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Sun, 2 Apr 2000, Mikhail Teterin wrote:

>>  It's actually quite easy. The problem  is that those kinds of filters
>> are either so restrictive that they filter posts that they should not,
>> or so loose as to not really be of much use.
>
>I'd come up with  a filter to defeat this claim, but  I'm afraid it will
>not be employed anyway...
>
>	-mi

As far as I'm concerned there are better ways for the project to spend
its time than catering to the demands of those too lazy to setup their
own procmail filters.  The original poster can filter his own mail.

Brandon D. Valentine
-- 
    "...and as for hackers, we note that all of those known to
    The Register are so strapped financially that seizing their
    property would be tantamount to squeezing blood from a stone."
                                     -- The Register, 02/17/2000



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