From owner-freebsd-current Sun Jul 12 07:34:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA29891 for freebsd-current-outgoing; Sun, 12 Jul 1998 07:34:52 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from atlantis.nconnect.net (atlantis.nconnect.net [207.227.50.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA29886 for ; Sun, 12 Jul 1998 07:34:50 -0700 (PDT) (envelope-from randyd@nconnect.net) Received: from nconnect.net (birddog-mke-x2-13.nconnect.net [207.227.61.13]) by atlantis.nconnect.net (8.8.5/8.8.5) with ESMTP id JAA05758 for ; Sun, 12 Jul 1998 09:24:55 -0500 (CDT) Message-ID: <35A8C969.9C2EFD6F@nconnect.net> Date: Sun, 12 Jul 1998 09:34:17 -0500 From: Randy DuCharme Organization: Astrolab Development X-Mailer: Mozilla 4.05 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: Softupdates panic? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greetings, Is this that hard-to-catch softupdates panic, or is this something else? Panic: handle_workitem_freeblocks: block count mp_lock = 01000001; cpuid = 1; lapic-id = 01000000 Debugger("panic") Stopped at _Debugger+0x35: movb $0,_in_Debugger.98 db> -- Randall D DuCharme Systems Engineer Novell, Microsoft, and UNIX Networking Support Computer Specialists Free Your Machine.... FreeBSD 414-253-9998 414-253-9919 (fax) The Power To Serve! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 12 09:31:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA13666 for freebsd-current-outgoing; Sun, 12 Jul 1998 09:31:51 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA13625 for ; Sun, 12 Jul 1998 09:31:38 -0700 (PDT) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.0/frmug-2.3/nospam) with UUCP id SAA10056 for freebsd-current@FreeBSD.ORG; Sun, 12 Jul 1998 18:31:31 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: (from roberto@localhost) by keltia.freenix.fr (8.9.0.Beta4/keltia-2.14/nospam) id SAA18353 for freebsd-current@FreeBSD.ORG; Sun, 12 Jul 1998 18:29:36 +0200 (CEST) (envelope-from roberto) Message-ID: <19980712182936.A18333@keltia.freenix.fr> Date: Sun, 12 Jul 1998 18:29:36 +0200 From: Ollivier Robert To: "FreeBSD Current Users' list" Subject: Weirdness in CURRENT Mail-Followup-To: FreeBSD Current Users' list Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93i X-Operating-System: FreeBSD 3.0-CURRENT ctm#4462 AMD-K6 MMX @ 225 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Am I the one only to see this during "make world" ? - why the "cd .../games; cp ..." ?? - why trying to build build-tools inside "/usr/src/bin/sh" ? CTM cvs-cur #4462 build on 1998/07/12 15:08 -=-=-=-=-=- cc -O -pipe -DSHELL -I. -I/src/src/bin/sh -I/usr/obj/usr/src/tmp/usr/include -c /src/src/bin/sh/output.c cc -O -pipe -DSHELL -I. -I/src/src/bin/sh -I/usr/obj/usr/src/tmp/usr/include -c /src/src/bin/sh/var.c cc -O -pipe -DSHELL -I. -I/src/src/bin/sh -I/usr/obj/usr/src/tmp/usr/include -static -o sh arith.o arith_lex.o builtins.o init.o nodes.o syntax.o alias.o cd.o echo.o error.o eval.o exec.o expand.o histedit.o input.o jobs.o mail.o main.o memalloc.o miscbltin.o mystring.o options.o parser.o printf.o redir.o show.o trap.o output.o var.o -ll -ledit -ltermcap install -C -c -c -s -o root -g staff -m 555 sh /usr/obj/usr/src/tmp/bin cd /usr/obj/usr/src/tmp/usr/games; cp -p caesar strfile /usr/obj/usr/src/tmp/usr/bin cd /src/src/bin/sh; /usr/obj/usr/src/tmp/usr/bin/make -DNOINFO -DNOMAN -DNOPROFILE -D_BUILD_TOOLS build-tools make: don't know how to make build-tools. Stop *** Error code 2 Stop. *** Error code 1 Stop. 896.86 real 644.03 user 203.18 sys Sun Jul 12 18:14:08 CEST 1998 -=-=-=-=-=- -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #11: Sat Jun 27 00:41:06 CEST 1998 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 12 10:47:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA24356 for freebsd-current-outgoing; Sun, 12 Jul 1998 10:47:46 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dillinger.io.com (euclid@dillinger.io.com [199.170.88.11]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA24351 for ; Sun, 12 Jul 1998 10:47:43 -0700 (PDT) (envelope-from euclid@dillinger.io.com) Received: (from euclid@localhost) by dillinger.io.com (8.8.7/8.8.5) id MAA17029; Sun, 12 Jul 1998 12:47:41 -0500 (CDT) Message-ID: <19980712124741.46946@io.com> Date: Sun, 12 Jul 1998 12:47:41 -0500 From: Matthew Jason Euclid Barnhart To: freebsd-current@FreeBSD.ORG Subject: Secure portmap in /usr/src/usr.sbin/portmap Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i X-Barnyard-Animals: Chickens Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG My system is PII/266, running 3.0-CURRENT (daily cvsup). I've installed tcp_wrappers-7.6 from the Ports collection, and tcpd works fine from inetd. In looking at the Makefile and source for the distributed portmap, it looks as though I can simply define HOSTS_ACCESS (which I've tried in /etc/make.conf, and by hand) to enable wrappers support. However, every compile fails as such: cc -O -pipe -DHOSTS_ACCESS -DCHECK_PORT -o portmap portmap.o from_local.o pmap_check.o pmap_check.o: Undefined symbol `_hosts_ctl' referenced from text segment pmap_check.o: Undefined symbol `_hosts_ctl' referenced from text segment pmap_check.o: Undefined symbol `_hosts_ctl' referenced from text segment *** Error code 1 Stop. I'm sure I'm doing something completely stupid. Any guidance is appreciated, as I'm at my wit's end with this. Thanks... -- Matthew Jason Euclid Barnhart - euclid@io.com - http://www.io.com/~trc/Euclid/ The Transcontinental Recording Company - trc@io.com - http://www.io.com/~trc/ "God shows his contempt for wealth by the kind of person He selects to receive it." -- Austin O'Malley (1858-1952) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 12 11:04:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA26696 for freebsd-current-outgoing; Sun, 12 Jul 1998 11:04:43 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from magnet.geophysik.tu-freiberg.de (magnet.geophysik.tu-freiberg.de [139.20.128.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA26690 for ; Sun, 12 Jul 1998 11:04:41 -0700 (PDT) (envelope-from freebsd@magnet.geophysik.tu-freiberg.de) Received: (from freebsd@localhost) by magnet.geophysik.tu-freiberg.de (8.8.8/8.7.3) id UAA07724; Sun, 12 Jul 1998 20:04:31 +0200 (CEST) From: Holm Tiffe Message-Id: <199807121804.UAA07724@magnet.geophysik.tu-freiberg.de> Subject: Re: Arrgh ! resubscribing again again again.... In-Reply-To: <199807120621.XAA29796@usr07.primenet.com> from Terry Lambert at "Jul 12, 98 06:21:52 am" To: tlambert@primenet.com (Terry Lambert) Date: Sun, 12 Jul 1998 20:04:30 +0200 (CEST) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL26 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > TL> You don't *have* to do that. You *could* shutdown your X server and > > TL> restart it. You simply choose to have your demons die, instead of > > TL> doing this and/or limiting the amount of VM available to the X server > > TL> and Netscape, or disabling the X shm extensions. > > > > Terry, your explanation is ok. But what X-server should I shutdown? > > For I don't have any X's. And yesterday I repeated 'make -j64 buildworld', > > and as always: sendmail childs die with SIGSEGV, cron seems to be in > > memory, but no cron jobs run. And all that after makeworld has finished, > > system is _absolutely_ idle. > > Interesting. Clearly, you're not the person running Netscape to > cause a similar problem. 8-). I'am that person, but Terry I have never sayed that this problem only occurs when I run netscape ! This was only an easy to reproduce example, any big job on that lousy 486 triggers the same set of problems. > > Do you have any zombie processes? > No zombies at all, but childs from system programs and any other program that was paget out, are getting killed by a segfault. Non - forking programs in the background are runnig fine so far. Maybe that fork's copy from the process space gets corrupted after an VM exhaust ? > Have you looked at the vmstat output? > > If you kill -HUP cron, what happens? > > If you kill -HUP sendmail, what happens? > I'll try that. > Did you get any errors in the buildworld, or did it complete without > damaging itself (only damaging sendmail and cron)? > Long time ago, that I have build worlds on that machine. Installworld is working fine. > Are you overclocking your CPU? No. > > How much memory do you have -- is it enough that if you missed a > refresh cycle or two (say, because you did something silly, like > a buildworld with -j64 and you have an Adaptec controller with a > high bus-on time, or you are using a PIO IDE controller, etc...), > that the upper memory contents might degrade and cause these problems? Terry Terry, there are several guys here, all claiming about the same refresh problem ? Oh no. This is easy to reproduce, just put memory out of your computer and let run big jobs. [..] > > It would be nice to know if this problem was the result of running > out of VM, or if you can cause it by load without actually exhasting > the VM... > > Makeworld takes a while; have you tried putting a crontab entry that > spits the time out to the console once a minute, and bracketing the > buildworld with "date"? Interesting idea. > > Maybe it's a particular section of the tree, and not the load, that's > getting you? Perhaps that region of the disk is corrupt? And that netscape thing by me ? I'll try to give you an other example tomorrow. Holm -- ******************************************************************************* * Holm Tiffe holm@geophysik.tu-freiberg.de * * Freiberger Strasse 24 * * 09600 Kleinschirma, Germany Microsoft is not the Answer - * * Tel.: 49 3731 74233 Microsoft is the Question, * * UUCP: 49 3731 73719 unicorn!holm and the Answer is no ! * ******************************************************************************* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 12 11:45:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA00773 for freebsd-current-outgoing; Sun, 12 Jul 1998 11:45:33 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alushta.NL.net (alushta.NL.net [193.78.240.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA00768 for ; Sun, 12 Jul 1998 11:45:30 -0700 (PDT) (envelope-from benst@terminus.stuyts.nl) Received: from stuyts by alushta.NL.net with UUCP id <9016-17282>; Sun, 12 Jul 1998 20:45:22 +0200 Received: from daneel.stuyts.nl (daneel.stuyts.nl [193.78.231.7]) by terminus.stuyts.nl (8.8.8/8.8.8) with ESMTP id TAA21623 for ; Sun, 12 Jul 1998 19:36:34 +0200 (MET DST) (envelope-from benst) Received: (from benst@localhost) by daneel.stuyts.nl (8.8.5/8.8.5) id TAA06849 for current@freebsd.org; Sun, 12 Jul 1998 19:36:30 +0200 (MET DST) Message-Id: <199807121736.TAA06849@daneel.stuyts.nl> Content-Type: text/plain MIME-Version: 1.0 (NeXT Mail 3.3 v118.2) X-Nextstep-Mailer: Mail 3.3 (Enhance 1.2) Received: by NeXT.Mailer (1.118.2) From: Ben Stuyts Date: Sun, 12 Jul 98 19:36:28 +0200 To: current@FreeBSD.ORG Subject: Cputime limit exceeded Reply-To: ben@stuyts.nl Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I often get the Cputime limit exceeded errors from news-related programs. For example: > Date: Sun, 12 Jul 1998 15:10:00 +0200 (MET DST) > From: News Subsystem > To: newscrisis > Subject: news (urgent): possible expire problems > > 66048 kept, 6032 expired > 3141 residual lines > 31 links archived, 6997 junked, 154 missing > Cputime limit exceeded > /usr/local/news/cnewsbin/nov/expov: expovguts failed in comp/sys/next/announce > ...using fallback code This if from the password file: news:*:8:8:news:0:0:News Subsystem:/:/nonexistent And this from login.conf: news:\ :path=/usr/local/news/bin /bin /sbin /usr/bin /usr/sbin /usr/local/bin /usr/local/sbin:\ :cputime=infinity:\ :filesize=128M:\ :datasize-cur=64M:\ :stacksize-cur=32M:\ :coredumpsize-cur=0:\ :maxmemorysize-cur=128M:\ :memorylocked=32M:\ :maxproc=128:\ :openfiles=256:\ :tc=default: I am running xntpd, but at those times there is no internet connection up. I thought setting cputime=infinity would solve the problem, but it didn't. I saw in the archives that more people had this kind of problem, but I couldn't find a solution to it. The system is cvsupped and built last on June 12. It has otherwise been quite stable. Thanks, Ben To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 12 13:03:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA07399 for freebsd-current-outgoing; Sun, 12 Jul 1998 13:03:17 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from titus.stade.co.uk (stade.demon.co.uk [158.152.29.164]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA07391 for ; Sun, 12 Jul 1998 13:03:14 -0700 (PDT) (envelope-from aw1@stade.co.uk) Received: (from aw1@localhost) by titus.stade.co.uk (8.8.8/8.8.8) id RAA03481; Sun, 12 Jul 1998 17:02:09 +0100 (BST) (envelope-from aw1) Message-ID: <19980712170208.A2656@stade.co.uk> Date: Sun, 12 Jul 1998 17:02:08 +0100 From: Adrian Wontroba To: freebsd-current@FreeBSD.ORG Subject: Re: SOLUTION! 2.2.6-Release to -current Reply-To: aw1@stade.co.uk Mail-Followup-To: freebsd-current@FreeBSD.ORG References: <199807100843.SAA27370@cimlogic.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199807100843.SAA27370@cimlogic.com.au>; from John Birrell on Fri, Jul 10, 1998 at 06:43:49PM +1000 Organization: Stade Computers Ltd, UK X-Phone: +(44) 121 681 6677 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jul 10, 1998 at 06:43:49PM +1000, John Birrell wrote: > *Grumble*. Today I went though the exercise of installing 2.2.6-RELEASE > from the CD that WC ships. I booted from the install CD, used the visual To reinforce this - I've just upgraded my 2.2-STABLE box to 3.0-CURRENT by following the buildworld / installworld, build kernel, sort out /etc route with very little trouble. I must confess that the new named caught me out, but other than that things went far more smoothly than I had anticipated. -- Adrian Wontroba, Stade Computers Limited. phone: (+44) 121 681 6677 Mail info@accu.org for information about the Association of C and C++ Users or see To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 12 13:03:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA07473 for freebsd-current-outgoing; Sun, 12 Jul 1998 13:03:37 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from burka.carrier.kiev.ua (root@burka.carrier.kiev.ua [193.193.193.107]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA07456 for ; Sun, 12 Jul 1998 13:03:26 -0700 (PDT) (envelope-from archer@grape.carrier.kiev.ua) Received: from kozlik.carrier.kiev.ua (kozlik.carrier.kiev.ua [193.193.193.111]) by burka.carrier.kiev.ua (8.9.0/8.Who.Cares) with ESMTP id XAA09976; Sun, 12 Jul 1998 23:03:11 +0300 (EEST) Received: (from uucp@localhost) by kozlik.carrier.kiev.ua (8.9.0/8.9.0/8.Who.Cares) with UUCP id XAA08636; Sun, 12 Jul 1998 23:00:49 +0300 (EEST) Received: (from archer@localhost) by grape.carrier.kiev.ua (8.8.8/8.8.8) id WAA20384; Sun, 12 Jul 1998 22:35:58 +0300 (EEST) (envelope-from archer) Message-ID: <19980712223558.37658@carrier.kiev.ua> Date: Sun, 12 Jul 1998 22:35:58 +0300 From: Alexander Litvin To: Terry Lambert Cc: current@FreeBSD.ORG Subject: Re: Arrgh ! resubscribing again again again.... References: <199807120536.IAA07205@grape.carrier.kiev.ua> <199807120621.XAA29796@usr07.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88e In-Reply-To: <199807120621.XAA29796@usr07.primenet.com>; from Terry Lambert on Sun, Jul 12, 1998 at 06:21:52AM +0000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jul 12, 1998 at 06:21:52AM +0000, Terry Lambert wrote: > > TL> You don't *have* to do that. You *could* shutdown your X server and > > TL> restart it. You simply choose to have your demons die, instead of > > TL> doing this and/or limiting the amount of VM available to the X server > > TL> and Netscape, or disabling the X shm extensions. > > > > Terry, your explanation is ok. But what X-server should I shutdown? > > For I don't have any X's. And yesterday I repeated 'make -j64 buildworld', > > and as always: sendmail childs die with SIGSEGV, cron seems to be in > > memory, but no cron jobs run. And all that after makeworld has finished, > > system is _absolutely_ idle. > > Interesting. Clearly, you're not the person running Netscape to > cause a similar problem. 8-). > > Do you have any zombie processes? No. > Have you looked at the vmstat output? Noting interesting, it seems. Just ordinary idle system. > If you kill -HUP cron, what happens? It doesn't help, at least in the cases I tried it. > If you kill -HUP sendmail, what happens? Well, sendmail restarts. May be it is not the same always. Though today it restarted just fine. > Did you get any errors in the buildworld, or did it complete without > damaging itself (only damaging sendmail and cron)? Well, sometimes it worked, simetimes -- no, though I cannot say for sure whether it was due to VM shortage, or because the world was broken at the time (I tested it several times with sources of different dates). > Are you overclocking your CPU? No. > How much memory do you have -- is it enough that if you missed a > refresh cycle or two (say, because you did something silly, like > a buildworld with -j64 and you have an Adaptec controller with a > high bus-on time, or you are using a PIO IDE controller, etc...), > that the upper memory contents might degrade and cause these problems? I do not exactly understand what you're asking about here. Here's my boot log: Jul 10 23:35:06 grape /kernel: FreeBSD 3.0-CURRENT #96: Fri Jul 10 22:22:46 EEST 1998 Jul 10 23:35:06 grape /kernel: archer@grape.carrier.kiev.ua:/usr/src/sys/compile /GRAPE Jul 10 23:35:06 grape /kernel: Timecounter "i8254" frequency 1193182 Hz cost 4 239 ns Jul 10 23:35:06 grape /kernel: Timecounter "TSC" frequency 120053411 Hz cost 1 96 ns Jul 10 23:35:06 grape /kernel: CPU: Pentium/P54C (120.05-MHz 586-class CPU) Jul 10 23:35:06 grape /kernel: Origin = "GenuineIntel" Id = 0x52c Stepping=12 Jul 10 23:35:06 grape /kernel: Features=0x1bf Jul 10 23:35:06 grape /kernel: real memory = 33554432 (32768K bytes) Jul 10 23:35:06 grape /kernel: avail memory = 30408704 (29696K bytes) Jul 10 23:35:06 grape /kernel: Probing for devices on PCI bus 0: Jul 10 23:35:06 grape /kernel: chip0: rev 0x23 on pci0.0.0 Jul 10 23:35:06 grape /kernel: chip1: rev 0x27 on pc i0.7.0 Jul 10 23:35:06 grape /kernel: ide_pci0: rev 0x06 on pci0.7.1 Jul 10 23:35:06 grape /kernel: Probing for devices on the ISA bus: Jul 10 23:35:06 grape /kernel: sc0 at 0x60-0x6f irq 1 on motherboard Jul 10 23:35:06 grape /kernel: sc0: VGA color <16 virtual consoles, flags=0x0> Jul 10 23:35:06 grape /kernel: sio0 at 0x3f8-0x3ff irq 4 on isa Jul 10 23:35:06 grape /kernel: sio0: type 16550A Jul 10 23:35:06 grape /kernel: sio1 at 0x2f8-0x2ff irq 3 on isa Jul 10 23:35:06 grape /kernel: sio1: type 16550A Jul 10 23:35:06 grape /kernel: fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa Jul 10 23:35:06 grape /kernel: wdc0 at 0x1f0-0x1f7 irq 14 flags 0xa0ffa0ff on is a Jul 10 23:35:06 grape /kernel: wdc0: unit 0 (wd0): , DMA, 32-bit, mult i-block-16 Jul 10 23:35:06 grape /kernel: wd0: 1221MB (2501856 sectors), 2482 cyls, 16 head s, 63 S/T, 512 B/S Jul 10 23:35:06 grape /kernel: wdc1 at 0x170-0x177 irq 15 on isa Jul 10 23:35:06 grape /kernel: wdc1: unit 0 (wd2): Jul 10 23:35:06 grape /kernel: wd2: 257MB (527450 sectors), 959 cyls, 11 heads, 50 S/T, 512 B/S Jul 10 23:35:06 grape /kernel: npx0 flags 0x1 on motherboard Jul 10 23:35:07 grape /kernel: npx0: INT 16 interface Jul 10 23:35:07 grape /kernel: Intel Pentium F00F detected, installing workaroun d > Does -j32 have the same problem? No, there is enough memory to make world with -j32. > -j16? > > etc.? > > It would be nice to know if this problem was the result of running > out of VM, or if you can cause it by load without actually exhasting > the VM... > > Makeworld takes a while; have you tried putting a crontab entry that > spits the time out to the console once a minute, and bracketing the > buildworld with "date"? > > Maybe it's a particular section of the tree, and not the load, that's > getting you? Perhaps that region of the disk is corrupt? I can repeat the effect without building world. In fact I may cause it in some 1-2 minutes -- much faster than with makeworld. I just encountered it for the first time trying to test softupdates, when I ran 'make -j64 buildworld'. Just the same happenes if I just exhaust VM with some other means, e.g., start some 10-15 progs, each mallocing 32M of memory and durtying it. > Obviously, I don't expect you to answer all of these to the list, or > even to me, if the answer to the questions is "no impact". > > > Terry Lambert > terry@lambert.org > --- > Any opinions in this posting are my own and not those of my present > or previous employers. --- Twenty Percent of Zero is Better than Nothing. -- Walt Kelly To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 12 15:30:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA20858 for freebsd-current-outgoing; Sun, 12 Jul 1998 15:30:26 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from duey.hs.wolves.k12.mo.us (root@duey.hs.wolves.k12.mo.us [207.160.214.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA20837; Sun, 12 Jul 1998 15:30:17 -0700 (PDT) (envelope-from cdillon@wolves.k12.mo.us) Received: from duey.hs.wolves.k12.mo.us (cdillon@duey.hs.wolves.k12.mo.us [207.160.214.9]) by duey.hs.wolves.k12.mo.us (8.8.7/8.8.7) with SMTP id RAA15698; Sun, 12 Jul 1998 17:30:14 -0500 (CDT) (envelope-from cdillon@wolves.k12.mo.us) Date: Sun, 12 Jul 1998 17:30:13 -0500 (CDT) From: Chris Dillon X-Sender: cdillon@duey.hs.wolves.k12.mo.us To: Stefan Esser cc: Julian Elischer , current@FreeBSD.ORG Subject: Re: TESTERS NEEDED: Softupdates looks Very good. In-Reply-To: <19980711105643.41001@mi.uni-koeln.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 11 Jul 1998, Stefan Esser wrote: > Don't worry, that's just a precaution taken by the driver code. > There have been SCSI devices that are willing to accept any > data rate offered during negotiation, but actually can't handle > more than 5MHz. These are pre-SCSI-2 drives, which just knew > they are *that* fast, they can handle *any* data rate offered > by the host adapter (which was at most 5MHz at that time ;-) > > The driver won't negotiate data rates beyond 5MHz until the drive > has been identified as a SCSI-2 device, and that's when another > negotiation is started by the driver ... > > Negotiations may be started by both the drive or host adapter > at any time. But except for IBM, most vendors leave it up to > the host system to send the first message (which the driver > does after receiving the result of an INQUIRY command). Ok, makes sense.. I was just wondering. :-) And I guess that last part about IBM drives is a GoodThing? -- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net /* FreeBSD: The fastest and most stable server OS on the planet. For Intel x86 and compatibles (SPARC and Alpha under development) (http://www.freebsd.org) */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 12 16:16:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA00126 for freebsd-current-outgoing; Sun, 12 Jul 1998 16:16:53 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from limbo.rtfm.net (nathan@38.nyack.fcc.net [204.141.125.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA29932 for ; Sun, 12 Jul 1998 16:16:24 -0700 (PDT) (envelope-from nathan@limbo.rtfm.net) Received: (from nathan@localhost) by limbo.rtfm.net (8.8.8/8.8.8) id TAA00206; Sun, 12 Jul 1998 19:15:16 -0400 (EDT) (envelope-from nathan) Message-ID: <19980712191515.A195@rtfm.net> Date: Sun, 12 Jul 1998 19:15:15 -0400 From: Nathan Dorfman To: current@FreeBSD.ORG Subject: Display locked when X server dies Mail-Followup-To: current@FreeBSD.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This problem seems to exist from as long as a month or two ago to today's -current. If the X display is on the current virtual console, the X server dying results in the display locking up. The server does exit, but the display is frozen. C-A-BS doesn't work because the X server is no longer active. C-A-Fx and A-Fx don't work, nor does A-Fx. Killing the X server from a regular vty works fine. Try this: vty$ startx vty$ kill -9 [pid of X server] --- vty$ startx xterm$ kill -9 [pid of X server] The first example works fine, the X server exits as expected. In the second form, you'll see your X session freeze. Please post your results, as I'd like to know if this is a problem in -current or just something wrong here (did make world and built a fresh kernel with make clean; make; make install today. rebuilt XFree86 yesterday). It's XFree86-3.3.2 from the ports. -- ________________ ___________________________________________ / Nathan Dorfman \ / "My problems start when the smarter bears / nathan@rtfm.net \/ and the dumber visitors intersect." / finger for PGP key \ Steve Thompson, Yosemite wildlife biologist To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 12 17:22:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA10596 for freebsd-current-outgoing; Sun, 12 Jul 1998 17:22:59 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from home.dragondata.com (toasty@home.dragondata.com [204.137.237.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA10591 for ; Sun, 12 Jul 1998 17:22:57 -0700 (PDT) (envelope-from toasty@home.dragondata.com) Received: (from toasty@localhost) by home.dragondata.com (8.8.8/8.8.5) id TAA13983 for current@freebsd.org; Sun, 12 Jul 1998 19:22:53 -0500 (CDT) From: Kevin Day Message-Id: <199807130022.TAA13983@home.dragondata.com> Subject: Another -current crash To: current@FreeBSD.ORG Date: Sun, 12 Jul 1998 19:22:53 -0500 (CDT) X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG vm_page_free: pindex(0), busy(0), PG_BUSY(1), hold(0) panic: vm_page_free: freeing free page mp_lock = 01000001; cpuid = 1; lapic.id = 01000000 _Debugger _panic _vm_page_freechk_and_unqueue _vm_page_free _vm_object_collapse _vm_object_deallocate _vm_map_entry_delete _vm_map_delete _vm_map_remove _exit1 _sigexit _postsig _trap calltrap() --- trap 0xc, eip = 0x2008e015, esp = 0xefb22ff4, ebp = 0xefbfdd84 --- And again, it hangs when I try to do a core dump... Any idea what's causing this? Or is this a case of 'Something already freed the page, and at this point, it's too late to figure out what?' Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 12 17:38:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA12451 for freebsd-current-outgoing; Sun, 12 Jul 1998 17:38:05 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA12382 for ; Sun, 12 Jul 1998 17:37:58 -0700 (PDT) (envelope-from doconnor@cain.gsoft.com.au) Received: from cain (localhost [127.0.0.1]) by cain.gsoft.com.au (8.8.8/8.6.9) with ESMTP id KAA04389; Mon, 13 Jul 1998 10:07:21 +0930 (CST) Message-Id: <199807130037.KAA04389@cain.gsoft.com.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Nathan Dorfman cc: current@FreeBSD.ORG Subject: Re: Display locked when X server dies In-reply-to: Your message of "Sun, 12 Jul 1998 19:15:15 -0400." <19980712191515.A195@rtfm.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 13 Jul 1998 10:07:20 +0930 From: "Daniel O'Connor" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Killing the X server from a regular vty works fine. Try > this: > > vty$ startx > vty$ kill -9 [pid of X server] > --- > vty$ startx > xterm$ kill -9 [pid of X server] > > The first example works fine, the X server exits as expected. In the > second form, you'll see your X session freeze. Please post your > results, as I'd like to know if this is a problem in -current or Nope, thats perfectly normal behaviour.. If you send the X process a normal kill then it will be able to exit and take the video card out of gfx mode, if you muke it with -9 then the kernel will kill the process before it can do anything useful to the garphics card (a program can't catch a kill -9) The reason you can't fix it is because the kernel doesn't know how to take the video card out of graphics mode (thats what the drivers are for in X :) --------------------------------------------------------------------- |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-current" in the body of the message From owner-freebsd-current Sun Jul 12 17:49:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA13984 for freebsd-current-outgoing; Sun, 12 Jul 1998 17:49:56 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from limbo.rtfm.net (nathan@38.nyack.fcc.net [204.141.125.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA13965; Sun, 12 Jul 1998 17:49:53 -0700 (PDT) (envelope-from nathan@limbo.rtfm.net) Received: (from nathan@localhost) by limbo.rtfm.net (8.8.8/8.8.8) id UAA09290; Sun, 12 Jul 1998 20:48:47 -0400 (EDT) (envelope-from nathan) Message-ID: <19980712204846.A9285@rtfm.net> Date: Sun, 12 Jul 1998 20:48:46 -0400 From: Nathan Dorfman To: "Daniel O'Connor" , freebsd-current@FreeBSD.ORG Cc: current@FreeBSD.ORG Subject: Re: Display locked when X server dies Mail-Followup-To: Daniel O'Connor , freebsd-current@FreeBSD.org, current@FreeBSD.ORG References: <19980712191515.A195@rtfm.net> <199807130037.KAA04389@cain.gsoft.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199807130037.KAA04389@cain.gsoft.com.au>; from Daniel O'Connor on Mon, Jul 13, 1998 at 10:07:20AM +0930 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jul 13, 1998 at 10:07:20AM +0930, Daniel O'Connor wrote: > > > Killing the X server from a regular vty works fine. Try > > this: > > > > vty$ startx > > vty$ kill -9 [pid of X server] > > --- > > vty$ startx > > xterm$ kill -9 [pid of X server] > > > > The first example works fine, the X server exits as expected. In the > > second form, you'll see your X session freeze. Please post your > > results, as I'd like to know if this is a problem in -current or > Nope, thats perfectly normal behaviour.. > If you send the X process a normal kill then it will be able to exit and take > the video card out of gfx mode, if you muke it with -9 then the kernel will > kill the process before it can do anything useful to the garphics card (a > program can't catch a kill -9) > > The reason you can't fix it is because the kernel doesn't know how to take the > video card out of graphics mode (thats what the drivers are for in X :) > This makes sense. The reason that it is a "problem" is that XFree86 is doing this to itself, it seems at random. I could just be moving the mouse from one xterm to another, when *wham*. This has been happening since a long's ago -current, around the same time I stopped seeing the "recommend more swap space" messages on console. Any ideas? -- ________________ ___________________________________________ / Nathan Dorfman \ / "My problems start when the smarter bears / nathan@rtfm.net \/ and the dumber visitors intersect." / finger for PGP key \ Steve Thompson, Yosemite wildlife biologist To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 12 18:22:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA17127 for freebsd-current-outgoing; Sun, 12 Jul 1998 18:22:50 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA17118; Sun, 12 Jul 1998 18:22:46 -0700 (PDT) (envelope-from doconnor@cain.gsoft.com.au) Received: from cain (localhost [127.0.0.1]) by cain.gsoft.com.au (8.8.8/8.6.9) with ESMTP id KAA06241; Mon, 13 Jul 1998 10:52:29 +0930 (CST) Message-Id: <199807130122.KAA06241@cain.gsoft.com.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Nathan Dorfman cc: freebsd-current@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Display locked when X server dies In-reply-to: Your message of "Sun, 12 Jul 1998 20:48:46 -0400." <19980712204846.A9285@rtfm.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 13 Jul 1998 10:52:29 +0930 From: "Daniel O'Connor" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > This makes sense. The reason that it is a "problem" is that XFree86 > is doing this to itself, it seems at random. I could just be moving > the mouse from one xterm to another, when *wham*. This has been > happening since a long's ago -current, around the same time I stopped > seeing the "recommend more swap space" messages on console. Any ideas? Hmm.. well you could really actually be running out of swap and the system could be killing your X process.. Do you stay logged in for a long time? If so you may be encountering a memory leak of some description, which is making your system run out of RAM. --------------------------------------------------------------------- |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-current" in the body of the message From owner-freebsd-current Sun Jul 12 18:28:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA18152 for freebsd-current-outgoing; Sun, 12 Jul 1998 18:28:39 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA18147 for ; Sun, 12 Jul 1998 18:28:33 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id LAA04438; Mon, 13 Jul 1998 11:28:28 +1000 Date: Mon, 13 Jul 1998 11:28:28 +1000 From: Bruce Evans Message-Id: <199807130128.LAA04438@godzilla.zeta.org.au> To: freebsd-current@FreeBSD.ORG, roberto@keltia.freenix.fr Subject: Re: Weirdness in CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Am I the one only to see this during "make world" ? > >- why the "cd .../games; cp ..." ?? >- why trying to build build-tools inside "/usr/src/bin/sh" ? RCS file: /home/ncvs/src/Makefile,v Working file: Makefile head: 1.205 ... ---------------------------- revision 1.204 date: 1998/07/07 05:37:34; author: bde; state: Exp; lines: +19 -1 Build internal tools in build-tools so that they have some chance of working when the target system is not binary compatible. Use various hacks to work around minor problems in the source and binary tree layouts: - caesar and strfile are built normally (the source layout is good), then installed by copying them to ${WORLDTMP}/usr/bin (they are installed in ${WORLDTMP}/usr/games, but I don't want to put that in $PATH). - colldef and mklocale are built and installed normally. Messy and incomplete relative path searches for them and caesar and strfile can now go away. - internal tools that aren't installed are now built and left lying around for the `make all' pass to use. If the target system is not binary compatible, it is critical that these tools don't get rebuilt. Cleaning of the obj tree before building the internal tools should ensure this. - most internal tools are built using internal build-tools targets, but tn3270 is simpler for a change - it has all the tools in a separate tree, so they can be built using `make all'. ---------------------------- ... RCS file: /home/ncvs/src/bin/sh/Makefile,v Working file: Makefile head: 1.28 ... ---------------------------- revision 1.28 date: 1998/07/07 01:06:58; author: bde; state: Exp; lines: +3 -4 Added a `build-tools' target for internal tools. Removed explicit dependencies of foo.o on foo.c. These were mainly placeholders for comments about missing dependencies of tools objects on headers. This problem needs to be handled more generally. ---------------------------- ... Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 12 19:05:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA20439 for freebsd-current-outgoing; Sun, 12 Jul 1998 19:05:12 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com (rah.star-gate.com [209.133.7.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA20433 for ; Sun, 12 Jul 1998 19:05:11 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id TAA02513 for ; Sun, 12 Jul 1998 19:05:00 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199807130205.TAA02513@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-current@FreeBSD.ORG Subject: Netscape and -current. Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 12 Jul 1998 19:05:00 -0700 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A couple of times over the last few days I encountered problems with X apps and pulldown menus such that the application does not seem to respond to the menus. Never seen such behavior. This started happening this week after I cvsup the system. Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 12 21:19:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA05861 for freebsd-current-outgoing; Sun, 12 Jul 1998 21:19:59 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from localhost.ziplink.net (mi@kot.ne.mediaone.net [24.128.29.55]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA05856 for ; Sun, 12 Jul 1998 21:19:57 -0700 (PDT) (envelope-from mi@rtfm.ziplink.net) Received: from rtfm.ziplink.net (mi@rtfm [199.232.255.52]) by localhost.ziplink.net (8.8.8/8.8.7) with ESMTP id EAA04117 for ; Mon, 13 Jul 1998 04:19:52 GMT (envelope-from mi@rtfm.ziplink.net) Received: (from mi@localhost) by rtfm.ziplink.net (8.8.8/8.8.5) id AAA08502 for current@freebsd.org; Mon, 13 Jul 1998 00:19:51 -0400 (EDT) From: Mikhail Teterin Message-Id: <199807130419.AAA08502@rtfm.ziplink.net> Subject: soft updates, ccd, old drives To: current@FreeBSD.ORG Date: Mon, 13 Jul 1998 00:19:50 -0400 (EDT) X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli" type 0 fixed SCSI 2 sd3: type 0 fixed SCSI 2 sd4: type 0 fixed SCSI 2 sd6: type 0 fixed SCSI 2 they are on a dual bus Adaptec : ahc0: at 0x9c00-0x9cff irq 10 ahc0: on eisa0 slot 9 ahc0: Using Level Sensitive Interrupts ahc0: aic7770 <= Rev C, Twin Channel, A SCSI Id=7, B SCSI Id=7, 4 SCBs ahc0: Resetting Channel B ahc0: Resetting Channel A ahc0: Downloading Sequencer Program...ahc0: 376 instructions downloaded two on one bus and two on the other. First weirdness is that kernel said "ffs_mountfs: superblock updated" every time I mounted my /ccd . It does not say that if I disable soft updates, so I report it. Now, `cd /ccd/ports; make clean' was working just fine (that's my place for the ports-tree). But extracting anything was hanging one disk or the other: with kernel messages about sd[46] "timeout in dataout" or similar. This would not respond to ctrl-alt-del, and, though the shells were working in other virtual consoles, they could not execute anything, including "reboot". So -- cold reset to the horrible fsck screenfulls. Hardware, I thought -- the poor old disks were never pushed that hard with the simple async mounts. So I grabbed the EISA floppy and set the maximum transfer rate from 8Mbps to the minimum 3.7Mbps. Same hangs, although this time there were no "timeout" messages on the console. I gave up, and disabled soft updates on /ccd (why is the tunefs option `-n'? did anyone notice, that the character 'n' is not even used in "soft updates"!). Since then, I successfully extracted XFree86 and gcc28 ports, and am currently building the gcc28 without problems. My conclusion is, that something in Soft Updates and CCD combination is wrong, which was hanging AND causing the disks to be pushed hard. After I took the maximum transfer rate down, the disks were not pushed as hard, so -- no timeouts, but the hangs were still here. This is a debug kernel and I have a corresponding kernel.debug. If someone wants me, I can try different things here to try to resolve this. Yours, -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 12 22:19:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA12309 for freebsd-current-outgoing; Sun, 12 Jul 1998 22:19:13 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mickey00.mickey.ai.kyutech.ac.jp (mickey.ai.kyutech.ac.jp [131.206.1.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA12300 for ; Sun, 12 Jul 1998 22:19:11 -0700 (PDT) (envelope-from ohashi@mickey.ai.kyutech.ac.jp) Received: from ateken2.mickey.ai.kyutech.ac.jp (ateken2.mickey.ai.kyutech.ac.jp [131.206.21.141]) by mickey00.mickey.ai.kyutech.ac.jp (8.8.8/3.6W-mickey) with ESMTP id OAA11203; Mon, 13 Jul 1998 14:18:46 +0900 (JST) Received: (from ohashi@localhost) by ateken2.mickey.ai.kyutech.ac.jp (8.8.8/3.5Wpl5) id OAA00399; Mon, 13 Jul 1998 14:18:47 +0900 (JST) Date: Mon, 13 Jul 1998 14:18:47 +0900 (JST) Message-Id: <199807130518.OAA00399@ateken2.mickey.ai.kyutech.ac.jp> To: c5666305@comp.polyu.edu.hk Cc: freebsd-current@FreeBSD.ORG Subject: Re: non 512 bytes device support (MO 640M) In-Reply-To: Your message of "Sat, 11 Jul 1998 19:11:26 JST". <199807111011.SAA14624@cssolar85.COMP.HKP.HK> From: ohashi@mickey.ai.kyutech.ac.jp (Takeshi Ohashi) X-Mailer: mnews [version 1.21] 1997-12/23(Tue) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, c5666305>>I would like to know if the MO 640M support by FreeBSD 2.2.x or 3.0-snap c5666305>>or not. Thanks. Shunsuke Akiyama has released od-driver for 2.2.x. ftp://jaz.jp.freebsd.org/pub/FreeBSD-jp/OD/ MD5 CHECKSUM: MD5 (od-driver-2.2.1R.tar.gz) = 707642ad0e40297d3c8c44d2c4973732 MD5 (od-driver-2.2.2R.tar.gz) = 2ee07568080bca404840b8f69aa8c696 MD5 (od-driver-2.2.6R.tar.gz) = 6161de10a87d2ecbc89446e00f055caa -- Takeshi OHASHI, Dept. of A.I., Kyushu Inst. of Tech., Iizuka 820, JAPAN ohashi@mickey.ai.kyutech.ac.jp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 12 23:34:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA18616 for freebsd-current-outgoing; Sun, 12 Jul 1998 23:34:14 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from titus.stade.co.uk (stade.demon.co.uk [158.152.29.164]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA18610 for ; Sun, 12 Jul 1998 23:34:11 -0700 (PDT) (envelope-from aw1@stade.co.uk) Received: (from aw1@localhost) by titus.stade.co.uk (8.8.8/8.8.8) id HAA11216; Mon, 13 Jul 1998 07:16:10 +0100 (BST) (envelope-from aw1) Message-ID: <19980713071609.A15469@stade.co.uk> Date: Mon, 13 Jul 1998 07:16:09 +0100 From: Adrian Wontroba To: current@FreeBSD.ORG Subject: Re: soft updates, ccd, old drives Reply-To: aw1@stade.co.uk Mail-Followup-To: current@FreeBSD.ORG References: <199807130419.AAA08502@rtfm.ziplink.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199807130419.AAA08502@rtfm.ziplink.net>; from Mikhail Teterin on Mon, Jul 13, 1998 at 12:19:50AM -0400 Organization: Stade Computers Ltd, UK X-Phone: +(44) 121 681 6677 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jul 13, 1998 at 12:19:50AM -0400, Mikhail Teterin wrote: > dataout" or similar. This would not respond to ctrl-alt-del, and, > though the shells were working in other virtual consoles, they > could not execute anything, including "reboot". So -- cold reset > to the horrible fsck screenfulls. I've been getting something similar. The machine has a 2949AU adapter, with a very recent current. With softupdates enabled everything initially seems fine, but doing anything slightly heavy causes similar symptoms (forking anything takes an inordinately long time), with much pounding on one of the discs but little user program activity. It seems horribly repeatable. I did have systat/vmstat running for one of these near freezes, and noticed that freevnodes had a very low value (<10). I suspect I need to tune some sysctl variables, but don't have a clue as to what. Possibly unconnected, but very worrying - part of my ppp log appeared in /etc/motd. I've not noticed any other signs of filesystem corruption. -- Adrian Wontroba, Stade Computers Limited. phone: (+44) 121 681 6677 Mail info@accu.org for information about the Association of C and C++ Users or see To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 13 02:21:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA04583 for freebsd-current-outgoing; Mon, 13 Jul 1998 02:21:40 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA04556 for ; Mon, 13 Jul 1998 02:21:37 -0700 (PDT) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.0/frmug-2.3/nospam) with UUCP id LAA24533 for freebsd-current@FreeBSD.ORG; Mon, 13 Jul 1998 11:21:31 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: (from roberto@localhost) by keltia.freenix.fr (8.9.0.Beta4/keltia-2.14/nospam) id KAA13169 for freebsd-current@FreeBSD.ORG; Mon, 13 Jul 1998 10:48:51 +0200 (CEST) (envelope-from roberto) Message-ID: <19980713104850.A2280@keltia.freenix.fr> Date: Mon, 13 Jul 1998 10:48:50 +0200 From: Ollivier Robert To: freebsd-current@FreeBSD.ORG Subject: Re: Weirdness in CURRENT Mail-Followup-To: freebsd-current@FreeBSD.ORG References: <199807130128.LAA04438@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93i In-Reply-To: <199807130128.LAA04438@godzilla.zeta.org.au>; from Bruce Evans on Mon, Jul 13, 1998 at 11:28:28AM +1000 X-Operating-System: FreeBSD 3.0-CURRENT ctm#4462 AMD-K6 MMX @ 225 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Bruce Evans: > >- why trying to build build-tools inside "/usr/src/bin/sh" ? A ``Tag'' file had crept into my bin/sh/CVS directory, preventing CVS from updating the Makefile :-( Sorry. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #61: Sun Jul 12 14:38:23 CEST 1998 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 13 03:51:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA13147 for freebsd-current-outgoing; Mon, 13 Jul 1998 03:51:30 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from news1.gtn.com (news1.gtn.com [192.109.159.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA13132 for ; Mon, 13 Jul 1998 03:51:19 -0700 (PDT) (envelope-from andreas@klemm.gtn.com) Received: (from uucp@localhost) by news1.gtn.com (8.8.6/8.8.6) with UUCP id MAA09779 for current@FreeBSD.ORG; Mon, 13 Jul 1998 12:45:14 +0200 (MET DST) Received: (from andreas@localhost) by klemm.gtn.com (8.8.8/8.8.8) id MAA17032; Mon, 13 Jul 1998 12:33:21 +0200 (CEST) (envelope-from andreas) Message-ID: <19980713123321.A16305@klemm.gtn.com> Date: Mon, 13 Jul 1998 12:33:21 +0200 From: Andreas Klemm To: current@FreeBSD.ORG Subject: Re: soft updates, ccd, old drives References: <199807130419.AAA08502@rtfm.ziplink.net> <19980713071609.A15469@stade.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <19980713071609.A15469@stade.co.uk>; from Adrian Wontroba on Mon, Jul 13, 1998 at 07:16:09AM +0100 X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 3.0-CURRENT SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jul 13, 1998 at 07:16:09AM +0100, Adrian Wontroba wrote: > On Mon, Jul 13, 1998 at 12:19:50AM -0400, Mikhail Teterin wrote: I'm using: - ccd - softupdates - i4b - SMP I'm using 4 ccd's and partly have a lot of traffic there when building a release or world or such ... Never had noticed any ccd or SCSI failures. No problems so far: Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/sd0s2a 31743 22806 6398 78% / devfs 16 16 0 100% dummy_mount /dev/sd0s2f 1029135 429853 516952 45% /usr /dev/sd0s2e 127023 33955 82907 29% /var /dev/ccd0c 198327 160098 22363 88% /obj /dev/ccd1c 198327 35848 146613 20% /news /dev/ccd2c 99055 61581 29550 68% /proxy /dev/ccd3c 3400078 2714608 413464 87% /home procfs 4 4 0 100% /proc /dev/sd0s1 818960 768592 50368 94% /dos mfs:33 30991 18 28494 0% /tmp amd:182 0 0 0 100% /host Copyright (c) 1992-1998 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-CURRENT #0: Fri Jul 10 19:01:41 CEST 1998 root@titan.klemm.gtn.com:/home/src/sys/compile/ISDNSMP Timecounter "i8254" frequency 1193182 Hz cost 3558 ns CPU: Pentium Pro (686-class CPU) Origin = "GenuineIntel" Id = 0x619 Stepping=9 Features=0xfbff real memory = 83886080 (81920K bytes) avail memory = 78114816 (76284K bytes) 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 DEVFS: ready for devices Probing for devices on PCI bus 0: chip0: rev 0x02 on pci0.0.0 chip1: rev 0x01 on pci0.7.0 vx0: <3COM 3C900 Etherlink XL PCI> rev 0x00 int a irq 19 on pci0.11.0 utp/aui/bnc[*utp*] address 00:60:97:aa:3a:db vga0: rev 0x01 int a irq 18 on pci0.12.0 ahc0: rev 0x00 int a irq 17 on pci0.13.0 ahc0: aic7880 Single Channel, SCSI Id=7, 16/255 SCBs ahc0: waiting for scsi devices to settle scbus0 at ahc0 bus 0 ahc0: target 0 Tagged Queuing Device sd0 at scbus0 target 0 lun 0 sd0: type 0 fixed SCSI 2 sd0: Direct-Access 2063MB (4226725 512 byte sectors) sd0: with 6703 cyls, 5 heads, and an average 126 sectors/track st0 at scbus0 target 4 lun 0 st0: type 1 removable SCSI 2 st0: Sequential-Access density code 0x0, 512-byte blocks, write-enabled cd0 at scbus0 target 6 lun 0 cd0: type 5 removable SCSI 2 cd0: CD-ROM can't get the size ahc1: rev 0x03 int a irq 16 on pci0.14.0 ahc1: aic7870 Single Channel, SCSI Id=7, 16/255 SCBs ahc1: waiting for scsi devices to settle scbus1 at ahc1 bus 0 ahc1: target 1 Tagged Queuing Device sd1 at scbus1 target 1 lun 0 sd1: type 0 fixed SCSI 2 sd1: Direct-Access 2063MB (4226725 512 byte sectors) sd1: with 6703 cyls, 5 heads, and an average 126 sectors/track ahc1: target 2 Tagged Queuing Device sd2 at scbus1 target 2 lun 0 sd2: type 0 fixed SCSI 2 sd2: Direct-Access 2063MB (4226725 512 byte sectors) sd2: with 6703 cyls, 5 heads, and an average 126 sectors/track Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <4 virtual consoles, flags=0x0> ed0 at 0x280-0x29f irq 10 maddr 0xd0000 msize 16384 on isa ed0: address 00:00:c0:5a:98:2a, type WD8013EPC (16 bit) sio0 at 0x3f8-0x3ff irq 4 flags 0x20 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface psm0 at 0x60-0x64 irq 12 on motherboard psm0: model Generic PS/2 mouse, device ID 0 pcm0 at 0x220 irq 5 drq 1 flags 0x15 on isa fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in isic0 at 0xd80 irq 9 flags 0x4 on isa isic0: Teles S0/16.3 isic0: ISAC 2085 Version A1/A2 or 2086/2186 Version 1.1 (IOM-2) (Addr=0x960) isic0: HSCX 82525 or 21525 Version 2.1 (AddrA=0x160, AddrB=0x560) npx0 flags 0x1 on motherboard npx0: INT 16 interface DEVFS: ready to run APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via pin 2 ccd0-3: Concatenated disk drivers i4b: ISDN call control device attached i4bisppp: 4 ISDN SyncPPP device(s) attached i4bctl: ISDN system control port attached i4bipr: 4 IP over raw HDLC ISDN device(s) attached i4btel: 2 ISDN telephony interface device(s) attached i4brbch: 4 raw B channel access device(s) attached i4btrc: 4 ISDN trace device(s) attached IP packet filtering initialized, divert enabled, rule-based forwarding disabled, logging limited to 500 packets/entry IP Filter: initialized. Default = pass all, Logging = enabled changing root device to sd0s2a SMP: AP CPU #1 Launched! ffs_mountfs: superblock updated ffs_mountfs: superblock updated ffs_mountfs: superblock updated ffs_mountfs: superblock updated ffs_mountfs: superblock updated vx0: selected utp. (link2) isppp0: phase establish i4b-L2-i4b_tei_assign: tx TEI ID_Request i4b-L2-i4b_T202_timeout: unit 0, N202 = 3 i4b-L2-i4b_tei_assign: tx TEI ID_Request i4b-L2-i4b_tei_rx_frame: TEI ID Assign - TEI = 99 isppp0: phase authenticate isppp0: phase network # # ISDNSMP kernel # machine "i386" cpu "I686_CPU" ident ISDNSMP # rse's recommendations for heavily users apache servers maxusers 256 options SOMAXCONN="256" options "NMBCLUSTER=4096" #options "CHILD_MAX=512" #options "OPEN_MAX=512" # Options for the VM subsystem #options PQ_NOOPT # No coloring #options PQ_LARGECACHE # color for 512k/16k cache options PQ_HUGECACHE # color for 1024k/16k cache options SMP # Symmetric MultiProcessor Kernel options APIC_IO # Symmetric (APIC) I/O options INCLUDE_CONFIG_FILE # Include this file in kernel #options USERCONFIG #boot -c editor #options VISUAL_USERCONFIG #visual boot -c editor options DDB options KTRACE #kernel tracing options SHOW_BUSYBUFS # busy buffers on shutdown ? options INET #InterNETworking options IPFIREWALL #firewall options IPFIREWALL_VERBOSE #print information about dropped packets options "IPFIREWALL_VERBOSE_LIMIT=500" #limit verbosity options IPDIVERT #divert sockets options IPFILTER #kernel ipfilter support options IPFILTER_LOG #ipfilter logging options "P1003_1B" options "_KPOSIX_PRIORITY_SCHEDULING" options "_KPOSIX_VERSION=199309L" options FFS #Berkeley Fast Filesystem options NFS #Network File System options MFS #Memory File System options UNION #Union filesystem options "CD9660" #ISO 9660 filesystem options MSDOSFS #MS DOS File System options PROCFS #Process filesystem options NSWAPDEV=3 #Allow this many swap-devices. options QUOTA #enable disk quotas options SOFTUPDATES #Kirk McKusick's code # DEVFS and SLICE are experimental but work. # SLICE disables too much old code so enabling it in LINT would be bad options DEVFS #devices filesystem #options SLICE #devfs based disk handling # misc options options "COMPAT_43" #Compatible with BSD 4.3 [KEEP THIS!] options UCONSOLE #Allow users to grab the console options SYSVSHM,SYSVSEM,SYSVMSG #shared memory (X11) options COMPAT_LINUX # Linux Binary compatibility #options USER_LDT # for Wine options "MD5" #options "VM86" config kernel root on sd1 # ISA and PCI BUS support controller isa0 controller pci0 # Floppy Disk Controller controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr disk fd0 at fdc0 drive 0 # SCSI Devices # AHA 2940U controller ahc0 controller scbus0 at ahc0 disk sd0 at scbus0 target 0 unit 0 disk sd3 at scbus0 target 1 unit 0 tape st0 at scbus0 target 4 device worm0 at scbus0 target 5 device cd0 at scbus0 target 6 # AHA 2940 controller ahc1 controller scbus1 at ahc1 disk sd1 at scbus1 target 1 unit 0 disk sd2 at scbus1 target 2 unit 0 options SCSI_DELAY=4 # Be pessimistic about Joe SCSI device options "CD9660_ROOTDELAY=8" options AHC_TAGENABLE # tagged command queueing options AHC_ALLOW_MEMIO options AHC_SCBPAGING_ENABLE options SCSI_REPORT_GEOMETRY # SCO compatible system console device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr options MAXCONS=4 # number of virtual consoles options SC_HISTORY_SIZE=200 # number of history buffer lines # The pcvt console driver (vt220 compatible). #device vt0 at isa? port "IO_KBD" tty irq 1 vector pcrint #options XSERVER # support for running an X server. #options FAT_CURSOR # start with block cursor # floating point unit device npx0 at isa? port "IO_NPX" flags 0x1 irq 13 vector npxintr # serial devices on mainboard # `flags' for serial drivers that support consoles (only for sio now): # 0x10 enable console support for this unit. The other console flags # are ignored unless this is set. Enabling console support does # not make the unit the preferred console - boot with -h or set # the 0x20 flag for that. Currently, at most one unit can have # console support; the first one (in config file order) with # this flag set is preferred. Setting this flag for sio0 gives # the old behaviour. # 0x20 force this unit to be the console (unless there is another # higher priority console). This replaces the COMCONSOLE option. # 0x40 reserve this unit for low level console operations. Do not # device sio0 at isa? port "IO_COM1" tty irq 4 flags 0x20 vector siointr device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr options BREAK_TO_DEBUGGER #a BREAK on a comconsole goes to DDB, #if available. options CONSPEED=38400 #default speed for serial console #(default 9600) # parallel device on mainboard device lpt0 at isa? port? tty irq 7 vector lptintr # PS/2 mouse on mainboard device psm0 at isa? port "IO_KBD" conflicts tty irq 12 vector psmintr options "PSM_ACCEL=1" # PS/2 mouse acceleration # Joystick #device joy0 at isa? port "IO_GAME" # Network 3COM PCI device vx0 device ed0 at isa? port 0x280 net irq 10 iomem 0xd0000 vector edintr # Soundblaster 16 # SoundBlaster DSP driver - for SB, SB Pro, SB16, PAS(emulating SB) # SoundBlaster 16 DSP driver - for SB16 - requires sb0 device # SoundBlaster 16 MIDI - for SB16 - requires sb0 device # Yamaha OPL-2/OPL-3 FM - for SB, SB Pro, SB16, PAS # controller snd0 # device sb0 at isa? port 0x220 irq 5 conflicts drq 1 vector sbintr # device sbxvi0 at isa? port? irq? drq 5 conflicts # device sbmidi0 at isa? port 0x330 irq? conflicts # device opl0 at isa? port 0x388 conflicts # pcm: PCM audio through various sound cards. # New Sound code device pcm0 at isa? port ? tty irq 5 drq 1 flags 0x15 vector pcmintr # Pseudo devices pseudo-device loop #Network loopback device pseudo-device ether #Generic Ethernet pseudo-device vn 1 #Vnode driver (turns a file into a dev.) pseudo-device snp 3 #Snoop device - to look at pty/vty/etc.. pseudo-device disc #Discard device pseudo-device bpfilter 4 #Berkeley packet filter pseudo-device pty 16 #Pseudo ttys - can go as high as 256 pseudo-device gzip # Exec gzipped a.out's pseudo-device ccd 4 #Concatenated disk driver pseudo-device tun 1 #Tunnel driver (user process ppp(8)) pseudo-device ppp 1 #Point-to-point protocol options PPP_BSDCOMP #PPP BSD-compress support options PPP_DEFLATE #PPP zlib/deflate/gzip support options PPP_FILTER #enable bpf filtering (needs bpfilter) # Size of the kernel message buffer. Should be N * pagesize. options "MSGBUF_SIZE=40960" ## BISDN #options IPI_VJ # Van Jacobsen header compression support ##options "IPI_DIPA=3" # send ip accounting packets every 3 seconds #options TELES_HAS_MEMCPYB # bisdn 0.97 # ## Teles S0/16.3 ################################################### IRQ 9 ## #controller tel0 at isa? port 0xd80 net irq 9 vector telintr #pseudo-device disdn #pseudo-device isdn #pseudo-device ipi 4 #pseudo-device ispy 4 #pseudo-device itel 1 options "I4B_SMP_WORKAROUND" # i4b passive ISDN cards support (isic - I4b Siemens Isdn Chipset driver) # Teles S0/16.3 options "TEL_S0_16_3" device isic0 at isa? port 0xd80 net irq 9 flags 0x04 vector isicintr # i4b passive cards D channel handling # Q.921 pseudo-device "i4bq921" # Q.931 pseudo-device "i4bq931" # common passive and active layer 4 # layer 4 pseudo-device "i4b" # userland driver to do ISDN tracing (for passive cards oly) pseudo-device "i4btrc" 4 # userland driver to control the whole thing pseudo-device "i4bctl" # userland driver for access to raw B channel pseudo-device "i4brbch" 4 # userland driver for telephony pseudo-device "i4btel" 2 # network driver for IP over raw HDLC ISDN pseudo-device "i4bipr" 4 # enable VJ header compression detection for ipr i/f options IPR_VJ # network driver for sync PPP over ISDN pseudo-device "i4bisppp" 4 pseudo-device sppp 4 -- Andreas Klemm http://www.FreeBSD.ORG/~andreas What gives you 90% more speed, for example, in kernel compilation ? http://www.FreeBSD.ORG/~fsmp/SMP/akgraph-a/graph1.html "NT = Not Today" (Maggie Biggs) ``powered by FreeBSD SMP'' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 13 03:53:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA13290 for freebsd-current-outgoing; Mon, 13 Jul 1998 03:53:01 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from news1.gtn.com (news1.gtn.com [192.109.159.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA13285 for ; Mon, 13 Jul 1998 03:52:53 -0700 (PDT) (envelope-from andreas@klemm.gtn.com) Received: (from uucp@localhost) by news1.gtn.com (8.8.6/8.8.6) with UUCP id MAA09780; Mon, 13 Jul 1998 12:45:18 +0200 (MET DST) Received: (from andreas@localhost) by klemm.gtn.com (8.8.8/8.8.8) id MAA17044; Mon, 13 Jul 1998 12:35:34 +0200 (CEST) (envelope-from andreas) Message-ID: <19980713123534.B16305@klemm.gtn.com> Date: Mon, 13 Jul 1998 12:35:34 +0200 From: Andreas Klemm To: Amancio Hasty , freebsd-current@FreeBSD.ORG Subject: Re: Netscape and -current. References: <199807130205.TAA02513@rah.star-gate.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199807130205.TAA02513@rah.star-gate.com>; from Amancio Hasty on Sun, Jul 12, 1998 at 07:05:00PM -0700 X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 3.0-CURRENT SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jul 12, 1998 at 07:05:00PM -0700, Amancio Hasty wrote: > > > A couple of times over the last few days I encountered problems with X apps > and pulldown menus such that the application does not seem to respond > to the menus. Never seen such behavior. This started happening this > week after I cvsup the system. correct, same for me when using Netscape for some time. The mousecursor gets unuseable, the mouse produces a lot of events ... the more error messages you click away the more you produce ;-) I installed updated -current _and_ X11R6 to newest release. So I wasn't sure, whom to blame. -- Andreas Klemm http://www.FreeBSD.ORG/~andreas What gives you 90% more speed, for example, in kernel compilation ? http://www.FreeBSD.ORG/~fsmp/SMP/akgraph-a/graph1.html "NT = Not Today" (Maggie Biggs) ``powered by FreeBSD SMP'' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 13 04:18:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA18173 for freebsd-current-outgoing; Mon, 13 Jul 1998 04:18:34 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA18162 for ; Mon, 13 Jul 1998 04:18:31 -0700 (PDT) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id HAA16504; Mon, 13 Jul 1998 07:17:55 -0400 (EDT) (envelope-from luoqi) Date: Mon, 13 Jul 1998 07:17:55 -0400 (EDT) From: Luoqi Chen Message-Id: <199807131117.HAA16504@lor.watermarkgroup.com> To: aw1@stade.co.uk, current@FreeBSD.ORG Subject: Re: soft updates, ccd, old drives Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Mon, Jul 13, 1998 at 12:19:50AM -0400, Mikhail Teterin wrote: > > dataout" or similar. This would not respond to ctrl-alt-del, and, > > though the shells were working in other virtual consoles, they > > could not execute anything, including "reboot". So -- cold reset > > to the horrible fsck screenfulls. > > I've been getting something similar. > > The machine has a 2949AU adapter, with a very recent current. With > softupdates enabled everything initially seems fine, but doing anything > slightly heavy causes similar symptoms (forking anything takes an > inordinately long time), with much pounding on one of the discs but > little user program activity. It seems horribly repeatable. I did have > systat/vmstat running for one of these near freezes, and noticed that > freevnodes had a very low value (<10). I suspect this has something to do with the fact that ccd allocates component buffer headers from the main memory pool. Under low memory condition, this allocation would cause paging, if the swap is also on ccd, more component buffer headers are required and would cause more paging, this process multiplies and eventually depletes all memory available, the system slows down to near freeze. Very low freevnodes count is an indication of this memory depletion, so is the slow fork. Try creating a private pool for these component buffer headers, the size of the pool should depend on how many transfers the disks can handle at one time and should be quite small. Or alternatively, set an upper limit on how many buf headers a ccd device could allocate from the main memory pool. This is just a theory. I don't have ccd myself and therefore no way to test it. -lq > > I suspect I need to tune some sysctl variables, but don't have a clue as > to what. > > Possibly unconnected, but very worrying - part of my ppp log appeared in > /etc/motd. I've not noticed any other signs of filesystem corruption. > > -- > Adrian Wontroba, Stade Computers Limited. phone: (+44) 121 681 6677 > Mail info@accu.org for information about the Association of C and C++ Users > or see > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 13 06:26:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA28660 for freebsd-current-outgoing; Mon, 13 Jul 1998 06:26:19 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA28502 for ; Mon, 13 Jul 1998 06:25:57 -0700 (PDT) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.0/frmug-2.3/nospam) with UUCP id PAA04772 for current@FreeBSD.ORG; Mon, 13 Jul 1998 15:25:37 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: (from roberto@localhost) by keltia.freenix.fr (8.9.0.Beta4/keltia-2.14/nospam) id LAA06097 for current@FreeBSD.ORG; Mon, 13 Jul 1998 11:35:41 +0200 (CEST) (envelope-from roberto) Message-ID: <19980713113540.A4498@keltia.freenix.fr> Date: Mon, 13 Jul 1998 11:35:40 +0200 From: Ollivier Robert To: current@FreeBSD.ORG Subject: Re: soft updates, ccd, old drives Mail-Followup-To: current@FreeBSD.ORG References: <199807130419.AAA08502@rtfm.ziplink.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93i In-Reply-To: <199807130419.AAA08502@rtfm.ziplink.net>; from Mikhail Teterin on Mon, Jul 13, 1998 at 12:19:50AM -0400 X-Operating-System: FreeBSD 3.0-CURRENT ctm#4462 AMD-K6 MMX @ 225 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Mikhail Teterin: > First weirdness is that kernel said "ffs_mountfs: superblock updated" > every time I mounted my /ccd . It does not say that if I disable > soft updates, so I report it. That's expected. It will probably go away in the future but for now, each time you mount a FS with softupdates, you'll get the message. Ignore it. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #61: Sun Jul 12 14:38:23 CEST 1998 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 13 08:48:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA17597 for freebsd-current-outgoing; Mon, 13 Jul 1998 08:48:29 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA17588 for ; Mon, 13 Jul 1998 08:48:27 -0700 (PDT) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id LAA18092; Mon, 13 Jul 1998 11:47:08 -0400 (EDT) (envelope-from luoqi) Date: Mon, 13 Jul 1998 11:47:08 -0400 (EDT) From: Luoqi Chen Message-Id: <199807131547.LAA18092@lor.watermarkgroup.com> To: andreas@klemm.gtn.com, current@FreeBSD.ORG Subject: Re: soft updates, ccd, old drives Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm using: > - ccd > - softupdates > - i4b > - SMP > > I'm using 4 ccd's and partly have a lot of traffic there > when building a release or world or such ... > > Never had noticed any ccd or SCSI failures. > > No problems so far: > Filesystem 1K-blocks Used Avail Capacity Mounted on > /dev/sd0s2a 31743 22806 6398 78% / > devfs 16 16 0 100% dummy_mount > /dev/sd0s2f 1029135 429853 516952 45% /usr > /dev/sd0s2e 127023 33955 82907 29% /var > /dev/ccd0c 198327 160098 22363 88% /obj > /dev/ccd1c 198327 35848 146613 20% /news > /dev/ccd2c 99055 61581 29550 68% /proxy > /dev/ccd3c 3400078 2714608 413464 87% /home > procfs 4 4 0 100% /proc > /dev/sd0s1 818960 768592 50368 94% /dos > mfs:33 30991 18 28494 0% /tmp > amd:182 0 0 0 100% /host > I bet you have your swap on sd0s2b, am I right? -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 13 09:07:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA19495 for freebsd-current-outgoing; Mon, 13 Jul 1998 09:07:40 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com (rah.star-gate.com [209.133.7.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA19488 for ; Mon, 13 Jul 1998 09:07:37 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id JAA01896; Mon, 13 Jul 1998 09:07:27 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199807131607.JAA01896@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Andreas Klemm cc: freebsd-current@FreeBSD.ORG Subject: Re: Netscape and -current. In-reply-to: Your message of "Mon, 13 Jul 1998 12:35:34 +0200." <19980713123534.B16305@klemm.gtn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 13 Jul 1998 09:07:27 -0700 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I cvsup my system about a month ago or so and the bug was not there however I decided to upgrade rah after Julian's call for softupdate's testers. Tnks, Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 13 09:24:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA21343 for freebsd-current-outgoing; Mon, 13 Jul 1998 09:24:42 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from news1.gtn.com (news1.gtn.com [192.109.159.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA21319 for ; Mon, 13 Jul 1998 09:24:09 -0700 (PDT) (envelope-from andreas@klemm.gtn.com) Received: (from uucp@localhost) by news1.gtn.com (8.8.6/8.8.6) with UUCP id SAA27597; Mon, 13 Jul 1998 18:15:16 +0200 (MET DST) Received: (from andreas@localhost) by klemm.gtn.com (8.8.8/8.8.8) id SAA26982; Mon, 13 Jul 1998 18:01:58 +0200 (CEST) (envelope-from andreas) Message-ID: <19980713180158.A26972@klemm.gtn.com> Date: Mon, 13 Jul 1998 18:01:58 +0200 From: Andreas Klemm To: Luoqi Chen , current@FreeBSD.ORG Subject: Re: soft updates, ccd, old drives References: <199807131547.LAA18092@lor.watermarkgroup.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199807131547.LAA18092@lor.watermarkgroup.com>; from Luoqi Chen on Mon, Jul 13, 1998 at 11:47:08AM -0400 X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 3.0-CURRENT SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jul 13, 1998 at 11:47:08AM -0400, Luoqi Chen wrote: > > > I bet you have your swap on sd0s2b, am I right? Not only on that drive ;-) Device 1K-blocks Used Avail Capacity Type /dev/sd0s2b 67584 21488 45968 32% Interleaved /dev/sd1s1b 102400 21360 80912 21% Interleaved /dev/sd2s1b 102400 21372 80900 21% Interleaved Total 272000 64220 207780 24% -- Andreas Klemm http://www.FreeBSD.ORG/~andreas What gives you 90% more speed, for example, in kernel compilation ? http://www.FreeBSD.ORG/~fsmp/SMP/akgraph-a/graph1.html "NT = Not Today" (Maggie Biggs) ``powered by FreeBSD SMP'' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 13 10:12:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA27974 for freebsd-current-outgoing; Mon, 13 Jul 1998 10:12:36 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from proxy3.ba.best.com (root@proxy3.ba.best.com [206.184.139.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA27969 for ; Mon, 13 Jul 1998 10:12:34 -0700 (PDT) (envelope-from Kurt@Boolean.Net) Received: from Boolean.Net (smx-ca16-54.ix.netcom.com [207.93.148.182]) by proxy3.ba.best.com (8.9.0/8.9.0/best.out) with ESMTP id KAA28809 for ; Mon, 13 Jul 1998 10:10:27 -0700 (PDT) Message-ID: <35AA3D71.84F37A20@Boolean.Net> Date: Mon, 13 Jul 1998 10:01:37 -0700 From: "Kurt D. Zeilenga" Organization: Net Boolean Incorporated X-Mailer: Mozilla 4.05 [en] (WinNT; U) MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG Subject: CAM on a -current branch Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've been attempting to construct a decent source combining -current of mid-May (5/13, 5/19, or 5/20) with CAM source available via ftp.freebsd.org. Given the problems with build/install world of mid-May and not knowing the exact time the CAM source was based upon, it's damn near impossible. Figure I'll just wait out the next CAM snapshot. It appears that more and more folks are now running CAM (namely for support of newer devices like the AIC-7895 and overall SCSI stability). I would think it would be wise to check the source into the repository (on a branch of -current). This should would make life easier for the testers and users of this fine software. It might even make life easier for developers (as they would have to rely on folks doing the merge correctly). I'll be running CAM+CCD+Softupdates... hopefully it won't be that interesting. Regards, Kurt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 13 10:12:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA28017 for freebsd-current-outgoing; Mon, 13 Jul 1998 10:12:50 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from panzer.plutotech.com (ken@panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA28007 for ; Mon, 13 Jul 1998 10:12:43 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.8.8/8.8.5) id LAA03753 for current@freebsd.org; Mon, 13 Jul 1998 11:12:38 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199807131712.LAA03753@panzer.plutotech.com> Subject: panic in the dec driver To: current@FreeBSD.ORG Date: Mon, 13 Jul 1998 11:12:38 -0600 (MDT) X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: multipart/mixed; boundary=ELM900349958-3657-0_ Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --ELM900349958-3657-0_ Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit I got a panic today in the DEC driver, and I was wondering if anyone has seen anything similar. Here's a stack trace: ======================================================================== tulip_txput (sc=0xf08b5800, m=0xf0538f00) at machine/pmap.h:172 (kgdb) where #0 tulip_txput (sc=0xf08b5800, m=0xf0538f00) at machine/pmap.h:172 #1 0xf01cb4ad in tulip_ifstart_one (ifp=0xf08b5818) at ../../pci/if_de.c:4843 #2 0xf017965c in ether_output (ifp=0xf08b5818, m0=0xf0536000, dst=0xf336cb70, rt0=0xf08e7f00) at ../../net/if_ethersubr.c:385 #3 0xf018b6f8 in ip_output (m0=0xf0536000, opt=0x0, ro=0xf336cb6c, flags=0, imo=0x0) at ../../netinet/ip_output.c:532 #4 0xf018ff11 in tcp_output (tp=0xf336cba0) at ../../netinet/tcp_output.c:695 #5 0xf0190f4f in tcp_timers (tp=0xf336cba0, timer=0) at ../../netinet/tcp_timer.c:295 #6 0xf0190d64 in tcp_slowtimo () at ../../netinet/tcp_timer.c:151 #7 0xf014bdc3 in pfslowtimo (arg=0x0) at ../../kern/uipc_domain.c:235 #8 0xf013bb63 in softclock () at ../../kern/kern_timeout.c:124 ======================================================================== And here's the snippet of code in question from pmap.h: static __inline vm_offset_t pmap_kextract(vm_offset_t va) { vm_offset_t pa; if ((pa = (vm_offset_t) PTD[va >> PDRSHIFT]) & PG_PS) { pa = (pa & ~(NBPDR - 1)) | (va & (NBPDR - 1)); } else { pa = *(vm_offset_t *)vtopte(va); pa = (pa & PG_FRAME) | (va & PAGE_MASK); } return pa; } The kernel is a CAM kernel based on source from Saturday. (July 11th) This is *not* a CAM problem, however, since I can reproduce the behavior that leads to the panic on a stock current kernel. I think it's dying in vtopte(). The way I reproduce this is: machine A: P6/233, 128MB RAM, Adaptec 2940, Intel 82558 machine B: P5/133, 32MB RAM, Adaptec 2940, DEC 21140-based card both machines are running -current + CAM as of Saturday - rlogin from machine A to machine B - do a find . -print on machine B - find process hangs almost immediately, in the 'ttywri' state. - I can still do things on the console, and I can still do network I/O to and from the box even. - if I do one more keystroke in the rlogin session (xterm), machine B locks up hard. Numlock doesn't work, ctl-alt-esc doesn't work, ctl-alt-del doesn't work. - I waited a while, and then got the above panic I can reproduce this at will on machine B. I've attached the kernel config file and dmesg output. I previously had a kernel based on sources from July 6th on the machine. That kernel worked just fine. I know that Peter Wemm made a small change to the DEC driver on July 8th, but I'm not positive that it's the source of the problem. I have tried disabling, the ipfw code and the snp device, with the idea that they might be contributing to the problem. That made no difference. The next step is to put an Intel card in and see if I get the same behavior with the fxp driver. I'm trying to track down a spare card now... Anyway, if anyone has seen similar behavior, let me know. Ken -- Kenneth Merry ken@plutotech.com --ELM900349958-3657-0_ Content-Type: text/plain; charset=ISO-8859-1 Content-Disposition: attachment; filename=bladerunner Content-Description: bladerunner Content-Transfer-Encoding: 7bit # # GENERIC -- Generic machine with WD/AHx/NCR/BTx family disks # # For more information read the handbook part System Administration -> # Configuring the FreeBSD Kernel -> The Configuration File. # The handbook is available in /usr/share/doc/handbook or online as # latest version from the FreeBSD World Wide Web server # # # An exhaustive list of options and more detailed explanations of the # device lines is present in the ./LINT configuration file. If you are # in doubt as to the purpose or necessity of a line, check first in LINT. # # $Id: GENERIC,v 1.77.2.1 1996/12/21 02:10:50 se Exp $ machine "i386" # cpu "I386_CPU" # cpu "I486_CPU" cpu "I586_CPU" cpu "I686_CPU" ident bladerunner maxusers 64 options INET #InterNETworking options FFS #Berkeley Fast Filesystem options NFS #Network Filesystem options UNION #Union filesystem options MFS #Memory File System options MSDOSFS #MSDOS Filesystem options "CD9660" #ISO 9660 Filesystem options PROCFS #Process filesystem options "COMPAT_43" #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=3 #Be pessimistic about Joe SCSI device options UCONSOLE #Allow users to grab the console # options USERCONFIG #boot -c editor # options VISUAL_USERCONFIG #visual boot -c editor #options CHILD_MAX=128 #options OPEN_MAX=128 options SYSVSHM options SYSVSEM options SYSVMSG options KTRACE options MROUTING options IPFIREWALL options IPFIREWALL_VERBOSE options "IPFIREWALL_VERBOSE_LIMIT=100" options IPDIVERT options DEVFS # options "MAXMEM=(128*1024)" options MAXCONS=16 options AHC_ALLOW_MEMIO options COMPAT_LINUX options DDB #options CDDEBUG #options NO_SCHEDULE_MODS options "CAM_MAX_HIGHPOWER=8" options "CHANGER_MIN_BUSY_SECONDS=3" options "CHANGER_MAX_BUSY_SECONDS=11" options "MSGBUF_SIZE=32768" config kernel root on da0 # config kernel root on da0 controller isa0 # controller eisa0 controller pci0 controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr disk fd0 at fdc0 drive 0 disk fd1 at fdc0 drive 1 # tape ft0 at fdc0 drive 2 # A single entry for any of these controllers (ncr, ahb, ahc, amd) is # sufficient for any number of installed devices. controller ahc0 controller adv0 controller adv1 at isa? port ? cam irq ? controller scbus0 device da0 device cd0 #Only need one of these, the code dynamically grows # Ken's passthrough SCSI driver device pass0 device sa0 device ch0 # controller snd0 # device gus0 at isa? vector gusintr # device gus0 at isa? port 0x220 irq 11 drq 1 flags 0x3 vector gusintr # syscons is the default console driver, resembling an SCO console device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr # Mandatory, don't remove device npx0 at isa? port "IO_NPX" irq 13 vector npxintr device sio0 at isa? port "IO_COM1" tty irq 4 vector siointr device sio1 at isa? port "IO_COM2" tty flags 0x50 irq 3 vector siointr # device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr device lpt0 at isa? disable port? tty irq 7 vector lptintr device lpt1 at isa? disable port? tty # Order is important here due to intrusive probes, do *not* alphabetize # this list of network interfaces until the probes have been fixed. # Right now it appears that the ie0 must be probed before ep0. See # revision 1.20 of this file. device de0 device fxp0 # device vx0 # device ed0 at isa? port 0x280 net irq 5 iomem 0xd8000 vector edintr pseudo-device loop pseudo-device ether pseudo-device sl 1 # ijppp uses tun instead of ppp device #pseudo-device ppp 1 pseudo-device tun 3 pseudo-device pty 128 pseudo-device gzip # Exec gzipped a.out's pseudo-device bpfilter 4 pseudo-device snp 3 pseudo-device vn --ELM900349958-3657-0_ Content-Type: text/plain; charset=ISO-8859-1 Content-Disposition: attachment; filename=br.dmesg Content-Description: br.dmesg Content-Transfer-Encoding: 7bit Copyright (c) 1992-1998 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-CURRENT #0: Mon Jul 13 10:10:19 MDT 1998 ken@roadwarrior.plutotech.com:/usr/home/ken/perforce/cam/sys/compile/bladerunner Calibrating clock(s) ... TSC clock: 132207328 Hz, i8254 clock: 1193540 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz cost 2533 ns CLK_USE_TSC_CALIBRATION not specified - using old calibration method Timecounter "TSC" frequency 132168541 Hz cost 173 ns CPU: Pentium/P54C (132.17-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x52b Stepping=11 Features=0x1bf real memory = 33554432 (32768K bytes) Physical memory chunk(s): 0x00001000 - 0x0009efff, 647168 bytes (158 pages) 0x00299000 - 0x01ff7fff, 30797824 bytes (7519 pages) avail memory = 30150656 (29444K bytes) Found BIOS32 Service Directory header at 0xf00f6f10 Entry = 0xf6f20 (0xf00f6f20) Rev = 0 Len = 1 PCI BIOS entry at 0x6f41 Other BIOS signatures found: ACPI: 00000000 $PnP: 000f9500 DEVFS: ready for devices pci_open(1): mode 1 addr port (0x0cf8) is 0x8000384c pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=122d8086) Probing for devices on PCI bus 0: found-> vendor=0x8086, dev=0x122d, revid=0x02 class=06-00-00, hdrtype=0x00, mfdev=0 chip0: rev 0x02 on pci0.0.0 CPU Inactivity timer: clocks Peer Concurrency: enabled CPU-to-PCI Write Bursting: enabled PCI Streaming: enabled Bus Concurrency: enabled Cache: 256K pipelined-burst secondary; L1 enabled DRAM: no memory hole, 66 MHz refresh Read burst timing: x-2-2-2/x-3-3-3 Write burst timing: x-3-3-3 RAS-CAS delay: 3 clocks found-> vendor=0x8086, dev=0x122e, revid=0x02 class=06-01-00, hdrtype=0x00, mfdev=1 chip1: rev 0x02 on pci0.7.0 I/O Recovery Timing: 8-bit 8 clocks, 16-bit 4 clocks Extended BIOS: disabled Lower BIOS: disabled Coprocessor IRQ13: enabled Mouse IRQ12: disabled Interrupt Routing: A: IRQ12, B: disabled, C: IRQ10, D: IRQ12 MB0: disabled, MB1: disabled found-> vendor=0x8086, dev=0x1230, revid=0x02 class=01-01-80, hdrtype=0x00, mfdev=0 found-> vendor=0x9004, dev=0x8178, revid=0x00 class=01-00-00, hdrtype=0x00, mfdev=0 intpin=a, irq=12 map[0]: type 4, range 32, base 0000f400, size 8 map[1]: type 1, range 32, base ffbdd000, size 12 ahc0: rev 0x00 int a irq 12 on pci0.17.0 ahc0: Reading SEEPROM...done. ahc0: internal SE 50 cable is present, internal SE 68 cable is present ahc0: external SE cable not present ahc0: BIOS eeprom is present ahc0: SE High byte termination Enabled ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs ahc0: Downloading Sequencer Program... 419 instructions downloaded found-> vendor=0x1011, dev=0x0009, revid=0x12 class=02-00-00, hdrtype=0x00, mfdev=0 intpin=a, irq=10 map[0]: type 4, range 32, base 0000f880, size 7 map[1]: type 1, range 32, base ffbdef80, size 7 de0: rev 0x12 int a irq 10 on pci0.18.0 de0: 21140 [10-100Mb/s] pass 1.2 de0: address 00:40:05:21:04:a3 bpf: de0 attached found-> vendor=0x1002, dev=0x4758, revid=0x03 class=03-00-00, hdrtype=0x00, mfdev=0 map[0]: type 1, range 32, base fe000000, size 24 vga0: rev 0x03 on pci0.19.0 found-> vendor=0x9004, dev=0x8178, revid=0x00 class=01-00-00, hdrtype=0x00, mfdev=0 intpin=a, irq=12 map[0]: type 4, range 32, base 0000fc00, size 8 map[1]: type 1, range 32, base ffbdf000, size 12 ahc1: rev 0x00 int a irq 12 on pci0.20.0 using shared irq12. ahc1: Reading SEEPROM...done. ahc1: SE Low byte termination Enabled ahc1: SE High byte termination Enabled ahc1: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs ahc1: Resetting Channel A ahc1: Downloading Sequencer Program... 419 instructions downloaded Probing for devices on the ISA bus: sc0: the current keyboard controller command byte 0045 kbdio: DIAGNOSE status:0055 kbdio: TEST_KBD_PORT status:0000 kbdio: RESET_KBD return code:00fa kbdio: RESET_KBD status:00aa sc0: keyboard device ID: ab41 sc0 at 0x60-0x6f irq 1 on motherboard sc0: BIOS video mode:3 sc0: VGA registers upon power-up 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 07 80 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff sc0: video mode:24 sc0: VGA registers in BIOS for mode:24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff sc0: VGA registers to be used for mode:24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff sc0: rows_offset:1 sc0: VGA color <16 virtual consoles, flags=0x0> sio0: irq maps: 0x1 0x11 0x1 0x1 sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1: reserved for low-level i/o sio1 not found at 0x2f8 lpt0: disabled, not probed. lpt1: disabled, not probed. fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fd0: 1.44MB 3.5in adv1: AdvanSys SCSI Host Adapter, SCSI ID 7, queue depth 16 adv1 at 0x110 irq 11 drq 5 on isa npx0 on motherboard npx0: INT 16 interface i586_bzero() bandwidth = 110375275 bytes/sec bzero() bandwidth = 86926286 bytes/sec imasks: bio c0080040, tty c0070412, net c0070412 BIOS Geometries: 0:03f13f20 0..1009=1010 cylinders, 0..63=64 heads, 1..32=32 sectors 1:0104fe3f 0..260=261 cylinders, 0..254=255 heads, 1..63=63 sectors 0 accounted for Device configuration finished. Intel Pentium F00F detected, installing workaround DEVFS: ready to run Linux-ELF exec handler installed bpf: tun0 attached bpf: tun1 attached bpf: tun2 attached bpf: sl0 attached bpf: lo0 attached IP packet filtering initialized, divert enabled, rule-based forwarding disabled, logging limited to 100 packets/entry SCSI bus reset delivered. 0 SCBs aborted. SCSI bus reset delivered. 0 SCBs aborted. ahc1: Selection Timeout. 1 SCBs aborted ahc0: Selection Timeout. 1 SCBs aborted ahc1: Selection Timeout. 1 SCBs aborted ahc0: Selection Timeout. 1 SCBs aborted ahc1: Selection Timeout. 1 SCBs aborted ahc0: Selection Timeout. 1 SCBs aborted ahc0: Selection Timeout. 1 SCBs aborted ahc1: Selection Timeout. 1 SCBs aborted ahc0: Selection Timeout. 1 SCBs aborted ahc1: Selection Timeout. 1 SCBs aborted ahc0: Selection Timeout. 1 SCBs aborted ahc1: Selection Timeout. 1 SCBs aborted ahc0: Selection Timeout. 1 SCBs aborted ahc1: Selection Timeout. 1 SCBs aborted ahc0: Selection Timeout. 1 SCBs aborted ahc1: Selection Timeout. 1 SCBs aborted ahc0: Selection Timeout. 1 SCBs aborted ahc1: Selection Timeout. 1 SCBs aborted ahc0: Selection Timeout. 1 SCBs aborted ahc0: target 3 synchronous at 10.0MHz, offset = 0x8 ahc0: target 3 using asynchronous transfers ahc0: target 3 synchronous at 10.0MHz, offset = 0x8 ahc0: target 6 synchronous at 4.0MHz, offset = 0xf ahc0: target 6 using asynchronous transfers ahc0: target 6 synchronous at 4.0MHz, offset = 0xf ahc0: target 5 synchronous at 5.0MHz, offset = 0xf ahc0: target 1 synchronous at 20.0MHz, offset = 0xf ahc0: target 0 using 16bit transfers ahc0: target 0 synchronous at 10.0MHz, offset = 0x8 ahc1: Selection Timeout. 1 SCBs aborted ahc1: Selection Timeout. 1 SCBs aborted ahc1: Selection Timeout. 1 SCBs aborted ahc1: Selection Timeout. 1 SCBs aborted ahc1:A:3: refuses synchronous negotiation. Using asynchronous transfers ahc1: target 4 synchronous at 4.0MHz, offset = 0xb ahc1: target 4 using asynchronous transfers ahc1: target 4 synchronous at 4.0MHz, offset = 0xb sa0 at ahc0 bus 0 target 5 lun 0 sa0: Removable Sequential Access SCSI2 device sa0: 5.0MB/s transfers (5.0MHz, offset 15) sa1 at ahc1 bus 0 target 4 lun 0 sa1: Removable Sequential Access SCSI2 device sa1: Serial Number 00263194 sa1: 4.32MB/s transfers (4.32MHz, offset 11) ahc0: target 3 using asynchronous transfers pass0 at ahc0 bus 0 taahc0: target 3 synchronous at 10.0MHz, offset = 0x8 rget 0 lun 0 pass0: Fixed Direct Access SCSI2 device pasahc0: target 6 using asynchronous transfers s0: Serial Number 00893659 pass0: 20.0MB/s transfers (10.0MHz, offset 8, 16bit), Tagged Queueing Enabled ahc0: target 6 synchronous at 4.0MHz, offset = 0xf pass1 at ahc0 bus 0 target 1 lun 0 pass1: Fixed Direct Access SCSI2 device pass1: Serial Number 005950490RF5DZ pass1: 20.0MB/s transfers (20.0MHz, offset 15), Tagged Queueing Enabled pass2 at ahc0 bus 0 target 3 lun 0 pass2: Removable CD-ROM SCSI2 device pass2: 10.0MB/s transfers (10.0MHz, offset 8) pass3 at ahc0 bus 0 target 5 lun 0 pass3: Removable Sequential Access SCSI2 device pass3: 5.0MB/s transfers (5.0MHz, offset 15) pass4 at ahc0 bus 0 target 6 lun 0 pass4: Removable CD-ROM SCSI2 device pass4: 4.32MB/s transfers (4.32MHz, offset 15) pass5 at ahc1 bus 0 target 3 lun 0 pass5: Removable Changer SCSI2 device pass5: 3.300MB/s transfers pass6 at ahc1 bus 0 target 4 lun 0 pass6: Removable Sequential Access SCSI2 device pass6: Serial Number 00263194 pass6: 4.32MB/s transfers (4.32MHz, offset 11) da1 at ahc0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI2 device da1: Serial Number 005950490RF5DZ da1: 20.0MB/s transfers (20.0MHz, offset 15), Tagged Queueing Enabled da1: 2049MB (4197405 512 byte sectors: 255H 63S/T 261C) da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI2 device da0: Serial Number 00893659 da0: 20.0MB/s transfers (10.0MHz, offset 8, 16bit), Tagged Queueing Enabled da0: 1010MB (2069860 512 byte sectors: 64H 32S/T 1010C) cd0 at ahc0 bus 0 target 3 lun 0 cd0: Removable CD-ROM SCSI2 device cd0: 10.0MB/s transfers (10.0MHz, offset 8) cd0: Attempt to query device size failed: NOT READY, Medium not present cd1 at ahc0 bus 0 target 6 lun 0 cd1: Removable CD-ROM SCSI2 device cd1: 4.32MB/s transfers (4.32MHz, offset 15) cd1: Attempt to query device size failed: NOT READY, Medium not present ch0 at ahc1 bus 0 target 3 lun 0 ch0: Removable Changer SCSI2 device ch0: 3.300MB/s transfers ch0: 10 slots, 1 drive, 1 picker, 0 portals Considering FFS root f/s. changing root device to da0s1a da0s1: type 0xa5, start 32, end = 2068479, size 2068448 : OK --ELM900349958-3657-0_-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 13 10:29:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA00765 for freebsd-current-outgoing; Mon, 13 Jul 1998 10:29:12 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from home.dragondata.com (toasty@home.dragondata.com [204.137.237.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA00759 for ; Mon, 13 Jul 1998 10:29:10 -0700 (PDT) (envelope-from toasty@home.dragondata.com) Received: (from toasty@localhost) by home.dragondata.com (8.8.8/8.8.5) id MAA22835; Mon, 13 Jul 1998 12:28:56 -0500 (CDT) From: Kevin Day Message-Id: <199807131728.MAA22835@home.dragondata.com> Subject: Re: panic in the dec driver In-Reply-To: <199807131712.LAA03753@panzer.plutotech.com> from "Kenneth D. Merry" at "Jul 13, 98 11:12:38 am" To: ken@plutotech.com (Kenneth D. Merry) Date: Mon, 13 Jul 1998 12:28:56 -0500 (CDT) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I got a panic today in the DEC driver, and I was wondering if > anyone has seen anything similar. Here's a stack trace: > > ======================================================================== > tulip_txput (sc=0xf08b5800, m=0xf0538f00) at machine/pmap.h:172 > (kgdb) where > #0 tulip_txput (sc=0xf08b5800, m=0xf0538f00) at machine/pmap.h:172 > #1 0xf01cb4ad in tulip_ifstart_one (ifp=0xf08b5818) at ../../pci/if_de.c:4843 > #2 0xf017965c in ether_output (ifp=0xf08b5818, m0=0xf0536000, dst=0xf336cb70, > rt0=0xf08e7f00) at ../../net/if_ethersubr.c:385 > #3 0xf018b6f8 in ip_output (m0=0xf0536000, opt=0x0, ro=0xf336cb6c, flags=0, Yep, I've seen the same thing, about once a month.... Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 13 10:30:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA00986 for freebsd-current-outgoing; Mon, 13 Jul 1998 10:30:45 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from panzer.plutotech.com (ken@panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA00980 for ; Mon, 13 Jul 1998 10:30:43 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.8.8/8.8.5) id LAA03883; Mon, 13 Jul 1998 11:30:39 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199807131730.LAA03883@panzer.plutotech.com> Subject: Re: panic in the dec driver In-Reply-To: <199807131712.LAA03753@panzer.plutotech.com> from "Kenneth D. Merry" at "Jul 13, 98 11:12:38 am" To: ken@plutotech.com (Kenneth D. Merry) Date: Mon, 13 Jul 1998 11:30:39 -0600 (MDT) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kenneth D. Merry wrote... > > I got a panic today in the DEC driver, and I was wondering if > anyone has seen anything similar. Here's a stack trace: > > ======================================================================== > tulip_txput (sc=0xf08b5800, m=0xf0538f00) at machine/pmap.h:172 > (kgdb) where > #0 tulip_txput (sc=0xf08b5800, m=0xf0538f00) at machine/pmap.h:172 > #1 0xf01cb4ad in tulip_ifstart_one (ifp=0xf08b5818) at ../../pci/if_de.c:4843 > #2 0xf017965c in ether_output (ifp=0xf08b5818, m0=0xf0536000, dst=0xf336cb70, > rt0=0xf08e7f00) at ../../net/if_ethersubr.c:385 > #3 0xf018b6f8 in ip_output (m0=0xf0536000, opt=0x0, ro=0xf336cb6c, flags=0, > imo=0x0) at ../../netinet/ip_output.c:532 > #4 0xf018ff11 in tcp_output (tp=0xf336cba0) at ../../netinet/tcp_output.c:695 > #5 0xf0190f4f in tcp_timers (tp=0xf336cba0, timer=0) > at ../../netinet/tcp_timer.c:295 > #6 0xf0190d64 in tcp_slowtimo () at ../../netinet/tcp_timer.c:151 > #7 0xf014bdc3 in pfslowtimo (arg=0x0) at ../../kern/uipc_domain.c:235 > #8 0xf013bb63 in softclock () at ../../kern/kern_timeout.c:124 > ======================================================================== > Sorry to follow up on myself, but I just swapped out the DEC-based card for an Intel EtherExpress Pro/100+ (82558), and everything works just dandy. I think there really is a bug in the DEC driver. BTW, the DEC-based card I have says it's a Linksys, and the chip says it's a 21140-AB. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 13 10:37:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA02530 for freebsd-current-outgoing; Mon, 13 Jul 1998 10:37:01 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ifi.uio.no (0@ifi.uio.no [129.240.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA02525 for ; Mon, 13 Jul 1998 10:36:58 -0700 (PDT) (envelope-from dag-erli@ifi.uio.no) Received: from hel.ifi.uio.no (2602@hel.ifi.uio.no [129.240.64.91]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id TAA06875; Mon, 13 Jul 1998 19:36:49 +0200 (MET DST) Received: (from dag-erli@localhost) by hel.ifi.uio.no ; Mon, 13 Jul 1998 19:36:48 +0200 (MET DST) Mime-Version: 1.0 To: Ollivier Robert Cc: current@FreeBSD.ORG Subject: Re: TESTERS NEEDED: Softupdates looks Very good. References: <35A52E6B.6201DD56@whistle.com> <19980710235529.A6695@keltia.freenix.fr> Organization: University of Oslo, Department of Informatics X-url: http://www.stud.ifi.uio.no/~dag-erli/ X-other-addresses: 'finger dag-erli@ifi.uio.no' for a list X-disclaimer-1: The views expressed in this article are mine alone, and do X-disclaimer-2: not necessarily coincide with those of any organisation or X-disclaimer-3: company with which am or have been affiliated. X-Stop-Spam: http://www.cauce.org/ From: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= ) Date: 13 Jul 1998 19:36:48 +0200 In-Reply-To: Ollivier Robert's message of "Fri, 10 Jul 1998 23:55:29 +0200" Message-ID: Lines: 33 X-Mailer: Gnus v5.5/Emacs 19.34 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id KAA02526 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ollivier Robert writes: > According to Dag-Erling Coidan Smørgrav: > > Am I right to assume that failing a news server, 'make world' is the > > best file system stress test? I might install a repository copy and do > > a complete 'make release NOPORTS=YES NODOCS=YES' while I'm at it... > "make buildworld" should succeed without problem. Now, "make installworld" > is another matter and what was failing up to now. I'll test the new version > soon. I've run a bunch of make world, make buildworld, make installworld, make reinstall, kernel compilations, ports compilations. I installed -current from scratch; first the february snapshot from a CD - hi Eivind! ;) - then I cvsupped from niobe, made world and built a kernel, rebooted, enabled softupdates on all filesystems (including root), compiled a bunch of ports (bash, ssh, lynx, ncftp2 and a few others). No fs problems at all. I *am* having trouble with that box, but I don't think it fs related. It's very weird though; the main problem is that init(8) just stops cold after running /etc/rc. It never starts getty(8). I tried adding 'set -x' to the top of /etc/rc, and confirmed that it runs through the whole thing, but stops cold right after /etc/rc ends. The console still works, kinda; I can scroll up and down with ScrollLock, but I can't type anything, much less log in. The machine responds to pings, but not to ssh; I suspect the problem is tty/vty/pty related. Single-user mode works just fine. I am running with DEVFS and SLICE, and haven't tried disabling them; there are lots of possibilities I haven't explored yet, due to lack of time (and right now lack of a monitor) but if any of you has a suggestion I'll try it out. DES -- One two, one two, one two. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 13 10:58:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA05399 for freebsd-current-outgoing; Mon, 13 Jul 1998 10:58:41 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.hughes.net (mail.hughes.net [205.139.35.24]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA05375; Mon, 13 Jul 1998 10:58:31 -0700 (PDT) (envelope-from jer@hughes.net) Received: from ws-47-110.selectaswitch.com (47-110.hughes.net [208.135.47.110]) by mail.hughes.net (post.office MTA v2.0 0813 ID# 0-13727) with SMTP id AAA1842; Mon, 13 Jul 1998 10:58:23 -0700 Message-ID: <009501bdae88$70e84f20$6e2f87d0@ws-47-110.selectaswitch.com> From: "Jeremy Domingue" To: , , , Subject: Disgruntled Linux User... questions about FreeBSD Date: Mon, 13 Jul 1998 11:02:45 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hey all... First of all, parts of this message may sound like Linux bashing to some people... that's not my intent, so if I come across that way I apoligize. Also, this message is going to be pretty long... please bear with me. I started using Linux (RedHat) a year ago. At first, I had a lot of problems but I assumed that was simply because I was very unexperienced and had to go through the normal learning curve that everyone does. About 8 months ago, I got myself a brand new Gateway (ALR) Pentium II 266 server, and needless to say I was completely excited. I thought that with this new hardware linux was going to completely ROCK and fix some of the problems I was having with my previous (clone) server. Obviously, since I am here now, it did not. Ever since I first installed Linux a year ago I have been going back and forth from bug to bug, problem to problem, in a never ending battle of trying to get my server to stay up any more than a week. I have been told everything from "your hardware is bad" to "wait for the next version" to "that's not supported" to "there are bugs in that code and someone needs to fix it". Frankly, I am SICK of hearing this again and again! If I had some piece of crap clone hardware, I could probably understand some of the issues I have been having, but this is name brand (what I thought to be) quality hardware! I have replaced almost every piece of hardware in that server under the assumption it was bad and it has not helped one bit. When I started out with my new Gateway server, it was just a plain Pentium II 266 w/ 128mb of RAM. After googles of crashes, I thought, well, maybe it just isn't enough server for the load. So, I proceeded to get a second PII processor and upgraded to 512mb of RAM. More crashes, different errors, the story of my life with Linux. I have tried the latest release and development kernels, just about every patch I can find, and nothing works with it. It is the most unstable computer I have ever used in my entrie life... and I run an NT box as well (pretty sad the NT box stays up for months on end and I can't even keep the linux box running a week). So, at this point, I am looking for a fresh start, something that will allow the server to actually run a week or more without crashing. Finally, to my questions about FreeBSD: 1) First and foremost, I am wondering what issues I will face being a user very accustomed to linux. I know there will be differences between linux and FreeBSD, but can anyone outline some of the major ones? 2) Is there a way I can install FreeBSD without losing all of the stuff on the server right now such as user files, web pages, programs, etc? And possibly keep linux on there somewhere in case I ever decide to go back? 3) Is anyone using SMP on FreeBSD with an Adaptec 7880 on-board SCSI controller? Linux people keep telling me that this is not a good configuration for Linux... how about for FreeBSD? 4) I know that the current build of FreeBSD is listed as development and should not be used in a mission critical environment, however, what are people's experiences with it so far? If it seems to be fairly stable, I would be willing to give it a shot... I really need the SMP support. 5) Are there any other problems or issues I may face with my hardware configuration (listed below)? I would also be very interested in hearing from other previous (or current) Linux users' experiences with FreeBSD, and what comments they may have about the differences and advantages (especially stability-wise) to using FreeBSD instead of Linux. Any input would be greatly appreciated.... Only 24 hours till the next Linux crash... woo hoo! TIA, Jeremy Domingue jer@hughes.net Hardware Configuration: Gateway (formerly ALR) NS-7000 Server Dual PII 266mhz 512mb EDO ECC SDRAM (all from the same lot, same manufacturer) Adaptec 7880 on-board SCSI controller 3Com 10/100 Ethernet Card 2-4.1gb IBM SCSI hard drives To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 13 12:05:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA16686 for freebsd-current-outgoing; Mon, 13 Jul 1998 12:05:36 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA16658 for ; Mon, 13 Jul 1998 12:05:27 -0700 (PDT) (envelope-from gallatin@duke.cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.8.5/8.8.5) with ESMTP id PAA10051 for ; Mon, 13 Jul 1998 15:05:18 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.8.8/8.8.8) id PAA08176; Mon, 13 Jul 1998 15:05:17 -0400 (EDT) (envelope-from gallatin) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Mon, 13 Jul 1998 15:05:17 -0400 (EDT) To: current@FreeBSD.ORG Subject: PF_LOCAL socket problems? X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <13738.22232.735035.745625@grasshopper.cs.duke.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Over the weekend, I built world (and kernel) for the first time in months. Much to my chagrin, I've had X apps dying with BadLength X errors all day. The primary offendors are Netscape & Xemacs, which tend lock up after issuing errors like: X Error of failed request: BadLength (poly request too large or internal Xlib length error) Major opcode of failed request: 86 (X_AllocColorCells) Serial number of failed request: 59501 Current serial number in output stream: 59576 Widget hierarchy of resource: unknown I can generally crash Netscape within a few seconds by loading a large page & scrolling around in it. The reason I suspect PF_LOCAL sockets is because these problems go away if I set my DISPLAY to machinename:0.0 rather than :0.0. As I recall, X apps talk to a server with a display of :0.0 via PF_LOCAL sockets. Not that it matters, but this is on a 300Mhz PII, running XF86 3.3.2 (XF86_SVGA atop a 4MB NNidia Riva128 agp video card) Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 13 12:24:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA19485 for freebsd-current-outgoing; Mon, 13 Jul 1998 12:24:46 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gatekeeper.falcon.com (bppp1.sysnet.net [206.142.16.35]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA19472 for ; Mon, 13 Jul 1998 12:24:28 -0700 (PDT) (envelope-from patton@sysnet.net) Received: from [192.168.1.10] ([192.168.1.10]) by gatekeeper.falcon.com (8.8.8/8.8.5) with ESMTP id PAA21606 for ; Mon, 13 Jul 1998 15:14:57 -0400 (EDT) X-Sender: patton@mail.sysnet.net Message-Id: In-Reply-To: <199807101013.DAA22643@mailgate.cadence.com> References: <199807100843.SAA27370@cimlogic.com.au> from Matthew Patton at "Jul 8, 98 08:02:49 pm" Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sun, 12 Jul 1998 03:45:37 -0400 To: freebsd-current@FreeBSD.ORG From: Matthew Patton Subject: Re: SOLUTION! 2.2.6-Release to -current Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG well I will concede that probably the vast majority of people out there do not seem to have problems doing a buildworld. But what I find interesting is that NOBODY seems to have done an FTP install which is what I do and did. Not that it should make any difference. Seems the "-m" directive doesn't help 100% of the time either. It ought to, I agree. I've also run into the problems with vinode.c being garbage or 0 bytes and having to restart the kernel build. This is a bit strange. To those out there having trouble (like libc failing) make sure you cvsup again (just in case) and give my steps a whirl. YMMV. -------- "If I were called upon to identify briefly the principal trait of the 20th Century, here too I would be unable to find anything more precise and pithy than to repeat once again: Men have forgotten God." - Aleksander Solzhenitsyn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 13 12:26:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA19903 for freebsd-current-outgoing; Mon, 13 Jul 1998 12:26:18 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from echonyc.com (echonyc.com [198.67.15.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA19897 for ; Mon, 13 Jul 1998 12:26:16 -0700 (PDT) (envelope-from benedict@echonyc.com) Received: from localhost (benedict@localhost) by echonyc.com (8.8.7/8.8.7) with SMTP id PAA18581; Mon, 13 Jul 1998 15:26:03 -0400 (EDT) Date: Mon, 13 Jul 1998 15:26:02 -0400 (EDT) From: Snob Art Genre Reply-To: ben@rosengart.com To: Andrew Gallatin cc: current@FreeBSD.ORG Subject: Re: PF_LOCAL socket problems? In-Reply-To: <13738.22232.735035.745625@grasshopper.cs.duke.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 13 Jul 1998, Andrew Gallatin wrote: > Over the weekend, I built world (and kernel) for the first time in > months. Much to my chagrin, I've had X apps dying with BadLength X > errors all day. The primary offendors are Netscape & Xemacs, which > tend lock up after issuing errors like: I don't get this with netscape, but xmix does it reliably on startup. > The reason I suspect PF_LOCAL sockets is because these problems go > away if I set my DISPLAY to machinename:0.0 rather than :0.0. > As I recall, X apps talk to a server with a display of :0.0 via > PF_LOCAL sockets. Hey, look at that, I set DISPLAY to localhost:0.0 and now xmix works. > Not that it matters, but this is on a 300Mhz PII, running XF86 3.3.2 > (XF86_SVGA atop a 4MB NNidia Riva128 agp video card) 200 MHz PPro here, same X server, but the S3V version. Ben "You have your mind on computers, it seems." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 13 13:49:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA02705 for freebsd-current-outgoing; Mon, 13 Jul 1998 13:49:01 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA02700 for ; Mon, 13 Jul 1998 13:48:59 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id NAA20587 for ; Mon, 13 Jul 1998 13:41:34 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd020572; Mon Jul 13 20:41:29 1998 Date: Mon, 13 Jul 1998 13:41:22 -0700 (PDT) From: Julian Elischer To: current@FreeBSD.ORG Subject: CVS problems anyone? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Has anyone seen the following behaviour? 1/ generate large set of changes.. cvs diff -c >/tmp/xx try apply patch to a clean try discover that the diff file is corrupted.. the symptom is that after about 800 or so lines of diff, a line is truncated, (including the \n) this the patch is corrupted because the line counts for that section are incorrent.. it's easily reproducible here, on my 2.2.5 machine using freefall as the server, and on 3.0 using a 2.2.6 machine as the server. julian (hand fixing all my diff files so that I can apply them to the -current sources) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 13 14:31:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA13199 for freebsd-current-outgoing; Mon, 13 Jul 1998 14:31:04 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA13108 for ; Mon, 13 Jul 1998 14:30:46 -0700 (PDT) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.0/frmug-2.3/nospam) with UUCP id XAA13568 for current@FreeBSD.ORG; Mon, 13 Jul 1998 23:30:34 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: (from roberto@localhost) by keltia.freenix.fr (8.9.0.Beta4/keltia-2.14/nospam) id VAA01929 for current@FreeBSD.ORG; Mon, 13 Jul 1998 21:50:42 +0200 (CEST) (envelope-from roberto) Message-ID: <19980713215042.A1919@keltia.freenix.fr> Date: Mon, 13 Jul 1998 21:50:42 +0200 From: Ollivier Robert To: current@FreeBSD.ORG Subject: Re: TESTERS NEEDED: Softupdates looks Very good. Mail-Followup-To: current@FreeBSD.ORG References: <35A52E6B.6201DD56@whistle.com> <19980710235529.A6695@keltia.freenix.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.93i In-Reply-To: =?iso-8859-1?Q?=3Cxzphg0lmz4f=2Efsf=40hel=2Eifi=2Euio=2Eno=3E=3B_from_Da?= =?iso-8859-1?Q?g-Erling_Coidan_Sm=F8rgrav__on_Mon=2C_Jul_13=2C_1998_at_0?= =?iso-8859-1?Q?7:36:48PM_+0200?= X-Operating-System: FreeBSD 3.0-CURRENT ctm#4462 AMD-K6 MMX @ 225 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Dag-Erling Coidan Smørgrav : > I've run a bunch of make world, make buildworld, make installworld, > make reinstall, kernel compilations, ports compilations. I installed Well, I ran "make world" with yesterday's sources and it succeeded without a problem during "installworld". Softupdates are now back on all partitions. Thanks to Kirk, Julian and all who made it working ! -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #61: Sun Jul 12 14:38:23 CEST 1998 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 13 14:52:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA16258 for freebsd-current-outgoing; Mon, 13 Jul 1998 14:52:12 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gatekeeper.falcon.com (appp12.sysnet.net [206.142.16.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA16246 for ; Mon, 13 Jul 1998 14:52:07 -0700 (PDT) (envelope-from patton@sysnet.net) Received: from [192.168.1.10] ([192.168.1.10]) by gatekeeper.falcon.com (8.8.8/8.8.5) with ESMTP id RAA10426 for ; Mon, 13 Jul 1998 17:42:37 -0400 (EDT) X-Sender: patton@mail.sysnet.net Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sun, 12 Jul 1998 17:48:20 -0400 To: freebsd-current@FreeBSD.ORG From: Matthew Patton Subject: living without PROCFS Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is there any way to eliminate the use of procfs from -current? I discovered what happens when you leave it out of the kernel config file. Or is /proc a really useful device that is for now and forevermore "standard"? It used to be, that there existed all sorts of security problems with PROCFS. Notably on slowaris. -------- "If I were called upon to identify briefly the principal trait of the 20th Century, here too I would be unable to find anything more precise and pithy than to repeat once again: Men have forgotten God." - Aleksander Solzhenitsyn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 13 14:53:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA16412 for freebsd-current-outgoing; Mon, 13 Jul 1998 14:53:06 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from myrddin.demon.co.uk (exim@myrddin.demon.co.uk [158.152.54.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA16389 for ; Mon, 13 Jul 1998 14:52:56 -0700 (PDT) (envelope-from dom@myrddin.demon.co.uk) Received: from dom by myrddin.demon.co.uk with local (Exim 1.92 #1) id 0yvRzX-00006l-00; Sun, 12 Jul 1998 20:40:59 +0100 To: Matthew Jason Euclid Barnhart Cc: freebsd-current@FreeBSD.ORG Subject: Re: Secure portmap in /usr/src/usr.sbin/portmap References: <19980712124741.46946@io.com> From: Dom Mitchell In-Reply-To: Matthew Jason Euclid Barnhart's message of "Sun, 12 Jul 1998 12:47:41 -0500" X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald" Date: Sun, 12 Jul 1998 20:40:59 +0100 Message-Id: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Jason Euclid Barnhart writes: > My system is PII/266, running 3.0-CURRENT (daily cvsup). > > I've installed tcp_wrappers-7.6 from the Ports collection, and tcpd > works fine from inetd. In looking at the Makefile and source for the > distributed portmap, it looks as though I can simply define HOSTS_ACCESS > (which I've tried in /etc/make.conf, and by hand) to enable wrappers > support. However, every compile fails as such: > > cc -O -pipe -DHOSTS_ACCESS -DCHECK_PORT -o portmap portmap.o > from_local.o pmap_check.o > pmap_check.o: Undefined symbol `_hosts_ctl' referenced from text segment > pmap_check.o: Undefined symbol `_hosts_ctl' referenced from text segment > pmap_check.o: Undefined symbol `_hosts_ctl' referenced from text segment > *** Error code 1 Try adding (not sure of the exact bmake syntax): LDADD+= -lwrap To the Makefile. You might also need to point it at the correct lib directory under /usr/local/lib. -- ``If make doesn't do what you expect it to, it's a good chance the makefile is wrong.'' -- Adam de Boor To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 13 15:13:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA20422 for freebsd-current-outgoing; Mon, 13 Jul 1998 15:13:15 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from symbion.srrc.usda.gov ([199.78.118.118]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA20399 for ; Mon, 13 Jul 1998 15:13:05 -0700 (PDT) (envelope-from glenn@nola.srrc.usda.gov) Received: from nola.srrc.usda.gov (localhost.srrc.usda.gov [127.0.0.1]) by symbion.srrc.usda.gov (8.8.8/8.8.8) with ESMTP id RAA02798; Mon, 13 Jul 1998 17:12:04 -0500 (CDT) (envelope-from glenn@nola.srrc.usda.gov) Message-Id: <199807132212.RAA02798@symbion.srrc.usda.gov> X-Mailer: exmh version 2.0.2 2/24/98 To: "Jeremy Domingue" cc: current@FreeBSD.ORG From: Glenn Johnson Subject: Re: Disgruntled Linux User... questions about FreeBSD In-reply-to: Your message of "Mon, 13 Jul 1998 11:02:45 PDT." <009501bdae88$70e84f20$6e2f87d0@ws-47-110.selectaswitch.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 13 Jul 1998 17:12:04 -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I used Linux for a while so I may be of some help. I must say that I did not experience problems with Linux of the magnitude that you outlined but I can say without any hesitation that FreeBSD is better. > > 1) First and foremost, I am wondering what issues I will face being a user > very accustomed to linux. I know there will be differences between linux and > FreeBSD, but can anyone outline some of the major ones? The first thing you will probably notice is that rather than have a ton of software packages to choose whether to install or not, the FreeBSD installation process loads a fairly minimal (relative to RedHat Linux) set of tools. You then build your system up with the ports/packages that you select. Also, there is no "default" X configuration. The next thing you will notice is that FreeBSD uses csh by default and Linux uses Bash. Bash is available in the ports but of course needs to be installed later. When it comes to administration, Linux, particularly RedHat uses SYSV initialazion scripts for each service it starts up. The BSD style is to basically configure the system with variable initializations in one script, ie. /etc/rc.conf. Also, there are no runlevels as in Linux, although there are different security levels and a single user mode. > > 2) Is there a way I can install FreeBSD without losing all of the stuff on > the server right now such as user files, web pages, programs, etc? And > possibly keep linux on there somewhere in case I ever decide to go back? > Yes, refer to the installation instructions for partioning your disk. > > 3) Is anyone using SMP on FreeBSD with an Adaptec 7880 on-board SCSI > controller? Linux people keep telling me that this is not a good > configuration for Linux... how about for FreeBSD? > Yes, I have 4 such systems running large computational chemistry calculations. They literally run 24/7 with 100% CPU load. I also have two other systems with dual PentiumPros. > > 4) I know that the current build of FreeBSD is listed as development and > should not be used in a mission critical environment, however, what are > people's experiences with it so far? If it seems to be fairly stable, I > would be willing to give it a shot... I really need the SMP support. > Well, I consider the jobs that my systems do to be mission critiacal. I have a total of 6 FreeBSD SMP systems and have never had a crash. The only problem I have had in the past year and a half with -CURRENT was a few months ago when NFS was broken for a few weeks. That has since been fixed. I find it necessary to closely monitor the state of -CURRENT via the mailing lists and commit e-mails. > > 5) Are there any other problems or issues I may face with my hardware > configuration (listed below)? > > > Hardware Configuration: > > Gateway (formerly ALR) NS-7000 Server > Dual PII 266mhz > 512mb EDO ECC SDRAM (all from the same lot, same manufacturer) > Adaptec 7880 on-board SCSI controller > 3Com 10/100 Ethernet Card > 2-4.1gb IBM SCSI hard drives The only possible problem you may have is with the Ethernet card. I am assuming that is one of the so-called vortex cards. If it is a 3C509, you are OK; if it is a 3C509B, then it will not work. I understand that there is a driver being worked on but I do not know when it will be available. Ethernet cards are not terribly expensive and most people recommend the Intel EtherExpress Pro 100+. > > I would also be very interested in hearing from other previous (or current) > Linux users' experiences with FreeBSD, and what comments they may have about > the differences and advantages (especially stability-wise) to using FreeBSD > instead of Linux. > I find the ports/package system of FreeBSD to be much less of a pain than the package (rpm) system of RedHat. I find it easier to administer FreeBSD as well, but these types of things are really a matter of taste. By the way, FreeBSD can run Linux binaries. Finally, I do not know much about Linux mailing lists but the FreeBSD mailing lists are excellent. I try to figure out things as much I can on my own, but when I have asked a question I get a courteous and accurate response within a day. I hope this helps. Good luck! -- Glenn Johnson Technician USDA, ARS, SRRC New Orleans, LA To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 13 15:17:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA21174 for freebsd-current-outgoing; Mon, 13 Jul 1998 15:17:50 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from thing.dyn.ml.org (root@dyn-max8-191.chicago.il.ameritech.net [206.141.211.191] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA21115 for ; Mon, 13 Jul 1998 15:17:39 -0700 (PDT) (envelope-from mcdougall@ameritech.net) Received: from ameritech.net (bsdx [192.168.1.2]) by thing.dyn.ml.org (8.8.8/8.8.7) with ESMTP id SAA11292; Mon, 13 Jul 1998 18:17:24 -0400 (EDT) (envelope-from mcdougall@ameritech.net) Message-ID: <35AA8772.80993BB2@ameritech.net> Date: Mon, 13 Jul 1998 18:17:22 -0400 From: Adam McDougall Reply-To: mcdougall@ameritech.net X-Mailer: Mozilla 4.05 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: Andrew Gallatin CC: current@FreeBSD.ORG Subject: Re: PF_LOCAL socket problems? References: <13738.22232.735035.745625@grasshopper.cs.duke.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andrew Gallatin wrote: > Over the weekend, I built world (and kernel) for the first time in > months. Much to my chagrin, I've had X apps dying with BadLength X > errors all day. The primary offendors are Netscape & Xemacs, which > tend lock up after issuing errors like: > > X Error of failed request: BadLength (poly request too large or internal Xlib length error) > Major opcode of failed request: 86 (X_AllocColorCells) > Serial number of failed request: 59501 > Current serial number in output stream: 59576 > Widget hierarchy of resource: unknown > > I can generally crash Netscape within a few seconds by loading a large > page & scrolling around in it. > > The reason I suspect PF_LOCAL sockets is because these problems go > away if I set my DISPLAY to machinename:0.0 rather than :0.0. > As I recall, X apps talk to a server with a display of :0.0 via > PF_LOCAL sockets. > > Not that it matters, but this is on a 300Mhz PII, running XF86 3.3.2 > (XF86_SVGA atop a 4MB NNidia Riva128 agp video card) > > Drew > > ------------------------------------------------------------------------------ > Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin > Duke University Email: gallatin@cs.duke.edu > Department of Computer Science Phone: (919) 660-6590 > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message I too run 3.3.2 and SVGA server and -current and have been noticing the same symptoms with VNC, and sure enough using -display myhostname:0 cleared it up, thanks for the workaround! I was getting this before, while using VNC to contant either of my two NT machines. To one machine it bombed out reliably on the first screen refresh, and the other randomly. X Error of failed request: BadLength (poly request too large or internal Xlib l ength error) Major opcode of failed request: 16 (X_InternAtom) Serial number of failed request: 8403 Current serial number in output stream: 8930 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 13 15:28:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA23601 for freebsd-current-outgoing; Mon, 13 Jul 1998 15:28:56 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from tarsier.ca.sandia.gov (tarsier.ca.sandia.gov [146.246.246.124]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA23593 for ; Mon, 13 Jul 1998 15:28:53 -0700 (PDT) (envelope-from cc@tarsier.ca.sandia.gov) Received: from tarsier.ca.sandia.gov (localhost [127.0.0.1]) by tarsier.ca.sandia.gov (8.8.8/8.8.8) with ESMTP id PAA16266; Mon, 13 Jul 1998 15:27:26 -0700 (PDT) (envelope-from cc@tarsier.ca.sandia.gov) Message-Id: <199807132227.PAA16266@tarsier.ca.sandia.gov> X-Mailer: exmh version 2.0.2 2/24/98 To: Matthew Patton cc: freebsd-current@FreeBSD.ORG Subject: Re: living without PROCFS In-reply-to: Your message of "Sun, 12 Jul 1998 17:48:20 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 13 Jul 1998 15:27:26 -0700 From: "Chris Csanady" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Is there any way to eliminate the use of procfs from -current? I discovered >what happens when you leave it out of the kernel config file. Or is /proc a >really useful device that is for now and forevermore "standard"? It used to >be, that there existed all sorts of security problems with PROCFS. Notably >on slowaris. Well without procfs, you are stuck with groveling through kmem. Kmem is a terrible interface for this type of thing, as it requires a recompile of many utilites when the kernel structures change. It is arguable much more dangerous as well, since it requires access to all of kernel memory. Procfs (and the like) provide a much cleaner interface, and will probably stick around for a good long time. If anything, the use of kmem for this type of thing should go away altogether. Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 13 16:18:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA01701 for freebsd-current-outgoing; Mon, 13 Jul 1998 16:18:46 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from engulf.net (engulf.com [207.96.124.102]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA01620; Mon, 13 Jul 1998 16:18:35 -0700 (PDT) (envelope-from brandon@engulf.net) Received: from localhost (brandon@localhost) by engulf.net (8.8.8/8.8.8) with SMTP id TAA10505; Mon, 13 Jul 1998 19:14:25 -0400 (EDT) Date: Mon, 13 Jul 1998 19:14:16 -0400 (EDT) From: Brandon Lockhart To: Jeremy Domingue cc: current@FreeBSD.ORG, stable@FreeBSD.ORG, smp@FreeBSD.ORG, questions@FreeBSD.ORG Subject: Re: Disgruntled Linux User... questions about FreeBSD In-Reply-To: <009501bdae88$70e84f20$6e2f87d0@ws-47-110.selectaswitch.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG First of all, I do not recommend Gateway 2k for server's. Get a COMPAQ or HP or SUN. RISC is the way to go. Second of all, no offense, but I don't need to hear your life story about your *server*, you could have just asked the questions. :1) First and foremost, I am wondering what issues I will face being a user :very accustomed to linux. I know there will be differences between linux and :FreeBSD, but can anyone outline some of the major ones? Well, let's see. Linux is a clone of SYSV, and FreeBSD a clone of BSD, is that major enough for you? Possibly different devices, different FS, different operating system, just to name a few. :2) Is there a way I can install FreeBSD without losing all of the stuff on :the server right now such as user files, web pages, programs, etc? And :possibly keep linux on there somewhere in case I ever decide to go back? Ever heard of a tape backup or multiple partitions? Possibly a nice CD-RW :3) Is anyone using SMP on FreeBSD with an Adaptec 7880 on-board SCSI :controller? Linux people keep telling me that this is not a good :configuration for Linux... how about for FreeBSD? Most likely. I am not to experienced with it. :4) I know that the current build of FreeBSD is listed as development and :should not be used in a mission critical environment, however, what are :people's experiences with it so far? If it seems to be fairly stable, I :would be willing to give it a shot... I really need the SMP support. I love my 3.0-CURRENT, update every saturday. yes, sometimes I do need to patch some things, but hey, that's what you get when you have crappy hardware. :5) Are there any other problems or issues I may face with my hardware :configuration (listed below)? Read #1, difference device names and you may have faster access to the devices, if that is a problem for you. Your performance will most likely be boosted, and you will most likely have a more stable system, my suggestion, hit it with a stick twice a night or until it crashes to solve the stability problem. :I would also be very interested in hearing from other previous (or current) :Linux users' experiences with FreeBSD, and what comments they may have about :the differences and advantages (especially stability-wise) to using FreeBSD :instead of Linux. : :Any input would be greatly appreciated.... : :Only 24 hours till the next Linux crash... woo hoo! : :TIA, : :Jeremy Domingue :jer@hughes.net : :Hardware Configuration: : :Gateway (formerly ALR) NS-7000 Server :Dual PII 266mhz :512mb EDO ECC SDRAM (all from the same lot, same manufacturer) :Adaptec 7880 on-board SCSI controller :3Com 10/100 Ethernet Card :2-4.1gb IBM SCSI hard drives : : :To Unsubscribe: send mail to majordomo@FreeBSD.org :with "unsubscribe freebsd-current" in the body of the message : ,-----------------------------------------------------------------. | //// "Anything I say represents only my opinion." | | (o o) / | | ,---ooO--(_)--Ooo---------------------------------------------, | | | BRANDON LOCKHART | | | `-------------------------------------------------------------' | | brandon.lockhart@usinternetworking.com brandon@engulf.net | | Work: (410) 897-4551 Pager: (888) xxx-xxxx | `-----------------------------------------------------------------' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 13 16:27:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA03323 for freebsd-current-outgoing; Mon, 13 Jul 1998 16:27:20 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pluto.plutotech.com (mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA03302; Mon, 13 Jul 1998 16:27:18 -0700 (PDT) (envelope-from gibbs@plutotech.com) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.8.7/8.8.5) with ESMTP id RAA11828; Mon, 13 Jul 1998 17:27:14 -0600 (MDT) Message-Id: <199807132327.RAA11828@pluto.plutotech.com> X-Mailer: exmh version 2.0.2 2/24/98 To: scsi@FreeBSD.ORG cc: current@FreeBSD.ORG, stable@FreeBSD.ORG Subject: 11980712 CAM snapshot now available. Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 13 Jul 1998 17:22:01 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Complete information about this snapshot may be obtains from: ftp://ftp.FreeBSD.org/pub/FreeBSD/cam/README or ftp://ftp.kdm.org/pub/FreeBSD/cam/README The snapshot is currently available in diff form only, but a full 3.0SNAP binary release should be available on ftp.FreeBSD.org tonight or tomorrow morning. A release for 2.2-stable should follow a day later. Changes for the 19980712 Snapshot: - Ports collection now includes Tosha, cdrecord, and xmcd 2.3. - Added devstat(3) and devstat(9) man page. - Some bug fixes to the hard-wiring code. - Added preliminary Adaptec 174X driver. - Aic7xxx driver improvements: Attempt to read SEEPROM data in both formats before failing. This should allow the driver to detect a SEEPROM on many mother board controllers. Correct the setting of the SCSIID for ULTRA2 chips if we can't find a SEEPROM. Fix hang in dataphase on Rev B. aic7880 parts. Correct some LVD/Ultra2 bugs. LVD support has now been tested on a 2940U2W with both Seagate Cheetah and Quantum Atlas II LVD drives. Corrected incorrect sync rate setting for all non-ULTRA2 adapters for rates other than 20MHz or 10MHz. This was a bug introduced in the last snapshot. Fixed a few error recovery bugs. Added support for reading the SEEPROM from aic7850 based cards like the 2910C. - Corrected several bugs in the AdvanSys driver's command completion and timeout handling code as well as fully convert it to bus_dma. Thanks to John-Mark Gurney for being a patient tester. - Corrected several bugs in the BusLogic MultiMaster driver's command completion and timeout handling code. Thanks again to John-Mark Gurney for being a patient tester. - Incorperated a few bug fixes from Stefan Esser for the NCR driver. Some experimental fixes to the QUEUE FULL handler are also included. - QLogic ISP driver integrated by Matthew Jacob - Allow the CD driver to attach to WORM devices. - Corrected devstat(9) support in the floppy driver. - Added support for "short erase" as "mt erase 0". The sa driver defaults to a "long erase" as is the behavior of the st driver it replaces. - Be smarter about tape devices that lack a compression page. Corrects a problem reported by Joey Miller where the driver refused to access an Archive DDS1 drive. - Add support for PC98 geometry conversion based on code provided by KATO Takenori . - Mode page editing features have been incorporated into the camcontrol utility. - libcam now knows how to parse arbitrary command strings just like the old SCSI library. - Use 10byte CDBs for CDROM reads and writes. The spec lists 6byte CDBs as optional. - The XPT layer no longer caches sync rate information. Instead it asks the SIM driver when it wants it. This should ensure that mailbox based and cards with similar interfaces don't have to jump through hoops to provide this information via an async callback. It should make the information provided by the bt and isp drivers acurate. - Fixed several problems in the CAM_GET_PASSTHROUGH xpt ioctl. >From Hans Huebner - Updated the ch(4) driver and chio(1) command to include volume tag support. These changes have been tested with a Breeze Hill Q47 DLT and a DEC DLT2500 media changer. The latter has no volume tag support. - The chio(1) command was updated to include various flags to the status subcommand. These flags can be used to select additional information to be displayed (like volume tags). - A new chio(1) subcommand named 'voltag' has been added which allows for changes to volume tags inside the media changer controller. This could not be tested as the Q47 does not provide the functio- nality. - The ch(4) manual page was updated to include more information about the reality of this driver. - usr.sbin/rmt/rmt.c has been updated to include the V command, which is used by SGI's xfsdump to verify the rmt servers version number. -- Justin T. Gibbs Kenneth D. Merry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 13 16:48:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA07565 for freebsd-current-outgoing; Mon, 13 Jul 1998 16:48:59 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from vortex.starix.net (syko@vortex.starix.net [208.219.83.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA07552 for ; Mon, 13 Jul 1998 16:48:51 -0700 (PDT) (envelope-from syko@sykotik.org) Received: from localhost (syko@localhost) by vortex.starix.net (8.7.6/8.7.3) with SMTP id TAA24545 for ; Mon, 13 Jul 1998 19:46:05 -0400 X-Authentication-Warning: vortex.starix.net: syko owned process doing -bs Date: Mon, 13 Jul 1998 19:46:05 -0400 (EDT) From: Dusk Auriel Sykotik X-Sender: syko@vortex.starix.net To: current@FreeBSD.ORG Subject: alpha support Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I was wondering if -CURRENT supported the alpha platform, and if not when does it expect to be supported? Right now the only options presented to me for alphas are redhat linux (ugh) and digiunix (too much money). I would prefer to run FreeBSD, since its running on the other server now, and its run very well for me, and I've really enjoyed working with it. Thanks. /* * Matt Harris +++ Syko * BPSOFH, BIOFH, C, SQL, PERL +++ http://starix.technonet.net/~syko/ * FreeBSD SysAdmin +++ apocalypse.sykotik.org */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 13 17:05:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA11128 for freebsd-current-outgoing; Mon, 13 Jul 1998 17:05:00 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lucy.bedford.net (lucy.bedford.net [206.99.145.54]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA10909; Mon, 13 Jul 1998 17:04:21 -0700 (PDT) (envelope-from listread@lucy.bedford.net) Received: (from listread@localhost) by lucy.bedford.net (8.8.8/8.8.8) id TAA02118; Mon, 13 Jul 1998 19:38:41 -0400 (EDT) (envelope-from listread) Message-Id: <199807132338.TAA02118@lucy.bedford.net> Subject: Re: Disgruntled Linux User... questions about FreeBSD In-Reply-To: <009501bdae88$70e84f20$6e2f87d0@ws-47-110.selectaswitch.com> from Jeremy Domingue at "Jul 13, 98 11:02:45 am" To: jer@hughes.net (Jeremy Domingue) Date: Mon, 13 Jul 1998 19:38:41 -0400 (EDT) Cc: current@FreeBSD.ORG, stable@FreeBSD.ORG, smp@FreeBSD.ORG, questions@FreeBSD.ORG X-no-archive: yes Reply-to: djv@bedford.net From: CyberPeasant X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jeremy Domingue wrote: [Charset iso-8859-1 unsupported, filtering to ASCII...] > Hey all... > > tale of woe snipped... > Finally, to my questions about FreeBSD: > > 1) First and foremost, I am wondering what issues I will face being a user > very accustomed to linux. I know there will be differences between linux and > FreeBSD, but can anyone outline some of the major ones? Well, BSD is BSD and Linux is SysVish. You will find system startup procedures different. There are different systems calls, and slightly different file system semantics. There are a few conventional differences in where files go. (Mail folders in /var/mail, not /var/spool/mail, man pages in /usr/share/man, not /usr/man... stuff like that). These are all minor things. Ease the transition by using bash as your shell. Applications stay the same, by and large. Sendmail is sendmail, BIND is BIND. X is X. Apache is apache... > 2) Is there a way I can install FreeBSD without losing all of the stuff on > the server right now such as user files, web pages, programs, etc? And > possibly keep linux on there somewhere in case I ever decide to go back? Not a problem. See the webpage www.freebsd.org. Essentially, you need some free primary partition. FreeBSD will read your linux partitions just dandy. (You'll need to build a kernel for this, though, I think). Linux Intel binaries can (with some exceptions) be run efficiently under linux emulation. > 3) Is anyone using SMP on FreeBSD with an Adaptec 7880 on-board SCSI > controller? Linux people keep telling me that this is not a good > configuration for Linux... how about for FreeBSD? I don't know about the SMP aspects, but for single processor use (in my case PPro 200), the 7880 has been the source of no problems. My impression from the list is that this is a "good" SCSI card/chip. Again, how that impacts on SMP, I don't know. > 4) I know that the current build of FreeBSD is listed as development and > should not be used in a mission critical environment, however, what are > people's experiences with it so far? If it seems to be fairly stable, I > would be willing to give it a shot... I really need the SMP support. don't know. Try it single processor with 2.2.6-RELEASE and see if you /really/ need SMP. *BSD* is rumored to work better under load than Linux. ;-) You'll probably want to tweak up a custom kernel, anyway. > 5) Are there any other problems or issues I may face with my hardware > configuration (listed below)? The only problem I see is with the NIC. If it's a 3C905B, there's trouble: not yet supported. Tell the list precisely what kind it is. I don't use a 3Com NIC of any type. Since you're a commercial site, forking out for a different NIC (Intel 100B seems to be the current "fave"), is a minor problem. > I would also be very interested in hearing from other previous (or current) > Linux users' experiences with FreeBSD, and what comments they may have about > the differences and advantages (especially stability-wise) to using FreeBSD > instead of Linux. I had very good stability experiences with Linux (lightly loaded machine, very very vanilla hardware); what drove me from Linux was the continual upgrade/configuration game. It seemed that, just to keep the machine in some semblence of "current" (i.e. bug removal) required a great deal of effort, newsgroup and mailinglist stalking, fussing with various packages/rpms/blah from a thousand places on the 'net. I had installed BSD (Open and Net) on other machines, and noticed that all I did with them was /boot them and use them/, that I just wasn't fussing around so much, that the machines that I could rely on weren't the one I was fooling around with. So I turned all the i86 hardware over to FreeBSD. Yup, no more configuration games. No more wondering which version of ld.so works this week. The BSD's behave much more like a commercial Unix: install, configure, test/checkout, put it into production. Then sit back and read the logs. There are no "distribution" nightmares or libc/glibc version shennanigans. The "distribution" is everything: kernel, source, userland. This may seem unimportant, until you realize how little of /your/ time and thought goes into using it. Slick, in other words. The other Linux misfeature that drove me away was the low quality and disinterest in the improvemnet of such unglamorous things as NFS, the r-commands, some userland security things. Despite the fact that the source code has been free for-- what? 10 years?-- linux still can't seem to read and write a unix filesystem. Why? Well, "ext2fs is superior! Use that! N.I.H.!" I don't think you can run an arbitrary *BSD* binary under Linux, either. "Just recompile it!" > Hardware Configuration: > > Gateway (formerly ALR) NS-7000 Server > Dual PII 266mhz > 512mb EDO ECC SDRAM (all from the same lot, same manufacturer) > Adaptec 7880 on-board SCSI controller > 3Com 10/100 Ethernet Card See above. > 2-4.1gb IBM SCSI hard drives Dave -- Sancho Panza: `Microsoft Windows NT Server is the most secure network operating system available.' Don Quixote: `You are mistaken, Sancho.' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 13 17:56:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA19646 for freebsd-current-outgoing; Mon, 13 Jul 1998 17:56:43 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from geeklab.globalserve.net ([209.90.144.63]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA19619; Mon, 13 Jul 1998 17:56:34 -0700 (PDT) (envelope-from philipp@globalserve.net) Received: from localhost (philipp@localhost) by geeklab.globalserve.net (8.8.8/8.8.7) with SMTP id VAA18012; Mon, 13 Jul 1998 21:17:54 -0400 (EDT) X-Authentication-Warning: geeklab.globalserve.net: philipp owned process doing -bs Date: Mon, 13 Jul 1998 21:17:54 -0400 (EDT) From: Peter Philipp To: Jeremy Domingue cc: current@FreeBSD.ORG, smp@FreeBSD.ORG Subject: Re: Disgruntled Linux User... questions about FreeBSD In-Reply-To: <009501bdae88$70e84f20$6e2f87d0@ws-47-110.selectaswitch.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 13 Jul 1998, Jeremy Domingue wrote: > 3) Is anyone using SMP on FreeBSD with an Adaptec 7880 on-board SCSI > controller? Linux people keep telling me that this is not a good > configuration for Linux... how about for FreeBSD? Where I work we have a dual PII with built in SCSI controller. In my opinion this was a bad buy, but that's the process of "gaining experience" I guess. First off look at what a built in SCSI can do to you... Imagine yourself in a scenario where it's a sunday morning and the built in adapter somehow dies. Not only do you have to replace the motherboard but you'll be looking all over town for a place that sells these dual cpu motherboards. It's much easier to find a place with an external scsi adapter, and you'll be off after replacing it (or if you're smart you'll have a spare scsi card lying around somewhere, and just replace the broken one...would you have a spare motherboard lying around for the price it is?).. I don't think we use the built in scsi on the box at all...it's just too much pain fiddling with it. I'd stay away from it. Hope that helps... Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 13 18:29:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA23607 for freebsd-current-outgoing; Mon, 13 Jul 1998 18:29:37 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from thing.dyn.ml.org (dyn-max8-219.chicago.il.ameritech.net [206.141.211.219] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA23600 for ; Mon, 13 Jul 1998 18:29:32 -0700 (PDT) (envelope-from mcdougall@ameritech.net) Received: from ameritech.net (bsdx [192.168.1.2]) by thing.dyn.ml.org (8.8.8/8.8.7) with ESMTP id VAA01892; Mon, 13 Jul 1998 21:29:25 -0400 (EDT) (envelope-from mcdougall@ameritech.net) Message-ID: <35AAB473.614A964@ameritech.net> Date: Mon, 13 Jul 1998 21:29:23 -0400 From: Adam McDougall Reply-To: mcdougall@ameritech.net X-Mailer: Mozilla 4.05 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: current@FreeBSD.ORG CC: Jeremy Domingue Subject: Re: Disgruntled Linux User... questions about FreeBSD References: <199807132212.RAA02798@symbion.srrc.usda.gov> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Glenn Johnson wrote: > I used Linux for a while so I may be of some help. I must say that I did not > experience problems with Linux of the magnitude that you outlined but I can > say without any hesitation that FreeBSD is better. > > > > > 1) First and foremost, I am wondering what issues I will face being a user > > very accustomed to linux. I know there will be differences between linux and > > FreeBSD, but can anyone outline some of the major ones? > > The first thing you will probably notice is that rather than have a ton of > software packages to choose whether to install or not, the FreeBSD > installation process loads a fairly minimal (relative to RedHat Linux) set of > tools. You then build your system up with the ports/packages that you select. > Also, there is no "default" X configuration. > > The next thing you will notice is that FreeBSD uses csh by default and Linux > uses Bash. Bash is available in the ports but of course needs to be installed > later. > > When it comes to administration, Linux, particularly RedHat uses SYSV > initialazion scripts for each service it starts up. The BSD style is to > basically configure the system with variable initializations in one script, > ie. /etc/rc.conf. Also, there are no runlevels as in Linux, although there are > different security levels and a single user mode. > > > > > 2) Is there a way I can install FreeBSD without losing all of the stuff on > > the server right now such as user files, web pages, programs, etc? And > > possibly keep linux on there somewhere in case I ever decide to go back? > > > > Yes, refer to the installation instructions for partioning your disk. > > > > > 3) Is anyone using SMP on FreeBSD with an Adaptec 7880 on-board SCSI > > controller? Linux people keep telling me that this is not a good > > configuration for Linux... how about for FreeBSD? > > > > Yes, I have 4 such systems running large computational chemistry calculations. > They literally run 24/7 with 100% CPU load. I also have two other systems with > dual PentiumPros. > > > > > 4) I know that the current build of FreeBSD is listed as development and > > should not be used in a mission critical environment, however, what are > > people's experiences with it so far? If it seems to be fairly stable, I > > would be willing to give it a shot... I really need the SMP support. > > > > Well, I consider the jobs that my systems do to be mission critiacal. I have a > total of 6 FreeBSD SMP systems and have never had a crash. The only problem I > have had in the past year and a half with -CURRENT was a few months ago when > NFS was broken for a few weeks. That has since been fixed. I find it necessary > to closely monitor the state of -CURRENT via the mailing lists and commit > e-mails. > > > > > 5) Are there any other problems or issues I may face with my hardware > > configuration (listed below)? > > > > > > Hardware Configuration: > > > > Gateway (formerly ALR) NS-7000 Server > > Dual PII 266mhz > > 512mb EDO ECC SDRAM (all from the same lot, same manufacturer) > > Adaptec 7880 on-board SCSI controller > > 3Com 10/100 Ethernet Card > > 2-4.1gb IBM SCSI hard drives > > The only possible problem you may have is with the Ethernet card. I am > assuming that is one of the so-called vortex cards. If it is a 3C509, you are > OK; if it is a 3C509B, then it will not work. I assume here you mean 905 and 905B respectively. I think the 509 and 509B work, and the 905, but the 905B is not currently supported. But someone IS working on the driver, and I think you may be able to attain a copy of it if you asked the person working on it, find out who by searching the mailing list archives. > I understand that there is a > driver being worked on but I do not know when it will be available. Ethernet > cards are not terribly expensive and most people recommend the Intel > EtherExpress Pro 100+. > > > > > I would also be very interested in hearing from other previous (or current) > > Linux users' experiences with FreeBSD, and what comments they may have about > > the differences and advantages (especially stability-wise) to using FreeBSD > > instead of Linux. > > > > I find the ports/package system of FreeBSD to be much less of a pain than the > package (rpm) system of RedHat. I find it easier to administer FreeBSD as > well, but these types of things are really a matter of taste. By the way, > FreeBSD can run Linux binaries. > > Finally, I do not know much about Linux mailing lists but the FreeBSD mailing > lists are excellent. I try to figure out things as much I can on my own, but > when I have asked a question I get a courteous and accurate response within a > day. I hope this helps. Good luck! > > -- > Glenn Johnson > Technician > USDA, ARS, SRRC > New Orleans, LA > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 13 18:37:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA25292 for freebsd-current-outgoing; Mon, 13 Jul 1998 18:37:59 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA25287 for ; Mon, 13 Jul 1998 18:37:57 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id SAA15931; Mon, 13 Jul 1998 18:37:50 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: Peter Philipp cc: Jeremy Domingue , current@FreeBSD.ORG Subject: Re: Disgruntled Linux User... questions about FreeBSD In-reply-to: Your message of "Mon, 13 Jul 1998 21:17:54 EDT." Date: Mon, 13 Jul 1998 18:37:49 -0700 Message-ID: <15927.900380269@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Where I work we have a dual PII with built in SCSI controller. In my > opinion this was a bad buy, but that's the process of "gaining experience" > I guess. Your comments about the pain of potentially losing an on-board SCSI controller are well taken, but I think perhaps just a bit too shy over the line of "appropriate conservatism" to really support. The fact remains that these types of motherboards have their place, and they have their place for several reasons. First, for many people the PCI slot is a very scarce and valuable resource, each and every slot saved making the difference between either deploying a FreeBSD machine in a certain scenario or having to use some other solution. This is especially true for motherboards like the Intel Providence, which supplies on-board 7880 and Intel Etherexpress Pro 100B - saving 2 full PCI slots. Second, the number of actual failures in the field simply does not support such a level of paranoia - I've seen motherboards fail for all sorts of reasons and have yet to have that reason be an on-board SCSI controller. Even if I did encounter such a scenario, it would hardly be the end of the world - I'd simply disable the thing and stick a 2940 in there until I had a chance to either replace the MB or simply decide to leave things that way. With Intel Providence motherboards now going for $89 (or, with 2 CPUS, for $300) on the street, I can *afford* to lose the on-board SCSI or ethernet. :-) In short, I simply do not agree with your suggestion that such boards should be avoided and the FreeBSD Project would certainly lose several very useful machines if we suddenly adopted that kind of hard-line stance. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 13 19:17:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA00498 for freebsd-current-outgoing; Mon, 13 Jul 1998 19:17:41 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from geeklab.globalserve.net (geeklab.globalserve.net [209.90.144.63]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA00493 for ; Mon, 13 Jul 1998 19:17:38 -0700 (PDT) (envelope-from philipp@globalserve.net) Received: from localhost (philipp@localhost) by geeklab.globalserve.net (8.8.8/8.8.7) with SMTP id WAA11875; Mon, 13 Jul 1998 22:39:46 -0400 (EDT) X-Authentication-Warning: geeklab.globalserve.net: philipp owned process doing -bs Date: Mon, 13 Jul 1998 22:39:46 -0400 (EDT) From: Peter Philipp To: "Jordan K. Hubbard" cc: Jeremy Domingue , current@FreeBSD.ORG Subject: Re: Disgruntled Linux User... questions about FreeBSD In-Reply-To: <15927.900380269@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 13 Jul 1998, Jordan K. Hubbard wrote: > In short, I simply do not agree with your suggestion that such boards > should be avoided and the FreeBSD Project would certainly lose several > very useful machines if we suddenly adopted that kind of hard-line > stance. In time I may change my stance, as support for built-in ethernet/scsi becomes more popular and give a variety of brands to select from. I'm glad that people do disagree with me, because then we would have no effort to improve things as they are developed. I'm certainly glad that you disagree with me jkh, this means that at least some of the FreeBSD project are looking into hardware such as this, and kernel development for the specific hardware. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 13 19:22:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA01193 for freebsd-current-outgoing; Mon, 13 Jul 1998 19:22:38 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from localhost.ziplink.net (mi@kot.ne.mediaone.net [24.128.29.55]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA01185 for ; Mon, 13 Jul 1998 19:22:37 -0700 (PDT) (envelope-from mi@rtfm.ziplink.net) Received: from rtfm.ziplink.net (mi@rtfm [199.232.255.52]) by localhost.ziplink.net (8.8.8/8.8.7) with ESMTP id CAA07571 for ; Tue, 14 Jul 1998 02:22:30 GMT (envelope-from mi@rtfm.ziplink.net) Received: (from mi@localhost) by rtfm.ziplink.net (8.8.8/8.8.5) id WAA26858 for current@freebsd.org; Mon, 13 Jul 1998 22:22:29 -0400 (EDT) From: Mikhail Teterin Message-Id: <199807140222.WAA26858@rtfm.ziplink.net> Subject: xdelta port To: current@FreeBSD.ORG Date: Mon, 13 Jul 1998 22:22:29 -0400 (EDT) X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli" did not build for me on 2 days old current -- missing symbols ___errno and _access in main.o . I rebuilt libgdbm just in case, but that did not help :( Yours, -mi P.S. Is the gcc28 port being fixed to look in /usr/lib/{aout|elf} for things like crt0.o and crt++0.o? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 13 19:38:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA02791 for freebsd-current-outgoing; Mon, 13 Jul 1998 19:38:25 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bandicoot.prth.tensor.pgs.com (bandicoot.prth.tensor.pgs.com [157.147.224.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA02772; Mon, 13 Jul 1998 19:38:20 -0700 (PDT) (envelope-from shocking@ariadne.prth.tensor.pgs.com) Received: from ariadne.tensor.pgs.com (ariadne [157.147.227.36]) by bandicoot.prth.tensor.pgs.com (8.8.8/8.8.8) with SMTP id KAA16747; Tue, 14 Jul 1998 10:37:20 +0800 (WST) Received: from ariadne by ariadne.tensor.pgs.com (SMI-8.6/SMI-SVR4) id KAA10232; Tue, 14 Jul 1998 10:37:46 +0800 Message-Id: <199807140237.KAA10232@ariadne.tensor.pgs.com> X-Mailer: exmh version 2.0.2 2/24/98 To: hackers@FreeBSD.ORG, current@FreeBSD.ORG Subject: How do you tell (within the kernel) if we started setuid? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 14 Jul 1998 10:37:46 +0800 From: Stephen Hocking-Senior Programmer PGS Tensor Perth Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG If you're executing a program that was started setuid root but has subsequently given up its privileges, is there anyway to tell if it was originally set uid? Stephen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 13 19:44:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA03749 for freebsd-current-outgoing; Mon, 13 Jul 1998 19:44:32 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA03656 for ; Mon, 13 Jul 1998 19:43:35 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.8/8.8.7) id MAA10339; Tue, 14 Jul 1998 12:37:07 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199807140237.MAA10339@cimlogic.com.au> Subject: Re: alpha support In-Reply-To: from Dusk Auriel Sykotik at "Jul 13, 98 07:46:05 pm" To: syko@sykotik.org (Dusk Auriel Sykotik) Date: Tue, 14 Jul 1998 12:37:07 +1000 (EST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dusk Auriel Sykotik wrote: > I was wondering if -CURRENT supported the alpha platform, and if not when Not quite. It is still a work in progress - with people actively working on it in what ever spare time they have. > does it expect to be supported? Right now the only options presented to > me for alphas are redhat linux (ugh) and digiunix (too much money). I NetBSD/Alpha supports a wide range of alpha systems (but very few graphics cards). > would prefer to run FreeBSD, since its running on the other server now, > and its run very well for me, and I've really enjoyed working with it. Depending on what you want to do with your system, it is possible to build much of FreeBSD's user land on alpha right now from the same sources as the i386 -current. -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 13 21:37:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA15271 for freebsd-current-outgoing; Mon, 13 Jul 1998 21:37:31 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA15266 for ; Mon, 13 Jul 1998 21:37:29 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.8.8/8.7.3) id WAA00729; Mon, 13 Jul 1998 22:32:07 -0600 (MDT) Date: Mon, 13 Jul 1998 22:32:07 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199807140432.WAA00729@narnia.plutotech.com> To: "Kurt D. Zeilenga" cc: current@FreeBSD.ORG Subject: Re: CAM on a -current branch Newsgroups: pluto.freebsd.current In-Reply-To: <35AA3D71.84F37A20@Boolean.Net> User-Agent: tin/pre-1.4-971204 (UNIX) (FreeBSD/3.0-CURRENT (i386)) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <35AA3D71.84F37A20@Boolean.Net> you wrote: > I've been attempting to construct a decent source combining > -current of mid-May (5/13, 5/19, or 5/20) with CAM source available > via ftp.freebsd.org. Given the problems with build/install world of > mid-May > and not knowing the exact time the CAM source was based upon, it's damn > near impossible. Figure I'll just wait out the next CAM snapshot. I'm open to ideas on this front. The snapshot that was released today is available in diff format and, as soon as my release build completes, as a fully installable release. We could certainly provide a full src tree tar ball too if you think it would be useful. > It appears that more and more folks are now running CAM (namely for > support of newer devices like the AIC-7895 and overall SCSI stability). > I would think it would be wise to check the source into the repository > (on a branch of -current). This should would make life easier for the > testers and users of this fine software. It might even make life > easier for developers (as they would have to rely on folks doing the > merge correctly). Putting the code onto a CVS branch would help the developers very little. We would likely still perform all of our development in our local Perforce repository and only perform branch merges and updates in the CVS repository on the interval of the current snapshots. I'm as antsy as the next guy for getting CAM into the main tree, but I only want to do so once we have the basic functionality in place and aren't changing the code on a daily basis. This should happen before 3.0 and when the appropriate time does come, we will first place the code on a branch, shake it out, then pull it into current. > I'll be running CAM+CCD+Softupdates... hopefully it won't be that > interesting. Softupdates on a reasonably fast disk under CAM seems to wedge machines here. There have been other reports of CCD having similar effects. > Regards, Kurt -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 13 21:46:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA16271 for freebsd-current-outgoing; Mon, 13 Jul 1998 21:46:04 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA16266 for ; Mon, 13 Jul 1998 21:46:01 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.8.8/8.7.3) id WAA01685; Mon, 13 Jul 1998 22:40:37 -0600 (MDT) Date: Mon, 13 Jul 1998 22:40:37 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199807140440.WAA01685@narnia.plutotech.com> To: Ollivier Robert cc: current@FreeBSD.ORG Subject: Re: TESTERS NEEDED: Softupdates looks Very good. User-Agent: tin/pre-1.4-971204 (UNIX) (FreeBSD/3.0-CURRENT (i386)) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> I've run a bunch of make world, make buildworld, make installworld, >> make reinstall, kernel compilations, ports compilations. I installed > > Well, I ran "make world" with yesterday's sources and it succeeded without > a problem during "installworld". Softupdates are now back on all > partitions. > > Thanks to Kirk, Julian and all who made it working ! I'm still leary. I built a successful release here overnight, but noticing a few small bugs, I wanted to run it again. So I decide to test out soft updates to speed up the second build. The machine completely wedged a few hours into the process. It seemed that interrupts still worked (num lock toggled), but having left the machine running X, I couldn't get into the debugger. My guess is some kind of resource shortage/loop at high spl. I will try to reproduce this with a serial console after I get this CAM release out the door. BTW, most of the I/O was going to an LVD Cheetah drive which peaks out at ~19MB/s and ~260 tps, and certain portions of make release will peg this disk. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 13 22:13:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA18923 for freebsd-current-outgoing; Mon, 13 Jul 1998 22:13:48 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from minotaur.com (www.minotaur.com [209.70.17.2]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id WAA18917 for ; Mon, 13 Jul 1998 22:13:45 -0700 (PDT) (envelope-from jon@minotaur.com) Received: (qmail 27096 invoked from network); 14 Jul 1998 05:12:28 -0000 Received: from roaming.minotaur.com (HELO roaming) (209.70.17.100) by www.minotaur.com with SMTP; 14 Jul 1998 05:12:28 -0000 From: "Jon E. Mitchiner" To: "Justin T. Gibbs" , Cc: Subject: RE: 11980712 CAM snapshot now available. Date: Tue, 14 Jul 1998 01:13:21 -0400 Message-ID: <00a201bdaee6$1ea01280$641146d1@roaming.minotaur.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 In-Reply-To: <199807132327.RAA11828@pluto.plutotech.com> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Are there any plans to integrate DPT PM3334UW RAID Controller to the CAM drivers in the near future? I realize most of the driver work was developed by Simon Shapiro, but I was wondering if this would happen anytime in the near future. Thanks! Jon > -----Original Message----- > From: owner-freebsd-current@FreeBSD.ORG > [mailto:owner-freebsd-current@FreeBSD.ORG]On Behalf Of Justin T. Gibbs > Sent: Monday, July 13, 1998 7:22 PM > To: scsi@FreeBSD.ORG > Cc: current@FreeBSD.ORG; stable@FreeBSD.ORG > Subject: 11980712 CAM snapshot now available. > > > Complete information about this snapshot may be obtains from: > > ftp://ftp.FreeBSD.org/pub/FreeBSD/cam/README > > or > > ftp://ftp.kdm.org/pub/FreeBSD/cam/README > > The snapshot is currently available in diff form only, but a full > 3.0SNAP binary release should be available on ftp.FreeBSD.org tonight > or tomorrow morning. A release for 2.2-stable should follow a day > later. > > Changes for the 19980712 Snapshot: > > - Ports collection now includes Tosha, cdrecord, and xmcd 2.3. > > - Added devstat(3) and devstat(9) man page. > > - Some bug fixes to the hard-wiring code. > > - Added preliminary Adaptec 174X driver. > > - Aic7xxx driver improvements: > Attempt to read SEEPROM data in both formats before > failing. This should allow the driver to detect a > SEEPROM on many mother board controllers. > > Correct the setting of the SCSIID for ULTRA2 chips > if we can't find a SEEPROM. > > Fix hang in dataphase on Rev B. aic7880 parts. > > Correct some LVD/Ultra2 bugs. LVD support has now been > tested on a 2940U2W with both Seagate Cheetah and > Quantum Atlas II LVD drives. > > Corrected incorrect sync rate setting for all non-ULTRA2 > adapters for rates other than 20MHz or 10MHz. This was > a bug introduced in the last snapshot. > > Fixed a few error recovery bugs. > > Added support for reading the SEEPROM from aic7850 based > cards like the 2910C. > > - Corrected several bugs in the AdvanSys driver's command > completion and timeout handling code as well as fully convert > it to bus_dma. Thanks to John-Mark Gurney for being a patient > tester. > > - Corrected several bugs in the BusLogic MultiMaster driver's > command completion and timeout handling code. Thanks again to > John-Mark Gurney for being a patient tester. > > - Incorperated a few bug fixes from Stefan Esser for the NCR > driver. Some experimental fixes to the QUEUE FULL handler > are also included. > > - QLogic ISP driver integrated by Matthew Jacob > > - Allow the CD driver to attach to WORM devices. > > - Corrected devstat(9) support in the floppy driver. > > - Added support for "short erase" as "mt erase 0". The > sa driver defaults to a "long erase" as is the behavior > of the st driver it replaces. > > - Be smarter about tape devices that lack a compression > page. Corrects a problem reported by Joey Miller where > the driver refused to access an Archive DDS1 drive. > > - Add support for PC98 geometry conversion based on code provided > by KATO Takenori . > > - Mode page editing features have been incorporated into the > camcontrol utility. > > - libcam now knows how to parse arbitrary command strings just > like the old SCSI library. > > - Use 10byte CDBs for CDROM reads and writes. The spec lists > 6byte CDBs as optional. > > - The XPT layer no longer caches sync rate information. Instead > it asks the SIM driver when it wants it. This should ensure that > mailbox based and cards with similar interfaces don't have to > jump through hoops to provide this information via an async > callback. It should make the information provided by the bt > and isp drivers acurate. > > - Fixed several problems in the CAM_GET_PASSTHROUGH xpt ioctl. > > >From Hans Huebner > - Updated the ch(4) driver and chio(1) command to include volume > tag support. These changes have been tested with a Breeze Hill > Q47 DLT and a DEC DLT2500 media changer. The latter has no > volume tag support. > > - The chio(1) command was updated to include various flags to the > status subcommand. These flags can be used to select additional > information to be displayed (like volume tags). > > - A new chio(1) subcommand named 'voltag' has been added > which allows > for changes to volume tags inside the media changer controller. > This could not be tested as the Q47 does not provide the functio- > nality. > > - The ch(4) manual page was updated to include more information > about the reality of this driver. > > - usr.sbin/rmt/rmt.c has been updated to include the V command, > which is used by SGI's xfsdump to verify the rmt servers version > number. > > -- > Justin T. Gibbs > Kenneth D. Merry > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 13 23:04:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA24721 for freebsd-current-outgoing; Mon, 13 Jul 1998 23:04:03 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from korin.warman.org.pl (korin.nask.waw.pl [148.81.160.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA24451 for ; Mon, 13 Jul 1998 23:01:52 -0700 (PDT) (envelope-from abial@nask.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.8.8/8.8.5) with SMTP id IAA07139; Tue, 14 Jul 1998 08:03:44 +0200 (CEST) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Tue, 14 Jul 1998 08:03:44 +0200 (CEST) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: Chris Csanady cc: Matthew Patton , freebsd-current@FreeBSD.ORG Subject: Re: living without PROCFS In-Reply-To: <199807132227.PAA16266@tarsier.ca.sandia.gov> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 13 Jul 1998, Chris Csanady wrote: > > >Is there any way to eliminate the use of procfs from -current? I > > Well without procfs, you are stuck with groveling through kmem. Kmem is a > terrible interface for this type of thing, as it requires a recompile of > many utilites when the kernel structures change. It is arguable much more > dangerous as well, since it requires access to all of kernel memory. Not necessarily. Most data can be obtained through sysctl(3) - in fact, if I remember correctly, last month someone commited changes to ps and netstat to rely more on that instead of procfs/kmem. And sysctl interface is _way_ cleaner than either procfs or (*shudder*) kvm. As it is now in -current, you can retrieve exactly the same information about processes via sysctl as via procfs (there is still a part being obtained via kvm). Andrzej Bialecki +---------------------+------------------------+--------------------------+ | | When in problem or in | if(halt_per_mth > 0) { | | Research & Academic | doubt, run in circles, | fetch("FreeBSD"); | | Network in Poland | scream and shout. | } | + --------------------+------------------------+--------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 13 23:30:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA26620 for freebsd-current-outgoing; Mon, 13 Jul 1998 23:30:35 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from magnet.geophysik.tu-freiberg.de (magnet.geophysik.tu-freiberg.de [139.20.128.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA26611 for ; Mon, 13 Jul 1998 23:30:31 -0700 (PDT) (envelope-from freebsd@magnet.geophysik.tu-freiberg.de) Received: (from freebsd@localhost) by magnet.geophysik.tu-freiberg.de (8.8.8/8.7.3) id IAA16767 for freebsd-current@freebsd.org; Tue, 14 Jul 1998 08:30:13 +0200 (CEST) From: Holm Tiffe Message-Id: <199807140630.IAA16767@magnet.geophysik.tu-freiberg.de> Subject: CTM - generation stopped ?! To: freebsd-current@FreeBSD.ORG Date: Tue, 14 Jul 1998 08:30:12 +0200 (CEST) X-Mailer: ELM [version 2.4ME+ PL26 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Good morning, what is happening with the generation of ctm - deltas ? The latest cvs-cur delta on ftp.freebsd.org, the cvs-cur.4450.gz is from July 8 1998! Holm -- ******************************************************************************* * Holm Tiffe holm@geophysik.tu-freiberg.de * * Freiberger Strasse 24 * * 09600 Kleinschirma, Germany Microsoft is not the Answer - * * Tel.: 49 3731 74233 Microsoft is the Question, * * UUCP: 49 3731 73719 unicorn!holm and the Answer is no ! * ******************************************************************************* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 14 02:08:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA09607 for freebsd-current-outgoing; Tue, 14 Jul 1998 02:08:53 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from octopus.originative.co.uk (originat.demon.co.uk [158.152.220.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA09597 for ; Tue, 14 Jul 1998 02:08:45 -0700 (PDT) (envelope-from paul@originative.co.uk) Received: by OCTOPUS with Internet Mail Service (5.5.1960.3) id <35Z8GPFZ>; Tue, 14 Jul 1998 10:08:24 +0100 Message-ID: From: Paul Richards To: "'Jordan K. Hubbard'" , Peter Philipp Cc: Jeremy Domingue , current@FreeBSD.ORG Subject: RE: Disgruntled Linux User... questions about FreeBSD Date: Tue, 14 Jul 1998 10:08:22 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.1960.3) Content-Type: text/plain Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: Jordan K. Hubbard [mailto:jkh@time.cdrom.com] > MB or simply decide to leave things that way. With Intel Providence > motherboards now going for $89 (or, with 2 CPUS, for $300) on the > street, I can *afford* to lose the on-board SCSI or ethernet. :-) To back this point up, it's often cheaper to replace a motherboard than it is to replace the SCSI controller (based on the fact that the onboard SCSI is usually adaptec and their kits ain't cheap). If downtime is not your main concern (since replacing a motherboard is going to take longer) then they are a very economical buy. If downtime is your concern then there are more appropriate ways of ensuring your service stays up than going for a motherboard without an onboard controller. Even in this case, a redundant SCSI card only uses up one slot, whereas a redundant card would otherwise use up a second slot. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 14 02:50:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA12854 for freebsd-current-outgoing; Tue, 14 Jul 1998 02:50:12 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from thing.dyn.ml.org (dyn-max8-219.chicago.il.ameritech.net [206.141.211.219] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA12844; Tue, 14 Jul 1998 02:50:06 -0700 (PDT) (envelope-from mcdougall@ameritech.net) Received: from ameritech.net (bsdx [192.168.1.2]) by thing.dyn.ml.org (8.8.8/8.8.7) with ESMTP id FAA06846; Tue, 14 Jul 1998 05:49:56 -0400 (EDT) (envelope-from mcdougall@ameritech.net) Message-ID: <35AB29C1.FFFF01E0@ameritech.net> Date: Tue, 14 Jul 1998 05:49:53 -0400 From: Adam McDougall Reply-To: mcdougall@ameritech.net X-Mailer: Mozilla 4.05 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: current@FreeBSD.ORG CC: julian@FreeBSD.ORG Subject: Re: TESTERS NEEDED: Softupdates looks Very good. References: <199807140440.WAA01685@narnia.plutotech.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a partition solely for the source and ports tree with softupdates enabled (and also /usr since things were going smoothly lately) but while trying to build the XFree86 port on a kernel and system from approx. midnight, it has been hanging the system.I noticed because ther compile stopped doing anything, it just sat there, just like my telnets into the machine. I could switch consoles, and I switched to a console that had been running top, and it was running happily, but I noticed several Zombies as shown by the second line of top. I use top -I so I didnt see what they were, but i assume they were the proccesses that tried to run past the 'hang'. ctrl-alt-del did not work, I had to cold boot the machine. This has happened twice tonight. I have a dpt 2144UW HBA, p233mmx, and was using links to the latest ffs_softdep.c and softdep.h. Is there something useful I could get out of DDB when this happens? I could probably reproduce it. Anything else I could try to help analyze whats wrong? Any more machine-specific info needed? Thanks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 14 03:16:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA15140 for freebsd-current-outgoing; Tue, 14 Jul 1998 03:16:43 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from csns02.comp.polyu.edu.hk (csns02.comp.polyu.edu.hk [158.132.25.95]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA15133 for ; Tue, 14 Jul 1998 03:16:40 -0700 (PDT) (envelope-from c5666305@comp.polyu.edu.hk) Received: from cssolar85.COMP.HKP.HK (cssolar85 [158.132.8.174]) by csns02.comp.polyu.edu.hk (8.8.8/8.8.8) with SMTP id SAA20818 for ; Tue, 14 Jul 1998 18:15:35 +0800 (HKT) Received: (from c5666305@localhost) by cssolar85.COMP.HKP.HK (SMI-8.6/) id SAA23618 for freebsd-current@freebsd.org; Tue, 14 Jul 1998 18:15:35 +0800 Message-Id: <199807141015.SAA23618@cssolar85.COMP.HKP.HK> Subject: how to upgrade ? To: freebsd-current@FreeBSD.ORG Date: Tue, 14 Jul 1998 18:15:35 +0800 (HKT) From: "c5666305" X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I am a newbie to play with 3.0-snap. I had installed 980622 some days ago. I want to upgrade to 980711 (from current.freebsd.org). Can anyone tell me the proper procedures to do it ? Thanks. Clarence CHAN To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 14 03:23:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA15846 for freebsd-current-outgoing; Tue, 14 Jul 1998 03:23:42 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from boco.fee.vutbr.cz (boco.fee.vutbr.cz [147.229.9.11]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA15838 for ; Tue, 14 Jul 1998 03:23:37 -0700 (PDT) (envelope-from cejkar@dcse.fee.vutbr.cz) Received: from kazi.dcse.fee.vutbr.cz (kazi.dcse.fee.vutbr.cz [147.229.9.51]) by boco.fee.vutbr.cz (8.9.1/8.9.1) with ESMTP id MAA11569 for ; Tue, 14 Jul 1998 12:23:25 +0200 (MET DST) Received: (from cejkar@localhost) by kazi.dcse.fee.vutbr.cz (8.8.8/8.8.8) id MAA09803 for freebsd-current@freebsd.org; Tue, 14 Jul 1998 12:23:22 +0200 (CEST) From: Cejka Rudolf Message-Id: <199807141023.MAA09803@kazi.dcse.fee.vutbr.cz> Subject: Re: Is MSDOS FS OK? To: freebsd-current@FreeBSD.ORG (freebsd-current@freebsd.org) Date: Tue, 14 Jul 1998 12:23:22 +0200 (CEST) X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-2 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id DAA15842 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Does anyone have any reports of MSDOSFS stomping on drives? (I am interested i n > the current version, as of today). > I realise there is no guarantee, but I'd like an idea of its danger before I > have a real fiddle with it :) > The partitions I want to use it on are a 499Mb FAT16 partition, and a 2.6Gb > FAT32 partition. > (I have tried it read only and it seems fine..) Yes, I have problems (FreeBSD 3.0-CURRENT #7: Wed May 27 09:58:35 CEST 1998). Line from /etc/fstab: /dev/wd2s1 /dos_d msdos rw 0 0 Line from "ls -l /": drwx------ 1 cejkar wheel 16384 Pro 31 1979 dos_d Example: su cd /dos_d echo A > xxx cp xxx xxx.new mv xxx.new xxx.bad ls -l ... -rwx------ 1 cejkar wheel 2 Èvc 14 12:10 xxx -rwx------ 1 cejkar wheel 2 Èvc 14 12:10 xxx.bad ... # Ok - it is good still rm xxx xxx.bad echo A > xxx cp xxx xxx.new ls -l ... -rwx------ 1 cejkar wheel 2 Èvc 14 12:14 XXX.BAD -rwx------ 1 cejkar wheel 2 Èvc 14 12:14 xxx ... # Hmm, there _should_ be "xxx" and "xxx.new", am I right? Is this example sufficient? Is this widely repeatible? (I have installed Win95 & FreeBSD-CURRENT in my box.) -------------------------------------------------------------------------- Rudolf Cejka (cejkar@dcse.fee.vutbr.cz; http://www.fee.vutbr.cz/~cejkar) Technical University of Brno, Faculty of El. Engineering and Comp. Science Bozetechova 2, 612 66 Brno, Czech Republic To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 14 03:59:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA18925 for freebsd-current-outgoing; Tue, 14 Jul 1998 03:59:20 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA18912 for ; Tue, 14 Jul 1998 03:59:15 -0700 (PDT) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.0/frmug-2.3/nospam) with UUCP id MAA19476 for freebsd-current@FreeBSD.ORG; Tue, 14 Jul 1998 12:59:07 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: (from roberto@localhost) by keltia.freenix.fr (8.9.0.Beta4/keltia-2.14/nospam) id MAA05685 for freebsd-current@FreeBSD.ORG; Tue, 14 Jul 1998 12:29:28 +0200 (CEST) (envelope-from roberto) Message-ID: <19980714122927.A5650@keltia.freenix.fr> Date: Tue, 14 Jul 1998 12:29:27 +0200 From: Ollivier Robert To: freebsd-current@FreeBSD.ORG Subject: Re: CTM - generation stopped ?! Mail-Followup-To: freebsd-current@FreeBSD.ORG References: <199807140630.IAA16767@magnet.geophysik.tu-freiberg.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93i In-Reply-To: <199807140630.IAA16767@magnet.geophysik.tu-freiberg.de>; from Holm Tiffe on Tue, Jul 14, 1998 at 08:30:12AM +0200 X-Operating-System: FreeBSD 3.0-CURRENT ctm#4462 AMD-K6 MMX @ 225 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Holm Tiffe: > what is happening with the generation of ctm - deltas ? > The latest cvs-cur delta on ftp.freebsd.org, > the cvs-cur.4450.gz is from July 8 1998! Use if it is not too far from you. It is very up-to-date. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #61: Sun Jul 12 14:38:23 CEST 1998 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 14 04:15:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA22672 for freebsd-current-outgoing; Tue, 14 Jul 1998 04:15:24 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from relay1.aha.ru (relay1.aha.ru [195.2.83.105]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA22649 for ; Tue, 14 Jul 1998 04:15:13 -0700 (PDT) (envelope-from osa@serv.etrust.ru) Received: from sunny.aha.ru (sunny.aha.ru [195.2.83.112]) by relay1.aha.ru (8.9.1/aha-r/0.04B) with ESMTP id PAA12584; Tue, 14 Jul 1998 15:13:42 +0400 (MSD) Received: by sunny.aha.ru id PAA15630; (8.8.8/vak/1.9) Tue, 14 Jul 1998 15:12:45 +0400 (MSD) Received: from unknown(195.2.84.114) by sunny.aha.ru via smap (V1.3) id sma015435; Tue Jul 14 15:12:09 1998 Received: from localhost by serv.etrust.ru with SMTP id PAA09226; (8.9.0/vak/1.9) Tue, 14 Jul 1998 15:15:14 +0400 (MSD) Date: Tue, 14 Jul 1998 15:15:14 +0400 (MSD) From: =?KOI8-R?B?88XSx8XKIO/Tz8vJzg==?= To: c5666305 cc: freebsd-current@FreeBSD.ORG Subject: Re: how to upgrade ? In-Reply-To: <199807141015.SAA23618@cssolar85.COMP.HKP.HK> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 14 Jul 1998, c5666305 wrote: > Hello, > > I am a newbie to play with 3.0-snap. I had installed 980622 some days ago. > I want to upgrade to 980711 (from current.freebsd.org). Can anyone tell me > the proper procedures to do it ? Thanks. > > Clarence CHAN > Install cvsup for update sources & then recompile system Rgdz, oZZ, osa@etrust.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 14 06:57:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA05586 for freebsd-current-outgoing; Tue, 14 Jul 1998 06:57:05 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from donny.ida.net (mail.ida.net [204.228.203.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA05567 for ; Tue, 14 Jul 1998 06:56:57 -0700 (PDT) (envelope-from muck@ida.net) Received: from falcon.hinterlands.com (tc-pt1-43.ida.net [208.141.181.52]) by donny.ida.net (8.8.7/8.8.7) with SMTP id HAA17800; Tue, 14 Jul 1998 07:57:03 -0600 (MDT) Date: Tue, 14 Jul 1998 07:57:06 -0600 (MDT) From: Mike X-Sender: muck@falcon.hinterlands.com To: c5666305 cc: freebsd-current@FreeBSD.ORG Subject: Re: how to upgrade ? In-Reply-To: <199807141015.SAA23618@cssolar85.COMP.HKP.HK> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 14 Jul 1998, c5666305 wrote: > Hello, > > I am a newbie to play with 3.0-snap. I had installed 980622 some days ago. > I want to upgrade to 980711 (from current.freebsd.org). Can anyone tell me > the proper procedures to do it ? Thanks. > > Clarence CHAN > You would probably want to use cvsup. Go to /usr/ports/net/cvsup and type "make install". If you don't know how to generate a /etc/cvsupfile, type "pkg_add ftp://ftp.freebsd.org/pub/FreeBSD/CVSup/cvsupit.tgz". This will make a /etc/cvsupfile for you and run CVS for you. Then, later, you can type "/usr/local/bin/cvsup -g -L 2 /etc/cvsupfile" to update your system. After you do a cvsup, go to /usr/src and type "make world". You must be superuser to do both a make world and a cvsup. Alternately, you can spit the building and installing up with "make buildworld" and then "make installworld". After the new system is installed, go to /usr/src/sys/i386/conf. Type "config MYKERNEL" or "config GENERIC" if you haven't built a custom kernel. Then, goto ../../compile/MYKERNEL. Type "make depend", then "make", then "make install". You might also have to update /etc/. There is a good tutorial in the handbook about upgrading FreeBSD from source using Make World. You should read it. After installing your new kernel, reboot the system. To confirm that you upgraded, after the system is up, type "uname -a" Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 14 07:32:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA10243 for freebsd-current-outgoing; Tue, 14 Jul 1998 07:32:42 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bright.ny.otec.com (bright.ny.otec.com [209.3.16.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA10229 for ; Tue, 14 Jul 1998 07:32:38 -0700 (PDT) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.ny.otec.com (8.8.8/8.8.8) with SMTP id KAA07341; Tue, 14 Jul 1998 10:32:43 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.ny.otec.com: bright owned process doing -bs Date: Tue, 14 Jul 1998 10:32:43 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.ny.otec.com To: c5666305 cc: freebsd-current@FreeBSD.ORG Subject: Re: how to upgrade ? In-Reply-To: <199807141015.SAA23618@cssolar85.COMP.HKP.HK> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG http://www.cs.sunyit.edu/~perlsta -> freebsd -> upgrading -Alfred On Tue, 14 Jul 1998, c5666305 wrote: > Hello, > > I am a newbie to play with 3.0-snap. I had installed 980622 some days ago. > I want to upgrade to 980711 (from current.freebsd.org). Can anyone tell me > the proper procedures to do it ? Thanks. > > Clarence CHAN > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 14 08:12:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA16476 for freebsd-current-outgoing; Tue, 14 Jul 1998 08:12:32 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA16439; Tue, 14 Jul 1998 08:12:25 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id IAA18210; Tue, 14 Jul 1998 08:11:51 -0700 (PDT) Message-Id: <199807141511.IAA18210@implode.root.com> To: Brandon Lockhart cc: Jeremy Domingue , current@FreeBSD.ORG, stable@FreeBSD.ORG, questions@FreeBSD.ORG Subject: Re: Disgruntled Linux User... questions about FreeBSD In-reply-to: Your message of "Mon, 13 Jul 1998 19:14:16 EDT." From: David Greenman Reply-To: dg@root.com Date: Tue, 14 Jul 1998 08:11:50 -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >First of all, I do not recommend Gateway 2k for server's. Get a COMPAQ or >HP or SUN. RISC is the way to go. It's a good thing that we (the FreeBSD developers) don't believe this else several of the largest servers on the Internet wouldn't be running FreeBSD. ...but of course we think otherwise. FreeBSD makes an excellent server platform and most PCs, despite their warts, work just fine in this application. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 14 08:31:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA19308 for freebsd-current-outgoing; Tue, 14 Jul 1998 08:31:39 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA19300 for ; Tue, 14 Jul 1998 08:31:35 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.8.8/8.8.8) id LAA14435; Tue, 14 Jul 1998 11:31:21 -0400 (EDT) (envelope-from wollman) Date: Tue, 14 Jul 1998 11:31:21 -0400 (EDT) From: Garrett Wollman Message-Id: <199807141531.LAA14435@khavrinen.lcs.mit.edu> To: "Jordan K. Hubbard" Cc: Peter Philipp , Jeremy Domingue , current@FreeBSD.ORG Subject: Re: Disgruntled Linux User... questions about FreeBSD In-Reply-To: <15927.900380269@time.cdrom.com> References: <15927.900380269@time.cdrom.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > certain scenario or having to use some other solution. This is > especially true for motherboards like the Intel Providence, which > supplies on-board 7880 and Intel Etherexpress Pro 100B - saving 2 full > PCI slots. And similarly, we've been really happy with our Intel Buckeye motherboards -- the only problems that we've had came from the VAR who put them together (and the UPS drivers who dropped them en route from Arizona). Never had one of the SCSI controllers fail, nor the hot-swap backplane. (Just wish those Seacrate WC disks weren't so much more expensive than standard Ws...) The last lot of servers we bought were Intel Balboas with the on-board Adaptec plus an add-in 2940 to drive a second SCSI bus. > In short, I simply do not agree with your suggestion that such boards > should be avoided and the FreeBSD Project would certainly lose several > very useful machines if we suddenly adopted that kind of hard-line > stance. Thankfully, PC hardware in this case being actually reasonable for a change, we couldn't do this even if we wanted to. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 14 09:18:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA25412 for freebsd-current-outgoing; Tue, 14 Jul 1998 09:18:34 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from news1.gtn.com (news1.gtn.com [194.77.0.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA25399 for ; Tue, 14 Jul 1998 09:18:25 -0700 (PDT) (envelope-from andreas@klemm.gtn.com) Received: (from uucp@localhost) by news1.gtn.com (8.8.6/8.8.6) with UUCP id SAA11843; Tue, 14 Jul 1998 18:15:24 +0200 (MET DST) Received: (from andreas@localhost) by klemm.gtn.com (8.8.8/8.8.8) id RAA07205; Tue, 14 Jul 1998 17:33:15 +0200 (CEST) (envelope-from andreas) Message-ID: <19980714173314.A2988@klemm.gtn.com> Date: Tue, 14 Jul 1998 17:33:14 +0200 From: Andreas Klemm To: "Justin T. Gibbs" , "Kurt D. Zeilenga" Cc: current@FreeBSD.ORG Subject: Re: CAM on a -current branch References: <35AA3D71.84F37A20@Boolean.Net> <199807140432.WAA00729@narnia.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199807140432.WAA00729@narnia.plutotech.com>; from Justin T. Gibbs on Mon, Jul 13, 1998 at 10:32:07PM -0600 X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 3.0-CURRENT SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jul 13, 1998 at 10:32:07PM -0600, Justin T. Gibbs wrote: > > Softupdates on a reasonably fast disk under CAM seems to wedge machines > here. There have been other reports of CCD having similar effects. Huh, 'though I don't have very fast disks I should perhaps stay away from using CAM ? I'm using ccd and softupdates ... How unstable is it would you say ? I can't remember reports concerning this ... -- Andreas Klemm http://www.FreeBSD.ORG/~andreas What gives you 90% more speed, for example, in kernel compilation ? http://www.FreeBSD.ORG/~fsmp/SMP/akgraph-a/graph1.html "NT = Not Today" (Maggie Biggs) ``powered by FreeBSD SMP'' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 14 09:29:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA27413 for freebsd-current-outgoing; Tue, 14 Jul 1998 09:29:40 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mx1.home.com (mx1.home.com [24.0.0.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA27407 for ; Tue, 14 Jul 1998 09:29:38 -0700 (PDT) (envelope-from nellie@home.com) Received: from cc219337-a.lwmrn1.pa.home.com (cc219337-a.lwmrn1.pa.home.com [24.3.111.2]) by mx1.home.com (8.8.5/8.8.5-AtHome) with SMTP id JAA14232 for ; Tue, 14 Jul 1998 09:29:25 -0700 (PDT) Date: Tue, 14 Jul 1998 12:25:05 -0400 (EDT) From: Wu-Tang Forever X-Sender: nellie@cc219337-a.lwmrn1.pa.home.com To: current@FreeBSD.ORG Subject: -current & Makefile Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I cvsupped using the example file in /usr/src/share/examples/cvsup/standard-supfile, tried to make world in /usr/src but the makefile is borked, needs an operators is easy to fix but I got errors if if-less endif and something else, how to fix? Progress takes away what forever took to find -dmb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 14 09:40:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA29770 for freebsd-current-outgoing; Tue, 14 Jul 1998 09:40:21 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from symbion.srrc.usda.gov ([199.78.118.118]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA29763 for ; Tue, 14 Jul 1998 09:40:07 -0700 (PDT) (envelope-from glenn@nola.srrc.usda.gov) Received: from nola.srrc.usda.gov (localhost.srrc.usda.gov [127.0.0.1]) by symbion.srrc.usda.gov (8.8.8/8.8.8) with ESMTP id LAA05974; Tue, 14 Jul 1998 11:39:30 -0500 (CDT) (envelope-from glenn@nola.srrc.usda.gov) Message-Id: <199807141639.LAA05974@symbion.srrc.usda.gov> X-Mailer: exmh version 2.0.2 2/24/98 To: mcdougall@ameritech.net cc: current@FreeBSD.ORG, Jeremy Domingue From: Glenn Johnson Subject: Re: Disgruntled Linux User... questions about FreeBSD In-reply-to: Your message of "Mon, 13 Jul 1998 21:29:23 EDT." <35AAB473.614A964@ameritech.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 14 Jul 1998 11:39:29 -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Glenn Johnson wrote: > >>> >>> 5) Are there any other problems or issues I may face with my hardware >>> configuration (listed below)? >>> >>> >>> Hardware Configuration: >>> >>> Gateway (formerly ALR) NS-7000 Server >>> Dual PII 266mhz >>> 512mb EDO ECC SDRAM (all from the same lot, same manufacturer) >>> Adaptec 7880 on-board SCSI controller >>> 3Com 10/100 Ethernet Card >>> 2-4.1gb IBM SCSI hard drives >> >> The only possible problem you may have is with the Ethernet card. I am >> assuming that is one of the so-called vortex cards. If it is a 3C509, you are >> OK; if it is a 3C509B, then it will not work. > ...and Adam McDougall replied: > I assume here you mean 905 and 905B respectively. Indeed, I did mean the 905 and 905B. We have a ton of 509 cards where I work so somehow that was imprinted in my mind. The 509 cards do work OK, but I was trying to refer to the 905 series. Sorry for the dyslexic misinformation and thanks for the correction. -- Glenn Johnson Technician USDA, ARS, SRRC New Orleans, LA To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 14 09:47:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA01257 for freebsd-current-outgoing; Tue, 14 Jul 1998 09:47:05 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pluto.plutotech.com (mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA01252 for ; Tue, 14 Jul 1998 09:47:02 -0700 (PDT) (envelope-from gibbs@plutotech.com) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.8.7/8.8.5) with ESMTP id KAA29678; Tue, 14 Jul 1998 10:46:51 -0600 (MDT) Message-Id: <199807141646.KAA29678@pluto.plutotech.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Andreas Klemm cc: "Justin T. Gibbs" , "Kurt D. Zeilenga" , current@FreeBSD.ORG Subject: Re: CAM on a -current branch In-reply-to: Your message of "Tue, 14 Jul 1998 17:33:14 +0200." <19980714173314.A2988@klemm.gtn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 14 Jul 1998 10:41:39 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >On Mon, Jul 13, 1998 at 10:32:07PM -0600, Justin T. Gibbs wrote: >> >> Softupdates on a reasonably fast disk under CAM seems to wedge machines >> here. There have been other reports of CCD having similar effects. > >Huh, 'though I don't have very fast disks I should perhaps stay away >from using CAM ? I'm using ccd and softupdates ... I think that CAM simply exacerbates a problem that already exists with soft updates. It is not the root of the problem. >How unstable is it would you say ? I can't remember reports concerning >this ... I cannot build a release on a partition with soft updates enabled. This is "unstable enough" for me to not use soft updates. >-- >Andreas Klemm http://www.FreeBSD.ORG/~andreas > What gives you 90% more speed, for example, in kernel compilation ? > http://www.FreeBSD.ORG/~fsmp/SMP/akgraph-a/graph1.html > "NT = Not Today" (Maggie Biggs) ``powered by FreeBSD SMP'' -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 14 10:07:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA04264 for freebsd-current-outgoing; Tue, 14 Jul 1998 10:07:19 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from peloton.physics.montana.edu (peloton.physics.montana.edu [153.90.192.177]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA04249 for ; Tue, 14 Jul 1998 10:07:17 -0700 (PDT) (envelope-from brett@peloton.physics.montana.edu) Received: from localhost (brett@localhost) by peloton.physics.montana.edu (8.8.8/8.8.7) with SMTP id LAA03823; Tue, 14 Jul 1998 11:06:47 -0600 (MDT) (envelope-from brett@peloton.physics.montana.edu) Date: Tue, 14 Jul 1998 11:06:47 -0600 (MDT) From: Brett Taylor To: Mikhail Teterin cc: current@FreeBSD.ORG Subject: Re: xdelta port In-Reply-To: <199807140222.WAA26858@rtfm.ziplink.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, > did not build for me on 2 days old current -- missing symbols > ___errno and _access in main.o . I rebuilt libgdbm just in case, > but that did not help :( Yours, This has been known for awhile and is the reason it was removed as a dependency from the Gimp port. I'm not running -current so not sure what the problem is - maybe ask the maintainer: MAINTAINER= jmacd@FreeBSD.ORG Brett *********************************************************** Brett Taylor brett@peloton.physics.montana.edu http://peloton.physics.montana.edu/brett/ How many Microsoft employees does it take to change a light bulb? Zero. They declared Darkness[tm] the standard. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 14 10:08:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA04571 for freebsd-current-outgoing; Tue, 14 Jul 1998 10:08:21 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from opus.cts.cwu.edu (skynyrd@opus.cts.cwu.edu [198.104.92.71]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA04547 for ; Tue, 14 Jul 1998 10:08:18 -0700 (PDT) (envelope-from skynyrd@opus.cts.cwu.edu) Received: from localhost (skynyrd@localhost) by opus.cts.cwu.edu (8.8.8/8.8.8) with SMTP id KAA25376; Tue, 14 Jul 1998 10:07:53 -0700 (PDT) (envelope-from skynyrd@opus.cts.cwu.edu) Date: Tue, 14 Jul 1998 10:07:53 -0700 (PDT) From: Chris Timmons To: Brandon Lockhart cc: Jeremy Domingue , current@FreeBSD.ORG Subject: Re: Disgruntled Linux User... questions about FreeBSD In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG We have more than 20 genuine Compaq file servers with genuine Compaq memory and Compaq blessed disks with Compaq firmware. Also Suns, DECalpha, and a pile of server class FreeBSD machines. In practice, the generic pentium and pentium pro based hardware has been at least as reliable as the Compaq stuff. Sun has been equally reliable. The occasional disk failure, even a memory module going bad from time to time. The biggest liability with PC hardware is buying a solid power supply and a case which supplies adequate cooling. Use quality SCSI disks, and in my experience, once you do these things - there is no reliability gap between a "PC" parts machine and Compaq or the usual RISC workstations. -Chris On Mon, 13 Jul 1998, Brandon Lockhart wrote: > First of all, I do not recommend Gateway 2k for server's. Get a COMPAQ or > HP or SUN. RISC is the way to go. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 14 11:01:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA11295 for freebsd-current-outgoing; Tue, 14 Jul 1998 11:01:05 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ifi.uio.no (0@ifi.uio.no [129.240.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA11288 for ; Tue, 14 Jul 1998 11:01:03 -0700 (PDT) (envelope-from dag-erli@ifi.uio.no) Received: from hrotti.ifi.uio.no (2602@hrotti.ifi.uio.no [129.240.64.15]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id UAA29664; Tue, 14 Jul 1998 20:00:48 +0200 (MET DST) Received: (from dag-erli@localhost) by hrotti.ifi.uio.no ; Tue, 14 Jul 1998 20:00:47 +0200 (MET DST) Mime-Version: 1.0 To: Ollivier Robert Cc: current@FreeBSD.ORG Subject: Re: TESTERS NEEDED: Softupdates looks Very good. References: <35A52E6B.6201DD56@whistle.com> <19980710235529.A6695@keltia.freenix.fr> Organization: University of Oslo, Department of Informatics X-url: http://www.stud.ifi.uio.no/~dag-erli/ X-other-addresses: 'finger dag-erli@ifi.uio.no' for a list X-disclaimer-1: The views expressed in this article are mine alone, and do X-disclaimer-2: not necessarily coincide with those of any organisation or X-disclaimer-3: company with which am or have been affiliated. X-Stop-Spam: http://www.cauce.org/ From: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= ) Date: 14 Jul 1998 20:00:46 +0200 In-Reply-To: dag-erli@ifi.uio.no's message of "13 Jul 1998 19:36:48 +0200" Message-ID: Lines: 13 X-Mailer: Gnus v5.5/Emacs 19.34 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id LAA11290 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG dag-erli@ifi.uio.no (Dag-Erling Coidan Smørgrav ) writes: > I *am* having trouble with that box, but I don't think it fs related. > It's very weird though; the main problem is that init(8) just stops > cold after running /etc/rc. It never starts getty(8). I tried adding > [...] Boys and girls, never ever *ever* accidentally leave out "lo0" from network_interfaces in /etc/rc.conf. Particularly on a NIS client. Auto-lart deluxe. DES -- One two, one two, one two. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 14 11:02:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA11753 for freebsd-current-outgoing; Tue, 14 Jul 1998 11:02:30 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pop02.globecomm.net (pop02.globecomm.net [207.51.48.186]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA11728; Tue, 14 Jul 1998 11:02:27 -0700 (PDT) (envelope-from mbriggs@switchboard.net) Received: from switchboard.net (gw2.iridium.com [208.226.76.6]) by pop02.globecomm.net (8.8.8/8.8.0) with ESMTP id OAA14714; Tue, 14 Jul 1998 14:02:12 -0400 (EDT) Message-ID: <35AB9D1B.E62A84C2@switchboard.net> Date: Tue, 14 Jul 1998 14:02:03 -0400 From: "Matthew R. Briggs" X-Mailer: Mozilla 4.04 [en] (Win95; I) MIME-Version: 1.0 To: Dusk Auriel Sykotik CC: current@FreeBSD.ORG, freebsd-alpha@FreeBSD.ORG Subject: Re: alpha support References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [forwarded to freebsd-alpha as well as current] Dusk Auriel Sykotik wrote: > > I was wondering if -CURRENT supported the alpha platform, and if not when > does it expect to be supported? Right now the only options presented to > me for alphas are redhat linux (ugh) and digiunix (too much money). I > would prefer to run FreeBSD, since its running on the other server now, > and its run very well for me, and I've really enjoyed working with it. > Thanks. > > /* > * Matt Harris +++ Syko > * BPSOFH, BIOFH, C, SQL, PERL +++ http://starix.technonet.net/~syko/ > * FreeBSD SysAdmin +++ apocalypse.sykotik.org > */ > Hello, I'd be interested to know this as well. I just bought an AS200 from Onsale, and finally got OpenBSD running on it after fighting with Debian Linux for three days (I hate the ARC console...arrgh). I like FreeBSD better, though. How is the port coming along, and what can be done to help? Matt Briggs mbriggs@switchboard.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 14 11:06:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA12488 for freebsd-current-outgoing; Tue, 14 Jul 1998 11:06:09 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from news1.gtn.com (news1.gtn.com [194.77.0.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA12402 for ; Tue, 14 Jul 1998 11:06:02 -0700 (PDT) (envelope-from andreas@klemm.gtn.com) Received: (from uucp@localhost) by news1.gtn.com (8.8.6/8.8.6) with UUCP id UAA17410; Tue, 14 Jul 1998 20:00:11 +0200 (MET DST) Received: (from andreas@localhost) by klemm.gtn.com (8.8.8/8.8.8) id TAA03592; Tue, 14 Jul 1998 19:02:57 +0200 (CEST) (envelope-from andreas) Message-ID: <19980714190256.A3474@klemm.gtn.com> Date: Tue, 14 Jul 1998 19:02:56 +0200 From: Andreas Klemm To: "Justin T. Gibbs" Cc: "Kurt D. Zeilenga" , current@FreeBSD.ORG Subject: Re: CAM on a -current branch References: <19980714173314.A2988@klemm.gtn.com> <199807141646.KAA29678@pluto.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199807141646.KAA29678@pluto.plutotech.com>; from Justin T. Gibbs on Tue, Jul 14, 1998 at 10:41:39AM -0600 X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 3.0-CURRENT SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jul 14, 1998 at 10:41:39AM -0600, Justin T. Gibbs wrote: > > >How unstable is it would you say ? I can't remember reports concerning > >this ... > > I cannot build a release on a partition with soft updates enabled. This > is "unstable enough" for me to not use soft updates. What happens then ??? Kernel panic ? -- Andreas Klemm http://www.FreeBSD.ORG/~andreas What gives you 90% more speed, for example, in kernel compilation ? http://www.FreeBSD.ORG/~fsmp/SMP/akgraph-a/graph1.html "NT = Not Today" (Maggie Biggs) ``powered by FreeBSD SMP'' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 14 11:13:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA13635 for freebsd-current-outgoing; Tue, 14 Jul 1998 11:13:17 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from echonyc.com (echonyc.com [198.67.15.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA13616 for ; Tue, 14 Jul 1998 11:13:13 -0700 (PDT) (envelope-from benedict@echonyc.com) Received: from localhost (benedict@localhost) by echonyc.com (8.8.7/8.8.7) with SMTP id OAA07981 for ; Tue, 14 Jul 1998 14:13:05 -0400 (EDT) Date: Tue, 14 Jul 1998 14:13:05 -0400 (EDT) From: Snob Art Genre Reply-To: ben@rosengart.com To: current@FreeBSD.ORG Subject: MAKE_KERBEROS4 and OBJLINK incompatible Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I can build world fine (with today's sources) with either MAKE_KERBEROS4 or OBJLINK defined in /etc/make.conf, but with both, the build dies here: test -e /usr/src/kerberosIV/lib/libkadm/obj/../../lib/libkadm/kadm_err.et || ln -s /usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kadm/kadm_err.et /usr/src/kerberosIV/lib/libkadm/obj/../../lib/libkadm cd /usr/src/kerberosIV/lib/libkadm/obj/../../lib/libkadm; compile_et kadm_err.et cd: can't cd to /usr/src/kerberosIV/lib/libkadm/obj/../../lib/libkadm *** Error code 2 I've actually had this problem for quite some time, now that I think about it. Ben "You have your mind on computers, it seems." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 14 11:13:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA13709 for freebsd-current-outgoing; Tue, 14 Jul 1998 11:13:29 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from merlin.camalott.com (root@merlin.camalott.com [208.229.74.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA13683 for ; Tue, 14 Jul 1998 11:13:23 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-123.camalott.com [208.229.74.123]) by merlin.camalott.com (8.8.7/8.8.7) with ESMTP id NAA14771; Tue, 14 Jul 1998 13:10:50 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.8.8/8.8.8) id NAA00458; Tue, 14 Jul 1998 13:09:23 -0500 (CDT) (envelope-from joelh) Date: Tue, 14 Jul 1998 13:09:23 -0500 (CDT) Message-Id: <199807141809.NAA00458@detlev.UUCP> To: paul@originative.co.uk CC: jkh@time.cdrom.com, philipp@globalserve.net, jer@hughes.net, current@FreeBSD.ORG In-reply-to: (message from Paul Richards on Tue, 14 Jul 1998 10:08:22 +0100) Subject: Re: Disgruntled Linux User... questions about FreeBSD From: Joel Ray Holveck Reply-to: joelh@gnu.org References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Even in this case, a redundant SCSI card only uses up one slot, > whereas a redundant card would otherwise use up a second slot. Can FreeBSD handle a redundant SCSI card? Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 14 11:29:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA17076 for freebsd-current-outgoing; Tue, 14 Jul 1998 11:29:35 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from echonyc.com (echonyc.com [198.67.15.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA17067 for ; Tue, 14 Jul 1998 11:29:32 -0700 (PDT) (envelope-from benedict@echonyc.com) Received: from localhost (benedict@localhost) by echonyc.com (8.8.7/8.8.7) with SMTP id OAA12285; Tue, 14 Jul 1998 14:29:21 -0400 (EDT) Date: Tue, 14 Jul 1998 14:29:20 -0400 (EDT) From: Snob Art Genre Reply-To: ben@rosengart.com To: Wu-Tang Forever cc: current@FreeBSD.ORG Subject: Re: -current & Makefile In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG cd /usr/src make -m /usr/src/share/mk world thanks to John Birrell On Tue, 14 Jul 1998, Wu-Tang Forever wrote: > I cvsupped using the example file in > /usr/src/share/examples/cvsup/standard-supfile, tried to make world in > /usr/src but the makefile is borked, needs an operators is easy to fix but > I got errors if if-less endif and something else, how to fix? > > Progress takes away what forever took to find -dmb > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Ben "You have your mind on computers, it seems." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 14 11:49:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA21100 for freebsd-current-outgoing; Tue, 14 Jul 1998 11:49:46 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pluto.plutotech.com (mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA21095 for ; Tue, 14 Jul 1998 11:49:44 -0700 (PDT) (envelope-from gibbs@plutotech.com) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.8.7/8.8.5) with ESMTP id MAA05620; Tue, 14 Jul 1998 12:49:27 -0600 (MDT) Message-Id: <199807141849.MAA05620@pluto.plutotech.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Andreas Klemm cc: "Justin T. Gibbs" , "Kurt D. Zeilenga" , current@FreeBSD.ORG Subject: Re: CAM on a -current branch In-reply-to: Your message of "Tue, 14 Jul 1998 19:02:56 +0200." <19980714190256.A3474@klemm.gtn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 14 Jul 1998 12:44:15 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> I cannot build a release on a partition with soft updates enabled. This >> is "unstable enough" for me to not use soft updates. > >What happens then ??? Kernel panic ? I believe so. My machine was in X at the time, but I will attempt to reproduce the problem with a serial console once I get the 2.2CAM snapshot release build completed. >-- >Andreas Klemm http://www.FreeBSD.ORG/~andreas > What gives you 90% more speed, for example, in kernel compilation ? > http://www.FreeBSD.ORG/~fsmp/SMP/akgraph-a/graph1.html > "NT = Not Today" (Maggie Biggs) ``powered by FreeBSD SMP'' -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 14 12:12:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA26263 for freebsd-current-outgoing; Tue, 14 Jul 1998 12:12:54 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pop01.globecomm.net (pop01.globecomm.net [207.51.48.185]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA26256 for ; Tue, 14 Jul 1998 12:12:51 -0700 (PDT) (envelope-from mbriggs@switchboard.net) Received: from switchboard.net (gw2.iridium.com [208.226.76.6]) by pop01.globecomm.net (8.8.8/8.8.0) with ESMTP id PAA25352 for ; Tue, 14 Jul 1998 15:12:41 -0400 (EDT) Message-ID: <35ABADA7.C111A65C@switchboard.net> Date: Tue, 14 Jul 1998 15:12:39 -0400 From: "Matthew R. Briggs" X-Mailer: Mozilla 4.04 [en] (Win95; I) MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG Subject: MAXUSERS kernel compile problem Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, A kernel compile has been doing this to me for the past two days (despite repeated cvsups). It happens on my custom config file as well as LINT: __________ cc -c -O -pipe -Wreturn-type -Wcomment -Wredundant-decls -W implicit -Wnested-externs -Wstrict-prototypes -Wmissing-pr ototypes -Wpointer-arith -Winline -Wuninitialized -ansi -g -nostdinc -I- -I. -I../.. -I../../../include -DKERNEL -in clude opt_global.h param.c param.c:76: `MAXUSERS' undeclared here (not in a function) param.c:76: initializer element is not constant param.c:77: `MAXUSERS' undeclared here (not in a function) param.c:77: initializer element is not constant param.c:78: `MAXUSERS' undeclared here (not in a function) param.c:78: initializer element is not constant param.c:79: `MAXUSERS' undeclared here (not in a function) param.c:79: initializer element is not constant param.c:80: `MAXUSERS' undeclared here (not in a function) param.c:80: `MAXUSERS' undeclared here (not in a function) param.c:80: initializer element is not constant param.c:86: `MAXUSERS' undeclared here (not in a function) param.c:86: initializer element is not constant param.c:93: `MAXUSERS' undeclared here (not in a function) param.c:93: initializer element is not constant param.c:96: `MAXUSERS' undeclared here (not in a function) param.c:96: initializer element is not constant *** Error code 1 Stop. __________ Sorry about the hacked up cut-and-paste. I'm using a Windows SSH client at work. Any ideas? Am I doing something stupid? Thanks for any help. Matt Briggs mbriggs@switchboard.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 14 12:40:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA01323 for freebsd-current-outgoing; Tue, 14 Jul 1998 12:40:56 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pluto.plutotech.com (mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA01318; Tue, 14 Jul 1998 12:40:54 -0700 (PDT) (envelope-from gibbs@plutotech.com) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.8.7/8.8.5) with ESMTP id NAA07875; Tue, 14 Jul 1998 13:40:48 -0600 (MDT) Message-Id: <199807141940.NAA07875@pluto.plutotech.com> X-Mailer: exmh version 2.0.2 2/24/98 To: scsi@FreeBSD.ORG cc: current@FreeBSD.ORG Subject: 3.0CAM-19980712-SNAP release availalable Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 14 Jul 1998 13:35:35 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A full CAM release is now available at: ftp://ftp.FreeBSD.org/pub/cam/3.0CAM-19980712-SNAP/ -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 14 13:16:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA07181 for freebsd-current-outgoing; Tue, 14 Jul 1998 13:16:31 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from news1.gtn.com (news1.gtn.com [192.109.159.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA07158 for ; Tue, 14 Jul 1998 13:16:22 -0700 (PDT) (envelope-from andreas@klemm.gtn.com) Received: (from uucp@localhost) by news1.gtn.com (8.8.6/8.8.6) with UUCP id WAA24019; Tue, 14 Jul 1998 22:15:06 +0200 (MET DST) Received: (from andreas@localhost) by klemm.gtn.com (8.8.8/8.8.8) id WAA01251; Tue, 14 Jul 1998 22:00:31 +0200 (CEST) (envelope-from andreas) Message-ID: <19980714220030.A1225@klemm.gtn.com> Date: Tue, 14 Jul 1998 22:00:30 +0200 From: Andreas Klemm To: "Justin T. Gibbs" Cc: "Kurt D. Zeilenga" , current@FreeBSD.ORG Subject: Re: CAM on a -current branch References: <19980714190256.A3474@klemm.gtn.com> <199807141849.MAA05620@pluto.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199807141849.MAA05620@pluto.plutotech.com>; from Justin T. Gibbs on Tue, Jul 14, 1998 at 12:44:15PM -0600 X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 3.0-CURRENT SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jul 14, 1998 at 12:44:15PM -0600, Justin T. Gibbs wrote: > >> I cannot build a release on a partition with soft updates enabled. This > >> is "unstable enough" for me to not use soft updates. > > > >What happens then ??? Kernel panic ? > > I believe so. My machine was in X at the time, but I will attempt to > reproduce the problem with a serial console once I get the 2.2CAM > snapshot release build completed. I build a debug kernel using CAM, ccd and softupdates, let's see, I'll try a make -j 4 world... /dev/da0s2a on / (NFS exported, local, soft-updates, writes: sync 4 async 124) devfs on dummy_mount (local) /dev/da0s2f on /usr (NFS exported, local, soft-updates, writes: sync 2 async 415) /dev/da0s2e on /var (local, soft-updates, writes: sync 13 async 495) /dev/ccd0c on /obj (asynchronous, local, noatime, writes: sync 2 async 0) /dev/ccd1c on /news (NFS exported, local, noatime, soft-updates, writes: sync 2 async 201) /dev/ccd2c on /proxy (local, noatime, soft-updates, writes: sync 2 async 34) /dev/ccd3c on /home (NFS exported, local, soft-updates, writes: sync 2 async 218) procfs on /proc (local) /dev/da0s1 on /dos (local) mfs:33 on /tmp (asynchronous, local, writes: sync 6 async 55) amd:182 on /host -- Andreas Klemm http://www.FreeBSD.ORG/~andreas What gives you 90% more speed, for example, in kernel compilation ? http://www.FreeBSD.ORG/~fsmp/SMP/akgraph-a/graph1.html "NT = Not Today" (Maggie Biggs) ``powered by FreeBSD SMP'' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 14 13:39:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA11195 for freebsd-current-outgoing; Tue, 14 Jul 1998 13:39:44 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from tim.xenologics.com (tim.xenologics.com [194.77.5.24]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA11154; Tue, 14 Jul 1998 13:39:36 -0700 (PDT) (envelope-from seggers@semyam.dinoco.de) Received: (from uucp@localhost) by tim.xenologics.com (8.8.5/8.8.8) with UUCP id WAA07018; Tue, 14 Jul 1998 22:34:43 +0200 (MET DST) Received: from semyam.dinoco.de (semyam.dinoco.de [127.0.0.1]) by semyam.dinoco.de (8.8.8/8.8.8) with ESMTP id MAA10824; Tue, 14 Jul 1998 12:43:25 +0200 (CEST) (envelope-from seggers@semyam.dinoco.de) Message-Id: <199807141043.MAA10824@semyam.dinoco.de> To: Brandon Lockhart cc: Jeremy Domingue , current@FreeBSD.ORG, stable@FreeBSD.ORG, questions@FreeBSD.ORG, seggers@semyam.dinoco.de Subject: Re: Disgruntled Linux User... questions about FreeBSD In-reply-to: Your message of "Mon, 13 Jul 1998 19:14:16 EDT." Date: Tue, 14 Jul 1998 12:43:25 +0200 From: Stefan Eggers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Well, let's see. Linux is a clone of SYSV, and FreeBSD a clone of BSD, is > that major enough for you? Possibly different devices, different FS, Linux has no connection to System V source so clone is OK. But FreeBSD is based on 4.4BSD-Lite code so I think the term "clone" is not appropriate here. Stefan. -- Stefan Eggers Lu4 yao2 zhi1 ma3 li4, Max-Slevogt-Str. 1 ri4 jiu3 jian4 ren2 xin1. 51109 Koeln Federal Republic of Germany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 14 14:02:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA14548 for freebsd-current-outgoing; Tue, 14 Jul 1998 14:02:11 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA14523; Tue, 14 Jul 1998 14:02:06 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.8.8/8.8.5) with SMTP id WAA04585; Tue, 14 Jul 1998 22:04:24 +0100 (BST) Date: Tue, 14 Jul 1998 22:04:24 +0100 (BST) From: Doug Rabson To: "Matthew R. Briggs" cc: Dusk Auriel Sykotik , current@FreeBSD.ORG, freebsd-alpha@FreeBSD.ORG Subject: Re: alpha support In-Reply-To: <35AB9D1B.E62A84C2@switchboard.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 14 Jul 1998, Matthew R. Briggs wrote: > [forwarded to freebsd-alpha as well as current] > > Dusk Auriel Sykotik wrote: > > > > I was wondering if -CURRENT supported the alpha platform, and if not when > > does it expect to be supported? Right now the only options presented to > > me for alphas are redhat linux (ugh) and digiunix (too much money). I > > would prefer to run FreeBSD, since its running on the other server now, > > and its run very well for me, and I've really enjoyed working with it. > > Thanks. > > > > /* > > * Matt Harris +++ Syko > > * BPSOFH, BIOFH, C, SQL, PERL +++ http://starix.technonet.net/~syko/ > > * FreeBSD SysAdmin +++ apocalypse.sykotik.org > > */ > > > > Hello, > I'd be interested to know this as well. I just bought an AS200 from > Onsale, and finally got OpenBSD running on it after fighting with Debian > Linux for three days (I hate the ARC console...arrgh). I like FreeBSD > better, though. How is the port coming along, and what can be done to > help? The port is coming on slowly. I'm not really ready for people to try and use it yet though (unless they want to help out on debugging the kernel :-). -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891 Fax: +44 181 381 1039 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 14 14:50:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA19536 for freebsd-current-outgoing; Tue, 14 Jul 1998 14:50:33 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from joshua.enteract.com (joshua.enteract.com [207.229.129.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id OAA19530 for ; Tue, 14 Jul 1998 14:50:31 -0700 (PDT) (envelope-from djhoward@joshua.enteract.com) Received: (qmail 13344 invoked by uid 1032); 14 Jul 1998 21:50:23 -0000 Message-ID: <19980714165023.G6511@enteract.com> Date: Tue, 14 Jul 1998 16:50:23 -0500 From: dannyman To: Stefan Eggers , Brandon Lockhart Cc: Jeremy Domingue , current@FreeBSD.ORG, stable@FreeBSD.ORG, questions@FreeBSD.ORG Subject: Re: Disgruntled Linux User... questions about FreeBSD Mail-Followup-To: Stefan Eggers , Brandon Lockhart , Jeremy Domingue , current@FreeBSD.ORG, stable@FreeBSD.ORG, questions@FreeBSD.ORG References: <199807141043.MAA10824@semyam.dinoco.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199807141043.MAA10824@semyam.dinoco.de>; from Stefan Eggers on Tue, Jul 14, 1998 at 12:43:25PM +0200 X-Loop: djhoward@uiuc.edu X-URL: http://www.dannyland.org/~dannyman/ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jul 14, 1998 at 12:43:25PM +0200, Stefan Eggers wrote: > > Well, let's see. Linux is a clone of SYSV, and FreeBSD a clone of BSD, is > > that major enough for you? Possibly different devices, different FS, > > Linux has no connection to System V source so clone is OK. But > FreeBSD is based on 4.4BSD-Lite code so I think the term "clone" is > not appropriate here. Actually, clone would be more appropriate for BSD, as they're sharing the same genetic code, whereas Linux is an approximation based on SysV. ;) Semantics ... of course the dict command is ever insightful; 3 definitions found >From WordNet (r) 1.6 [wn]: clone n : a group of genetically identical cells or organisms derived from a single cell or individual by some kind of asexual reproduction [syn: {clon}] v : make a clone of >From Jargon File (4.0.0/24 July 1996) [jargon]: clone /n./ 1. An exact duplicate: "Our product is a clone of their product." Implies a legal reimplementation from documentation or by reverse-engineering. Also connotes lower price. 2. A shoddy, spurious copy: "Their product is a clone of our product." 3. A blatant ripoff, most likely violating copyright, patent, or trade secret protections: "Your product is a clone of my product." This use implies legal action is pending. 4. `PC clone:' a PC-BUS/ISA or EISA-compatible 80x86-based microcomputer (this use is sometimes spelled `klone' or `PClone'). These invariably have much more bang for the buck than the IBM archetypes they resemble. 5. In the construction `Unix clone': An OS designed to deliver a Unix-lookalike environment without Unix license fees, or with additional `mission-critical' features such as support for real-time programming. 6. /v./ To make an exact copy of something. "Let me clone that" might mean "I want to borrow that paper so I can make a photocopy" or "Let me get a copy of that file before you {mung} it". >From The Free On-line Dictionary of Computing (15Feb98) [foldoc]: clone 1. An exact duplicate: "Our product is a clone of their product." Implies a legal reimplementation from documentation or by reverse-engineering. Also connotes lower price. 2. A shoddy, spurious copy: "Their product is a clone of our product." 3. A blatant ripoff, most likely violating copyright, patent, or trade secret protections: "Your product is a clone of my product." This use implies legal action is pending. 4. "PC clone:" a PC-BUS/{ISA} or {EISA}-compatible 80x86-based microcomputer (this use is sometimes spelled "klone" or "PClone"). These invariably have much more bang per buck than the {IBM} archetypes they resemble. 5. In the construction "Unix clone": An {operating system} designed to deliver a {Unix}-like environment without Unix licence fees or with additional "mission-critical" features such as support for {real-time} programming. 6. A {clonebot}. (16 Dec 1994) -- // dannyman yori aiokomete || Our Honored Symbol deserves \\/ http://www.dannyland.org/~dannyman/ || an Honorable Retirement (UIUC) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 14 16:11:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA29571 for freebsd-current-outgoing; Tue, 14 Jul 1998 16:11:54 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp11.bellglobal.com (smtp11.bellglobal.com [204.101.251.53]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA29562 for ; Tue, 14 Jul 1998 16:11:51 -0700 (PDT) (envelope-from tim@localhost.my.domain) Received: from localhost.my.domain (ppp1558.on.bellglobal.com [206.172.249.22]) by smtp11.bellglobal.com (8.8.5/8.8.5) with ESMTP id TAA11899; Tue, 14 Jul 1998 19:11:42 -0400 (EDT) Received: (from tim@localhost) by localhost.my.domain (8.8.8/8.8.8) id RAA02370; Tue, 14 Jul 1998 17:11:41 -0400 (EDT) (envelope-from tim) Message-ID: <19980714171141.A2344@zappo> Date: Tue, 14 Jul 1998 17:11:41 -0400 From: Tim Vanderhoek To: Glenn Johnson , Jeremy Domingue Cc: current@FreeBSD.ORG Subject: Re: Disgruntled Linux User... questions about FreeBSD References: <009501bdae88$70e84f20$6e2f87d0@ws-47-110.selectaswitch.com> <199807132212.RAA02798@symbion.srrc.usda.gov> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199807132212.RAA02798@symbion.srrc.usda.gov>; from Glenn Johnson on Mon, Jul 13, 1998 at 05:12:04PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jul 13, 1998 at 05:12:04PM -0500, Glenn Johnson wrote: > > > > 4) I know that the current build of FreeBSD is listed as development and > > should not be used in a mission critical environment, however, what are [...] > > Well, I consider the jobs that my systems do to be mission critiacal. > I have a total of 6 FreeBSD SMP systems and have never had a crash. > The only problem I After yet another endorsement of -current, it may bear reminding that it was _not_ very long ago that -current was randomly _trashing_ filesystems. You should avoid running -current in a production environment unless you need to. If you do (and there seems to be a fairly large number currently (haha) doing so succesfully, generally people who need -current's features even though 3.0-RELEASE is still being held back), then don't track -current regularly (only upgrade when you have reason to believe that -current on a given date is reasonably solid) and do follow the relavent mailing-lists. -- This .sig is not innovative, witty, or profund. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 14 16:23:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA00910 for freebsd-current-outgoing; Tue, 14 Jul 1998 16:23:57 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA00891; Tue, 14 Jul 1998 16:23:53 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id QAA11209; Tue, 14 Jul 1998 16:15:56 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd011204; Tue Jul 14 23:15:50 1998 Date: Tue, 14 Jul 1998 16:15:45 -0700 (PDT) From: Julian Elischer To: Adam McDougall cc: current@FreeBSD.ORG, julian@FreeBSD.ORG Subject: Re: TESTERS NEEDED: Softupdates looks Very good. In-Reply-To: <35AB29C1.FFFF01E0@ameritech.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I got a fix for some hanging sent to me today.. I will check it out and get back to you.. julian On Tue, 14 Jul 1998, Adam McDougall wrote: > I have a partition solely for the source and ports tree with softupdates > enabled (and also /usr since things were going smoothly lately) but while > trying to build the XFree86 port on a kernel and system from approx. midnight, > it has been hanging the system.I noticed because ther compile stopped doing > anything, it just sat there, just like my telnets into the machine. I could > switch consoles, and I switched to a console that had been running top, and it > was running happily, but I noticed several Zombies as shown by the second line > of top. I use top -I so I didnt see what they were, but i assume they were the > proccesses that tried to run past the 'hang'. ctrl-alt-del did not work, I had > to cold boot the machine. This has happened twice tonight. I have a dpt 2144UW > HBA, p233mmx, and was using links to the latest ffs_softdep.c and softdep.h. > Is there something useful I could get out of DDB when this happens? I could > probably reproduce it. Anything else I could try to help analyze whats wrong? > Any more machine-specific info needed? Thanks > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 14 16:46:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA03549 for freebsd-current-outgoing; Tue, 14 Jul 1998 16:46:28 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from news1.gtn.com (news1.gtn.com [194.77.0.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA03543 for ; Tue, 14 Jul 1998 16:46:24 -0700 (PDT) (envelope-from andreas@klemm.gtn.com) Received: (from uucp@localhost) by news1.gtn.com (8.8.6/8.8.6) with UUCP id BAA04546; Wed, 15 Jul 1998 01:30:06 +0200 (MET DST) Received: (from andreas@localhost) by klemm.gtn.com (8.8.8/8.8.8) id BAA02047; Wed, 15 Jul 1998 01:13:06 +0200 (CEST) (envelope-from andreas) Message-ID: <19980715011306.A21986@klemm.gtn.com> Date: Wed, 15 Jul 1998 01:13:06 +0200 From: Andreas Klemm To: "Justin T. Gibbs" Cc: "Kurt D. Zeilenga" , current@FreeBSD.ORG Subject: Re: CAM on a -current branch References: <19980714190256.A3474@klemm.gtn.com> <199807141849.MAA05620@pluto.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199807141849.MAA05620@pluto.plutotech.com>; from Justin T. Gibbs on Tue, Jul 14, 1998 at 12:44:15PM -0600 X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 3.0-CURRENT SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jul 14, 1998 at 12:44:15PM -0600, Justin T. Gibbs wrote: > >> I cannot build a release on a partition with soft updates enabled. This > >> is "unstable enough" for me to not use soft updates. > > > >What happens then ??? Kernel panic ? > > I believe so. My machine was in X at the time, but I will attempt to > reproduce the problem with a serial console once I get the 2.2CAM > snapshot release build completed. My machine behaves well. One make buildworld ran without problems. No I do a make -j 16 buildworld in a "while loop" to stress test CAM and softupdates. I'm not running X for this test, to see the messages on the console if something bad happens ;-) I'll keep you informed. Here my system configuration for reference: Copyright (c) 1992-1998 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-CURRENT #0: Tue Jul 14 21:53:34 CEST 1998 root@titan.klemm.gtn.com:/home/src/sys/compile/ISDNSMPCAM Timecounter "i8254" frequency 1193182 Hz cost 3624 ns CPU: Pentium Pro (686-class CPU) Origin = "GenuineIntel" Id = 0x619 Stepping=9 Features=0xfbff real memory = 83886080 (81920K bytes) avail memory = 78135296 (76304K bytes) 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 DEVFS: ready for devices Probing for devices on PCI bus 0: chip0: rev 0x02 on pci0.0.0 chip1: rev 0x01 on pci0.7.0 vx0: <3COM 3C900 Etherlink XL PCI> rev 0x00 int a irq 19 on pci0.11.0 utp/aui/bnc[*utp*] address 00:60:97:aa:3a:db vga0: rev 0x01 int a irq 18 on pci0.12.0 ahc0: rev 0x00 int a irq 17 on pci0.13.0 ahc0: aic7880 Single Channel A, SCSI Id=7, 16/255 SCBs ahc1: rev 0x03 int a irq 16 on pci0.14.0 ahc1: aic7870 Single Channel A, SCSI Id=7, 16/255 SCBs Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <4 virtual consoles, flags=0x0> ed0 at 0x280-0x29f irq 10 maddr 0xd0000 msize 16384 on isa ed0: address 00:00:c0:5a:98:2a, type WD8013EPC (16 bit) sio0 at 0x3f8-0x3ff irq 4 flags 0x20 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface psm0 at 0x60-0x64 irq 12 on motherboard psm0: model Generic PS/2 mouse, device ID 0 pcm0 at 0x220 irq 5 drq 1 flags 0x15 on isa fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in isic0 at 0xd80 irq 9 flags 0x4 on isa isic0: Teles S0/16.3 isic0: ISAC 2085 Version A1/A2 or 2086/2186 Version 1.1 (IOM-2) (Addr=0x960) isic0: HSCX 82525 or 21525 Version 2.1 (AddrA=0x160, AddrB=0x560) npx0 flags 0x1 on motherboard npx0: INT 16 interface DEVFS: ready to run APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via pin 2 ccd0-3: Concatenated disk drivers i4b: ISDN call control device attached i4bisppp: 4 ISDN SyncPPP device(s) attached i4bctl: ISDN system control port attached i4bipr: 4 IP over raw HDLC ISDN device(s) attached i4btel: 2 ISDN telephony interface device(s) attached i4brbch: 4 raw B channel access device(s) attached i4btrc: 4 ISDN trace device(s) attached IP packet filtering initialized, divert enabled, rule-based forwarding disabled, logging limited to 500 packets/entry SMP: AP CPU #1 Launched! sa0 at ahc0 bus 0 target 4 lun 0 sa0: Removable Sequential Access SCSI2 device sa0: 4.807MB/s transfers (4.807MHz, offset 8) changing root device to da0s2a da1 at ahc1 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI2 device da1: 10.0MB/s transfers (10.0MHz, offset 15), Tagged Queueing Enabled da1: 2063MB (4226725 512 byte sectors: 255H 63S/T 263C) da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI2 device da0: 20.0MB/s transfers (20.0MHz, offset 15), Tagged Queueing Enabled da0: 2063MB (4226725 512 byte sectors: 255H 63S/T 263C) da2 at ahc1 bus 0 target 2 lun 0 da2: Fixed Direct Access SCSI2 device da2: 10.0MB/s transfers (10.0MHz, offset 15), Tagged Queueing Enabled da2: 2063MB (4226725 512 byte sectors: 255H 63S/T 263C) cd0 at ahc0 bus 0 target 6 lun 0 cd0: Removable CD-ROM SCSI2 device cd0: 10.0MB/s transfers (10.0MHz, offset 8) cd0: cd present [323122 x 2048 byte records] ffs_mountfs: superblock updated ffs_mountfs: superblock updated ffs_mountfs: superblock updated ffs_mountfs: superblock updated ffs_mountfs: superblock updated vx0: selected utp. (link2) isppp0: phase establish i4b-L2-i4b_tei_assign: tx TEI ID_Request i4b-L2-i4b_T202_timeout: unit 0, N202 = 3 i4b-L2-i4b_tei_assign: tx TEI ID_Request i4b-L2-i4b_tei_rx_frame: TEI ID Assign - TEI = 103 isppp0: phase authenticate isppp0: phase network (da0:ahc0:0:0:0): tagged openings now 32 0 open: device busy isppp0: phase terminate isppp0: phase dead (da2:ahc1:0:2:0): tagged openings now 32 (da1:ahc1:0:1:0): tagged openings now 32 isppp0: phase establish isppp0: phase authenticate isppp0: phase network isppp0: phase terminate isppp0: phase dead isppp0: phase establish isppp0: phase authenticate isppp0: phase network # # ISDN kernel # machine "i386" cpu "I686_CPU" ident ISDNSMPCAM # rse's recommendations for heavily users apache servers maxusers 256 options SOMAXCONN="256" options "NMBCLUSTER=4096" # Options for the VM subsystem options PQ_HUGECACHE # color for 1024k/16k cache options SMP # Symmetric MultiProcessor Kernel options APIC_IO # Symmetric (APIC) I/O options INCLUDE_CONFIG_FILE # Include this file in kernel options DDB options KTRACE #kernel tracing options SHOW_BUSYBUFS # busy buffers on shutdown ? options INET #InterNETworking options IPFIREWALL #firewall options IPFIREWALL_VERBOSE #print information about dropped packets options "IPFIREWALL_VERBOSE_LIMIT=500" #limit verbosity options IPDIVERT #divert sockets options "P1003_1B" options "_KPOSIX_PRIORITY_SCHEDULING" options "_KPOSIX_VERSION=199309L" options FFS #Berkeley Fast Filesystem options NFS #Network File System options MFS #Memory File System options "CD9660" #ISO 9660 filesystem options MSDOSFS #MS DOS File System options PROCFS #Process filesystem options NSWAPDEV=3 #Allow this many swap-devices. options SOFTUPDATES #Kirk McKusick's code options DEVFS #devices filesystem # misc options options "COMPAT_43" #Compatible with BSD 4.3 [KEEP THIS!] options UCONSOLE #Allow users to grab the console options SYSVSHM,SYSVSEM,SYSVMSG #shared memory (X11) options COMPAT_LINUX # Linux Binary compatibility options "MD5" config kernel root on da1 # ISA and PCI BUS support controller isa0 controller pci0 # Floppy Disk Controller controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr disk fd0 at fdc0 drive 0 # SCSI Devices # AHA 2940U controller ahc0 controller scbus0 at ahc0 disk da0 at scbus0 target 0 unit 0 disk da3 at scbus0 target 1 unit 0 tape sa0 at scbus0 target 4 device cd0 at scbus0 target 6 # AHA 2940 controller ahc1 controller scbus1 at ahc1 disk da1 at scbus1 target 1 unit 0 disk da2 at scbus1 target 2 unit 0 options SCSI_DELAY=4 # Be pessimistic about Joe SCSI device options "CD9660_ROOTDELAY=8" options SCSI_REPORT_GEOMETRY # SCO compatible system console device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr options MAXCONS=4 # number of virtual consoles options SC_HISTORY_SIZE=200 # number of history buffer lines # floating point unit device npx0 at isa? port "IO_NPX" flags 0x1 irq 13 vector npxintr device sio0 at isa? port "IO_COM1" tty irq 4 flags 0x20 vector siointr device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr options BREAK_TO_DEBUGGER #a BREAK on a comconsole goes to DDB, #if available. options CONSPEED=38400 #default speed for serial console #(default 9600) # parallel device on mainboard device lpt0 at isa? port? tty irq 7 vector lptintr # PS/2 mouse on mainboard device psm0 at isa? port "IO_KBD" conflicts tty irq 12 vector psmintr options "PSM_ACCEL=1" # PS/2 mouse acceleration # Network 3COM PCI device vx0 device ed0 at isa? port 0x280 net irq 10 iomem 0xd0000 vector edintr # New Sound code device pcm0 at isa? port ? tty irq 5 drq 1 flags 0x15 vector pcmintr # Pseudo devices pseudo-device loop #Network loopback device pseudo-device ether #Generic Ethernet pseudo-device vn 1 #Vnode driver (turns a file into a dev.) pseudo-device snp 3 #Snoop device - to look at pty/vty/etc.. pseudo-device disc #Discard device pseudo-device bpfilter 4 #Berkeley packet filter pseudo-device pty 16 #Pseudo ttys - can go as high as 256 pseudo-device gzip # Exec gzipped a.out's pseudo-device ccd 4 #Concatenated disk driver pseudo-device tun 1 #Tunnel driver (user process ppp(8)) pseudo-device ppp 1 #Point-to-point protocol options PPP_BSDCOMP #PPP BSD-compress support options PPP_DEFLATE #PPP zlib/deflate/gzip support options PPP_FILTER #enable bpf filtering (needs bpfilter) # Size of the kernel message buffer. Should be N * pagesize. options "MSGBUF_SIZE=40960" options "I4B_SMP_WORKAROUND" # i4b passive ISDN cards support (isic - I4b Siemens Isdn Chipset driver) # Teles S0/16.3 options "TEL_S0_16_3" device isic0 at isa? port 0xd80 net irq 9 flags 0x04 vector isicintr # i4b passive cards D channel handling # Q.921 pseudo-device "i4bq921" # Q.931 pseudo-device "i4bq931" # common passive and active layer 4 # layer 4 pseudo-device "i4b" # userland driver to do ISDN tracing (for passive cards oly) pseudo-device "i4btrc" 4 # userland driver to control the whole thing pseudo-device "i4bctl" # userland driver for access to raw B channel pseudo-device "i4brbch" 4 # userland driver for telephony pseudo-device "i4btel" 2 # network driver for IP over raw HDLC ISDN pseudo-device "i4bipr" 4 # enable VJ header compression detection for ipr i/f options IPR_VJ # network driver for sync PPP over ISDN pseudo-device "i4bisppp" 4 pseudo-device sppp 4 -- Andreas Klemm http://www.FreeBSD.ORG/~andreas What gives you 90% more speed, for example, in kernel compilation ? http://www.FreeBSD.ORG/~fsmp/SMP/akgraph-a/graph1.html "NT = Not Today" (Maggie Biggs) ``powered by FreeBSD SMP'' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 14 16:46:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA03564 for freebsd-current-outgoing; Tue, 14 Jul 1998 16:46:34 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from news1.gtn.com (news1.gtn.com [194.77.0.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA03544 for ; Tue, 14 Jul 1998 16:46:24 -0700 (PDT) (envelope-from andreas@klemm.gtn.com) Received: (from uucp@localhost) by news1.gtn.com (8.8.6/8.8.6) with UUCP id BAA05379; Wed, 15 Jul 1998 01:45:06 +0200 (MET DST) Received: (from andreas@localhost) by klemm.gtn.com (8.8.8/8.8.8) id BAA22387; Wed, 15 Jul 1998 01:22:54 +0200 (CEST) (envelope-from andreas) Message-ID: <19980715012253.A11569@klemm.gtn.com> Date: Wed, 15 Jul 1998 01:22:53 +0200 From: Andreas Klemm To: ben@rosengart.com, current@FreeBSD.ORG Subject: Re: MAKE_KERBEROS4 and OBJLINK incompatible References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from Snob Art Genre on Tue, Jul 14, 1998 at 02:13:05PM -0400 X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 3.0-CURRENT SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jul 14, 1998 at 02:13:05PM -0400, Snob Art Genre wrote: > I can build world fine (with today's sources) with either MAKE_KERBEROS4 > or OBJLINK defined in /etc/make.conf, but with both, the build dies > here: You don't need OBJLINK, since everything is build in /usr/obj with tools under /usr/obj ... -- Andreas Klemm http://www.FreeBSD.ORG/~andreas What gives you 90% more speed, for example, in kernel compilation ? http://www.FreeBSD.ORG/~fsmp/SMP/akgraph-a/graph1.html "NT = Not Today" (Maggie Biggs) ``powered by FreeBSD SMP'' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 14 16:48:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA03869 for freebsd-current-outgoing; Tue, 14 Jul 1998 16:48:03 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dns.webwizard.net.mx (mexcom.net.mx [207.249.162.140]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA03812 for ; Tue, 14 Jul 1998 16:47:55 -0700 (PDT) (envelope-from eculp@webwizard.org.mx) Received: from sunix (eculp@sunix.mexcom.net [206.103.64.3]) by dns.webwizard.net.mx (8.8.8/8.8.7) with SMTP id SAA27127 for ; Tue, 14 Jul 1998 18:46:42 -0500 (CDT) Message-ID: <35ABE149.76EA9037@webwizard.org.mx> Date: Tue, 14 Jul 1998 17:52:57 -0500 From: Edwin Culp Organization: Mexico Communicates X-Mailer: Mozilla 3.01Gold (X11; I; Linux 2.0.14 i586) MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG Subject: Softupdates Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I installed softupdates this morning on a new machine with a one ide disk (not much room for creativity), three slices, root, usr and swap. Mounted root and usr with softupdates, cvsuped and did a make world in 59 minutes. I was very pleasantly surprised. I then recompiled kernel and rebooted did a mount and had lost softupdates from my / partition:-( Can I keep this from happening? What is the easiest way to do tunefs -n enable. This morning I used boot floppies:-) There has to be a better way. Thanks ed To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 14 17:00:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA06053 for freebsd-current-outgoing; Tue, 14 Jul 1998 17:00:43 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from engulf.net (engulf.com [207.96.124.102]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA06002; Tue, 14 Jul 1998 17:00:33 -0700 (PDT) (envelope-from brandon@engulf.net) Received: from localhost (brandon@localhost) by engulf.net (8.8.8/8.8.8) with SMTP id TAA17431; Tue, 14 Jul 1998 19:56:37 -0400 (EDT) Date: Tue, 14 Jul 1998 19:56:28 -0400 (EDT) From: Brandon Lockhart To: David Greenman cc: Jeremy Domingue , current@FreeBSD.ORG, stable@FreeBSD.ORG, questions@FreeBSD.ORG Subject: Re: Disgruntled Linux User... questions about FreeBSD In-Reply-To: <199807141511.IAA18210@implode.root.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG What are you talking about, I was talking about for a HIGHLY used server, as in, more then cdrom.com, and I was talking about a REAL server, not a PC supped up. I am talking about a rack mount server, a REAL server. Which in case you where out of the loop, most REAL servers use RISC. On Tue, 14 Jul 1998, David Greenman wrote: :>First of all, I do not recommend Gateway 2k for server's. Get a COMPAQ or :>HP or SUN. RISC is the way to go. : : It's a good thing that we (the FreeBSD developers) don't believe this else :several of the largest servers on the Internet wouldn't be running FreeBSD. :...but of course we think otherwise. FreeBSD makes an excellent server :platform and most PCs, despite their warts, work just fine in this application. : :-DG : :David Greenman :Co-founder/Principal Architect, The FreeBSD Project : ,-----------------------------------------------------------------. | //// "Anything I say represents only my opinion." | | (o o) / | | ,---ooO--(_)--Ooo---------------------------------------------, | | | BRANDON LOCKHART | | | `-------------------------------------------------------------' | | brandon.lockhart@usinternetworking.com brandon@engulf.net | | Work: (410) 897-4551 Pager: (888) xxx-xxxx | `-----------------------------------------------------------------' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 14 17:22:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA09134 for freebsd-current-outgoing; Tue, 14 Jul 1998 17:22:57 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA09102; Tue, 14 Jul 1998 17:22:49 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id RAA25013; Tue, 14 Jul 1998 17:22:24 -0700 (PDT) Message-Id: <199807150022.RAA25013@implode.root.com> To: Brandon Lockhart cc: Jeremy Domingue , current@FreeBSD.ORG, stable@FreeBSD.ORG, questions@FreeBSD.ORG Subject: Re: Disgruntled Linux User... questions about FreeBSD In-reply-to: Your message of "Tue, 14 Jul 1998 19:56:28 EDT." From: David Greenman Reply-To: dg@root.com Date: Tue, 14 Jul 1998 17:22:24 -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >What are you talking about, I was talking about for a HIGHLY used server, >as in, more then cdrom.com, ...and yahoo.com, and hotmail.com (and countless thousands of other "HIGHLY used" Internet servers)...you mean, like those servers? > and I was talking about a REAL server, not a >PC supped up. I am talking about a rack mount server, a REAL server. ftp.cdrom.com and www.cdrom.com are rack mounted, but that has nothing to do with them being "REAL" servers or not. If your definition of a "REAL" server is one that doesn't contain an Intel CPU, then that's fine, but is nothing more than your opinion and has little to do with the reality of the world. >Which in case you where out of the loop, most REAL servers use RISC. No, they don't. Most servers in the world - be them corporate-internal or Internet, are PCs running, unfortunately, Windows/NT. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 14 17:34:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA11372 for freebsd-current-outgoing; Tue, 14 Jul 1998 17:34:24 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ixion.honeywell.com (ixion.honeywell.com [129.30.4.80]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA11236; Tue, 14 Jul 1998 17:34:18 -0700 (PDT) (envelope-from sleas@ixion.honeywell.com) Received: from localhost by ixion.honeywell.com with SMTP (1.40.112.8/16.2) id AA028882727; Tue, 14 Jul 1998 19:32:07 -0500 Date: Tue, 14 Jul 1998 19:32:07 -0500 (CDT) From: Shawn Leas To: Brandon Lockhart Cc: David Greenman , Jeremy Domingue , current@FreeBSD.ORG, stable@FreeBSD.ORG, questions@FreeBSD.ORG Subject: Re: Disgruntled Linux User... questions about FreeBSD In-Reply-To: Message-Id: X-Clinton-Hdr4: test header4 Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Maybe you need to look into VLIW, IMHO the future of architecture. Very Long Instruction Word... You know how fixed lengh RISC instructions are easily pipelined? Well, VLIW is pipelined at compile time... Of course, non of this to my knowledge is in production anywhere, so a moot point.. Thought I'd mention it though, as it's fun stuff. -Shawn <=========== America Held Hostage ===========> Day 2001 for the poor and the middle class. Day 2020 for the rich and the dead. 921 days remaining in the Raw Deal. <============================================> On Tue, 14 Jul 1998, Brandon Lockhart wrote: > What are you talking about, I was talking about for a HIGHLY used server, > as in, more then cdrom.com, and I was talking about a REAL server, not a > PC supped up. I am talking about a rack mount server, a REAL server. > Which in case you where out of the loop, most REAL servers use RISC. > > > On Tue, 14 Jul 1998, David Greenman wrote: > > :>First of all, I do not recommend Gateway 2k for server's. Get a COMPAQ or > :>HP or SUN. RISC is the way to go. > : > : It's a good thing that we (the FreeBSD developers) don't believe this else > :several of the largest servers on the Internet wouldn't be running FreeBSD. > :...but of course we think otherwise. FreeBSD makes an excellent server > :platform and most PCs, despite their warts, work just fine in this application. > : > :-DG > : > :David Greenman > :Co-founder/Principal Architect, The FreeBSD Project > : > > > ,-----------------------------------------------------------------. > | //// "Anything I say represents only my opinion." | > | (o o) / | > | ,---ooO--(_)--Ooo---------------------------------------------, | > | | BRANDON LOCKHART | | > | `-------------------------------------------------------------' | > | brandon.lockhart@usinternetworking.com brandon@engulf.net | > | Work: (410) 897-4551 Pager: (888) xxx-xxxx | > `-----------------------------------------------------------------' > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 14 17:38:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA12460 for freebsd-current-outgoing; Tue, 14 Jul 1998 17:38:28 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id RAA12452; Tue, 14 Jul 1998 17:38:27 -0700 (PDT) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 0ywFZq-0003zk-00; Tue, 14 Jul 1998 17:37:46 -0700 Date: Tue, 14 Jul 1998 17:37:43 -0700 (PDT) From: Tom X-Sender: tom@shell.uniserve.ca To: Brandon Lockhart cc: David Greenman , Jeremy Domingue , current@FreeBSD.ORG, stable@FreeBSD.ORG, questions@FreeBSD.ORG Subject: Re: Disgruntled Linux User... questions about FreeBSD In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 14 Jul 1998, Brandon Lockhart wrote: > What are you talking about, I was talking about for a HIGHLY used server, > as in, more then cdrom.com, and I was talking about a REAL server, not a More than wcarchive.cdrom.com? Can you even name a server that does more traffic than wcarchive.cdrom.com? > PC supped up. I am talking about a rack mount server, a REAL server. cdrom.com is a rack mount server. > Which in case you where out of the loop, most REAL servers use RISC. Most servers are not risc. Period. See sales figures. Tom Systems Support Uniserve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 14 17:38:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA12552 for freebsd-current-outgoing; Tue, 14 Jul 1998 17:38:39 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA12520 for ; Tue, 14 Jul 1998 17:38:34 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id RAA27617 for ; Tue, 14 Jul 1998 17:37:22 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: current@FreeBSD.ORG Subject: STOP THE BLOODY CROSS POSTING! Date: Tue, 14 Jul 1998 17:37:22 -0700 Message-ID: <27613.900463042@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm going to start unsubscribing people the next time I see a message cross-posted to "current", "stable" and "questions" and I don't care if you just followed up without bothering to trim the cc or if you originated the message yourself. People just aren't getting the message here, and that's to knock it off with the cross posting! It's specifically disallowed by the mailing list charters, something which I advise anyone who has yet to read them to go read: http://www.freebsd.org/handbook/eresources:charters.html And no, I'm not simply going to whap `delete' on cross-posts or make procmail a solution for a problem which should be handled by the posters themselves. The charters were written for a reason and we expect people to follow them. Thanks. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 14 17:55:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA14984 for freebsd-current-outgoing; Tue, 14 Jul 1998 17:55:13 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA14978 for ; Tue, 14 Jul 1998 17:55:09 -0700 (PDT) (envelope-from doconnor@cain.gsoft.com.au) Received: from cain (localhost [127.0.0.1]) by cain.gsoft.com.au (8.8.8/8.6.9) with ESMTP id KAA16582; Wed, 15 Jul 1998 10:24:46 +0930 (CST) Message-Id: <199807150054.KAA16582@cain.gsoft.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Cejka Rudolf cc: freebsd-current@FreeBSD.ORG (freebsd-current@freebsd.org) Subject: Re: Is MSDOS FS OK? In-reply-to: Your message of "Tue, 14 Jul 1998 12:23:22 +0200." <199807141023.MAA09803@kazi.dcse.fee.vutbr.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Date: Wed, 15 Jul 1998 10:24:46 +0930 From: "Daniel O'Connor" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id RAA14980 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Yes, I have problems (FreeBSD 3.0-CURRENT #7: Wed May 27 09:58:35 CEST 1998). > Is this example sufficient? Is this widely repeatible? > (I have installed Win95 & FreeBSD-CURRENT in my box.) Hmm.. I partially toasted my FAT32 partition using an oldish MSDOSFS :) Still, it was windows so I was used to reinstalling :-/ I think my problem has been solved... Well I'll find out when I finish upgrading. --------------------------------------------------------------------- |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-current" in the body of the message From owner-freebsd-current Tue Jul 14 18:00:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA15859 for freebsd-current-outgoing; Tue, 14 Jul 1998 18:00:21 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dns.webwizard.net.mx (mexcom.net.mx [207.249.162.140]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA15850 for ; Tue, 14 Jul 1998 18:00:15 -0700 (PDT) (envelope-from eculp@webwizard.org.mx) Received: from sunix (eculp@sunix.mexcom.net [206.103.64.3]) by dns.webwizard.net.mx (8.8.8/8.8.7) with SMTP id TAA28742 for ; Tue, 14 Jul 1998 19:59:02 -0500 (CDT) Message-ID: <35ABF23E.283458B7@webwizard.org.mx> Date: Tue, 14 Jul 1998 19:05:18 -0500 From: Edwin Culp Organization: Mexico Communicates X-Mailer: Mozilla 3.01Gold (X11; I; Linux 2.0.14 i586) MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG Subject: Re: Softupdates References: <35ABE149.76EA9037@webwizard.org.mx> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Edwin Culp wrote: > > I installed softupdates this morning on a new machine with > a one ide disk (not much room for creativity), three slices, > root, usr and swap. Mounted root and usr with softupdates, > cvsuped and did a make world in 59 minutes. I was very > pleasantly surprised. I then recompiled kernel and rebooted > did a mount and had lost softupdates from my / partition:-( > > Can I keep this from happening? What is the easiest way to > do tunefs -n enable. This morning I used boot floppies:-) > There has to be a better way. > > Thanks > > ed I did it this time from single user with no problem. I thought I had done the same the first time but I guess I was in too big a hurry to make world :-) Sorry about the noise. ed To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 14 18:03:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA16614 for freebsd-current-outgoing; Tue, 14 Jul 1998 18:03:18 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lithium.elemental.org (lithium.elemental.org [204.91.240.100]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA16569; Tue, 14 Jul 1998 18:03:12 -0700 (PDT) (envelope-from daleg@lithium.elemental.org) Received: from localhost (daleg@localhost) by lithium.elemental.org (8.8.8/8.8.4) with SMTP id UAA16143; Tue, 14 Jul 1998 20:57:49 -0400 Date: Tue, 14 Jul 1998 20:57:49 -0400 (EDT) From: Dale Ghent Reply-To: Dale Ghent To: Tom cc: Brandon Lockhart , David Greenman , Jeremy Domingue , current@FreeBSD.ORG, stable@FreeBSD.ORG, questions@FreeBSD.ORG Subject: Re: Disgruntled Linux User... questions about FreeBSD In-Reply-To: Message-ID: X-President-Clinton: On Crack X-LART: Homelite Chainsaw MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 14 Jul 1998, Tom wrote: | > PC supped up. I am talking about a rack mount server, a REAL server. | | cdrom.com is a rack mount server. ftp://ftp.cdrom.com/archive-info/wcarchive.jpg -Dale G. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 14 18:03:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA16668 for freebsd-current-outgoing; Tue, 14 Jul 1998 18:03:27 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA16641 for ; Tue, 14 Jul 1998 18:03:22 -0700 (PDT) (envelope-from doconnor@cain.gsoft.com.au) Received: from cain (localhost [127.0.0.1]) by cain.gsoft.com.au (8.8.8/8.6.9) with ESMTP id KAA16716 for ; Wed, 15 Jul 1998 10:33:20 +0930 (CST) Message-Id: <199807150103.KAA16716@cain.gsoft.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: current@FreeBSD.ORG Subject: My kernel keeps hanging looking for root Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 15 Jul 1998 10:33:20 +0930 From: "Daniel O'Connor" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I did a build/install world and then recompiled my kernel, and when I rebooted it kept hanging looking for the root FS (ie I booted -v and it hung at 'considering root F/S'. Any ideas why? I had 'config kernel on wd0' in my config file, then I tried 'config kernel on wd0s2a'. But no joy :-/ I can post my kernel config file etc if necessary. My old kernel still works, so its not much of a problem. --------------------------------------------------------------------- |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-current" in the body of the message From owner-freebsd-current Tue Jul 14 18:58:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA24766 for freebsd-current-outgoing; Tue, 14 Jul 1998 18:58:22 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA24759 for ; Tue, 14 Jul 1998 18:58:20 -0700 (PDT) (envelope-from michaelh@cet.co.jp) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.8/CET-v2.2) with SMTP id BAA21244; Wed, 15 Jul 1998 01:49:50 GMT Date: Wed, 15 Jul 1998 10:49:50 +0900 (JST) From: Michael Hancock To: Shawn Leas cc: Brandon Lockhart , David Greenman , Jeremy Domingue , current@FreeBSD.ORG Subject: Re: Disgruntled Linux User... questions about FreeBSD In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Isn't VLIW a part of what Merced is about? On Tue, 14 Jul 1998, Shawn Leas wrote: > > Maybe you need to look into VLIW, IMHO the future of architecture. Very > Long Instruction Word... You know how fixed lengh RISC instructions > are easily pipelined? Well, VLIW is pipelined at compile time... Of > course, non of this to my knowledge is in production anywhere, so a moot > point.. Thought I'd mention it though, as it's fun stuff. > > -Shawn > <=========== America Held Hostage ===========> > Day 2001 for the poor and the middle class. > Day 2020 for the rich and the dead. > 921 days remaining in the Raw Deal. > <============================================> > > On Tue, 14 Jul 1998, Brandon Lockhart wrote: > > > What are you talking about, I was talking about for a HIGHLY used server, > > as in, more then cdrom.com, and I was talking about a REAL server, not a > > PC supped up. I am talking about a rack mount server, a REAL server. > > Which in case you where out of the loop, most REAL servers use RISC. > > > > > > On Tue, 14 Jul 1998, David Greenman wrote: > > > > :>First of all, I do not recommend Gateway 2k for server's. Get a COMPAQ or > > :>HP or SUN. RISC is the way to go. > > : > > : It's a good thing that we (the FreeBSD developers) don't believe this else > > :several of the largest servers on the Internet wouldn't be running FreeBSD. > > :...but of course we think otherwise. FreeBSD makes an excellent server > > :platform and most PCs, despite their warts, work just fine in this application. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 14 19:08:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA25773 for freebsd-current-outgoing; Tue, 14 Jul 1998 19:08:55 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from www.video-collage.com (root@www.video-collage.com [206.15.171.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA25768 for ; Tue, 14 Jul 1998 19:08:53 -0700 (PDT) (envelope-from mi@xxx.video-collage.com) Received: from xxx.video-collage.com (mi@xxx.video-collage.com [199.232.254.68]) by www.video-collage.com (8.8.5/8.8.5) with ESMTP id WAA04435 for ; Tue, 14 Jul 1998 22:09:50 -0400 (EDT) Received: (from mi@localhost) by xxx.video-collage.com (8.8.8/8.8.7) id WAA29904 for current@freebsd.org; Tue, 14 Jul 1998 22:08:44 -0400 (EDT) (envelope-from mi) From: Mikhail Teterin Message-Id: <199807150208.WAA29904@xxx.video-collage.com> Subject: Re: STOP THE BLOODY CROSS POSTING! In-Reply-To: <27613.900463042@time.cdrom.com> from "Jordan K. Hubbard" at "Jul 14, 98 05:37:22 pm" To: current@FreeBSD.ORG Date: Tue, 14 Jul 1998 22:08:43 -0400 (EDT) X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli" Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA26704 for freebsd-current-outgoing; Tue, 14 Jul 1998 19:17:35 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ixion.honeywell.com (ixion.honeywell.com [129.30.4.80]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA26686 for ; Tue, 14 Jul 1998 19:17:32 -0700 (PDT) (envelope-from sleas@ixion.honeywell.com) Received: from localhost by ixion.honeywell.com with SMTP (1.40.112.8/16.2) id AA236128900; Tue, 14 Jul 1998 21:15:00 -0500 Date: Tue, 14 Jul 1998 21:15:00 -0500 (CDT) From: Shawn Leas To: Michael Hancock Cc: Brandon Lockhart , David Greenman , Jeremy Domingue , current@FreeBSD.ORG Subject: Re: Disgruntled Linux User... questions about FreeBSD In-Reply-To: Message-Id: X-Clinton-Hdr4: test header4 Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, the closest I could find on that is the following quotes from http://www.intel.com/pressroom/archive/speeches/MPF1097C.HTM It's all quite interesting! "Then a number of influences came along. One of them was VLIW which showed that it was possible for certain applications to get a lot of things going in parallel. VLIW was not a commercial success, but it provided the motivation behind superscalar and then today's out of order superscalar machines, where we have hardware doing a fair amount of work, looking for parallelism in your instruction code, searching for and dispatching independent instructions, and then enhancing that through out of order techniques, register renaming a smaller register set to a larger register set, and in general, a lot of hardware activity to find implicit parallelism in your code and to take advantage of that." .... "The other thing that's very important, particularly in the explicit parallelism activity, is what distinguishes us from the earlier VLIW machines, and that is we have built in flexibility in specifying the parallelism so we can offer scalability ahead, and compatibility ahead as we go to wider and wider machines." <=========== America Held Hostage ===========> Day 2001 for the poor and the middle class. Day 2020 for the rich and the dead. 921 days remaining in the Raw Deal. <============================================> On Wed, 15 Jul 1998, Michael Hancock wrote: > Isn't VLIW a part of what Merced is about? > > On Tue, 14 Jul 1998, Shawn Leas wrote: > > > > > Maybe you need to look into VLIW, IMHO the future of architecture. Very > > Long Instruction Word... You know how fixed lengh RISC instructions > > are easily pipelined? Well, VLIW is pipelined at compile time... Of > > course, non of this to my knowledge is in production anywhere, so a moot > > point.. Thought I'd mention it though, as it's fun stuff. > > > > -Shawn > > <=========== America Held Hostage ===========> > > Day 2001 for the poor and the middle class. > > Day 2020 for the rich and the dead. > > 921 days remaining in the Raw Deal. > > <============================================> > > > > On Tue, 14 Jul 1998, Brandon Lockhart wrote: > > > > > What are you talking about, I was talking about for a HIGHLY used server, > > > as in, more then cdrom.com, and I was talking about a REAL server, not a > > > PC supped up. I am talking about a rack mount server, a REAL server. > > > Which in case you where out of the loop, most REAL servers use RISC. > > > > > > > > > On Tue, 14 Jul 1998, David Greenman wrote: > > > > > > :>First of all, I do not recommend Gateway 2k for server's. Get a COMPAQ or > > > :>HP or SUN. RISC is the way to go. > > > : > > > : It's a good thing that we (the FreeBSD developers) don't believe this else > > > :several of the largest servers on the Internet wouldn't be running FreeBSD. > > > :...but of course we think otherwise. FreeBSD makes an excellent server > > > :platform and most PCs, despite their warts, work just fine in this application. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 14 19:39:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA29393 for freebsd-current-outgoing; Tue, 14 Jul 1998 19:39:41 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns2.cetlink.net (root@ns2.cetlink.net [209.54.54.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA29388 for ; Tue, 14 Jul 1998 19:39:40 -0700 (PDT) (envelope-from jak@cetlink.net) Received: from EXIT10 (i485-gw.cetlink.net [209.198.15.97]) by ns2.cetlink.net (8.9.1/8.9.1) with SMTP id WAA10207 for ; Tue, 14 Jul 1998 22:39:33 -0400 (EDT) From: jak@cetlink.net (John Kelly) To: current@FreeBSD.ORG Subject: tickadj -t not changing tick Date: Wed, 15 Jul 1998 02:42:09 GMT Message-ID: <35ac1492.102379029@mail.cetlink.net> References: <199807150208.WAA29904@xxx.video-collage.com> In-Reply-To: <199807150208.WAA29904@xxx.video-collage.com> X-Mailer: Forte Agent 1.5/32.451 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id TAA29389 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Has anyone else noticed that tickadj -t is broken in -current? It does not change the tick. I can tell by setting the tick to a very low or high value like 9951 or 10049, and then running ntpdate -b every few minutes to see if the time step function of ntpdate is compensating for the low/high tick value. In 2.2.5 it does, but in -current it does not. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 14 20:30:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA05090 for freebsd-current-outgoing; Tue, 14 Jul 1998 20:30:53 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA05079 for ; Tue, 14 Jul 1998 20:30:50 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id NAA22646; Wed, 15 Jul 1998 13:30:29 +1000 Date: Wed, 15 Jul 1998 13:30:29 +1000 From: Bruce Evans Message-Id: <199807150330.NAA22646@godzilla.zeta.org.au> To: jak@cetlink.net Subject: Re: tickadj -t not changing tick Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Has anyone else noticed that tickadj -t is broken in -current? It >does not change the tick. I think it changes the kernel `tick' variable. However, this variable is not used for timekeeping in -current. It is only used to calculate timeout intervals. >I can tell by setting the tick to a very low or high value like 9951 >or 10049, and then running ntpdate -b every few minutes to see if the >time step function of ntpdate is compensating for the low/high tick >value. In 2.2.5 it does, but in -current it does not. `tick' shouldn't be changed in any version of 2.2 or -current. Instead, change some of the the lower-level timer variables machdep.i586_freq, machdep.tsc_freq and machdep.i8254_freq using sysctl to make `tick' actually correct. These variables should be set correctly enough by default, just like `tick', but if not, changing them works better than changing `tick' because the change routines propagate necessary changes to associated variables and/or hardware programming. The relevant sysctl variables depend on the the FreeBSD version and configuration: machdep.i8254_freq: always exists, never hurts to set it right, but only essential for it to be right on systems using it for timekeeping (2.2., -current on sub-586's and 586+'s running SMP or APM. machdep.i586_freq: 2.2 name for machdep.tsc_freq. Doesn't hurt to set it right, but not essential for it it be right. machdep.tsc_freq: -current only, must be right if it is used for timekeeping. It is used on 586+'s not running SMP or APM. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 14 20:31:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA05205 for freebsd-current-outgoing; Tue, 14 Jul 1998 20:31:28 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.camalott.com (root@mail.camalott.com [208.203.140.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA05200 for ; Tue, 14 Jul 1998 20:31:24 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-112.camalott.com [208.229.74.112]) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id WAA17459; Tue, 14 Jul 1998 22:32:00 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.8.8/8.8.8) id WAA08086; Tue, 14 Jul 1998 22:31:07 -0500 (CDT) (envelope-from joelh) Date: Tue, 14 Jul 1998 22:31:07 -0500 (CDT) Message-Id: <199807150331.WAA08086@detlev.UUCP> To: Subject: aout / elf library directories From: Joel Ray Holveck Reply-to: joelh@gnu.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A new Emacs is being tested for release, and I'm looking at one line in the FreeBSD-specific configuration file: #define START_FILES pre-crt0.o /usr/lib/crt0.o Is -current's /usr/lib/{aout,elf} going to persist for a while (which would imply I should try to get this changed before release), or is it a fairly temporary condition? (It would be possible to look for aout and elf directories, and choose among them. I only want to do this if it looks like either (1) this is going to take some time to resolve, or (2) we have had or will have any releases going out the door like this.) Thanks, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 14 20:38:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA06305 for freebsd-current-outgoing; Tue, 14 Jul 1998 20:38:23 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns2.cetlink.net (root@ns2.cetlink.net [209.54.54.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA06300 for ; Tue, 14 Jul 1998 20:38:20 -0700 (PDT) (envelope-from jak@cetlink.net) Received: from EXIT10 (i485-gw.cetlink.net [209.198.15.97]) by ns2.cetlink.net (8.9.1/8.9.1) with SMTP id XAA16090; Tue, 14 Jul 1998 23:38:05 -0400 (EDT) From: jak@cetlink.net (John Kelly) To: Bruce Evans Cc: Subject: Re: tickadj -t not changing tick Date: Wed, 15 Jul 1998 03:40:42 GMT Message-ID: <35ac2401.106331343@mail.cetlink.net> References: <199807150330.NAA22646@godzilla.zeta.org.au> In-Reply-To: <199807150330.NAA22646@godzilla.zeta.org.au> X-Mailer: Forte Agent 1.5/32.451 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id UAA06301 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 15 Jul 1998 13:30:29 +1000, Bruce Evans wrote: >`tick' shouldn't be changed in any version of 2.2 or -current. Instead, >change some of the the lower-level timer variables machdep.i586_freq, >machdep.tsc_freq and machdep.i8254_freq using sysctl to make `tick' >actually correct. These variables should be set correctly enough by >default, just like `tick', but if not, changing them works better than >changing `tick' because the change routines propagate necessary changes >to associated variables and/or hardware programming. > >The relevant sysctl variables depend on the the FreeBSD version and >configuration: > >machdep.i8254_freq: always exists, never hurts to set it right, but only > essential for it to be right on systems using it for timekeeping > (2.2., -current on sub-586's and 586+'s running SMP or APM. >machdep.i586_freq: 2.2 name for machdep.tsc_freq. Doesn't hurt to set it > right, but not essential for it it be right. >machdep.tsc_freq: -current only, must be right if it is used for timekeeping. > It is used on 586+'s not running SMP or APM. > >Bruce Ick! And all I wanted to change was tick! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 14 20:59:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA08764 for freebsd-current-outgoing; Tue, 14 Jul 1998 20:59:13 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp13.bellglobal.com (smtp13.bellglobal.com [204.101.251.52]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA08757 for ; Tue, 14 Jul 1998 20:59:11 -0700 (PDT) (envelope-from ac199@hwcn.org) Received: from localhost.my.domain (ppp1659.on.bellglobal.com [206.172.249.123]) by smtp13.bellglobal.com (8.8.5/8.8.5) with ESMTP id XAA29830; Tue, 14 Jul 1998 23:58:20 -0400 (EDT) Received: from localhost (tim@localhost) by localhost.my.domain (8.8.8/8.8.8) with SMTP id VAA04055; Tue, 14 Jul 1998 21:59:04 -0400 (EDT) (envelope-from ac199@hwcn.org) X-Authentication-Warning: localhost.my.domain: tim owned process doing -bs Date: Tue, 14 Jul 1998 21:59:04 -0400 (EDT) From: Tim Vanderhoek X-Sender: tim@localhost Reply-To: ac199@hwcn.org To: Mikhail Teterin cc: Subject: Re: STOP THE BLOODY CROSS POSTING! In-Reply-To: <199807150208.WAA29904@xxx.video-collage.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 14 Jul 1998, Mikhail Teterin wrote: > IMHO, this should be handled by mailing list software. Make sure > no-one gets the same message ID twice is rather simple, since all This is easy. If you only want to "get" the same message ID once, then filter your own messages based on message ID. Goto line 320 or so of procmailex(5). There are other people who may subscribe each mailing list to a specific email address (eg. jkh-freebsd-current@time.cdrom.com, jkh-freebsd-stable@time.cdrom.com, etc). Even more importantly, if a message is cross-posted, then it SHOULD belong in all the -lists it is cross-posted to. Consider: I may only scan the -current list today because I'm short on time. Unfortunately an important notice was cross-posted to -announce and -current, but the stupid mailing-list software only sent me the copy that was posted to -current. Because I only briefly glanced at the -current messages today before hitting 'd', I totally missed this announcement. If I had been sent both the copy to -current and the copy to -announce, I would have noticed that there was an important announcement. So long as we filter on Sender:, two copies must be sent. Or, consider another case where I keep my own personal mail archives. Again, I need a copy for each -list. > Once such software appears, the mailing chapters can probably, > be amended :-) Cross-posting merely encourages over-use of the mailing-lists, even with such mailing-list software as you envision. By encouraging cross-posting, your subscription to -current will slowly become a subscription to -current, -stable, -hackers, -chat, and -questions. By then -alpha and maybe -smp will probably have taken off and you'll start getting those postings, too. All through -current. And this, of course, belongs on -chat. -- This .sig is not innovative, witty, or profund. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 14 21:33:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA13144 for freebsd-current-outgoing; Tue, 14 Jul 1998 21:33:49 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA13139 for ; Tue, 14 Jul 1998 21:33:48 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id VAA29057; Tue, 14 Jul 1998 21:32:35 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: Mikhail Teterin cc: Subject: Re: STOP THE BLOODY CROSS POSTING! In-reply-to: Your message of "Tue, 14 Jul 1998 22:08:43 EDT." <199807150208.WAA29904@xxx.video-collage.com> Date: Tue, 14 Jul 1998 21:32:35 -0700 Message-ID: <29054.900477155@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > There may be situations when it is desirable to get the message to > more then one list. It is, of course, causing a high level of > annoyance if the intersection between the lists is high. The charters are pretty clear on that - it's really not open to debate. :( > IMHO, this should be handled by mailing list software. Make sure > no-one gets the same message ID twice is rather simple, since all Tell it to the postmaster - I've been trying to convince him of this for ages. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 14 21:50:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA15880 for freebsd-current-outgoing; Tue, 14 Jul 1998 21:50:27 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gjp.erols.com (root@alex-va-n008c079.moon.jic.com [206.156.18.89]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA15875 for ; Tue, 14 Jul 1998 21:50:25 -0700 (PDT) (envelope-from gjp@gjp.erols.com) Received: from gjp.erols.com (gjp@localhost.erols.com [127.0.0.1]) by gjp.erols.com (8.8.8/8.8.7) with ESMTP id AAA13013; Wed, 15 Jul 1998 00:50:02 -0400 (EDT) (envelope-from gjp@gjp.erols.com) X-Mailer: exmh version 2.0.1 12/23/97 To: Brandon Lockhart cc: From: "Gary Palmer" Subject: Re: Disgruntled Linux User... questions about FreeBSD In-reply-to: Your message of "Tue, 14 Jul 1998 19:56:28 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 15 Jul 1998 00:50:02 -0400 Message-ID: <13009.900478202@gjp.erols.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brandon Lockhart wrote in message ID : > What are you talking about, I was talking about for a HIGHLY used server, > as in, more then cdrom.com, and I was talking about a REAL server, not a > PC supped up. I am talking about a rack mount server, a REAL server. > Which in case you where out of the loop, most REAL servers use RISC. So you discount Sun UE series machines? Most of those are not Rack Mount. And, incase you hadn't noticed, this is the FreeBSD mailing list. Which means, like it or not, people running on Intel architecture (currently at least). You have have strong opinions about the poor architecture, but its here for a while, and people reading this list are using it. So if you could keep the S/N ratio acceptable, a whole bunch of people would appreciate it :) Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 14 22:45:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA22425 for freebsd-current-outgoing; Tue, 14 Jul 1998 22:45:58 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from news1.gtn.com (news1.gtn.com [194.77.0.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA22419 for ; Tue, 14 Jul 1998 22:45:53 -0700 (PDT) (envelope-from andreas@klemm.gtn.com) Received: (from uucp@localhost) by news1.gtn.com (8.8.6/8.8.6) with UUCP id HAA20682; Wed, 15 Jul 1998 07:45:06 +0200 (MET DST) Received: (from andreas@localhost) by klemm.gtn.com (8.8.8/8.8.8) id HAA16724; Wed, 15 Jul 1998 07:35:40 +0200 (CEST) (envelope-from andreas) Message-ID: <19980715073539.A11287@klemm.gtn.com> Date: Wed, 15 Jul 1998 07:35:39 +0200 From: Andreas Klemm To: "Justin T. Gibbs" Cc: "Kurt D. Zeilenga" , current@FreeBSD.ORG Subject: Re: CAM on a -current branch References: <19980714190256.A3474@klemm.gtn.com> <199807141849.MAA05620@pluto.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199807141849.MAA05620@pluto.plutotech.com>; from Justin T. Gibbs on Tue, Jul 14, 1998 at 12:44:15PM -0600 X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 3.0-CURRENT SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jul 14, 1998 at 12:44:15PM -0600, Justin T. Gibbs wrote: > I believe so. My machine was in X at the time, but I will attempt to > reproduce the problem with a serial console once I get the 2.2CAM > snapshot release build completed. My machine did 7 buildworlds this night without crashing ... The only thing I noticed is the following kernel message (I include the complete dmesg for reference ...) ahc0: rev 0x00 int a irq 17 on pci0.13.0 ahc0: aic7880 Single Channel A, SCSI Id=7, 16/255 SCBs ahc1: rev 0x03 int a irq 16 on pci0.14.0 ahc1: aic7870 Single Channel A, SCSI Id=7, 16/255 SCBs ccd0-3: Concatenated disk drivers sa0 at ahc0 bus 0 target 4 lun 0 sa0: Removable Sequential Access SCSI2 device sa0: 4.807MB/s transfers (4.807MHz, offset 8) changing root device to da0s2a da1 at ahc1 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI2 device da1: 10.0MB/s transfers (10.0MHz, offset 15), Tagged Queueing Enabled da1: 2063MB (4226725 512 byte sectors: 255H 63S/T 263C) da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI2 device da0: 20.0MB/s transfers (20.0MHz, offset 15), Tagged Queueing Enabled da0: 2063MB (4226725 512 byte sectors: 255H 63S/T 263C) da2 at ahc1 bus 0 target 2 lun 0 da2: Fixed Direct Access SCSI2 device da2: 10.0MB/s transfers (10.0MHz, offset 15), Tagged Queueing Enabled da2: 2063MB (4226725 512 byte sectors: 255H 63S/T 263C) cd0 at ahc0 bus 0 target 6 lun 0 cd0: Removable CD-ROM SCSI2 device cd0: 10.0MB/s transfers (10.0MHz, offset 8) cd0: cd present [323122 x 2048 byte records] ffs_mountfs: superblock updated ffs_mountfs: superblock updated ffs_mountfs: superblock updated ffs_mountfs: superblock updated ffs_mountfs: superblock updated (da0:ahc0:0:0:0): tagged openings now 32 (da2:ahc1:0:2:0): tagged openings now 32 (da1:ahc1:0:1:0): tagged openings now 32 (sa0:ahc0:0:4:0): SCB 0x4 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 SEQADDR == 0xa SSTAT1 == 0xa (sa0:ahc0:0:4:0): Queuing a BDR SCB (sa0:ahc0:0:4:0): Bus Device Reset Message Sent (sa0:ahc0:0:4:0): no longer in timeout, status = 34b ahc0: Bus Device Reset Sent. 1 SCBs aborted (sa0:ahc0:0:4:0): REWIND. CDB: 1 1 0 0 0 0 (sa0:ahc0:0:4:0): UNIT ATTENTION asc:29,0 (sa0:ahc0:0:4:0): Power on, reset, or bus device reset occurred Despite of this the machine still runs without trouble. So, this should show, that - SMP - Softupdates - CAM - ccd - i4b can be mixed without trouble ... or ?! /dev/da0s2a on / (NFS exported, local, soft-updates, writes: sync 4 async 8057) devfs on dummy_mount (local) /dev/da0s2f on /usr (NFS exported, local, soft-updates, writes: sync 2 async 18202) /dev/da0s2e on /var (local, soft-updates, writes: sync 45 async 9411) /dev/ccd0c on /obj (asynchronous, local, noatime, writes: sync 13778 async 215173) /dev/ccd1c on /news (NFS exported, local, noatime, soft-updates, writes: sync 2 async 2410) /dev/ccd2c on /proxy (local, noatime, soft-updates, writes: sync 2 async 31) /dev/ccd3c on /home (NFS exported, local, soft-updates, writes: sync 8 async 104370) procfs on /proc (local) /dev/da0s1 on /dos (local) mfs:33 on /tmp (asynchronous, local, writes: sync 6 async 17830) amd:182 on /host -- Andreas Klemm http://www.FreeBSD.ORG/~andreas What gives you 90% more speed, for example, in kernel compilation ? http://www.FreeBSD.ORG/~fsmp/SMP/akgraph-a/graph1.html "NT = Not Today" (Maggie Biggs) ``powered by FreeBSD SMP'' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 14 23:13:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA25663 for freebsd-current-outgoing; Tue, 14 Jul 1998 23:13:52 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from monk.via.net (monk.via.net [209.81.9.10]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id XAA25654 for ; Tue, 14 Jul 1998 23:13:50 -0700 (PDT) (envelope-from joe@via.net) Received: (from joe@localhost) by monk.via.net (8.6.11/8.6.12) id XAA25245; Tue, 14 Jul 1998 23:12:24 -0700 Date: Tue, 14 Jul 1998 23:12:24 -0700 From: Joe McGuckin Message-Id: <199807150612.XAA25245@monk.via.net> To: paul@originative.co.uk Subject: RE: Disgruntled Linux User... questions about FreeBSD Cc: X-Sun-Charset: US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'd just like to say that as a longtime SUN user (Sun 2 workstations through current models have built in SCSI, video(sometimes) and ethernet on the motherboard), I've only encountered one system that had a defective onboard device. The ethernet on my SS1 died last year. That machine was purchased new in 1990 for 16K. It had *long* outlived its usefulness when the ethernet died. My experience is that onboard ethernet & scsi are just as reliable as add-on cards. As ethernet becomes ubiquitous in the pc world, most motherboards will incorporate it. Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 14 23:49:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA01766 for freebsd-current-outgoing; Tue, 14 Jul 1998 23:49:50 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ConSys.COM (ConSys.COM [209.141.107.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA01753 for ; Tue, 14 Jul 1998 23:49:48 -0700 (PDT) (envelope-from rcarter@pinyon.org) Received: (from pinyon@localhost) by ConSys.COM (8.8.6/8.8.6) id XAA09264; Tue, 14 Jul 1998 23:49:40 -0700 (MST) Date: Tue, 14 Jul 1998 23:49:40 -0700 (MST) From: "Russell L. Carter" Message-Id: <199807150649.XAA09264@ConSys.COM> To: joelh@gnu.org Subject: Re: aout / elf library directories Cc: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG |Is -current's /usr/lib/{aout,elf} going to persist for a while (which |would imply I should try to get this changed before release), or is it |a fairly temporary condition? What an interesting question! Russell To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 14 23:53:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA02562 for freebsd-current-outgoing; Tue, 14 Jul 1998 23:53:24 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from monk.via.net (monk.via.net [209.81.9.10]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id XAA02557 for ; Tue, 14 Jul 1998 23:53:24 -0700 (PDT) (envelope-from joe@via.net) Received: (from joe@localhost) by monk.via.net (8.6.11/8.6.12) id XAA25952; Tue, 14 Jul 1998 23:51:50 -0700 Date: Tue, 14 Jul 1998 23:51:50 -0700 From: Joe McGuckin Message-Id: <199807150651.XAA25952@monk.via.net> To: doconnor@gsoft.com.au Subject: Re: My kernel keeps hanging looking for root Cc: X-Sun-Charset: US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG My machine with a Symbios '875 controller behaves similar. Actually, it's not hung. An error is occuring in the driver & it eventually times out. It takes 3 or 4 minutes. Jul 13 13:28:34 www8 /kernel: ncr0:1: ERROR (90:0) (8-0-0) (0/5) @ (script 5b4:50000 000). Jul 13 13:28:34 www8 /kernel: ncr0: script cmd = 80000000 Jul 13 13:28:34 www8 /kernel: ncr0: regdump: de 00 00 05 47 00 0f 0f 35 08 81 00 90 00 0f 0a. Jul 13 13:28:34 www8 /kernel: ncr0: restart (fatal error). Jul 13 13:28:34 www8 /kernel: sd0(ncr0:0:0): COMMAND FAILED (9 ff) @f1073400. Jul 13 13:28:34 www8 /kernel: sd0(ncr0:0:0): WIDE SCSI (16 bit) enabledsd0(ncr0:0:0) : 40.0 MB/s (50 ns, offset 16) Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 14 23:57:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA03420 for freebsd-current-outgoing; Tue, 14 Jul 1998 23:57:54 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA03412 for ; Tue, 14 Jul 1998 23:57:51 -0700 (PDT) (envelope-from doconnor@cain.gsoft.com.au) Received: from cain (localhost [127.0.0.1]) by cain.gsoft.com.au (8.8.8/8.6.9) with ESMTP id QAA02863; Wed, 15 Jul 1998 16:27:28 +0930 (CST) Message-Id: <199807150657.QAA02863@cain.gsoft.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Joe McGuckin cc: doconnor@gsoft.com.au, current@FreeBSD.ORG Subject: Re: My kernel keeps hanging looking for root In-reply-to: Your message of "Tue, 14 Jul 1998 23:51:50 MST." <199807150651.XAA25952@monk.via.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 15 Jul 1998 16:27:28 +0930 From: "Daniel O'Connor" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > My machine with a Symbios '875 controller behaves similar. > Actually, it's not hung. An error is occuring in the driver & it > eventually times out. It takes 3 or 4 minutes. Hmm.. Well, I have an IDE drive :) It used to work for current around May :-/ --------------------------------------------------------------------- |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-current" in the body of the message From owner-freebsd-current Wed Jul 15 04:25:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA04577 for freebsd-current-outgoing; Wed, 15 Jul 1998 04:25:05 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pop.asahi-net.or.jp (pop.asahi-net.or.jp [202.224.39.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA04537 for ; Wed, 15 Jul 1998 04:24:57 -0700 (PDT) (envelope-from tfuruya@ppp142059.asahi-net.or.jp) Received: from galois.tf.or.jp (ppp142059.asahi-net.or.jp [202.213.142.59]) by pop.asahi-net.or.jp (8.8.8/3.6W) with ESMTP id UAA40986; Wed, 15 Jul 1998 20:30:25 +0900 Received: from galois.tf.or.jp (localhost.tf.or.jp [127.0.0.1]) by galois.tf.or.jp (8.8.8/3.6W-ht5t-fry@asahi-net-98042218) with ESMTP id UAA11631; Wed, 15 Jul 1998 20:24:14 +0900 (JST) Message-Id: <199807151124.UAA11631@galois.tf.or.jp> To: mbriggs@switchboard.net Cc: freebsd-current@FreeBSD.ORG Cc: Tetsuro FURUYA Subject: Re: MAXUSERS kernel compile problem From: Tetsuro FURUYA Reply-To: Tetsuro FURUYA In-Reply-To: Your message of "Tue, 14 Jul 1998 15:12:39 -0400" References: <35ABADA7.C111A65C@switchboard.net> X-Mailer: Mew version 1.54 on Emacs 19.28.1, Mule 2.3 X-fingerprint: F1 BA 5F C1 C2 48 1D C7 AE 5F 16 ED 12 17 75 38 X-URL: http://sodan.komaba.ecc.u-tokyo.ac.jp/~tfuruya/ Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Wed, 15 Jul 1998 20:24:14 +0900 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In Message-ID: <35ABADA7.C111A65C@switchboard.net> "Matthew R. Briggs" wrote: > Hello, > A kernel compile has been doing this to me for the past two days > (despite repeated cvsups). It happens on my custom config file as well > as LINT: > __________ > > cc -c -O -pipe -Wreturn-type -Wcomment -Wredundant-decls -W > implicit -Wnested-externs -Wstrict-prototypes -Wmissing-pr > ototypes -Wpointer-arith -Winline -Wuninitialized -ansi -g > -nostdinc -I- -I. -I../.. -I../../../include -DKERNEL -in > clude opt_global.h param.c > param.c:76: `MAXUSERS' undeclared here (not in a function) > param.c:76: initializer element is not constant > param.c:77: `MAXUSERS' undeclared here (not in a function) > param.c:77: initializer element is not constant So, you cannot compile param.c. You had better check like this, cd /usr/src/sys; egrep -aRi 'maxusers' conf i386/conf ======================================================================== FAX: 048-858-1597 E-Mail: ht5t-fry@asahi-net.or.jp , tfu@ff.iij4u.or.jp pgp-fingerprint: pub Tetsuro FURUYA Key fingerprint = F1 BA 5F C1 C2 48 1D C7 AE 5F 16 ED 12 17 75 38 ========================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 15 06:35:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA17843 for freebsd-current-outgoing; Wed, 15 Jul 1998 06:35:32 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pop02.globecomm.net (pop02.globecomm.net [207.51.48.186]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA17836 for ; Wed, 15 Jul 1998 06:35:29 -0700 (PDT) (envelope-from mbriggs@switchboard.net) Received: from switchboard.net (gw2.iridium.com [208.226.76.6]) by pop02.globecomm.net (8.8.8/8.8.0) with ESMTP id JAA12484; Wed, 15 Jul 1998 09:35:15 -0400 (EDT) Message-ID: <35ACB008.9EC2C127@switchboard.net> Date: Wed, 15 Jul 1998 09:35:04 -0400 From: "Matthew R. Briggs" X-Mailer: Mozilla 4.04 [en] (Win95; I) MIME-Version: 1.0 To: Tetsuro FURUYA CC: freebsd-current@FreeBSD.ORG Subject: Re: MAXUSERS kernel compile problem References: <35ABADA7.C111A65C@switchboard.net> <199807151124.UAA11631@galois.tf.or.jp> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Tetsuro FURUYA wrote: > > In Message-ID: <35ABADA7.C111A65C@switchboard.net> > "Matthew R. Briggs" wrote: > > > Hello, > > A kernel compile has been doing this to me for the past two days > > (despite repeated cvsups). It happens on my custom config file as well > > as LINT: > > __________ > > > > cc -c -O -pipe -Wreturn-type -Wcomment -Wredundant-decls -W > > implicit -Wnested-externs -Wstrict-prototypes -Wmissing-pr > > ototypes -Wpointer-arith -Winline -Wuninitialized -ansi -g > > -nostdinc -I- -I. -I../.. -I../../../include -DKERNEL -in > > clude opt_global.h param.c > > param.c:76: `MAXUSERS' undeclared here (not in a function) > > param.c:76: initializer element is not constant > > param.c:77: `MAXUSERS' undeclared here (not in a function) > > param.c:77: initializer element is not constant > > So, you cannot compile param.c. > You had better check like this, > > cd /usr/src/sys; egrep -aRi 'maxusers' conf i386/conf > Hi, I just cvsupped (9:15AM EDT) and ran into the same problem. Here is the output of the grep you suggested: _______ su-2.02# cd /usr/src/sys; egrep -aRi 'maxusers' conf i386/conf conf/options:MAXUSERS opt_param.h conf/param.c: * Compiled with -DMAXUSERS=xx conf/param.c:#define NPROC (20 + 16 * MAXUSERS) conf/param.c:#define NMBCLUSTERS (512 + MAXUSERS *16) i386/conf/GENERIC:maxusers 10 i386/conf/LINT:# The `maxusers' parameter controls the static sizing of a number of i386/conf/LINT:maxusers 10 i386/conf/LKM:maxusers 2 i386/conf/PCCARD:maxusers 10 i386/conf/SMP-GENERIC:maxusers 10 i386/conf/ANGELICA-SMP:maxusers 10 _______ ANGELICA-SMP is my config file, and it is very similar to SMP-GENERIC. I'll save bandwith and not post it unless you think it interesting. compiling param.c by hand with the additional flag -DMAXUSERS=10 seems to fix the problem, so it looks like Makefile breakage. I'll see if I can track it down. Matt Briggs mbriggs@switchboard.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 15 06:47:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA19325 for freebsd-current-outgoing; Wed, 15 Jul 1998 06:47:41 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bright.ny.otec.com (bright.ny.otec.com [209.3.16.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA19316 for ; Wed, 15 Jul 1998 06:47:38 -0700 (PDT) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.ny.otec.com (8.8.8/8.8.8) with SMTP id JAA00375 for ; Wed, 15 Jul 1998 09:47:44 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.ny.otec.com: bright owned process doing -bs Date: Wed, 15 Jul 1998 09:47:43 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.ny.otec.com To: current@FreeBSD.ORG Subject: repeatable crash with softupdates Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I recently enabled softupdates on every filesystem but root. i can cause a crash by running the x11 version of cvsup to download the source tree. this happens just about every time. i enabled crashdumps to my swap device and ran savecore, but my limited cluefullness hasn't figured me out a way to actually examine what happened, all i saw was that the kernel had panic'd from a page fault. the kernel i'm running is from ~noon yesterday. what can i do to provide more info about this to the developers? what information would be useful? (i didn't want to just randomly attach my config file, dmesg and whatnot without asking first) also, it seems i have had a bunch of crashes before the softupdates went into my kernel but these were few and far between ( well every 3-6 days ) although it might been the punks at the office rebooting me for other stuff. :) these new crashes are produceable right after a reboot though. thank you, -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 15 07:17:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA22766 for freebsd-current-outgoing; Wed, 15 Jul 1998 07:17:21 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bright.ny.otec.com (bright.ny.otec.com [209.3.16.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA22760 for ; Wed, 15 Jul 1998 07:17:19 -0700 (PDT) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.ny.otec.com (8.8.8/8.8.8) with SMTP id KAA00340 for ; Wed, 15 Jul 1998 10:17:23 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.ny.otec.com: bright owned process doing -bs Date: Wed, 15 Jul 1998 10:17:23 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.ny.otec.com To: current@FreeBSD.ORG Subject: (got the trace) repeatable crash with softupdates In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I recently enabled softupdates on every filesystem but root. > > i can cause a crash by running the x11 version of cvsup to download the > source tree. > > this happens just about every time. ...blah blah... Elvind told me how to get a trace and the panic info, thanks -Alfred here's the crash info: bright# gdb -k kernel.0 vmcore.0 GDB is free software and you are welcome to distribute copies of it under certain conditions; type "show copying" to see the conditions. There is absolutely no warranty for GDB; type "show warranty" for details. GDB 4.16 (i386-unknown-freebsd), Copyright 1996 Free Software Foundation, Inc...(no debugging symbols found)... IdlePTD 2498560 initial pcb at 233dcc panicstr: page fault panic messages: --- Fatal trap 12: page fault while in kernel mode fault virtual address = 0xefdd1bd8 fault code = supervisor read, page not present instruction pointer = 0x8:0xf01a19a5 stack pointer = 0x10:0xf0220df8 frame pointer = 0x10:0xf0220e2c 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 trap number = 12 panic: page fault syncing disks... Fatal trap 12: page fault while in kernel mode fault virtual address = 0x30 fault code = supervisor read, page not present instruction pointer = 0x8:0xf01c1068 stack pointer = 0x10:0xf0220b3c frame pointer = 0x10:0xf0220b40 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 trap number = 12 panic: page fault dumping to dev 40001, offset 352256 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 0xf0119a77 in boot () (kgdb) bt #0 0xf0119a77 in boot () #1 0xf0119d46 in panic () #2 0xf01ed81d in trap_fatal () #3 0xf01ed2b0 in trap_pfault () #4 0xf01ecf47 in trap () #5 0xf01c1068 in acquire_lock () #6 0xf01c4847 in initiate_write_inodeblock () #7 0xf01c4437 in softdep_disk_io_initiation () #8 0xf01486fa in spec_strategy () #9 0xf0147e19 in spec_vnoperate () #10 0xf01d036d in ufs_vnoperatespec () #11 0xf013534d in bwrite () #12 0xf0139b46 in vop_stdbwrite () #13 0xf0139981 in vop_defaultop () #14 0xf0147e19 in spec_vnoperate () #15 0xf01d036d in ufs_vnoperatespec () #16 0xf0135de7 in vfs_bio_awrite () #17 0xf01c9ff7 in ffs_fsync () #18 0xf01c84a7 in ffs_sync () #19 0xf013e1f7 in sync () #20 0xf011992b in boot () #21 0xf0119d46 in panic () #22 0xf01ed81d in trap_fatal () #23 0xf01ed2b0 in trap_pfault () #24 0xf01ecf47 in trap () #25 0xf01a19a5 in tulip_txput () #26 0xf01a1f8d in tulip_ifstart_one () #27 0xf01535fc in ether_output () #28 0xf0163e64 in ip_output () #29 0xf0168671 in tcp_output () #30 0xf01696af in tcp_timers () #31 0xf01694c4 in tcp_slowtimo () #32 0xf012db33 in pfslowtimo () #33 0xf011e293 in softclock () (kgdb) dmesg: Copyright (c) 1992-1998 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-CURRENT #6: Thu Jul 2 14:36:20 EST 1998 bright@bright.ny.otec.com:/usr/src/sys/compile/bright Timecounter "i8254" frequency 1193182 Hz cost 3031 ns CPU: Pentium II (300.01-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x634 Stepping=4 Features=0x80f9ff real memory = 134217728 (131072K bytes) avail memory = 127868928 (124872K bytes) Probing for devices on PCI bus 0: chip0: rev 0x03 on pci0.0.0 chip1: rev 0x03 on pci0.1.0 chip2: rev 0x02 on pci0.7.0 ide_pci0: rev 0x01 on pci0.7.1 chip3: rev 0x01 int d irq 11 on pci0.7.2 chip4: rev 0x02 on pci0.7.3 de0: rev 0x11 int a irq 10 on pci0.13.0 de0: 21041 [10Mb/s] pass 1.1 de0: address 00:40:33:91:13:8c vga0: rev 0x00 int a irq 9 on pci0.14.0 Probing for devices on PCI bus 1: Probing for PnP devices: CSN 1 Vendor ID: YMH0030 [0x3000a865] Serial 0x80860001 mss_attach 1 at 0x530 irq 5 dma 0:1 flags 0x11 pcm1 (CS423x/Yamaha sn 0x80860001) at 0x530-0x537 irq 5 drq 0 flags 0x11 on isa Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1: configured irq 3 not in bitmap of probed irqs 0 sio1 not found at 0x2f8 psm0 at 0x60-0x64 irq 12 on motherboard psm0: model Generic PS/2 mouse, device ID 0 pcm0 not found fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): wd0: 8063MB (16514064 sectors), 16383 cyls, 16 heads, 63 S/T, 512 B/S wdc1 at 0x170-0x177 irq 15 on isa wdc1: unit 0 (atapi): , removable, dma, iordy wcd0: 2412/5512Kb/sec, 256Kb cache, audio play, 256 volume levels, ejectable tray wcd0: no disc inside, unlocked npx0 on motherboard npx0: INT 16 interface ppc0 at 0x378 irq 7 on isa ppc0: Generic chipset in PS/2 mode ppi0: on ppbus 0 de0: enabling 10baseT port changing root device to wd0s3a To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 15 07:25:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA24070 for freebsd-current-outgoing; Wed, 15 Jul 1998 07:25:39 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from shrimp.dataplex.net (shrimp.dataplex.net [208.2.87.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA24037 for ; Wed, 15 Jul 1998 07:25:31 -0700 (PDT) (envelope-from rkw@dataplex.net) Received: from [208.2.87.10] (user10.dataplex.net [208.2.87.10]) by shrimp.dataplex.net (8.8.8/8.8.5) with ESMTP id JAA23952; Wed, 15 Jul 1998 09:25:14 -0500 (CDT) X-Sender: rkw@mail.dataplex.net Message-Id: In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 15 Jul 1998 09:24:23 -0500 To: Alfred Perlstein From: Richard Wackerbarth Subject: Re: repeatable crash with softupdates Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 9:47 AM -0500 7/15/98, Alfred Perlstein wrote: >I recently enabled softupdates on every filesystem but root. > >i can cause a crash by running the x11 version of cvsup to download the >source tree. > >this happens just about every time. Which NIC do you have? Does the same kernel crash with softupdates turned off? Richard Wackerbarth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 15 07:37:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA25401 for freebsd-current-outgoing; Wed, 15 Jul 1998 07:37:50 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bright.ny.otec.com (bright.ny.otec.com [209.3.16.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA25383 for ; Wed, 15 Jul 1998 07:37:45 -0700 (PDT) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.ny.otec.com (8.8.8/8.8.8) with SMTP id KAA25293 for ; Wed, 15 Jul 1998 10:37:55 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.ny.otec.com: bright owned process doing -bs Date: Wed, 15 Jul 1998 10:37:55 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.ny.otec.com To: current@FreeBSD.ORG Subject: Re: repeatable crash with softupdates In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG my crash info should have hit the lists already (panic and backtrace and dmesg) so i'm not going to repost it. unfortunatly i had already cvsup'd over the kernel i had compiled, my "stable" kernel (without softupdates) is: FreeBSD bright.ny.otec.com 3.0-CURRENT FreeBSD 3.0-CURRENT #6: Thu Jul 2 14:36:20 EST 1998 bright@bright.ny.otec.com:/usr/src/sys/compile/bright i386 my bad kernel is: -r-xr-xr-x 1 root wheel 1464261 Jul 14 17:08 /kernel (compiled july 14th) i'm going to compile a kernel with and without softupdates and test them later, but i've REALLY got to get to work right now, more later. thank you, Alfred On Wed, 15 Jul 1998, Richard Wackerbarth wrote: > At 9:47 AM -0500 7/15/98, Alfred Perlstein wrote: > >I recently enabled softupdates on every filesystem but root. > > > >i can cause a crash by running the x11 version of cvsup to download the > >source tree. > > > >this happens just about every time. > > Which NIC do you have? Does the same kernel crash with softupdates turned off? > > Richard Wackerbarth > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 15 08:11:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA29999 for freebsd-current-outgoing; Wed, 15 Jul 1998 08:11:02 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from localhost.ziplink.net (mi@kot.ne.mediaone.net [24.128.29.55]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA29968 for ; Wed, 15 Jul 1998 08:10:52 -0700 (PDT) (envelope-from mi@rtfm.ziplink.net) Received: from rtfm.ziplink.net (mi@rtfm [199.232.255.52]) by localhost.ziplink.net (8.8.8/8.8.7) with ESMTP id PAA00327 for ; Wed, 15 Jul 1998 15:10:34 GMT (envelope-from mi@rtfm.ziplink.net) Received: (from mi@localhost) by rtfm.ziplink.net (8.8.8/8.8.5) id LAA00382 for current@freebsd.org; Wed, 15 Jul 1998 11:10:36 -0400 (EDT) From: Mikhail Teterin Message-Id: <199807151510.LAA00382@rtfm.ziplink.net> Subject: Re: CAM on a -current branch In-Reply-To: <19980715073539.A11287@klemm.gtn.com> from "Andreas Klemm" at "Jul 15, 98 07:35:39 am" To: current@FreeBSD.ORG Date: Wed, 15 Jul 1998 11:10:36 -0400 (EDT) X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli" Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA21598 for freebsd-current-outgoing; Wed, 15 Jul 1998 10:56:29 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gate.ljis.ml.org (cyberworld.demon.co.uk [158.152.125.109]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA21584; Wed, 15 Jul 1998 10:56:25 -0700 (PDT) (envelope-from ljohnston@cyberworld.demon.co.uk) Received: (from ljohnston@localhost) by gate.ljis.ml.org (8.8.8/8.8.8) id SAA01171; Wed, 15 Jul 1998 18:55:22 +0100 (BST) (envelope-from ljohnston) Message-ID: <19980715185522.B733@ljis.ml.org> Date: Wed, 15 Jul 1998 18:55:22 +0100 From: Lee Johnston To: Brandon Lockhart , David Greenman Cc: Jeremy Domingue , current@FreeBSD.ORG, stable@FreeBSD.ORG, questions@FreeBSD.ORG Subject: Re: Disgruntled Linux User... questions about FreeBSD References: <199807141511.IAA18210@implode.root.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from Brandon Lockhart on Tue, Jul 14, 1998 at 07:56:28PM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jul 14, 1998 at 07:56:28PM -0400, Brandon Lockhart wrote: > What are you talking about, I was talking about for a HIGHLY used server, > as in, more then cdrom.com, and I was talking about a REAL server, not a > PC supped up. I am talking about a rack mount server, a REAL server. > Which in case you where out of the loop, most REAL servers use RISC. More than ftp.cdrom.com? I thought ftp.cdrom.com was one of the busiest if not _THE_ busiest FTP Server on the Internet. What servers are you talking about? Lee. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 15 11:24:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA27361 for freebsd-current-outgoing; Wed, 15 Jul 1998 11:24:31 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.westbend.net (ns1.westbend.net [207.217.224.194]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA27352 for ; Wed, 15 Jul 1998 11:24:24 -0700 (PDT) (envelope-from hetzels@westbend.net) Received: from admin (admin.westbend.net [207.217.224.195]) by mail.westbend.net (8.8.8/8.8.8) with SMTP id NAA03988; Wed, 15 Jul 1998 13:24:12 -0500 (CDT) (envelope-from hetzels@westbend.net) Message-ID: <036401bdb01d$c4139600$c3e0d9cf@westbend.net> From: "Scot W. Hetzel" To: Cc: "FreeBSD-Current" Subject: Re: aout / elf library directories Date: Wed, 15 Jul 1998 13:24:11 -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.0518.4 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.0518.4 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From: Joel Ray Holveck >A new Emacs is being tested for release, and I'm looking at one line >in the FreeBSD-specific configuration file: > > #define START_FILES pre-crt0.o /usr/lib/crt0.o > >Is -current's /usr/lib/{aout,elf} going to persist for a while (which >would imply I should try to get this changed before release), or is it >a fairly temporary condition? > Don't know how long it's going to persist, but it will most likely persist through the 3.0 RELEASES. Previous messages have stated that aout libraries were to be placed in /usr/lib/aout, and elf libraries in /usr/lib. You'll probably need something like the following: #if (defined __FreeBSD__ >= 3 ) && ( __FreeBSD_version >= 300003 ) && !defined(BINFORMAT) || ( BINFORMAT == aout )) #Allow the build to work on 3.0-CURRENT w/aout libraries #define START_FILES pre-crt0.o /usr/lib/aout/crt0.o #else # Allow the build to work on 3.0-CURRENT w/elf libraries # or 2.x w/aout libraries #define START_FILES pre-crt0.o /usr/lib/crt0.o #endif Scot To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 15 11:53:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA00912 for freebsd-current-outgoing; Wed, 15 Jul 1998 11:53:08 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from uni-sb.de (uni-sb.de [134.96.252.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA00873 for ; Wed, 15 Jul 1998 11:53:02 -0700 (PDT) (envelope-from rock@wurzelausix.cs.uni-sb.de) Received: from cs.uni-sb.de (cs.uni-sb.de [134.96.252.31]) by uni-sb.de (8.9.0/1998052000) with ESMTP id UAA14888 for ; Wed, 15 Jul 1998 20:52:46 +0200 (CEST) Received: from gate.ics (acc2-212.telip.uni-sb.de [134.96.112.212]) by cs.uni-sb.de (8.9.0/1998060300) with ESMTP id UAA17758 for ; Wed, 15 Jul 1998 20:52:45 +0200 (CEST) Received: from doom.ics (doom.ics [192.168.0.254]) by gate.ics (8.9.0/1998061600) with ESMTP id UAA09563 for ; Wed, 15 Jul 1998 20:51:13 +0200 (CEST) Received: (from rock@localhost) by doom.ics (8.9.0/1998061600) id UAA13471; Wed, 15 Jul 1998 20:56:56 +0200 (CEST) From: "D. Rock" MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Wed, 15 Jul 1998 20:56:56 +0200 (CEST) To: current@FreeBSD.ORG Subject: Bug in kernel disklabel code? X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <13740.64305.837054.908108@doom.ics> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG There seems to be bug in the disklabel kernel code. I recently deleted an FreeBSD partition and created a DOS partition instead (with DOS fdisk). Because this is the 2nd DOS partition on the same drive an extended partition was created with an DOS drive in it. Because the extended partition is just "a disk drive by itself", the first (logical) head wasn't overwritten (besides the partition table). It seems the disklabel code finds a FreeBSD disklabel in it and tries to use it, although the partition type isn't FreeBSD: wd0s2: raw partition size != slice size wd0s2: start 6602715, end 9735389, size 3132675 wd0s2c: start 6602715, end 9767519, size 3164805 wd0s2: truncating raw partition wd0s2: rejecting partition in BSD label: it isn't entirely within the slice wd0s2: start 6602715, end 9735389, size 3132675 wd0s2a: start 6602715, end 9767519, size 3164805 It is rejecting them, but what if the partition sizes were slightly different (creating a DOS partition larger than the initial BSD partition(*))? Shouldn't the disklabel code look first at the partition ID? (*) The DOS partition is "magically" smaller than the BSD partition before. DOS fdisk didn't use the entire disk, but "forgot" the last 2 cylinders: ******* Working on device /dev/rwd0 ******* parameters extracted from in-core disklabel are: cylinders=608 heads=255 sectors/track=63 (16065 blks/cyl) parameters to be used for BIOS calculations are: cylinders=608 heads=255 sectors/track=63 (16065 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 11,(DOS or Windows 95 with 32 bit FAT) start 63, size 6602652 (3223 Meg), flag 0 beg: cyl 0/ sector 1/ head 1; end: cyl 410/ sector 63/ head 254 The data for partition 2 is: sysid 5,(Extended DOS) start 6602715, size 3132675 (1529 Meg), flag 0 beg: cyl 411/ sector 1/ head 0; end: cyl 605/ sector 63/ head 254 The data for partition 3 is: The data for partition 4 is: Daniel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 15 11:53:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA01015 for freebsd-current-outgoing; Wed, 15 Jul 1998 11:53:39 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from uni-sb.de (uni-sb.de [134.96.252.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA01006 for ; Wed, 15 Jul 1998 11:53:29 -0700 (PDT) (envelope-from rock@wurzelausix.cs.uni-sb.de) Received: from cs.uni-sb.de (cs.uni-sb.de [134.96.252.31]) by uni-sb.de (8.9.0/1998052000) with ESMTP id UAA14892 for ; Wed, 15 Jul 1998 20:52:48 +0200 (CEST) Received: from gate.ics (acc2-212.telip.uni-sb.de [134.96.112.212]) by cs.uni-sb.de (8.9.0/1998060300) with ESMTP id UAA17761; Wed, 15 Jul 1998 20:52:46 +0200 (CEST) Received: from doom.ics (doom.ics [192.168.0.254]) by gate.ics (8.9.0/1998061600) with ESMTP id UAA09543; Wed, 15 Jul 1998 20:50:00 +0200 (CEST) Received: (from rock@localhost) by doom.ics (8.9.0/1998061600) id UAA13453; Wed, 15 Jul 1998 20:55:44 +0200 (CEST) From: "D. Rock" MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Date: Wed, 15 Jul 1998 20:55:43 +0200 (CEST) To: current@FreeBSD.ORG, rock@cs.uni-sb.de Subject: Re: softupdates and / In-Reply-To: <199806231530.LAA00998@lor.watermarkgroup.com> References: <199806231530.LAA00998@lor.watermarkgroup.com> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <13740.63488.73527.611486@doom.ics> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Luoqi Chen writes: > > Hi, > > > > I had some (hardware related) crashes lately and noticed that > > softupdates aren´t enabled if the filesystem was unclean. So after a > > crash I had to boot twice to re-enable softupdates on / again (no need > > to run tunefs though). > > Is this because soft updates are no mount option and so cannot be > > enabled later and soft updates aren´t enabled on an unclean fs for > > safety reasons? > > Or is this just a bug? > > > > Daniel > > > I believe this is a bug. After fsck fixes inconsistencies on the disk, > it will remount / with MNT_RELOAD flag to update the in-core superblock > image. For some reason, fsck might change fs_ronly flag in superblock > (to be more precise, it will change fs_ronly iff it has fixed the free > block count -- could any more knowledgeable person tell me why it is > doing that?!), and because of that, all the code to be called during > ro->rw update is bypassed, including enabling of softupdate. [patch deleted] OK, I saw the patch being integrated into current. But still my root fs doesn't get soft updates enabled after a crash. This is my system booted after a forced crash: % mount /dev/sd0s1a on / (local, writes: sync 54051 async 62742) /dev/wd2a on /data (local, soft-updates, writes: sync 126 async 24454) procfs on /proc (local) /dev/wd0s1 on /dos (local) mfs:23 on /tmp (asynchronous, local, writes: sync 30 async 380) After a 2nd reboot, soft updated are enabled again, so the flag is on the on-disk copy of the superblock correct. Daniel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 15 13:09:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA10039 for freebsd-current-outgoing; Wed, 15 Jul 1998 13:09:02 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bright.ny.otec.com (bright.ny.otec.com [209.3.16.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA10031 for ; Wed, 15 Jul 1998 13:09:00 -0700 (PDT) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.ny.otec.com (8.8.8/8.8.8) with SMTP id QAA20634; Wed, 15 Jul 1998 16:08:46 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.ny.otec.com: bright owned process doing -bs Date: Wed, 15 Jul 1998 16:08:46 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.ny.otec.com To: Richard Wackerbarth cc: current@FreeBSD.ORG Subject: Re: repeatable crash with softupdates In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hrm however my kernel from a few days back seems ok... i'm going to get an etherexpress PRO kinda soon hopefully. if anyone with the knowhow could take a look at the de driver i guess that makes 2 people seeing instability because of the code. thanks, -Alfred On Wed, 15 Jul 1998, Richard Wackerbarth wrote: > >my crash info should have hit the lists already (panic and backtrace and > >dmesg) so i'm not going to repost it. > > > >unfortunatly i had already cvsup'd over the kernel i had compiled, my > >"stable" kernel (without softupdates) is: > > > >FreeBSD bright.ny.otec.com 3.0-CURRENT FreeBSD 3.0-CURRENT #6: Thu Jul 2 > >14:36:20 EST 1998 > >bright@bright.ny.otec.com:/usr/src/sys/compile/bright i386 > > > >my bad kernel is: > >-r-xr-xr-x 1 root wheel 1464261 Jul 14 17:08 /kernel > >(compiled july 14th) > > > >i'm going to compile a kernel with and without softupdates and test them > >later, but i've REALLY got to get to work right now, more later. > > Rather than removing the softupdate code from the kernel, you should > first try simply disabling it with tunefs. > > I suspect that your problem is actually with the "de" driver. > (I'm having the same problem with cvsup (no X) and no softupdates.) > > >#25 0xf01a19a5 in tulip_txput () > >#26 0xf01a1f8d in tulip_ifstart_one () > > Richard Wackerbarth > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 15 14:02:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA15779 for freebsd-current-outgoing; Wed, 15 Jul 1998 14:02:09 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from top.worldcontrol.com (surf21.cruzers.com [205.215.232.21]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id OAA15774 for ; Wed, 15 Jul 1998 14:02:07 -0700 (PDT) (envelope-from brian@worldcontrol.com) From: brian@worldcontrol.com Received: (qmail 10815 invoked by uid 100); 15 Jul 1998 21:01:52 -0000 Message-ID: <19980715140148.A10804@top.worldcontrol.com> Date: Wed, 15 Jul 1998 14:01:48 -0700 To: freebsd-current@FreeBSD.ORG Subject: Where is F_LOCK defined? Mail-Followup-To: freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Where is F_LOCK or F_ULOCK defined? Thanks, -- Brian Litzinger To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 15 15:22:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA25463 for freebsd-current-outgoing; Wed, 15 Jul 1998 15:22:57 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from myrddin.demon.co.uk (exim@myrddin.demon.co.uk [158.152.54.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA25454; Wed, 15 Jul 1998 15:22:53 -0700 (PDT) (envelope-from dom@myrddin.demon.co.uk) Received: from dom by myrddin.demon.co.uk with local (Exim 1.92 #1) id 0ywLpN-0000MH-00; Wed, 15 Jul 1998 08:18:13 +0100 To: djv@bedford.net Cc: jer@hughes.net (Jeremy Domingue), current@FreeBSD.ORG, stable@FreeBSD.ORG, smp@FreeBSD.ORG, questions@FreeBSD.ORG Subject: Re: Disgruntled Linux User... questions about FreeBSD References: <199807132338.TAA02118@lucy.bedford.net> From: Dom Mitchell In-Reply-To: CyberPeasant's message of "Mon, 13 Jul 1998 19:38:41 -0400 (EDT)" X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald" Date: Wed, 15 Jul 1998 08:18:13 +0100 Message-Id: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG CyberPeasant writes: > The BSD's behave much more like a commercial Unix: No they don't; they crash less often and have more features. -- ``If make doesn't do what you expect it to, it's a good chance the makefile is wrong.'' -- Adam de Boor To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 15 15:28:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA26750 for freebsd-current-outgoing; Wed, 15 Jul 1998 15:28:28 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from phobos.muc.de (phobos.muc.de [193.174.4.45]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA26742 for ; Wed, 15 Jul 1998 15:28:15 -0700 (PDT) (envelope-from ras@phobos.muc.de) Received: (from ras@localhost) by phobos.muc.de (8.8.8/8.8.5) id AAA08114; Thu, 16 Jul 1998 00:25:23 +0200 (MET DST) Date: Thu, 16 Jul 1998 00:25:22 +0200 (MET DST) From: Rudolf Schreiner To: brian@worldcontrol.com cc: freebsd-current@FreeBSD.ORG Subject: Re: Where is F_LOCK defined? In-Reply-To: <19980715140148.A10804@top.worldcontrol.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 15 Jul 1998 brian@worldcontrol.com wrote: > Where is F_LOCK or F_ULOCK defined? That's SYSV style record locking, check lockf(3C) e.g. on Solaris 2.6. Lockf is not supported by BSD, I had the same problem when I ported SESAME to FreeBSD (2.2.6). I used the lockf function from glibc, it seems to work. Rudi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 15 15:48:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA29358 for freebsd-current-outgoing; Wed, 15 Jul 1998 15:48:12 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail1.its.rpi.edu (root@mail1.its.rpi.edu [128.113.100.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA29353 for ; Wed, 15 Jul 1998 15:48:10 -0700 (PDT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail1.its.rpi.edu (8.8.8/8.8.6) with ESMTP id SAA26104; Wed, 15 Jul 1998 18:47:43 -0400 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Sender: drosih@pop1.rpi.edu Message-Id: In-Reply-To: <19980715140148.A10804@top.worldcontrol.com> Date: Wed, 15 Jul 1998 18:51:41 -0400 To: brian@worldcontrol.com, freebsd-current@FreeBSD.ORG From: Garance A Drosihn Subject: Re: Where is F_LOCK defined? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 2:01 PM -0700 7/15/98, brian@worldcontrol.com wrote: > Where is F_LOCK or F_ULOCK defined? A quick (and quite possibly incomplete) search does not seem to find them under FreeBSD-stable or FreeBSD current. Under Solaris and IRIX they are both found in /usr/include/unistd.h. Under AIX they are in /usr/include/sys/lockf.h, and there is an include for that file in /usr/include/unistd.h. --- Garance Alistair Drosehn = gad@eclipse.its.rpi.edu Senior Systems Programmer or drosih@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 15 15:51:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA00283 for freebsd-current-outgoing; Wed, 15 Jul 1998 15:51:47 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pop.asahi-net.or.jp (pop.asahi-net.or.jp [202.224.39.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA00274 for ; Wed, 15 Jul 1998 15:51:43 -0700 (PDT) (envelope-from tfuruya@ppp142015.asahi-net.or.jp) Received: from galois.tf.or.jp (ppp142015.asahi-net.or.jp [202.213.142.15]) by pop.asahi-net.or.jp (8.8.8/3.6W) with ESMTP id HAA33184; Thu, 16 Jul 1998 07:57:12 +0900 Received: from galois.tf.or.jp (localhost.tf.or.jp [127.0.0.1]) by galois.tf.or.jp (8.8.8/3.6W-ht5t-fry@asahi-net-98042218) with ESMTP id HAA01326; Thu, 16 Jul 1998 07:51:10 +0900 (JST) Message-Id: <199807152251.HAA01326@galois.tf.or.jp> To: mbriggs@switchboard.net Cc: tfu@ff.iij4u.or.jp, freebsd-current@FreeBSD.ORG Subject: Re: MAXUSERS kernel compile problem From: Tetsuro FURUYA Reply-To: Tetsuro FURUYA In-Reply-To: Your message of "Wed, 15 Jul 1998 09:35:04 -0400" References: <35ACB008.9EC2C127@switchboard.net> X-Mailer: Mew version 1.54 on Emacs 19.28.1, Mule 2.3 X-fingerprint: F1 BA 5F C1 C2 48 1D C7 AE 5F 16 ED 12 17 75 38 X-URL: http://sodan.komaba.ecc.u-tokyo.ac.jp/~tfuruya/ Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Thu, 16 Jul 1998 07:51:09 +0900 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In Message-ID: <35ACB008.9EC2C127@switchboard.net> "Matthew R. Briggs" wrote: > Hi, > I just cvsupped (9:15AM EDT) and ran into the same problem. Here is > the output of the grep you suggested: > > _______ > > su-2.02# cd /usr/src/sys; egrep -aRi 'maxusers' conf i386/conf > conf/options:MAXUSERS opt_param.h For the first time I see this statement. When this statement comes to be generated ? So, how about you insert the following lines to config file. options MAXUSERS 10 or, MAXUSERS 10 Like other options in config file. > compiling param.c by hand with the additional flag -DMAXUSERS=10 seems > to fix the problem, so it looks like Makefile breakage. I'll see if I > can track it down. > > Matt Briggs > mbriggs@switchboard.net ======================================================================== FAX: 048-858-1597 E-Mail: ht5t-fry@asahi-net.or.jp , tfu@ff.iij4u.or.jp pgp-fingerprint: pub Tetsuro FURUYA Key fingerprint = F1 BA 5F C1 C2 48 1D C7 AE 5F 16 ED 12 17 75 38 ========================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 15 16:32:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA05093 for freebsd-current-outgoing; Wed, 15 Jul 1998 16:32:12 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA05086 for ; Wed, 15 Jul 1998 16:32:07 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id JAA25461; Thu, 16 Jul 1998 09:31:58 +1000 Date: Thu, 16 Jul 1998 09:31:58 +1000 From: Bruce Evans Message-Id: <199807152331.JAA25461@godzilla.zeta.org.au> To: current@FreeBSD.ORG, rock@cs.uni-sb.de Subject: Re: Bug in kernel disklabel code? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >I recently deleted an FreeBSD partition and created a DOS partition >instead (with DOS fdisk). Because this is the 2nd DOS partition on the >same drive an extended partition was created with an DOS drive in >it. Because the extended partition is just "a disk drive by itself", >the first (logical) head wasn't overwritten (besides the partition >table). It seems the disklabel code finds a FreeBSD disklabel in it >and tries to use it, although the partition type isn't FreeBSD: The "machine-independent" part of the disklabel code doesn't want to know about partition tables. It is supposed to see only logical drives and look for labels in them. This is wrong for extended partitions in the primary partition table, at least when extended partition is valid. There is no problem for nested extended partitions because slices for them aren't passed up to the machine-independent code. >wd0s2: raw partition size != slice size >wd0s2: start 6602715, end 9735389, size 3132675 >wd0s2c: start 6602715, end 9767519, size 3164805 >wd0s2: truncating raw partition >wd0s2: rejecting partition in BSD label: it isn't entirely within the slice >wd0s2: start 6602715, end 9735389, size 3132675 >wd0s2a: start 6602715, end 9767519, size 3164805 > >It is rejecting them, but what if the partition sizes were slightly >different (creating a DOS partition larger than the initial BSD >partition(*))? Shouldn't the disklabel code look first at the >partition ID? Nothing much happens if you don't use these partitions. They used to be normally unused (there is no good reason to access the slice for the extended partition), but now the slice initialization code attempts to find all labels on all slices so that it can create devfs device nodes. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 15 16:59:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA08215 for freebsd-current-outgoing; Wed, 15 Jul 1998 16:59:58 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA08210 for ; Wed, 15 Jul 1998 16:59:57 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id QAA02303 for ; Wed, 15 Jul 1998 16:58:48 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: current@FreeBSD.ORG Subject: /usr/src/sbin/i386/mount_msdos - can we move it already? Date: Wed, 15 Jul 1998 16:58:48 -0700 Message-ID: <2299.900547128@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It makes no sense to have this under i386 since I could just as easily have a DOS formatted partition I might want to read on my ALPHA. It should be up with the rest of the mount_foo programs. Unless there are no serious objections, I'll ask Peter to do a repository copy so we don't lose history on it. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 15 17:04:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA08847 for freebsd-current-outgoing; Wed, 15 Jul 1998 17:04:12 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pop.asahi-net.or.jp (pop.asahi-net.or.jp [202.224.39.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA08842 for ; Wed, 15 Jul 1998 17:04:10 -0700 (PDT) (envelope-from tfuruya@ppp142122.asahi-net.or.jp) Received: from galois.tf.or.jp (ppp142122.asahi-net.or.jp [202.213.142.122]) by pop.asahi-net.or.jp (8.8.8/3.6W) with ESMTP id JAA63066; Thu, 16 Jul 1998 09:09:39 +0900 Received: from galois.tf.or.jp (localhost.tf.or.jp [127.0.0.1]) by galois.tf.or.jp (8.8.8/3.6W-ht5t-fry@asahi-net-98042218) with ESMTP id JAA02327; Thu, 16 Jul 1998 09:03:36 +0900 (JST) Message-Id: <199807160003.JAA02327@galois.tf.or.jp> To: mbriggs@switchboard.net Cc: tfu@ff.iij4u.or.jp, freebsd-current@FreeBSD.ORG Subject: Re: MAXUSERS kernel compile problem From: Tetsuro FURUYA Reply-To: Tetsuro FURUYA In-Reply-To: Your message of "Thu, 16 Jul 1998 07:51:09 +0900" References: <199807152251.HAA01326@galois.tf.or.jp> X-Mailer: Mew version 1.54 on Emacs 19.28.1, Mule 2.3 X-fingerprint: F1 BA 5F C1 C2 48 1D C7 AE 5F 16 ED 12 17 75 38 X-URL: http://sodan.komaba.ecc.u-tokyo.ac.jp/~tfuruya/ Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Thu, 16 Jul 1998 09:03:36 +0900 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Mr. Matt Briggs In preveous mail, I have written that > > su-2.02# cd /usr/src/sys; egrep -aRi 'maxusers' conf i386/conf > > conf/options:MAXUSERS opt_param.h > > For the first time I see this statement. > When this statement comes to be generated ? > > So, how about you insert the following lines to config file. > > options MAXUSERS 10 > or, > MAXUSERS 10 > > Like other options in config file. > But, options MAXUSERS=10 must be right. As '=' is requitred in other options. Tetsuro, Furuya. ht5t-fry@asahi-net.or.jp ======================================================================== TEL: 048-852-3520 FAX: 048-858-1597 E-Mail: ht5t-fry@asahi-net.or.jp , tfu@ff.iij4u.or.jp pgp-fingerprint: pub Tetsuro FURUYA Key fingerprint = F1 BA 5F C1 C2 48 1D C7 AE 5F 16 ED 12 17 75 38 ========================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 15 17:06:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA09400 for freebsd-current-outgoing; Wed, 15 Jul 1998 17:06:03 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA09317 for ; Wed, 15 Jul 1998 17:06:00 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id KAA28109; Thu, 16 Jul 1998 10:05:50 +1000 Date: Thu, 16 Jul 1998 10:05:50 +1000 From: Bruce Evans Message-Id: <199807160005.KAA28109@godzilla.zeta.org.au> To: ht5t-fry@asahi-net.or.jp, mbriggs@switchboard.net Subject: Re: MAXUSERS kernel compile problem Cc: freebsd-current@FreeBSD.ORG, tfu@ff.iij4u.or.jp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> su-2.02# cd /usr/src/sys; egrep -aRi 'maxusers' conf i386/conf >> conf/options:MAXUSERS opt_param.h > >For the first time I see this statement. >When this statement comes to be generated ? > >So, how about you insert the following lines to config file. > >options MAXUSERS 10 >or, >MAXUSERS 10 > >Like other options in config file. MAXUSERS isn't a standard option. It is specified by the maxusers directive, which is converted to a #define of MAXUSERS by current versions of config(8). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 15 17:56:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA16004 for freebsd-current-outgoing; Wed, 15 Jul 1998 17:56:22 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from indigo.ie (nsmart@ts03-117.dublin.indigo.ie [194.125.148.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA15999 for ; Wed, 15 Jul 1998 17:56:19 -0700 (PDT) (envelope-from rotel@indigo.ie) Received: (from nsmart@localhost) by indigo.ie (8.8.8/8.8.7) id BAA02792 for freebsd-current@freebsd.org; Thu, 16 Jul 1998 01:51:47 +0100 (IST) (envelope-from rotel@indigo.ie) From: Niall Smart Message-Id: <199807160051.BAA02792@indigo.ie> Date: Thu, 16 Jul 1998 01:51:47 +0000 Reply-To: rotel@indigo.ie X-Files: The truth is out there X-Mailer: Mail User's Shell (7.2.6 beta(3) 11/17/96) To: freebsd-current@FreeBSD.ORG Subject: Re those MAXUSERS troubles Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, When I recompiled config from fresh sources that problem went away. Niall -- Niall Smart. PGP: finger njs3@motmot.doc.ic.ac.uk FreeBSD: Turning PC's into Workstations: www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 15 18:41:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA22311 for freebsd-current-outgoing; Wed, 15 Jul 1998 18:41:11 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from uni-sb.de (uni-sb.de [134.96.252.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA22305 for ; Wed, 15 Jul 1998 18:41:06 -0700 (PDT) (envelope-from rock@wurzelausix.cs.uni-sb.de) Received: from cs.uni-sb.de (cs.uni-sb.de [134.96.252.31]) by uni-sb.de (8.9.0/1998052000) with ESMTP id DAA18102 for ; Thu, 16 Jul 1998 03:40:57 +0200 (CEST) Received: from gate.ics (acc1-176.telip.uni-sb.de [134.96.113.176]) by cs.uni-sb.de (8.9.0/1998060300) with ESMTP id DAA24886 for ; Thu, 16 Jul 1998 03:40:56 +0200 (CEST) Received: from doom.ics (doom.ics [192.168.0.254]) by gate.ics (8.9.0/1998061600) with ESMTP id DAA14588 for ; Thu, 16 Jul 1998 03:39:47 +0200 (CEST) Received: (from rock@localhost) by doom.ics (8.9.0/1998061600) id DAA00399; Thu, 16 Jul 1998 03:45:17 +0200 (CEST) From: "D. Rock" MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Date: Thu, 16 Jul 1998 03:45:17 +0200 (CEST) To: current@FreeBSD.ORG Subject: Re: softupdates and / In-Reply-To: <13740.63488.73527.611486@doom.ics> References: <199806231530.LAA00998@lor.watermarkgroup.com> <13740.63488.73527.611486@doom.ics> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <13741.22887.960238.966148@doom.ics> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Luoqi Chen writes: > > > Hi, > > > > > > I had some (hardware related) crashes lately and noticed that > > > softupdates aren´t enabled if the filesystem was unclean. So after a > > > crash I had to boot twice to re-enable softupdates on / again (no need > > > to run tunefs though). > > > Is this because soft updates are no mount option and so cannot be > > > enabled later and soft updates aren´t enabled on an unclean fs for > > > safety reasons? > > > Or is this just a bug? > > > > > > Daniel > > > > > I believe this is a bug. After fsck fixes inconsistencies on the disk, > > it will remount / with MNT_RELOAD flag to update the in-core superblock > > image. For some reason, fsck might change fs_ronly flag in superblock > > (to be more precise, it will change fs_ronly iff it has fixed the free > > block count -- could any more knowledgeable person tell me why it is > > doing that?!), and because of that, all the code to be called during > > ro->rw update is bypassed, including enabling of softupdate. F'upd my own mail. I just forgot to mention: At least 2 times, after a crash, the root fs was noted "clean" during the reboot (but not my other UFS partition) and no fsck required (and now of course with soft updates enabled). I didn't trust the information (does the superblock gets updated while being mounted or does it have a "stable" flag similar to Sun's UFS?)After rebooting again in single user mode and doing a forced fsck of / an error was indeed found ("LINK COUNT INCREASING"). Probably it wasn't more because the system was almost idle while it crashed. Daniel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 15 18:57:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA24074 for freebsd-current-outgoing; Wed, 15 Jul 1998 18:57:11 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: (from jmb@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA24068 for current; Wed, 15 Jul 1998 18:57:10 -0700 (PDT) (envelope-from jmb) From: "Jonathan M. Bresler" Message-Id: <199807160157.SAA24068@hub.freebsd.org> Subject: DPT raid controllers To: current Date: Wed, 15 Jul 1998 18:57:10 -0700 (PDT) X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG how's our support for DPT raid controllers. looking for people with DPT raid controllers in service. both success and horror stories welcome. a client wants to use one on a 2.2.6 box. is an upgrade to -current required? jmb -- Jonathan M. Bresler FreeBSD Core Team, Postmaster jmb@FreeBSD.ORG FreeBSD--The Power to Serve http://www.freebsd.org/ PGP 2.6.2 Fingerprint: 31 57 41 56 06 C1 40 13 C5 1C E3 E5 DC 62 0E FB ~ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 15 19:58:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA01211 for freebsd-current-outgoing; Wed, 15 Jul 1998 19:58:34 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id TAA01203; Wed, 15 Jul 1998 19:58:32 -0700 (PDT) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 0yweFT-00040V-00; Wed, 15 Jul 1998 19:58:23 -0700 Date: Wed, 15 Jul 1998 19:58:19 -0700 (PDT) From: Tom X-Sender: tom@shell.uniserve.ca To: "Jonathan M. Bresler" cc: current@hub.freebsd.org Subject: Re: DPT raid controllers In-Reply-To: <199807160157.SAA24068@hub.freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 15 Jul 1998, Jonathan M. Bresler wrote: > > how's our support for DPT raid controllers. > looking for people with DPT raid controllers in service. > both success and horror stories welcome. Sucessful. I've been using one a mail server for almost a year now (running 2.2). > a client wants to use one on a 2.2.6 box. Driver is included with 2.2.6, just compile it in. > is an upgrade to -current required? > > jmb > -- > Jonathan M. Bresler FreeBSD Core Team, Postmaster jmb@FreeBSD.ORG > FreeBSD--The Power to Serve http://www.freebsd.org/ > PGP 2.6.2 Fingerprint: 31 57 41 56 06 C1 40 13 C5 1C E3 E5 DC 62 0E FB Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 15 20:38:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA06083 for freebsd-current-outgoing; Wed, 15 Jul 1998 20:38:07 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from locnar.336.net (root@locnar.336.net [207.69.181.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA06074; Wed, 15 Jul 1998 20:38:04 -0700 (PDT) (envelope-from sevn@336.net) Received: from locnar.336.net (sevn@locnar.336.net [207.69.181.130]) by locnar.336.net (8.8.8/8.8.8) with SMTP id XAA10370; Wed, 15 Jul 1998 23:38:21 -0400 (EDT) (envelope-from sevn@336.net) Date: Wed, 15 Jul 1998 23:38:21 -0400 (EDT) From: Scott To: "Jonathan M. Bresler" cc: current@hub.freebsd.org Subject: Re: DPT raid controllers In-Reply-To: <199807160157.SAA24068@hub.freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The driver is excellent. It's maintained by Simon Shapiro, who I am lucky enough to work with. Scott Wilson Engineer/Sysadmin MindSpring Enterprises Portable, adj.: Survives system reboot. On Wed, 15 Jul 1998, Jonathan M. Bresler wrote: > > how's our support for DPT raid controllers. > looking for people with DPT raid controllers in service. > both success and horror stories welcome. > > a client wants to use one on a 2.2.6 box. > > is an upgrade to -current required? > > jmb > -- > Jonathan M. Bresler FreeBSD Core Team, Postmaster jmb@FreeBSD.ORG > FreeBSD--The Power to Serve http://www.freebsd.org/ > PGP 2.6.2 Fingerprint: 31 57 41 56 06 C1 40 13 C5 1C E3 E5 DC 62 0E FB > ~ > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 15 21:01:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA08312 for freebsd-current-outgoing; Wed, 15 Jul 1998 21:01:19 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA08306 for ; Wed, 15 Jul 1998 21:01:17 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id OAA12439; Thu, 16 Jul 1998 14:01:04 +1000 Date: Thu, 16 Jul 1998 14:01:04 +1000 From: Bruce Evans Message-Id: <199807160401.OAA12439@godzilla.zeta.org.au> To: current@FreeBSD.ORG, jkh@time.cdrom.com Subject: Re: /usr/src/sbin/i386/mount_msdos - can we move it already? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >It makes no sense to have this under i386 since I could just as easily >have a DOS formatted partition I might want to read on my ALPHA. It >should be up with the rest of the mount_foo programs. > >Unless there are no serious objections, I'll ask Peter to do a repository >copy so we don't lose history on it. Same for comcontrol. It handles only a couple of machine-independent serial ioctls. OTOH, the control programs for serial drivers with lots of machine-dependent ioctls (stallion/* and sicontrol) are not in i386 subdirectories. Same for fdisk. It can be used on any block device. I could easily use it to manage disks containing DOS formatted partitions on your ALPHA. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 15 21:30:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA10656 for freebsd-current-outgoing; Wed, 15 Jul 1998 21:30:18 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA10651 for ; Wed, 15 Jul 1998 21:30:17 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id VAA00834; Wed, 15 Jul 1998 21:28:49 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: Bruce Evans cc: current@FreeBSD.ORG Subject: Re: /usr/src/sbin/i386/mount_msdos - can we move it already? In-reply-to: Your message of "Thu, 16 Jul 1998 14:01:04 +1000." <199807160401.OAA12439@godzilla.zeta.org.au> Date: Wed, 15 Jul 1998 21:28:48 -0700 Message-ID: <831.900563328@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG No objection from me - I was wondering about those two also. - Jordan > >It makes no sense to have this under i386 since I could just as easily > >have a DOS formatted partition I might want to read on my ALPHA. It > >should be up with the rest of the mount_foo programs. > > > >Unless there are no serious objections, I'll ask Peter to do a repository > >copy so we don't lose history on it. > > Same for comcontrol. It handles only a couple of machine-independent > serial ioctls. OTOH, the control programs for serial drivers with lots > of machine-dependent ioctls (stallion/* and sicontrol) are not in i386 > subdirectories. > > Same for fdisk. It can be used on any block device. I could easily > use it to manage disks containing DOS formatted partitions on your > ALPHA. > > Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 15 21:57:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA13060 for freebsd-current-outgoing; Wed, 15 Jul 1998 21:57:56 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.blurred.net (insight.blurred.net [198.53.161.124]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA13033 for ; Wed, 15 Jul 1998 21:57:52 -0700 (PDT) (envelope-from kligs@mail.blurred.net) Received: (from kligs@localhost) by mail.blurred.net (8.8.8/8.8.4) id AAA20691 for current@freebsd.org; Thu, 16 Jul 1998 00:58:08 -0400 (EDT) Message-ID: <19980716005808.A20663@insight.blurred.net> Date: Thu, 16 Jul 1998 00:58:08 -0400 From: Daniel Kligerman To: current@FreeBSD.ORG Subject: Problem building libbib during buildworld Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello. I am attempting to 'make buildworld' FreeBSD 3.0-current source which was cvsup'd two days ago, on my system: FreeBSD insight.blurred.net 3.0-980520-SNAP FreeBSD 3.0-980520-SNAP #0: Tue Jul 14 04:16:49 EDT 1998 root@insight.blurred.net: /usr/src/sys/compile/INSIGHT i386 I received the following error, and am unsure as to what might be causing it. Any suggestions would be appreciated. If more information is required, please let me know. Thanks. --- ... building standard driver library ranlib libdriver.a ===> libbib c++ -I/usr/obj/usr/src/tmp/usr/include/g++ -O -pipe -I/usr/src/gnu/usr.bin/groff/libbib/../include -DHAVE_UNISTD_H=1 -DHAVE_DIRENT_H=1 -DHAVE_LIMITS_H=1 -DHAVE_SYS_DIR_H=1 -DHAVE_STDLIB_H=1 -DUNISTD_H_DECLARES_GETOPT=1 -DSTDLIB_H_DECLARES_PUTENV=1 -DSTDIO_H_DECLARES_POPEN=1 -DSTDIO_H_DECLARE_PCLOSE=1 -DHAVE_CC_OSFCN_H=1 -DHAVE_CC_LIMITS_H=1 -DRETSIGTYPE=void -DHAVE_STRUCT_EXCEPTION=1 -DHAVE_RENAME=1 -DHAVE_MKSTEMP=1 -DSYS_SIGLIST_DECLARED=1 -I/usr/src/gnu/usr.bin/groff/libbib/../../../../contrib/groff/include -fno-for-scope -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/gnu/usr.bin/groff/libbib/../../../../contrib/groff/libbib/common.cc -o common.o c++ -I/usr/obj/usr/src/tmp/usr/include/g++ -O -pipe -I/usr/src/gnu/usr.bin/groff/libbib/../include -DHAVE_UNISTD_H=1 -DHAVE_DIRENT_H=1 -DHAVE_LIMITS_H=1 -DHAVE_SYS_DIR_H=1 -DHAVE_STDLIB_H=1 -DUNISTD_H_DECLARES_GETOPT=1 -DSTDLIB_H_DECLARES_PUTENV=1 -DSTDIO_H_DECLARES_POPEN=1 -DSTDIO_H_DECLARE_PCLOSE=1 -DHAVE_CC_OSFCN_H=1 -DHAVE_CC_LIMITS_H=1 -DRETSIGTYPE=void -DHAVE_STRUCT_EXCEPTION=1 -DHAVE_RENAME=1 -DHAVE_MKSTEMP=1 -DSYS_SIGLIST_DECLARED=1 -I/usr/src/gnu/usr.bin/groff/libbib/../../../../contrib/groff/include -fno-for-scope -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/gnu/usr.bin/groff/libbib/../../../../contrib/groff/libbib/index.cc -o index.o /usr/src/gnu/usr.bin/groff/libbib/../../../../contrib/groff/libbib/index.cc: In method `int index_search_item::load(int)': /usr/src/gnu/usr.bin/groff/libbib/../../../../contrib/groff/libbib/index.cc:217: Internal compiler error. /usr/src/gnu/usr.bin/groff/libbib/../../../../contrib/groff/libbib/index.cc:217: Please submit a full bug report to `bug-g++@prep.ai.mit.edu'. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. -- |) |\ o _, , @blurred.net | Daniel Kligerman |/) |/ | / | / \_ @feh.net | "I do not fear computers. | \/|_/|/\/|/ \/ @drivel.net | I fear the lack of them." (| | -- Isaac Asimov To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 15 22:06:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA14158 for freebsd-current-outgoing; Wed, 15 Jul 1998 22:06:54 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from duey.hs.wolves.k12.mo.us (root@duey.hs.wolves.k12.mo.us [207.160.214.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA14153 for ; Wed, 15 Jul 1998 22:06:52 -0700 (PDT) (envelope-from cdillon@wolves.k12.mo.us) Received: from duey.hs.wolves.k12.mo.us (cdillon@duey.hs.wolves.k12.mo.us [207.160.214.9]) by duey.hs.wolves.k12.mo.us (8.8.7/8.8.7) with SMTP id AAA04740 for ; Thu, 16 Jul 1998 00:06:44 -0500 (CDT) (envelope-from cdillon@wolves.k12.mo.us) Date: Thu, 16 Jul 1998 00:06:43 -0500 (CDT) From: Chris Dillon X-Sender: cdillon@duey.hs.wolves.k12.mo.us Reply-To: Chris Dillon To: current@FreeBSD.ORG Subject: Softupdates crash: Got it! Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The elusive "newdirrem: inum %d should be %d" reared its head again, and I finally caught it in the act. root@cheetah [/var/crash] # gdb -k GDB is free software and you are welcome to distribute copies of it under certain conditions; type "show copying" to see the conditions. There is absolutely no warranty for GDB; type "show warranty" for details. GDB 4.16 (i386-unknown-freebsd), Copyright 1996 Free Software Foundation, Inc. (kgdb) symbol-file /kernel.debug Reading symbols from /kernel.debug...done. (kgdb) exec-file /var/crash/kernel.0 (kgdb) core-file /var/crash/vmcore.0 IdlePTD 2146304 initial pcb at 1e7880 panicstr: newdirrem: inum %d should be %d panic messages: --- panic: newdirrem: inum 151732 should be 151731 syncing disks... panic: softdep_disk_write_complete: lock is held dumping to dev 20401, offset 245760 dump 80 79 78 77 76 75 74 73 72 71 70 69 68 67 66 65 64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 --- #0 boot (howto=260) at ../../kern/kern_shutdown.c:286 286 dumppcb.pcb_cr3 = rcr3(); (kgdb) where #0 boot (howto=260) at ../../kern/kern_shutdown.c:286 #1 0xf01166b6 in panic ( fmt=0xf017f543 "softdep_disk_write_complete: lock is held") at ../../kern/kern_shutdown.c:427 #2 0xf017f603 in softdep_disk_write_complete (bp=0xf222d8c8) at ../../ufs/ffs/ffs_softdep.c:2896 #3 0xf013302e in biodone (bp=0xf222d8c8) at ../../kern/vfs_bio.c:1918 #4 0xf016ef44 in scsi_done (xs=0xf080cf00) at ../../scsi/scsi_base.c:448 #5 0xf0165ade in ncr_complete (np=0xf0809000, cp=0xf080a800) at ../../pci/ncr.c:4836 #6 0xf0165b29 in ncr_wakeup (np=0xf0809000, code=0) at ../../pci/ncr.c:4878 #7 0xf0166920 in ncr_exception (np=0xf0809000) at ../../pci/ncr.c:5657 #8 0xf0164cea in ncr_intr (vnp=0xf0809000) at ../../pci/ncr.c:4033 #9 0xf019da32 in vec15 () #10 0xf0132e0f in biowait (bp=0xf2273368) at ../../kern/vfs_bio.c:1860 #11 0xf0130e22 in bread (vp=0xf4ab6b20, blkno=7798960, size=8192, cred=0x0, bpp=0xf4b47d10) at ../../kern/vfs_bio.c:299 #12 0xf017aa70 in ffs_update (vp=0xf4ae7880, access=0xf4b47d78, modify=0xf4b47d78, waitfor=0) at ../../ufs/ffs/ffs_inode.c:100 #13 0xf0184be9 in ffs_fsync (ap=0xf4b47db4) at ../../ufs/ffs/ffs_vnops.c:255 #14 0xf0182fb7 in ffs_sync (mp=0xf0843c00, waitfor=2, cred=0xf080cb80, p=0xf0200d30) at vnode_if.h:499 #15 0xf0139f07 in sync (p=0xf0200d30, uap=0x0) at ../../kern/vfs_syscalls.c:515 #16 0xf011629b in boot (howto=256) at ../../kern/kern_shutdown.c:203 #17 0xf01166b6 in panic (fmt=0xf017e87e "newdirrem: inum %d should be %d") at ../../kern/kern_shutdown.c:427 #18 0xf017e9d1 in newdirrem (bp=0xf22211e8, dp=0xf0c94c00, ip=0xf0e97c00, isrmdir=0) at ../../ufs/ffs/ffs_softdep.c:2382 #19 0xf017e7fc in softdep_setup_remove (bp=0xf22211e8, dp=0xf0c94c00, ip=0xf0e97c00, isrmdir=0) at ../../ufs/ffs/ffs_softdep.c:2311 #20 0xf0186ce7 in ufs_dirremove (dvp=0xf4e3aee0, ip=0xf0e97c00, flags=32776, isrmdir=0) at ../../ufs/ufs/ufs_lookup.c:895 #21 0xf0188c6b in ufs_remove (ap=0xf4b47f08) at ../../ufs/ufs/ufs_vnops.c:703 #22 0xf018ae4d in ufs_vnoperate (ap=0xf4b47f08) at ../../ufs/ufs/ufs_vnops.c:2287 #23 0xf013b277 in unlink (p=0xf4abc340, uap=0xf4b47f94) at vnode_if.h:523 #24 0xf01a65cf in syscall (frame={tf_es = 39, tf_ds = 39, tf_edi = 8938, tf_esi = 0, tf_ebp = -272639348, tf_isp = -189497372, tf_ebx = 444264, tf_edx = -272639376, tf_ecx = 15, tf_eax = 10, tf_trapno = 12, tf_err = 7, tf_eip = 55349, tf_cs = 31, tf_eflags = 582, tf_esp = -272639372, tf_ss = 39}) at ../../i386/i386/trap.c:1031 #25 0xd835 in ?? () #26 0x289d in ?? () #27 0x1fb9 in ?? () #28 0x107e in ?? () I _think_ Julian told me to upload the kernel+corefiles to ftp://ftp.whistle.com/incoming. I'll just tar cvf - /var/crash/kernel.0 /var/crash/vmcore.0 /kernel.debug | gzip -9 > cdillon_softupdates_crash_19980715.tar.gz and stick them in incoming. -- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net /* FreeBSD: The fastest and most stable server OS on the planet. For Intel x86 and compatibles (SPARC and Alpha under development) (http://www.freebsd.org) */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 15 22:44:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA17243 for freebsd-current-outgoing; Wed, 15 Jul 1998 22:44:24 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp03.primenet.com (daemon@smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA17238 for ; Wed, 15 Jul 1998 22:44:22 -0700 (PDT) (envelope-from tlambert@usr07.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id WAA03017; Wed, 15 Jul 1998 22:44:09 -0700 (MST) Received: from usr07.primenet.com(206.165.6.207) via SMTP by smtp03.primenet.com, id smtpd002920; Wed Jul 15 22:44:00 1998 Received: (from tlambert@localhost) by usr07.primenet.com (8.8.5/8.8.5) id WAA13103; Wed, 15 Jul 1998 22:43:53 -0700 (MST) From: Terry Lambert Message-Id: <199807160543.WAA13103@usr07.primenet.com> Subject: Re: Bug in kernel disklabel code? To: bde@zeta.org.au (Bruce Evans) Date: Thu, 16 Jul 1998 05:43:52 +0000 (GMT) Cc: current@FreeBSD.ORG, rock@cs.uni-sb.de In-Reply-To: <199807152331.JAA25461@godzilla.zeta.org.au> from "Bruce Evans" at Jul 16, 98 09:31:58 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Nothing much happens if you don't use these partitions. They used to > be normally unused (there is no good reason to access the slice for > the extended partition), but now the slice initialization code attempts > to find all labels on all slices so that it can create devfs device > nodes. I argued with Julian that there should be a preferred search order, and a preferred type at each level. I was unable to come up with a concrete example, except for a generic partitioning tool that would recognize all partition types, and be happy to manage them all. I'm sorry it's a problem for the poster, but I'm glad that someone has come up with a concrete example showing that a lack of preference order is a bad thing in at least one real-world situation... Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 15 22:45:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA17441 for freebsd-current-outgoing; Wed, 15 Jul 1998 22:45:32 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp01.primenet.com (daemon@smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA17432 for ; Wed, 15 Jul 1998 22:45:30 -0700 (PDT) (envelope-from tlambert@usr07.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id WAA27908; Wed, 15 Jul 1998 22:45:22 -0700 (MST) Received: from usr07.primenet.com(206.165.6.207) via SMTP by smtp01.primenet.com, id smtpd027892; Wed Jul 15 22:45:16 1998 Received: (from tlambert@localhost) by usr07.primenet.com (8.8.5/8.8.5) id WAA13187; Wed, 15 Jul 1998 22:45:14 -0700 (MST) From: Terry Lambert Message-Id: <199807160545.WAA13187@usr07.primenet.com> Subject: Re: /usr/src/sbin/i386/mount_msdos - can we move it already? To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Thu, 16 Jul 1998 05:45:14 +0000 (GMT) Cc: current@FreeBSD.ORG In-Reply-To: <2299.900547128@time.cdrom.com> from "Jordan K. Hubbard" at Jul 15, 98 04:58:48 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > It makes no sense to have this under i386 since I could just as easily > have a DOS formatted partition I might want to read on my ALPHA. It > should be up with the rest of the mount_foo programs. > > Unless there are no serious objections, I'll ask Peter to do a repository > copy so we don't lose history on it. In point of fact, the PReP and CHRP standards both require a DOS partition table (these are for Motorola PPC based hardware). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 15 22:51:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA18287 for freebsd-current-outgoing; Wed, 15 Jul 1998 22:51:25 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp03.primenet.com (daemon@smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA18280 for ; Wed, 15 Jul 1998 22:51:23 -0700 (PDT) (envelope-from tlambert@usr07.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id WAA04782; Wed, 15 Jul 1998 22:51:15 -0700 (MST) Received: from usr07.primenet.com(206.165.6.207) via SMTP by smtp03.primenet.com, id smtpd004725; Wed Jul 15 22:51:06 1998 Received: (from tlambert@localhost) by usr07.primenet.com (8.8.5/8.8.5) id WAA13571; Wed, 15 Jul 1998 22:51:03 -0700 (MST) From: Terry Lambert Message-Id: <199807160551.WAA13571@usr07.primenet.com> Subject: Re: /usr/src/sbin/i386/mount_msdos - can we move it already? To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Thu, 16 Jul 1998 05:51:03 +0000 (GMT) Cc: bde@zeta.org.au, current@FreeBSD.ORG In-Reply-To: <831.900563328@time.cdrom.com> from "Jordan K. Hubbard" at Jul 15, 98 09:28:48 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > No objection from me - I was wondering about those two also. [ ... ] > > Same for fdisk. It can be used on any block device. I could easily > > use it to manage disks containing DOS formatted partitions on your > > ALPHA. Really, the use of "fdisk" is wrong. There needs to be an abstract interface to parittioning management that doesn't care about what code is actually doing the managing. It would open the device, and basically ask it if it had current partitioning, and also ask what modules would be willing to manage partitioning on it. Then it would write a clean label or whatever via an ioctl() that is independent of the partitioning being enacted that says "Hey you, manage this". One problem with this is that the SLICE code sort of makes some assumptions about locking and devices access that aren't very good assumptions if you wanted this to work. In addition, there are not entry points for "splat a label on this puppy Mr. XXX slice type manager!". Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 15 23:17:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA20825 for freebsd-current-outgoing; Wed, 15 Jul 1998 23:17:31 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns2.cetlink.net (root@ns2.cetlink.net [209.54.54.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA20819 for ; Wed, 15 Jul 1998 23:17:26 -0700 (PDT) (envelope-from jak@cetlink.net) Received: from EXIT10 (i485-gw.cetlink.net [209.198.15.97]) by ns2.cetlink.net (8.9.1/8.9.1) with SMTP id CAA05937; Thu, 16 Jul 1998 02:16:49 -0400 (EDT) From: jak@cetlink.net (John Kelly) To: Bruce Evans Cc: current@FreeBSD.ORG Subject: Re: tickadj -t not changing tick Date: Thu, 16 Jul 1998 06:19:36 GMT Message-ID: <35ad9407.200559635@mail.cetlink.net> References: <199807150330.NAA22646@godzilla.zeta.org.au> In-Reply-To: <199807150330.NAA22646@godzilla.zeta.org.au> X-Mailer: Forte Agent 1.5/32.451 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id XAA20820 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 15 Jul 1998 13:30:29 +1000, Bruce Evans wrote: >machdep.i8254_freq: always exists, never hurts to set it right, but only > essential for it to be right on systems using it for timekeeping > (2.2., -current on sub-586's and 586+'s running SMP or APM. Sysctl shows my default value of machdep.i8254_freq = 1,193,182, the same value one of my hardware books says is the "standard" oscillator rate input to the 8254. But since my clock runs fast, my oscillator seems to be at a slightly higher rate. So am I correct in assuming I need to increase the i8254_freq value to match the true oscillator rate, and the kernel will adjust accordingly? And besides trial and error, is there any way of determining what the true frequency of my oscillator is? >machdep.tsc_freq: -current only, must be right if it is used for timekeeping. > It is used on 586+'s not running SMP or APM. I know what the 8254 is, but what is the TSC? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 15 23:33:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA23239 for freebsd-current-outgoing; Wed, 15 Jul 1998 23:33:06 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.camalott.com (root@mail.camalott.com [208.203.140.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA23232 for ; Wed, 15 Jul 1998 23:33:04 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-67.camalott.com [208.229.74.67]) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id BAA30949; Thu, 16 Jul 1998 01:33:16 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.8.8/8.8.8) id BAA02045; Thu, 16 Jul 1998 01:32:28 -0500 (CDT) (envelope-from joelh) Date: Thu, 16 Jul 1998 01:32:28 -0500 (CDT) Message-Id: <199807160632.BAA02045@detlev.UUCP> To: jak@cetlink.net CC: bde@zeta.org.au, current@FreeBSD.ORG In-reply-to: <35ad9407.200559635@mail.cetlink.net> (jak@cetlink.net) Subject: Re: tickadj -t not changing tick From: Joel Ray Holveck Reply-to: joelh@gnu.org References: <199807150330.NAA22646@godzilla.zeta.org.au> <35ad9407.200559635@mail.cetlink.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > And besides trial and error, is there any way of determining what the > true frequency of my oscillator is? Well, you *could* hook up a frequency counter... Or, at a guess, you may be able to take the number of seconds deviation you get in a week, divide by 604800 (seconds per week), and multiply by your current value of machdep.i8254_freq, and get the number of ticks you need to adjust the value by. But I'm rather tired at the moment and can't be sure that I got the math right. A real quick dimensional analysis doesn't seem to turn out right, but it's more likely I'm doing that wrong than the original formula. Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 15 23:54:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA25895 for freebsd-current-outgoing; Wed, 15 Jul 1998 23:54:17 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA25889 for ; Wed, 15 Jul 1998 23:54:14 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id QAA24751; Thu, 16 Jul 1998 16:53:55 +1000 Date: Thu, 16 Jul 1998 16:53:55 +1000 From: Bruce Evans Message-Id: <199807160653.QAA24751@godzilla.zeta.org.au> To: bde@zeta.org.au, jak@cetlink.net Subject: Re: tickadj -t not changing tick Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>machdep.i8254_freq: always exists, never hurts to set it right, but only >> essential for it to be right on systems using it for timekeeping >> (2.2., -current on sub-586's and 586+'s running SMP or APM. > >Sysctl shows my default value of machdep.i8254_freq = 1,193,182, the >same value one of my hardware books says is the "standard" oscillator >rate input to the 8254. But since my clock runs fast, my oscillator >seems to be at a slightly higher rate. So am I correct in assuming I >need to increase the i8254_freq value to match the true oscillator >rate, and the kernel will adjust accordingly? It wouldn't hurt, but I guess you have a Pentium not running SMP or APM, so it wouldn;t help much. >And besides trial and error, is there any way of determining what the >true frequency of my oscillator is? Boot with -v and note the frequency calibrated relative to the RTC and use that is input to sysctl, or use CLK_USE_I8254_CALIBRATION to set this frequency by default. The RTC is usually more accurate than the i8254. >>machdep.tsc_freq: -current only, must be right if it is used for timekeeping. >> It is used on 586+'s not running SMP or APM. > >I know what the 8254 is, but what is the TSC? The "Pentium" TimeStamp Counter. It runs at 300 MHz for a CPU frequency of 300 MHz, etc. It is initially calibrated relative to the i8254. You can boot with -v to see its frequency relative to the RTC, or use CLK_USE_TSC_CALIBRATION to use this frequency by default. Another sysctl, `sysctl kern.timecounter.frequency', gives the frequency of the counter being used for timekeeping. If it is about 1 MHz then the i8254 is being used; otherwise the TSC is being used. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 16 00:27:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA28991 for freebsd-current-outgoing; Thu, 16 Jul 1998 00:27:17 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA28962 for ; Thu, 16 Jul 1998 00:26:34 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.5) with ESMTP id JAA00280; Thu, 16 Jul 1998 09:23:27 +0200 (CEST) To: jak@cetlink.net (John Kelly) cc: Bruce Evans , current@FreeBSD.ORG Subject: Re: tickadj -t not changing tick In-reply-to: Your message of "Thu, 16 Jul 1998 06:19:36 GMT." <35ad9407.200559635@mail.cetlink.net> Date: Thu, 16 Jul 1998 09:23:27 +0200 Message-ID: <278.900573807@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <35ad9407.200559635@mail.cetlink.net>, John Kelly writes: >On Wed, 15 Jul 1998 13:30:29 +1000, Bruce Evans >wrote: > >>machdep.i8254_freq: always exists, never hurts to set it right, but only >> essential for it to be right on systems using it for timekeeping >> (2.2., -current on sub-586's and 586+'s running SMP or APM. > >Sysctl shows my default value of machdep.i8254_freq = 1,193,182, the >same value one of my hardware books says is the "standard" oscillator >rate input to the 8254. But since my clock runs fast, my oscillator >seems to be at a slightly higher rate. So am I correct in assuming I >need to increase the i8254_freq value to match the true oscillator >rate, and the kernel will adjust accordingly? > >And besides trial and error, is there any way of determining what the >true frequency of my oscillator is? You want to fiddle kern.timecounter.frequency (units: Hz) or kern.timecounter.adjustment (Units: PPM/2^16) The real way is to run ntpd, if you don't have a permanent connection, consider looking into "burstmode" in the new xntpd4... >I know what the 8254 is, but what is the TSC? A 64 bit counter internal to the Pentium, which counts clockcycles... -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 16 00:28:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA29221 for freebsd-current-outgoing; Thu, 16 Jul 1998 00:28:40 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pop.asahi-net.or.jp (pop.asahi-net.or.jp [202.224.39.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA29204 for ; Thu, 16 Jul 1998 00:28:38 -0700 (PDT) (envelope-from tfuruya@ppp142052.asahi-net.or.jp) Received: from galois.tf.or.jp (ppp142052.asahi-net.or.jp [202.213.142.52]) by pop.asahi-net.or.jp (8.8.8/3.6W) with ESMTP id QAA05992; Thu, 16 Jul 1998 16:34:07 +0900 Received: from galois.tf.or.jp (localhost.tf.or.jp [127.0.0.1]) by galois.tf.or.jp (8.8.8/3.6W-ht5t-fry@asahi-net-98042218) with ESMTP id QAA05395; Thu, 16 Jul 1998 16:28:02 +0900 (JST) Message-Id: <199807160728.QAA05395@galois.tf.or.jp> To: rotel@indigo.ie Cc: freebsd-current@FreeBSD.ORG, Tetsuro FURUYA Subject: Re: Re those MAXUSERS troubles From: Tetsuro FURUYA Reply-To: Tetsuro FURUYA In-Reply-To: Your message of "Thu, 16 Jul 1998 01:51:47 +0000" References: <199807160051.BAA02792@indigo.ie> X-Mailer: Mew version 1.54 on Emacs 19.28.1, Mule 2.3 X-fingerprint: F1 BA 5F C1 C2 48 1D C7 AE 5F 16 ED 12 17 75 38 X-URL: http://sodan.komaba.ecc.u-tokyo.ac.jp/~tfuruya/ Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Thu, 16 Jul 1998 16:28:01 +0900 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In Message-ID: <199807160051.BAA02792@indigo.ie> Niall Smart : > Hi, > > When I recompiled config from fresh sources that problem went away. > > Niall Do you mean cvsuped fresh source ? Tetsuro, Furuya. ht5t-fry@asahi-net.or.jp ======================================================================== TEL: 048-852-3520 FAX: 048-858-1597 E-Mail: ht5t-fry@asahi-net.or.jp , tfu@ff.iij4u.or.jp pgp-fingerprint: pub Tetsuro FURUYA Key fingerprint = F1 BA 5F C1 C2 48 1D C7 AE 5F 16 ED 12 17 75 38 ========================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 16 00:48:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA00975 for freebsd-current-outgoing; Thu, 16 Jul 1998 00:48:44 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from oslo.geco-prakla.slb.com (geos01.oslo.geco-prakla.slb.com [134.32.44.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA00929; Thu, 16 Jul 1998 00:48:36 -0700 (PDT) (envelope-from smoergrd@oslo.sl.slb.com) Received: from sunw110.oslo.Geco-Prakla.slb.com (sunw110 [192.23.231.54]) by oslo.geco-prakla.slb.com (8.8.8/8.6.9) with SMTP id JAA21620 ; Thu, 16 Jul 1998 09:46:28 +0200 (MET DST) Received: by sunw110.oslo.Geco-Prakla.slb.com (SMI-8.6/SMI-SVR4) id JAA14880; Thu, 16 Jul 1998 09:46:27 +0200 To: Lee Johnston Cc: Brandon Lockhart , David Greenman , Jeremy Domingue , current@FreeBSD.ORG, stable@FreeBSD.ORG, questions@FreeBSD.ORG Subject: Re: Disgruntled Linux User... questions about FreeBSD References: <199807141511.IAA18210@implode.root.com> <19980715185522.B733@ljis.ml.org> Organization: Schlumberger Geco-Prakla X-Disclaimer: I speak only for myself. From: smoergrd@oslo.geco-prakla.slb.com (Dag-Erling Coidan Smørgrav) Date: 16 Jul 1998 09:46:27 +0200 In-Reply-To: Lee Johnston's message of Wed, 15 Jul 1998 18:55:22 +0100 Message-ID: Lines: 15 X-Mailer: Gnus v5.3/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Lee Johnston writes: > On Tue, Jul 14, 1998 at 07:56:28PM -0400, Brandon Lockhart wrote: > > What are you talking about, I was talking about for a HIGHLY used server, > > as in, more then cdrom.com, and I was talking about a REAL server, not a > > PC supped up. I am talking about a rack mount server, a REAL server. > > Which in case you where out of the loop, most REAL servers use RISC. > More than ftp.cdrom.com? I thought ftp.cdrom.com was one of the busiest > if not _THE_ busiest FTP Server on the Internet. What servers are you > talking about? Aw shucks, the guy's just one big fscking troll. Ignore him. DES -- Dag-Erling Smørgrav - smoergrd@oslo.geco-prakla.slb.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 16 00:52:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA02004 for freebsd-current-outgoing; Thu, 16 Jul 1998 00:52:19 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp11.bellglobal.com (smtp11.bellglobal.com [204.101.251.53]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA01997 for ; Thu, 16 Jul 1998 00:52:14 -0700 (PDT) (envelope-from tim@localhost.my.domain) Received: from localhost.my.domain (ppp1727.on.bellglobal.com [206.172.249.191]) by smtp11.bellglobal.com (8.8.5/8.8.5) with ESMTP id DAA13864; Thu, 16 Jul 1998 03:52:07 -0400 (EDT) Received: (from tim@localhost) by localhost.my.domain (8.8.8/8.8.8) id BAA20570; Thu, 16 Jul 1998 01:52:30 -0400 (EDT) (envelope-from tim) Message-ID: <19980716015229.C20457@zappo> Date: Thu, 16 Jul 1998 01:52:29 -0400 From: Tim Vanderhoek To: "Scot W. Hetzel" , joelh@gnu.org Cc: FreeBSD-Current Subject: Re: aout / elf library directories References: <036401bdb01d$c4139600$c3e0d9cf@westbend.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <036401bdb01d$c4139600$c3e0d9cf@westbend.net>; from Scot W. Hetzel on Wed, Jul 15, 1998 at 01:24:11PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jul 15, 1998 at 01:24:11PM -0500, Scot W. Hetzel wrote: > From: Joel Ray Holveck [...] > >Is -current's /usr/lib/{aout,elf} going to persist for a while (which > >would imply I should try to get this changed before release), or is it > >a fairly temporary condition? > > > Don't know how long it's going to persist, but it will most likely persist > through the 3.0 RELEASES. Ooh. I could've sworn jdp said this was only temporary... [extended musical search interlude] Aha. It was sos. See his Message-id: 199805270803.KAA17092@sos.freebsd.dk. I think the timeframe for the death of /usr/lib/elf is within the next couple weeks, if all goes well. -- This .sig is not innovative, witty, or profund. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 16 00:57:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA02456 for freebsd-current-outgoing; Thu, 16 Jul 1998 00:57:38 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from oslo.geco-prakla.slb.com (geos01.oslo.geco-prakla.slb.com [134.32.44.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA02450 for ; Thu, 16 Jul 1998 00:57:34 -0700 (PDT) (envelope-from smoergrd@oslo.sl.slb.com) Received: from sunw110.oslo.Geco-Prakla.slb.com (sunw110 [192.23.231.54]) by oslo.geco-prakla.slb.com (8.8.8/8.6.9) with SMTP id JAA22164 ; Thu, 16 Jul 1998 09:56:54 +0200 (MET DST) Received: by sunw110.oslo.Geco-Prakla.slb.com (SMI-8.6/SMI-SVR4) id JAA15002; Thu, 16 Jul 1998 09:56:53 +0200 To: Chris Dillon Cc: current@FreeBSD.ORG Subject: Re: Softupdates crash: Got it! References: Organization: Schlumberger Geco-Prakla X-Disclaimer: I speak only for myself. From: smoergrd@oslo.geco-prakla.slb.com (Dag-Erling Coidan Smørgrav) Date: 16 Jul 1998 09:56:53 +0200 In-Reply-To: Chris Dillon's message of Thu, 16 Jul 1998 00:06:43 -0500 (CDT) Message-ID: Lines: 10 X-Mailer: Gnus v5.3/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Chris Dillon writes: > The elusive "newdirrem: inum %d should be %d" reared its head again, > and I finally caught it in the act. Somehow I feel a celebration is required. Like when Zim catches the brain bug in _Starship Troopers_... DES ;) -- Dag-Erling Smørgrav - smoergrd@oslo.geco-prakla.slb.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 16 01:06:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA04842 for freebsd-current-outgoing; Thu, 16 Jul 1998 01:06:15 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from magnet.geophysik.tu-freiberg.de (magnet.geophysik.tu-freiberg.de [139.20.128.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA04781 for ; Thu, 16 Jul 1998 01:06:11 -0700 (PDT) (envelope-from freebsd@magnet.geophysik.tu-freiberg.de) Received: (from freebsd@localhost) by magnet.geophysik.tu-freiberg.de (8.8.8/8.7.3) id KAA04016; Thu, 16 Jul 1998 10:05:48 +0200 (CEST) Message-ID: <19980716100547.37260@geophysik.tu-freiberg.de> Date: Thu, 16 Jul 1998 10:05:47 +0200 From: Holm Tiffe To: freebsd-current@FreeBSD.ORG Subject: URGENT! ASUS P2B/LS supported ? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, I need to know urgently if the onboard peripherals from the ASUS P2B/LS Motherboard are supported under -current. On the ASUS website is the following information: Onboard Intel 82558 fast Ethernet LAN Controller Onboard Adaptec AIC 7890 & AIC 3860 (option) 80 MBPS Ultra 2 Wide SCSI Intel 440BX AGP Chipset I whish to use a Matrox Millenium II AGP in this board. Ist this supported ? Should I buy this board ? Should I buy the Matrox ? Sorry for my poor english, Holm -- ******************************************************************************* * Holm Tiffe holm@geophysik.tu-freiberg.de * * Freiberger Strasse 24 * * 09600 Kleinschirma, Germany Microsoft is not the Answer - * * Tel.: 49 3731 74233 Microsoft is the Question, * * UUCP: 49 3731 73719 unicorn!holm and the Answer is no ! * ******************************************************************************* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 16 01:08:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA05529 for freebsd-current-outgoing; Thu, 16 Jul 1998 01:08:23 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from oslo.geco-prakla.slb.com (geos01.oslo.geco-prakla.slb.com [134.32.44.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA05524 for ; Thu, 16 Jul 1998 01:08:21 -0700 (PDT) (envelope-from smoergrd@oslo.sl.slb.com) Received: from sunw110.oslo.Geco-Prakla.slb.com (sunw110 [192.23.231.54]) by oslo.geco-prakla.slb.com (8.8.8/8.6.9) with SMTP id KAA22728 for ; Thu, 16 Jul 1998 10:07:42 +0200 (MET DST) Received: by sunw110.oslo.Geco-Prakla.slb.com (SMI-8.6/SMI-SVR4) id KAA15140; Thu, 16 Jul 1998 10:07:40 +0200 To: current@FreeBSD.ORG Subject: Soft updates Organization: Schlumberger Geco-Prakla X-Disclaimer: I speak only for myself. From: smoergrd@oslo.geco-prakla.slb.com (Dag-Erling Coidan Smørgrav) Date: 16 Jul 1998 10:07:40 +0200 Message-ID: Lines: 12 X-Mailer: Gnus v5.3/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thought you'd like a data point: Luna has been running soft updates on all file systems (one IDE disk) since saturday, without a single panic, doing practically nothing but continuous make buildworld, installworld, release (including 'cvs co src' from an NFS-mounted repository) and a couple of cvsups. Niobe is switching to soft updates on all file systems (three SCSI disks) as soon as I get a new kernel compiled tonight. DES -- Dag-Erling Smørgrav - smoergrd@oslo.geco-prakla.slb.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 16 01:15:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA06686 for freebsd-current-outgoing; Thu, 16 Jul 1998 01:15:05 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns2.cetlink.net (root@ns2.cetlink.net [209.54.54.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA06681 for ; Thu, 16 Jul 1998 01:15:02 -0700 (PDT) (envelope-from jak@cetlink.net) Received: from EXIT10 (i485-gw.cetlink.net [209.198.15.97]) by ns2.cetlink.net (8.9.1/8.9.1) with SMTP id EAA16325; Thu, 16 Jul 1998 04:14:46 -0400 (EDT) From: jak@cetlink.net (John Kelly) To: Bruce Evans Cc: current@FreeBSD.ORG Subject: Re: tickadj -t not changing tick Date: Thu, 16 Jul 1998 08:16:45 GMT Message-ID: <35adaeab.207380020@mail.cetlink.net> References: <199807160653.QAA24751@godzilla.zeta.org.au> In-Reply-To: <199807160653.QAA24751@godzilla.zeta.org.au> X-Mailer: Forte Agent 1.5/32.451 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id BAA06682 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 16 Jul 1998 16:53:55 +1000, Bruce Evans wrote: >>So am I correct in assuming I >>need to increase the i8254_freq value to match the true oscillator >>rate, and the kernel will adjust accordingly? > >It wouldn't hurt, but I guess you have a Pentium not running SMP or APM, >so it wouldn;t help much. Both 486's and Pentiums, so I need to understand how to tweak both i8254 and TSC. One of my 486 machines is fast by 27.68 seconds per day, so it seems I need to change its i8254_freq to 1,193,564. >Boot with -v and note the frequency calibrated relative to the RTC and >use that is input to sysctl, or use CLK_USE_I8254_CALIBRATION to set >this frequency by default. The RTC is usually more accurate than the >i8254. That's helpful too, but using the value calculated by hand from an average daily deviation as determined by ntpdate seems more precise, so I think I'll sysctl my hand-calculated value at bootup somehow. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 16 01:39:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA09821 for freebsd-current-outgoing; Thu, 16 Jul 1998 01:39:41 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from atlas.iexpress.net.au (atlas.iexpress.net.au [203.38.34.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA09786; Thu, 16 Jul 1998 01:39:36 -0700 (PDT) (envelope-from mikey@iexpress.net.au) Received: from localhost (mikey@localhost) by atlas.iexpress.net.au (8.9.0/8.9.0) with SMTP id QAA22520; Thu, 16 Jul 1998 16:38:01 +0800 (WST) Date: Thu, 16 Jul 1998 16:38:01 +0800 (WST) From: Michael Slater To: Dag-Erling Coidan Smørgrav cc: Lee Johnston , Brandon Lockhart , David Greenman , Jeremy Domingue , current@FreeBSD.ORG, stable@FreeBSD.ORG, questions@FreeBSD.ORG Subject: Re: Disgruntled Linux User... questions about FreeBSD In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by hub.freebsd.org id BAA09787 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 16 Jul 1998, Dag-Erling Coidan Smørgrav wrote: > Lee Johnston writes: > > On Tue, Jul 14, 1998 at 07:56:28PM -0400, Brandon Lockhart wrote: > > > What are you talking about, I was talking about for a HIGHLY used server, > > > as in, more then cdrom.com, and I was talking about a REAL server, not a > > > PC supped up. I am talking about a rack mount server, a REAL server. If it's mounted in a rack it must be REAL.. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 16 01:40:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA10059 for freebsd-current-outgoing; Thu, 16 Jul 1998 01:40:12 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns2.cetlink.net (root@ns2.cetlink.net [209.54.54.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA10044 for ; Thu, 16 Jul 1998 01:40:09 -0700 (PDT) (envelope-from jak@cetlink.net) Received: from EXIT10 (i485-gw.cetlink.net [209.198.15.97]) by ns2.cetlink.net (8.9.1/8.9.1) with SMTP id EAA17156; Thu, 16 Jul 1998 04:36:26 -0400 (EDT) From: jak@cetlink.net (John Kelly) To: Poul-Henning Kamp Cc: Bruce Evans , current@FreeBSD.ORG Subject: Re: tickadj -t not changing tick Date: Thu, 16 Jul 1998 08:38:25 GMT Message-ID: <35aeb750.209593961@mail.cetlink.net> References: <278.900573807@critter.freebsd.dk> In-Reply-To: <278.900573807@critter.freebsd.dk> X-Mailer: Forte Agent 1.5/32.451 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id BAA10049 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 16 Jul 1998 09:23:27 +0200, Poul-Henning Kamp wrote: >The real way is to run ntpd, if you don't have a permanent connection, >consider looking into "burstmode" in the new xntpd4... According to John Polstra in an archived message about tickadj, his "real way" is to adjust the undisciplined clock before running xntpd, formerly with tickadj, but now via sysctl as Bruce suggested. I like the idea of getting the kernel synchronized with the hardware before trying to run xntpd. >You want to fiddle kern.timecounter.frequency (units: Hz) or >kern.timecounter.adjustment (Units: PPM/2^16) Judging from what Bruce said, it seems that kern.timecounter.frequency is derived from the machdep.*_freq variables, so it would be better to change them and let the kernel propagate the changes. And if the appropriate machdep.*_freq variable is set precisely, is there any need for kern.timecounter.adjustment? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 16 01:53:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA11927 for freebsd-current-outgoing; Thu, 16 Jul 1998 01:53:51 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA11920 for ; Thu, 16 Jul 1998 01:53:48 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id SAA31913; Thu, 16 Jul 1998 18:53:34 +1000 Date: Thu, 16 Jul 1998 18:53:34 +1000 From: Bruce Evans Message-Id: <199807160853.SAA31913@godzilla.zeta.org.au> To: jak@cetlink.net, phk@critter.freebsd.dk Subject: Re: tickadj -t not changing tick Cc: bde@zeta.org.au, current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>You want to fiddle kern.timecounter.frequency (units: Hz) or >>kern.timecounter.adjustment (Units: PPM/2^16) > >Judging from what Bruce said, it seems that kern.timecounter.frequency >is derived from the machdep.*_freq variables, so it would be better to >change them and let the kernel propagate the changes. It would be nicest to change the machine-independent variables and let the kernel propagate the changes to the machine-dependent variables and hardware. However the kernel makes no attempt to propagate the changes. OTOH, when you change the m-d variables, the kernel attempts to propagate the changes, but it doesn't succeed (it sets the active frequency, possibly causing a glitch due to the non-atomic update, and the change gets blown away at the next clock interrupt). >And if the appropriate machdep.*_freq variable is set precisely, is >there any need for kern.timecounter.adjustment? Only in practice. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 16 02:01:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA12690 for freebsd-current-outgoing; Thu, 16 Jul 1998 02:01:46 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns2.cetlink.net (root@ns2.cetlink.net [209.54.54.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA12683 for ; Thu, 16 Jul 1998 02:01:40 -0700 (PDT) (envelope-from jak@cetlink.net) Received: from EXIT10 (i485-gw.cetlink.net [209.198.15.97]) by ns2.cetlink.net (8.9.1/8.9.1) with SMTP id FAA18163; Thu, 16 Jul 1998 05:01:20 -0400 (EDT) From: jak@cetlink.net (John Kelly) To: Bruce Evans Cc: current@FreeBSD.ORG Subject: Re: tickadj -t not changing tick Date: Thu, 16 Jul 1998 09:04:09 GMT Message-ID: <35afc126.212112276@mail.cetlink.net> References: <199807160853.SAA31913@godzilla.zeta.org.au> In-Reply-To: <199807160853.SAA31913@godzilla.zeta.org.au> X-Mailer: Forte Agent 1.5/32.451 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id CAA12684 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 16 Jul 1998 18:53:34 +1000, Bruce Evans wrote: >>>You want to fiddle kern.timecounter.frequency (units: Hz) or >>>kern.timecounter.adjustment (Units: PPM/2^16) >> >>Judging from what Bruce said, it seems that kern.timecounter.frequency >>is derived from the machdep.*_freq variables, so it would be better to >>change them and let the kernel propagate the changes. > >It would be nicest to change the machine-independent variables and let >the kernel propagate the changes to the machine-dependent variables and >hardware. However the kernel makes no attempt to propagate the changes. >OTOH, when you change the m-d variables, the kernel attempts to propagate >the changes, but it doesn't succeed (it sets the active frequency, >possibly causing a glitch due to the non-atomic update, and the change >gets blown away at the next clock interrupt). Argh! So should I change both kern.timecounter.frequency and the machine dependent variable? Will that work? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 16 02:09:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA13222 for freebsd-current-outgoing; Thu, 16 Jul 1998 02:09:06 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from tyree.iii.co.uk ([195.89.149.230]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA13215 for ; Thu, 16 Jul 1998 02:09:02 -0700 (PDT) (envelope-from nik@iii.co.uk) From: nik@iii.co.uk Received: from carrig.strand.iii.co.uk (carrig.strand.iii.co.uk [192.168.7.25]) by tyree.iii.co.uk (8.8.8/8.8.8) with ESMTP id KAA21600; Thu, 16 Jul 1998 10:08:36 +0100 (BST) Received: (from nik@localhost) by carrig.strand.iii.co.uk (8.8.8/8.8.7) id KAA29493; Thu, 16 Jul 1998 10:07:51 +0100 (BST) Message-ID: <19980716100751.16056@iii.co.uk> Date: Thu, 16 Jul 1998 10:07:51 +0100 To: Tim Vanderhoek Cc: "Scot W. Hetzel" , joelh@gnu.org, FreeBSD-Current Subject: Re: aout / elf library directories References: <036401bdb01d$c4139600$c3e0d9cf@westbend.net> <19980716015229.C20457@zappo> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.85e In-Reply-To: <19980716015229.C20457@zappo>; from Tim Vanderhoek on Thu, Jul 16, 1998 at 01:52:29AM -0400 Organization: interactive investor Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jul 16, 1998 at 01:52:29AM -0400, Tim Vanderhoek wrote: > I think the timeframe for the death of /usr/lib/elf is within the next > couple weeks, if all goes well. [ Disclaimer: this is well out of my general area of expertise, but this has had me wondering for a while ] I'm a little confused by this. If I understand correctly, there are some niggling problems with ELF (which is why we have tools such as brandelf) and a switch to yet another format at some point in the future is not totally out of the question. At which point we'd need to go through all this again. Wouldn't it actually make more sense to have /usr/lib.aout, /usr/lib.elf, and have /usr/lib be a symlink[1] to one or the other as appropriate? Then in X years time when (if) a new format is adopted, it can slot in with less effort. N [1] Or variant symlink -- Work: nik@iii.co.uk | FreeBSD + Perl + Apache Rest: nik@nothing-going-on.demon.co.uk | Remind me again why we need Play: nik@freebsd.org | Microsoft? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 16 02:16:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA13942 for freebsd-current-outgoing; Thu, 16 Jul 1998 02:16:23 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns2.cetlink.net (root@ns2.cetlink.net [209.54.54.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA13931 for ; Thu, 16 Jul 1998 02:16:21 -0700 (PDT) (envelope-from jak@cetlink.net) Received: from EXIT10 (i485-gw.cetlink.net [209.198.15.97]) by ns2.cetlink.net (8.9.1/8.9.1) with SMTP id FAA18778; Thu, 16 Jul 1998 05:15:59 -0400 (EDT) From: jak@cetlink.net (John Kelly) To: Bruce Evans Cc: current@FreeBSD.ORG Subject: Re: tickadj -t not changing tick Date: Thu, 16 Jul 1998 09:17:58 GMT Message-ID: <35adc33e.212647565@mail.cetlink.net> References: <199807160853.SAA31913@godzilla.zeta.org.au> In-Reply-To: <199807160853.SAA31913@godzilla.zeta.org.au> X-Mailer: Forte Agent 1.5/32.451 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id CAA13936 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 16 Jul 1998 18:53:34 +1000, Bruce Evans wrote: >OTOH, when you change the m-d variables, the kernel attempts to propagate >the changes, but it doesn't succeed (it sets the active frequency, >possibly causing a glitch due to the non-atomic update, and the change >gets blown away at the next clock interrupt). I just tried this on a 486 running a 980515 SNAP, and it worked. It *did* propagate machdep.i8254_freq to kern.timecounter.frequency. And from checking the time deviation with ntpdate, it seems to be right on the mark now. Are you saying it may propagate sometimes but not always? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 16 02:25:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA14945 for freebsd-current-outgoing; Thu, 16 Jul 1998 02:25:43 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA14939 for ; Thu, 16 Jul 1998 02:25:38 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.5) with ESMTP id LAA01047; Thu, 16 Jul 1998 11:23:00 +0200 (CEST) To: jak@cetlink.net (John Kelly) cc: Bruce Evans , current@FreeBSD.ORG Subject: Re: tickadj -t not changing tick In-reply-to: Your message of "Thu, 16 Jul 1998 08:38:25 GMT." <35aeb750.209593961@mail.cetlink.net> Date: Thu, 16 Jul 1998 11:23:00 +0200 Message-ID: <1045.900580980@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <35aeb750.209593961@mail.cetlink.net>, John Kelly writes: >And if the appropriate machdep.*_freq variable is set precisely, is >there any need for kern.timecounter.adjustment? You can apply finer adjustment than 1hz with it. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 16 02:45:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA16916 for freebsd-current-outgoing; Thu, 16 Jul 1998 02:45:00 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA16911 for ; Thu, 16 Jul 1998 02:44:55 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id TAA02024; Thu, 16 Jul 1998 19:44:45 +1000 Date: Thu, 16 Jul 1998 19:44:45 +1000 From: Bruce Evans Message-Id: <199807160944.TAA02024@godzilla.zeta.org.au> To: bde@zeta.org.au, jak@cetlink.net Subject: Re: tickadj -t not changing tick Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>OTOH, when you change the m-d variables, the kernel attempts to propagate >>the changes, but it doesn't succeed (it sets the active frequency, >>possibly causing a glitch due to the non-atomic update, and the change >>gets blown away at the next clock interrupt). > >I just tried this on a 486 running a 980515 SNAP, and it worked. It >*did* propagate machdep.i8254_freq to kern.timecounter.frequency. And >from checking the time deviation with ntpdate, it seems to be right on >the mark now. > >Are you saying it may propagate sometimes but not always? Perhaps it is only broken for my version of machdep.tsc_freq. For the standard version, setting machdep.tsc_freq to 0 causes a panic for division by 0 for obvious reasons instead of switching to the i8254 version like it is supposed to and does in my version. Standard versions just depend on the `tweak' timecounter being at index 0, which it is. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 16 02:47:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA17109 for freebsd-current-outgoing; Thu, 16 Jul 1998 02:47:36 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA17101 for ; Thu, 16 Jul 1998 02:47:31 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.5) with ESMTP id LAA01170; Thu, 16 Jul 1998 11:37:22 +0200 (CEST) To: jak@cetlink.net (John Kelly) cc: Bruce Evans , current@FreeBSD.ORG Subject: Re: tickadj -t not changing tick In-reply-to: Your message of "Thu, 16 Jul 1998 09:04:09 GMT." <35afc126.212112276@mail.cetlink.net> Date: Thu, 16 Jul 1998 11:37:22 +0200 Message-ID: <1168.900581842@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <35afc126.212112276@mail.cetlink.net>, John Kelly writes: >Argh! So should I change both kern.timecounter.frequency and the >machine dependent variable? Will that work? This is why it is so much easier just to start xntpd and be done with it. They only time where you need to tweak any sysctl's is when the hardware is outside the capture range (+/- 128 PPM ?) of xntpd. After I implemented timecounters, time keeping doesn't depend on tick, and since the adjustment is for all practical purposes continuous, there is no benefit of tweaking the sysctls. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 16 03:14:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA19703 for freebsd-current-outgoing; Thu, 16 Jul 1998 03:14:56 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ic.net (qmailr@srv1b.ic.net [152.160.72.20]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id DAA19698 for ; Thu, 16 Jul 1998 03:14:53 -0700 (PDT) (envelope-from rickl@ic.net) Received: (qmail 28606 invoked from network); 16 Jul 1998 10:14:32 -0000 Received: from unknown (HELO lurch.rickl.org) (152.160.108.51) by unknown with SMTP; 16 Jul 1998 10:14:32 -0000 Message-ID: X-Mailer: XFMail 1.2 [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: <199807160003.JAA02327@galois.tf.or.jp> Date: Thu, 16 Jul 1998 06:14:14 -0400 (EDT) Reply-To: rickl@ic.net Organization: ic.net From: Rick Lotoczky To: Tetsuro FURUYA Subject: Re: MAXUSERS kernel compile problem Cc: freebsd-current@FreeBSD.ORG, tfu@ff.iij4u.or.jp, mbriggs@switchboard.net Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi I had the same problem....just recompile config (in usr/src/usr.sbin) and then run config, all should be well. Rick On 16-Jul-98 Tetsuro FURUYA wrote: > Hi, Mr. Matt Briggs > > > In preveous mail, I have written that > >> > su-2.02# cd /usr/src/sys; egrep -aRi 'maxusers' conf i386/conf >> > conf/options:MAXUSERS opt_param.h >> >> For the first time I see this statement. >> When this statement comes to be generated ? >> >> So, how about you insert the following lines to config file. >> >> options MAXUSERS 10 >> or, >> MAXUSERS 10 >> >> Like other options in config file. >> > But, > > options MAXUSERS=10 > > must be right. As '=' is requitred in other options. > > > Tetsuro, Furuya. ht5t-fry@asahi-net.or.jp > > ======================================================================== > TEL: 048-852-3520 FAX: 048-858-1597 > E-Mail: > ht5t-fry@asahi-net.or.jp , tfu@ff.iij4u.or.jp > pgp-fingerprint: > pub Tetsuro FURUYA > Key fingerprint = F1 BA 5F C1 C2 48 1D C7 AE 5F 16 ED 12 17 75 38 > ========================================================================= > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 16 04:29:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA26652 for freebsd-current-outgoing; Thu, 16 Jul 1998 04:29:37 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from hub.org (hub.org [209.47.148.200]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA26633; Thu, 16 Jul 1998 04:29:25 -0700 (PDT) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by hub.org (8.8.8/8.7.5) with SMTP id HAA17762; Thu, 16 Jul 1998 07:29:11 -0400 (EDT) Date: Thu, 16 Jul 1998 07:29:11 -0400 (EDT) From: The Hermit Hacker To: scsi@FreeBSD.ORG cc: current@FreeBSD.ORG Subject: hub security check output (fwd) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Morning... I woke up this morning to see this in my mailbox, and am wondering if anyone can comment on it. The two drives referred to below are: hub# dmesg | egrep "da1|da2" da1 at ahc1 bus 0 target 0 lun 0 da1: Fixed Direct Access SCSI2 device da1: Serial Number PCB=20-113000-02; HDA=184701310988 da1: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled da1: 4341MB (8890760 512 byte sectors: 255H 63S/T 553C) da2 at ahc1 bus 0 target 1 lun 0 da2: Fixed Direct Access SCSI2 device da2: Serial Number PCB=20-113000-02; HDA=184709110359 da2: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled da2: 4341MB (8890760 512 byte sectors: 255H 63S/T 553C) Now, these drives are less then 2 months old, da2 being less then a couple of weeks old (we've already replaced it once). Both drives are running off the same SCSI controller: ahc1: rev 0x01 int a irq 11 on pci0.12.0 ahc1: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs My kernel is a Jun10th-CURRENT with the May20th CAM drivers installed. The question(s) are: 1. could this be caused by a bug in CURRENT or those CAM drivers? 2. could this be caused by a bad SCSI controller? 3. or am I just having real bad luck with SCSI drives? Thanks... ---------- Forwarded message ---------- Date: Thu, 16 Jul 1998 02:00:04 -0400 (EDT) From: Superuser To: undisclosed-recipients: ; Subject: hub security check output checking setuid files and devices: checking for uids of 0: root 0 hub kernel log messages: > (da1:ahc1:0:0:0): SCB 0x32 - timed out in dataout phase, SCSISIGI == 0xe6 > SEQADDR == 0x115 > SSTAT1 == 0x13 > (da1:ahc1:0:0:0): BDR message in message buffer > (da1:ahc1:0:0:0): SCB 0x32 - timed out in dataout phase, SCSISIGI == 0xf6 > SEQADDR == 0x115 > SSTAT1 == 0x13 > (da1:ahc1:0:0:0): no longer in timeout, status = 34b > ahc1: Issued Channel A Bus Reset. 4 SCBs aborted > (da1:ahc1:0:0:0): SCB 0x32 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 > SEQADDR == 0x18b > SSTAT1 == 0x0 > (da1:ahc1:0:0:0): Queuing a BDR SCB > (da1:ahc1:0:0:0): SCB 0x32 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 > SEQADDR == 0x18b > SSTAT1 == 0x0 > (da1:ahc1:0:0:0): no longer in timeout, status = 34b > ahc1: Issued Channel A Bus Reset. 2 SCBs aborted > (da2:ahc1:0:1:0): READ(10). CDB: 28 0 0 40 13 38 0 0 8 0 > (da2:ahc1:0:1:0): UNIT ATTENTION asc:29,2 > (da2:ahc1:0:1:0): Scsi bus reset occurred > (da1:ahc1:0:0:0): WRITE(06). CDB: a e be 60 10 0 > (da1:ahc1:0:0:0): UNIT ATTENTION asc:29,2 > (da1:ahc1:0:0:0): Scsi bus reset occurred > spec_getpages: I/O read failure: (error code=5) > size: 4096, resid: 4096, a_count: 4096, valid: 0x0 > nread: 0, reqpage: 0, pindex: 464671, pcount: 1 > vm_fault: pager input (probably hardware) error, PID 26899 failure To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 16 05:38:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA03400 for freebsd-current-outgoing; Thu, 16 Jul 1998 05:38:40 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns2.cetlink.net (root@ns2.cetlink.net [209.54.54.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA03391 for ; Thu, 16 Jul 1998 05:38:38 -0700 (PDT) (envelope-from jak@cetlink.net) Received: from EXIT10 (i485-gw.cetlink.net [209.198.15.97]) by ns2.cetlink.net (8.9.1/8.9.1) with SMTP id IAA29977; Thu, 16 Jul 1998 08:34:54 -0400 (EDT) From: jak@cetlink.net (John Kelly) To: Poul-Henning Kamp Cc: current@FreeBSD.ORG Subject: Re: tickadj -t not changing tick Date: Thu, 16 Jul 1998 12:37:44 GMT Message-ID: <35adf2b5.224800464@mail.cetlink.net> References: <1168.900581842@critter.freebsd.dk> In-Reply-To: <1168.900581842@critter.freebsd.dk> X-Mailer: Forte Agent 1.5/32.451 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id FAA03394 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 16 Jul 1998 11:37:22 +0200, Poul-Henning Kamp wrote: >>Argh! So should I change both kern.timecounter.frequency and the >>machine dependent variable? Will that work? > >This is why it is so much easier just to start xntpd and be done with it. > >They only time where you need to tweak any sysctl's is when the hardware >is outside the capture range (+/- 128 PPM ?) of xntpd. That's true for my hardware. >After I implemented timecounters, time keeping doesn't depend on tick, >and since the adjustment is for all practical purposes continuous, >there is no benefit of tweaking the sysctls. That sounds contradictory to the previous paragraph. So why tweak sysctls when it's outside the capture range of xntpd? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 16 05:45:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA04101 for freebsd-current-outgoing; Thu, 16 Jul 1998 05:45:00 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA04095 for ; Thu, 16 Jul 1998 05:44:57 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.5) with ESMTP id OAA02150; Thu, 16 Jul 1998 14:42:21 +0200 (CEST) To: jak@cetlink.net (John Kelly) cc: current@FreeBSD.ORG Subject: Re: tickadj -t not changing tick In-reply-to: Your message of "Thu, 16 Jul 1998 12:37:44 GMT." <35adf2b5.224800464@mail.cetlink.net> Date: Thu, 16 Jul 1998 14:42:20 +0200 Message-ID: <2148.900592940@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <35adf2b5.224800464@mail.cetlink.net>, John Kelly writes: >>>Argh! So should I change both kern.timecounter.frequency and the >>>machine dependent variable? Will that work? >> >>This is why it is so much easier just to start xntpd and be done with it. >> >>They only time where you need to tweak any sysctl's is when the hardware >>is outside the capture range (+/- 128 PPM ?) of xntpd. > >That's true for my hardware. > >>After I implemented timecounters, time keeping doesn't depend on tick, >>and since the adjustment is for all practical purposes continuous, >>there is no benefit of tweaking the sysctls. > >That sounds contradictory to the previous paragraph. So why tweak >sysctls when it's outside the capture range of xntpd? To get it inside xntpd's capture range ? -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 16 06:05:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA06472 for freebsd-current-outgoing; Thu, 16 Jul 1998 06:05:45 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns2.cetlink.net (root@ns2.cetlink.net [209.54.54.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA06465 for ; Thu, 16 Jul 1998 06:05:43 -0700 (PDT) (envelope-from jak@cetlink.net) Received: from EXIT10 (i485-gw.cetlink.net [209.198.15.97]) by ns2.cetlink.net (8.9.1/8.9.1) with SMTP id JAA02590; Thu, 16 Jul 1998 09:01:57 -0400 (EDT) From: jak@cetlink.net (John Kelly) To: Poul-Henning Kamp Cc: current@FreeBSD.ORG Subject: Re: tickadj -t not changing tick Date: Thu, 16 Jul 1998 13:04:48 GMT Message-ID: <35adf8c4.226351854@mail.cetlink.net> References: <2148.900592940@critter.freebsd.dk> In-Reply-To: <2148.900592940@critter.freebsd.dk> X-Mailer: Forte Agent 1.5/32.451 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id GAA06466 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 16 Jul 1998 14:42:20 +0200, Poul-Henning Kamp wrote: >>>They only time where you need to tweak any sysctl's is when the hardware >>>is outside the capture range (+/- 128 PPM ?) of xntpd. >> >>That's true for my hardware. >> >>>After I implemented timecounters, time keeping doesn't depend on tick, >>>and since the adjustment is for all practical purposes continuous, >>>there is no benefit of tweaking the sysctls. >> >>That sounds contradictory to the previous paragraph. So why tweak >>sysctls when it's outside the capture range of xntpd? > >To get it inside xntpd's capture range ? First you say don't bother, then you say it's worthwhile. Since tweaking sysctls is sometimes needed to get the hardware within xntpd's capture range, then, even in the case where the hardware may be within the capture range, why not go ahead and tweak the sysctl to a more accurate value? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 16 06:29:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA09760 for freebsd-current-outgoing; Thu, 16 Jul 1998 06:29:00 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from csns02.comp.polyu.edu.hk (csns02.COMP.POLYU.EDU.HK [158.132.25.95]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA09750 for ; Thu, 16 Jul 1998 06:28:56 -0700 (PDT) (envelope-from c5666305@comp.polyu.edu.hk) Received: from cssolar85.COMP.HKP.HK (cssolar85 [158.132.8.174]) by csns02.comp.polyu.edu.hk (8.8.8/8.8.8) with SMTP id VAA15999 for ; Thu, 16 Jul 1998 21:27:46 +0800 (HKT) Received: (from c5666305@localhost) by cssolar85.COMP.HKP.HK (SMI-8.6/) id VAA29450 for freebsd-current@freebsd.org; Thu, 16 Jul 1998 21:27:44 +0800 Message-Id: <199807161327.VAA29450@cssolar85.COMP.HKP.HK> Subject: what does this mean da0:(ahc0:0:0:0) ... To: freebsd-current@FreeBSD.ORG Date: Thu, 16 Jul 1998 21:27:43 +0800 (HKT) From: "c5666305" X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I just upgrade to cam-980712 (3.0-snap) and found this message da0:(ahc0:0:0:0) tagged openings now 8. What does it mean ? can anyone tell me. Does it harmful ? Thanks. Clarence CHAN To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 16 06:35:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA10403 for freebsd-current-outgoing; Thu, 16 Jul 1998 06:35:49 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pop.asahi-net.or.jp (pop.asahi-net.or.jp [202.224.39.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA10395 for ; Thu, 16 Jul 1998 06:35:42 -0700 (PDT) (envelope-from tfuruya@ppp142116.asahi-net.or.jp) Received: from galois.tf.or.jp (ppp142116.asahi-net.or.jp [202.213.142.116]) by pop.asahi-net.or.jp (8.8.8/3.6W) with ESMTP id WAA05872; Thu, 16 Jul 1998 22:40:42 +0900 Received: from galois.tf.or.jp (localhost.tf.or.jp [127.0.0.1]) by galois.tf.or.jp (8.8.8/3.6W-ht5t-fry@asahi-net-98042218) with ESMTP id WAA07429; Thu, 16 Jul 1998 22:34:34 +0900 (JST) Message-Id: <199807161334.WAA07429@galois.tf.or.jp> To: rickl@ic.net Cc: freebsd-current@FreeBSD.ORG, tfu@ff.iij4u.or.jp, mbriggs@switchboard.net, Niall Smart , Bruce Evans Subject: Re: MAXUSERS kernel compile problem From: Tetsuro FURUYA Reply-To: Tetsuro FURUYA In-Reply-To: Your message of "Thu, 16 Jul 1998 06:14:14 -0400 (EDT)" References: X-Mailer: Mew version 1.54 on Emacs 19.28.1, Mule 2.3 X-fingerprint: F1 BA 5F C1 C2 48 1D C7 AE 5F 16 ED 12 17 75 38 X-URL: http://sodan.komaba.ecc.u-tokyo.ac.jp/~tfuruya/ Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Thu, 16 Jul 1998 22:34:34 +0900 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG That's very good reports. In Message-ID: Rick Lotoczky worte: > Hi > > I had the same problem....just recompile config (in usr/src/usr.sbin) and then > run config, all should be well. > > Rick So, there were 2 ( 3 ? ) reports that 'config' command has changed, and that recompilation of new 'config' command resolve the problem of kernel compilation. I appreciate the efforts of all of you, and thank all of you ! Tetsuro, Furuya. ht5t-fry@asahi-net.or.jp ======================================================================== TEL: 048-852-3520 FAX: 048-858-1597 E-Mail: ht5t-fry@asahi-net.or.jp , tfu@ff.iij4u.or.jp pgp-fingerprint: pub Tetsuro FURUYA Key fingerprint = F1 BA 5F C1 C2 48 1D C7 AE 5F 16 ED 12 17 75 38 ========================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 16 06:40:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA11139 for freebsd-current-outgoing; Thu, 16 Jul 1998 06:40:40 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zone.baldcom.net (green@zone.BALDCOM.NET [205.232.46.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA11131 for ; Thu, 16 Jul 1998 06:40:38 -0700 (PDT) (envelope-from green@zone.baldcom.net) Received: from localhost (green@localhost) by zone.baldcom.net (8.8.8/8.8.7) with SMTP id JAA28227 for ; Thu, 16 Jul 1998 09:39:47 -0400 (EDT) Date: Thu, 16 Jul 1998 09:39:46 -0400 (EDT) From: Brian Feldman To: current@FreeBSD.ORG Subject: Re: tickadj -t not changing tick In-Reply-To: <2148.900592940@critter.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 16 Jul 1998, Poul-Henning Kamp wrote: > In message <35adf2b5.224800464@mail.cetlink.net>, John Kelly writes: > > >>>Argh! So should I change both kern.timecounter.frequency and the > >>>machine dependent variable? Will that work? > >> > >>This is why it is so much easier just to start xntpd and be done with it. > >> > >>They only time where you need to tweak any sysctl's is when the hardware > >>is outside the capture range (+/- 128 PPM ?) of xntpd. > > > >That's true for my hardware. > > > >>After I implemented timecounters, time keeping doesn't depend on tick, > >>and since the adjustment is for all practical purposes continuous, > >>there is no benefit of tweaking the sysctls. > > > >That sounds contradictory to the previous paragraph. So why tweak > >sysctls when it's outside the capture range of xntpd? > > To get it inside xntpd's capture range ? > > -- > Poul-Henning Kamp FreeBSD coreteam member > phk@FreeBSD.ORG "Real hackers run -current on their laptop." > "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > FWIW, I've always just been band-aiding the problem, i.e. add "ntpdate tick.usno.navy.mil" to ppp.linkup, or if having a real connection, sticking it in crontab. Brian Feldman green@zona.baldcom.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 16 07:06:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA14616 for freebsd-current-outgoing; Thu, 16 Jul 1998 07:06:13 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from csns02.comp.polyu.edu.hk (csns02.COMP.POLYU.EDU.HK [158.132.25.95]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA14597 for ; Thu, 16 Jul 1998 07:06:06 -0700 (PDT) (envelope-from c5666305@comp.polyu.edu.hk) Received: from cssolar85.COMP.HKP.HK (cssolar85 [158.132.8.174]) by csns02.comp.polyu.edu.hk (8.8.8/8.8.8) with SMTP id WAA16336 for ; Thu, 16 Jul 1998 22:04:46 +0800 (HKT) Received: (from c5666305@localhost) by cssolar85.COMP.HKP.HK (SMI-8.6/) id WAA29473 for freebsd-current@freebsd.org; Thu, 16 Jul 1998 22:04:43 +0800 Message-Id: <199807161404.WAA29473@cssolar85.COMP.HKP.HK> Subject: pthread for 3.0-snap To: freebsd-current@FreeBSD.ORG Date: Thu, 16 Jul 1998 22:04:43 +0800 (HKT) From: "c5666305" X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I would like to know if there exist a version of pthread supporting 3.0-snap. I know it is supporting 2.x. Thanks. Clarence CHAN To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 16 07:16:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA15618 for freebsd-current-outgoing; Thu, 16 Jul 1998 07:16:55 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nomis.simon-shapiro.org ([209.86.126.163]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id HAA15613 for ; Thu, 16 Jul 1998 07:16:53 -0700 (PDT) (envelope-from shimon@simon-shapiro.org) Received: (qmail 24135 invoked by uid 1000); 16 Jul 1998 15:18:55 -0000 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Thu, 16 Jul 1998 11:18:55 -0400 (EDT) Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: Chris Dillon Subject: RE: Softupdates crash: Got it! Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On a totally different subject; Where did you register your domain name? I keep forgetting the name of that non-internic entity. Thanx! Simon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 16 07:47:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA19806 for freebsd-current-outgoing; Thu, 16 Jul 1998 07:47:20 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from localhost.ziplink.net (mi@kot.ne.mediaone.net [24.128.29.55]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA19799 for ; Thu, 16 Jul 1998 07:47:18 -0700 (PDT) (envelope-from mi@rtfm.ziplink.net) Received: from rtfm.ziplink.net (mi@rtfm [199.232.255.52]) by localhost.ziplink.net (8.8.8/8.8.7) with ESMTP id OAA03900 for ; Thu, 16 Jul 1998 14:47:06 GMT (envelope-from mi@rtfm.ziplink.net) Received: (from mi@localhost) by rtfm.ziplink.net (8.8.8/8.8.5) id KAA06046 for current@freebsd.org; Thu, 16 Jul 1998 10:47:06 -0400 (EDT) From: Mikhail Teterin Message-Id: <199807161447.KAA06046@rtfm.ziplink.net> Subject: Re: tickadj -t not changing tick In-Reply-To: <35aeb750.209593961@mail.cetlink.net> from "John Kelly" at "Jul 16, 98 08:38:25 am" To: current@FreeBSD.ORG Date: Thu, 16 Jul 1998 10:47:06 -0400 (EDT) X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli" wrote: =>The real way is to run ntpd, if you don't have a permanent connection, =>consider looking into "burstmode" in the new xntpd4... =According to John Polstra in an archived message about tickadj, his ="real way" is to adjust the undisciplined clock before running xntpd, =formerly with tickadj, but now via sysctl as Bruce suggested. I like =the idea of getting the kernel synchronized with the hardware before =trying to run xntpd. [...] You, people, are just kidding, right? There is no way this nonsense is going to be required for longer then a week, until one wizard or another commits a patch? My machine hare not only ran windoze without time problems before it came to my hands, it also ran FreeBSD-2.2 with clock running just peachy. -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 16 08:06:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA23063 for freebsd-current-outgoing; Thu, 16 Jul 1998 08:06:58 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA23044 for ; Thu, 16 Jul 1998 08:06:55 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.8.8/8.7.3) id JAA21042; Thu, 16 Jul 1998 09:01:19 -0600 (MDT) Date: Thu, 16 Jul 1998 09:01:19 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199807161501.JAA21042@narnia.plutotech.com> To: "c5666305" cc: current@FreeBSD.ORG Subject: Re: what does this mean da0:(ahc0:0:0:0) ... Newsgroups: pluto.freebsd.current In-Reply-To: <199807161327.VAA29450@cssolar85.COMP.HKP.HK> User-Agent: tin/pre-1.4-971204 (UNIX) (FreeBSD/3.0-CURRENT (i386)) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Queations about CAM should really go to the SCSI list... > Hello, > > I just upgrade to cam-980712 (3.0-snap) and found this message > da0:(ahc0:0:0:0) tagged openings now 8. What does it mean ? can anyone > tell me. Does it harmful ? Thanks. It means that CAM has discovered that this device will only accept 8 transactions in parallel and has reduced the number of resources it has allocated to that device accordingly. > Clarence CHAN -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 16 08:43:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA28194 for freebsd-current-outgoing; Thu, 16 Jul 1998 08:43:53 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id IAA28184 for ; Thu, 16 Jul 1998 08:43:48 -0700 (PDT) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0ywqC0-0001HG-00; Thu, 16 Jul 1998 09:43:36 -0600 Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.8.8/8.8.3) with ESMTP id JAA25102 for ; Thu, 16 Jul 1998 09:44:58 -0600 (MDT) Message-Id: <199807161544.JAA25102@harmony.village.org> To: current@FreeBSD.ORG Subject: Proposed fix for ___error problem. Date: Thu, 16 Jul 1998 09:44:57 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG OK. I have found that a -current from approx Oct exhibits this error when I do a 'make buildworld -m /usr/src/share/mk'. So I got into digging into this problem and discovered that I can fix it and the MACHINE_ARCH problem fairly well for legacy systems. Enclosed please find a patch to do both of these things. First, if MACHINE_ARCH isn't defined, I define it to be ${MACHINE} in bsd.own.mk. Next, I've moved the format selection from bsd.lib.mk to bsd.own.mk because it is defined too late to give ${LIBDIR} a meaningful value on aout machine (it should be /usr/lib/aout, but instead winds up defaulting to /usr/lib). I've tested these patches on my Jul 4 current machine as well as my Octish current machine. If people could attempt to do a make buildworld like I quoted above (substituting the path of the source tree for /usr/src) and let me know if they encounter problems with this on their machine. I'm most interested in 2.2.x machines since I don't have one of those I can easily do a buildworld on to test this out. Also, can people please comment on the changes themselves? Warner Index: bsd.lib.mk =================================================================== RCS file: /home/imp/FreeBSD/CVS/src/share/mk/bsd.lib.mk,v retrieving revision 1.74 diff -u -r1.74 bsd.lib.mk --- bsd.lib.mk 1998/06/05 18:38:54 1.74 +++ bsd.lib.mk 1998/07/16 15:37:59 @@ -6,13 +6,6 @@ .include "${.CURDIR}/../Makefile.inc" .endif -# Default executable format -.if ${MACHINE} == "alpha" -BINFORMAT?= elf -.else -BINFORMAT?= aout -.endif - .if exists(${.CURDIR}/shlib_version) SHLIB_MAJOR != . ${.CURDIR}/shlib_version ; echo $$major .if ${BINFORMAT} == aout Index: bsd.own.mk =================================================================== RCS file: /home/imp/FreeBSD/CVS/src/share/mk/bsd.own.mk,v retrieving revision 1.14 diff -u -r1.14 bsd.own.mk --- bsd.own.mk 1998/05/26 20:12:54 1.14 +++ bsd.own.mk 1998/07/16 15:38:03 @@ -122,6 +122,15 @@ BINMODE?= 555 NOBINMODE?= 444 +MACHINE_ARCH?=${MACHINE} + +# Default executable format +.if ${MACHINE} == "alpha" +BINFORMAT?= elf +.else +BINFORMAT?= aout +.endif + .if ${BINFORMAT} == aout LIBDIR?= /usr/lib/aout .else To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 16 08:47:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA28797 for freebsd-current-outgoing; Thu, 16 Jul 1998 08:47:35 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id IAA28789 for ; Thu, 16 Jul 1998 08:47:32 -0700 (PDT) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0ywqFe-0001I1-00; Thu, 16 Jul 1998 09:47:22 -0600 Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.8.8/8.8.3) with ESMTP id JAA00694; Thu, 16 Jul 1998 09:48:43 -0600 (MDT) Message-Id: <199807161548.JAA00694@harmony.village.org> To: Terry Lambert Subject: Re: /usr/src/sbin/i386/mount_msdos - can we move it already? Cc: jkh@time.cdrom.com (Jordan K. Hubbard), current@FreeBSD.ORG In-reply-to: Your message of "Thu, 16 Jul 1998 05:45:14 -0000." <199807160545.WAA13187@usr07.primenet.com> References: <199807160545.WAA13187@usr07.primenet.com> Date: Thu, 16 Jul 1998 09:48:43 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199807160545.WAA13187@usr07.primenet.com> Terry Lambert writes: : In point of fact, the PReP and CHRP standards both require a DOS : partition table (these are for Motorola PPC based hardware). As do the ARC BIOS standards for at least the MIPS based PC-like machines. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 16 09:11:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA01642 for freebsd-current-outgoing; Thu, 16 Jul 1998 09:11:03 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns2.cetlink.net (root@ns2.cetlink.net [209.54.54.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA01636 for ; Thu, 16 Jul 1998 09:10:53 -0700 (PDT) (envelope-from jak@cetlink.net) Received: from EXIT10 (i485-gw.cetlink.net [209.198.15.97]) by ns2.cetlink.net (8.9.1/8.9.1) with SMTP id MAA20799; Thu, 16 Jul 1998 12:10:34 -0400 (EDT) From: jak@cetlink.net (John Kelly) To: Mikhail Teterin Cc: current@FreeBSD.ORG Subject: Re: tickadj -t not changing tick Date: Thu, 16 Jul 1998 16:13:26 GMT Message-ID: <35ae253a.237736064@mail.cetlink.net> References: <199807161447.KAA06046@rtfm.ziplink.net> In-Reply-To: <199807161447.KAA06046@rtfm.ziplink.net> X-Mailer: Forte Agent 1.5/32.451 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id JAA01637 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 16 Jul 1998 10:47:06 -0400 (EDT), Mikhail Teterin wrote: >=>The real way is to run ntpd, if you don't have a permanent connection, >=>consider looking into "burstmode" in the new xntpd4... > >=According to John Polstra in an archived message about tickadj, his >="real way" is to adjust the undisciplined clock before running xntpd, >=formerly with tickadj, but now via sysctl as Bruce suggested. I like >=the idea of getting the kernel synchronized with the hardware before >=trying to run xntpd. >[...] > >You, people, are just kidding, right? Totally and deadly serious. >There is no way this nonsense is going to be required for longer then >a week, until one wizard or another commits a patch? Many wizards have committed many patches just to get us where we are today. >My machine hare not only ran windoze without time problems before it >came to my hands That speaks for itself. >it also ran FreeBSD-2.2 with clock running just peachy. Clock? You mean a little X app? Wheeeee! (Sorry, but one silly post deserves another) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 16 09:43:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA07630 for freebsd-current-outgoing; Thu, 16 Jul 1998 09:43:16 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from localhost.ziplink.net (mi@kot.ne.mediaone.net [24.128.29.55]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA07623 for ; Thu, 16 Jul 1998 09:43:04 -0700 (PDT) (envelope-from mi@rtfm.ziplink.net) Received: from rtfm.ziplink.net (mi@rtfm [199.232.255.52]) by localhost.ziplink.net (8.8.8/8.8.7) with ESMTP id QAA04496; Thu, 16 Jul 1998 16:42:31 GMT (envelope-from mi@rtfm.ziplink.net) Received: (from mi@localhost) by rtfm.ziplink.net (8.8.8/8.8.5) id MAA06432; Thu, 16 Jul 1998 12:42:30 -0400 (EDT) From: Mikhail Teterin Message-Id: <199807161642.MAA06432@rtfm.ziplink.net> Subject: Re: tickadj -t not changing tick In-Reply-To: <35ae253a.237736064@mail.cetlink.net> from "John Kelly" at "Jul 16, 98 04:13:26 pm" To: current@FreeBSD.ORG Date: Thu, 16 Jul 1998 12:42:30 -0400 (EDT) Cc: jak@cetlink.net X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli"There is no way this nonsense is going to be required for longer then =>a week, until one wizard or another commits a patch? = =Many wizards have committed many patches just to get us where we are =today. And today, the -current's handling of machine's clock is broken -- for some machines, at least. =>My machine hare not only ran windoze without time problems before it =>came to my hands = =That speaks for itself. Please, explain what you are trying to say, sir... Kindly excuse my poor English comprehension, and try to be clear and specific. =>it also ran FreeBSD-2.2 with clock running just peachy. = =Clock? You mean a little X app? Wheeeee! (Sorry, but one silly post =deserves another) No. Not a little clock. I mean, the machine's clock never used to gain 10-20 seconds an hour until I installed the May's snapshot of the current. It's too bad, that the silly form of my post masked its very serious content. I meant to ask a question: is the current state recognized as broken? what is the ETA for a fix? -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 16 09:47:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA08573 for freebsd-current-outgoing; Thu, 16 Jul 1998 09:47:43 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA08555 for ; Thu, 16 Jul 1998 09:47:30 -0700 (PDT) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.8/8.8.8) with ESMTP id JAA26999 for ; Thu, 16 Jul 1998 09:46:56 -0700 (PDT) (envelope-from jdp) Message-Id: <199807161646.JAA26999@austin.polstra.com> To: current@FreeBSD.ORG Subject: Make release fails because kernel is too large Date: Thu, 16 Jul 1998 09:46:55 -0700 From: John Polstra Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Make release of -current is failing, because the install kernel is too large to fit into the filesystem on the boot floppy: loading kernel rearranging symbols text data bss dec hex 1314816 1560576 121404 2996796 2dba3c ./dumpnlist /R/stage/boot.std/kernel > /tmp/mnt_xx/stand/symbols ./write_mfs_in_kernel /R/stage/boot.std/kernel fs-image.std kzip -v /R/stage/boot.std/kernel real kernel start address will be: 0x100000 real kernel end address will be: 0x3dba3c kzip data start address will be: 0x28b91e kzip data end address will be: 0x3e3990 sh -e /usr/src/release/doFS.sh /R/stage /mnt 1440 /R/stage/boot.std 100000 fd14 40 disklabel: ioctl DIOCWLABEL: Operation not supported by device Warning: Block size restricts cylinders per group to 9. /dev/rvn0c: 2880 sectors in 1 cylinders of 1 tracks, 2880 sectors 1.4MB in 1 cyl groups (9 c/g, 12.66MB/g, 32 i/g) super-block backups (for fsck -b #) at: 32, cpio: write error: No space left on device *** Error code 1 Does anybody have an idea of what we can take out? It seems likely that when CAM comes in, it will further expand the kernel. And CAM definitely needs to come in. It looks like we are currently too big by about 3K. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 16 10:02:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA10226 for freebsd-current-outgoing; Thu, 16 Jul 1998 10:02:50 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from duey.hs.wolves.k12.mo.us (root@duey.hs.wolves.k12.mo.us [207.160.214.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA10221 for ; Thu, 16 Jul 1998 10:02:47 -0700 (PDT) (envelope-from cdillon@wolves.k12.mo.us) Received: from duey.hs.wolves.k12.mo.us (cdillon@duey.hs.wolves.k12.mo.us [207.160.214.9]) by duey.hs.wolves.k12.mo.us (8.8.7/8.8.7) with SMTP id MAA06498; Thu, 16 Jul 1998 12:02:29 -0500 (CDT) (envelope-from cdillon@wolves.k12.mo.us) Date: Thu, 16 Jul 1998 12:02:29 -0500 (CDT) From: Chris Dillon X-Sender: cdillon@duey.hs.wolves.k12.mo.us To: Dag-Erling Coidan Smørgrav cc: current@FreeBSD.ORG Subject: Re: Softupdates crash: Got it! In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by hub.freebsd.org id KAA10222 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 16 Jul 1998, Dag-Erling Coidan Smørgrav wrote: > Chris Dillon writes: > > The elusive "newdirrem: inum %d should be %d" reared its head again, > > and I finally caught it in the act. > > Somehow I feel a celebration is required. Like when Zim catches the > brain bug in _Starship Troopers_... Unfortunately I haven't seen Starship Troopers. Did I miss much? :-) I suppose we shouldn't celebrate until it is actually fixed. -- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net /* FreeBSD: The fastest and most stable server OS on the planet. For Intel x86 and compatibles (SPARC and Alpha under development) (http://www.freebsd.org) */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 16 10:23:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA13023 for freebsd-current-outgoing; Thu, 16 Jul 1998 10:23:15 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA13004 for ; Thu, 16 Jul 1998 10:23:12 -0700 (PDT) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 0ywrjt-0002J2-00; Thu, 16 Jul 1998 10:22:41 -0700 Date: Thu, 16 Jul 1998 10:22:39 -0700 (PDT) From: Tom X-Sender: tom@shell.uniserve.ca To: nik@iii.co.uk cc: Tim Vanderhoek , "Scot W. Hetzel" , joelh@gnu.org, FreeBSD-Current Subject: Re: aout / elf library directories In-Reply-To: <19980716100751.16056@iii.co.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 16 Jul 1998 nik@iii.co.uk wrote: > On Thu, Jul 16, 1998 at 01:52:29AM -0400, Tim Vanderhoek wrote: > > I think the timeframe for the death of /usr/lib/elf is within the next > > couple weeks, if all goes well. > > [ Disclaimer: this is well out of my general area of expertise, but this > has had me wondering for a while ] > > I'm a little confused by this. If I understand correctly, there are some > niggling problems with ELF (which is why we have tools such as brandelf) brandelf has little do with this. You need brandelf to mark binaries as to which ABI the binary is for. However, aout support will be required for support of dynamically linked 2.2 binaries. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 16 11:08:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA19318 for freebsd-current-outgoing; Thu, 16 Jul 1998 11:08:58 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ifi.uio.no (0@ifi.uio.no [129.240.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA19311 for ; Thu, 16 Jul 1998 11:08:50 -0700 (PDT) (envelope-from dag-erli@ifi.uio.no) Received: from hrotti.ifi.uio.no (2602@hrotti.ifi.uio.no [129.240.64.15]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id UAA06666 for ; Thu, 16 Jul 1998 20:08:38 +0200 (MET DST) Received: (from dag-erli@localhost) by hrotti.ifi.uio.no ; Thu, 16 Jul 1998 20:08:37 +0200 (MET DST) Mime-Version: 1.0 To: current@FreeBSD.ORG Subject: make installworld -j8 Organization: University of Oslo, Department of Informatics X-url: http://www.stud.ifi.uio.no/~dag-erli/ X-other-addresses: 'finger dag-erli@ifi.uio.no' for a list X-disclaimer-1: The views expressed in this article are mine alone, and do X-disclaimer-2: not necessarily coincide with those of any organisation or X-disclaimer-3: company with which am or have been affiliated. X-Stop-Spam: http://www.cauce.org/ From: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= ) Date: 16 Jul 1998 20:08:36 +0200 Message-ID: Lines: 28 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Here's a nice little race condition for you: ===> bin/sh --- realinstall --- --- maninstall --- --- realinstall --- install -c -s -o bin -g bin -m 555 sh /bin --- maninstall --- Could not execute shell *** Error code 1 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error make can't execute /bin/sh to install the sh(1) man pages because /bin/sh is in the process of being clobbered by a sibling make process. Shouldn't make installworld use the freshly compiled sh from /usr/obj rather than /bin/sh? DES -- One two, one two, one two. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 16 11:57:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA26887 for freebsd-current-outgoing; Thu, 16 Jul 1998 11:57:42 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.133.1] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA26882 for ; Thu, 16 Jul 1998 11:57:36 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.5) with ESMTP id UAA03044; Thu, 16 Jul 1998 20:54:39 +0200 (CEST) To: John Polstra cc: current@FreeBSD.ORG Subject: Re: Make release fails because kernel is too large In-reply-to: Your message of "Thu, 16 Jul 1998 09:46:55 PDT." <199807161646.JAA26999@austin.polstra.com> Date: Thu, 16 Jul 1998 20:54:39 +0200 Message-ID: <3042.900615279@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199807161646.JAA26999@austin.polstra.com>, John Polstra writes: >Make release of -current is failing, because the install kernel is >too large to fit into the filesystem on the boot floppy: Hmm, what was it Jordan said to me that made me agree to kill the 1200K boot floppy, "and with 1.44 we have plenty of space for a couple of years at least, well, maybe not that long time but you get the idea..." You were right. What's next Jordan ? -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 16 12:06:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA27658 for freebsd-current-outgoing; Thu, 16 Jul 1998 12:06:15 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.133.1] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA27646 for ; Thu, 16 Jul 1998 12:06:03 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.5) with ESMTP id VAA03099; Thu, 16 Jul 1998 21:02:22 +0200 (CEST) To: Mikhail Teterin cc: current@FreeBSD.ORG, jak@cetlink.net Subject: Re: tickadj -t not changing tick In-reply-to: Your message of "Thu, 16 Jul 1998 12:42:30 EDT." <199807161642.MAA06432@rtfm.ziplink.net> Date: Thu, 16 Jul 1998 21:02:22 +0200 Message-ID: <3097.900615742@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >No. Not a little clock. I mean, the machine's clock never used to >gain 10-20 seconds an hour until I installed the May's snapshot of >the current. It's too bad, that the silly form of my post masked >its very serious content. I meant to ask a question: > > is the current state recognized as broken? > what is the ETA for a fix? Is APM enabled in your BIOS-SETUP ? What kind of machine ? Add these options to your kernel: options "CLK_USE_I8254_CALIBRATION" options CLK_USE_TSC_CALIBRATION and send me email with dmesg from a "boot -v" -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 16 12:52:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA03505 for freebsd-current-outgoing; Thu, 16 Jul 1998 12:52:55 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from korin.warman.org.pl (korin.nask.waw.pl [148.81.160.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA03486 for ; Thu, 16 Jul 1998 12:52:44 -0700 (PDT) (envelope-from abial@nask.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.8.8/8.8.5) with SMTP id VAA25773; Thu, 16 Jul 1998 21:55:31 +0200 (CEST) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Thu, 16 Jul 1998 21:55:30 +0200 (CEST) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: John Polstra cc: current@FreeBSD.ORG Subject: Re: Make release fails because kernel is too large In-Reply-To: <199807161646.JAA26999@austin.polstra.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 16 Jul 1998, John Polstra wrote: > Make release of -current is failing, because the install kernel is > too large to fit into the filesystem on the boot floppy: > Does anybody have an idea of what we can take out? It seems likely > that when CAM comes in, it will further expand the kernel. And CAM > definitely needs to come in. Perhaps with the advent of CAM boot floppies we should also use DEVFS, which would allow for saving ca. 50kB on inodes' space. Andrzej Bialecki +---------------------+------------------------+--------------------------+ | | When in problem or in | if(halt_per_mth > 0) { | | Research & Academic | doubt, run in circles, | fetch("FreeBSD"); | | Network in Poland | scream and shout. | } | + --------------------+------------------------+--------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 16 13:13:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA07219 for freebsd-current-outgoing; Thu, 16 Jul 1998 13:13:07 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA07208 for ; Thu, 16 Jul 1998 13:13:03 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id NAA04196; Thu, 16 Jul 1998 13:07:19 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: Poul-Henning Kamp cc: John Polstra , current@FreeBSD.ORG Subject: Re: Make release fails because kernel is too large In-reply-to: Your message of "Thu, 16 Jul 1998 20:54:39 +0200." <3042.900615279@critter.freebsd.dk> Date: Thu, 16 Jul 1998 13:07:19 -0700 Message-ID: <4192.900619639@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'll look into the kernel and see what can be sed'd out specifically for the boot floppy. Fortunately, we do this already for an number of items (like the NFS server code) so it's easy to add new stuff to the list. - Jordan > In message <199807161646.JAA26999@austin.polstra.com>, John Polstra writes: > >Make release of -current is failing, because the install kernel is > >too large to fit into the filesystem on the boot floppy: > > Hmm, what was it Jordan said to me that made me agree to kill the 1200K > boot floppy, "and with 1.44 we have plenty of space for a couple of years > at least, well, maybe not that long time but you get the idea..." > > You were right. What's next Jordan ? > > -- > Poul-Henning Kamp FreeBSD coreteam member > phk@FreeBSD.ORG "Real hackers run -current on their laptop." > "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 16 13:24:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA08289 for freebsd-current-outgoing; Thu, 16 Jul 1998 13:24:34 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.westbend.net (ns1.westbend.net [207.217.224.194]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA08284 for ; Thu, 16 Jul 1998 13:24:33 -0700 (PDT) (envelope-from hetzels@westbend.net) Received: from admin (admin.westbend.net [207.217.224.195]) by mail.westbend.net (8.8.8/8.8.8) with SMTP id PAA07529 for ; Thu, 16 Jul 1998 15:24:23 -0500 (CDT) (envelope-from hetzels@westbend.net) Message-ID: <00df01bdb0f7$b88cfc60$c3e0d9cf@westbend.net> From: "Scot W. Hetzel" To: Subject: Re: Make release fails because kernel is too large Date: Thu, 16 Jul 1998 15:24:22 -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.0518.4 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.0518.4 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From: Poul-Henning Kamp >Hmm, what was it Jordan said to me that made me agree to kill the 1200K >boot floppy, "and with 1.44 we have plenty of space for a couple of years >at least, well, maybe not that long time but you get the idea..." > >You were right. What's next Jordan ? > What about using 1.68 or 1.72 MB floppies? FDformat can make these kinds of disks for DOS systems ( ftp://ftp.univ-lille1.fr/pub/pc/coast/msdos/diskutil/fdform18.zip , FDformat has sources included (PASCAL)). I also read that mtools might be able to create >1.44MB floppies. So what would it take to get FreeBSD to create 1.68/1.72MB floppies for the release floppies? That would give an extra 240-280K for the boot floppy. Would fdimage need to be updated or replaced? Scot To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 16 14:05:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA13766 for freebsd-current-outgoing; Thu, 16 Jul 1998 14:05:48 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from echonyc.com (echonyc.com [198.67.15.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA13753 for ; Thu, 16 Jul 1998 14:05:46 -0700 (PDT) (envelope-from benedict@echonyc.com) Received: from localhost (benedict@localhost) by echonyc.com (8.8.7/8.8.7) with SMTP id RAA23273; Thu, 16 Jul 1998 17:05:12 -0400 (EDT) Date: Thu, 16 Jul 1998 17:05:11 -0400 (EDT) From: Snob Art Genre Reply-To: ben@rosengart.com To: "Scot W. Hetzel" cc: current@FreeBSD.ORG Subject: Re: Make release fails because kernel is too large In-Reply-To: <00df01bdb0f7$b88cfc60$c3e0d9cf@westbend.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 16 Jul 1998, Scot W. Hetzel wrote: > What about using 1.68 or 1.72 MB floppies? I think that this would drastically reduce the amount of FreeBSD-friendly hardware out there. Ben "You have your mind on computers, it seems." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 16 14:20:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA17188 for freebsd-current-outgoing; Thu, 16 Jul 1998 14:20:11 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp04.primenet.com (daemon@smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA17183 for ; Thu, 16 Jul 1998 14:20:09 -0700 (PDT) (envelope-from tlambert@usr07.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id OAA06894 for ; Thu, 16 Jul 1998 14:19:53 -0700 (MST) Received: from usr07.primenet.com(206.165.6.207) via SMTP by smtp04.primenet.com, id smtpd006878; Thu Jul 16 14:19:45 1998 Received: (from tlambert@localhost) by usr07.primenet.com (8.8.5/8.8.5) id OAA03471 for current@freebsd.org; Thu, 16 Jul 1998 14:19:44 -0700 (MST) From: Terry Lambert Message-Id: <199807162119.OAA03471@usr07.primenet.com> Subject: PTHREADS: broken in current, stable? To: current@FreeBSD.ORG Date: Thu, 16 Jul 1998 21:19:44 +0000 (GMT) X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have received a bug report from someone attempting to run LDAP that the libc_r implementation fails to allow LDAP to operate correctly. This may be nothing, but he is running a -stable system, recently upgraded. With the pending release of 2.2.7, this is protentially a rather large bug; I don't know of other programs that are really exercising the threads code. In the LDAP patches, I used PTHREAD_MUTEX_INITIALIZER to determine if the pthreads implementation was Darft 4, or if it was Draft 10 (Final standard). This bears on how a number of threads functions operate; most notably, a Draft 4 implementation is expected to take the address of an attribute pointer, whereas a Final standard implementation is expected to take an attribute pointer, as an argument to the pthread_create() function. It is apparent from the debugging information he sent me that the PTHREAD_MUTEX_INITIALIZER value is defined. I would caution *against* this definition, unless the threads library has been brought up to full Final Standard functionality. There is some possibility that this was pilot error on the part of the person sending the bug report; however, careful consideration should be made about pthreads functionality before assuming anything here. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 16 14:25:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA18287 for freebsd-current-outgoing; Thu, 16 Jul 1998 14:25:07 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA18281 for ; Thu, 16 Jul 1998 14:25:04 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.8/8.8.7) id HAA17349; Fri, 17 Jul 1998 07:41:21 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199807162141.HAA17349@cimlogic.com.au> Subject: Re: Proposed fix for ___error problem. In-Reply-To: <199807161544.JAA25102@harmony.village.org> from Warner Losh at "Jul 16, 98 09:44:57 am" To: imp@village.org (Warner Losh) Date: Fri, 17 Jul 1998 07:41:20 +1000 (EST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Warner Losh wrote: > > OK. I have found that a -current from approx Oct exhibits this error > when I do a 'make buildworld -m /usr/src/share/mk'. So I got into > digging into this problem and discovered that I can fix it and the > MACHINE_ARCH problem fairly well for legacy systems. I haven't tried putting buildworld before the -m argument, but from what I see in your message, the "-m /usr/src/share/mk" isn't getting the correct includes. No patches are necessary if you use the correct command. The __error problem indicates that /usr/lib is being used instead of /usr/lib/aout because the top level makefile is using an old sys.mk. -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 16 14:27:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA18766 for freebsd-current-outgoing; Thu, 16 Jul 1998 14:27:44 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp02.primenet.com (daemon@smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA18728 for ; Thu, 16 Jul 1998 14:27:35 -0700 (PDT) (envelope-from tlambert@usr07.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id OAA09879; Thu, 16 Jul 1998 14:27:19 -0700 (MST) Received: from usr07.primenet.com(206.165.6.207) via SMTP by smtp02.primenet.com, id smtpd009838; Thu Jul 16 14:27:16 1998 Received: (from tlambert@localhost) by usr07.primenet.com (8.8.5/8.8.5) id OAA03954; Thu, 16 Jul 1998 14:27:08 -0700 (MST) From: Terry Lambert Message-Id: <199807162127.OAA03954@usr07.primenet.com> Subject: Re: Softupdates crash: Got it! To: shimon@simon-shapiro.org Date: Thu, 16 Jul 1998 21:27:08 +0000 (GMT) Cc: cdillon@wolves.k12.mo.us, current@FreeBSD.ORG In-Reply-To: from "Simon Shapiro" at Jul 16, 98 11:18:55 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On a totally different subject; Where did you register your domain name? > > I keep forgetting the name of that non-internic entity. ARIN -- the American Registry for Internet Numbers It's a wholly owned subsidiary of InterNIC, as far as I can tell... Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 16 14:30:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA19664 for freebsd-current-outgoing; Thu, 16 Jul 1998 14:30:36 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp02.primenet.com (daemon@smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA19652 for ; Thu, 16 Jul 1998 14:30:33 -0700 (PDT) (envelope-from tlambert@usr07.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id OAA10920; Thu, 16 Jul 1998 14:30:13 -0700 (MST) Received: from usr07.primenet.com(206.165.6.207) via SMTP by smtp02.primenet.com, id smtpd010887; Thu Jul 16 14:30:09 1998 Received: (from tlambert@localhost) by usr07.primenet.com (8.8.5/8.8.5) id OAA04066; Thu, 16 Jul 1998 14:29:58 -0700 (MST) From: Terry Lambert Message-Id: <199807162129.OAA04066@usr07.primenet.com> Subject: Re: Make release fails because kernel is too large To: ben@rosengart.com Date: Thu, 16 Jul 1998 21:29:57 +0000 (GMT) Cc: hetzels@westbend.net, current@FreeBSD.ORG In-Reply-To: from "Snob Art Genre" at Jul 16, 98 05:05:11 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > What about using 1.68 or 1.72 MB floppies? > > I think that this would drastically reduce the amount of > FreeBSD-friendly hardware out there. You mean "the amount of hardware-friendly FreeBSD"... Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 16 14:33:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA20359 for freebsd-current-outgoing; Thu, 16 Jul 1998 14:33:19 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp01.primenet.com (daemon@smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA20354 for ; Thu, 16 Jul 1998 14:33:16 -0700 (PDT) (envelope-from tlambert@usr07.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id OAA06020; Thu, 16 Jul 1998 14:32:58 -0700 (MST) Received: from usr07.primenet.com(206.165.6.207) via SMTP by smtp01.primenet.com, id smtpd005977; Thu Jul 16 14:32:50 1998 Received: (from tlambert@localhost) by usr07.primenet.com (8.8.5/8.8.5) id OAA04208; Thu, 16 Jul 1998 14:32:46 -0700 (MST) From: Terry Lambert Message-Id: <199807162132.OAA04208@usr07.primenet.com> Subject: Re: Make release fails because kernel is too large To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Thu, 16 Jul 1998 21:32:46 +0000 (GMT) Cc: phk@critter.freebsd.dk, jdp@polstra.com, current@FreeBSD.ORG In-Reply-To: <4192.900619639@time.cdrom.com> from "Jordan K. Hubbard" at Jul 16, 98 01:07:19 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'll look into the kernel and see what can be sed'd out specifically > for the boot floppy. Fortunately, we do this already for an number of > items (like the NFS server code) so it's easy to add new stuff to the > list. I have it on good authority that Mike Smith has an INT 13 VM86 based disk driver working. The answer to your question might be "all hardware specific disk drivers, to be LKM'ed in later to provide support for specific controllers once they have been detected". Mike is *such* a code stud... Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 16 14:40:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA21790 for freebsd-current-outgoing; Thu, 16 Jul 1998 14:40:17 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from artemis.syncom.net (artemis.syncom.net [206.64.31.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA21634; Thu, 16 Jul 1998 14:39:59 -0700 (PDT) (envelope-from cyouse@artemis.syncom.net) Received: from localhost (localhost [[UNIX: localhost]]) by artemis.syncom.net (8.8.8/8.8.8) with SMTP id RAA21838; Thu, 16 Jul 1998 17:47:24 -0400 (EDT) Date: Thu, 16 Jul 1998 17:47:23 -0400 (EDT) From: Charles Youse To: Dag-Erling Coidan Smørgrav cc: Lee Johnston , Brandon Lockhart , David Greenman , Jeremy Domingue , current@FreeBSD.ORG, stable@FreeBSD.ORG, questions@FreeBSD.ORG Subject: Re: Disgruntled Linux User... questions about FreeBSD In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by hub.freebsd.org id OAA21697 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 16 Jul 1998, Dag-Erling Coidan Smørgrav wrote: > > > What are you talking about, I was talking about for a HIGHLY used server, > > > as in, more then cdrom.com, and I was talking about a REAL server, not a > > > PC supped up. I am talking about a rack mount server, a REAL server. > > > Which in case you where out of the loop, most REAL servers use RISC. > > More than ftp.cdrom.com? I thought ftp.cdrom.com was one of the busiest > > if not _THE_ busiest FTP Server on the Internet. What servers are you > > talking about? > > Aw shucks, the guy's just one big fscking troll. Ignore him. I was just about to pull out my PDP-11 and put it up in place of my Dual PII server. The PDP-11 is, of course, rack-mounted, and thus must be a 'REAL' server. Chuck Youse cyouse@syncom.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 16 14:59:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA25192 for freebsd-current-outgoing; Thu, 16 Jul 1998 14:59:36 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from myrddin.demon.co.uk (exim@myrddin.demon.co.uk [158.152.54.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA25178 for ; Thu, 16 Jul 1998 14:59:33 -0700 (PDT) (envelope-from dom@myrddin.demon.co.uk) Received: from dom by myrddin.demon.co.uk with local (Exim 1.92 #1) id 0ywvxg-0000x2-00; Thu, 16 Jul 1998 22:53:12 +0100 To: ben@rosengart.com Cc: "Scot W. Hetzel" , current@FreeBSD.ORG Subject: Re: Make release fails because kernel is too large References: From: Dom Mitchell In-Reply-To: Snob Art Genre's message of "Thu, 16 Jul 1998 17:05:11 -0400 (EDT)" X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald" Date: Thu, 16 Jul 1998 22:53:11 +0100 Message-Id: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Snob Art Genre writes: > On Thu, 16 Jul 1998, Scot W. Hetzel wrote: > > > What about using 1.68 or 1.72 MB floppies? > > I think that this would drastically reduce the amount of > FreeBSD-friendly hardware out there. Yes, but don't Microsoft do similiar sorts of things with the Win95 boot floppies? I know that doesn't grant a right to do so by God, but it's a fairly clear idea of how much hardware *does* support it. -- ``If make doesn't do what you expect it to, it's a good chance the makefile is wrong.'' -- Adam de Boor To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 16 15:12:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA29307 for freebsd-current-outgoing; Thu, 16 Jul 1998 15:12:33 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA29299 for ; Thu, 16 Jul 1998 15:12:31 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id PAA04626; Thu, 16 Jul 1998 15:11:12 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: "Scot W. Hetzel" cc: current@FreeBSD.ORG Subject: Re: Make release fails because kernel is too large In-reply-to: Your message of "Thu, 16 Jul 1998 15:24:22 CDT." <00df01bdb0f7$b88cfc60$c3e0d9cf@westbend.net> Date: Thu, 16 Jul 1998 15:11:12 -0700 Message-ID: <4623.900627072@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > What about using 1.68 or 1.72 MB floppies? No. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 16 15:21:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA01665 for freebsd-current-outgoing; Thu, 16 Jul 1998 15:21:23 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from forbidden-donut.anet-stl.com (vmailer@forbidden-donut.anet-stl.com [209.83.128.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA01598 for ; Thu, 16 Jul 1998 15:21:11 -0700 (PDT) (envelope-from doogie@forbidden-donut.anet-stl.com) Received: from localhost (localhost.anet-stl.com 127.0.0.1) by forbidden-donut.anet-stl.com (VMailer) via SMTP id 3C44AEB1E; Thu, 16 Jul 1998 17:20:52 -0500 (CDT) Date: Thu, 16 Jul 1998 17:20:52 -0500 (CDT) From: Jason Young To: "Jordan K. Hubbard" Cc: Poul-Henning Kamp , John Polstra , current@FreeBSD.ORG Subject: Re: Make release fails because kernel is too large In-Reply-To: <4192.900619639@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Would it be possible to split sysinstall into: A bootstrap program that knows how to locate and mount media or establish network connections and pull into MFS and: The rest of sysinstall: newfs, partition, distributions, packages, final machine configuration, etc. If you split the two portions up, the first boot floppy could bootstrap the main sysinstall off the installation media (cdrom, ftp, whatever). This would allow you to grow sysinstall as big as you want and free up room for a larger kernel with more base hardware support. Jason Young ANET Chief Network Engineer On Thu, 16 Jul 1998, Jordan K. Hubbard wrote: > I'll look into the kernel and see what can be sed'd out specifically > for the boot floppy. Fortunately, we do this already for an number of > items (like the NFS server code) so it's easy to add new stuff to the > list. > > - Jordan > > > In message <199807161646.JAA26999@austin.polstra.com>, John Polstra writes: > > >Make release of -current is failing, because the install kernel is > > >too large to fit into the filesystem on the boot floppy: > > > > Hmm, what was it Jordan said to me that made me agree to kill the 1200K > > boot floppy, "and with 1.44 we have plenty of space for a couple of years > > at least, well, maybe not that long time but you get the idea..." > > > > You were right. What's next Jordan ? > > > > -- > > Poul-Henning Kamp FreeBSD coreteam member > > phk@FreeBSD.ORG "Real hackers run -current on their laptop." > > "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 16 15:25:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA03176 for freebsd-current-outgoing; Thu, 16 Jul 1998 15:25:37 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from echonyc.com (echonyc.com [198.67.15.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA03140 for ; Thu, 16 Jul 1998 15:25:31 -0700 (PDT) (envelope-from benedict@echonyc.com) Received: from localhost (benedict@localhost) by echonyc.com (8.8.7/8.8.7) with SMTP id SAA15158 for ; Thu, 16 Jul 1998 18:25:20 -0400 (EDT) Date: Thu, 16 Jul 1998 18:25:20 -0400 (EDT) From: Snob Art Genre Reply-To: ben@rosengart.com To: current@FreeBSD.ORG Subject: ppp problems Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm having intermittent userland PPP problems with bleeding-edge current. I've seen this before, but it just happened twice in ten minutes, which is unusual. The symptom is that traffic across the PPP link stops cold, even though the routing tables are correct and the PPP program still seems to think the link is up (i.e. the prompt says "PPP", not "ppp"). I "down" the link and then type "dial", but nothing happens. If I quit PPP and restart it, everything works fine, at least until the problem recurs. Ben "You have your mind on computers, it seems." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 16 15:45:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA08610 for freebsd-current-outgoing; Thu, 16 Jul 1998 15:45:42 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA08603 for ; Thu, 16 Jul 1998 15:45:39 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id PAA04712; Thu, 16 Jul 1998 15:38:36 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: Jason Young cc: Poul-Henning Kamp , John Polstra , current@FreeBSD.ORG Subject: Re: Make release fails because kernel is too large In-reply-to: Your message of "Thu, 16 Jul 1998 17:20:52 CDT." Date: Thu, 16 Jul 1998 15:38:36 -0700 Message-ID: <4708.900628716@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It would be possible, yes. Who wants to do the work? :-) - Jordan P.S. Don't look at me - I've already paid my dues with that evil program. :) > > Would it be possible to split sysinstall into: > > A bootstrap program that knows how to locate and mount media or establish > network connections and pull into MFS > > and: > > The rest of sysinstall: newfs, partition, distributions, packages, final > machine configuration, etc. > > If you split the two portions up, the first boot floppy could bootstrap > the main sysinstall off the installation media (cdrom, ftp, whatever). > This would allow you to grow sysinstall as big as you want and free up > room for a larger kernel with more base hardware support. > > Jason Young > ANET Chief Network Engineer > > On Thu, 16 Jul 1998, Jordan K. Hubbard wrote: > > > I'll look into the kernel and see what can be sed'd out specifically > > for the boot floppy. Fortunately, we do this already for an number of > > items (like the NFS server code) so it's easy to add new stuff to the > > list. > > > > - Jordan > > > > > In message <199807161646.JAA26999@austin.polstra.com>, John Polstra write s: > > > >Make release of -current is failing, because the install kernel is > > > >too large to fit into the filesystem on the boot floppy: > > > > > > Hmm, what was it Jordan said to me that made me agree to kill the 1200K > > > boot floppy, "and with 1.44 we have plenty of space for a couple of years > > > at least, well, maybe not that long time but you get the idea..." > > > > > > You were right. What's next Jordan ? > > > > > > -- > > > Poul-Henning Kamp FreeBSD coreteam member > > > phk@FreeBSD.ORG "Real hackers run -current on their laptop. " > > > "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color term inal > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > with "unsubscribe freebsd-current" in the body of the message > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 16 15:53:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA09942 for freebsd-current-outgoing; Thu, 16 Jul 1998 15:53:04 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id PAA09934 for ; Thu, 16 Jul 1998 15:53:02 -0700 (PDT) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0ywwtP-0001Tf-00; Thu, 16 Jul 1998 16:52:51 -0600 Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.8.8/8.8.3) with ESMTP id QAA14657; Thu, 16 Jul 1998 16:54:16 -0600 (MDT) Message-Id: <199807162254.QAA14657@harmony.village.org> To: John Birrell Subject: Re: Proposed fix for ___error problem. Cc: current@FreeBSD.ORG In-reply-to: Your message of "Fri, 17 Jul 1998 07:41:20 +1000." <199807162141.HAA17349@cimlogic.com.au> References: <199807162141.HAA17349@cimlogic.com.au> Date: Thu, 16 Jul 1998 16:54:16 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199807162141.HAA17349@cimlogic.com.au> John Birrell writes: : I haven't tried putting buildworld before the -m argument, but from what : I see in your message, the "-m /usr/src/share/mk" isn't getting the correct : includes. No patches are necessary if you use the correct command. : The __error problem indicates that /usr/lib is being used instead of : /usr/lib/aout because the top level makefile is using an old sys.mk. What failed was "sudo make -m share/mk buildworld MACHINE_ARCH=i386". The -m didn't work for anything except the top level makefile, which is what lead me to believe there were problems. When I did make -m share/mk MACHINE_ARCH=i386 -V LIBDIR, it printed the wrong thing. Just now I did make -m /where/I/have/the/sources/share/mk -V LIBDIR it printed the right thing. The tree builds the same with the absolute path w/ or w/o my patches. This leads me to believe that the -m share/mk (the relative path) is what caused the problems :-(. Maybe we should check for that somehow since it is so easy to stubmle over. Or, as Mrs Yetti Goosecreature used to say "Oh, that's different. Never mind." Warner P.S. The following would have kept me from making this mistake. It is the check I mentioned above. Index: Makefile =================================================================== RCS file: /home/imp/FreeBSD/CVS/src/Makefile,v retrieving revision 1.205 diff -u -r1.205 Makefile --- Makefile 1998/07/07 09:59:48 1.205 +++ Makefile 1998/07/16 22:52:34 @@ -233,6 +233,10 @@ # success, regardless of how old your existing system is. # buildworld: + @(if (echo ${MAKEFLAGS} | egrep -- '-m [^/]' > /dev/null); then \ + echo "make -m can't have a relative path for world targets" ;\ + exit 1;\ + fi) .if !defined(NOCLEAN) @echo @echo "--------------------------------------------------------------" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 16 16:03:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA12055 for freebsd-current-outgoing; Thu, 16 Jul 1998 16:03:33 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freefall.pipeline.ch (freefall.pipeline.ch [195.134.128.40]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA12042 for ; Thu, 16 Jul 1998 16:03:24 -0700 (PDT) (envelope-from andre@pipeline.ch) Received: from pipeline.ch ([195.134.128.41]) by freefall.pipeline.ch (Netscape Mail Server v2.02) with ESMTP id AAA317; Fri, 17 Jul 1998 01:01:16 +0200 Message-ID: <35AE866F.B9D340CC@pipeline.ch> Date: Fri, 17 Jul 1998 01:02:07 +0200 From: "IBS / Andre Oppermann" Organization: Internet Business Solutions Ltd. (AG) X-Mailer: Mozilla 4.03 [en] (WinNT; U) MIME-Version: 1.0 To: Terry Lambert CC: cdillon@wolves.k12.mo.us, current@FreeBSD.ORG Subject: Re: .US domains (was: Softupdates crash: Got it!) References: <199807162127.OAA03954@usr07.primenet.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Terry Lambert wrote: > > > On a totally different subject; Where did you register your domain name? > > > > I keep forgetting the name of that non-internic entity. > > ARIN -- the American Registry for Internet Numbers > > It's a wholly owned subsidiary of InterNIC, as far as I can tell... Nope, ARIN states on it's second page: ARIN is a non-profit organization established for the purpose of administration and registration of Internet Protocol (IP) numbers to the geographical areas previously managed by Network Solutions, Inc. (InterNIC). ^^^^^^^^^^ You can apply for domain names under the .US TLD here: http://www.isi.edu/in-notes/usdnr/ -- Andre Oppermann CEO / Geschaeftsfuehrer Internet Business Solutions Ltd. (AG) Hardstrasse 235, 8005 Zurich, Switzerland Fon +41 1 277 75 75 / Fax +41 1 277 75 77 http://www.pipeline.ch ibs@pipeline.ch To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 16 18:37:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA02394 for freebsd-current-outgoing; Thu, 16 Jul 1998 18:37:17 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from thing.dyn.ml.org (dyn-max10-165.chicago.il.ameritech.net [206.141.212.165] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA02387 for ; Thu, 16 Jul 1998 18:37:14 -0700 (PDT) (envelope-from mcdougall@ameritech.net) Received: from ameritech.net (bsdx [192.168.1.2]) by thing.dyn.ml.org (8.8.8/8.8.7) with ESMTP id VAA27068 for ; Thu, 16 Jul 1998 21:36:41 -0400 (EDT) (envelope-from mcdougall@ameritech.net) Message-ID: <35AEAAA5.FFD655EF@ameritech.net> Date: Thu, 16 Jul 1998 21:36:37 -0400 From: Adam McDougall Reply-To: mcdougall@ameritech.net X-Mailer: Mozilla 4.05 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: Re: ppp problems References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Snob Art Genre wrote: > I'm having intermittent userland PPP problems with bleeding-edge > current. I've seen this before, but it just happened twice in ten > minutes, which is unusual. > > The symptom is that traffic across the PPP link stops cold, even though > the routing tables are correct and the PPP program still seems to think > the link is up (i.e. the prompt says "PPP", not "ppp"). I "down" the > link and then type "dial", but nothing happens. If I quit PPP and > restart it, everything works fine, at least until the problem recurs. > > Ben > > "You have your mind on computers, it seems." > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message Hmm, this morning I woke up to a dead link, from my mrtg graphs apparently it had been dead several hours, I just told it to close and -ddial took care of reconnecting. So I might be seeing the same thing as you. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 16 19:23:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA06891 for freebsd-current-outgoing; Thu, 16 Jul 1998 19:23:09 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA06884 for ; Thu, 16 Jul 1998 19:23:07 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id MAA28858; Fri, 17 Jul 1998 12:22:40 +1000 Date: Fri, 17 Jul 1998 12:22:40 +1000 From: Bruce Evans Message-Id: <199807170222.MAA28858@godzilla.zeta.org.au> To: abial@nask.pl, jdp@polstra.com Subject: Re: Make release fails because kernel is too large Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> Does anybody have an idea of what we can take out? It seems likely >> that when CAM comes in, it will further expand the kernel. And CAM >> definitely needs to come in. > >Perhaps with the advent of CAM boot floppies we should also use DEVFS, >which would allow for saving ca. 50kB on inodes' space. More like -15K (e.g., +5K savings for compressed inodes' space -10K for compressed code to register devfs names, and -10K for compressed code for devfs itself). The 2.2 boot floppy has 45K for metadata in the uncompressed (boot) file system. Of this, 12K is very easy to save using `newfs -i large' to reduce the inodes' space from 16K to 4K. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 16 20:20:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA11656 for freebsd-current-outgoing; Thu, 16 Jul 1998 20:20:24 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA11649 for ; Thu, 16 Jul 1998 20:20:21 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id NAA00328; Fri, 17 Jul 1998 13:19:59 +1000 Date: Fri, 17 Jul 1998 13:19:59 +1000 From: Bruce Evans Message-Id: <199807170319.NAA00328@godzilla.zeta.org.au> To: current@FreeBSD.ORG, dag-erli@ifi.uio.no Subject: Re: make installworld -j8 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >make can't execute /bin/sh to install the sh(1) man pages because >/bin/sh is in the process of being clobbered by a sibling make >process. Shouldn't make installworld use the freshly compiled sh from >/usr/obj rather than /bin/sh? You mean `make -jN installworld'. `make installworld' doesn't have this problem, since it doesn't install things concurrently. `make -jN world' doesn't have this problem, since it uses `${MAKE} -B installworld' internally. All the world-related targets attempt to use ${WORLDTMP}/bin/sh after it is created, but many programs have /bin/sh hard-coded. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 16 21:44:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA17915 for freebsd-current-outgoing; Thu, 16 Jul 1998 21:44:58 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp02.primenet.com (daemon@smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA17910 for ; Thu, 16 Jul 1998 21:44:52 -0700 (PDT) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id VAA01760; Thu, 16 Jul 1998 21:44:42 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp02.primenet.com, id smtpd001735; Thu Jul 16 21:44:37 1998 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id VAA18397; Thu, 16 Jul 1998 21:44:34 -0700 (MST) From: Terry Lambert Message-Id: <199807170444.VAA18397@usr02.primenet.com> Subject: Re: .US domains (was: Softupdates crash: Got it!) To: andre@pipeline.ch (IBS / Andre Oppermann) Date: Fri, 17 Jul 1998 04:44:33 +0000 (GMT) Cc: tlambert@primenet.com, cdillon@wolves.k12.mo.us, current@FreeBSD.ORG In-Reply-To: <35AE866F.B9D340CC@pipeline.ch> from "IBS / Andre Oppermann" at Jul 17, 98 01:02:07 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > On a totally different subject; Where did you register your domain name? > > > > > > I keep forgetting the name of that non-internic entity. > > > > ARIN -- the American Registry for Internet Numbers > > > > It's a wholly owned subsidiary of InterNIC, as far as I can tell... > > Nope, ARIN states on it's second page: > > ARIN is a non-profit organization established for the purpose of > administration and registration of Internet Protocol (IP) numbers > to the geographical areas previously managed by Network Solutions, > Inc. (InterNIC). ^^^^^^^^^^ I'm pretty sure the same people own both places, and it's just a dodge to keep control of the registry. If you track back the registered names to their origins, you will see that they are withing 20 miles of each other in Virgina, and the same people are involved (admittely, you'll have to go "off the net" (God forbid!) for that information... Not that I'm complaining: $35 is less than $50; but maybe I've been "bought off" for a $15 differential for what I really think should be free. On the other hand, disincenting people like Dupont from domaining all its registered trademarks has a bit to be said for it... not the least of which is that it's tacit admission that the trademark namespace and the DNS namespace are not equal... Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 16 23:01:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA22509 for freebsd-current-outgoing; Thu, 16 Jul 1998 23:01:42 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from compound.east.sun.com (port44.prairietech.net [208.141.230.121]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA22503 for ; Thu, 16 Jul 1998 23:01:38 -0700 (PDT) (envelope-from alk@compound.east.sun.com) Received: (from alk@localhost) by compound.east.sun.com (8.8.8/8.7.3) id BAA00320; Fri, 17 Jul 1998 01:01:49 -0500 (CDT) From: Tony Kimball MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Fri, 17 Jul 1998 01:01:45 -0500 (CDT) X-Face: O9M"E%K;(f-Go/XDxL+pCxI5*gr[=FN@Y`cl1.Tn Reply-To: alk@pobox.com To: current@FreeBSD.ORG Subject: State of current... X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <13742.59308.502069.876495@compound.east> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG FYI: After good function and stability at the beginning of the month, it's starting to look pretty sad... rcmds to foreign platforms are not working (again--resurrecting an *old* bug), X applications are failing (in particular: netscape: X Error of failed request: BadPixmap (invalid Pixmap parameter) Major opcode of failed request: 56 (X_ChangeGC) Resource id in failed request: 0x50038 Serial number of failed request: 117146 Current serial number in output stream: 117380 netscape: X Error of failed request: BadLength (poly request too large or internal Xlib length error) Major opcode of failed request: 22 (X_SetSelectionOwner) Serial number of failed request: 117147 Current serial number in output stream: 117380 etc.) And yesterday xemacs wrote a bunch of nulls instead of the proper end of the source file I was editing (realloc failing to copy perhaps?). In all, pretty shaky. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 17 01:07:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA03099 for freebsd-current-outgoing; Fri, 17 Jul 1998 01:07:43 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freebie.lemis.com (freebie.lemis.com [139.130.136.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA03093 for ; Fri, 17 Jul 1998 01:07:39 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id RAA00713; Fri, 17 Jul 1998 17:37:15 +0930 (CST) Message-ID: <19980717173714.Q566@freebie.lemis.com> Date: Fri, 17 Jul 1998 17:37:14 +0930 From: Greg Lehey To: alk@pobox.com, current@FreeBSD.ORG Subject: Re: State of current... References: <13742.59308.502069.876495@compound.east> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <13742.59308.502069.876495@compound.east>; from Tony Kimball on Fri, Jul 17, 1998 at 01:01:45AM -0500 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Friday, 17 July 1998 at 1:01:45 -0500, Tony Kimball wrote: > FYI: After good function and stability at the beginning of the month, > it's starting to look pretty sad... rcmds to foreign platforms are > not working (again--resurrecting an *old* bug), X applications are > failing (in particular: > netscape: X Error of failed request: BadPixmap (invalid Pixmap parameter) > Major opcode of failed request: 56 (X_ChangeGC) > Resource id in failed request: 0x50038 > Serial number of failed request: 117146 > Current serial number in output stream: 117380 > > netscape: X Error of failed request: BadLength (poly request too large or internal Xlib length error) > Major opcode of failed request: 22 (X_SetSelectionOwner) > Serial number of failed request: 117147 > Current serial number in output stream: 117380 > etc.) And yesterday xemacs wrote a bunch of nulls instead of the > proper end of the source file I was editing (realloc failing to copy perhaps?). > In all, pretty shaky. I was wondering if something was wrong, too. I haven't had this particular problem, but I've had a number of processes, including Emacs, hang in select after VisibilityNotify events, unable to update their displays. It's nothing enough to be sure that anything's wrong, but enough to be noticable. I'm rebuilding with the latest -current (as of about 2 hours ago), and will try again. Greg -- See complete headers for address and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 17 01:59:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA08581 for freebsd-current-outgoing; Fri, 17 Jul 1998 01:59:48 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.133.1] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA08566 for ; Fri, 17 Jul 1998 01:59:25 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.5) with ESMTP id KAA06603; Fri, 17 Jul 1998 10:56:03 +0200 (CEST) To: Greg Lehey cc: alk@pobox.com, current@FreeBSD.ORG Subject: Re: State of current... In-reply-to: Your message of "Fri, 17 Jul 1998 17:37:14 +0930." <19980717173714.Q566@freebie.lemis.com> Date: Fri, 17 Jul 1998 10:56:03 +0200 Message-ID: <6601.900665763@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've seen this problem too. In message <19980717173714.Q566@freebie.lemis.com>, Greg Lehey writes: >On Friday, 17 July 1998 at 1:01:45 -0500, Tony Kimball wrote: >> FYI: After good function and stability at the beginning of the month, >> it's starting to look pretty sad... rcmds to foreign platforms are >> not working (again--resurrecting an *old* bug), X applications are >> failing (in particular: >> netscape: X Error of failed request: BadPixmap (invalid Pixmap parameter) >> Major opcode of failed request: 56 (X_ChangeGC) >> Resource id in failed request: 0x50038 >> Serial number of failed request: 117146 >> Current serial number in output stream: 117380 >> >> netscape: X Error of failed request: BadLength (poly request too large or internal Xlib length error) >> Major opcode of failed request: 22 (X_SetSelectionOwner) >> Serial number of failed request: 117147 >> Current serial number in output stream: 117380 >> etc.) And yesterday xemacs wrote a bunch of nulls instead of the >> proper end of the source file I was editing (realloc failing to copy perhaps?). >> In all, pretty shaky. > >I was wondering if something was wrong, too. I haven't had this >particular problem, but I've had a number of processes, including >Emacs, hang in select after VisibilityNotify events, unable to update >their displays. It's nothing enough to be sure that anything's wrong, >but enough to be noticable. I'm rebuilding with the latest -current >(as of about 2 hours ago), and will try again. > >Greg >-- >See complete headers for address and phone numbers >finger grog@lemis.com for PGP public key > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message > -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 17 02:57:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA11869 for freebsd-current-outgoing; Fri, 17 Jul 1998 02:57:19 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freebie.lemis.com (freebie.lemis.com [139.130.136.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA11864 for ; Fri, 17 Jul 1998 02:57:14 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id TAA00497; Fri, 17 Jul 1998 19:25:34 +0930 (CST) Message-ID: <19980717192534.B342@freebie.lemis.com> Date: Fri, 17 Jul 1998 19:25:34 +0930 From: Greg Lehey To: Poul-Henning Kamp Cc: alk@pobox.com, current@FreeBSD.ORG Subject: Re: State of current... References: <19980717173714.Q566@freebie.lemis.com> <6601.900665763@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <6601.900665763@critter.freebsd.dk>; from Poul-Henning Kamp on Fri, Jul 17, 1998 at 10:56:03AM +0200 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Friday, 17 July 1998 at 10:56:03 +0200, Poul-Henning Kamp wrote: >> On Friday, 17 July 1998 at 1:01:45 -0500, Tony Kimball wrote: >>> FYI: After good function and stability at the beginning of the month, >>> it's starting to look pretty sad... rcmds to foreign platforms are >>> not working (again--resurrecting an *old* bug), X applications are >>> failing (in particular: >>> netscape: X Error of failed request: BadPixmap (invalid Pixmap parameter) >>> Major opcode of failed request: 56 (X_ChangeGC) >>> Resource id in failed request: 0x50038 >>> Serial number of failed request: 117146 >>> Current serial number in output stream: 117380 >>> >>> netscape: X Error of failed request: BadLength (poly request too large or internal Xlib length error) >>> Major opcode of failed request: 22 (X_SetSelectionOwner) >>> Serial number of failed request: 117147 >>> Current serial number in output stream: 117380 >>> etc.) And yesterday xemacs wrote a bunch of nulls instead of the >>> proper end of the source file I was editing (realloc failing to copy perhaps?). >>> In all, pretty shaky. >> >> I was wondering if something was wrong, too. I haven't had this >> particular problem, but I've had a number of processes, including >> Emacs, hang in select after VisibilityNotify events, unable to update >> their displays. It's nothing enough to be sure that anything's wrong, >> but enough to be noticable. I'm rebuilding with the latest -current >> (as of about 2 hours ago), and will try again. > > I've seen this problem too. It still seems to be there with the latest -current. Greg -- See complete headers for address and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 17 03:15:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA13113 for freebsd-current-outgoing; Fri, 17 Jul 1998 03:15:34 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from oslo.geco-prakla.slb.com (geos01.oslo.geco-prakla.slb.com [134.32.44.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA13107 for ; Fri, 17 Jul 1998 03:15:31 -0700 (PDT) (envelope-from smoergrd@oslo.sl.slb.com) Received: from sunw110.oslo.Geco-Prakla.slb.com (sunw110 [192.23.231.54]) by oslo.geco-prakla.slb.com (8.8.8/8.6.9) with SMTP id MAA10031 ; Fri, 17 Jul 1998 12:13:32 +0200 (MET DST) Received: by sunw110.oslo.Geco-Prakla.slb.com (SMI-8.6/SMI-SVR4) id MAA19827; Fri, 17 Jul 1998 12:13:31 +0200 To: Dom Mitchell Cc: ben@rosengart.com, "Scot W. Hetzel" , current@FreeBSD.ORG Subject: Re: Make release fails because kernel is too large References: Organization: Schlumberger Geco-Prakla X-Disclaimer: I speak only for myself. From: smoergrd@oslo.geco-prakla.slb.com (Dag-Erling Coidan Smørgrav) Date: 17 Jul 1998 12:13:30 +0200 In-Reply-To: Dom Mitchell's message of Thu, 16 Jul 1998 22:53:11 +0100 Message-ID: Lines: 15 X-Mailer: Gnus v5.3/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dom Mitchell writes: > Snob Art Genre writes: > > On Thu, 16 Jul 1998, Scot W. Hetzel wrote: > > > What about using 1.68 or 1.72 MB floppies? > > I think that this would drastically reduce the amount of > > FreeBSD-friendly hardware out there. > Yes, but don't Microsoft do similiar sorts of things with the Win95 > boot floppies? I know that doesn't grant a right to do so by God, but > it's a fairly clear idea of how much hardware *does* support it. I suggest we revise Goodwin's Law to cover Microsoft and Bill Gates. DES -- Dag-Erling Smørgrav - smoergrd@oslo.geco-prakla.slb.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 17 03:19:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA13621 for freebsd-current-outgoing; Fri, 17 Jul 1998 03:19:02 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from oslo.geco-prakla.slb.com (geos01.oslo.geco-prakla.slb.com [134.32.44.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA13613 for ; Fri, 17 Jul 1998 03:18:58 -0700 (PDT) (envelope-from smoergrd@oslo.sl.slb.com) Received: from sunw110.oslo.Geco-Prakla.slb.com (sunw110 [192.23.231.54]) by oslo.geco-prakla.slb.com (8.8.8/8.6.9) with SMTP id MAA09911 ; Fri, 17 Jul 1998 12:10:09 +0200 (MET DST) Received: by sunw110.oslo.Geco-Prakla.slb.com (SMI-8.6/SMI-SVR4) id MAA19821; Fri, 17 Jul 1998 12:10:08 +0200 To: "Jordan K. Hubbard" Cc: Jason Young , Poul-Henning Kamp , John Polstra , current@FreeBSD.ORG Subject: Re: Make release fails because kernel is too large References: <4708.900628716@time.cdrom.com> Organization: Schlumberger Geco-Prakla X-Disclaimer: I speak only for myself. From: smoergrd@oslo.geco-prakla.slb.com (Dag-Erling Coidan Smørgrav) Date: 17 Jul 1998 12:10:07 +0200 In-Reply-To: "Jordan K. Hubbard"'s message of Thu, 16 Jul 1998 15:38:36 -0700 Message-ID: Lines: 10 X-Mailer: Gnus v5.3/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jordan K. Hubbard" writes: > It would be possible, yes. Who wants to do the work? :-) Isn't sysinstall scheduled for a rewrite anyway? ISTR volunteering a while back. Don't expect it to be finished in time for 2.2.7, though... DES -- Dag-Erling Smørgrav - smoergrd@oslo.geco-prakla.slb.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 17 03:37:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA15197 for freebsd-current-outgoing; Fri, 17 Jul 1998 03:37:53 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA15191 for ; Fri, 17 Jul 1998 03:37:50 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id DAA15168; Fri, 17 Jul 1998 03:31:10 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: smoergrd@oslo.geco-prakla.slb.com (Dag-Erling Coidan Sm rgrav) cc: Jason Young , Poul-Henning Kamp , John Polstra , current@FreeBSD.ORG Subject: Re: Make release fails because kernel is too large In-reply-to: Your message of "17 Jul 1998 12:10:07 +0200." Date: Fri, 17 Jul 1998 03:31:09 -0700 Message-ID: <15164.900671469@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Isn't sysinstall scheduled for a rewrite anyway? ISTR volunteering a > while back. Don't expect it to be finished in time for 2.2.7, > though... "Scheduled" is such a relative term when it comes to the practical realities of the situation. :-) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 17 06:18:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA00262 for freebsd-current-outgoing; Fri, 17 Jul 1998 06:18:10 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA00256 for ; Fri, 17 Jul 1998 06:18:09 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.8.8/8.8.8) id JAA10283; Fri, 17 Jul 1998 09:17:12 -0400 (EDT) (envelope-from wollman) Date: Fri, 17 Jul 1998 09:17:12 -0400 (EDT) From: Garrett Wollman Message-Id: <199807171317.JAA10283@khavrinen.lcs.mit.edu> To: Greg Lehey Cc: alk@pobox.com, current@FreeBSD.ORG Subject: Re: State of current... In-Reply-To: <19980717173714.Q566@freebie.lemis.com> References: <13742.59308.502069.876495@compound.east> <19980717173714.Q566@freebie.lemis.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > I was wondering if something was wrong, too. I haven't had this > particular problem, but I've had a number of processes, including > Emacs, hang in select after VisibilityNotify events, unable to update > their displays. Try backing out rev. 1.41 of kern/uipc_socket.c. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 17 07:21:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA28706 for freebsd-current-outgoing; Fri, 17 Jul 1998 07:21:38 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from terminator.informatik.ba-stuttgart.de (terminator.informatik.ba-stuttgart.de [141.31.111.23]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA28643 for ; Fri, 17 Jul 1998 07:21:20 -0700 (PDT) (envelope-from henry@MX.BA-Stuttgart.De) Received: from marylin.goethestr12-net.marbach-neckar (marylin.informatik.ba-stuttgart.de [141.31.112.1]) by terminator.informatik.ba-stuttgart.de (8.8.8/8.8.8) with ESMTP id QAA03607; Fri, 17 Jul 1998 16:13:09 +0200 (CEST) (envelope-from henry@MX.BA-Stuttgart.De) Received: (from henry@localhost) by marylin.goethestr12-net.marbach-neckar (8.8.8/8.8.8) id QAA02990; Fri, 17 Jul 1998 16:13:50 +0200 (CEST) (envelope-from henry) From: Henry Vogt Message-Id: <199807171413.QAA02990@marylin.goethestr12-net.marbach-neckar> Subject: Re: State of current... In-Reply-To: <19980717192534.B342@freebie.lemis.com> from Greg Lehey at "Jul 17, 98 07:25:34 pm" To: grog@lemis.com (Greg Lehey) Date: Fri, 17 Jul 1998 16:13:50 +0200 (CEST) Cc: phk@critter.freebsd.dk, alk@pobox.com, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31H (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Friday, 17 July 1998 at 10:56:03 +0200, Poul-Henning Kamp wrote: > >> On Friday, 17 July 1998 at 1:01:45 -0500, Tony Kimball wrote: > >>> FYI: After good function and stability at the beginning of the month, > >>> it's starting to look pretty sad... rcmds to foreign platforms are > >>> not working (again--resurrecting an *old* bug), X applications are > >>> failing (in particular: > >>> netscape: X Error of failed request: BadPixmap (invalid Pixmap parameter) > >>> Major opcode of failed request: 56 (X_ChangeGC) > >>> Resource id in failed request: 0x50038 > >>> Serial number of failed request: 117146 > >>> Current serial number in output stream: 117380 > >>> > >>> netscape: X Error of failed request: BadLength (poly request too large or internal Xlib length error) > >>> Major opcode of failed request: 22 (X_SetSelectionOwner) > >>> Serial number of failed request: 117147 > >>> Current serial number in output stream: 117380 > >>> etc.) And yesterday xemacs wrote a bunch of nulls instead of the > >>> proper end of the source file I was editing (realloc failing to copy perhaps?). > >>> In all, pretty shaky. > >> > >> I was wondering if something was wrong, too. I haven't had this > >> particular problem, but I've had a number of processes, including > >> Emacs, hang in select after VisibilityNotify events, unable to update > >> their displays. It's nothing enough to be sure that anything's wrong, > >> but enough to be noticable. I'm rebuilding with the latest -current > >> (as of about 2 hours ago), and will try again. > > > > I've seen this problem too. > > It still seems to be there with the latest -current. > > Greg > -- Yes, i'm running SMP 3.0-Current here and there are at least two more essential programs (xdvi and gv) with this very problems.. Someone on the list mentioned a few days ago using DISPLAY=localhost:0.0, instead simply :0.0, seems to help and indeed, xdvi and gv are working again here. So this appears to me like a new introduced bug in the shared memory handling? (Or am I wrong that the difference between :0.0 and :0.0 is the way IPC between X-Server and -Client ist handled ?) Has something substantially been changed there, about 2 weeks ago ? Henry -- // // Do you suffer from long term memory loss ? I don't remember:-( // // Henry Vogt (henry@BA-Stuttgart.De) // Goethestr. 12, 71672 Marbach (Neckar), Tel. 07144/841653 // To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 17 08:56:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA28468 for freebsd-current-outgoing; Fri, 17 Jul 1998 08:56:19 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com (rah.star-gate.com [209.133.7.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA28364 for ; Fri, 17 Jul 1998 08:56:13 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id IAA02118; Fri, 17 Jul 1998 08:55:01 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199807171555.IAA02118@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Henry Vogt cc: grog@lemis.com (Greg Lehey), alk@pobox.com, current@FreeBSD.ORG Subject: Re: State of current... In-reply-to: Your message of "Fri, 17 Jul 1998 16:13:50 +0200." <199807171413.QAA02990@marylin.goethestr12-net.marbach-neckar> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 17 Jul 1998 08:55:01 -0700 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG My guess is that the problems are due to the recent network patches. Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 17 09:05:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA02747 for freebsd-current-outgoing; Fri, 17 Jul 1998 09:05:21 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from helmholtz.salk.edu (helmholtz.salk.edu [198.202.70.34]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA02710 for ; Fri, 17 Jul 1998 09:05:11 -0700 (PDT) (envelope-from bartol@salk.edu) Received: from cole.salk.edu (cole [198.202.70.113]) by helmholtz.salk.edu (8.7.5/8.7.3) with SMTP id JAA07291 for ; Fri, 17 Jul 1998 09:04:58 -0700 (PDT) Date: Fri, 17 Jul 1998 09:04:57 -0700 (PDT) From: Tom Bartol To: current@FreeBSD.ORG Subject: X gets left out of install of 3.0-19980711-SNAP Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, I just burned a bootable CD of 3.0-19980711-SNAP and did a clean install from scratch off the CD. The installation was smooth and nearly flawless -- the sole exception being that XFree86 was overlooked by the install process even thought I selected it. Puzzled, I rebooted into my newly installed system and ran /stand/sysinstall and reselected the XFree86 distribution for installation but it was still ignored. I verified that I was selecting distributions correctly by reselecting and reinstalling the src distribution without a problem. So, has anyone else experienced this, have I found a real problem here, or is my CD somehow corrupted? Thanks, Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 17 09:31:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA08896 for freebsd-current-outgoing; Fri, 17 Jul 1998 09:31:49 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pluto.plutotech.com (mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA08867; Fri, 17 Jul 1998 09:31:46 -0700 (PDT) (envelope-from gibbs@plutotech.com) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.8.7/8.8.5) with ESMTP id KAA07649; Fri, 17 Jul 1998 10:31:33 -0600 (MDT) Message-Id: <199807171631.KAA07649@pluto.plutotech.com> Date: Fri, 17 Jul 1998 10:26:19 -0600 From: "Justin T. Gibbs" Subject: 19980716 CAM Snapshot now available. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG To: undisclosed-recipients:; ------- Blind-Carbon-Copy X-Mailer: exmh version 2.0.2 2/24/98 To: scsi@FreeBSD.org Subject: 19980716 CAM Snapshot now available. Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 17 Jul 1998 10:26:19 -0600 From: "Justin T. Gibbs" This snapshot is available in full release format for 2.2-stable as well as diffs for both 2.2-stable and 3.0-current. Complete information about CAM can be found at: ftp://ftp.FreeBSD.org/pub/FreeBSD/cam/README or ftp://ftp.kdm.org/pub/FreeBSD/cam/README Full CAM releases are available at: ftp://ftp.FreeBSD.org/pub/FreeBSD/cam Changes for the 19980716 Snapshot: - Corrected chioctl definition in the SCSI Changer driver for -stable. - Corrected support for using "left over BIOS settings" for aic7890 chips embedded on motherboards. This should allow these systems to operate at full LVD Ultra2 speeds. - Fixed a few more bugs in the AdvanSys driver's error recovery code. - Quieted error messages from devices that return INVALID REQUEST for inquiry commands to luns above zero. - -- Justin T. Gibbs Kenneth D. Merry ------- End of Blind-Carbon-Copy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 17 12:43:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA06123 for freebsd-current-outgoing; Fri, 17 Jul 1998 12:43:23 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ady.warpnet.ro (ady.warpnet.ro [193.230.201.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA06104 for ; Fri, 17 Jul 1998 12:43:12 -0700 (PDT) (envelope-from ady@warpnet.ro) Received: from localhost (ady@localhost) by ady.warpnet.ro (8.8.8/8.8.8) with SMTP id WAA12092; Fri, 17 Jul 1998 22:42:23 +0300 (EEST) (envelope-from ady@warpnet.ro) Date: Fri, 17 Jul 1998 22:42:23 +0300 (EEST) From: Adrian Penisoara To: Adam McDougall cc: current@FreeBSD.ORG Subject: Re: ppp problems In-Reply-To: <35AEAAA5.FFD655EF@ameritech.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, On Thu, 16 Jul 1998, Adam McDougall wrote: > Snob Art Genre wrote: > > > I'm having intermittent userland PPP problems with bleeding-edge > > current. I've seen this before, but it just happened twice in ten > > minutes, which is unusual. > > I don't know about you guys, but I have a problem like this with PPP connections between FreeBSD 3.0-980520-SNAP and other FreeBSD machines (2.2.5-RELEASE, 2.2.6-RELEASE and even 3.0971117-SNAP). Synopsys: suddenly (maybe) the ppp process starts logging lines like the following in /var/log/ppp.log and the PPP connection remains in a "stale" phase in which IP data packets _cannot_ be transferred but the low-level PPP control packets (except CCP, see down) seem to work in both directions (the connection doesn't time out). --[ /var/log/ppp.log extract ]------------------------------------------- Jul 12 21:45:56 ady ppp[6854]: tun2: Warning: CCP: Incorrect ResetAck (id 2, not 3) ignored ------------------------------------------------------------------------- And the messages keep rolling on until I either break the link (by upluging the phone jack) or I restart the ppp daemon. Notice, I'm starting the ppp process with 'ppp -ddial profile'... Is this what you see or is it another problem ? > > Ben > > > > "You have your mind on computers, it seems." > > > Hmm, this morning I woke up to a dead link, from my mrtg graphs > apparently it had been dead several hours, I just told it to close and > -ddial took care of reconnecting. So I might be seeing the same thing as > you. Thank you, Ady (@freebsd.ady.ro) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 17 12:45:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA06495 for freebsd-current-outgoing; Fri, 17 Jul 1998 12:45:11 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.133.1] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA06484 for ; Fri, 17 Jul 1998 12:45:00 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.5) with ESMTP id VAA00930; Fri, 17 Jul 1998 21:40:17 +0200 (CEST) To: Amancio Hasty cc: Henry Vogt , grog@lemis.com (Greg Lehey), alk@pobox.com, current@FreeBSD.ORG Subject: Re: State of current... In-reply-to: Your message of "Fri, 17 Jul 1998 08:55:01 PDT." <199807171555.IAA02118@rah.star-gate.com> Date: Fri, 17 Jul 1998 21:40:17 +0200 Message-ID: <928.900704417@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199807171555.IAA02118@rah.star-gate.com>, Amancio Hasty writes: >My guess is that the problems are due to the recent network patches. > Seems like it, I have backed down to 1.40 of sys/kern/uipc_socket.c as Garrett suggested, and I havn't had any problems since... -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 17 12:54:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA08706 for freebsd-current-outgoing; Fri, 17 Jul 1998 12:54:48 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gjp.erols.com (root@alex-va-n008c079.moon.jic.com [206.156.18.89]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA08688 for ; Fri, 17 Jul 1998 12:54:43 -0700 (PDT) (envelope-from gjp@gjp.erols.com) Received: from gjp.erols.com (gjp@localhost.erols.com [127.0.0.1]) by gjp.erols.com (8.8.8/8.8.7) with ESMTP id PAA05750; Fri, 17 Jul 1998 15:54:05 -0400 (EDT) (envelope-from gjp@gjp.erols.com) X-Mailer: exmh version 2.0.1 12/23/97 To: Greg Lehey cc: alk@pobox.com, current@FreeBSD.ORG From: "Gary Palmer" Subject: Re: State of current... In-reply-to: Your message of "Fri, 17 Jul 1998 17:37:14 +0930." <19980717173714.Q566@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 17 Jul 1998 15:54:05 -0400 Message-ID: <5746.900705245@gjp.erols.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greg Lehey wrote in message ID <19980717173714.Q566@freebie.lemis.com>: > I was wondering if something was wrong, too. I haven't had this > particular problem, but I've had a number of processes, including > Emacs, hang in select after VisibilityNotify events, unable to update > their displays. It's nothing enough to be sure that anything's wrong, > but enough to be noticable. I'm rebuilding with the latest -current > (as of about 2 hours ago), and will try again. I've had exmh 2.0.1 hang without obvious cause (and in select), and Netscape seems to often have problems generating message popups. (They often came up with zero dimensions) Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 17 12:59:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA09724 for freebsd-current-outgoing; Fri, 17 Jul 1998 12:59:02 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA09719 for ; Fri, 17 Jul 1998 12:58:56 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id MAA19685; Fri, 17 Jul 1998 12:57:39 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: Tom Bartol cc: current@FreeBSD.ORG Subject: Re: X gets left out of install of 3.0-19980711-SNAP In-reply-to: Your message of "Fri, 17 Jul 1998 09:04:57 PDT." Date: Fri, 17 Jul 1998 12:57:39 -0700 Message-ID: <19682.900705459@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hmmmm! I'll look into this. - Jordan > I just burned a bootable CD of 3.0-19980711-SNAP and did a clean install > from scratch off the CD. The installation was smooth and nearly flawless > -- the sole exception being that XFree86 was overlooked by the install > process even thought I selected it. Puzzled, I rebooted into my newly > installed system and ran /stand/sysinstall and reselected the XFree86 > distribution for installation but it was still ignored. I verified that I > was selecting distributions correctly by reselecting and reinstalling the > src distribution without a problem. > > So, has anyone else experienced this, have I found a real problem here, > or is my CD somehow corrupted? > > Thanks, > > Tom > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 17 12:59:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA09760 for freebsd-current-outgoing; Fri, 17 Jul 1998 12:59:09 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ady.warpnet.ro (ady.warpnet.ro [193.230.201.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA09711 for ; Fri, 17 Jul 1998 12:58:52 -0700 (PDT) (envelope-from ady@warpnet.ro) Received: from localhost (ady@localhost) by ady.warpnet.ro (8.8.8/8.8.8) with SMTP id WAA12160; Fri, 17 Jul 1998 22:57:46 +0300 (EEST) (envelope-from ady@warpnet.ro) Date: Fri, 17 Jul 1998 22:57:46 +0300 (EEST) From: Adrian Penisoara To: Tom Bartol cc: current@FreeBSD.ORG Subject: Re: X gets left out of install of 3.0-19980711-SNAP In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, On Fri, 17 Jul 1998, Tom Bartol wrote: > > Hi all, > > I just burned a bootable CD of 3.0-19980711-SNAP and did a clean install > from scratch off the CD. The installation was smooth and nearly flawless > -- the sole exception being that XFree86 was overlooked by the install > process even thought I selected it. Puzzled, I rebooted into my newly > installed system and ran /stand/sysinstall and reselected the XFree86 > distribution for installation but it was still ignored. I verified that I > was selecting distributions correctly by reselecting and reinstalling the > src distribution without a problem. If I'm not mistaken 2.2.6-RELEASE has the same behaviour -- I once wanted to install the X packages too and, after selecting bin,docs,man,src and choosing the X servers and additional packages and after rebooting I realised that everything but X was installed; after this, when I tried /stand/sysinstall, it did install the X packages but without any pre-/post- installation scripts, it didn't run ldconfig on /usr/X11R6/lib. This is just from my memories, I haven't check this in detail, I thought I did smth. wrong. > > So, has anyone else experienced this, have I found a real problem here, > or is my CD somehow corrupted? > > Thanks, > > Tom > Ady (@freebsd.ady.ro) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 17 13:33:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA15349 for freebsd-current-outgoing; Fri, 17 Jul 1998 13:33:02 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from forbidden-donut.anet-stl.com (vmailer@forbidden-donut.anet-stl.com [209.83.128.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA15298 for ; Fri, 17 Jul 1998 13:32:54 -0700 (PDT) (envelope-from doogie@forbidden-donut.anet-stl.com) Received: from localhost (localhost.anet-stl.com 127.0.0.1) by forbidden-donut.anet-stl.com (VMailer) via SMTP id 3C447AB81; Fri, 17 Jul 1998 15:32:40 -0500 (CDT) Date: Fri, 17 Jul 1998 15:32:40 -0500 (CDT) From: Jason Young To: "Jordan K. Hubbard" Cc: Tom Bartol , current@FreeBSD.ORG Subject: Re: X gets left out of install of 3.0-19980711-SNAP In-Reply-To: <19682.900705459@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This happened several times to me. It would install compat21, but nothing else. Eventually, I found out that ftp2.freebsd.org doesn't have XFree86. I switched over to ftp3 which does, and it was copacetic from there. Sysinstall naturally can't install what isn't there, but it would be nice if it would at least complain about it. Sysinstall knows to complain about normal dists that it can't fetch. I assume that he put XFree86 on the CD, but it may not be in a path that sysinstall wants to find it in, and thus it just silently fails. Jason Young ANET Chief Network Engineer On Fri, 17 Jul 1998, Jordan K. Hubbard wrote: > Hmmmm! I'll look into this. > > - Jordan > > > I just burned a bootable CD of 3.0-19980711-SNAP and did a clean install > > from scratch off the CD. The installation was smooth and nearly flawless > > -- the sole exception being that XFree86 was overlooked by the install > > process even thought I selected it. Puzzled, I rebooted into my newly > > installed system and ran /stand/sysinstall and reselected the XFree86 > > distribution for installation but it was still ignored. I verified that I > > was selecting distributions correctly by reselecting and reinstalling the > > src distribution without a problem. > > > > So, has anyone else experienced this, have I found a real problem here, > > or is my CD somehow corrupted? > > > > Thanks, > > > > Tom > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 17 13:54:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA19786 for freebsd-current-outgoing; Fri, 17 Jul 1998 13:54:59 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zone.baldcom.net (green@zone.BALDCOM.NET [205.232.46.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA19781 for ; Fri, 17 Jul 1998 13:54:54 -0700 (PDT) (envelope-from green@zone.baldcom.net) Received: from localhost (green@localhost) by zone.baldcom.net (8.8.8/8.8.7) with SMTP id QAA18133 for ; Fri, 17 Jul 1998 16:54:52 -0400 (EDT) Date: Fri, 17 Jul 1998 16:54:52 -0400 (EDT) From: Brian Feldman To: current@FreeBSD.ORG Subject: Re: State of current... In-Reply-To: <199807171555.IAA02118@rah.star-gate.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yes, this certainly does fix it. Anyone want to back out that delta? Here's the patchlet to go back to the old version: Index: src/sys/kern/uipc_socket.c diff -u src/sys/kern/uipc_socket.c:1.41 src/sys/kern/uipc_socket.c:1.40 --- src/sys/kern/uipc_socket.c:1.41 Mon Jul 6 19:27:14 1998 +++ src/sys/kern/uipc_socket.c Fri May 15 20:11:30 1998 @@ -31,7 +31,7 @@ * SUCH DAMAGE. * * @(#)uipc_socket.c 8.3 (Berkeley) 4/15/94 - * $Id: uipc_socket.c,v 1.41 1998/07/06 19:27:14 fenner Exp $ + * $Id: uipc_socket.c,v 1.40 1998/05/15 20:11:30 wollman Exp $ */ #include @@ -491,7 +491,6 @@ mlen = MCLBYTES; len = min(min(mlen, resid), space); } else { - atomic = 1; nopages: len = min(min(mlen, resid), space); /* Cheers, Brian Feldman P.S. Sorry, hope the patch doesn't insult anyone's intelligence. On Fri, 17 Jul 1998, Amancio Hasty wrote: > My guess is that the problems are due to the recent network patches. > > Amancio > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 17 13:58:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA20541 for freebsd-current-outgoing; Fri, 17 Jul 1998 13:58:12 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from helmholtz.salk.edu (helmholtz.salk.edu [198.202.70.34]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA20534 for ; Fri, 17 Jul 1998 13:58:11 -0700 (PDT) (envelope-from bartol@salk.edu) Received: from cole.salk.edu (cole [198.202.70.113]) by helmholtz.salk.edu (8.7.5/8.7.3) with SMTP id NAA16179; Fri, 17 Jul 1998 13:57:48 -0700 (PDT) Date: Fri, 17 Jul 1998 13:57:46 -0700 (PDT) From: Tom Bartol To: Jason Young cc: "Jordan K. Hubbard" , current@FreeBSD.ORG Subject: Re: X gets left out of install of 3.0-19980711-SNAP In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just to clarify -- Yes I do have XFree86 on the CD in the correct place. And Yes, sysinstall is failing silently. Tom On Fri, 17 Jul 1998, Jason Young wrote: > > This happened several times to me. It would install compat21, but nothing > else. Eventually, I found out that ftp2.freebsd.org doesn't have XFree86. > I switched over to ftp3 which does, and it was copacetic from there. > > Sysinstall naturally can't install what isn't there, but it would be nice > if it would at least complain about it. Sysinstall knows to complain about > normal dists that it can't fetch. > > I assume that he put XFree86 on the CD, but it may not be in a path that > sysinstall wants to find it in, and thus it just silently fails. > > Jason Young > ANET Chief Network Engineer > > On Fri, 17 Jul 1998, Jordan K. Hubbard wrote: > > > Hmmmm! I'll look into this. > > > > - Jordan > > > > > I just burned a bootable CD of 3.0-19980711-SNAP and did a clean install > > > from scratch off the CD. The installation was smooth and nearly flawless > > > -- the sole exception being that XFree86 was overlooked by the install > > > process even thought I selected it. Puzzled, I rebooted into my newly > > > installed system and ran /stand/sysinstall and reselected the XFree86 > > > distribution for installation but it was still ignored. I verified that I > > > was selecting distributions correctly by reselecting and reinstalling the > > > src distribution without a problem. > > > > > > So, has anyone else experienced this, have I found a real problem here, > > > or is my CD somehow corrupted? > > > > > > Thanks, > > > > > > Tom > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > with "unsubscribe freebsd-current" in the body of the message > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 17 14:22:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA25326 for freebsd-current-outgoing; Fri, 17 Jul 1998 14:22:43 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from thing.dyn.ml.org (dyn-max10-165.chicago.il.ameritech.net [206.141.212.165] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA25318 for ; Fri, 17 Jul 1998 14:22:41 -0700 (PDT) (envelope-from mcdougall@ameritech.net) Received: from ameritech.net (bsdx [192.168.1.2]) by thing.dyn.ml.org (8.8.8/8.8.7) with ESMTP id RAA09153; Fri, 17 Jul 1998 17:21:46 -0400 (EDT) (envelope-from mcdougall@ameritech.net) Message-ID: <35AFC069.48AAED73@ameritech.net> Date: Fri, 17 Jul 1998 17:21:45 -0400 From: Adam McDougall Reply-To: mcdougall@ameritech.net X-Mailer: Mozilla 4.05 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: Adrian Penisoara CC: current@FreeBSD.ORG Subject: Re: ppp problems References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Adrian Penisoara wrote: > And the messages keep rolling on until I either break the link (by > upluging the phone jack) or I restart the ppp daemon. Notice, I'm starting > the ppp process with 'ppp -ddial profile'... > > Is this what you see or is it another problem ? > Hmm didnt think to check the logs :) Unfortunately nothing happened in the log at the time of failure. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 17 14:26:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA26303 for freebsd-current-outgoing; Fri, 17 Jul 1998 14:26:53 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ady.warpnet.ro (ady.warpnet.ro [193.230.201.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA26282 for ; Fri, 17 Jul 1998 14:26:41 -0700 (PDT) (envelope-from ady@warpnet.ro) Received: from localhost (ady@localhost) by ady.warpnet.ro (8.8.8/8.8.8) with SMTP id AAA12651; Sat, 18 Jul 1998 00:26:17 +0300 (EEST) (envelope-from ady@warpnet.ro) Date: Sat, 18 Jul 1998 00:26:17 +0300 (EEST) From: Adrian Penisoara To: Adam McDougall cc: current@FreeBSD.ORG Subject: Re: ppp problems In-Reply-To: <35AFC069.48AAED73@ameritech.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, On Fri, 17 Jul 1998, Adam McDougall wrote: > Adrian Penisoara wrote: > > > And the messages keep rolling on until I either break the link (by > > upluging the phone jack) or I restart the ppp daemon. Notice, I'm starting > > the ppp process with 'ppp -ddial profile'... > > > > Is this what you see or is it another problem ? > > > > Hmm didnt think to check the logs :) Unfortunately nothing happened in the > log at the time of failure. But was it behaving like my case -- remaining "stale" until you manually break the link (restarting the process, disconecting the phone jack, etc.)? > Thanks, Ady (@freebsd.ady.ro) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 17 14:51:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA01067 for freebsd-current-outgoing; Fri, 17 Jul 1998 14:51:15 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from home.dragondata.com (toasty@home.dragondata.com [204.137.237.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA01062 for ; Fri, 17 Jul 1998 14:51:13 -0700 (PDT) (envelope-from toasty@home.dragondata.com) Received: (from toasty@localhost) by home.dragondata.com (8.8.8/8.8.5) id QAA22723; Fri, 17 Jul 1998 16:50:54 -0500 (CDT) From: Kevin Day Message-Id: <199807172150.QAA22723@home.dragondata.com> Subject: Re: X gets left out of install of 3.0-19980711-SNAP In-Reply-To: <19682.900705459@time.cdrom.com> from "Jordan K. Hubbard" at "Jul 17, 98 12:57:39 pm" To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Fri, 17 Jul 1998 16:50:53 -0500 (CDT) Cc: bartol@salk.edu, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hmmmm! I'll look into this. > I've had this happen too, you select the Xfree distro, it installs everything *but* xfree that youv'e selected, and leaves it checked in the 'Distributions' menu. No matter what I did, I couldn't get it to take it. This was on an install over FTP..... Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 17 16:54:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA19113 for freebsd-current-outgoing; Fri, 17 Jul 1998 16:54:57 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from isua3.iastate.edu (isua3.iastate.edu [129.186.1.139]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA19094 for ; Fri, 17 Jul 1998 16:54:50 -0700 (PDT) (envelope-from graphix@iastate.edu) Received: from localhost (graphix@localhost) by isua3.iastate.edu (8.8.5/8.8.5) with SMTP id SAA12810; Fri, 17 Jul 1998 18:54:35 -0500 (CDT) Message-Id: <199807172354.SAA12810@isua3.iastate.edu> To: freebsd-current@FreeBSD.ORG cc: xfree86@xfree86.org Reply-To: kent@iastate.edu Subject: XFree and -current Date: Fri, 17 Jul 1998 18:54:34 CDT From: Kent Vander Velden Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Starting a week ago after I installed a new kernel, XFree 3.3.2 has become _very_ flaky. The problem only seems to show up in 24 bit true-color mode. Many programs such as Netscape die with, generally, a BadLength X error. I am using the S3 server with a 4M STB Velocity 64. --- Kent Vander Velden kent@iastate.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 17 17:11:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA21967 for freebsd-current-outgoing; Fri, 17 Jul 1998 17:11:13 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.mishkei.org.il (host3-64.mishkei.org.il [62.0.64.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA21956 for ; Fri, 17 Jul 1998 17:11:07 -0700 (PDT) (envelope-from lickyou@ein-hashofet.co.il) Received: from localhost.my.domain (host40-68.mishkei.org.il [62.0.68.40]) by mail.mishkei.org.il (8.8.5/8.8.5) with SMTP id DAA23787 for ; Sat, 18 Jul 1998 03:10:23 +0300 Date: Sat, 18 Jul 1998 03:08:53 +0000 (GMT) From: Gilad Rom X-Sender: lickyou@localhost.my.domain Reply-To: rom_glsa@ein-hashofet.co.il To: current@FreeBSD.ORG Subject: Re: X gets left out of install of 3.0-19980711-SNAP In-Reply-To: <199807172150.QAA22723@home.dragondata.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Same here. Cant seem to make sysinstall Install X. Happened to me with -RELEASE and -STABLE. Ive never had the chance to install -CURRENT from scratch using sysinstall. This was all on FTP installs, so maybe I did something wrong, or the mirror was failing. I cant exactly tell. Gilad To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 17 18:41:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA02075 for freebsd-current-outgoing; Fri, 17 Jul 1998 18:41:48 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from echonyc.com (echonyc.com [198.67.15.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA02058 for ; Fri, 17 Jul 1998 18:41:45 -0700 (PDT) (envelope-from benedict@echonyc.com) Received: from localhost (benedict@localhost) by echonyc.com (8.8.7/8.8.7) with SMTP id VAA20398; Fri, 17 Jul 1998 21:40:34 -0400 (EDT) Date: Fri, 17 Jul 1998 21:40:34 -0400 (EDT) From: Snob Art Genre Reply-To: ben@rosengart.com To: Adrian Penisoara cc: Adam McDougall , current@FreeBSD.ORG Subject: Re: ppp problems In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 17 Jul 1998, Adrian Penisoara wrote: > --[ /var/log/ppp.log extract ]------------------------------------------- > Jul 12 21:45:56 ady ppp[6854]: tun2: Warning: CCP: Incorrect ResetAck (id > 2, not 3) ignored > ------------------------------------------------------------------------- > > And the messages keep rolling on until I either break the link (by > upluging the phone jack) or I restart the ppp daemon. Notice, I'm starting > the ppp process with 'ppp -ddial profile'... > > Is this what you see or is it another problem ? I must be seeing something else, my ppp.log is empty and ppp.log.0.gz doesn't contain any instances of the string "CCP". Ben "You have your mind on computers, it seems." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 17 21:13:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA13672 for freebsd-current-outgoing; Fri, 17 Jul 1998 21:13:13 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from home.corecom.net (mikepp@[199.237.128.11]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA13657 for ; Fri, 17 Jul 1998 21:13:00 -0700 (PDT) (envelope-from mikepp@home.corecom.net) Received: (from mikepp@localhost) by home.corecom.net (8.8.7/8.8.7) id TAA11445; Fri, 17 Jul 1998 19:46:30 -0800 (AKDT) Message-ID: X-Mailer: XFMail 1.2 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Fri, 17 Jul 1998 20:11:29 -0800 (AKDT) Reply-To: me@corecom.net From: "Michael A. Endsley" To: current@FreeBSD.ORG Subject: lost my pnp devices after recompile Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I haven't seen this discussed. I am running 3.0-980523-SNAP. I had to re-compile to use sio 3 and 4. After recompiling and rebooting, there was no pnp modem or sound card attached! Is this normal? Do I have to reconfigure those in everytime I compile? Otherwise, this snap is working great for me (presently just a home user). I ask this question here since I am running current and thot it might be a bug. TIA, Mike ------------------------------------------------------------------------------- OS's of CHOICE? Unix (FreeBSD), Linux (Debian), OS2/Warp3 If Microsoft is the answer, the question should never have been asked! me AT corecom.net http://www.corecom.net/endsley/ ------------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 17 23:12:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA23418 for freebsd-current-outgoing; Fri, 17 Jul 1998 23:12:02 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zone.baldcom.net (green@zone.BALDCOM.NET [205.232.46.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA23376 for ; Fri, 17 Jul 1998 23:11:59 -0700 (PDT) (envelope-from green@zone.baldcom.net) Received: from localhost (green@localhost) by zone.baldcom.net (8.8.8/8.8.7) with SMTP id CAA23363; Sat, 18 Jul 1998 02:11:47 -0400 (EDT) Date: Sat, 18 Jul 1998 02:11:47 -0400 (EDT) From: Brian Feldman To: "Michael A. Endsley" cc: current@FreeBSD.ORG Subject: Re: lost my pnp devices after recompile In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yes, you do. 1. make sure that pnp is actually compiled in the kernel and 2. realize that the all config options, pnp included, get saved in-kernel at boot-time with dset, so new kernels would have to be configured again if you configured this previous one with userconf; of course, another solution would be making a kernel configuration file to go in your root dir. Hope this helps. Brian Feldman On Fri, 17 Jul 1998, Michael A. Endsley wrote: > Hello, > I haven't seen this discussed. > I am running 3.0-980523-SNAP. I had to re-compile to use sio 3 and 4. After > recompiling and rebooting, there was no pnp modem or sound card attached! > Is this normal? Do I have to reconfigure those in everytime I compile? > Otherwise, this snap is working great for me (presently just a home user). > I ask this question here since I am running current and thot it might be a > bug. > TIA, > Mike > > ------------------------------------------------------------------------------- > OS's of CHOICE? Unix (FreeBSD), Linux (Debian), OS2/Warp3 > If Microsoft is the answer, the question should never have been asked! > > me AT corecom.net > http://www.corecom.net/endsley/ > ------------------------------------------------------------------------------- > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 18 00:57:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA00287 for freebsd-current-outgoing; Sat, 18 Jul 1998 00:57:45 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA00281 for ; Sat, 18 Jul 1998 00:57:42 -0700 (PDT) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id JAA00446 for current@FreeBSD.ORG; Sat, 18 Jul 1998 09:57:28 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: (from roberto@localhost) by keltia.freenix.fr (8.9.0.Beta4/keltia-2.14/nospam) id AAA09137 for current@FreeBSD.ORG; Sat, 18 Jul 1998 00:27:11 +0200 (CEST) (envelope-from roberto) Message-ID: <19980718002711.A6798@keltia.freenix.fr> Date: Sat, 18 Jul 1998 00:27:11 +0200 From: Ollivier Robert To: current@FreeBSD.ORG Subject: Re: State of current... Mail-Followup-To: current@FreeBSD.ORG References: <19980717173714.Q566@freebie.lemis.com> <6601.900665763@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93i In-Reply-To: <6601.900665763@critter.freebsd.dk>; from Poul-Henning Kamp on Fri, Jul 17, 1998 at 10:56:03AM +0200 X-Operating-System: FreeBSD 3.0-CURRENT ctm#4462 AMD-K6 MMX @ 225 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Poul-Henning Kamp: > I've seen this problem too. I'm seeing it too (although my current is about 6 days old). I had a few xterms stopping updating then dying on me (without any message). My X server died once too. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #61: Sun Jul 12 14:38:23 CEST 1998 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 18 02:04:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA03804 for freebsd-current-outgoing; Sat, 18 Jul 1998 02:04:40 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freebie.lemis.com (freebie.lemis.com [139.130.136.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA03799 for ; Sat, 18 Jul 1998 02:04:34 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id SAA03462; Sat, 18 Jul 1998 18:34:10 +0930 (CST) Message-ID: <19980718183410.F957@freebie.lemis.com> Date: Sat, 18 Jul 1998 18:34:10 +0930 From: Greg Lehey To: Brian Feldman Cc: FreeBSD current users Subject: Re: State of current... References: <199807171555.IAA02118@rah.star-gate.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from Brian Feldman on Fri, Jul 17, 1998 at 04:54:52PM -0400 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Friday, 17 July 1998 at 16:54:52 -0400, Brian Feldman wrote: > Yes, this certainly does fix it. Anyone want to back out that delta? > Here's the patchlet to go back to the old version: > > Index: src/sys/kern/uipc_socket.c > diff -u src/sys/kern/uipc_socket.c:1.41 src/sys/kern/uipc_socket.c:1.40 > --- src/sys/kern/uipc_socket.c:1.41 Mon Jul 6 19:27:14 1998 > +++ src/sys/kern/uipc_socket.c Fri May 15 20:11:30 1998 > @@ -31,7 +31,7 @@ > * SUCH DAMAGE. > * > * @(#)uipc_socket.c 8.3 (Berkeley) 4/15/94 > - * $Id: uipc_socket.c,v 1.41 1998/07/06 19:27:14 fenner Exp $ > + * $Id: uipc_socket.c,v 1.40 1998/05/15 20:11:30 wollman Exp $ > */ > > #include > @@ -491,7 +491,6 @@ > mlen = MCLBYTES; > len = min(min(mlen, resid), space); > } else { > - atomic = 1; > nopages: > len = min(min(mlen, resid), space); > /* That seems to have done the trick for me, too. Greg -- See complete headers for address and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 18 02:18:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA04555 for freebsd-current-outgoing; Sat, 18 Jul 1998 02:18:42 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com (rah.star-gate.com [209.133.7.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA04550 for ; Sat, 18 Jul 1998 02:18:40 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id CAA01439; Sat, 18 Jul 1998 02:18:14 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199807180918.CAA01439@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Greg Lehey cc: Brian Feldman , FreeBSD current users Subject: Re: State of current... In-reply-to: Your message of "Sat, 18 Jul 1998 18:34:10 +0930." <19980718183410.F957@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 18 Jul 1998 02:18:13 -0700 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG No problems over here after the patch. Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 18 02:51:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA06619 for freebsd-current-outgoing; Sat, 18 Jul 1998 02:51:33 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp03.primenet.com (daemon@smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA06614 for ; Sat, 18 Jul 1998 02:51:26 -0700 (PDT) (envelope-from tlambert@usr07.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id CAA01589; Sat, 18 Jul 1998 02:51:14 -0700 (MST) Received: from usr07.primenet.com(206.165.6.207) via SMTP by smtp03.primenet.com, id smtpd001581; Sat Jul 18 02:51:13 1998 Received: (from tlambert@localhost) by usr07.primenet.com (8.8.5/8.8.5) id CAA06301; Sat, 18 Jul 1998 02:51:11 -0700 (MST) From: Terry Lambert Message-Id: <199807180951.CAA06301@usr07.primenet.com> Subject: Re: State of current... To: roberto@keltia.freenix.fr (Ollivier Robert) Date: Sat, 18 Jul 1998 09:51:11 +0000 (GMT) Cc: current@FreeBSD.ORG In-Reply-To: <19980718002711.A6798@keltia.freenix.fr> from "Ollivier Robert" at Jul 18, 98 00:27:11 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Some like it hot; Some like it cold; Some like it in the pot... > I'm seeing it too (although my current is about 6 days old). Try upgrading now... Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 18 04:15:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA13840 for freebsd-current-outgoing; Sat, 18 Jul 1998 04:15:05 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from engulf.net (engulf.com [207.96.124.102]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA13825 for ; Sat, 18 Jul 1998 04:15:01 -0700 (PDT) (envelope-from brandon@engulf.net) Received: from localhost (brandon@localhost) by engulf.net (8.8.8/8.8.8) with SMTP id HAA07865 for ; Sat, 18 Jul 1998 07:13:16 -0400 (EDT) Date: Sat, 18 Jul 1998 07:13:05 -0400 (EDT) From: Brandon Lockhart To: freebsd-current@FreeBSD.ORG Subject: engulf weekly run output (fwd) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Running weekly.local: Sat Jul 18 03:33:06 EDT 1998 Sat Jul 18 03:58:54 EDT 1998 # /etc/weekly.local date cd /usr/src/ make world 1>/dev/null 2>/dev/null date That seems awful fast to Make the source, what am I missing here?!? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 18 07:09:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA23038 for freebsd-current-outgoing; Sat, 18 Jul 1998 07:09:23 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from news1.gtn.com (news1.gtn.com [192.109.159.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA23032 for ; Sat, 18 Jul 1998 07:09:20 -0700 (PDT) (envelope-from andreas@klemm.gtn.com) Received: (from uucp@localhost) by news1.gtn.com (8.8.6/8.8.6) with UUCP id QAA20024; Sat, 18 Jul 1998 16:00:10 +0200 (MET DST) Received: (from andreas@localhost) by klemm.gtn.com (8.8.8/8.8.8) id QAA14366; Sat, 18 Jul 1998 16:48:59 +0200 (CEST) (envelope-from andreas) Message-ID: <19980718164859.B13033@klemm.gtn.com> Date: Sat, 18 Jul 1998 16:48:59 +0200 From: Andreas Klemm To: Brandon Lockhart , freebsd-current@FreeBSD.ORG Subject: Re: engulf weekly run output (fwd) References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from Brandon Lockhart on Sat, Jul 18, 1998 at 07:13:05AM -0400 X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 3.0-CURRENT SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Jul 18, 1998 at 07:13:05AM -0400, Brandon Lockhart wrote: > Running weekly.local: > Sat Jul 18 03:33:06 EDT 1998 > Sat Jul 18 03:58:54 EDT 1998 > > # /etc/weekly.local > date > cd /usr/src/ > make world 1>/dev/null 2>/dev/null > date > That seems awful fast to Make the source, what am I missing here?!? Looks good. You could also write this as: make world > /dev/null 2>&1 Instead of this I'd also do it this way: - put it into your root's crontab, so that your weekly script doesn't contain too much overhead, - do a ( cd /usr/src; date; make buildworld > /usr/src/world.log 2>&1; date ) or ( cd /usr/src; date; make buildworld; date ) Then you also get the result as mail on a daily or weekly basis - if a make buildworld was completely successfull, then I'd do a make installworld manually in single user mode and then reboot -- Andreas Klemm http://www.FreeBSD.ORG/~andreas What gives you 90% more speed, for example, in kernel compilation ? http://www.FreeBSD.ORG/~fsmp/SMP/akgraph-a/graph1.html "NT = Not Today" (Maggie Biggs) ``powered by FreeBSD SMP'' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 18 07:09:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA23070 for freebsd-current-outgoing; Sat, 18 Jul 1998 07:09:39 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from news1.gtn.com (news1.gtn.com [192.109.159.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA23065 for ; Sat, 18 Jul 1998 07:09:36 -0700 (PDT) (envelope-from andreas@klemm.gtn.com) Received: (from uucp@localhost) by news1.gtn.com (8.8.6/8.8.6) with UUCP id QAA20034; Sat, 18 Jul 1998 16:00:19 +0200 (MET DST) Received: (from andreas@localhost) by klemm.gtn.com (8.8.8/8.8.8) id QAA13046; Sat, 18 Jul 1998 16:41:44 +0200 (CEST) (envelope-from andreas) Message-ID: <19980718164143.A13033@klemm.gtn.com> Date: Sat, 18 Jul 1998 16:41:43 +0200 From: Andreas Klemm To: kent@iastate.edu, freebsd-current@FreeBSD.ORG Cc: xfree86@xfree86.org Subject: Re: XFree and -current References: <199807172354.SAA12810@isua3.iastate.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199807172354.SAA12810@isua3.iastate.edu>; from Kent Vander Velden on Fri, Jul 17, 1998 at 06:54:34PM -0500 X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 3.0-CURRENT SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jul 17, 1998 at 06:54:34PM -0500, Kent Vander Velden wrote: > > Starting a week ago after I installed a new kernel, XFree 3.3.2 > has become _very_ flaky. The problem only seems to show up in 24 bit > true-color mode. Many programs such as Netscape die with, generally, a > BadLength X error. I am using the S3 server with a 4M STB Velocity 64. Read the thread "State of current...". Backout the last patch of /sys/kern/uipc_socket.c (1.41 -> 1.40) This did the trick for many people reporting netscape instability. -- Andreas Klemm http://www.FreeBSD.ORG/~andreas What gives you 90% more speed, for example, in kernel compilation ? http://www.FreeBSD.ORG/~fsmp/SMP/akgraph-a/graph1.html "NT = Not Today" (Maggie Biggs) ``powered by FreeBSD SMP'' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 18 07:31:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA26051 for freebsd-current-outgoing; Sat, 18 Jul 1998 07:31:21 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from limbo.rtfm.net (nathan@38.nyack.fcc.net [204.141.125.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA26046 for ; Sat, 18 Jul 1998 07:31:18 -0700 (PDT) (envelope-from nathan@limbo.rtfm.net) Received: (from nathan@localhost) by limbo.rtfm.net (8.8.8/8.8.8) id KAA00704; Sat, 18 Jul 1998 10:29:57 -0400 (EDT) (envelope-from nathan) Date: Sat, 18 Jul 1998 10:29:57 -0400 (EDT) From: Nathan Dorfman Message-Id: <199807181429.KAA00704@limbo.rtfm.net> To: kent@iastate.edu, freebsd-current@FreeBSD.ORG Subject: Re: XFree and -current In-Reply-To: <199807172354.SAA12810@isua3.iastate.edu> Organization: RTFM.net Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Starting a week ago after I installed a new kernel, XFree 3.3.2 >has become _very_ flaky. The problem only seems to show up in 24 bit >true-color mode. Many programs such as Netscape die with, generally, a >BadLength X error. I am using the S3 server with a 4M STB Velocity 64. I'm getting this in 16-bit color mode, with XF86_SVGA and Diamond 3D 3000 Pro (S3 ViRGE). >--- >Kent Vander Velden >kent@iastate.edu > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message > -- ________________ ___________________________________________ / Nathan Dorfman \ / "My problems start when the smarter bears / nathan@rtfm.net \/ and the dumber visitors intersect." / finger for PGP key \ Steve Thompson, Yosemite wildlife biologist To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 18 07:40:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA26939 for freebsd-current-outgoing; Sat, 18 Jul 1998 07:40:56 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ady.warpnet.ro (ady.warpnet.ro [193.230.201.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA26917 for ; Sat, 18 Jul 1998 07:40:37 -0700 (PDT) (envelope-from ady@warpnet.ro) Received: from localhost (ady@localhost) by ady.warpnet.ro (8.8.8/8.8.8) with SMTP id RAA06488; Sat, 18 Jul 1998 17:38:09 +0300 (EEST) (envelope-from ady@warpnet.ro) Date: Sat, 18 Jul 1998 17:38:09 +0300 (EEST) From: Adrian Penisoara To: ben@rosengart.com cc: Adam McDougall , current@FreeBSD.ORG Subject: Re: ppp problems In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, On Fri, 17 Jul 1998, Snob Art Genre wrote: > On Fri, 17 Jul 1998, Adrian Penisoara wrote: > > > --[ /var/log/ppp.log extract ]------------------------------------------- > > Jul 12 21:45:56 ady ppp[6854]: tun2: Warning: CCP: Incorrect ResetAck (id > > 2, not 3) ignored > > ------------------------------------------------------------------------- > > > > And the messages keep rolling on until I either break the link (by > > upluging the phone jack) or I restart the ppp daemon. Notice, I'm starting > > the ppp process with 'ppp -ddial profile'... > > > > Is this what you see or is it another problem ? > > I must be seeing something else, my ppp.log is empty and ppp.log.0.gz > doesn't contain any instances of the string "CCP". Maybe you have disabled some of the logging (I have "set log Link Connect TUN" here) ? But anyway, there is quite a time gap from 980520 and -current, maybe you're right, it was fixed and this is something else... BTW, does the link remain in a "stale" phase, like it remains up but no data can be transfered through the link ? > > > Ben > > "You have your mind on computers, it seems." > Thanks, Ady (@freebsd.ady.ro) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 18 08:47:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA03600 for freebsd-current-outgoing; Sat, 18 Jul 1998 08:47:55 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ix.netcom.com (sil-wa4-51.ix.netcom.com [207.93.136.115]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA03595 for ; Sat, 18 Jul 1998 08:47:53 -0700 (PDT) (envelope-from tomdean@ix.netcom.com) Received: (from tomdean@localhost) by ix.netcom.com (8.8.8/8.8.8) id IAA00505; Sat, 18 Jul 1998 08:47:37 -0700 (PDT) (envelope-from tomdean) Date: Sat, 18 Jul 1998 08:47:37 -0700 (PDT) Message-Id: <199807181547.IAA00505@ix.netcom.com> From: Thomas Dean To: brandon@engulf.net CC: freebsd-current@FreeBSD.ORG In-reply-to: (message from Brandon Lockhart on Sat, 18 Jul 1998 07:13:05 -0400 (EDT)) Subject: Re: engulf weekly run output (fwd) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Looks like 'make world' failed. Tyr make world > /usr/src/make.out 2>&1 and look at 'tail -40' make.out To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 18 10:52:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA11649 for freebsd-current-outgoing; Sat, 18 Jul 1998 10:52:46 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from isua3.iastate.edu (isua3.iastate.edu [129.186.1.139]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA11636 for ; Sat, 18 Jul 1998 10:52:43 -0700 (PDT) (envelope-from graphix@iastate.edu) Received: from localhost (graphix@localhost) by isua3.iastate.edu (8.8.5/8.8.5) with SMTP id MAA20662; Sat, 18 Jul 1998 12:52:23 -0500 (CDT) Message-Id: <199807181752.MAA20662@isua3.iastate.edu> To: Andreas Klemm cc: freebsd-current@FreeBSD.ORG Subject: Re: XFree and -current In-reply-to: Your message of "Sat, 18 Jul 1998 16:41:43 +0200." <19980718164143.A13033@klemm.gtn.com> Date: Sat, 18 Jul 1998 12:52:23 CDT From: Kent Vander Velden Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19980718164143.A13033@klemm.gtn.com>, Andreas Klemm writes: >On Fri, Jul 17, 1998 at 06:54:34PM -0500, Kent Vander Velden wrote: >> >> Starting a week ago after I installed a new kernel, XFree 3.3.2 >> has become _very_ flaky. The problem only seems to show up in 24 bit >> true-color mode. Many programs such as Netscape die with, generally, a >> BadLength X error. I am using the S3 server with a 4M STB Velocity 64. > >Read the thread "State of current...". >Backout the last patch of /sys/kern/uipc_socket.c (1.41 -> 1.40) >This did the trick for many people reporting netscape instability. Thanks. I read that shortly after sending my question and then receiving the freebsd-current digest. BTW: The fix works fine for me. Too bad I spent those two days hunting down a bug with my program though :) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 18 11:53:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA15835 for freebsd-current-outgoing; Sat, 18 Jul 1998 11:53:07 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpha.xerox.com (omega.Xerox.COM [13.1.64.95]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id LAA15828 for ; Sat, 18 Jul 1998 11:53:06 -0700 (PDT) (envelope-from fenner@parc.xerox.com) Received: from mango.parc.xerox.com ([13.1.102.232]) by alpha.xerox.com with SMTP id <40646(2)>; Sat, 18 Jul 1998 11:52:19 PDT Received: from mango.parc.xerox.com (localhost [127.0.0.1]) by mango.parc.xerox.com (8.8.8/8.8.8) with ESMTP id LAA12992 for ; Sat, 18 Jul 1998 11:52:12 -0700 (PDT) (envelope-from fenner@mango.parc.xerox.com) Message-Id: <199807181852.LAA12992@mango.parc.xerox.com> To: current@FreeBSD.ORG Subject: Re: State of current... In-reply-to: Your message of "Sat, 18 Jul 1998 02:51:11 PDT." <199807180951.CAA06301@usr07.primenet.com> Date: Sat, 18 Jul 1998 11:52:12 PDT From: Bill Fenner Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I backed out the fix. Does anyone have a test case that would reliably fail, so that I can try to figure out exactly what was going on? My testing didn't unveil any problems. Thanks, Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 18 13:08:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA21703 for freebsd-current-outgoing; Sat, 18 Jul 1998 13:08:29 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA21698 for ; Sat, 18 Jul 1998 13:08:28 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id NAA15940; Sat, 18 Jul 1998 13:03:46 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd015938; Sat Jul 18 20:03:43 1998 Date: Sat, 18 Jul 1998 13:03:37 -0700 (PDT) From: Julian Elischer To: Bill Fenner cc: current@FreeBSD.ORG Subject: Re: State of current... In-Reply-To: <199807181852.LAA12992@mango.parc.xerox.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG bill, I saw mail that said that the problem went away if DISPLAY was specified with localhost:0.0 instead of :0.0 I BELIEVE that this indicates that what was broken was unix domain sockets. (but I may be wrong) julian On Sat, 18 Jul 1998, Bill Fenner wrote: > I backed out the fix. Does anyone have a test case that would > reliably fail, so that I can try to figure out exactly what was > going on? My testing didn't unveil any problems. > > Thanks, > Bill > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 18 13:24:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA23853 for freebsd-current-outgoing; Sat, 18 Jul 1998 13:24:49 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com (rah.star-gate.com [209.133.7.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA23848 for ; Sat, 18 Jul 1998 13:24:47 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id NAA07599; Sat, 18 Jul 1998 13:24:33 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199807182024.NAA07599@rah.star-gate.com> To: Bill Fenner cc: current@FreeBSD.ORG, hasty@rah.star-gate.com Subject: Re: State of current... In-reply-to: Your message of "Sat, 18 Jul 1998 11:52:12 PDT." <199807181852.LAA12992@mango.parc.xerox.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <7596.900793473.1@rah.star-gate.com> Date: Sat, 18 Jul 1998 13:24:33 -0700 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Bill, Tony Kimball reported that remsh was not working reliably so perhaps he can tell us a little bit more. Over here , X apps were failing at random . Tnks! Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 18 13:45:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA26021 for freebsd-current-outgoing; Sat, 18 Jul 1998 13:45:05 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ecntr1.hosp.go.jp (ecntr1.hosp.go.jp [202.235.8.1]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA25965 for ; Sat, 18 Jul 1998 13:44:50 -0700 (PDT) (envelope-from ph_pan@stu.ust.hk) From: ph_pan@stu.ust.hk Received: by ecntr1.hosp.go.jp (8.6.12+2.5W/4.03) id FAA38616; Sun, 19 Jul 1998 05:39:23 +0900 DATE: 18 Jul 98 4:45:16 PM Reply-to: samson@samson-1.com Message-ID: TO: DO@ecntr1.hosp.go.jp, YOU@ecntr1.hosp.go.jp, WANT@ecntr1.hosp.go.jp, TO@ecntr1.hosp.go.jp, TRADE@ecntr1.hosp.go.jp, LINKS?@ecntr1.hosp.go.jp SUBJECT: L I N K ! Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Please add my site to your pages links, below is the code: APHRODISIACS "REAL" (VIAGRA/GHB/TESTOSTERONE) - THE GREY MARKET WEB MALL Cut and paste this link onto your website. Also, please send us a link to your webpage using the same code. We then will immediately place it on our links page. Our Web-Site is currently recieving approximatley 1000-1500 hits per/day. Thanks, Dan Amato - President SAMSON powerlifting / Bodybuilding co. 1-888-256-6785 (Toll Free Phone Call) email - samson@samson-1.com web address - www.samson-1.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 18 14:12:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA28664 for freebsd-current-outgoing; Sat, 18 Jul 1998 14:12:16 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from david.siemens.de (david.siemens.de [192.35.17.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA28657 for ; Sat, 18 Jul 1998 14:12:15 -0700 (PDT) (envelope-from andre.albsmeier@mchp.siemens.de) X-Envelope-Sender-Is: andre.albsmeier@mchp.siemens.de (at relayer david.siemens.de) Received: from mail.siemens.de (asp-khe.thm.net [139.23.33.13]) by david.siemens.de (8.9.1/8.9.1) with ESMTP id XAA01816 for ; Sat, 18 Jul 1998 23:10:16 +0200 (MET DST) Received: from curry.mchp.siemens.de (daemon@curry.mchp.siemens.de [146.180.31.23]) by mail.siemens.de (8.9.1/8.9.1) with ESMTP id XAA19131 for ; Sat, 18 Jul 1998 23:11:46 +0200 (MET DST) Received: (from daemon@localhost) by curry.mchp.siemens.de (8.8.8/8.8.8) id XAA11655 for ; Sat, 18 Jul 1998 23:11:47 +0200 (CEST) From: Andre Albsmeier Message-Id: <199807182111.XAA10290@internal> Subject: Re: State of current... In-Reply-To: <199807181852.LAA12992@mango.parc.xerox.com> from Bill Fenner at "Jul 18, 98 11:52:12 am" To: fenner@parc.xerox.com (Bill Fenner) Date: Sat, 18 Jul 1998 23:11:43 +0200 (CEST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I backed out the fix. Does anyone have a test case that would > reliably fail, so that I can try to figure out exactly what was > going on? My testing didn't unveil any problems. You know I was testing it on -STABLE for my squid proxy where the communication with its dnsservers worked like a charm WITH it. However, since I compile all my kernels from the same source I noticed in very rare cases the following thing on my X-Servers: I usually use CTRL-ALT-Backspace to leave the windowmanager which then drops back into xdm. From the moment I put the patch into sys/kern/uipc_socket.c this would fail in approx. 1 of 20 cases. The system freezes and could be recovered only by reset. I still doubt that is has something to do with it but it is funny that it started exactly when the patch was applied. -Andre To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 18 14:41:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA01674 for freebsd-current-outgoing; Sat, 18 Jul 1998 14:41:15 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zone.baldcom.net (green@zone.BALDCOM.NET [205.232.46.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA01666 for ; Sat, 18 Jul 1998 14:41:13 -0700 (PDT) (envelope-from green@zone.baldcom.net) Received: from localhost (green@localhost) by zone.baldcom.net (8.8.8/8.8.7) with SMTP id RAA05349; Sat, 18 Jul 1998 17:40:38 -0400 (EDT) Date: Sat, 18 Jul 1998 17:40:38 -0400 (EDT) From: Brian Feldman To: Julian Elischer cc: Bill Fenner , current@FreeBSD.ORG Subject: Re: State of current... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yes, this was the exact problem. The atomic = 1; assignment caused quite a large amount of breakage, mainly with X geometry calls, etc. using localhost:0.0, I.E. using tcp port 6000 for communication rather than the /tmp X11 socket. I am still experiencing intermittent complaints from WindowMaker of the same vein as those reported for other apps, however WindowMaker doesn't seem to crash at all, and seems to be the only program still exhibiting problems. Will investigate more.... Brian Feldman green@zone.baldcom.net On Sat, 18 Jul 1998, Julian Elischer wrote: > bill, I saw mail that said that the problem went away if DISPLAY was > specified with localhost:0.0 instead of :0.0 > > I BELIEVE that this indicates that what was broken was unix domain > sockets. (but I may be wrong) > > > julian > > On Sat, 18 Jul 1998, Bill Fenner wrote: > > > I backed out the fix. Does anyone have a test case that would > > reliably fail, so that I can try to figure out exactly what was > > going on? My testing didn't unveil any problems. > > > > Thanks, > > Bill > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 18 18:38:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA19179 for freebsd-current-outgoing; Sat, 18 Jul 1998 18:38:31 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA19174 for ; Sat, 18 Jul 1998 18:38:23 -0700 (PDT) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.8.8/8.8.8) id DAA22125 for freebsd-current@FreeBSD.ORG; Sun, 19 Jul 1998 03:37:53 +0200 (CEST) (envelope-from olli) Date: Sun, 19 Jul 1998 03:37:53 +0200 (CEST) From: Oliver Fromme Message-Id: <199807190137.DAA22125@dorifer.heim3.tu-clausthal.de> To: freebsd-current@FreeBSD.ORG Subject: Re: Make release fails because kernel is too large Newsgroups: list.freebsd-current Organization: Administration Heim 3 Reply-To: freebsd-current@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: TIN [version 1.2 RZTUC(3) PL2] Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Snob Art Genre writes: > > On Thu, 16 Jul 1998, Scot W. Hetzel wrote: > > > > > What about using 1.68 or 1.72 MB floppies? > > > > I think that this would drastically reduce the amount of > > FreeBSD-friendly hardware out there. > > Yes, but don't Microsoft do similiar sorts of things with the Win95 > boot floppies? I know that doesn't grant a right to do so by God, but > it's a fairly clear idea of how much hardware *does* support it. I have to agree with Jordan's "no". Only a few (modern) BIOS versions are able to read and boot from non-standard floppy formats (> 18 sectors/track). Many older BIOS versions don't support this. As far as Win95 floppies are concerned: The boot floppy has a standard 1440 kb format, but the remaining floppies have non-standard formats. This is safe, because they're read by Microsoft's own code, not by the BIOS. If the FreeBSD install floppy is split into two, the second one could be 1680 kb, provided that FreeBSD's own floppy driver is used. (1720 kb is a bad idea anyway, because it requires > 80 tracks, which can be a problem with certain no-name floppies or disk drives.) Regards Oliver PS: My 2 cents: I'd prefer to have _one_ install floppy. This is very convenient, especially if there are problems and you have to experiment and boot several times. -- Oliver Fromme, Leibnizstr. 18-61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message