From owner-freebsd-current Sun Jul 19 00:14:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA09847 for freebsd-current-outgoing; Sun, 19 Jul 1998 00:14:24 -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 AAA09842 for ; Sun, 19 Jul 1998 00:14:21 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id QAA00897; Sun, 19 Jul 1998 16:43:49 +0930 (CST) Message-ID: <19980719164349.I435@freebie.lemis.com> Date: Sun, 19 Jul 1998 16:43:49 +0930 From: Greg Lehey To: Rudolf Schreiner , brian@worldcontrol.com Cc: freebsd-current@FreeBSD.ORG Subject: Re: Where is F_LOCK defined? References: <19980715140148.A10804@top.worldcontrol.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from Rudolf Schreiner on Thu, Jul 16, 1998 at 12:25:22AM +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 Thursday, 16 July 1998 at 0:25:22 +0200, Rudolf Schreiner wrote: > 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. lockf(3) was added to -CURRENT about the 8th July. The definitions are in unistd.h. 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 Sun Jul 19 03:16:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA27164 for freebsd-current-outgoing; Sun, 19 Jul 1998 03:16:33 -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 DAA27099 for ; Sun, 19 Jul 1998 03:16:04 -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 MAA16729 for freebsd-current@freebsd.org; Sun, 19 Jul 1998 12:15:08 +0200 (MET DST) Received: (from andreas@localhost) by klemm.gtn.com (8.8.8/8.8.8) id MAA21041; Sun, 19 Jul 1998 12:15:37 +0200 (CEST) (envelope-from andreas) Message-ID: <19980719121537.A20790@klemm.gtn.com> Date: Sun, 19 Jul 1998 12:15:37 +0200 From: Andreas Klemm To: freebsd-current@FreeBSD.ORG Subject: Re: Make release fails because kernel is too large References: <199807190137.DAA22125@dorifer.heim3.tu-clausthal.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199807190137.DAA22125@dorifer.heim3.tu-clausthal.de>; from Oliver Fromme on Sun, Jul 19, 1998 at 03:37:53AM +0200 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 19, 1998 at 03:37:53AM +0200, Oliver Fromme wrote: > 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.) Just my thoughts. -- 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 Sun Jul 19 03:52:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA02249 for freebsd-current-outgoing; Sun, 19 Jul 1998 03:52: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 DAA02244 for ; Sun, 19 Jul 1998 03:52:15 -0700 (PDT) (envelope-from benedict@echonyc.com) Received: from localhost (benedict@localhost) by echonyc.com (8.8.7/8.8.7) with SMTP id GAA25270; Sun, 19 Jul 1998 06:50:45 -0400 (EDT) Date: Sun, 19 Jul 1998 06:50:44 -0400 (EDT) From: Snob Art Genre Reply-To: ben@rosengart.com To: Adrian Penisoara cc: ben@rosengart.com, 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 Sat, 18 Jul 1998, Adrian Penisoara wrote: > On Fri, 17 Jul 1998, Snob Art Genre wrote: > > > > 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) ? I am using the default logging level. > 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 ? Yes. Tonight I discovered that "down" then "dial" does work, it just takes a long time before the dialing begins. 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 Sun Jul 19 03:56:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA02529 for freebsd-current-outgoing; Sun, 19 Jul 1998 03:56:28 -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 DAA02514 for ; Sun, 19 Jul 1998 03:56:23 -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 MAA15550; Sun, 19 Jul 1998 12:47:11 +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 LAA08194; Sun, 19 Jul 1998 11:50:10 +0200 (CEST) (envelope-from seggers@semyam.dinoco.de) Message-Id: <199807190950.LAA08194@semyam.dinoco.de> To: "Scot W. Hetzel" cc: current@FreeBSD.ORG, seggers@semyam.dinoco.de 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: Sun, 19 Jul 1998 11:50:09 +0200 From: Stefan Eggers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > What about using 1.68 or 1.72 MB floppies? > > FDformat can make these kinds of disks for DOS systems How do I create such a floppy on a Unix type system which has dd, can handle standard HD disks but isn't able to format such a beast? One might want to do this to install a system via FTP w/o having Dos. The initial install floppy one can create on such a Unix type system for example and do the rest at home. 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 Sun Jul 19 05:42:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA11546 for freebsd-current-outgoing; Sun, 19 Jul 1998 05:42:56 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA11540 for ; Sun, 19 Jul 1998 05:42:53 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from gate.lan.awfulhak.org (brian@localhost [127.0.0.1]) by awfulhak.org (8.8.8/8.8.8) with ESMTP id NAA05560; Sun, 19 Jul 1998 13:30:47 +0100 (BST) (envelope-from brian@gate.lan.awfulhak.org) Message-Id: <199807191230.NAA05560@awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: Adrian Penisoara cc: Adam McDougall , current@FreeBSD.ORG Subject: Re: ppp problems In-reply-to: Your message of "Sat, 18 Jul 1998 00:26:17 +0300." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 19 Jul 1998 13:30:47 +0100 From: Brian Somers 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.)? See my followup to the first post - check ``show mem'' and ``show timer'' to see how things really are - and enable tcp/ip logging. I believe the timer problem to be fixed now, but I'm not convinced :-( > Thanks, > Ady (@freebsd.ady.ro) -- Brian , , Don't _EVER_ lose your sense of humour.... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 19 05:42:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA11564 for freebsd-current-outgoing; Sun, 19 Jul 1998 05:42:58 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA11541 for ; Sun, 19 Jul 1998 05:42:54 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from gate.lan.awfulhak.org (brian@localhost [127.0.0.1]) by awfulhak.org (8.8.8/8.8.8) with ESMTP id NAA05538; Sun, 19 Jul 1998 13:27:00 +0100 (BST) (envelope-from brian@gate.lan.awfulhak.org) Message-Id: <199807191227.NAA05538@awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: Adrian Penisoara cc: Adam McDougall , current@FreeBSD.ORG Subject: Re: ppp problems In-reply-to: Your message of "Fri, 17 Jul 1998 22:42:23 +0300." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 19 Jul 1998 13:26:59 +0100 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [.....] > 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 > ------------------------------------------------------------------------- [.....] This is almost definitely a problem with the older versions of ppp - or maybe even older deflate libraries. I haven't seen this happen for some time with the latest ppp in -current. You should probably upgrade ppp on the non-current machines. > Thank you, > Ady (@freebsd.ady.ro) -- Brian , , Don't _EVER_ lose your sense of humour.... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 19 05:43:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA11678 for freebsd-current-outgoing; Sun, 19 Jul 1998 05:43:19 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA11657 for ; Sun, 19 Jul 1998 05:43:13 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from gate.lan.awfulhak.org (brian@localhost [127.0.0.1]) by awfulhak.org (8.8.8/8.8.8) with ESMTP id NAA04615; Sun, 19 Jul 1998 13:00:59 +0100 (BST) (envelope-from brian@gate.lan.awfulhak.org) Message-Id: <199807191200.NAA04615@awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: Bruce Evans cc: jak@cetlink.net, freebsd-current@FreeBSD.ORG Subject: Re: tickadj -t not changing tick In-reply-to: Your message of "Wed, 15 Jul 1998 13:30:29 +1000." <199807150330.NAA22646@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 19 Jul 1998 13:00:58 +0100 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [.....] > 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. Hmm, I have a timer problem with a Compaq Presario (notebook). It seems that the timer chip (i8254 is the only one probed) is acting a big strangely and returning ``past'' times - this is disastrous at the start of a programs life as it tends to exceed the maximum runtime (all set correctly to infinity in login.conf) and result in a sig 24. I don't know if anyone's interested in figuring out what may be the problem, I'm at a bit of a loss. This is what I've found out so far: The laptop: : FreeBSD 3.0-CURRENT #10: Tue Jul 14 10:02:00 BST 1998 : brian@woof.lan.awfulhak.org:/usr/src/sys/compile/WOOF : Timecounter "i8254" frequency 1193182 Hz cost 1296 ns : CPU: Cyrix GXm (17.09-MHz 586-class CPU) : Origin = "CyrixInstead" Id = 0x540 Stepping=0 DIR=0x3346 : Features=0x808131 : real memory = 33554432 (32768K bytes) : avail memory = 30597120 (29880K bytes) This is *really* a 233MHz chip. I did the following: : diff -u -r1.60 kern_synch.c : --- kern_synch.c 1998/07/11 13:06:41 1.60 : +++ kern_synch.c 1998/07/14 00:18:55 : @@ -642,6 +642,9 @@ : */ : if (p->p_stat != SZOMB && p->p_runtime > p->p_limit->p_cpulimit) { : rlim = &p->p_rlimit[RLIMIT_CPU]; : +#if 1 : + printf("(%ld - %ld) + (%ld - %ld) * 1000000\n", switchtime.tv_usec, p->p_switchtime.tv_usec, switchtime.tv_sec, p->p_switchtime.tv_sec); : +#else : if (p->p_runtime / (rlim_t)1000000 >= rlim->rlim_max) { : killproc(p, "exceeded maximum CPU limit"); : } else { : @@ -651,6 +654,7 @@ : rlim->rlim_cur += 5; : } : } : +#endif : } : : /* and now get the following diagnostics: : (109003 - 117991) + (48301 - 48301) * 1000000 : (113819 - 110145) + (48301 - 48301) * 1000000 : calcru: negative time of -882 usec for pid 23835 (sh) : (242041 - 249374) + (48342 - 48342) * 1000000 : (246223 - 242900) + (48342 - 48342) * 1000000 : (247569 - 247149) + (48342 - 48342) * 1000000 : calcru: negative time of -7489 usec for pid 24361 (test) : calcru: negative time of -6684 usec for pid 24629 (rm) : (561792 - 568752) + (48430 - 48430) * 1000000 : (568400 - 563267) + (48430 - 48430) * 1000000 : (272816 - 277721) + (48553 - 48553) * 1000000 : (785726 - 792859) + (48571 - 48571) * 1000000 Any suggestions anyone ? TIA. > Bruce -- Brian , , Don't _EVER_ lose your sense of humour.... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 19 05:52:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA12770 for freebsd-current-outgoing; Sun, 19 Jul 1998 05:52:48 -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 FAA12730 for ; Sun, 19 Jul 1998 05:52:25 -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 PAA04778; Sun, 19 Jul 1998 15:49:27 +0300 (EEST) (envelope-from ady@warpnet.ro) Date: Sun, 19 Jul 1998 15:49:27 +0300 (EEST) From: Adrian Penisoara To: Brian Somers cc: Adam McDougall , current@FreeBSD.ORG Subject: Re: ppp problems In-Reply-To: <199807191227.NAA05538@awfulhak.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 Hi, On Sun, 19 Jul 1998, Brian Somers wrote: > > --[ /var/log/ppp.log extract ]------------------------------------------- > > Jul 12 21:45:56 ady ppp[6854]: tun2: Warning: CCP: Incorrect ResetAck (id > > 2, not 3) ignored > > ------------------------------------------------------------------------- > [.....] > > This is almost definitely a problem with the older versions of ppp - > or maybe even older deflate libraries. I haven't seen this happen > for some time with the latest ppp in -current. > > You should probably upgrade ppp on the non-current machines. Do I stand any chance to manually upgrade (by patching and recompiling only the ppp sources, for every platform) to one of the current versions ? > -- > Brian , , > > Don't _EVER_ lose your sense of humour.... > 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 Sun Jul 19 09:13:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA25820 for freebsd-current-outgoing; Sun, 19 Jul 1998 09:13:28 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ix.netcom.com (sil-wa2-19.ix.netcom.com [206.214.137.51]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA25815 for ; Sun, 19 Jul 1998 09:13:25 -0700 (PDT) (envelope-from tomdean@ix.netcom.com) Received: (from tomdean@localhost) by ix.netcom.com (8.8.8/8.8.8) id JAA00683; Sun, 19 Jul 1998 09:13:14 -0700 (PDT) (envelope-from tomdean) Date: Sun, 19 Jul 1998 09:13:14 -0700 (PDT) Message-Id: <199807191613.JAA00683@ix.netcom.com> From: Thomas Dean To: current@FreeBSD.ORG Subject: Syntax Problem with i386/i386/autoconf.c Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Around line 400 of i386/i386/autoconf.c: static int setdumpdev(dev) dev_t dev; { int maj, psize; long newdumplo; if (dev == NODEV) { B dumpdev = dev; return (0); } Removing the 'B' allowed a kernel build. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 19 09:45:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA28774 for freebsd-current-outgoing; Sun, 19 Jul 1998 09:45:08 -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 JAA28769 for ; Sun, 19 Jul 1998 09:45:07 -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 JAA16689; Sun, 19 Jul 1998 09:43:52 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: Thomas Dean cc: current@FreeBSD.ORG Subject: Re: Syntax Problem with i386/i386/autoconf.c In-reply-to: Your message of "Sun, 19 Jul 1998 09:13:14 PDT." <199807191613.JAA00683@ix.netcom.com> Date: Sun, 19 Jul 1998 09:43:52 -0700 Message-ID: <16685.900866632@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Already found and fixed last night - please re-cvsup. > Around line 400 of i386/i386/autoconf.c: > > static int > setdumpdev(dev) > dev_t dev; > { > int maj, psize; > long newdumplo; > > if (dev == NODEV) { > B > dumpdev = dev; > return (0); > } > > Removing the 'B' allowed a kernel build. > > 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 Sun Jul 19 12:01:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA08708 for freebsd-current-outgoing; Sun, 19 Jul 1998 12:01:04 -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 MAA08703 for ; Sun, 19 Jul 1998 12:01:02 -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 VAA02526; Sun, 19 Jul 1998 21:00:36 +0200 (MET DST) Received: (from dag-erli@localhost) by hrotti.ifi.uio.no ; Sun, 19 Jul 1998 21:00:36 +0200 (MET DST) Mime-Version: 1.0 To: Andreas Klemm Cc: Brandon Lockhart , freebsd-current@FreeBSD.ORG Subject: Re: engulf weekly run output (fwd) References: <19980718164859.B13033@klemm.gtn.com> 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: 19 Jul 1998 21:00:35 +0200 In-Reply-To: Andreas Klemm's message of "Sat, 18 Jul 1998 16:48:59 +0200" Message-ID: Lines: 17 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andreas Klemm writes: > ( 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 Ouch. The output of make buildworld easily reaches 4 MB. I do: log=/var/log/make.`/bin/date '+%Y%m%d'` exec $log 2>&1 [...] make buildworld [...] 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 Sun Jul 19 13:07:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA15473 for freebsd-current-outgoing; Sun, 19 Jul 1998 13:07:20 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA15466 for ; Sun, 19 Jul 1998 13:07:13 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from gate.lan.awfulhak.org (brian@localhost [127.0.0.1]) by awfulhak.org (8.8.8/8.8.8) with ESMTP id NAA05241; Sun, 19 Jul 1998 13:24:11 +0100 (BST) (envelope-from brian@gate.lan.awfulhak.org) Message-Id: <199807191224.NAA05241@awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: ben@rosengart.com cc: current@FreeBSD.ORG Subject: Re: ppp problems In-reply-to: Your message of "Thu, 16 Jul 1998 18:25:20 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 19 Jul 1998 13:24:11 +0100 From: Brian Somers 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. If you ``show timer'' a few times, are the times changing ? What about enabling tcp diagnostics (set log [local] +tcp/ip) ? Is ppp trying to send stuff out and is it receiving stuff ? Another interesting piece of output is ``show mem'' - you can see how many internal mbufs are currently allocated. > Ben > > "You have your mind on computers, it seems." -- Brian , , Don't _EVER_ lose your sense of humour.... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 19 14:09:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA22304 for freebsd-current-outgoing; Sun, 19 Jul 1998 14:09:30 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA22271 for ; Sun, 19 Jul 1998 14:09:21 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from gate.lan.awfulhak.org (brian@localhost [127.0.0.1]) by awfulhak.org (8.8.8/8.8.8) with ESMTP id WAA22217; Sun, 19 Jul 1998 22:08:26 +0100 (BST) (envelope-from brian@gate.lan.awfulhak.org) Message-Id: <199807192108.WAA22217@awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: Adrian Penisoara cc: Brian Somers , Adam McDougall , current@FreeBSD.ORG Subject: Re: ppp problems In-reply-to: Your message of "Sun, 19 Jul 1998 15:49:27 +0300." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 19 Jul 1998 22:08:26 +0100 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG You can get a buildable ppp archive via http://www.Awfulhak.org/ppp.html > Hi, > > On Sun, 19 Jul 1998, Brian Somers wrote: > > > > --[ /var/log/ppp.log extract ]------------------------------------------- > > > Jul 12 21:45:56 ady ppp[6854]: tun2: Warning: CCP: Incorrect ResetAck (id > > > 2, not 3) ignored > > > ------------------------------------------------------------------------- > > [.....] > > > > This is almost definitely a problem with the older versions of ppp - > > or maybe even older deflate libraries. I haven't seen this happen > > for some time with the latest ppp in -current. > > > > You should probably upgrade ppp on the non-current machines. > > Do I stand any chance to manually upgrade (by patching and recompiling > only the ppp sources, for every platform) to one of the current versions ? > > > -- > > Brian , , > > > > Don't _EVER_ lose your sense of humour.... > > > > 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 Sun Jul 19 14:37:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA25380 for freebsd-current-outgoing; Sun, 19 Jul 1998 14:37:55 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from Octopussy.MI.Uni-Koeln.DE (Octopussy.MI.Uni-Koeln.DE [134.95.166.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA25371; Sun, 19 Jul 1998 14:37:46 -0700 (PDT) (envelope-from se@dialup124.zpr.uni-koeln.de) Received: from dialup124.zpr.Uni-Koeln.DE (dialup124.zpr.Uni-Koeln.DE [134.95.219.124]) by Octopussy.MI.Uni-Koeln.DE (8.8.8/8.8.8) with ESMTP id XAA07532; Sun, 19 Jul 1998 23:36:43 +0200 (MET DST) Received: (from se@localhost) by dialup124.zpr.Uni-Koeln.DE (8.8.8/8.6.9) id WAA25335; Sun, 19 Jul 1998 22:25:26 +0200 (CEST) X-Face: " Date: Sun, 19 Jul 1998 22:25:26 +0200 From: Stefan Esser To: Chris Dillon Cc: Julian Elischer , current@FreeBSD.ORG, Stefan Esser Subject: Re: TESTERS NEEDED: Softupdates looks Very good. Mail-Followup-To: Chris Dillon , Julian Elischer , current@freebsd.org References: <19980711105643.41001@mi.uni-koeln.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93i In-Reply-To: ; from Chris Dillon on Sun, Jul 12, 1998 at 05:30:13PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 1998-07-12 17:30 -0500, Chris Dillon wrote: > > 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? It doesn't really matter. The IBM driver have other annoying firmware features (e.g. can't deal with a "start motor" command in certain situation where it could be considered a NOP), and they sometimes drop the number of tagged commands they can deal with for no apparent reason. But I'm still thinking that the DDRS is a rather good buy, currently ;-) Regards, STefan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 19 16:22:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA09762 for freebsd-current-outgoing; Sun, 19 Jul 1998 16:22:12 -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 QAA09662; Sun, 19 Jul 1998 16:21:45 -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 SAA18756; Sun, 19 Jul 1998 18:21:30 -0500 (CDT) (envelope-from cdillon@wolves.k12.mo.us) Date: Sun, 19 Jul 1998 18:21:29 -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: <19980719222526.A25289@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 Sun, 19 Jul 1998, Stefan Esser wrote: > On 1998-07-12 17:30 -0500, Chris Dillon wrote: > > > 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? > > It doesn't really matter. The IBM driver have > other annoying firmware features (e.g. can't > deal with a "start motor" command in certain > situation where it could be considered a NOP), > and they sometimes drop the number of tagged > commands they can deal with for no apparent > reason. But I'm still thinking that the DDRS > is a rather good buy, currently ;-) I thought that tag problem was only with certain Quantum drives. :-) Well, these are DCAS drives, and have worked without a single hitch so far, but I wouldn't exactly say I put them under any major stress. Knock on wood. -- 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 19 23:03:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA00423 for freebsd-current-outgoing; Sun, 19 Jul 1998 23:03:57 -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 XAA00418 for ; Sun, 19 Jul 1998 23:03:54 -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 QAA15267; Mon, 20 Jul 1998 16:03:16 +1000 Date: Mon, 20 Jul 1998 16:03:16 +1000 From: Bruce Evans Message-Id: <199807200603.QAA15267@godzilla.zeta.org.au> To: bde@zeta.org.au, brian@Awfulhak.org Subject: Re: tickadj -t not changing tick Cc: freebsd-current@FreeBSD.ORG, jak@cetlink.net Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Hmm, I have a timer problem with a Compaq Presario (notebook). It >seems that the timer chip (i8254 is the only one probed) is acting a >big strangely and returning ``past'' times - this is disastrous at >the start of a programs life as it tends to exceed the maximum >runtime (all set correctly to infinity in login.conf) and result in a >sig 24. It can't be a problem with the i8254 hardware, because the i8254 timecounter never goes backwards (if the hardware goes backwards, then the timecounter jumps forwards). >The laptop: > >: FreeBSD 3.0-CURRENT #10: Tue Jul 14 10:02:00 BST 1998 >: brian@woof.lan.awfulhak.org:/usr/src/sys/compile/WOOF >: Timecounter "i8254" frequency 1193182 Hz cost 1296 ns >: CPU: Cyrix GXm (17.09-MHz 586-class CPU) >: Origin = "CyrixInstead" Id = 0x540 Stepping=0 DIR=0x3346 >: Features=0x808131 >: real memory = 33554432 (32768K bytes) >: avail memory = 30597120 (29880K bytes) > >This is *really* a 233MHz chip. APM seems to be preventing use of the TSC timecounter. Otherwise the clock would go non-backwards 233/17 faster :-). 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 19 23:43:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA03659 for freebsd-current-outgoing; Sun, 19 Jul 1998 23:43:05 -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 XAA03654 for ; Sun, 19 Jul 1998 23:43:02 -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 QAA17899; Mon, 20 Jul 1998 16:42:39 +1000 Date: Mon, 20 Jul 1998 16:42:39 +1000 From: Bruce Evans Message-Id: <199807200642.QAA17899@godzilla.zeta.org.au> To: bde@zeta.org.au, brian@Awfulhak.org Subject: Re: tickadj -t not changing tick Cc: freebsd-current@FreeBSD.ORG, jak@cetlink.net Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >APM seems to be preventing use of the TSC timecounter. Otherwise >the clock would go non-backwards 233/17 faster :-). The whole problem may be caused by APM. APM's time handling is of low quality. Among other bugs, it assumes that inittodr() has a resolution of about 1 usec. inittodr() actually has a resolution of about 1 second, so the time may be set wrong by up to +- 1 second after even a short suspension. This may cause the time to go backwards if the suspension period is shorter than 1 second. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 20 07:20:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA11847 for freebsd-current-outgoing; Mon, 20 Jul 1998 07:20:20 -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 HAA11830 for ; Mon, 20 Jul 1998 07:20:17 -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 QAA11183; Mon, 20 Jul 1998 16:18:35 +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 MAA07091; Mon, 20 Jul 1998 12:10:48 +0200 (CEST) (envelope-from seggers@semyam.dinoco.de) Message-Id: <199807201010.MAA07091@semyam.dinoco.de> To: Henry Vogt cc: current@FreeBSD.ORG, seggers@semyam.dinoco.de 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> Date: Mon, 20 Jul 1998 12:10:47 +0200 From: Stefan Eggers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > 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 ?) As far as I know :0.0 uses a Unix domain socket under /tmp while the latter form uses TCP/IP. It only could be shared memory (used by some X protocol extension as far as I know) if the client only tries to use it with a DISPLAY set- ting not including a hostname. I'd have to look up details to know more about this. The bug in questions seems to have something to do with the Unix domain sockets as backing out one of the changes was said to make it work normal again. That is consistent with the difference in the working and non-working DISPLAY settings. 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 Mon Jul 20 08:49:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA21892 for freebsd-current-outgoing; Mon, 20 Jul 1998 08:49:22 -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 IAA21886 for ; Mon, 20 Jul 1998 08:49:17 -0700 (PDT) (envelope-from benedict@echonyc.com) Received: from localhost (benedict@localhost) by echonyc.com (8.8.7/8.8.7) with SMTP id LAA15273 for ; Mon, 20 Jul 1998 11:49:00 -0400 (EDT) Date: Mon, 20 Jul 1998 11:48:59 -0400 (EDT) From: Snob Art Genre Reply-To: ben@rosengart.com To: current@FreeBSD.ORG Subject: keyboard lights 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 Every once in a while, all three of my keyboard lights flash at the same time. I've only noticed this in X, but I'm almost always running X, so that doesn't necessarily mean much. What is this? 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 20 10:47:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA10361 for freebsd-current-outgoing; Mon, 20 Jul 1998 10:47:47 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA10356 for ; Mon, 20 Jul 1998 10:47:46 -0700 (PDT) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id KAA04891; Mon, 20 Jul 1998 10:47:00 -0700 (PDT) Received: from bubba.whistle.com(207.76.205.7) by whistle.com via smap (V1.3) id sma004889; Mon Jul 20 10:46:51 1998 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id KAA15551; Mon, 20 Jul 1998 10:46:51 -0700 (PDT) From: Archie Cobbs Message-Id: <199807201746.KAA15551@bubba.whistle.com> Subject: Re: keyboard lights In-Reply-To: from Snob Art Genre at "Jul 20, 98 11:48:59 am" To: ben@rosengart.com Date: Mon, 20 Jul 1998 10:46:51 -0700 (PDT) Cc: current@FreeBSD.ORG 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 Snob Art Genre writes: > Every once in a while, all three of my keyboard lights flash at the same > time. > > I've only noticed this in X, but I'm almost always running X, so that > doesn't necessarily mean much. > > What is this? Do you have a flakey connection between the keyboard and your computer (eg, loose cable)? This could cause it. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.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 20 10:52:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA11572 for freebsd-current-outgoing; Mon, 20 Jul 1998 10:52: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 KAA11563 for ; Mon, 20 Jul 1998 10:52:14 -0700 (PDT) (envelope-from benedict@echonyc.com) Received: from localhost (benedict@localhost) by echonyc.com (8.8.7/8.8.7) with SMTP id NAA19551; Mon, 20 Jul 1998 13:51:55 -0400 (EDT) Date: Mon, 20 Jul 1998 13:51:54 -0400 (EDT) From: Snob Art Genre Reply-To: ben@rosengart.com To: Archie Cobbs cc: current@FreeBSD.ORG Subject: Re: keyboard lights In-Reply-To: <199807201746.KAA15551@bubba.whistle.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, 20 Jul 1998, Archie Cobbs wrote: > Do you have a flakey connection between the keyboard and your > computer (eg, loose cable)? This could cause it. I don't think so. My keystrokes always go through, and I just felt the connector and it seemed pretty solid. 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 20 15:18:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA25671 for freebsd-current-outgoing; Mon, 20 Jul 1998 15:18:24 -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 PAA25655 for ; Mon, 20 Jul 1998 15:18:22 -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 RAA12544; Mon, 20 Jul 1998 17:18:30 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.8.8/8.8.8) id RAA00950; Mon, 20 Jul 1998 17:17:33 -0500 (CDT) (envelope-from joelh) Date: Mon, 20 Jul 1998 17:17:33 -0500 (CDT) Message-Id: <199807202217.RAA00950@detlev.UUCP> To: freebsd-current@FreeBSD.ORG Subject: vn subsystem From: Joel Ray Holveck Reply-to: joelh@gnu.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is vnode support operational? It's hung my system when I've tried to use it lately. 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 Mon Jul 20 15:53:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA05279 for freebsd-current-outgoing; Mon, 20 Jul 1998 15:53:27 -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 PAA05272 for ; Mon, 20 Jul 1998 15:53:23 -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 SAA01602; Mon, 20 Jul 1998 18:53:15 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.ny.otec.com: bright owned process doing -bs Date: Mon, 20 Jul 1998 18:53:15 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.ny.otec.com To: Joel Ray Holveck cc: freebsd-current@FreeBSD.ORG Subject: Re: vn subsystem In-Reply-To: <199807202217.RAA00950@detlev.UUCP> 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 no, it's been broken for some time now. -Alfred On Mon, 20 Jul 1998, Joel Ray Holveck wrote: > Is vnode support operational? It's hung my system when I've tried to > use it lately. > > 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 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 20 16:15:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA10684 for freebsd-current-outgoing; Mon, 20 Jul 1998 16:15:36 -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 QAA10668 for ; Mon, 20 Jul 1998 16:15:32 -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 SAA15960; Mon, 20 Jul 1998 18:16:02 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.8.8/8.8.8) id SAA04506; Mon, 20 Jul 1998 18:15:03 -0500 (CDT) (envelope-from joelh) Date: Mon, 20 Jul 1998 18:15:03 -0500 (CDT) Message-Id: <199807202315.SAA04506@detlev.UUCP> To: bright@hotjobs.com CC: freebsd-current@FreeBSD.ORG In-reply-to: (message from Alfred Perlstein on Mon, 20 Jul 1998 18:53:15 -0500 (EST)) Subject: Re: vn subsystem From: Joel Ray Holveck Reply-to: joelh@gnu.org References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> Is vnode support operational? It's hung my system when I've tried to >> use it lately. > no, it's been broken for some time now. Do we know what is broken about it? If it is not a huge affair, I need to fix it quickly. 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 Mon Jul 20 16:33:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA15673 for freebsd-current-outgoing; Mon, 20 Jul 1998 16:33:09 -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 QAA15662 for ; Mon, 20 Jul 1998 16:33:07 -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 TAA20835; Mon, 20 Jul 1998 19:33:00 -0400 (EDT) Date: Mon, 20 Jul 1998 19:32:59 -0400 (EDT) From: Brian Feldman To: Alfred Perlstein cc: Joel Ray Holveck , freebsd-current@FreeBSD.ORG Subject: Re: vn subsystem 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 Seems to work "somewhat" okay for me, problems being, that doscmd and newfs_msdos can't seem to agree on the format of my msdos.drv (/dev/vn0); so when I newfs_msdos it I can then mount and use it, but I have to reformat it in doscmd so I can use it in DOS. I get strange errors when I try to do either with the wrong formatted drive. Brian Feldman On Mon, 20 Jul 1998, Alfred Perlstein wrote: > no, it's been broken for some time now. > > -Alfred > > On Mon, 20 Jul 1998, Joel Ray Holveck wrote: > > > Is vnode support operational? It's hung my system when I've tried to > > use it lately. > > > > 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 > > > > > 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 20 17:14:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA26603 for freebsd-current-outgoing; Mon, 20 Jul 1998 17:14:28 -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 RAA26591 for ; Mon, 20 Jul 1998 17:14:23 -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 RAA26379; Mon, 20 Jul 1998 17:13:07 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: Alfred Perlstein cc: Joel Ray Holveck , freebsd-current@FreeBSD.ORG Subject: Re: vn subsystem In-reply-to: Your message of "Mon, 20 Jul 1998 18:53:15 CDT." Date: Mon, 20 Jul 1998 17:13:06 -0700 Message-ID: <26376.900979986@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Works for me" I'd not be able to build 3.0 snapshots at all if it were broken. - Jordan > no, it's been broken for some time now. > > -Alfred > > On Mon, 20 Jul 1998, Joel Ray Holveck wrote: > > > Is vnode support operational? It's hung my system when I've tried to > > use it lately. > > > > 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 > > > > > 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 20 18:29:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA10172 for freebsd-current-outgoing; Mon, 20 Jul 1998 18:29:11 -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 SAA10166 for ; Mon, 20 Jul 1998 18:29:08 -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 VAA02324; Mon, 20 Jul 1998 21:29:08 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.ny.otec.com: bright owned process doing -bs Date: Mon, 20 Jul 1998 21:29:08 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.ny.otec.com To: Joel Ray Holveck cc: freebsd-current@FreeBSD.ORG Subject: Re: vn subsystem In-Reply-To: <199807202315.SAA04506@detlev.UUCP> 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, not really there was some traffic on the lists a few weeks/months back about it being broken, but that's all i know. -Alfred On Mon, 20 Jul 1998, Joel Ray Holveck wrote: > >> Is vnode support operational? It's hung my system when I've tried to > >> use it lately. > > no, it's been broken for some time now. > > Do we know what is broken about it? If it is not a huge affair, I > need to fix it quickly. > > 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 Mon Jul 20 18:30:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA10519 for freebsd-current-outgoing; Mon, 20 Jul 1998 18:30:15 -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 SAA10509 for ; Mon, 20 Jul 1998 18:30:12 -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 VAA02331; Mon, 20 Jul 1998 21:30:05 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.ny.otec.com: bright owned process doing -bs Date: Mon, 20 Jul 1998 21:30:05 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.ny.otec.com To: "Jordan K. Hubbard" cc: freebsd-current@FreeBSD.ORG Subject: Re: vn subsystem In-Reply-To: <26376.900979986@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 i'm sorry, afaik it'll compile, but it's not stable -Alfred On Mon, 20 Jul 1998, Jordan K. Hubbard wrote: > "Works for me" > > I'd not be able to build 3.0 snapshots at all if it were broken. > > - Jordan > > > no, it's been broken for some time now. > > > > -Alfred > > > > On Mon, 20 Jul 1998, Joel Ray Holveck wrote: > > > > > Is vnode support operational? It's hung my system when I've tried to > > > use it lately. > > > > > > 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 > > > > > > > > > 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 20 18:38:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA11927 for freebsd-current-outgoing; Mon, 20 Jul 1998 18:38:43 -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 SAA11922 for ; Mon, 20 Jul 1998 18:38:38 -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 SAA26846; Mon, 20 Jul 1998 18:37:25 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: Alfred Perlstein cc: freebsd-current@FreeBSD.ORG Subject: Re: vn subsystem In-reply-to: Your message of "Mon, 20 Jul 1998 21:30:05 CDT." Date: Mon, 20 Jul 1998 18:37:24 -0700 Message-ID: <26843.900985044@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG And making content-free statements like that don't help anyone. You need to give DETAILS before you say stuff like "it's broken" or "it's not stable" and you need to have shown that you've properly exonerated other factors before setting the blame squarely on vn's doorstep. Where is your data? This is not IRC, Alfred. We have to actaully *back up* some of the things we say in the mailing lists. :-) - Jordan > i'm sorry, afaik it'll compile, but it's not stable > > -Alfred > > On Mon, 20 Jul 1998, Jordan K. Hubbard wrote: > > > "Works for me" > > > > I'd not be able to build 3.0 snapshots at all if it were broken. > > > > - Jordan > > > > > no, it's been broken for some time now. > > > > > > -Alfred > > > > > > On Mon, 20 Jul 1998, Joel Ray Holveck wrote: > > > > > > > Is vnode support operational? It's hung my system when I've tried to > > > > use it lately. > > > > > > > > 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 > > > > > > > > > > > > > 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 20 18:45:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA13343 for freebsd-current-outgoing; Mon, 20 Jul 1998 18:45:05 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from thelab.hub.org (tc-22.acadiau.ca [131.162.2.122]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA13316; Mon, 20 Jul 1998 18:45:01 -0700 (PDT) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.8.8/8.8.2) with SMTP id WAA15734; Mon, 20 Jul 1998 22:46:41 -0300 (ADT) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Mon, 20 Jul 1998 22:46:40 -0300 (ADT) From: The Hermit Hacker To: freebsd-multimedia@FreeBSD.ORG cc: freebsd-current@FreeBSD.ORG Subject: cdrecord with 3.0-CURRENT ... 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... Can someone tell me what this error means, when I'm trying to write to my CDR? %cdrecord -v blank=all Cdrecord release 1.6 Copyright (C) 1995-1998 Jrg Schilling TOC Type: 1 = CD-ROM cdrecord: Function not implemented. WARNING: Cannot set RR-scheduler scsidev: '0,6,0' scsibus: 0 target: 6 lun: 0 cdrecord: Cannot do inquiry for CD-Recorder. cdrecord: Undefined error: 0. test unit ready: scsi sendcmd: fatal error CDB: 00 00 00 00 00 00 cmd finished after 0.000s timeout 40s I'm getting the following in /var/log/messages (and dmesg): cmd cdrecord pid 15594 tried to use non-present sched_get_priority_max cmd cdrecord pid 15594 tried to use non-present sched_setscheduler cdrecord did work before my last upgrade, with this same drive, which is why I'm asking on -current also... Still investigating at this end...new kernel as of July 16th... Marc G. Fournier Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.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 20 20:35:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA29819 for freebsd-current-outgoing; Mon, 20 Jul 1998 20:35: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 UAA29804 for ; Mon, 20 Jul 1998 20:35:04 -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 UAA27160; Mon, 20 Jul 1998 20:33:40 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: Alfred Perlstein cc: Joel Ray Holveck , freebsd-current@FreeBSD.ORG Subject: Re: vn subsystem In-reply-to: Your message of "Mon, 20 Jul 1998 21:29:08 CDT." Date: Mon, 20 Jul 1998 20:33:39 -0700 Message-ID: <27156.900992019@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > hrm, not really there was some traffic on the lists a few weeks/months > back about it being broken, but that's all i know. Erm, wonderful. Can we have some commentary from someone who's actually proven this either way now? Like I said, my own usage of the vn driver has not shown any such instability. If someone who's _actually used it_ can now comment on its instability, we'll get a lot further. - 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 20 22:26:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA16264 for freebsd-current-outgoing; Mon, 20 Jul 1998 22:26:22 -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 WAA16256 for ; Mon, 20 Jul 1998 22:26:19 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-113.camalott.com [208.229.74.113]) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id AAA05331; Tue, 21 Jul 1998 00:26:29 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.8.8/8.8.8) id AAA00857; Tue, 21 Jul 1998 00:25:32 -0500 (CDT) (envelope-from joelh) Date: Tue, 21 Jul 1998 00:25:32 -0500 (CDT) Message-Id: <199807210525.AAA00857@detlev.UUCP> To: jkh@time.cdrom.com CC: bright@hotjobs.com, freebsd-current@FreeBSD.ORG In-reply-to: <26843.900985044@time.cdrom.com> (jkh@time.cdrom.com) Subject: Re: vn subsystem From: Joel Ray Holveck Reply-to: joelh@gnu.org References: <26843.900985044@time.cdrom.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> Is vnode support operational? It's hung my system when I've tried to >>>>> use it lately. >>>> no, it's been broken for some time now. >>> "Works for me" >>> I'd not be able to build 3.0 snapshots at all if it were broken. >> i'm sorry, afaik it'll compile, but it's not stable > And making content-free statements like that don't help anyone. > You need to give DETAILS before you say stuff like "it's broken" or > "it's not stable" and you need to have shown that you've properly > exonerated other factors before setting the blame squarely on vn's > doorstep. Where is your data? This is not IRC, Alfred. We have to > actaully *back up* some of the things we say in the mailing lists. :-) Gentlemen, please! I only wanted to see if it was broken, or if instead I had done something wrong. It turns out to be the latter in my case, so please don't carry this on for my sake. It turns out that this one was pilot error. When I was revising my kernel config file, I had inadvertantly hit DEL and changed "pseudo-device vn 4" to "pseudo-device vn ". (Since that was a while ago, it didn't immediately occur to me to check the kernel config.) I don't know how it compiled, but it did. I don't know how vnconfig and mount both finished successfully, but they did. But when I tried to access the mountpoint, the system froze. Now, that's settled. Alfred, thanks for your information, but I can't be quite tell if this is first-hand or not. If you are using vn and it is failing, please let us know, with enough specifics so that we can pinpoint the problem. Bearing in mind that it may not be reproducable on every platform. Jordan and I, at least, depend on vn. I'm sure some other hackers do as well, so somebody will likely investigate your bug report. (The whole ounce of prevention bit, and all that.) Jordan, thanks for your results; it pointed me away from expected -current instabilities and helped me concentrate on finding the source of the problem. Now, on to another question. This one doesn't affect me, but it's worth asking. Is it just me, or do the vn devices not show up under devfs? (Yes, this is after booting from a corrected kernel.) 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 Mon Jul 20 23:33:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA24880 for freebsd-current-outgoing; Mon, 20 Jul 1998 23:33:14 -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 XAA24873 for ; Mon, 20 Jul 1998 23:33:12 -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 XAA21188; Mon, 20 Jul 1998 23:32:52 -0700 (PDT) (envelope-from skynyrd@opus.cts.cwu.edu) Date: Mon, 20 Jul 1998 23:32:51 -0700 (PDT) From: Chris Timmons To: Joel Ray Holveck cc: freebsd-current@FreeBSD.ORG Subject: Re: vn subsystem In-Reply-To: <199807210525.AAA00857@detlev.UUCP> 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 One vn subsystem bogon that I haven't attempted to reproduce since last summer involved a 2.2-stable system with a BigDisk NFS mounted from a 3.0-current system. 'make release' on the 2.2-stable system into the BigDisk would totally hose the 2.2-stable system to complete catatonia at the instant when the vn stuff executed. Since then, dyson et al fixed a bunch of nfs problems in -current, but it was never clear to me if this was really an NFS problem, or actually related to the vn driver in -stable. Prior to these problems I used to build 2.1.x releases with a BigDisk NFS mounted on then 2.2-current. Anybody doing this recently? -Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 21 00:38:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA00800 for freebsd-current-outgoing; Tue, 21 Jul 1998 00:38:27 -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 AAA00794 for ; Tue, 21 Jul 1998 00:38:25 -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 IAA22264; Tue, 21 Jul 1998 08:39:08 +0100 (BST) Date: Tue, 21 Jul 1998 08:39:08 +0100 (BST) From: Doug Rabson To: "Jordan K. Hubbard" cc: Alfred Perlstein , Joel Ray Holveck , freebsd-current@FreeBSD.ORG Subject: Re: vn subsystem In-Reply-To: <27156.900992019@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, 20 Jul 1998, Jordan K. Hubbard wrote: > > hrm, not really there was some traffic on the lists a few weeks/months > > back about it being broken, but that's all i know. > > Erm, wonderful. Can we have some commentary from someone who's > actually proven this either way now? Like I said, my own usage of the > vn driver has not shown any such instability. If someone who's > _actually used it_ can now comment on its instability, we'll get a lot > further. I was using it on 2.2.5 recently and managed to cause a reboot a couple of times copying large numbers of files into a ufs mounted from a vn device. I kind of assumed that it was a 2.2.x problem and ignored it. I'm afraid I don't even know what the panic message was since the console was in a different room. -- 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 21 00:44:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA02079 for freebsd-current-outgoing; Tue, 21 Jul 1998 00:44:57 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA02074 for ; Tue, 21 Jul 1998 00:44:55 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.5/8.8.8) with SMTP id AAA11338 for ; Tue, 21 Jul 1998 00:44:38 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Tue, 21 Jul 1998 00:44:38 -0700 (PDT) From: Doug White To: current@FreeBSD.ORG Subject: Does building current on 2.2.x still work? 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 Okay, I give up. Can someone send the The Complete Guide to Building -CURRENT on -STABLE? The binary format changes have made a complete mess of things: if ld doesn't die missing ___error (when BINFORMAT=aout), it's the assembler complaining about unknown psuedo-op .section (when BINFORMAT=foo to bypass bsd.own.mk's misassumptions about /usr/lib vs /usr/lib/aout in a 2.2.6-RELEASE universe). Or should I just copy /usr/lib to /usr/lib/aout, provide diffs to /usr/src/Makefile and /etc/make.conf documenting the new magic variables MACHINE_ARCH, BINFORMAT, and the above copying hack, then go back into my hole and be quiet? Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 21 01:24:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA05798 for freebsd-current-outgoing; Tue, 21 Jul 1998 01:24:21 -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 BAA05714 for ; Tue, 21 Jul 1998 01:24:07 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.8/8.8.7) id SAA01524; Tue, 21 Jul 1998 18:41:51 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199807210841.SAA01524@cimlogic.com.au> Subject: Re: Does building current on 2.2.x still work? In-Reply-To: from Doug White at "Jul 21, 98 00:44:38 am" To: dwhite@resnet.uoregon.edu (Doug White) Date: Tue, 21 Jul 1998 18:41:50 +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 Doug White wrote: > Okay, I give up. Can someone send the The Complete Guide to Building > -CURRENT on -STABLE? The binary format changes have made a complete mess > of things: if ld doesn't die missing ___error (when BINFORMAT=aout), it's > the assembler complaining about unknown psuedo-op .section (when > BINFORMAT=foo to bypass bsd.own.mk's misassumptions about /usr/lib vs > /usr/lib/aout in a 2.2.6-RELEASE universe). > > Or should I just copy /usr/lib to /usr/lib/aout, provide diffs to > /usr/src/Makefile and /etc/make.conf documenting the new magic variables > MACHINE_ARCH, BINFORMAT, and the above copying hack, then go back into my > hole and be quiet? Ahem, for the umpteenth time: cd /usr/src make -m /usr/src/share/mk world I'm getting real sick of repeating this. If I edit this into /usr/src/Makefile, do you think people would get the message? -- 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 Tue Jul 21 01:29:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA06634 for freebsd-current-outgoing; Tue, 21 Jul 1998 01:29:40 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from thelab.hub.org (tc-8.acadiau.ca [131.162.2.108]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA06611; Tue, 21 Jul 1998 01:29:32 -0700 (PDT) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.8.8/8.8.2) with SMTP id FAA00309; Tue, 21 Jul 1998 05:28:27 -0300 (ADT) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Tue, 21 Jul 1998 05:28:22 -0300 (ADT) From: The Hermit Hacker To: "Daniel O'Connor" cc: current@FreeBSD.ORG, multimedia@FreeBSD.ORG Subject: Re: cdrecord with 3.0-CURRENT ... In-Reply-To: <199807210250.MAA20783@cain.gsoft.com.au> 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, 21 Jul 1998, Daniel O'Connor wrote: > > > Can someone tell me what this error means, when I'm trying to > > write to my CDR? > > %cdrecord -v blank=all > > Cdrecord release 1.6 Copyright (C) 1995-1998 Jrg Schilling > > TOC Type: 1 = CD-ROM > > cdrecord: Function not implemented. WARNING: Cannot set RR-scheduler > > scsidev: '0,6,0' > > scsibus: 0 target: 6 lun: 0 > > cdrecord: Cannot do inquiry for CD-Recorder. > > cdrecord: Undefined error: 0. test unit ready: scsi sendcmd: fatal error > > CDB: 00 00 00 00 00 00 > > cmd finished after 0.000s timeout 40s > I get this when I don't run as root, but not the 'Function not implemented' > stuff so I suspect its not that :) After doing some peaking around, I figured out what was causing the 'Function not implemented' error message. Seems that newer kernels require the following options to be added, in order for the sched_* set of functions to work... options "P1003_1B" options "_KPOSIX_PRIORITY_SCHEDULING" options "_KPOSIX_VERSION=199309L" cdrecord still doesn't appear to work, but at least I'm one step closer :( I still get the 'Undefined error', even working as root, so if someone can suggest what might have changed in the kernel to cause it to fail, where it once worked, that would be much appreciated... Thanks... Marc G. Fournier Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 21 01:52:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA09230 for freebsd-current-outgoing; Tue, 21 Jul 1998 01:52:20 -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 BAA09225 for ; Tue, 21 Jul 1998 01:52:15 -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 KAA07939; Tue, 21 Jul 1998 10:53:43 +0200 (CEST) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Tue, 21 Jul 1998 10:53:42 +0200 (CEST) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: Doug Rabson cc: "Jordan K. Hubbard" , Alfred Perlstein , Joel Ray Holveck , freebsd-current@FreeBSD.ORG Subject: Re: vn subsystem 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, 21 Jul 1998, Doug Rabson wrote: > On Mon, 20 Jul 1998, Jordan K. Hubbard wrote: > > > > hrm, not really there was some traffic on the lists a few weeks/months > > > back about it being broken, but that's all i know. > > > > Erm, wonderful. Can we have some commentary from someone who's > > actually proven this either way now? Like I said, my own usage of the > > vn driver has not shown any such instability. If someone who's > > _actually used it_ can now comment on its instability, we'll get a lot > > further. > > I was using it on 2.2.5 recently and managed to cause a reboot a couple of I'm using it on regular basis on (relatively) fresh -current. I had one panic a few days ago. I did something stupid then which I don't remember exactly (something like truncating the file which was vnconfig'd), but it *did* panic. It was obviously my mistake, but if you feel it shouldn't lead to panic, I'll try to repeat it and send a stack trace... 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 Tue Jul 21 01:55:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA09582 for freebsd-current-outgoing; Tue, 21 Jul 1998 01:55:18 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from catastrophe.gelemna.ft-wayne.in.us (fw-line-27.fwi.com [209.84.172.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA09524 for ; Tue, 21 Jul 1998 01:55:06 -0700 (PDT) (envelope-from croyle@gelemna.ft-wayne.in.us) Received: from emerson.gelemna.ft-wayne.in.us (emerson.gelemna.ft-wayne.in.us [10.23.42.2]) by catastrophe.gelemna.ft-wayne.in.us (8.8.8/8.8.8) with ESMTP id DAA16445; Tue, 21 Jul 1998 03:54:18 -0500 (EST) (envelope-from croyle@gelemna.ft-wayne.in.us) Received: (from croyle@localhost) by emerson.gelemna.ft-wayne.in.us (8.8.8/8.8.8) id DAA17593; Tue, 21 Jul 1998 03:54:17 -0500 (EST) (envelope-from croyle@gelemna.ft-wayne.in.us) To: Doug White Cc: current@FreeBSD.ORG Subject: Re: Does building current on 2.2.x still work? References: Mime-Version: 1.0 (generated by tm-edit 7.108) Content-Type: text/plain; charset=US-ASCII From: Don Croyle Date: 21 Jul 1998 03:54:17 -0500 Organization: Minimal at best In-Reply-To: Doug White's message of "Tue, 21 Jul 1998 00:44:38 -0700 (PDT)" Message-ID: <86af63posm.fsf@emerson.gelemna.ft-wayne.in.us> Lines: 11 X-Mailer: Gnus v5.6.20/XEmacs 20.4 - "Emerald" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Doug White writes: > Okay, I give up. Can someone send the The Complete Guide to Building > -CURRENT on -STABLE? The binary format changes have made a complete mess make buildworld -m /usr/src/share/mk worked for me Saturday. -- I've always wanted to be a dilettante, but I've never quite been ready to make the commitment. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 21 02:20:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA13035 for freebsd-current-outgoing; Tue, 21 Jul 1998 02:20:54 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from atlrel2.hp.com (atlrel2.hp.com [156.153.255.202]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA13008 for ; Tue, 21 Jul 1998 02:20:44 -0700 (PDT) (envelope-from michael_class@hp.com) Received: from tmbbwmc.bbn.hp.com (atlrel2.hp.com [15.10.184.10]) by atlrel2.hp.com (8.8.6/8.8.5tis) with ESMTP id FAA12375 for ; Tue, 21 Jul 1998 05:19:34 -0400 (EDT) Received: from hp.com (michaelc@tmbbwmc.bbn.hp.com [15.136.25.181]) by tmbbwmc.bbn.hp.com (8.8.6/8.8.6) with ESMTP id LAA14454 for ; Tue, 21 Jul 1998 11:20:23 +0200 (METDST) Message-ID: <35B45D56.FD8FBF27@hp.com> Date: Tue, 21 Jul 1998 11:20:22 +0200 From: Michael Class Organization: Hewlett-Packard GmbH X-Mailer: Mozilla 4.5b1 [en] (X11; I; HP-UX B.10.20 9000/777) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG Subject: .. not getting any mails any more ... Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, for more then two weeks I am not getting any mails from freebsd-current and freebsd-scsi any more. I tried to resubscribe, but only got mails that stated that manual addition would be needed ( and done ), but nothing happend. I wrote to freebsd-current-owner@freebsd.org and got no answer. Is there something wrong??? Micha -- ___________________________________________________________________________ Michael Class E-Mail: michael_class@hp.com E-Business Solutions Center Phone: +49 7031 14-3707 EBSO-SERC Fax: +49 7031 14-4196 ___________________________________________________________________________ Hewlett-Packard GmbH, PO Box 1430, 71004 Boeblingen Sitz der Gesellschaft: Böblingen, Amtsgericht Böblingen HRB 4081 Geschäftsführer: Jörg Menno Harms (Vorsitzender), Heribert Schmitz, Rudi Speier, Fritz Schuller, Hans-Günter Hohmann ___________________________________________________________________________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 21 03:41:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA24183 for freebsd-current-outgoing; Tue, 21 Jul 1998 03:41:19 -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 DAA24175 for ; Tue, 21 Jul 1998 03:41:13 -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 MAA14673 ; Tue, 21 Jul 1998 12:38:59 +0200 (MET DST) Received: by sunw110.oslo.Geco-Prakla.slb.com (SMI-8.6/SMI-SVR4) id MAA22042; Tue, 21 Jul 1998 12:38:58 +0200 To: "Jordan K. Hubbard" Cc: Alfred Perlstein , Joel Ray Holveck , freebsd-current@FreeBSD.ORG Subject: Re: vn subsystem References: <26376.900979986@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: 21 Jul 1998 12:38:57 +0200 In-Reply-To: "Jordan K. Hubbard"'s message of Mon, 20 Jul 1998 17:13:06 -0700 Message-ID: Lines: 11 X-Mailer: Gnus v5.3/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jordan K. Hubbard" writes: > "Works for me" > > I'd not be able to build 3.0 snapshots at all if it were broken. Well, I haven't been able to make release for quite some time now. It stops when trying to vnconfig the floppy image. 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 Tue Jul 21 04:00:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA26996 for freebsd-current-outgoing; Tue, 21 Jul 1998 04:00:21 -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 EAA26989 for ; Tue, 21 Jul 1998 04:00:19 -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 DAA08018; Tue, 21 Jul 1998 03:58:53 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: smoergrd@oslo.geco-prakla.slb.com (Dag-Erling Coidan Sm rgrav) cc: Alfred Perlstein , Joel Ray Holveck , freebsd-current@FreeBSD.ORG Subject: Re: vn subsystem In-reply-to: Your message of "21 Jul 1998 12:38:57 +0200." Date: Tue, 21 Jul 1998 03:58:53 -0700 Message-ID: <8014.901018733@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sounds like a local configuration error - I just rolled 2 3.0 snaps in a row without trouble. - Jordan > "Jordan K. Hubbard" writes: > > "Works for me" > > > > I'd not be able to build 3.0 snapshots at all if it were broken. > > Well, I haven't been able to make release for quite some time now. It > stops when trying to vnconfig the floppy image. > > 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 Tue Jul 21 04:37:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA02864 for freebsd-current-outgoing; Tue, 21 Jul 1998 04:37:07 -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 EAA02839; Tue, 21 Jul 1998 04:36:57 -0700 (PDT) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by hub.org (8.8.8/8.7.5) with SMTP id HAA05558; Tue, 21 Jul 1998 07:36:11 -0400 (EDT) Date: Tue, 21 Jul 1998 07:36:07 -0400 (EDT) From: The Hermit Hacker To: "Daniel O'Connor" cc: current@FreeBSD.ORG, multimedia@FreeBSD.ORG Subject: Re: cdrecord with 3.0-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 Found the last problem with this at 5am this morning...I had scgx pointing at rworm#.ctl, which used to work. Changed it to point at rcd1.ctl, and now it works once more... On Tue, 21 Jul 1998, The Hermit Hacker wrote: > On Tue, 21 Jul 1998, Daniel O'Connor wrote: > > > > > > Can someone tell me what this error means, when I'm trying to > > > write to my CDR? > > > %cdrecord -v blank=all > > > Cdrecord release 1.6 Copyright (C) 1995-1998 Jrg Schilling > > > TOC Type: 1 = CD-ROM > > > cdrecord: Function not implemented. WARNING: Cannot set RR-scheduler > > > scsidev: '0,6,0' > > > scsibus: 0 target: 6 lun: 0 > > > cdrecord: Cannot do inquiry for CD-Recorder. > > > cdrecord: Undefined error: 0. test unit ready: scsi sendcmd: fatal error > > > CDB: 00 00 00 00 00 00 > > > cmd finished after 0.000s timeout 40s > > I get this when I don't run as root, but not the 'Function not implemented' > > stuff so I suspect its not that :) > > After doing some peaking around, I figured out what was causing the > 'Function not implemented' error message. Seems that newer kernels > require the following options to be added, in order for the sched_* set of > functions to work... > > options "P1003_1B" > options "_KPOSIX_PRIORITY_SCHEDULING" > options "_KPOSIX_VERSION=199309L" > > cdrecord still doesn't appear to work, but at least I'm one step closer :( > I still get the 'Undefined error', even working as root, so if someone can > suggest what might have changed in the kernel to cause it to fail, where > it once worked, that would be much appreciated... > > Thanks... > > Marc G. Fournier > Systems Administrator @ hub.org > primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org > > > 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 21 06:03:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA15197 for freebsd-current-outgoing; Tue, 21 Jul 1998 06:03:48 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mb05.swip.net (mb05.swip.net [193.12.122.209]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA15188 for ; Tue, 21 Jul 1998 06:03:45 -0700 (PDT) (envelope-from mg24174@gaia.swipnet.se) Received: from nic.swipnet.se (dialup159-2-53.swipnet.se [130.244.159.117]) by mb05.swip.net (8.8.8/8.8.8) with ESMTP id PAA23422 for ; Tue, 21 Jul 1998 15:03:27 +0200 (MET DST) Message-ID: <35B4903B.27B6F89D@gaia.swipnet.se> Date: Tue, 21 Jul 1998 14:57:32 +0200 From: joppe X-Mailer: Mozilla 4.0 [en] (Win95; I) MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe freebsd-current To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 21 06:43:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA20151 for freebsd-current-outgoing; Tue, 21 Jul 1998 06:43:01 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gilgamesch.bik-gmbh.de (gilgamesch.bik-gmbh.de [194.233.237.91]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA20146 for ; Tue, 21 Jul 1998 06:42:56 -0700 (PDT) (envelope-from cracauer@gilgamesch.bik-gmbh.de) Received: (from cracauer@localhost) by gilgamesch.bik-gmbh.de (8.8.8/8.7.3) id PAA01033; Tue, 21 Jul 1998 15:46:16 +0200 (MET DST) Message-ID: <19980721154615.B1009@cons.org> Date: Tue, 21 Jul 1998 15:46:15 +0200 From: Martin Cracauer To: The Hermit Hacker , "Daniel O'Connor" Cc: current@FreeBSD.ORG Subject: Re: cdrecord with 3.0-CURRENT ... Mail-Followup-To: The Hermit Hacker , Daniel O'Connor , current@FreeBSD.ORG References: <199807210250.MAA20783@cain.gsoft.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.1i In-Reply-To: ; from The Hermit Hacker on Tue, Jul 21, 1998 at 05:28:22AM -0300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In , The Hermit Hacker wrote: > On Tue, 21 Jul 1998, Daniel O'Connor wrote: > > > > > > Can someone tell me what this error means, when I'm trying to > > > write to my CDR? > > > %cdrecord -v blank=all > > > Cdrecord release 1.6 Copyright (C) 1995-1998 Jrg Schilling > > > TOC Type: 1 = CD-ROM > > > cdrecord: Function not implemented. WARNING: Cannot set RR-scheduler > > > scsidev: '0,6,0' > > > scsibus: 0 target: 6 lun: 0 > > > cdrecord: Cannot do inquiry for CD-Recorder. > > > cdrecord: Undefined error: 0. test unit ready: scsi sendcmd: fatal error > > > CDB: 00 00 00 00 00 00 > > > cmd finished after 0.000s timeout 40s > > I get this when I don't run as root, but not the 'Function not implemented' > > stuff so I suspect its not that :) > > After doing some peaking around, I figured out what was causing the > 'Function not implemented' error message. Seems that newer kernels > require the following options to be added, in order for the sched_* set of > functions to work... > > options "P1003_1B" > options "_KPOSIX_PRIORITY_SCHEDULING" > options "_KPOSIX_VERSION=199309L" > > cdrecord still doesn't appear to work, but at least I'm one step closer :( > I still get the 'Undefined error', even working as root, so if someone can > suggest what might have changed in the kernel to cause it to fail, where > it once worked, that would be much appreciated... cdrecords checks for Posix async I/O and uses it if it's available. This was implemented by John Dyson in FreeBSD, but it isn't by default in the kernel and it doesn't work on SMP at all. cdrecord's configure script uses include files or syscall stubs in libc (didn't check) to see if the system supports it, but it has no way to tell if it's available in the running kernel. Just import a binary package compiled on 2.2.x or see if cdrecord's configure script has a switch to disable using Posix aio. If so, please make a patch against the port and submit that, it probably doesn't make sense to have ports use aio at this time. Hope this helps Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer BSD User Group Hamburg, Germany http://www.bsdhh.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 21 06:58:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA23704 for freebsd-current-outgoing; Tue, 21 Jul 1998 06:58:53 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from goliath.camtech.net.au (goliath.camtech.net.au [203.5.73.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA23666 for ; Tue, 21 Jul 1998 06:58:44 -0700 (PDT) (envelope-from thyerm@camtech.net.au) Received: from camtech.net.au (dialup-ad-4-06.camtech.net.au [203.28.0.134]) by goliath.camtech.net.au (8.8.5/8.8.2) with ESMTP id XAA04259; Tue, 21 Jul 1998 23:26:10 +0930 (CST) Message-ID: <35B49E28.86F7CE19@camtech.net.au> Date: Tue, 21 Jul 1998 23:26:56 +0930 From: Matthew Thyer X-Mailer: Mozilla 4.05 [en] (X11; U; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: joelh@gnu.org CC: jkh@time.cdrom.com, bright@hotjobs.com, freebsd-current@FreeBSD.ORG Subject: Re: vn subsystem References: <26843.900985044@time.cdrom.com> <199807210525.AAA00857@detlev.UUCP> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Can someone please correct LINT and the manual page for vn(4) (under -CURRENT at least) if it is true that you are required to specify the number of vn devices. If it is not required, it would be good if the man page documented what number is assumed when unspecified. Joel Ray Holveck wrote: > > It turns out that this one was pilot error. When I was revising my > kernel config file, I had inadvertantly hit DEL and changed > "pseudo-device vn 4" to "pseudo-device vn ". (Since that was a while -- /=====================================================================\ |Work: Matthew.Thyer@dsto.defence.gov.au | Home: thyerm@camtech.net.au| \=====================================================================/ "If it is true that our Universe has a zero net value for all conserved quantities, then it may simply be a fluctuation of the vacuum of some larger space in which our Universe is imbedded. In answer to the question of why it happened, I offer the modest proposal that our Universe is simply one of those things which happen from time to time." E. P. Tryon from "Nature" Vol.246 Dec.14, 1973 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 21 07:28:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA00559 for freebsd-current-outgoing; Tue, 21 Jul 1998 07:28:10 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from goliath.camtech.net.au (goliath.camtech.net.au [203.5.73.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA00554 for ; Tue, 21 Jul 1998 07:28:07 -0700 (PDT) (envelope-from thyerm@camtech.net.au) Received: from camtech.net.au (dialup-ad-4-06.camtech.net.au [203.28.0.134]) by goliath.camtech.net.au (8.8.5/8.8.2) with ESMTP id XAA07897; Tue, 21 Jul 1998 23:57:32 +0930 (CST) Message-ID: <35B4A583.E3F1E64F@camtech.net.au> Date: Tue, 21 Jul 1998 23:58:19 +0930 From: Matthew Thyer X-Mailer: Mozilla 4.05 [en] (X11; U; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: FreeBSD CURRENT , Julian Elischer Subject: DEVFS not creating slice devices for my SCSI disks Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At CTM src-cur 3429 my system works fine but with kernels of src-cur 3457 and 346? (whatever it is we're currently up to - about 8 hours ago) DEVFS no longer has devices for the slices of my SCSI disks. All I see in /dev for the SCSI disks is: /dev/sd1, /dev/sd3 and /dev/sd4 (I have three disks wired down to their SCSI id's). These are old 1.3 and 1.8 GB disks (Seagates I think) which are connected to an adaptec 1542B controller. The disks in question have a single 'a' slice covering the whole disk and have filesystems that were created with either newfs -m 0 OR newfs -m 1 (I dont recall which right now). Maybe the problem started after raw devices went away ? All kernels have SLICE and DEVFS in them. Any idea whats up ? Unfortunately all source and my home directories are on these SCSI disks so I'm having to run with my 3429 kernel even though I've done two make worlds since. Sorry I cant provide more details but the system is remote (currently) and it hasn't come back from a boot on the newest kernel (as it couldn't fsck the filesystems of course!) -- /=====================================================================\ |Work: Matthew.Thyer@dsto.defence.gov.au | Home: thyerm@camtech.net.au| \=====================================================================/ "If it is true that our Universe has a zero net value for all conserved quantities, then it may simply be a fluctuation of the vacuum of some larger space in which our Universe is imbedded. In answer to the question of why it happened, I offer the modest proposal that our Universe is simply one of those things which happen from time to time." E. P. Tryon from "Nature" Vol.246 Dec.14, 1973 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 21 09:37:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA23059 for freebsd-current-outgoing; Tue, 21 Jul 1998 09:37:14 -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 JAA23009 for ; Tue, 21 Jul 1998 09:37:09 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id JAA08733; Tue, 21 Jul 1998 09:29:08 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdTd8731; Tue Jul 21 16:29:07 1998 Date: Tue, 21 Jul 1998 09:29:04 -0700 (PDT) From: Julian Elischer To: "Jordan K. Hubbard" cc: Dag-Erling Coidan Sm rgrav , Alfred Perlstein , Joel Ray Holveck , freebsd-current@FreeBSD.ORG Subject: Re: vn subsystem In-Reply-To: <8014.901018733@time.cdrom.com> 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 JAA23011 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Might soft-updates be involved? On Tue, 21 Jul 1998, Jordan K. Hubbard wrote: > Sounds like a local configuration error - I just rolled 2 3.0 snaps in > a row without trouble. > > - Jordan > > > "Jordan K. Hubbard" writes: > > > "Works for me" > > > > > > I'd not be able to build 3.0 snapshots at all if it were broken. > > > > Well, I haven't been able to make release for quite some time now. It > > stops when trying to vnconfig the floppy image. > > > > 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 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 21 09:54:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA26363 for freebsd-current-outgoing; Tue, 21 Jul 1998 09:54:56 -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 JAA26244 for ; Tue, 21 Jul 1998 09:54:29 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id JAA09451; Tue, 21 Jul 1998 09:43:37 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdsI9447; Tue Jul 21 16:43:36 1998 Date: Tue, 21 Jul 1998 09:43:33 -0700 (PDT) From: Julian Elischer To: Matthew Thyer cc: FreeBSD CURRENT Subject: Re: DEVFS not creating slice devices for my SCSI disks In-Reply-To: <35B4A583.E3F1E64F@camtech.net.au> 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 Thanks for letting me know.. I can't think what problem you may be having, but it soulds as if I've broken the 'format probes' for your disks.. how are they set up, "dangerously dedicated?" What does /dev look liek (regarding these devices) in a working kernel. and I presume that you end up with a 'can't mount root panic' if so, can you look above and try see what error messages hte SLICE code gives as a reasomn fr rejecting those disks? you say they don't find your SCSI disks.. does it still find your root disk? (I guess it must as you seem to be able to boot enough to look in /dev) can you give me a copy of 'dmesg' from such a boot? On Tue, 21 Jul 1998, Matthew Thyer wrote: > At CTM src-cur 3429 my system works fine but with kernels > of src-cur 3457 and 346? (whatever it is we're currently > up to - about 8 hours ago) DEVFS no longer has devices for > the slices of my SCSI disks. > > All I see in /dev for the SCSI disks is: /dev/sd1, /dev/sd3 > and /dev/sd4 (I have three disks wired down to their SCSI id's). > > These are old 1.3 and 1.8 GB disks (Seagates I think) which > are connected to an adaptec 1542B controller. > > The disks in question have a single 'a' slice covering the > whole disk and have filesystems that were created with either > newfs -m 0 OR newfs -m 1 (I dont recall which right now). shouldn't matter > here's what the end of MY boot looks like: what does the same part of YOUR boot look like? ----------------------- DEVFS: ready to run IP packet filtering initialized, divert enabled, rule-based forwarding enabled, logging disabled sd0: probing for MBR.. part 1, start=63, size=803187 sd0s1: type 6. Leaving part 2, start=803250, size=1397655 sd0s2: attaching disklabel.. .. nope sd1: probing for MBR.. part 1, start=63, size=2200842 sd1s1: attaching disklabel.. part a, start=0, size=65536 part b, start=65536, size=131072 part d, start=196608, size=65536 part e, start=262144, size=65536 part f, start=327680, size=327680 part g, start=655360, size=1545482 sd2: probing for MBR.. part 1, start=63, size=4193995 sd2s1: attaching disklabel.. part b, start=4128705, size=65290 part d, start=0, size=3678885 part e, start=3678885, size=449820 fd0: probing for MBR.. WOULD SELECT /sd1a but it doesn't exist /sd1s1a exists, I'll use that ------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 21 10:01:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA27645 for freebsd-current-outgoing; Tue, 21 Jul 1998 10:01:24 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from emu.sourcee.com (emu.sourcee.com [199.201.159.173]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA27629 for ; Tue, 21 Jul 1998 10:01:15 -0700 (PDT) (envelope-from nrice@emu.sourcee.com) Received: (from nrice@localhost) by emu.sourcee.com (8.8.8/8.8.3) id NAA20351; Tue, 21 Jul 1998 13:00:55 -0400 (EDT) Message-ID: <19980721130054.A20330@emu.sourcee.com> Date: Tue, 21 Jul 1998 13:00:54 -0400 From: Norman C Rice To: Doug White , current@FreeBSD.ORG Subject: Re: Does building current on 2.2.x still work? References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from Doug White on Tue, Jul 21, 1998 at 12:44:38AM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jul 21, 1998 at 12:44:38AM -0700, Doug White wrote: > Okay, I give up. Can someone send the The Complete Guide to Building > -CURRENT on -STABLE? The binary format changes have made a complete mess > of things: if ld doesn't die missing ___error (when BINFORMAT=aout), it's ^^^^^^^^ I have seen this happen when ``./'' is specified in the PATH environment. -- Regards, Norman C. Rice, Jr. > the assembler complaining about unknown psuedo-op .section (when > BINFORMAT=foo to bypass bsd.own.mk's misassumptions about /usr/lib vs > /usr/lib/aout in a 2.2.6-RELEASE universe). > > Or should I just copy /usr/lib to /usr/lib/aout, provide diffs to > /usr/src/Makefile and /etc/make.conf documenting the new magic variables > MACHINE_ARCH, BINFORMAT, and the above copying hack, then go back into my > hole and be quiet? > > Doug White | University of Oregon > Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant > http://gladstone.uoregon.edu/~dwhite | Computer Science Major To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 21 10:59:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA05704 for freebsd-current-outgoing; Tue, 21 Jul 1998 10:59:55 -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 KAA05669 for ; Tue, 21 Jul 1998 10:59:43 -0700 (PDT) (envelope-from benedict@echonyc.com) Received: from localhost (benedict@localhost) by echonyc.com (8.8.7/8.8.7) with SMTP id NAA22335 for ; Tue, 21 Jul 1998 13:59:23 -0400 (EDT) Date: Tue, 21 Jul 1998 13:59:22 -0400 (EDT) From: Snob Art Genre Reply-To: ben@rosengart.com To: current@FreeBSD.ORG Subject: softupdates and / 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 How do I enable softupdates on a root partition? I looked through the mailing list archives, because I *know* I saw this go by at one point, but couldn't find it. I'd just start trying different strategies, but this is on a remote system, and it's already tricky enough. I had to temporarily add a tunefs command to /etc/rc to get su enabled on /usr (does anyone know a better way?). 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 21 11:56:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA15989 for freebsd-current-outgoing; Tue, 21 Jul 1998 11:56:24 -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 LAA15881 for ; Tue, 21 Jul 1998 11:56:11 -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 0yyhZm-0004xt-00; Tue, 21 Jul 1998 12:55:50 -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 MAA27063; Tue, 21 Jul 1998 12:58:13 -0600 (MDT) Message-Id: <199807211858.MAA27063@harmony.village.org> To: Norman C Rice Subject: Re: Does building current on 2.2.x still work? Cc: Doug White , current@FreeBSD.ORG In-reply-to: Your message of "Tue, 21 Jul 1998 13:00:54 EDT." <19980721130054.A20330@emu.sourcee.com> References: <19980721130054.A20330@emu.sourcee.com> Date: Tue, 21 Jul 1998 12:58:13 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19980721130054.A20330@emu.sourcee.com> Norman C Rice writes: : > of things: if ld doesn't die missing ___error (when BINFORMAT=aout), it's cd /usr/src sudo make -m /usr/src/share/mk world Is all you need to do to upgrate from -stable to -current. Substitute buildworld if you just want to build. Note that using the relative path won't work, nor will trying to define things on the command line. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 21 12:32:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA22688 for freebsd-current-outgoing; Tue, 21 Jul 1998 12:32:50 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA22659 for ; Tue, 21 Jul 1998 12:32:38 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.5/8.8.8) with SMTP id MAA10279; Tue, 21 Jul 1998 12:31:54 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Tue, 21 Jul 1998 12:31:54 -0700 (PDT) From: Doug White To: John Birrell cc: current@FreeBSD.ORG Subject: Re: Does building current on 2.2.x still work? In-Reply-To: <199807210841.SAA01524@cimlogic.com.au> 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, 21 Jul 1998, John Birrell wrote: > Ahem, for the umpteenth time: > > cd /usr/src > make -m /usr/src/share/mk world > > I'm getting real sick of repeating this. If I edit this into > /usr/src/Makefile, do you think people would get the message? I would have, since that was the first thing I looked at when the compile barfed. Or the make-world tutorial. Or a commit log message. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major PS: yeah, I know, I should have checked the mail archives, but I figured it was non-obvious.... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 21 12:58:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA27277 for freebsd-current-outgoing; Tue, 21 Jul 1998 12:58:15 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from emu.sourcee.com (emu.sourcee.com [199.201.159.173]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA27163 for ; Tue, 21 Jul 1998 12:58:01 -0700 (PDT) (envelope-from nrice@emu.sourcee.com) Received: (from nrice@localhost) by emu.sourcee.com (8.8.8/8.8.3) id PAA20967; Tue, 21 Jul 1998 15:57:17 -0400 (EDT) Message-ID: <19980721155716.A20739@emu.sourcee.com> Date: Tue, 21 Jul 1998 15:57:16 -0400 From: Norman C Rice To: Warner Losh Cc: Doug White , current@FreeBSD.ORG Subject: Re: Does building current on 2.2.x still work? References: <19980721130054.A20330@emu.sourcee.com> <19980721130054.A20330@emu.sourcee.com> <199807211858.MAA27063@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199807211858.MAA27063@harmony.village.org>; from Warner Losh on Tue, Jul 21, 1998 at 12:58:13PM -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jul 21, 1998 at 12:58:13PM -0600, Warner Losh wrote: > In message <19980721130054.A20330@emu.sourcee.com> Norman C Rice writes: > : > of things: if ld doesn't die missing ___error (when BINFORMAT=aout), it's > > cd /usr/src > sudo make -m /usr/src/share/mk world > > Is all you need to do to upgrate from -stable to -current. Substitute > buildworld if you just want to build. > > Note that using the relative path won't work, nor will trying to > define things on the command line. Perhaps my intent was unclear. I was trying to let Doug know that using the relative path can/will `break' the build and spew the infamous ``___error'' messages. I thought as keeper of the FAQ this might be of interest to Doug. AFAIK, use of the relative path also breaks updates of -current. I do not have any problems with the build or install. I have not experienced any problems with the following, except after a few untimely cvsup's. ;-) make -m /usr/src/share/mk buildworld make -m /usr/src/share/mk installworld -- Regards, Norman C. Rice, Jr. > > Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 21 13:13:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA00531 for freebsd-current-outgoing; Tue, 21 Jul 1998 13:13:39 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA00517 for ; Tue, 21 Jul 1998 13:13:32 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from gate.lan.awfulhak.org (brian@localhost [127.0.0.1]) by awfulhak.org (8.8.8/8.8.8) with ESMTP id UAA19823; Tue, 21 Jul 1998 20:45:41 +0100 (BST) (envelope-from brian@gate.lan.awfulhak.org) Message-Id: <199807211945.UAA19823@awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: "Jordan K. Hubbard" cc: Alfred Perlstein , Joel Ray Holveck , freebsd-current@FreeBSD.ORG Subject: Re: vn subsystem In-reply-to: Your message of "Mon, 20 Jul 1998 20:33:39 PDT." <27156.900992019@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 21 Jul 1998 20:45:41 +0100 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > hrm, not really there was some traffic on the lists a few weeks/months > > back about it being broken, but that's all i know. > > Erm, wonderful. Can we have some commentary from someone who's > actually proven this either way now? Like I said, my own usage of the > vn driver has not shown any such instability. If someone who's > _actually used it_ can now comment on its instability, we'll get a lot > further. I have several iso images on disk and a script that vnconfig's the files then mount -t cd9660's them. The results are then seen as shares via samba to windows clients (albeit read-only). This (and ``make release'') has caused me no problems - in -current & -stable. > - Jordan -- Brian , , Don't _EVER_ lose your sense of humour.... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 21 13:14:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA00584 for freebsd-current-outgoing; Tue, 21 Jul 1998 13:14:03 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA00524; Tue, 21 Jul 1998 13:13:37 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from gate.lan.awfulhak.org (brian@localhost [127.0.0.1]) by awfulhak.org (8.8.8/8.8.8) with ESMTP id VAA20743; Tue, 21 Jul 1998 21:10:45 +0100 (BST) (envelope-from brian@gate.lan.awfulhak.org) Message-Id: <199807212010.VAA20743@awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: Bruce Evans cc: brian@Awfulhak.org, freebsd-current@FreeBSD.ORG, jak@cetlink.net, freebsd-mobile@FreeBSD.ORG Follow-up-To: me, freebsd-mobile@FreeBSD.org, jak@cetlink.net, Bruce Evans Subject: Re: tickadj -t not changing tick In-reply-to: Your message of "Mon, 20 Jul 1998 16:03:16 +1000." <199807200603.QAA15267@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 21 Jul 1998 21:10:45 +0100 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [Follow-up-to pointed at freebsd-mobile] > >Hmm, I have a timer problem with a Compaq Presario (notebook). It > >seems that the timer chip (i8254 is the only one probed) is acting a > >big strangely and returning ``past'' times - this is disastrous at > >the start of a programs life as it tends to exceed the maximum > >runtime (all set correctly to infinity in login.conf) and result in a > >sig 24. > > It can't be a problem with the i8254 hardware, because the i8254 > timecounter never goes backwards (if the hardware goes backwards, > then the timecounter jumps forwards). > > >The laptop: > > > >: FreeBSD 3.0-CURRENT #10: Tue Jul 14 10:02:00 BST 1998 > >: brian@woof.lan.awfulhak.org:/usr/src/sys/compile/WOOF > >: Timecounter "i8254" frequency 1193182 Hz cost 1296 ns > >: CPU: Cyrix GXm (17.09-MHz 586-class CPU) > >: Origin = "CyrixInstead" Id = 0x540 Stepping=0 DIR=0x3346 > >: Features=0x808131 > >: real memory = 33554432 (32768K bytes) > >: avail memory = 30597120 (29880K bytes) > > > >This is *really* a 233MHz chip. > > APM seems to be preventing use of the TSC timecounter. Otherwise > the clock would go non-backwards 233/17 faster :-). Well, you're right about apm & the tsc counter. If I remove apm, I get the TSC counter back.... *but* my clock *zoooms* along - at what visually looks like around 10 times the speed. Setting the tsc timecounter to 233000000 via sysctl normalises the time again :-I Unfortunately, I'm still seeing the sig24 avoidance stuff that I did, so something's still going backwards :-( Additionally, the apm controller is misbehaving - so all this may be a result of that. It's one of those nasty pci-come-isa jobs (VLSI 82C146, 5 mem & 2 i/o windows), and no matter what I do, I can't get it to notice the pccard's irq. I've tried manually assigning irq 12 (rather than 3) to the controller by tweaking pccard.c but it makes no difference. The card is functional in my old laptop and has a hard-coded irq 10 in pccard.conf - and I know irq 12 is free for the controller (I'm not sure about irq 3 'cos there's a built-in modem that I haven't been able to find i/o address-wise yet) :-/ I know it's an irq problem because if I ``ping -c2'', I get everything back in one go at the end. Any other ping results in nothing. arps work and dns (udp?) works very slowly. Anyone know if the PAO stuff might address this ? Is there a -current version of PAO ? > Bruce TIA anyone. -- Brian , , Don't _EVER_ lose your sense of humour.... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 21 13:18:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA01471 for freebsd-current-outgoing; Tue, 21 Jul 1998 13:18:12 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA01412 for ; Tue, 21 Jul 1998 13:17:57 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.5/8.8.8) with SMTP id NAA17873; Tue, 21 Jul 1998 13:17:27 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Tue, 21 Jul 1998 13:17:27 -0700 (PDT) From: Doug White To: Norman C Rice cc: Warner Losh , current@FreeBSD.ORG Subject: Re: Does building current on 2.2.x still work? In-Reply-To: <19980721155716.A20739@emu.sourcee.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, 21 Jul 1998, Norman C Rice wrote: > On Tue, Jul 21, 1998 at 12:58:13PM -0600, Warner Losh wrote: > > In message <19980721130054.A20330@emu.sourcee.com> Norman C Rice writes: > > : > of things: if ld doesn't die missing ___error (when BINFORMAT=aout), it's > > > > cd /usr/src > > sudo make -m /usr/src/share/mk world > > > > Is all you need to do to upgrate from -stable to -current. Substitute > > buildworld if you just want to build. > > > > Note that using the relative path won't work, nor will trying to > > define things on the command line. > > Perhaps my intent was unclear. I was trying to let Doug know that > using the relative path can/will `break' the build and spew the infamous > ``___error'' messages. I thought as keeper of the FAQ this might be of > interest to Doug. AFAIK, use of the relative path also breaks updates > of -current. I know that the ___error problem spawns from a libc version conflict. The last time I had current on this box they switched the libraries over, and the next day's build exploded. I remembered the discussion from -hackers about it, copied /usr/lib to /usr/lib/aout, re-ldconfig'd, and the build went smoothly. Also, the above published solution has not exploded yet .. It's chewing on liF77 now. (building from work over dialup just doesn't do great things for speding up the build.) I just remembered I have MACHINE_ARCH and BINFORMAT defined in make.conf; hope that doesn't confuse anything. > make -m /usr/src/share/mk buildworld > make -m /usr/src/share/mk installworld I'm not too much in favor of sticking -current-isms in the FAQ, but we could make an exception. Or Nik could drop it onto the tutorial (which was one of the places I checked, along with /usr/src/Makefile and the commit logs for said Makefile and make.conf). Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 21 13:50:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA08951 for freebsd-current-outgoing; Tue, 21 Jul 1998 13:50:17 -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 NAA08874 for ; Tue, 21 Jul 1998 13:50:09 -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 0yyjM4-00051S-00; Tue, 21 Jul 1998 14:49:48 -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 OAA27924; Tue, 21 Jul 1998 14:52:12 -0600 (MDT) Message-Id: <199807212052.OAA27924@harmony.village.org> To: Norman C Rice Subject: Re: Does building current on 2.2.x still work? Cc: Doug White , current@FreeBSD.ORG In-reply-to: Your message of "Tue, 21 Jul 1998 15:57:16 EDT." <19980721155716.A20739@emu.sourcee.com> References: <19980721155716.A20739@emu.sourcee.com> <19980721130054.A20330@emu.sourcee.com> <19980721130054.A20330@emu.sourcee.com> <199807211858.MAA27063@harmony.village.org> Date: Tue, 21 Jul 1998 14:52:12 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19980721155716.A20739@emu.sourcee.com> Norman C Rice writes: : Perhaps my intent was unclear. I was trying to let Doug know that : using the relative path can/will `break' the build and spew the infamous : ``___error'' messages. I thought as keeper of the FAQ this might be of : interest to Doug. AFAIK, use of the relative path also breaks updates : of -current. Hmmm. I think that the hacks I have in my local tree to forbid relative paths in the make buildworld aren't completely bad and should be committed. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 21 13:51:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA09123 for freebsd-current-outgoing; Tue, 21 Jul 1998 13:51:17 -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 NAA09112 for ; Tue, 21 Jul 1998 13:51:12 -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 0yyjN7-00051X-00; Tue, 21 Jul 1998 14:50:53 -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 OAA27935; Tue, 21 Jul 1998 14:53:18 -0600 (MDT) Message-Id: <199807212053.OAA27935@harmony.village.org> To: Doug White Subject: Re: Does building current on 2.2.x still work? Cc: Norman C Rice , current@FreeBSD.ORG In-reply-to: Your message of "Tue, 21 Jul 1998 13:17:27 PDT." References: Date: Tue, 21 Jul 1998 14:53:17 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Doug White writes: : I'm not too much in favor of sticking -current-isms in the FAQ, but we : could make an exception. Or Nik could drop it onto the tutorial (which : was one of the places I checked, along with /usr/src/Makefile and the : commit logs for said Makefile and make.conf). Actually better would be to fix it in -current so that you don't need to specify -m /muble/foo Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 21 14:00:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA11465 for freebsd-current-outgoing; Tue, 21 Jul 1998 14:00:49 -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 OAA11410 for ; Tue, 21 Jul 1998 14:00:33 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-76.camalott.com [208.229.74.76]) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id QAA11264; Tue, 21 Jul 1998 16:01:05 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.8.8/8.8.8) id QAA01743; Tue, 21 Jul 1998 16:00:10 -0500 (CDT) (envelope-from joelh) Date: Tue, 21 Jul 1998 16:00:10 -0500 (CDT) Message-Id: <199807212100.QAA01743@detlev.UUCP> To: freebsd-current@FreeBSD.ORG Subject: 3C509 driver status From: Joel Ray Holveck Reply-to: joelh@gnu.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is anybody presently hacking the ep0 (3C509) driver? It looks like it would be useful for me to bring it to working capacity if nobody else is. (And the first person who tells me about the $50 Intel cards gets to pay for both the card and a MB that will support it. :-)) Best, 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 21 14:14:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA14474 for freebsd-current-outgoing; Tue, 21 Jul 1998 14:14:22 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA14405 for ; Tue, 21 Jul 1998 14:14:12 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id OAA01951; Tue, 21 Jul 1998 14:11:19 -0700 (PDT) Message-Id: <199807212111.OAA01951@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Brian Somers cc: "Jordan K. Hubbard" , Alfred Perlstein , Joel Ray Holveck , freebsd-current@FreeBSD.ORG Subject: Re: vn subsystem In-reply-to: Your message of "Tue, 21 Jul 1998 20:45:41 BST." <199807211945.UAA19823@awfulhak.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 21 Jul 1998 14:11:18 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > hrm, not really there was some traffic on the lists a few weeks/months > > > back about it being broken, but that's all i know. > > > > Erm, wonderful. Can we have some commentary from someone who's > > actually proven this either way now? Like I said, my own usage of the > > vn driver has not shown any such instability. If someone who's > > _actually used it_ can now comment on its instability, we'll get a lot > > further. It's quite possible to get the 'vn' driver into a state where the device has been vnconfig'ed, but you can't un-vnconfig it (you get ENXIO). This usually bites me when I'm configing up a floppy image for bootstrapping; IIRC it generally stems from getting the (undocumented) -s slices option wrong. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 21 14:19:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA15695 for freebsd-current-outgoing; Tue, 21 Jul 1998 14:19:55 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA15590; Tue, 21 Jul 1998 14:19:25 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id OAA01981; Tue, 21 Jul 1998 14:16:50 -0700 (PDT) Message-Id: <199807212116.OAA01981@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Brian Somers cc: Bruce Evans , freebsd-current@FreeBSD.ORG, jak@cetlink.net, freebsd-mobile@FreeBSD.ORG Subject: Re: tickadj -t not changing tick In-reply-to: Your message of "Tue, 21 Jul 1998 21:10:45 BST." <199807212010.VAA20743@awfulhak.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 21 Jul 1998 14:16:50 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > >The laptop: > > > > > >: FreeBSD 3.0-CURRENT #10: Tue Jul 14 10:02:00 BST 1998 > > >: brian@woof.lan.awfulhak.org:/usr/src/sys/compile/WOOF > > >: Timecounter "i8254" frequency 1193182 Hz cost 1296 ns > > >: CPU: Cyrix GXm (17.09-MHz 586-class CPU) This isn't actually a Cyrix "MediaGX" processor, is it? If so *all* bets on its behaviour are off. The MediaGX emulates some of the system hardware using SMI traps, and the quality and accuracy of this emulation seems to vary widely with BIOS implementor. > Additionally, the apm controller is misbehaving - so all this may be > a result of that. It's one of those nasty pci-come-isa jobs (VLSI > 82C146, 5 mem & 2 i/o windows), and no matter what I do, I can't get > it to notice the pccard's irq. Don't confuse APM (which is a software interface to the BIOS) and the PCCARD controller (which is hardware). Completely different things. What do you mean by "notice the pccard's IRQ"? Have you verified that the controller in question is actually an 82C146, or just something that behaves something like it? The PCCARD controller is polled as well as handled by an interrupt, but that doesn't sound like your problem. > I've tried manually assigning irq 12 (rather than 3) to the > controller by tweaking pccard.c but it makes no difference. The card > is functional in my old laptop and has a hard-coded irq 10 in > pccard.conf - and I know irq 12 is free for the controller (I'm not > sure about irq 3 'cos there's a built-in modem that I haven't been > able to find i/o address-wise yet) :-/ > > I know it's an irq problem because if I ``ping -c2'', I get > everything back in one go at the end. Any other ping results in > nothing. arps work and dns (udp?) works very slowly. This isn't related to the controller IRQ, but rather the card IRQ. It sounds like either the controller is not correctly generating the requested IRQ, or the IRQ that you're assigning to the card is in use by something else in the system. Try moving your card IRQ's around. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 21 15:21:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA27635 for freebsd-current-outgoing; Tue, 21 Jul 1998 15:21:03 -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 PAA27627 for ; Tue, 21 Jul 1998 15:20:57 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.8/8.8.7) id IAA03131; Wed, 22 Jul 1998 08:38:06 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199807212238.IAA03131@cimlogic.com.au> Subject: Re: Does building current on 2.2.x still work? In-Reply-To: from Doug White at "Jul 21, 98 01:17:27 pm" To: dwhite@resnet.uoregon.edu (Doug White) Date: Wed, 22 Jul 1998 08:38:06 +1000 (EST) Cc: nrice@emu.sourcee.com, imp@village.org, 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 Doug White wrote: > I know that the ___error problem spawns from a libc version conflict. No it doesn't. It results from the world/buildworld not using -nostdlib and not finding the libraries it has just built because the library path is incorrectly set to /usr/obj/usr/src/usr/lib instead of /usr/obj/usr/src/usr/lib/aout. This is the result of using old installed .mk files, hence the need for the -m argument. Changing libc versions would not have any effect. -- 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 Tue Jul 21 15:24:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA28395 for freebsd-current-outgoing; Tue, 21 Jul 1998 15:24:34 -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 PAA28389 for ; Tue, 21 Jul 1998 15:24:31 -0700 (PDT) (envelope-from toasty@home.dragondata.com) Received: (from toasty@localhost) by home.dragondata.com (8.8.8/8.8.5) id RAA09883 for current@freebsd.org; Tue, 21 Jul 1998 17:24:13 -0500 (CDT) From: Kevin Day Message-Id: <199807212224.RAA09883@home.dragondata.com> Subject: panic: page fault while in kernel mode - from gcc To: current@FreeBSD.ORG Date: Tue, 21 Jul 1998 17:24:12 -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 I was able to make gcc produce this twice - then it wouldn't do it again: page fault while in kernel mode A trace shows: _zalloci _get_pv_entry _pmap_insert_entry _pmap_enter _vm_fault _trap calltrap() --- trap 0xc, eip = 0xf01cd754, esp = 0xfaa9fe88, ebp = 0xfaa9fe88 _get_ptbase _pmap_protect _vm_map_copy_entry _vmspace_fork _vm_fork _fork1 _vfork _syscall _Xsyscall This mean anything to anyone? Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 21 16:41:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA11644 for freebsd-current-outgoing; Tue, 21 Jul 1998 16:41:27 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA11589 for ; Tue, 21 Jul 1998 16:41:05 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from gate.lan.awfulhak.org (brian@localhost [127.0.0.1]) by awfulhak.org (8.8.8/8.8.8) with ESMTP id AAA28604; Wed, 22 Jul 1998 00:27:16 +0100 (BST) (envelope-from brian@gate.lan.awfulhak.org) Message-Id: <199807212327.AAA28604@awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: ben@rosengart.com cc: current@FreeBSD.ORG Subject: Re: softupdates and / In-reply-to: Your message of "Tue, 21 Jul 1998 13:59:22 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 22 Jul 1998 00:27:16 +0100 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > How do I enable softupdates on a root partition? I looked through the > mailing list archives, because I *know* I saw this go by at one point, > but couldn't find it. > > I'd just start trying different strategies, but this is on a remote > system, and it's already tricky enough. I had to temporarily add a > tunefs command to /etc/rc to get su enabled on /usr (does anyone know a > better way?). Go single-user, sync, tunefs, hit the power off switch. > Ben > > "You have your mind on computers, it seems." -- Brian , , Don't _EVER_ lose your sense of humour.... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 21 16:41:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA11719 for freebsd-current-outgoing; Tue, 21 Jul 1998 16:41:57 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA11655 for ; Tue, 21 Jul 1998 16:41:35 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from gate.lan.awfulhak.org (brian@localhost [127.0.0.1]) by awfulhak.org (8.8.8/8.8.8) with ESMTP id AAA28587; Wed, 22 Jul 1998 00:25:20 +0100 (BST) (envelope-from brian@gate.lan.awfulhak.org) Message-Id: <199807212325.AAA28587@awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: Julian Elischer cc: "Jordan K. Hubbard" , Dag-Erling Coidan Sm rgrav , Alfred Perlstein , Joel Ray Holveck , freebsd-current@FreeBSD.ORG Subject: Re: vn subsystem In-reply-to: Your message of "Tue, 21 Jul 1998 09:29:04 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Date: Wed, 22 Jul 1998 00:25:18 +0100 From: Brian Somers Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id QAA11699 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Indeed. DEVFS + SLICE = make release breakage. I tried a quick local hack to mount -t devfs devfs /dev || { cd /dev; sh ./MAKEDEV std; } (or similar), but it didn't work first time and I hadn't the time to try again. The problem was probably that I was already in a chrooted environment at that point and mounts are global.... so I was trying to mount /dev when it was already mounted and wasn't going near the chrooted area at all.... > Might soft-updates be involved? > > > On Tue, 21 Jul 1998, Jordan K. Hubbard wrote: > > > Sounds like a local configuration error - I just rolled 2 3.0 snaps in > > a row without trouble. > > > > - Jordan > > > > > "Jordan K. Hubbard" writes: > > > > "Works for me" > > > > > > > > I'd not be able to build 3.0 snapshots at all if it were broken. > > > > > > Well, I haven't been able to make release for quite some time now. It > > > stops when trying to vnconfig the floppy image. > > > > > > DES > > > -- > > > Dag-Erling Smørgrav - smoergrd@oslo.geco-prakla.slb.com -- Brian , , Don't _EVER_ lose your sense of humour.... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 21 16:51:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA13727 for freebsd-current-outgoing; Tue, 21 Jul 1998 16:51:24 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.dyn.ml.org (garbanzo@pm3-4.ppp.wenet.net [206.15.85.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA13703 for ; Tue, 21 Jul 1998 16:51:17 -0700 (PDT) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost) by zippy.dyn.ml.org (8.8.8/8.8.8) with SMTP id QAA07019; Tue, 21 Jul 1998 16:52:05 -0700 (PDT) (envelope-from garbanzo@hooked.net) X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs Date: Tue, 21 Jul 1998 16:52:05 -0700 (PDT) From: Alex X-Sender: garbanzo@zippy.dyn.ml.org To: ben@rosengart.com cc: current@FreeBSD.ORG Subject: Re: softupdates and / 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, 21 Jul 1998, Snob Art Genre wrote: > How do I enable softupdates on a root partition? I looked through the > mailing list archives, because I *know* I saw this go by at one point, > but couldn't find it. > > I'd just start trying different strategies, but this is on a remote > system, and it's already tricky enough. I had to temporarily add a > tunefs command to /etc/rc to get su enabled on /usr (does anyone know a > better way?). I booted into single user mode, ran tunefs -n enable on /dev/rsd0a, and hit reset. I'm sure something similar could be accomplished if you put that in a rc script that ended in reboot -n. Oddly enough, I only see one: ffs_mountfs: superblock updated Even though mount shows: zippy:~/png#mount /dev/sd0s1a on / (local, soft-updates, writes: sync 105 async 17719) /dev/sd1s1e on /mnt/usr2 (local, soft-updates, writes: sync 2 async 868) *shrug* YMMV - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 21 16:52:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA13876 for freebsd-current-outgoing; Tue, 21 Jul 1998 16:52:06 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.camalott.com (root@[208.203.140.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA13827 for ; Tue, 21 Jul 1998 16:51:59 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-124.camalott.com [208.229.74.124]) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id SAA22663; Tue, 21 Jul 1998 18:51:49 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.8.8/8.8.8) id SAA14507; Tue, 21 Jul 1998 18:50:50 -0500 (CDT) (envelope-from joelh) Date: Tue, 21 Jul 1998 18:50:50 -0500 (CDT) Message-Id: <199807212350.SAA14507@detlev.UUCP> To: brian@Awfulhak.org CC: julian@whistle.com, jkh@time.cdrom.com, smoergrd@oslo.geco-prakla.slb.com, bright@hotjobs.com, freebsd-current@FreeBSD.ORG In-reply-to: <199807212325.AAA28587@awfulhak.org> (message from Brian Somers on Wed, 22 Jul 1998 00:25:18 +0100) Subject: Re: vn subsystem From: Joel Ray Holveck Reply-to: joelh@gnu.org References: <199807212325.AAA28587@awfulhak.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Indeed. DEVFS + SLICE = make release breakage. > I tried a quick local hack to > mount -t devfs devfs /dev || { cd /dev; sh ./MAKEDEV std; } > (or similar), but it didn't work first time and I hadn't the time to > try again. The problem was probably that I was already in a chrooted > environment at that point and mounts are global.... so I was trying > to mount /dev when it was already mounted and wasn't going near the > chrooted area at all.... I could be mistaken, but doesn't DEVFS not list vn devices to begin with? 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 21 17:41:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA24478 for freebsd-current-outgoing; Tue, 21 Jul 1998 17:41:22 -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 RAA24449 for ; Tue, 21 Jul 1998 17:41:14 -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 IAA25854 for ; Wed, 22 Jul 1998 08:39:49 +0800 (HKT) Received: (from c5666305@localhost) by cssolar85.COMP.HKP.HK (SMI-8.6/) id IAA22610 for freebsd-current@freebsd.org; Wed, 22 Jul 1998 08:39:48 +0800 Message-Id: <199807220039.IAA22610@cssolar85.COMP.HKP.HK> Subject: confusion on da and sd device To: freebsd-current@FreeBSD.ORG Date: Wed, 22 Jul 1998 08:39:48 +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 playing with 3.0-19980712-SNAP smp system (CAM). However I am confuse by the da device (CAM) and the sd (previous). If I want to add a new disk what should I do with the da device. I am going to add a optical disk and a ccd disk which includes two identical disk. 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 21 17:50:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA26377 for freebsd-current-outgoing; Tue, 21 Jul 1998 17:50:34 -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 RAA26357 for ; Tue, 21 Jul 1998 17:50:24 -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 RAA22703; Tue, 21 Jul 1998 17:49:09 -0700 (PDT) Message-Id: <199807220049.RAA22703@implode.root.com> To: Kevin Day cc: current@FreeBSD.ORG Subject: Re: panic: page fault while in kernel mode - from gcc In-reply-to: Your message of "Tue, 21 Jul 1998 17:24:12 CDT." <199807212224.RAA09883@home.dragondata.com> From: David Greenman Reply-To: dg@root.com Date: Tue, 21 Jul 1998 17:49:09 -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >I was able to make gcc produce this twice - then it wouldn't do it again: > >page fault while in kernel mode > >A trace shows: > >_zalloci >_get_pv_entry >_pmap_insert_entry >_pmap_enter >_vm_fault >_trap >calltrap() >--- trap 0xc, eip = 0xf01cd754, esp = 0xfaa9fe88, ebp = 0xfaa9fe88 >_get_ptbase >_pmap_protect >_vm_map_copy_entry >_vmspace_fork >_vm_fork >_fork1 >_vfork >_syscall >_Xsyscall > >This mean anything to anyone? This seems to indicate that the new process's page directory either hasn't been allocated yet or went away for some reason. Apparantly one of several new bugs that John has left us with. -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 21 18:43:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA05164 for freebsd-current-outgoing; Tue, 21 Jul 1998 18:43:58 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA05150 for ; Tue, 21 Jul 1998 18:43:51 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.5/8.8.8) with SMTP id SAA12612; Tue, 21 Jul 1998 18:43:16 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Tue, 21 Jul 1998 18:43:16 -0700 (PDT) From: Doug White To: John Birrell cc: nrice@emu.sourcee.com, imp@village.org, current@FreeBSD.ORG Subject: Re: Does building current on 2.2.x still work? In-Reply-To: <199807212238.IAA03131@cimlogic.com.au> 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, 22 Jul 1998, John Birrell wrote: > Doug White wrote: > > I know that the ___error problem spawns from a libc version conflict. > > No it doesn't. It results from the world/buildworld not using -nostdlib > and not finding the libraries it has just built because the library > path is incorrectly set to /usr/obj/usr/src/usr/lib instead of > /usr/obj/usr/src/usr/lib/aout. This is the result of using old installed > .mk files, hence the need for the -m argument. Changing libc versions > would not have any effect. Ah, ok. Well, it didn't fall over this time, so record the ``make -m /foo/bar buildworld' as a solution. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 21 21:45:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA01398 for freebsd-current-outgoing; Tue, 21 Jul 1998 21:45:55 -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 VAA01375 for ; Tue, 21 Jul 1998 21:45:43 -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 VAA12195; Tue, 21 Jul 1998 21:45:21 -0700 (PDT) (envelope-from jdp) Message-Id: <199807220445.VAA12195@austin.polstra.com> To: julian@whistle.com Subject: Re: vn subsystem In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Date: Tue, 21 Jul 1998 21:45:21 -0700 From: John Polstra Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Might soft-updates be involved? I did a make release just last night on a system that's 100% soft-updates. It worked for me. -- 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 Tue Jul 21 22:42:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA09692 for freebsd-current-outgoing; Tue, 21 Jul 1998 22:42:19 -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 WAA09673 for ; Tue, 21 Jul 1998 22:42: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 BAA29747 for ; Wed, 22 Jul 1998 01:41:52 -0400 (EDT) Date: Wed, 22 Jul 1998 01:41:51 -0400 (EDT) From: Snob Art Genre Reply-To: ben@rosengart.com To: current@FreeBSD.ORG Subject: Re: softupdates and / In-Reply-To: <199807212327.AAA28604@awfulhak.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 Many thanks to all who replied. Summary: Luoqi Chen sent me a patch to tunefs which should eliminate the need to hit the reset button, which helps because it's a remote system. I will report my results tomorrow (I try to avoid tricky remote administration at this hour ;-). 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 21 23:00:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA13389 for freebsd-current-outgoing; Tue, 21 Jul 1998 23:00:46 -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 XAA13383 for ; Tue, 21 Jul 1998 23:00:41 -0700 (PDT) (envelope-from toasty@home.dragondata.com) Received: (from toasty@localhost) by home.dragondata.com (8.8.8/8.8.5) id AAA03924; Wed, 22 Jul 1998 00:59:55 -0500 (CDT) From: Kevin Day Message-Id: <199807220559.AAA03924@home.dragondata.com> Subject: Re: panic: page fault while in kernel mode - from gcc In-Reply-To: <199807220049.RAA22703@implode.root.com> from David Greenman at "Jul 21, 98 05:49:09 pm" To: dg@root.com Date: Wed, 22 Jul 1998 00:59:55 -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 was able to make gcc produce this twice - then it wouldn't do it again: > > > >page fault while in kernel mode > > > >A trace shows: > > > >_zalloci > >_get_pv_entry > >_pmap_insert_entry > >_pmap_enter > >_vm_fault > >_trap > >calltrap() > >--- trap 0xc, eip = 0xf01cd754, esp = 0xfaa9fe88, ebp = 0xfaa9fe88 > >_get_ptbase > >_pmap_protect > >_vm_map_copy_entry > >_vmspace_fork > >_vm_fork > >_fork1 > >_vfork > >_syscall > >_Xsyscall > > > >This mean anything to anyone? > > This seems to indicate that the new process's page directory either hasn't > been allocated yet or went away for some reason. Apparantly one of several > new bugs that John has left us with. > Is there any reason why someone doesn't back out his last few batches of large vm changes? Apparently he was half done with some of it, and what we had before seemed more stable than what we have now. (although the NFS changes did really fix a lot of problems) Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 21 23:18:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA16097 for freebsd-current-outgoing; Tue, 21 Jul 1998 23:18:38 -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 XAA16069 for ; Tue, 21 Jul 1998 23:18:27 -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 XAA26587; Tue, 21 Jul 1998 23:17:11 -0700 (PDT) Message-Id: <199807220617.XAA26587@implode.root.com> To: Kevin Day cc: current@FreeBSD.ORG Subject: Re: panic: page fault while in kernel mode - from gcc In-reply-to: Your message of "Wed, 22 Jul 1998 00:59:55 CDT." <199807220559.AAA03924@home.dragondata.com> From: David Greenman Reply-To: dg@root.com Date: Tue, 21 Jul 1998 23:17:11 -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> This seems to indicate that the new process's page directory either hasn't >> been allocated yet or went away for some reason. Apparantly one of several >> new bugs that John has left us with. >> > >Is there any reason why someone doesn't back out his last few batches of >large vm changes? Apparently he was half done with some of it, and what we >had before seemed more stable than what we have now. That may ultimately be what we have to do, but the fixes also fixed some serious 'leak' style problems with the Mach derived VM system, so I'd rather that we find the bugs and fix them rather than going back to the previous code. -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 21 23:21:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA16566 for freebsd-current-outgoing; Tue, 21 Jul 1998 23:21:18 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA16510 for ; Tue, 21 Jul 1998 23:21:02 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from gate.lan.awfulhak.org (brian@localhost [127.0.0.1]) by awfulhak.org (8.8.8/8.8.8) with ESMTP id HAA12871; Wed, 22 Jul 1998 07:17:25 +0100 (BST) (envelope-from brian@gate.lan.awfulhak.org) Message-Id: <199807220617.HAA12871@awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: Alex cc: ben@rosengart.com, current@FreeBSD.ORG Subject: Re: softupdates and / In-reply-to: Your message of "Tue, 21 Jul 1998 16:52:05 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 22 Jul 1998 07:17:25 +0100 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Tue, 21 Jul 1998, Snob Art Genre wrote: > > > How do I enable softupdates on a root partition? I looked through the > > mailing list archives, because I *know* I saw this go by at one point, > > but couldn't find it. > > > > I'd just start trying different strategies, but this is on a remote > > system, and it's already tricky enough. I had to temporarily add a > > tunefs command to /etc/rc to get su enabled on /usr (does anyone know a > > better way?). > > I booted into single user mode, ran tunefs -n enable on /dev/rsd0a, and > hit reset. I'm sure something similar could be accomplished if you put > that in a rc script that ended in reboot -n. > > Oddly enough, I only see one: > ffs_mountfs: superblock updated > Even though mount shows: > > zippy:~/png#mount > /dev/sd0s1a on / (local, soft-updates, writes: sync 105 async 17719) > /dev/sd1s1e on /mnt/usr2 (local, soft-updates, writes: sync 2 async 868) > > *shrug* > > YMMV My laptop has: Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/wd0s1a 1885583 1176081 558656 68% / procfs 4 4 0 100% /proc kernfs 1 1 0 100% /kern and I don't see any :-) I guess it doesn't report the update for the root slice. > - alex -- Brian , , Don't _EVER_ lose your sense of humour.... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 21 23:33:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA18879 for freebsd-current-outgoing; Tue, 21 Jul 1998 23:33:40 -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 XAA18874 for ; Tue, 21 Jul 1998 23:33:33 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id XAA08316; Tue, 21 Jul 1998 23:30:21 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdGw8314; Wed Jul 22 06:30:16 1998 Date: Tue, 21 Jul 1998 23:30:13 -0700 (PDT) From: Julian Elischer To: John Polstra cc: current@FreeBSD.ORG Subject: Re: vn subsystem In-Reply-To: <199807220445.VAA12195@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 ok, that's good new, however it's possible that my other box-o-tricks (devfs) may have a guilty look an its face at the moment. On Tue, 21 Jul 1998, John Polstra wrote: > > Might soft-updates be involved? > > I did a make release just last night on a system that's 100% > soft-updates. It worked for me. > -- > 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 Tue Jul 21 23:56:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA23257 for freebsd-current-outgoing; Tue, 21 Jul 1998 23:56:42 -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 XAA23242 for ; Tue, 21 Jul 1998 23:56:35 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id XAA08620; Tue, 21 Jul 1998 23:44:33 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdKV8617; Wed Jul 22 06:44:31 1998 Date: Tue, 21 Jul 1998 23:44:28 -0700 (PDT) From: Julian Elischer To: Brian Somers cc: Alex , ben@rosengart.com, current@FreeBSD.ORG Subject: Re: softupdates and / In-Reply-To: <199807220617.HAA12871@awfulhak.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 you are right.. the update doesn't get reported.. it's a debug print anyhow and should go away. (actually maybe if it DID get printed teh problem wouldn'e exist :-) julian On Wed, 22 Jul 1998, Brian Somers wrote: > > On Tue, 21 Jul 1998, Snob Art Genre wrote: > > > > > How do I enable softupdates on a root partition? I looked through the > > > mailing list archives, because I *know* I saw this go by at one point, > > > but couldn't find it. > > > > > > I'd just start trying different strategies, but this is on a remote > > > system, and it's already tricky enough. I had to temporarily add a > > > tunefs command to /etc/rc to get su enabled on /usr (does anyone know a > > > better way?). > > > > I booted into single user mode, ran tunefs -n enable on /dev/rsd0a, and > > hit reset. I'm sure something similar could be accomplished if you put > > that in a rc script that ended in reboot -n. > > > > Oddly enough, I only see one: > > ffs_mountfs: superblock updated > > Even though mount shows: > > > > zippy:~/png#mount > > /dev/sd0s1a on / (local, soft-updates, writes: sync 105 async 17719) > > /dev/sd1s1e on /mnt/usr2 (local, soft-updates, writes: sync 2 async 868) > > > > *shrug* > > > > YMMV > > My laptop has: > > Filesystem 1K-blocks Used Avail Capacity Mounted on > /dev/wd0s1a 1885583 1176081 558656 68% / > procfs 4 4 0 100% /proc > kernfs 1 1 0 100% /kern > > and I don't see any :-) I guess it doesn't report the update for the > root slice. > > > - alex > > > -- > Brian , , > > Don't _EVER_ lose your sense of humour.... > > > > 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 22 00:03:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA24257 for freebsd-current-outgoing; Wed, 22 Jul 1998 00:03:27 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from prcom.rcom.spb.su (prcom.rcom.spb.su [193.124.80.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA24241 for ; Wed, 22 Jul 1998 00:03:20 -0700 (PDT) (envelope-from dragonfa@prcom.rcom.spb.su) Received: (from dragonfa@localhost) by prcom.rcom.spb.su (8.8.8/8.8.8) id LAA10442; Wed, 22 Jul 1998 11:01:37 +0400 (MSD) (envelope-from dragonfa) From: Alexey Pialkin Message-Id: <199807220701.LAA10442@prcom.rcom.spb.su> Subject: Re: Does building current on 2.2.x still work? In-Reply-To: from Doug White at "Jul 21, 98 00:44:38 am" To: dwhite@resnet.uoregon.edu (Doug White) Date: Wed, 22 Jul 1998 11:01:37 +0400 (MSD) Cc: current@FreeBSD.ORG 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 > Okay, I give up. Can someone send the The Complete Guide to Building > -CURRENT on -STABLE? The binary format changes have made a complete mess > of things: if ld doesn't die missing ___error (when BINFORMAT=aout), it's > the assembler complaining about unknown psuedo-op .section (when > BINFORMAT=foo to bypass bsd.own.mk's misassumptions about /usr/lib vs > /usr/lib/aout in a 2.2.6-RELEASE universe). i'v tried to build -current on 2.2.6-release yestaday and done it successfully :) - i'v solved a problem with ___error by running "make world" , thus getting new lib.c and overwrting /usr/lib/libc.a with it. no problems with make world after that(i'v builded aout format). Alexey Pialkin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 22 00:48:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA01379 for freebsd-current-outgoing; Wed, 22 Jul 1998 00:48:19 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from monsoon.dial.pipex.net (monsoon.dial.pipex.net [158.43.128.69]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id AAA01332 for ; Wed, 22 Jul 1998 00:48:12 -0700 (PDT) (envelope-from pierre.dampure@k2c.co.uk) Received: (qmail 16666 invoked from network); 22 Jul 1998 07:47:50 -0000 Received: from userk794.uk.uudial.com (HELO k2c.co.uk) (193.149.72.116) by smtp.dial.pipex.com with SMTP; 22 Jul 1998 07:47:50 -0000 Message-ID: <35B598B1.8D7ECB64@k2c.co.uk> Date: Wed, 22 Jul 1998 08:45:53 +0100 From: "Pierre Y. Dampure" Organization: K2C Limited X-Mailer: Mozilla 4.05 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: FreeBSD-current@FreeBSD.ORG Subject: Current values of TTYHOG and RS_IBUFSIZE Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Over the past few weeks I've had several instances of userppp disconnecting a connection w/o particular reasons on bleeding edge -current. The only change on the box was the recent addition of a Hayes ESP card (I connect via ISDN), so I checked the archives for possible issues. Way back in 1996 (23 Nov), Brian Litzinger posted a follow-up to "Hayes ESP and interrupt-level buffer overflow" and advised altering the following constants : In /sys/sys/tty.h: TTYHOG Change to 4096 In /sys/i386/isa/sio.c RS_IBUFSIZE Change to 1024 I applied the above and haven't had any problems since -- in fact, it seems the connections are _much_ faster. Can anybody confirms whether these changes are valid and, if so, can we include them in -current (#ifdef'd via COM_ESP, of course)? Oh, on a completeley different subject, has anyone experienced problems connecting to Altavista (http://www.altavista.digital.com) recently? connection stay in ESTABLISHED state, nothing else happens. Works okay from work via a SunScreen... Best Regards, Pierre Y. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 22 00:55:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA02500 for freebsd-current-outgoing; Wed, 22 Jul 1998 00:55:16 -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 AAA02464 for ; Wed, 22 Jul 1998 00:54:52 -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 JAA21650 ; Wed, 22 Jul 1998 09:48:35 +0200 (MET DST) Received: by sunw110.oslo.Geco-Prakla.slb.com (SMI-8.6/SMI-SVR4) id JAA22751; Wed, 22 Jul 1998 09:48:34 +0200 To: joelh@gnu.org Cc: brian@Awfulhak.org, julian@whistle.com, jkh@time.cdrom.com, bright@hotjobs.com, freebsd-current@FreeBSD.ORG Subject: Re: vn subsystem References: <199807212325.AAA28587@awfulhak.org> <199807212350.SAA14507@detlev.UUCP> Organization: Schlumberger Geco-Prakla X-Disclaimer: I speak only for myself. From: smoergrd@oslo.geco-prakla.slb.com (Dag-Erling Coidan Smørgrav) Date: 22 Jul 1998 09:48:33 +0200 In-Reply-To: Joel Ray Holveck's message of Tue, 21 Jul 1998 18:50:50 -0500 (CDT) Message-ID: Lines: 14 X-Mailer: Gnus v5.3/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Joel Ray Holveck writes: > I could be mistaken, but doesn't DEVFS not list vn devices to begin > with? It does on my box. -current from about a week back. I edited /usr/src/release/Makefile to remove all the @ signs (what are they good for anyway? Better to show too much than too little IMHO) and Niobe is running make release with that Makefile right now. I'll pore over the logs when I get home from work. 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 Wed Jul 22 01:31:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA09931 for freebsd-current-outgoing; Wed, 22 Jul 1998 01:31:09 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA09852 for ; Wed, 22 Jul 1998 01:30:55 -0700 (PDT) (envelope-from kuku@gilberto.physik.RWTH-Aachen.DE) Received: from gilberto.physik.RWTH-Aachen.DE (gilberto.physik.rwth-aachen.de [137.226.30.2]) by freefall.freebsd.org (8.8.8/8.8.5) with ESMTP id BAA12182 for ; Wed, 22 Jul 1998 01:30:20 -0700 (PDT) Received: (from kuku@localhost) by gilberto.physik.RWTH-Aachen.DE (8.8.8/8.8.7) id KAA05011 for freebsd-current@freefall.cdrom.com; Wed, 22 Jul 1998 10:30:33 +0200 (MEST) (envelope-from kuku) Date: Wed, 22 Jul 1998 10:30:33 +0200 (MEST) From: Christoph Kukulies Message-Id: <199807220830.KAA05011@gilberto.physik.RWTH-Aachen.DE> To: freebsd-current@freefall.cdrom.com Subject: panic in one year old 3.0-current Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On a NFS/NIS server that serves a number of FreeBSD workstations a colleague who is doing backups over the net (using tar/rmt) told me that the server is crashing when he is trying to backup a FS over the net. I located the twp panics we had to be in these areas: The first one: /var/log/messages sagt : Jul 22 09:36:03 toots /kernel: Jul 22 09:36:03 toots /kernel: Jul 22 09:36:03 toots /kernel: Fatal trap 12: page fault while in kernel mode Jul 22 09:36:03 toots /kernel: fault virtual address = 0x64a4505d Jul 22 09:36:03 toots /kernel: fault code = supervisor write, +page not present Jul 22 09:36:03 toots /kernel: instruction pointer = 0x8:0xf0136e75 Jul 22 09:36:03 toots /kernel: stack pointer = 0x10:0xf4740ef4 Jul 22 09:36:03 toots /kernel: frame pointer = 0x10:0xf4740f58 Jul 22 09:36:04 toots /kernel: code segment = base 0x0, limit +0xfffff, type 0x1b Jul 22 09:36:04 toots /kernel: = DPL 0, pres 1, def32 1, gran +1 Jul 22 09:36:04 toots /kernel: processor eflags = interrupt enabled, resume, +IOPL = 0 Jul 22 09:36:04 toots /kernel: current process = 17629 (tar) Jul 22 09:36:04 toots /kernel: interrupt mask = Jul 22 09:36:04 toots /kernel: trap number = 12 Jul 22 09:36:04 toots /kernel: panic: page fault kernel region: f0136a8c T _rmdir f0136bec T _ogetdirentries f0136e64 T _getdirentries <<<<<< f0136e75 f0137020 T _umask f0137048 T _revoke f013715c T _getvnode f01371a0 F vfs_vnops.o and the second one: Jul 22 09:54:37 toots /kernel: Jul 22 09:54:37 toots /kernel: Jul 22 09:54:37 toots /kernel: Fatal trap 12: page fault while in kernel mode Jul 22 09:54:37 toots /kernel: fault virtual address = 0xa0004 Jul 22 09:54:37 toots /kernel: fault code = supervisor read, +page not present Jul 22 09:54:37 toots /kernel: instruction pointer = 0x8:0xf01aea28 Jul 22 09:54:37 toots /kernel: stack pointer = 0x10:0xf473ed84 Jul 22 09:54:37 toots /kernel: frame pointer = 0x10:0xf473ed98 Jul 22 09:54:37 toots /kernel: code segment = base 0x0, limit +0xfffff, type 0x1b Jul 22 09:54:37 toots /kernel: = DPL 0, pres 1, def32 1, gran +1 Jul 22 09:54:37 toots /kernel: processor eflags = interrupt enabled, resume, +IOPL = 0 Jul 22 09:54:37 toots /kernel: current process = 280 (gzip) Jul 22 09:54:37 toots /kernel: interrupt mask = net bio kernel region: f01ae694 t _pmap_remove_entry f01ae7ac t _pmap_insert_entry f01ae82c t _pmap_remove_pte f01ae8a8 t _pmap_remove_page f01ae8ec T _pmap_remove f01ae9f8 t _pmap_remove_all <<<<<<< f01aea28 f01aeb58 T _pmap_protect f01aed78 T _pmap_enter f01aefc8 t _pmap_enter_quick f01af0a0 T _pmap_object_init_pt f01af3b0 T _pmap_prefault f01af578 T _pmap_change_wiring Does anyone know if this behaviour may correlate to a meanwhile fixed bug and if it might be worth upgrading to 2.2.6-stable? -- Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 22 01:48:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA14169 for freebsd-current-outgoing; Wed, 22 Jul 1998 01:48:26 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from digger1.defence.gov.au (digger1.defence.gov.au [203.5.217.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA13639 for ; Wed, 22 Jul 1998 01:46:08 -0700 (PDT) (envelope-from Matthew.Thyer@dsto.defence.gov.au) Received: from exchsa1.dsto.defence.gov.au (exchsa1.dsto.defence.gov.au [131.185.2.94]) by digger1.defence.gov.au (8.7.5/8.7.3) with ESMTP id RAA27679; Wed, 22 Jul 1998 17:33:49 +0930 (CST) Received: from eddie.dsto.defence.gov.au ([131.185.2.111]) by exchsa1.dsto.defence.gov.au with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.1960.3) id PMP5T00K; Wed, 22 Jul 1998 15:49:37 +0930 Received: from dsto.defence.gov.au (localhost [127.0.0.1]) by eddie.dsto.defence.gov.au (8.8.8/8.8.5) with ESMTP id PAA01406; Wed, 22 Jul 1998 15:49:39 +0930 (CST) Message-ID: <35B58478.EAD74A90@dsto.defence.gov.au> Date: Wed, 22 Jul 1998 15:49:36 +0930 From: Matthew Thyer Organization: Defence Science Technology Organisation X-Mailer: Mozilla 4.05 [en] (X11; U; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: FreeBSD CURRENT CC: Julian Elischer Subject: Re: DEVFS not creating slice devices for my SCSI disks References: <35B4A583.E3F1E64F@camtech.net.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Following up my own message. Its the DEVFS probe of the disklabel that is failing to find any slices (partitions). The old kernel finds partition 0 but the new one finds none. There is no MBR on any of these SCSI disks according to all my DEVFS kernels. Is that a problem now ? Here are the disklabels (all are similar just the sizes differ): eddie: {1} disklabel -r sd1 # /dev/rsd1: type: unknown disk: label: flags: bytes/sector: 512 sectors/track: 87 tracks/cylinder: 15 sectors/cylinder: 1305 cylinders: 2120 sectors/unit: 2767245 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # milliseconds track-to-track seek: 0 # milliseconds drivedata: 0 3 partitions: # size offset fstype [fsize bsize bps/cpg] a: 2767245 0 unused 0 0 # (Cyl. 0 - 2120*) c: 2767245 0 unused 0 0 # (Cyl. 0 - 2120*) Filesystem settings: eddie: {5} tunefs -p /dev/sd1a tunefs: soft updates: (-n) disabled tunefs: maximum contiguous block count: (-a) 15 tunefs: rotational delay between contiguous blocks: (-d) 0 ms tunefs: maximum blocks per file in a cylinder group: (-e) 2048 tunefs: minimum percentage of free space: (-m) 1% tunefs: optimization preference: (-o) space extract of dmesg output for DEVFS partition probing with the new kernel: sd1: probing for MBR.. sd3: probing for MBR.. sd4: probing for MBR.. wd0: probing for MBR.. part 1, start=63, size=1169217 extracts of dmesg output: (from the CTM src-cur 3429 kernel): aha0 at 0x234-0x237 irq 11 drq 6 on isa scbus0 at aha0 bus 0 sd1 at scbus0 target 1 lun 0 sd1: type 0 fixed SCSI 2 sd1: Direct-Access 1351MB (2767245 512 byte sectors) sd3 at scbus0 target 3 lun 0 sd3: type 0 fixed SCSI 2 sd3: Direct-Access 1813MB (3713130 512 byte sectors) sd4 at scbus0 target 4 lun 0 sd4: type 0 fixed SCSI 2 sd4: Direct-Access 1812MB (3711990 512 byte sectors) DEVFS: ready to run sd1: probing for MBR.. nope sd1: probing for disklabel.. yep part 0, start=0, size=2767245 sd3: probing for MBR.. nope sd3: probing for disklabel.. yep part 0, start=0, size=3713130 sd4: probing for MBR.. nope sd4: probing for disklabel.. yep part 0, start=0, size=3711990 Matthew Thyer wrote: > > At CTM src-cur 3429 my system works fine but with kernels > of src-cur 3457 and 346? (whatever it is we're currently > up to - about 8 hours ago) DEVFS no longer has devices for > the slices of my SCSI disks. > > All I see in /dev for the SCSI disks is: /dev/sd1, /dev/sd3 > and /dev/sd4 (I have three disks wired down to their SCSI id's). > > These are old 1.3 and 1.8 GB disks (Seagates I think) which > are connected to an adaptec 1542B controller. > > The disks in question have a single 'a' slice covering the > whole disk and have filesystems that were created with either > newfs -m 0 OR newfs -m 1 (I dont recall which right now). > > Maybe the problem started after raw devices went away ? > > All kernels have SLICE and DEVFS in them. > > Any idea whats up ? > > Unfortunately all source and my home directories are on these > SCSI disks so I'm having to run with my 3429 kernel even though > I've done two make worlds since. > > Sorry I cant provide more details but the system is remote > (currently) and it hasn't come back from a boot on the newest > kernel (as it couldn't fsck the filesystems of course!) > > -- > /=====================================================================\ > |Work: Matthew.Thyer@dsto.defence.gov.au | Home: thyerm@camtech.net.au| > \=====================================================================/ > "If it is true that our Universe has a zero net value for all conserved > quantities, then it may simply be a fluctuation of the vacuum of some > larger space in which our Universe is imbedded. In answer to the > question of why it happened, I offer the modest proposal that our > Universe is simply one of those things which happen from time to time." > E. P. Tryon from "Nature" Vol.246 Dec.14, 1973 > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- Matthew Thyer Phone: +61 8 8259 7249 Corporate Information Systems Fax: +61 8 8259 5537 Defence Science and Technology Organisation, Salisbury PO Box 1500 Salisbury South Australia 5108 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 22 02:27:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA20632 for freebsd-current-outgoing; Wed, 22 Jul 1998 02:27:02 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from tyree.iii.co.uk (tyree.iii.co.uk [195.89.149.230]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA20514 for ; Wed, 22 Jul 1998 02:26:08 -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 KAA25821; Wed, 22 Jul 1998 10:25:21 +0100 (BST) Received: (from nik@localhost) by carrig.strand.iii.co.uk (8.8.8/8.8.7) id KAA15966; Wed, 22 Jul 1998 10:24:19 +0100 (BST) Message-ID: <19980722102419.29812@iii.co.uk> Date: Wed, 22 Jul 1998 10:24:19 +0100 To: Doug White Cc: John Birrell , current@FreeBSD.ORG Subject: Re: Does building current on 2.2.x still work? References: <199807210841.SAA01524@cimlogic.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.85e In-Reply-To: ; from Doug White on Tue, Jul 21, 1998 at 12:31:54PM -0700 Organization: interactive investor Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jul 21, 1998 at 12:31:54PM -0700, Doug White wrote: > On Tue, 21 Jul 1998, John Birrell wrote: > > Ahem, for the umpteenth time: > > > > cd /usr/src > > make -m /usr/src/share/mk world > > I would have, since that was the first thing I looked at when the compile > barfed. > > Or the make-world tutorial. Every time I see this suggestion posted, someone else jumps in with "But it didn't work properly for me.", which is why I haven't put it in the tutorial yet. John, if you're happy, with the following, I'll add it as 5.3 to the tutorial (bumping everything else on one). Can anyone else supply an accurate value for 'x'? 5.3 Moving from 2.2.6 to -current later than 'x' Some things changed with the -current build process on 'x', in order to support the eventual transition from the a.out object format to elf. These changes mean that the build process needs to use the new .mk files stored in /usr/src/share/mk, rather than the ones that will currently be installed in /usr/share/mk. In order to force the build process to use these files, add the parameter '-m /usr/src/share/mk' to your make command line, like so # make -m /usr/src/share/mk buildworld and # make -m /usr/src/share/mk installworld Typical symptoms of a build that has failed because of this are seeing the following errors; >> insert errors here, can anyone supply some samples? << N -- 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 Wed Jul 22 02:44:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA23616 for freebsd-current-outgoing; Wed, 22 Jul 1998 02:44:38 -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 CAA23522 for ; Wed, 22 Jul 1998 02:44:13 -0700 (PDT) (envelope-from paul@originative.co.uk) Received: by OCTOPUS with Internet Mail Service (5.5.1960.3) id ; Wed, 22 Jul 1998 10:43:39 +0100 Message-ID: From: Paul Richards To: "'John Birrell'" , dwhite@resnet.uoregon.edu Cc: nrice@emu.sourcee.com, imp@village.org, current@FreeBSD.ORG Subject: RE: Does building current on 2.2.x still work? Date: Wed, 22 Jul 1998 10:43:36 +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 Would it make sense to install the new mk files during the bootstrap target. The original idea I had for the bootstrap target was to deal with precisely these things, carry out steps required to bootstrap from the previously released version to current. It does mean that you get the mew mk files installed even if the build subsequently fails and you don't install the new version, would this cause any problems since you'd be working with new Makefiles anyway if you'd upgraded your sources to run the bootstrap in the first place. I successfully upgraded from 2.2.5 to current by doing cd /usr/src/share/mk make install and then doing a make world as normal. If there's no other problems just add the above step to bootstrap and make bootstrap the first stage of make world as it was meant to be. Paul Richards Ph.D. Originative Solutions Ltd > -----Original Message----- > From: John Birrell [mailto:jb@cimlogic.com.au] > Sent: Tuesday, July 21, 1998 11:38 PM > To: dwhite@resnet.uoregon.edu > Cc: nrice@emu.sourcee.com; imp@village.org; current@FreeBSD.ORG > Subject: Re: Does building current on 2.2.x still work? > > > Doug White wrote: > > I know that the ___error problem spawns from a libc version > conflict. > > No it doesn't. It results from the world/buildworld not using > -nostdlib > and not finding the libraries it has just built because the library > path is incorrectly set to /usr/obj/usr/src/usr/lib instead of > /usr/obj/usr/src/usr/lib/aout. This is the result of using > old installed > .mk files, hence the need for the -m argument. Changing libc versions > would not have any effect. > > -- > 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 22 02:45:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA23754 for freebsd-current-outgoing; Wed, 22 Jul 1998 02:45:17 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA23706 for ; Wed, 22 Jul 1998 02:44:57 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id JAA10077; Wed, 22 Jul 1998 09:43:49 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id LAA29612; Wed, 22 Jul 1998 11:43:49 +0200 (MET DST) Message-ID: <19980722114348.48281@follo.net> Date: Wed, 22 Jul 1998 11:43:48 +0200 From: Eivind Eklund To: Matthew Thyer , FreeBSD CURRENT Cc: Julian Elischer Subject: Re: DEVFS not creating slice devices for my SCSI disks References: <35B4A583.E3F1E64F@camtech.net.au> <35B58478.EAD74A90@dsto.defence.gov.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <35B58478.EAD74A90@dsto.defence.gov.au>; from Matthew Thyer on Wed, Jul 22, 1998 at 03:49:36PM +0930 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jul 22, 1998 at 03:49:36PM +0930, Matthew Thyer wrote: > Following up my own message. > > Its the DEVFS probe of the disklabel that is failing to find > any slices (partitions). > > The old kernel finds partition 0 but the new one finds none. > > There is no MBR on any of these SCSI disks according to all my > DEVFS kernels. Is that a problem now ? > > Here are the disklabels (all are similar just the sizes differ): > > eddie: {1} disklabel -r sd1 > # /dev/rsd1: > type: unknown This should say 'SCSI', I think. I don't remember exactly which effects you'll get by having it wrong, but they'll clearly be there. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 22 02:45:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA23815 for freebsd-current-outgoing; Wed, 22 Jul 1998 02:45:36 -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 CAA23751 for ; Wed, 22 Jul 1998 02:45:12 -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 TAA09666; Wed, 22 Jul 1998 19:44:46 +1000 Date: Wed, 22 Jul 1998 19:44:46 +1000 From: Bruce Evans Message-Id: <199807220944.TAA09666@godzilla.zeta.org.au> To: FreeBSD-current@FreeBSD.ORG, pierre.dampure@k2c.co.uk Subject: Re: Current values of TTYHOG and RS_IBUFSIZE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Way back in 1996 (23 Nov), Brian Litzinger posted a follow-up to "Hayes >ESP and interrupt-level buffer overflow" and advised altering the >following constants : > > In /sys/sys/tty.h: TTYHOG Change to 4096 > In /sys/i386/isa/sio.c RS_IBUFSIZE Change to 1024 > >I applied the above and haven't had any problems since -- in fact, it >seems the connections are _much_ faster. > >Can anybody confirms whether these changes are valid and, if so, can we >include them in -current (#ifdef'd via COM_ESP, of course)? These changes waste a lot of memory for ptys and any other non-ESP ttys, and don't get input flow control quite right (due to hard-coded 256's in tty.c). -current has support for allocating correctly sized buffers depending on the device type and port speed, but nothing actually uses this yet. The changes to use if for normal sio ports are something like: *** sio.c~ Wed Jul 15 22:30:11 1998 --- sio.c Wed Jul 15 22:30:15 1998 *************** *** 106,109 **** #define LOTS_OF_EVENTS 64 /* helps separate urgent events from input */ - #define RB_I_HIGH_WATER (TTYHOG - 2 * RS_IBUFSIZE) #define RS_IBUFSIZE 256 --- 110,112 ---- #define LOTS_OF_EVENTS 64 /* helps separate urgent events from input */ #define RS_IBUFSIZE 256 *************** *** 1190,1191 **** --- 1217,1221 ---- ? com->it_out : com->it_in; + tp->t_ififosize = 2 * RS_IBUFSIZE; + tp->t_ispeedwat = (speed_t)-1; + tp->t_ospeedwat = (speed_t)-1; (void)commctl(com, TIOCM_DTR | TIOCM_RTS, DMSET); *************** *** 1201,1203 **** */ - ttsetwater(tp); iobase = com->iobase; --- 1231,1232 ---- *************** *** 1983,1985 **** if (tp->t_state & TS_CAN_BYPASS_L_RINT) { ! if (tp->t_rawq.c_cc + incc >= RB_I_HIGH_WATER && (com->state & CS_RTS_IFLOW --- 2081,2083 ---- if (tp->t_state & TS_CAN_BYPASS_L_RINT) { ! if (tp->t_rawq.c_cc + incc > tp->t_ihiwat && (com->state & CS_RTS_IFLOW This gives an effective TTYHOG of about 11520 for 115200 bps, etc. RS_IBUFSIZE still needs to be increased for speeds larger than 115200 bps. RS_IBUFSIZE and/or tp->t_ififosize needs to be increased for hardware with large h/w fifos like the ESP. 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 22 02:47:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA24133 for freebsd-current-outgoing; Wed, 22 Jul 1998 02:47:14 -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 CAA23869 for ; Wed, 22 Jul 1998 02:45:49 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.8/8.8.7) id UAA04499; Wed, 22 Jul 1998 20:02:57 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199807221002.UAA04499@cimlogic.com.au> Subject: Re: Does building current on 2.2.x still work? In-Reply-To: <19980722102419.29812@iii.co.uk> from "nik@iii.co.uk" at "Jul 22, 98 10:24:19 am" To: nik@iii.co.uk Date: Wed, 22 Jul 1998 20:02:57 +1000 (EST) Cc: dwhite@resnet.uoregon.edu, jb@cimlogic.com.au, 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 nik@iii.co.uk wrote: > Every time I see this suggestion posted, someone else jumps in with "But > it didn't work properly for me.", which is why I haven't put it in the > tutorial yet. I sent a message (the one with the *grumble*) to this list asking people having trouble to send me private mail with the details of the problem. So far I've received a total of ZERO private mails on this subject. I can only conclude that when people follow the procedure, there is no problem. > > John, if you're happy, with the following, I'll add it as 5.3 to the > tutorial (bumping everything else on one). Can anyone else supply an > accurate value for 'x'? I don't think this is the way to word it. Anyone building -current needs to allow for the possibility that changes might have been made to the .mk files since the last installation on their machine. We all expect that sources in the tree are consistent so that /usr/src/Makefile should only be interpreted by make in conjunction with the .mk include files that are also in the tree. To ensure that this consistency is maintained and the world has the best chance of building, novice world builders should _always_ use the -m argument "just in case" IMHO. The fact that it is often possible to build without the -m argument should be the thing that is left undocumented. We shouldn't need to make special mention about building -current on 2.2.6 when there is a "command for all seasons" that is backed by logic. FWIW, when we've got an ELF only build, people building on an aout system will get even worse errors if they have out of date .mk files. -- 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 Wed Jul 22 02:53:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA25231 for freebsd-current-outgoing; Wed, 22 Jul 1998 02:53:50 -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 CAA25205 for ; Wed, 22 Jul 1998 02:53:36 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.8/8.8.7) id UAA04515; Wed, 22 Jul 1998 20:10:54 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199807221010.UAA04515@cimlogic.com.au> Subject: Re: Does building current on 2.2.x still work? In-Reply-To: from Paul Richards at "Jul 22, 98 10:43:36 am" To: paul@originative.co.uk (Paul Richards) Date: Wed, 22 Jul 1998 20:10:54 +1000 (EST) Cc: jb@cimlogic.com.au, dwhite@resnet.uoregon.edu, nrice@emu.sourcee.com, imp@village.org, 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 Paul Richards wrote: > Would it make sense to install the new mk files during the bootstrap > target. The original idea I had for the bootstrap target was to deal > with precisely these things, carry out steps required to bootstrap from > the previously released version to current. The issue here is that you can't necessarily parse the top level makefile without consistent .mk includes, so your bootstrap target won't be guaranteed of working. And a buildworld is not supposed to clobber things on the host system, so you have to live with old installed .mk files. The answer is: don't use them. Except for parsing the top level makefile, the current build system doesn't use the installed .mk files. When you specify the -m argument on the command line, you get a consistent build. W^5 (Which Was What We Wanted). -- 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 Wed Jul 22 03:50:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA03628 for freebsd-current-outgoing; Wed, 22 Jul 1998 03:50:12 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from hda.hda.com (hda-bicnet.bicnet.net [208.220.66.37]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA03561 for ; Wed, 22 Jul 1998 03:50:03 -0700 (PDT) (envelope-from dufault@hda.hda.com) Received: (from dufault@localhost) by hda.hda.com (8.8.5/8.8.5) id GAA24033; Wed, 22 Jul 1998 06:20:58 -0400 (EDT) From: Peter Dufault Message-Id: <199807221020.GAA24033@hda.hda.com> Subject: Re: cdrecord with 3.0-CURRENT ... In-Reply-To: <19980721154615.B1009@cons.org> from Martin Cracauer at "Jul 21, 98 03:46:15 pm" To: cracauer@cons.org (Martin Cracauer) Date: Wed, 22 Jul 1998 06:20:57 -0400 (EDT) Cc: scrappy@hub.org, doconnor@gsoft.com.au, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL25 (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 > > cdrecords checks for Posix async I/O and uses it if it's available. > > This was implemented by John Dyson in FreeBSD, but it isn't by default It checks for the Posix fixed priority scheduler implemented by me, but only checks the "this feature is supported in some configurations of this OS" and not "this feature is supported in this configuration of the OS". In my opinion, this is likely to happen for common POSIX features and those features will have to be made standard instead of changing the programs to try to detect run time configuration. It is already tough enough to implement feature detection in portable programs. Since this is a small option I think I will make it standard. Peter -- Peter Dufault (dufault@hda.com) Realtime development, Machine control, HD Associates, Inc. Safety critical systems, Agency approval To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 22 03:58:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA04984 for freebsd-current-outgoing; Wed, 22 Jul 1998 03:58:07 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from goliath.camtech.net.au (goliath.camtech.net.au [203.5.73.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA04886 for ; Wed, 22 Jul 1998 03:57:58 -0700 (PDT) (envelope-from thyerm@camtech.net.au) Received: from camtech.net.au (dialup-ad-4-16.camtech.net.au [203.28.0.144]) by goliath.camtech.net.au (8.8.5/8.8.2) with ESMTP id UAA03790; Wed, 22 Jul 1998 20:26:50 +0930 (CST) Message-ID: <35B5C599.BB45F4E1@camtech.net.au> Date: Wed, 22 Jul 1998 20:27:29 +0930 From: Matthew Thyer X-Mailer: Mozilla 4.05 [en] (X11; U; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: Eivind Eklund CC: Matthew Thyer , FreeBSD CURRENT , Julian Elischer Subject: Re: DEVFS not creating slice devices for my SCSI disks References: <35B4A583.E3F1E64F@camtech.net.au> <35B58478.EAD74A90@dsto.defence.gov.au> <19980722114348.48281@follo.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm pretty sure I labelled all three disks with the auto mode of disklabel. It's wierd that it used to work at CTM src-cur 3429 but not now. As I've just said to Julian, removing DEVFS and SLICE gives me a working system. Can I just edit these disklabels and put 'SCSI' in place of unknown without affecting the filesystems ? (I hope so!). Eivind Eklund wrote: > > On Wed, Jul 22, 1998 at 03:49:36PM +0930, Matthew Thyer wrote: > > Following up my own message. > > > > Its the DEVFS probe of the disklabel that is failing to find > > any slices (partitions). > > > > The old kernel finds partition 0 but the new one finds none. > > > > There is no MBR on any of these SCSI disks according to all my > > DEVFS kernels. Is that a problem now ? > > > > Here are the disklabels (all are similar just the sizes differ): > > > > eddie: {1} disklabel -r sd1 > > # /dev/rsd1: > > type: unknown > > This should say 'SCSI', I think. I don't remember exactly which > effects you'll get by having it wrong, but they'll clearly be there. > > Eivind. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- /=====================================================================\ |Work: Matthew.Thyer@dsto.defence.gov.au | Home: thyerm@camtech.net.au| \=====================================================================/ "If it is true that our Universe has a zero net value for all conserved quantities, then it may simply be a fluctuation of the vacuum of some larger space in which our Universe is imbedded. In answer to the question of why it happened, I offer the modest proposal that our Universe is simply one of those things which happen from time to time." E. P. Tryon from "Nature" Vol.246 Dec.14, 1973 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 22 04:06:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA07317 for freebsd-current-outgoing; Wed, 22 Jul 1998 04:06:26 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA07252 for ; Wed, 22 Jul 1998 04:06:17 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id LAA17289; Wed, 22 Jul 1998 11:05:44 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id NAA29898; Wed, 22 Jul 1998 13:05:37 +0200 (MET DST) Message-ID: <19980722130536.18609@follo.net> Date: Wed, 22 Jul 1998 13:05:36 +0200 From: Eivind Eklund To: Matthew Thyer Cc: Matthew Thyer , FreeBSD CURRENT , Julian Elischer Subject: Re: DEVFS not creating slice devices for my SCSI disks References: <35B4A583.E3F1E64F@camtech.net.au> <35B58478.EAD74A90@dsto.defence.gov.au> <19980722114348.48281@follo.net> <35B5C599.BB45F4E1@camtech.net.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <35B5C599.BB45F4E1@camtech.net.au>; from Matthew Thyer on Wed, Jul 22, 1998 at 08:27:29PM +0930 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jul 22, 1998 at 08:27:29PM +0930, Matthew Thyer wrote: > I'm pretty sure I labelled all three disks with the auto mode > of disklabel. 'auto' creates the wrong type - it hasn't got the logic to identify a SCSI-disk even if the disk comes barfing through it's code ;-) > It's wierd that it used to work at CTM src-cur 3429 but not now. > > As I've just said to Julian, removing DEVFS and SLICE gives > me a working system. > > Can I just edit these disklabels and put 'SCSI' in place of unknown > without affecting the filesystems ? (I hope so!). I can say "Yes" without taking financial responsibility here? "Yes." I know I've changed that label a couple of times, but I don't remember having done so on a running FS. I know I would do it without a second thought, at least. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 22 04:28:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA12245 for freebsd-current-outgoing; Wed, 22 Jul 1998 04:28:49 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from goliath.camtech.net.au (goliath.camtech.net.au [203.5.73.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA12218 for ; Wed, 22 Jul 1998 04:28:38 -0700 (PDT) (envelope-from thyerm@camtech.net.au) Received: from camtech.net.au (dialup-ad-4-16.camtech.net.au [203.28.0.144]) by goliath.camtech.net.au (8.8.5/8.8.2) with ESMTP id UAA07433; Wed, 22 Jul 1998 20:57:56 +0930 (CST) Message-ID: <35B5CCE3.8F198793@camtech.net.au> Date: Wed, 22 Jul 1998 20:58:35 +0930 From: Matthew Thyer X-Mailer: Mozilla 4.05 [en] (X11; U; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: Julian Elischer CC: FreeBSD CURRENT Subject: Re: DEVFS not creating slice devices for my SCSI disks References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG My second message has the extracts of dmesg you are after. I dont recall what /dev looks like for the working DEVFS kernel (CTM src-cur 3429). These disks are not dangerously dedicated (I think). I'm pretty sure I set them up with the auto mode of disklabel. Can I tell from the disklabel if they're DD or not ? Julian Elischer wrote: > > Thanks for letting me know.. > I can't think what problem you may be having, but it soulds as if I've > broken the 'format probes' for your disks.. > > how are they set up, "dangerously dedicated?" > What does /dev look liek (regarding these devices) in a working kernel. > > you say they don't find your SCSI disks.. > does it still find your root disk? > (I guess it must as you seem to be able to boot enough to look in /dev) > > can you give me a copy of 'dmesg' from such a boot? > > here's what the end of MY boot looks like: > > what does the same part of YOUR boot look like? > -- /=====================================================================\ |Work: Matthew.Thyer@dsto.defence.gov.au | Home: thyerm@camtech.net.au| \=====================================================================/ "If it is true that our Universe has a zero net value for all conserved quantities, then it may simply be a fluctuation of the vacuum of some larger space in which our Universe is imbedded. In answer to the question of why it happened, I offer the modest proposal that our Universe is simply one of those things which happen from time to time." E. P. Tryon from "Nature" Vol.246 Dec.14, 1973 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 22 04:50:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA14975 for freebsd-current-outgoing; Wed, 22 Jul 1998 04:50: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 EAA14943 for ; Wed, 22 Jul 1998 04:49:57 -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 VAA16770; Wed, 22 Jul 1998 21:49:34 +1000 Date: Wed, 22 Jul 1998 21:49:34 +1000 From: Bruce Evans Message-Id: <199807221149.VAA16770@godzilla.zeta.org.au> To: jb@cimlogic.com.au, nik@iii.co.uk Subject: Re: Does building current on 2.2.x still work? Cc: current@FreeBSD.ORG, dwhite@resnet.uoregon.edu Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> John, if you're happy, with the following, I'll add it as 5.3 to the >> tutorial (bumping everything else on one). Can anyone else supply an >> accurate value for 'x'? > >I don't think this is the way to word it. Anyone building -current needs >to allow for the possibility that changes might have been made to the >.mk files since the last installation on their machine. We all expect that >sources in the tree are consistent so that /usr/src/Makefile should only >be interpreted by make in conjunction with the .mk include files that are >also in the tree. To ensure that this consistency is maintained and the >world has the best chance of building, novice world builders should >_always_ use the -m argument "just in case" IMHO. This shouldn't be necessary. Novice world builders should expect `make world' to find the correct .mk files like it used to. >The fact that it is often possible to build without the -m argument >should be the thing that is left undocumented. We shouldn't need to >make special mention about building -current on 2.2.6 when there is >a "command for all seasons" that is backed by logic. All seasons of 2.2. -m doesn't exist in 2.1. 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 22 05:00:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA16241 for freebsd-current-outgoing; Wed, 22 Jul 1998 05:00: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 FAA16236 for ; Wed, 22 Jul 1998 05:00: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 WAA17349; Wed, 22 Jul 1998 22:00:25 +1000 Date: Wed, 22 Jul 1998 22:00:25 +1000 From: Bruce Evans Message-Id: <199807221200.WAA17349@godzilla.zeta.org.au> To: jb@cimlogic.com.au, paul@originative.co.uk Subject: Re: Does building current on 2.2.x still work? Cc: current@FreeBSD.ORG, dwhite@resnet.uoregon.edu, imp@village.org, nrice@emu.sourcee.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> Would it make sense to install the new mk files during the bootstrap >> target. The original idea I had for the bootstrap target was to deal >> with precisely these things, carry out steps required to bootstrap from >> the previously released version to current. > >The issue here is that you can't necessarily parse the top level makefile >without consistent .mk includes, so your bootstrap target won't be >guaranteed of working. And a buildworld is not supposed to clobber >things on the host system, so you have to live with old installed .mk >files. Yes, installing .mk files just to bootstrap would cause much the same problems as making the infamous `includes' target just to bootstrap. OTOH, src/Makefile is a simple Makefile; there is no reason it can't be written to work with the current set of .mk files provided they are consistent. >The answer is: don't use them. Except for parsing the top level makefile, >the current build system doesn't use the installed .mk files. When you >specify the -m argument on the command line, you get a consistent build. >W^5 (Which Was What We Wanted). Except when you specify the wrong -m arg on the command line. 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 22 05:06:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA16927 for freebsd-current-outgoing; Wed, 22 Jul 1998 05:06:45 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA16919 for ; Wed, 22 Jul 1998 05:06:44 -0700 (PDT) (envelope-from thyerm@camtech.net.au) Received: from goliath.camtech.net.au (goliath.camtech.net.au [203.5.73.2]) by freefall.freebsd.org (8.8.8/8.8.5) with ESMTP id FAA24141 for ; Wed, 22 Jul 1998 05:06:09 -0700 (PDT) Received: from camtech.net.au (dialup-ad-4-16.camtech.net.au [203.28.0.144]) by goliath.camtech.net.au (8.8.5/8.8.2) with ESMTP id VAA12119; Wed, 22 Jul 1998 21:35:26 +0930 (CST) Message-ID: <35B5D5AE.4801C673@camtech.net.au> Date: Wed, 22 Jul 1998 21:36:06 +0930 From: Matthew Thyer X-Mailer: Mozilla 4.05 [en] (X11; U; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: Christoph Kukulies CC: freebsd-current@freefall.cdrom.com Subject: Re: panic in one year old 3.0-current References: <199807220830.KAA05011@gilberto.physik.RWTH-Aachen.DE> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG NFS had lots of problems until quite recently. I was restricting my NFS use to the version 2 protocol until very recently. Now it seems to work very well with version 3 on recent current. e.g. I spent the other day building the world on a Pentium 100 with 32MB RAM running X (Netscape, fvwm2-95 and xterms) whilst at the same time I was installing various ports AND [here's the best bit]: Random playing 2 Gig worth of MPEG 1 layer 3 audio files with mpg123 version 0.59o from an NFS3 mounted directory (from a Solaris 2.5.1 system) without a hitch. I was not using any buffering with mpg123 but I did have to run it a a real time process to stop the sound breaking up. (rtprio 31 mpg123 .... ) I did this for 5 or 6 hours or so without a problem. Of course make world took a lot longer as mpg123 was using ~35% of the CPU most of the time. Paging didn't seem to be a problem as I was using about 50% of my 130 MB swap the whole time. The load average was usually between 3 and 4 most of the day. Needless to say I was very impressed as was the rest of the office. (Even the HP-UX lover had to be impressed as HP-UX 10.20 is really unstable with NFS3). Now thats thrashing the poor P100! Of course this is only a test of NFS3 client. Christoph Kukulies wrote: > > On a NFS/NIS server that serves a number of FreeBSD workstations > a colleague who is doing backups over the net (using tar/rmt) > told me that the server is crashing when he is trying to > backup a FS over the net. > > I located the twp panics we had to be in these areas: > > The first one: > > /var/log/messages sagt : > Jul 22 09:36:03 toots /kernel: > Jul 22 09:36:03 toots /kernel: > Jul 22 09:36:03 toots /kernel: Fatal trap 12: page fault while in kernel mode > Jul 22 09:36:03 toots /kernel: fault virtual address = 0x64a4505d > Jul 22 09:36:03 toots /kernel: fault code = supervisor write, > +page not present > Jul 22 09:36:03 toots /kernel: instruction pointer = 0x8:0xf0136e75 > Jul 22 09:36:03 toots /kernel: stack pointer = 0x10:0xf4740ef4 > Jul 22 09:36:03 toots /kernel: frame pointer = 0x10:0xf4740f58 > Jul 22 09:36:04 toots /kernel: code segment = base 0x0, limit > +0xfffff, type 0x1b > Jul 22 09:36:04 toots /kernel: = DPL 0, pres 1, def32 1, gran > +1 > Jul 22 09:36:04 toots /kernel: processor eflags = interrupt enabled, resume, > +IOPL = 0 > Jul 22 09:36:04 toots /kernel: current process = 17629 (tar) > Jul 22 09:36:04 toots /kernel: interrupt mask = > Jul 22 09:36:04 toots /kernel: trap number = 12 > Jul 22 09:36:04 toots /kernel: panic: page fault > > kernel region: > > f0136a8c T _rmdir > f0136bec T _ogetdirentries > f0136e64 T _getdirentries > <<<<<< f0136e75 > f0137020 T _umask > f0137048 T _revoke > f013715c T _getvnode > f01371a0 F vfs_vnops.o > > and the second one: > Jul 22 09:54:37 toots /kernel: > Jul 22 09:54:37 toots /kernel: > Jul 22 09:54:37 toots /kernel: Fatal trap 12: page fault while in kernel mode > Jul 22 09:54:37 toots /kernel: fault virtual address = 0xa0004 > Jul 22 09:54:37 toots /kernel: fault code = supervisor read, > +page > not present > Jul 22 09:54:37 toots /kernel: instruction pointer = 0x8:0xf01aea28 > Jul 22 09:54:37 toots /kernel: stack pointer = 0x10:0xf473ed84 > Jul 22 09:54:37 toots /kernel: frame pointer = 0x10:0xf473ed98 > Jul 22 09:54:37 toots /kernel: code segment = base 0x0, limit > +0xfffff, type 0x1b > Jul 22 09:54:37 toots /kernel: = DPL 0, pres 1, def32 1, gran > +1 > Jul 22 09:54:37 toots /kernel: processor eflags = interrupt enabled, resume, > +IOPL = 0 > Jul 22 09:54:37 toots /kernel: current process = 280 (gzip) > Jul 22 09:54:37 toots /kernel: interrupt mask = net bio > > kernel region: > > f01ae694 t _pmap_remove_entry > f01ae7ac t _pmap_insert_entry > f01ae82c t _pmap_remove_pte > f01ae8a8 t _pmap_remove_page > f01ae8ec T _pmap_remove > f01ae9f8 t _pmap_remove_all > <<<<<<< f01aea28 > f01aeb58 T _pmap_protect > f01aed78 T _pmap_enter > f01aefc8 t _pmap_enter_quick > f01af0a0 T _pmap_object_init_pt > f01af3b0 T _pmap_prefault > f01af578 T _pmap_change_wiring > > Does anyone know if this behaviour may correlate to a meanwhile > fixed bug and if it might be worth upgrading to 2.2.6-stable? > > -- > Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- /=====================================================================\ |Work: Matthew.Thyer@dsto.defence.gov.au | Home: thyerm@camtech.net.au| \=====================================================================/ "If it is true that our Universe has a zero net value for all conserved quantities, then it may simply be a fluctuation of the vacuum of some larger space in which our Universe is imbedded. In answer to the question of why it happened, I offer the modest proposal that our Universe is simply one of those things which happen from time to time." E. P. Tryon from "Nature" Vol.246 Dec.14, 1973 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 22 05:43:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA23046 for freebsd-current-outgoing; Wed, 22 Jul 1998 05:43:31 -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 FAA23039 for ; Wed, 22 Jul 1998 05:43:29 -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 FAA13688; Wed, 22 Jul 1998 05:41:58 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: Paul Richards cc: "'John Birrell'" , dwhite@resnet.uoregon.edu, nrice@emu.sourcee.com, imp@village.org, current@FreeBSD.ORG Subject: Re: Does building current on 2.2.x still work? In-reply-to: Your message of "Wed, 22 Jul 1998 10:43:36 BST." Date: Wed, 22 Jul 1998 05:41:58 -0700 Message-ID: <13683.901111318@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Would it make sense to install the new mk files during the bootstrap > target. The original idea I had for the bootstrap target was to deal > with precisely these things, carry out steps required to bootstrap from > the previously released version to current. Not really, since if the mk files have changed enough to cause the Makefile to not even parse properly (which is what happens in this case), how are you going to run the bootstrap target at all? :-) - 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 22 06:40:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA00864 for freebsd-current-outgoing; Wed, 22 Jul 1998 06:40:27 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA00855 for ; Wed, 22 Jul 1998 06:40:21 -0700 (PDT) (envelope-from kuku@gilberto.physik.RWTH-Aachen.DE) Received: from gilberto.physik.RWTH-Aachen.DE (gilberto.physik.rwth-aachen.de [137.226.30.2]) by freefall.freebsd.org (8.8.8/8.8.5) with ESMTP id GAA27978 for ; Wed, 22 Jul 1998 06:39:44 -0700 (PDT) Received: (from kuku@localhost) by gilberto.physik.RWTH-Aachen.DE (8.8.8/8.8.7) id PAA06052; Wed, 22 Jul 1998 15:39:30 +0200 (MEST) (envelope-from kuku) Message-ID: <19980722153930.A6043@gil.physik.rwth-aachen.de> Date: Wed, 22 Jul 1998 15:39:30 +0200 From: Christoph Kukulies To: Matthew Thyer , Christoph Kukulies Cc: freebsd-current@freefall.cdrom.com Subject: Re: panic in one year old 3.0-current References: <199807220830.KAA05011@gilberto.physik.RWTH-Aachen.DE> <35B5D5AE.4801C673@camtech.net.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91 In-Reply-To: <35B5D5AE.4801C673@camtech.net.au>; from Matthew Thyer on Wed, Jul 22, 1998 at 09:36:06PM +0930 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jul 22, 1998 at 09:36:06PM +0930, Matthew Thyer wrote: > NFS had lots of problems until quite recently. Sigh. Tell this a person to whom you always argued "I'm using FreeBSD over Linux for it's stability what networking is concerned" :-) Maybe things are even worse under Linux. NFS was indeed involved in my case alse (see below). > > I was restricting my NFS use to the version 2 protocol until very > recently. > > Now it seems to work very well with version 3 on recent current. > > e.g. I spent the other day building the world on a Pentium 100 > with 32MB RAM running X (Netscape, fvwm2-95 and xterms) whilst > at the same time I was installing various ports AND [here's the > best bit]: Random playing 2 Gig worth of MPEG 1 layer 3 audio > files with mpg123 version 0.59o from an NFS3 mounted directory > (from a Solaris 2.5.1 system) without a hitch. I was not using > any buffering with mpg123 but I did have to run it a a real time > process to stop the sound breaking up. (rtprio 31 mpg123 .... ) > > I did this for 5 or 6 hours or so without a problem. > > Of course make world took a lot longer as mpg123 was using ~35% > of the CPU most of the time. > > Paging didn't seem to be a problem as I was using about 50% of my > 130 MB swap the whole time. > > The load average was usually between 3 and 4 most of the day. > > Needless to say I was very impressed as was the rest of the office. > (Even the HP-UX lover had to be impressed as HP-UX 10.20 is really > unstable with NFS3). > > Now thats thrashing the poor P100! > > Of course this is only a test of NFS3 client. > > > Christoph Kukulies wrote: > > > > On a NFS/NIS server that serves a number of FreeBSD workstations > > a colleague who is doing backups over the net (using tar/rmt) I was errounously assuming that it was tar/rmt but it was tar with destination to a file on an NFS mounted Dec Alpha (OSF/1). > > told me that the server is crashing when he is trying to > > backup a FS over the net. > > > > I located the twp panics we had to be in these areas: > > > > The first one: > > > > /var/log/messages sagt : > > Jul 22 09:36:03 toots /kernel: > > Jul 22 09:36:03 toots /kernel: > > Jul 22 09:36:03 toots /kernel: Fatal trap 12: page fault while in kernel mode > > Jul 22 09:36:03 toots /kernel: fault virtual address = 0x64a4505d > > Jul 22 09:36:03 toots /kernel: fault code = supervisor write, > > +page not present > > Jul 22 09:36:03 toots /kernel: instruction pointer = 0x8:0xf0136e75 > > Jul 22 09:36:03 toots /kernel: stack pointer = 0x10:0xf4740ef4 > > Jul 22 09:36:03 toots /kernel: frame pointer = 0x10:0xf4740f58 > > Jul 22 09:36:04 toots /kernel: code segment = base 0x0, limit > > +0xfffff, type 0x1b > > Jul 22 09:36:04 toots /kernel: = DPL 0, pres 1, def32 1, gran > > +1 > > Jul 22 09:36:04 toots /kernel: processor eflags = interrupt enabled, resume, > > +IOPL = 0 > > Jul 22 09:36:04 toots /kernel: current process = 17629 (tar) > > Jul 22 09:36:04 toots /kernel: interrupt mask = > > Jul 22 09:36:04 toots /kernel: trap number = 12 > > Jul 22 09:36:04 toots /kernel: panic: page fault > > > > kernel region: > > > > f0136a8c T _rmdir > > f0136bec T _ogetdirentries > > f0136e64 T _getdirentries > > <<<<<< f0136e75 > > f0137020 T _umask > > f0137048 T _revoke > > f013715c T _getvnode > > f01371a0 F vfs_vnops.o > > > > and the second one: > > Jul 22 09:54:37 toots /kernel: > > Jul 22 09:54:37 toots /kernel: > > Jul 22 09:54:37 toots /kernel: Fatal trap 12: page fault while in kernel mode > > Jul 22 09:54:37 toots /kernel: fault virtual address = 0xa0004 > > Jul 22 09:54:37 toots /kernel: fault code = supervisor read, > > +page > > not present > > Jul 22 09:54:37 toots /kernel: instruction pointer = 0x8:0xf01aea28 > > Jul 22 09:54:37 toots /kernel: stack pointer = 0x10:0xf473ed84 > > Jul 22 09:54:37 toots /kernel: frame pointer = 0x10:0xf473ed98 > > Jul 22 09:54:37 toots /kernel: code segment = base 0x0, limit > > +0xfffff, type 0x1b > > Jul 22 09:54:37 toots /kernel: = DPL 0, pres 1, def32 1, gran > > +1 > > Jul 22 09:54:37 toots /kernel: processor eflags = interrupt enabled, resume, > > +IOPL = 0 > > Jul 22 09:54:37 toots /kernel: current process = 280 (gzip) > > Jul 22 09:54:37 toots /kernel: interrupt mask = net bio > > > > kernel region: > > > > f01ae694 t _pmap_remove_entry > > f01ae7ac t _pmap_insert_entry > > f01ae82c t _pmap_remove_pte > > f01ae8a8 t _pmap_remove_page > > f01ae8ec T _pmap_remove > > f01ae9f8 t _pmap_remove_all > > <<<<<<< f01aea28 > > f01aeb58 T _pmap_protect > > f01aed78 T _pmap_enter > > f01aefc8 t _pmap_enter_quick > > f01af0a0 T _pmap_object_init_pt > > f01af3b0 T _pmap_prefault > > f01af578 T _pmap_change_wiring > > > > Does anyone know if this behaviour may correlate to a meanwhile > > fixed bug and if it might be worth upgrading to 2.2.6-stable? > > > > -- > > Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > -- > /=====================================================================\ > |Work: Matthew.Thyer@dsto.defence.gov.au | Home: thyerm@camtech.net.au| > \=====================================================================/ > "If it is true that our Universe has a zero net value for all conserved > quantities, then it may simply be a fluctuation of the vacuum of some > larger space in which our Universe is imbedded. In answer to the > question of why it happened, I offer the modest proposal that our > Universe is simply one of those things which happen from time to time." > E. P. Tryon from "Nature" Vol.246 Dec.14, 1973 -- --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 22 07:11:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA04797 for freebsd-current-outgoing; Wed, 22 Jul 1998 07:11:53 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA04787 for ; Wed, 22 Jul 1998 07:11:45 -0700 (PDT) (envelope-from thyerm@camtech.net.au) Received: from goliath.camtech.net.au (goliath.camtech.net.au [203.5.73.2]) by freefall.freebsd.org (8.8.8/8.8.5) with ESMTP id HAA28204 for ; Wed, 22 Jul 1998 07:11:09 -0700 (PDT) Received: from camtech.net.au (dialup-ad-4-16.camtech.net.au [203.28.0.144]) by goliath.camtech.net.au (8.8.5/8.8.2) with ESMTP id XAA27342; Wed, 22 Jul 1998 23:40:07 +0930 (CST) Message-ID: <35B5F2E8.5818B999@camtech.net.au> Date: Wed, 22 Jul 1998 23:40:48 +0930 From: Matthew Thyer X-Mailer: Mozilla 4.05 [en] (X11; U; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: Christoph Kukulies CC: freebsd-current@freefall.cdrom.com Subject: Re: panic in one year old 3.0-current References: <199807220830.KAA05011@gilberto.physik.RWTH-Aachen.DE> <35B5D5AE.4801C673@camtech.net.au> <19980722153930.A6043@gil.physik.rwth-aachen.de> Content-Type: multipart/digest; boundary="------------560EF5681BD84399B9C30AD0" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------560EF5681BD84399B9C30AD0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit The attached messages will give you some idea on how recently NFS has been a major problem. It is so much better now that I think your should upgrade your machines to current as of now. There are still some rumours (not just rumours I think) of the odd niggling VM bug but overall current is in quite good shape as of a few hours ago (when I last built the world). I'm not one to comment on internals I'm just going on daily use (and abuse) of two current systems which I regularly update. Ask Peter Wemm for his opinion on the current state of NFS. I suspect there are still some problems in abnormal situations (NFS server crash may still be confusing the NFS client). Christoph Kukulies wrote: > > On Wed, Jul 22, 1998 at 09:36:06PM +0930, Matthew Thyer wrote: > > NFS had lots of problems until quite recently. > > Sigh. Tell this a person to whom you always argued "I'm using FreeBSD > over Linux for it's stability what networking is concerned" :-) > Maybe things are even worse under Linux. > > NFS was indeed involved in my case alse (see below). > > > > > I was restricting my NFS use to the version 2 protocol until very > > recently. > > > > Now it seems to work very well with version 3 on recent current. > -- > --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de -- /=====================================================================\ |Work: Matthew.Thyer@dsto.defence.gov.au | Home: thyerm@camtech.net.au| \=====================================================================/ "If it is true that our Universe has a zero net value for all conserved quantities, then it may simply be a fluctuation of the vacuum of some larger space in which our Universe is imbedded. In answer to the question of why it happened, I offer the modest proposal that our Universe is simply one of those things which happen from time to time." E. P. Tryon from "Nature" Vol.246 Dec.14, 1973 --------------560EF5681BD84399B9C30AD0 Received: from y.physics.usyd.edu.au (y.physics.usyd.edu.au [129.78.129.110]) by goliath.camtech.net.au (8.8.5/8.8.2) with ESMTP id AAA29105 for ; Mon, 1 Jun 1998 00:57:40 +0930 (CST) Received: from hub.freebsd.org (hub.FreeBSD.ORG [204.216.27.18]) by y.physics.usyd.edu.au (8.8.5/8.8.2) with ESMTP id BAA01353; Mon, 1 Jun 1998 01:30:19 +1000 (EST) Received: from localhost (daemon@localhost) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id HAA00950; Sun, 31 May 1998 07:53:59 -0700 (PDT) (envelope-from owner-freebsd-current) Received: by hub.freebsd.org (bulk_mailer v1.6); Sun, 31 May 1998 07:51:37 -0700 Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA00438 for freebsd-current-outgoing; Sun, 31 May 1998 07:51:37 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA00415 for ; Sun, 31 May 1998 07:51:30 -0700 (PDT) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id JAA01243; Sun, 31 May 1998 09:51:05 -0500 (EST) (envelope-from toor) From: "John S. Dyson" Message-Id: <199805311451.JAA01243@dyson.iquest.net> Subject: Re: jumbo nfs commit comming up soon... (ie: in a few hours) In-Reply-To: <199805311053.SAA02491@spinner.netplex.com.au> from Peter Wemm at "May 31, 98 06:53:55 pm" To: peter@netplex.com.au (Peter Wemm) Date: Sun, 31 May 1998 09:51:05 -0500 (EST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.ORG Content-Type: text/plain; charset=US-ASCII > I've got a series of large NFS commits coming up shortly. 'cvs diff -u | > wc -l sys/nfs' is in the order of 6000 lines, so I'll try and break it up > into smaller components where practical. > > This means that while things are in transit, the kernel and/or utilities > may well not compile. Don't be too suprised if your world falls over if > you try and build from sources mid-commit. (I have not checked all the > userland stuff yet, amd in particular). > > One of the bigger components is a long -> int32_t change for Alpha and > other 64 bit support. > It is *wonderful* that you are making progress on NFS. That is one of our major problems, and making progress on that is a major contribution. A personal thank you!!! John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message --------------560EF5681BD84399B9C30AD0 Received: from y.physics.usyd.edu.au (y.physics.usyd.edu.au [129.78.129.110]) by goliath.camtech.net.au (8.8.5/8.8.2) with ESMTP id CAA16865 for ; Wed, 22 Apr 1998 02:00:21 +0930 (CST) Received: from hub.freebsd.org (hub.FreeBSD.ORG [204.216.27.18]) by y.physics.usyd.edu.au (8.8.5/8.8.2) with ESMTP id CAA19082; Wed, 22 Apr 1998 02:32:36 +1000 (EST) Received: from localhost (daemon@localhost) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA07951; Tue, 21 Apr 1998 09:32:29 -0700 (PDT) (envelope-from owner-freebsd-current) Received: by hub.freebsd.org (bulk_mailer v1.6); Tue, 21 Apr 1998 09:23:13 -0700 Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA05977 for freebsd-current-outgoing; Tue, 21 Apr 1998 09:23:11 -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 QAA05941 for ; Tue, 21 Apr 1998 16:23:03 GMT (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.8.8/8.8.5) id KAA23401; Tue, 21 Apr 1998 10:22:54 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199804211622.KAA23401@panzer.plutotech.com> Subject: Re: NFS corruption In-Reply-To: <199804210559.PAA09123@troll.dtir.qld.gov.au> from Stephen McKay at "Apr 21, 98 03:59:47 pm" To: syssgm@dtir.qld.gov.au (Stephen McKay) Date: Tue, 21 Apr 1998 10:22:54 -0600 (MDT) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.ORG Content-Type: text/plain; charset=US-ASCII Stephen McKay wrote... > NFS is eating my .depend files during a make world. I can confirm this, but not from make world. I've got a source tree here that blows up when I compile over NFS. > The client is a Compaq Prolinea 486SX33 with 12Mb ram and 2 small SCSI-1 > disks on an Adaptec 1542b. The server is a pentium 133 with 32Mb ram and > 2 4Gb IBM UW SCSI disks on a FirePort 40 (ncr 875). > > The source and objects are on the server and NFS mounted to the client. The > client mounts src readonly and obj read-write (and async, if that does > anything under NFS). I have a similar setup, except the source and objects are in the same place, and the mount is r/w and not async. > The client kernel (and userland) is -current from April 19 (April 18 US time), > and has DIAGNOSTIC set. The server is -current from March 12, just before > the big VM changes. In my case, the client is from a week or two ago, and the server kernel was built from yesterday's sources. > Memory is short on the client, so paging is brisk. There is plenty of > swap space free. I don't run CAM or softupdates. I'm running CAM, I don't think that has anything to do with it. The client only has 24MB of memory, but it doesn't look like I'm running into swap at all: Device 1K-blocks Used Avail Capacity Type /dev/da0b 122880 0 122752 0% Interleaved > I ran 'make -j2 buildworld' and several hours later observed unusual error > messages complaining about garbage in .depend files. Many .depend files > were affected. Each .depend file was broken similarly. They would start > normally, then the corruption would start on a page boundary (multiple of > 0x1000), but *not* extend as far as the next page boundary. The corruption > was either C source, or C preprocessor output overwriting the normal contents. Right, I have the same problem. The corruption in the .depend files starts exactly at 0x1000, and continues on for a while, but not for a full page. From what Karl says, John is already aware of the problem. I just thought I'd confirm your findings... Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message --------------560EF5681BD84399B9C30AD0 Received: from y.physics.usyd.edu.au (y.physics.usyd.edu.au [129.78.129.110]) by goliath.camtech.net.au (8.8.5/8.8.2) with ESMTP id VAA16038 for ; Tue, 21 Apr 1998 21:20:41 +0930 (CST) Received: from hub.freebsd.org (hub.FreeBSD.ORG [204.216.27.18]) by y.physics.usyd.edu.au (8.8.5/8.8.2) with ESMTP id VAA17261; Tue, 21 Apr 1998 21:52:41 +1000 (EST) Received: from localhost (daemon@localhost) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id EAA23100; Tue, 21 Apr 1998 04:52:36 -0700 (PDT) (envelope-from owner-freebsd-current) Received: by hub.freebsd.org (bulk_mailer v1.6); Tue, 21 Apr 1998 04:46:44 -0700 Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA21918 for freebsd-current-outgoing; Tue, 21 Apr 1998 04:46:37 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from conductor.synapse.net (conductor.synapse.net [199.84.54.18]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id LAA21895 for ; Tue, 21 Apr 1998 11:46:25 GMT (envelope-from evanc@synapse.net) Received: (qmail 15971 invoked from network); 21 Apr 1998 11:46:24 -0000 Received: from cpu1970.adsl.bellglobal.com (HELO cello) (206.47.37.201) by conductor.synapse.net with SMTP; 21 Apr 1998 11:46:24 -0000 Message-ID: <008401bd6d1b$1c5ddd20$c9252fce@cello.synapse.net> From: "Evan Champion" To: , "Stephen McKay" Cc: Subject: Re: NFS corruption Date: Tue, 21 Apr 1998 07:46:23 -0400 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.ORG Content-Type: text/plain; charset="iso-8859-1" >I ran 'make -j2 buildworld' and several hours later observed unusual error >messages complaining about garbage in .depend files. Many .depend files >were affected. Each .depend file was broken similarly. They would start >normally, then the corruption would start on a page boundary (multiple of >0x1000), but *not* extend as far as the next page boundary. The corruption >was either C source, or C preprocessor output overwriting the normal contents. I have similar results, on 2.2.6-STABLE. I have also in the past seen the .depend's full of nulls. The only major difference is that my entire .depend is preprocessor output, and not just a page-worth. Mounting with nfsv2 seemed to have fixed that problem, but then I ran in to dead .nfs* files being left around, which caused grief elsewhere. I haven't been able to build over NFS since at least March, possibly even January or February. Evan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message --------------560EF5681BD84399B9C30AD0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 22 07:30:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA09012 for freebsd-current-outgoing; Wed, 22 Jul 1998 07:30:35 -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 HAA08954 for ; Wed, 22 Jul 1998 07:30:15 -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 AAA26644; Thu, 23 Jul 1998 00:29:49 +1000 Date: Thu, 23 Jul 1998 00:29:49 +1000 From: Bruce Evans Message-Id: <199807221429.AAA26644@godzilla.zeta.org.au> To: jkh@time.cdrom.com, paul@originative.co.uk Subject: Re: Does building current on 2.2.x still work? Cc: current@FreeBSD.ORG, dwhite@resnet.uoregon.edu, imp@village.org, jb@cimlogic.com.au, nrice@emu.sourcee.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> Would it make sense to install the new mk files during the bootstrap >> target. The original idea I had for the bootstrap target was to deal >> with precisely these things, carry out steps required to bootstrap from >> the previously released version to current. > >Not really, since if the mk files have changed enough to cause the >Makefile to not even parse properly (which is what happens in this >case), how are you going to run the bootstrap target at all? :-) Not for that reason. src/Makefile is doesn't use any complicated syntax. It only fails to parse because someone forgot to test for variables being defined before use in .if statements. It is easier to skip this check, and similar .if statements are used in *.mk, so my fix for this problem is to ensure that the variables are defined. 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 22 07:41:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA12095 for freebsd-current-outgoing; Wed, 22 Jul 1998 07:41:24 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA12082 for ; Wed, 22 Jul 1998 07:41:19 -0700 (PDT) (envelope-from kuku@gilberto.physik.RWTH-Aachen.DE) Received: from gilberto.physik.RWTH-Aachen.DE (gilberto.physik.rwth-aachen.de [137.226.30.2]) by freefall.freebsd.org (8.8.8/8.8.5) with ESMTP id HAA29408 for ; Wed, 22 Jul 1998 07:40:39 -0700 (PDT) Received: (from kuku@localhost) by gilberto.physik.RWTH-Aachen.DE (8.8.8/8.8.7) id QAA06420; Wed, 22 Jul 1998 16:40:41 +0200 (MEST) (envelope-from kuku) Message-ID: <19980722164041.A6323@gil.physik.rwth-aachen.de> Date: Wed, 22 Jul 1998 16:40:41 +0200 From: Christoph Kukulies To: Matthew Thyer , Christoph Kukulies Cc: freebsd-current@freefall.cdrom.com Subject: Re: panic in one year old 3.0-current References: <199807220830.KAA05011@gilberto.physik.RWTH-Aachen.DE> <35B5D5AE.4801C673@camtech.net.au> <19980722153930.A6043@gil.physik.rwth-aachen.de> <35B5F2E8.5818B999@camtech.net.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91 In-Reply-To: <35B5F2E8.5818B999@camtech.net.au>; from Matthew Thyer on Wed, Jul 22, 1998 at 11:40:48PM +0930 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jul 22, 1998 at 11:40:48PM +0930, Matthew Thyer wrote: > The attached messages will give you some idea on how recently > NFS has been a major problem. > > It is so much better now that I think your should upgrade your > machines to current as of now. > > There are still some rumours (not just rumours I think) of the > odd niggling VM bug but overall current is in quite good shape > as of a few hours ago (when I last built the world). I will give it a try. I have an application (8 MB image) that used to seg fault when invoked from a NFS mounted directory. That bug has been (kludge ?) fixed (dfr - Doug Rabson) 1997/05/17 in vfs_bio.c. I'll have to test this app first against -current. > > I'm not one to comment on internals I'm just going on daily use > (and abuse) of two current systems which I regularly update. > > Ask Peter Wemm for his opinion on the current state of NFS. > > I suspect there are still some problems in abnormal situations > (NFS server crash may still be confusing the NFS client). > > > Christoph Kukulies wrote: > > > > On Wed, Jul 22, 1998 at 09:36:06PM +0930, Matthew Thyer wrote: > > > NFS had lots of problems until quite recently. > > > > Sigh. Tell this a person to whom you always argued "I'm using FreeBSD > > over Linux for it's stability what networking is concerned" :-) > > Maybe things are even worse under Linux. > > > > NFS was indeed involved in my case alse (see below). > > > > > > > > I was restricting my NFS use to the version 2 protocol until very > > > recently. > > > > > > Now it seems to work very well with version 3 on recent current. > > > > -- > > --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de > > -- > /=====================================================================\ > |Work: Matthew.Thyer@dsto.defence.gov.au | Home: thyerm@camtech.net.au| > \=====================================================================/ > "If it is true that our Universe has a zero net value for all conserved > quantities, then it may simply be a fluctuation of the vacuum of some > larger space in which our Universe is imbedded. In answer to the > question of why it happened, I offer the modest proposal that our > Universe is simply one of those things which happen from time to time." > E. P. Tryon from "Nature" Vol.246 Dec.14, 1973 > Received: from y.physics.usyd.edu.au (y.physics.usyd.edu.au [129.78.129.110]) by goliath.camtech.net.au (8.8.5/8.8.2) with ESMTP id AAA29105 for ; Mon, 1 Jun 1998 00:57:40 +0930 (CST) > Received: from hub.freebsd.org (hub.FreeBSD.ORG [204.216.27.18]) by y.physics.usyd.edu.au (8.8.5/8.8.2) with ESMTP id BAA01353; Mon, 1 Jun 1998 01:30:19 +1000 (EST) > Received: from localhost (daemon@localhost) > by hub.freebsd.org (8.8.8/8.8.8) with SMTP id HAA00950; > Sun, 31 May 1998 07:53:59 -0700 (PDT) > (envelope-from owner-freebsd-current) > Received: by hub.freebsd.org (bulk_mailer v1.6); Sun, 31 May 1998 07:51:37 -0700 > Received: (from majordom@localhost) > by hub.freebsd.org (8.8.8/8.8.8) id HAA00438 > for freebsd-current-outgoing; Sun, 31 May 1998 07:51:37 -0700 (PDT) > (envelope-from owner-freebsd-current@FreeBSD.ORG) > Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) > by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA00415 > for ; Sun, 31 May 1998 07:51:30 -0700 (PDT) > (envelope-from toor@dyson.iquest.net) > Received: (from root@localhost) > by dyson.iquest.net (8.8.8/8.8.8) id JAA01243; > Sun, 31 May 1998 09:51:05 -0500 (EST) > (envelope-from toor) > From: "John S. Dyson" > Message-Id: <199805311451.JAA01243@dyson.iquest.net> > Subject: Re: jumbo nfs commit comming up soon... (ie: in a few hours) > In-Reply-To: <199805311053.SAA02491@spinner.netplex.com.au> from Peter Wemm at "May 31, 98 06:53:55 pm" > To: peter@netplex.com.au (Peter Wemm) > Date: Sun, 31 May 1998 09:51:05 -0500 (EST) > Cc: current@FreeBSD.ORG > X-Mailer: ELM [version 2.4ME+ PL38 (25)] > MIME-Version: 1.0 > Content-Transfer-Encoding: 7bit > Sender: owner-freebsd-current@FreeBSD.ORG > X-Loop: FreeBSD.ORG > Content-Type: text/plain; charset=US-ASCII > > > I've got a series of large NFS commits coming up shortly. 'cvs diff -u | > > wc -l sys/nfs' is in the order of 6000 lines, so I'll try and break it up > > into smaller components where practical. > > > > This means that while things are in transit, the kernel and/or utilities > > may well not compile. Don't be too suprised if your world falls over if > > you try and build from sources mid-commit. (I have not checked all the > > userland stuff yet, amd in particular). > > > > One of the bigger components is a long -> int32_t change for Alpha and > > other 64 bit support. > > > It is *wonderful* that you are making progress on NFS. That is one of > our major problems, and making progress on that is a major contribution. > > A personal thank you!!! > > John > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > > Received: from y.physics.usyd.edu.au (y.physics.usyd.edu.au [129.78.129.110]) by goliath.camtech.net.au (8.8.5/8.8.2) with ESMTP id CAA16865 for ; Wed, 22 Apr 1998 02:00:21 +0930 (CST) > Received: from hub.freebsd.org (hub.FreeBSD.ORG [204.216.27.18]) by y.physics.usyd.edu.au (8.8.5/8.8.2) with ESMTP id CAA19082; Wed, 22 Apr 1998 02:32:36 +1000 (EST) > Received: from localhost (daemon@localhost) > by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA07951; > Tue, 21 Apr 1998 09:32:29 -0700 (PDT) > (envelope-from owner-freebsd-current) > Received: by hub.freebsd.org (bulk_mailer v1.6); Tue, 21 Apr 1998 09:23:13 -0700 > Received: (from majordom@localhost) > by hub.freebsd.org (8.8.8/8.8.8) id JAA05977 > for freebsd-current-outgoing; Tue, 21 Apr 1998 09:23:11 -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 QAA05941 > for ; Tue, 21 Apr 1998 16:23:03 GMT > (envelope-from ken@panzer.plutotech.com) > Received: (from ken@localhost) > by panzer.plutotech.com (8.8.8/8.8.5) id KAA23401; > Tue, 21 Apr 1998 10:22:54 -0600 (MDT) > From: "Kenneth D. Merry" > Message-Id: <199804211622.KAA23401@panzer.plutotech.com> > Subject: Re: NFS corruption > In-Reply-To: <199804210559.PAA09123@troll.dtir.qld.gov.au> from Stephen McKay at "Apr 21, 98 03:59:47 pm" > To: syssgm@dtir.qld.gov.au (Stephen McKay) > Date: Tue, 21 Apr 1998 10:22:54 -0600 (MDT) > Cc: freebsd-current@FreeBSD.ORG > X-Mailer: ELM [version 2.4ME+ PL28s (25)] > MIME-Version: 1.0 > Content-Transfer-Encoding: 7bit > Sender: owner-freebsd-current@FreeBSD.ORG > X-Loop: FreeBSD.ORG > Content-Type: text/plain; charset=US-ASCII > > Stephen McKay wrote... > > NFS is eating my .depend files during a make world. > > I can confirm this, but not from make world. I've got a source > tree here that blows up when I compile over NFS. > > > The client is a Compaq Prolinea 486SX33 with 12Mb ram and 2 small SCSI-1 > > disks on an Adaptec 1542b. The server is a pentium 133 with 32Mb ram and > > 2 4Gb IBM UW SCSI disks on a FirePort 40 (ncr 875). > > > > The source and objects are on the server and NFS mounted to the client. The > > client mounts src readonly and obj read-write (and async, if that does > > anything under NFS). > > I have a similar setup, except the source and objects are in the > same place, and the mount is r/w and not async. > > > The client kernel (and userland) is -current from April 19 (April 18 US time), > > and has DIAGNOSTIC set. The server is -current from March 12, just before > > the big VM changes. > > In my case, the client is from a week or two ago, and the server > kernel was built from yesterday's sources. > > > Memory is short on the client, so paging is brisk. There is plenty of > > swap space free. I don't run CAM or softupdates. > > I'm running CAM, I don't think that has anything to do with it. > The client only has 24MB of memory, but it doesn't look like I'm running > into swap at all: > > Device 1K-blocks Used Avail Capacity Type > /dev/da0b 122880 0 122752 0% Interleaved > > > I ran 'make -j2 buildworld' and several hours later observed unusual error > > messages complaining about garbage in .depend files. Many .depend files > > were affected. Each .depend file was broken similarly. They would start > > normally, then the corruption would start on a page boundary (multiple of > > 0x1000), but *not* extend as far as the next page boundary. The corruption > > was either C source, or C preprocessor output overwriting the normal contents. > > Right, I have the same problem. The corruption in the .depend > files starts exactly at 0x1000, and continues on for a while, but not for > a full page. > > From what Karl says, John is already aware of the problem. I just > thought I'd confirm your findings... > > > Ken > -- > Kenneth Merry > ken@plutotech.com > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > > Received: from y.physics.usyd.edu.au (y.physics.usyd.edu.au [129.78.129.110]) by goliath.camtech.net.au (8.8.5/8.8.2) with ESMTP id VAA16038 for ; Tue, 21 Apr 1998 21:20:41 +0930 (CST) > Received: from hub.freebsd.org (hub.FreeBSD.ORG [204.216.27.18]) by y.physics.usyd.edu.au (8.8.5/8.8.2) with ESMTP id VAA17261; Tue, 21 Apr 1998 21:52:41 +1000 (EST) > Received: from localhost (daemon@localhost) > by hub.freebsd.org (8.8.8/8.8.8) with SMTP id EAA23100; > Tue, 21 Apr 1998 04:52:36 -0700 (PDT) > (envelope-from owner-freebsd-current) > Received: by hub.freebsd.org (bulk_mailer v1.6); Tue, 21 Apr 1998 04:46:44 -0700 > Received: (from majordom@localhost) > by hub.freebsd.org (8.8.8/8.8.8) id EAA21918 > for freebsd-current-outgoing; Tue, 21 Apr 1998 04:46:37 -0700 (PDT) > (envelope-from owner-freebsd-current@FreeBSD.ORG) > Received: from conductor.synapse.net (conductor.synapse.net [199.84.54.18]) > by hub.freebsd.org (8.8.8/8.8.8) with SMTP id LAA21895 > for ; Tue, 21 Apr 1998 11:46:25 GMT > (envelope-from evanc@synapse.net) > Received: (qmail 15971 invoked from network); 21 Apr 1998 11:46:24 -0000 > Received: from cpu1970.adsl.bellglobal.com (HELO cello) (206.47.37.201) > by conductor.synapse.net with SMTP; 21 Apr 1998 11:46:24 -0000 > Message-ID: <008401bd6d1b$1c5ddd20$c9252fce@cello.synapse.net> > From: "Evan Champion" > To: , "Stephen McKay" > Cc: > Subject: Re: NFS corruption > Date: Tue, 21 Apr 1998 07:46:23 -0400 > MIME-Version: 1.0 > Content-Transfer-Encoding: 7bit > X-Priority: 3 > X-MSMail-Priority: Normal > X-Mailer: Microsoft Outlook Express 4.72.2106.4 > X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 > Sender: owner-freebsd-current@FreeBSD.ORG > X-Loop: FreeBSD.ORG > Content-Type: text/plain; > charset="iso-8859-1" > > >I ran 'make -j2 buildworld' and several hours later observed unusual error > >messages complaining about garbage in .depend files. Many .depend files > >were affected. Each .depend file was broken similarly. They would start > >normally, then the corruption would start on a page boundary (multiple of > >0x1000), but *not* extend as far as the next page boundary. The corruption > >was either C source, or C preprocessor output overwriting the normal > contents. > > > I have similar results, on 2.2.6-STABLE. I have also in the past seen the > .depend's full of nulls. > > The only major difference is that my entire .depend is preprocessor output, > and not just a page-worth. > > Mounting with nfsv2 seemed to have fixed that problem, but then I ran in to > dead .nfs* files being left around, which caused grief elsewhere. I haven't > been able to build over NFS since at least March, possibly even January or > February. > > Evan > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 22 07:51:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA14224 for freebsd-current-outgoing; Wed, 22 Jul 1998 07:51:35 -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 HAA14164 for ; Wed, 22 Jul 1998 07:51:15 -0700 (PDT) (envelope-from rcarter@psf.Pinyon.ORG) Received: from psf.Pinyon.ORG (ip-17-091.prc.primenet.com [207.218.17.91]) by ConSys.COM (8.8.6/8.8.6) with ESMTP id HAA13021 for ; Wed, 22 Jul 1998 07:50:44 -0700 (MST) Received: from psf.Pinyon.ORG (localhost [127.0.0.1]) by psf.Pinyon.ORG (8.8.8/8.8.7) with ESMTP id HAA27124 for ; Wed, 22 Jul 1998 07:48:39 -0700 (MST) Message-Id: <199807221448.HAA27124@psf.Pinyon.ORG> X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-current@FreeBSD.ORG Subject: Re: vn subsystem In-reply-to: Your message of "Tue, 21 Jul 1998 14:11:18 MST." <199807212111.OAA01951@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 22 Jul 1998 07:48:39 -0700 From: "Russell L. Carter" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > hrm, not really there was some traffic on the lists a few weeks/months > > > > back about it being broken, but that's all i know. > > > > > > Erm, wonderful. Can we have some commentary from someone who's > > > actually proven this either way now? Like I said, my own usage of the > > > vn driver has not shown any such instability. If someone who's > > > _actually used it_ can now comment on its instability, we'll get a lot > > > further. I griped about the vn device a month or two ago, with a small amount of primary swap and a large vn swap device I could freeze the system at will when I started swapping to the vn device. *However*, I also found and fixed a hardware problem (summertime, ambient temp increased 10F, caused a cpu to overheat) that probably was the real cause. Anyway, tossing the vn device fixed the problem then, but by chasing the (reproducible) symptoms of the real problem to a completely different spot. (As an aside, then the system was completely stable except for building the world, it would hang every time at the exact same spot in the build, hardware is so much fun :). Haven't seen any vn problems since (but haven't looked either). The origin of the vn complaints was a comment by Dyson about vn "instability" when he was in the midst of VM mods in March or thereabouts. I'm a very happy camper now, looking forward to the elf stuff coming in. Russell To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 22 07:56:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA15225 for freebsd-current-outgoing; Wed, 22 Jul 1998 07:56:34 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id HAA15219 for ; Wed, 22 Jul 1998 07:56:31 -0700 (PDT) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: by outmail.utsunomiya-u.ac.jp id AA11780; Wed, 22 Jul 1998 23:55:51 +0900 Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id AAA01298; Thu, 23 Jul 1998 00:05:06 +0900 (JST) Message-Id: <199807221505.AAA01298@zodiac.mech.utsunomiya-u.ac.jp> To: ben@rosengart.com Cc: current@FreeBSD.ORG, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: keyboard lights In-Reply-To: Your message of "Mon, 20 Jul 1998 11:48:59 -0400." References: Date: Thu, 23 Jul 1998 00:05:06 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Every once in a while, all three of my keyboard lights flash at the same >time. > >I've only noticed this in X, but I'm almost always running X, so that >doesn't necessarily mean much. > >What is this? Does the keyboard do that even when you are not touching any keys? The keyboard flashes all LEDs at once when it is resetting. Maybe the power to the keyboard is somewhat shaky? Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 22 08:54:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA24405 for freebsd-current-outgoing; Wed, 22 Jul 1998 08:54:44 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA24395 for ; Wed, 22 Jul 1998 08:54:39 -0700 (PDT) (envelope-from lee@st-lcremean.tidalwave.net) Received: from st-lcremean.tidalwave.net (root@host-e186.tidalwave.net [208.213.203.186] (may be forged)) by freefall.freebsd.org (8.8.8/8.8.5) with ESMTP id IAA00362 for ; Wed, 22 Jul 1998 08:54:18 -0700 (PDT) Received: (from lee@localhost) by st-lcremean.tidalwave.net (8.8.7/8.8.7) id KAA27782; Wed, 22 Jul 1998 10:56:18 -0400 (EDT) (envelope-from lee) Message-ID: <19980722105618.07187@st-lcremean.tidalwave.net> Date: Wed, 22 Jul 1998 10:56:18 -0400 From: Lee Cremeans To: Christoph Kukulies Cc: Matthew Thyer , freebsd-current@freefall.cdrom.com Subject: Re: panic in one year old 3.0-current Reply-To: lcremean@tidalwave.net References: <199807220830.KAA05011@gilberto.physik.RWTH-Aachen.DE> <35B5D5AE.4801C673@camtech.net.au> <19980722153930.A6043@gil.physik.rwth-aachen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.85e In-Reply-To: <19980722153930.A6043@gil.physik.rwth-aachen.de>; from Christoph Kukulies on Wed, Jul 22, 1998 at 03:39:30PM +0200 X-OS: FreeBSD 2.2.5-STABLE (soon to be 3.0-CURRENT) X-Evil: microsoft.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jul 22, 1998 at 03:39:30PM +0200, Christoph Kukulies wrote: > On Wed, Jul 22, 1998 at 09:36:06PM +0930, Matthew Thyer wrote: > > NFS had lots of problems until quite recently. > > Sigh. Tell this a person to whom you always argued "I'm using FreeBSD > over Linux for it's stability what networking is concerned" :-) > Maybe things are even worse under Linux. I understand that the Linux NFS code, such as it is in 2.0.x, is very bad, worse than the FreeBSD code ever was. -- Lee C. -- Manassas, VA, USA (WakkyMouse on DALnet #watertower) A! JW223 YWD+++^ri P&B++ SL+++^i GDF B&M KK--i MD+++i P++ I++++ Did $++ E5/10/70/3c/73ac/95/96 H2 PonPippi Ay77 M | lcremean@tidalwave.net FreeBSD/Linux/Unix hacker...Win95 and M$ evil! (go see www.freebsd.org) My home page: http://st-lcremean.tidalwave.net/~lee | finger me for geek code To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 22 09:34:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA03812 for freebsd-current-outgoing; Wed, 22 Jul 1998 09:34:58 -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 JAA03769 for ; Wed, 22 Jul 1998 09:34:40 -0700 (PDT) (envelope-from benedict@echonyc.com) Received: from localhost (benedict@localhost) by echonyc.com (8.8.7/8.8.7) with SMTP id MAA13355; Wed, 22 Jul 1998 12:33:22 -0400 (EDT) Date: Wed, 22 Jul 1998 12:33:20 -0400 (EDT) From: Snob Art Genre Reply-To: ben@rosengart.com To: Kazutaka YOKOTA cc: ben@rosengart.com, current@FreeBSD.ORG Subject: Re: keyboard lights In-Reply-To: <199807221505.AAA01298@zodiac.mech.utsunomiya-u.ac.jp> 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, 23 Jul 1998, Kazutaka YOKOTA wrote: > Does the keyboard do that even when you are not touching any keys? I think so. It's hard to tell, it's unpredictable. > The keyboard flashes all LEDs at once when it is resetting. Maybe > the power to the keyboard is somewhat shaky? I suppose so, but the connector certainly doesn't feel shaky, and I never lose keystrokes or anything. 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 Wed Jul 22 10:15:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA12589 for freebsd-current-outgoing; Wed, 22 Jul 1998 10:15:32 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA12538 for ; Wed, 22 Jul 1998 10:15:13 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id KAA00650; Wed, 22 Jul 1998 10:13:10 -0700 (PDT) Message-Id: <199807221713.KAA00650@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: ben@rosengart.com cc: Kazutaka YOKOTA , current@FreeBSD.ORG Subject: Re: keyboard lights In-reply-to: Your message of "Wed, 22 Jul 1998 12:33:20 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 22 Jul 1998 10:13:10 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Thu, 23 Jul 1998, Kazutaka YOKOTA wrote: > > > Does the keyboard do that even when you are not touching any keys? > > I think so. It's hard to tell, it's unpredictable. > > > The keyboard flashes all LEDs at once when it is resetting. Maybe > > the power to the keyboard is somewhat shaky? > > I suppose so, but the connector certainly doesn't feel shaky, and I > never lose keystrokes or anything. I used to see this on one system a while back (440FX, AMI keyboard micro, Digital (perhaps Honeywell) keyboard). I'd lose a keystroke occasionally from it. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 22 10:39:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA16106 for freebsd-current-outgoing; Wed, 22 Jul 1998 10:39:59 -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 KAA16094 for ; Wed, 22 Jul 1998 10:39:53 -0700 (PDT) (envelope-from paul@originative.co.uk) Received: by OCTOPUS with Internet Mail Service (5.5.1960.3) id ; Wed, 22 Jul 1998 18:38:44 +0100 Message-ID: From: Paul Richards To: "'John Birrell'" Cc: current@FreeBSD.ORG Subject: RE: Does building current on 2.2.x still work? Date: Wed, 22 Jul 1998 18:38:43 +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: John Birrell [mailto:jb@cimlogic.com.au] > Sent: Wednesday, July 22, 1998 11:11 AM > To: paul@originative.co.uk > Cc: jb@cimlogic.com.au; dwhite@resnet.uoregon.edu; > nrice@emu.sourcee.com; imp@village.org; current@FreeBSD.ORG > Subject: Re: Does building current on 2.2.x still work? > > > Paul Richards wrote: > > Would it make sense to install the new mk files during the bootstrap > > target. The original idea I had for the bootstrap target was to deal > > with precisely these things, carry out steps required to > bootstrap from > > the previously released version to current. > > The issue here is that you can't necessarily parse the top > level makefile > without consistent .mk includes, so your bootstrap target won't be > guaranteed of working. And a buildworld is not supposed to clobber > things on the host system, so you have to live with old installed .mk > files. Ahh, good point. > The answer is: don't use them. Except for parsing the top > level makefile, > the current build system doesn't use the installed .mk files. When you > specify the -m argument on the command line, you get a > consistent build. > W^5 (Which Was What We Wanted). Hmm, we could wrapper the Makefile with a shell script for doing builds. This is attractive in that it isolates the build process from the action that makes it happen. This may just move the dependancy but I think isolation would be much easier to achieve than with the make environment since the shell mechanism virtually never changes whereas the make environement quite often does. If we created a buildworld command script then when a developer knows that a change is going to require something extra to be done they can update the buildworld script. Bootstrap problems like this have cropped up throughout FreeBSD's history and the problem always tends to be that people just forget what the extra steps are even though they've been told. People are creatures of habit, if we habitualise them to use a 'buildworld' script then we can isolate them from the changes. I find myself typing make world sometimes and hoping for the best because I've remembered that something needed to be done but not where I saved that important email that told me what :-) Paul Richards Ph.D. Originative Solutions Ltd To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 22 10:42:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA16560 for freebsd-current-outgoing; Wed, 22 Jul 1998 10:42:21 -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 KAA16555 for ; Wed, 22 Jul 1998 10:42:15 -0700 (PDT) (envelope-from paul@originative.co.uk) Received: by OCTOPUS with Internet Mail Service (5.5.1960.3) id ; Wed, 22 Jul 1998 18:41:45 +0100 Message-ID: From: Paul Richards To: "'Bruce Evans'" Cc: current@FreeBSD.ORG Subject: RE: Does building current on 2.2.x still work? Date: Wed, 22 Jul 1998 18:41:44 +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 Well, I've replied to this once suggesting a 'buildworld' script but my other thought while I was writing it was why can't we just ensure that the top level Makefile parses in the host environment and then any bootstrapping issues could in fact be dealt with using the bootstrap target. Paul Richards Ph.D. Originative Solutions Ltd > -----Original Message----- > From: Bruce Evans [mailto:bde@zeta.org.au] > Sent: Wednesday, July 22, 1998 3:30 PM > To: jkh@time.cdrom.com; paul@originative.co.uk > Cc: current@FreeBSD.ORG; dwhite@resnet.uoregon.edu; imp@village.org; > jb@cimlogic.com.au; nrice@emu.sourcee.com > Subject: Re: Does building current on 2.2.x still work? > > > >> Would it make sense to install the new mk files during the > bootstrap > >> target. The original idea I had for the bootstrap target > was to deal > >> with precisely these things, carry out steps required to > bootstrap from > >> the previously released version to current. > > > >Not really, since if the mk files have changed enough to cause the > >Makefile to not even parse properly (which is what happens in this > >case), how are you going to run the bootstrap target at all? :-) > > Not for that reason. src/Makefile is doesn't use any complicated > syntax. It only fails to parse because someone forgot to test for > variables being defined before use in .if statements. It is easier > to skip this check, and similar .if statements are used in *.mk, > so my fix for this problem is to ensure that the variables are > defined. > > 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 22 12:03:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA00522 for freebsd-current-outgoing; Wed, 22 Jul 1998 12:03:01 -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 MAA00401 for ; Wed, 22 Jul 1998 12:02:22 -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 VAA28959; Wed, 22 Jul 1998 21:00:29 +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 UAA01651; Wed, 22 Jul 1998 20:11:56 +0200 (CEST) (envelope-from seggers@semyam.dinoco.de) Message-Id: <199807221811.UAA01651@semyam.dinoco.de> To: Kevin Day cc: current@FreeBSD.ORG, seggers@semyam.dinoco.de Subject: Re: panic: page fault while in kernel mode - from gcc In-reply-to: Your message of "Tue, 21 Jul 1998 17:24:12 CDT." <199807212224.RAA09883@home.dragondata.com> Date: Wed, 22 Jul 1998 20:11:55 +0200 From: Stefan Eggers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I was able to make gcc produce this twice - then it wouldn't do it again: SMP or not? Then I know where I have to take a closer look at when it comes to #ifdef'ed code. Stefan. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 22 12:04:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA00818 for freebsd-current-outgoing; Wed, 22 Jul 1998 12:04:14 -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 MAA00726 for ; Wed, 22 Jul 1998 12:03:48 -0700 (PDT) (envelope-from toasty@home.dragondata.com) Received: (from toasty@localhost) by home.dragondata.com (8.8.8/8.8.5) id OAA24051; Wed, 22 Jul 1998 14:03:16 -0500 (CDT) From: Kevin Day Message-Id: <199807221903.OAA24051@home.dragondata.com> Subject: Re: panic: page fault while in kernel mode - from gcc In-Reply-To: <199807221811.UAA01651@semyam.dinoco.de> from Stefan Eggers at "Jul 22, 98 08:11:55 pm" To: seggers@semyam.dinoco.de (Stefan Eggers) Date: Wed, 22 Jul 1998 14:03:16 -0500 (CDT) Cc: current@FreeBSD.ORG, seggers@semyam.dinoco.de 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 was able to make gcc produce this twice - then it wouldn't do it again: > > SMP or not? Then I know where I have to take a closer look at when it > comes to #ifdef'ed code. > > Stefan. > Yep, SMP. :) Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 22 12:09:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA02028 for freebsd-current-outgoing; Wed, 22 Jul 1998 12:09:48 -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 MAA01887 for ; Wed, 22 Jul 1998 12:08:56 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id LAA29665; Wed, 22 Jul 1998 11:54:04 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdK29648; Wed Jul 22 18:54:02 1998 Date: Wed, 22 Jul 1998 11:53:57 -0700 (PDT) From: Julian Elischer To: Brian Somers cc: "Jordan K. Hubbard" , Dag-Erling Coidan Sm rgrav , Alfred Perlstein , Joel Ray Holveck , freebsd-current@FreeBSD.ORG Subject: Re: vn subsystem In-Reply-To: <199807212325.AAA28587@awfulhak.org> 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 MAA01907 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG AHA! of course, the vn devices don't work any more in a devfs world, without devfs.. as you worked out the trick woudl be to mount a copy of devfs in the right place in the chroot environment.. now, how best to DO that?? On Wed, 22 Jul 1998, Brian Somers wrote: > Indeed. DEVFS + SLICE = make release breakage. > > I tried a quick local hack to > > mount -t devfs devfs /dev || { cd /dev; sh ./MAKEDEV std; } > > (or similar), but it didn't work first time and I hadn't the time to > try again. The problem was probably that I was already in a chrooted > environment at that point and mounts are global.... so I was trying > to mount /dev when it was already mounted and wasn't going near the > chrooted area at all.... > > > Might soft-updates be involved? > > > > > > On Tue, 21 Jul 1998, Jordan K. Hubbard wrote: > > > > > Sounds like a local configuration error - I just rolled 2 3.0 snaps in > > > a row without trouble. > > > > > > - Jordan > > > > > > > "Jordan K. Hubbard" writes: > > > > > "Works for me" > > > > > > > > > > I'd not be able to build 3.0 snapshots at all if it were broken. > > > > > > > > Well, I haven't been able to make release for quite some time now. It > > > > stops when trying to vnconfig the floppy image. > > > > > > > > DES > > > > -- > > > > Dag-Erling Smørgrav - smoergrd@oslo.geco-prakla.slb.com > > -- > Brian , , > > Don't _EVER_ lose your sense of humour.... > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 22 12:17:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA04135 for freebsd-current-outgoing; Wed, 22 Jul 1998 12:17: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 MAA04091 for ; Wed, 22 Jul 1998 12:17:39 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id MAA00444; Wed, 22 Jul 1998 12:09:32 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdiyj438; Wed Jul 22 19:09:27 1998 Date: Wed, 22 Jul 1998 12:09:20 -0700 (PDT) From: Julian Elischer To: Matthew Thyer cc: FreeBSD CURRENT Subject: Re: DEVFS not creating slice devices for my SCSI disks In-Reply-To: <35B58478.EAD74A90@dsto.defence.gov.au> 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 ok I think I see the problem... I'll get back to you with a patch.. I seem to have broken disklabel-only formatted disks. On Wed, 22 Jul 1998, Matthew Thyer wrote: > > extract of dmesg output for DEVFS partition probing with the new kernel: sd1: probing for MBR.. sd3: probing for MBR.. sd4: probing for MBR.. wd0: probing for MBR.. part 1, start=63, size=1169217 > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 22 12:38:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA08856 for freebsd-current-outgoing; Wed, 22 Jul 1998 12:38:20 -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 MAA08730; Wed, 22 Jul 1998 12:37:49 -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 VAA00864; Wed, 22 Jul 1998 21:32:27 +0200 (CEST) To: Brian Somers cc: Bruce Evans , freebsd-current@FreeBSD.ORG, jak@cetlink.net, freebsd-mobile@FreeBSD.ORG Subject: Re: tickadj -t not changing tick In-reply-to: Your message of "Tue, 21 Jul 1998 21:10:45 BST." <199807212010.VAA20743@awfulhak.org> Date: Wed, 22 Jul 1998 21:32:26 +0200 Message-ID: <862.901135946@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199807212010.VAA20743@awfulhak.org>, Brian Somers writes: >[Follow-up-to pointed at freebsd-mobile] > >> >Hmm, I have a timer problem with a Compaq Presario (notebook). It >> >seems that the timer chip (i8254 is the only one probed) is acting a It seems to me that this gadget has something which is hosed or at least doesn't react as we'd expect it to. Without access to the machine it is all but impossible for me to isolate the problem, but if you're not afraid to look at some weird C code, the right place to look is in sys/i386/isa/clock.c, startrtclock() and thereabout. What chipset does this machine use ? a compaq invention ? if so they may have done something stupid to the timers in the 8254. -- 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 Wed Jul 22 12:41:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA09577 for freebsd-current-outgoing; Wed, 22 Jul 1998 12:41:52 -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 MAA09462 for ; Wed, 22 Jul 1998 12:41:07 -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 VAA00907; Wed, 22 Jul 1998 21:35:46 +0200 (CEST) To: Bruce Evans cc: brian@Awfulhak.org, freebsd-current@FreeBSD.ORG, jak@cetlink.net Subject: Re: tickadj -t not changing tick In-reply-to: Your message of "Mon, 20 Jul 1998 16:42:39 +1000." <199807200642.QAA17899@godzilla.zeta.org.au> Date: Wed, 22 Jul 1998 21:35:46 +0200 Message-ID: <905.901136146@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199807200642.QAA17899@godzilla.zeta.org.au>, Bruce Evans writes: >>APM seems to be preventing use of the TSC timecounter. Otherwise >>the clock would go non-backwards 233/17 faster :-). > >The whole problem may be caused by APM. APM's time handling is of low >quality. As currently designed, there is only the RTC chip which is reliably keeping track of time on a APMized system, and only reading the registers is reliable, the number of interrupts and their frequency is subject to change without notice. -- 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 Wed Jul 22 16:37:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA20030 for freebsd-current-outgoing; Wed, 22 Jul 1998 16:37:20 -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 QAA20021 for ; Wed, 22 Jul 1998 16:37:15 -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 TAA21278 for ; Wed, 22 Jul 1998 19:36:59 -0400 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Sender: drosih@pop1.rpi.edu Message-Id: Date: Wed, 22 Jul 1998 19:40:55 -0400 To: current@FreeBSD.ORG From: Garance A Drosihn Subject: Perl5 as default for current Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I was just curious: Are there plans to make the "standard" perl in FreeBSD be perl5? (yes, I know perl5 is in /usr/local/bin, and that it's very easy to get to there. I am just wondering if that will ever replace the perl which is currently perl4). I do not pretend that this is critical to the future of mankind, I'm just curious what the plans are... --- 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 22 16:50:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA22568 for freebsd-current-outgoing; Wed, 22 Jul 1998 16:50:21 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mailhub.ainet.com (mailhub.ainet.com [204.30.40.29]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA22459 for ; Wed, 22 Jul 1998 16:50:07 -0700 (PDT) (envelope-from jmscott@ainet.com) Received: from ainet.com (root@ainet.com [204.30.40.6]) by mailhub.ainet.com (8.9.1/8.8.7) with SMTP id QAA09231; Wed, 22 Jul 1998 16:49:46 -0700 (PDT) (envelope-from jmscott@ainet.com) Received: from perl.ainet.com by ainet.com (4.1/SMI-4.1) id AA29883; Wed, 22 Jul 98 16:50:45 PDT Message-Id: <3.0.5.32.19980722165030.00853ae0@mail.ainet.com> X-Sender: jmscott@mail.ainet.com X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Wed, 22 Jul 1998 16:50:30 -0700 To: Garance A Drosihn , current@FreeBSD.ORG From: "Joseph M. Scott" Subject: Re: Perl5 as default for current In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG If I recall correctly this was brought up before ( at least one that I caught anyway ). I believe the bottom line was that perl5 needed to build ok with bmake. I also thought that someone had stepped up and made the needed changes. That was the last that I had heard. If I'm totally off base let me know, also there may be more to the story than just my short version. Joseph Scott jmscott@ainet.com At 07:40 PM 7/22/98 -0400, Garance A Drosihn wrote: >I was just curious: > >Are there plans to make the "standard" perl in FreeBSD be perl5? >(yes, I know perl5 is in /usr/local/bin, and that it's very easy >to get to there. I am just wondering if that will ever replace >the perl which is currently perl4). > >I do not pretend that this is critical to the future of mankind, >I'm just curious what the plans are... > >--- >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 > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 22 19:16:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA16755 for freebsd-current-outgoing; Wed, 22 Jul 1998 19:16:38 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from camel7.mindspring.com (camel7.mindspring.com [207.69.200.57]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA16748 for ; Wed, 22 Jul 1998 19:16:36 -0700 (PDT) (envelope-from adric@adric.com) Received: from adric.com (user-38lc937.dialup.mindspring.com [209.86.36.103]) by camel7.mindspring.com (8.8.5/8.8.5) with ESMTP id WAA03080 for ; Wed, 22 Jul 1998 22:16:14 -0400 (EDT) Message-ID: <35B69CF1.33EB43B5@adric.com> Date: Wed, 22 Jul 1998 22:16:17 -0400 From: Adric Organization: adric.com X-Mailer: Mozilla 4.05 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: Re: Perl5 as default for current References: <3.0.5.32.19980722165030.00853ae0@mail.ainet.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Joseph M. Scott wrote: > If I recall correctly this was brought up before ( at least one that I caught anyway ). I believe the bottom line was that perl5 needed to build ok with bmake. I also thought that someone had stepped up and made the needed changes. That was the last that I had heard. > If I'm totally off base let me know, also there may be more to the story than just my short version. I've no idea what the official line is, but perl5 built fine for me (from ports on current) and installed fine too. It took we awhile to rename and relink things so that I will always get perl5 though.. I did that because of some wacky library mismatching on libnet something ... Anyway I guess I'll re-cloak now, but put in my vote for an ln in /usr/bin to /usr/local/bin/perl , linked to whatever the latest version is (That's about how I did it, 'cept I copied perl to perl4 too) -adric (I might've used gmake, can't remember..) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 22 20:21:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA26161 for freebsd-current-outgoing; Wed, 22 Jul 1998 20:21:56 -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 UAA26156 for ; Wed, 22 Jul 1998 20:21: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 XAA20963; Wed, 22 Jul 1998 23:21:10 -0400 (EDT) Date: Wed, 22 Jul 1998 23:21:10 -0400 (EDT) From: Brian Feldman To: "Jordan K. Hubbard" cc: Alfred Perlstein , Joel Ray Holveck , freebsd-current@FreeBSD.ORG Subject: Re: vn subsystem In-Reply-To: <27156.900992019@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 Alright, it's unstable for large files. observe the following scenario and appropriate coredump: -rw-r--r-- 1 green green 528482304 Jul 22 23:11 /home/green/msdos.drv vnconfig -c -s io -s labels /dev/vn0 /home/green/msdos.drv newfs_msdos /dev/vn0 mount /dev/vn0 /msdos (oops, should this matter anyway?) mount_msdos /dev/vn0 /msdos *crash* Here follows the backtrace, I've still got the core and kernel, by the way. #0 boot (howto=256) at ../../kern/kern_shutdown.c:286 #1 0xf0119147 in panic ( fmt=0xf01c2967 "vm_fault: fault on nofault entry, addr: %lx") at ../../kern/kern_shutdown.c:427 #2 0xf01c2ae6 in vm_fault (map=0xf024f9d8, vaddr=4078645248, fault_type=3 '\003', fault_flags=0) at ../../vm/vm_fault.c:233 #3 0xf01e424c in trap_pfault (frame=0xf58977e0, usermode=0) at ../../i386/i386/trap.c:761 #4 0xf01e3eef in trap (frame={tf_es = 16, tf_ds = 16, tf_edi = -216322048, tf_esi = -213143552, tf_ebp = -175540152, tf_isp = -175540216, tf_ebx = 4096, tf_edx = -213147136, tf_ecx = 128, tf_eax = -3178496, tf_trapno = 12, tf_err = 2, tf_eip = -266459326, tf_cs = 8, tf_eflags = 66070, tf_esp = -175539904, tf_ss = -175539912}) at ../../i386/i386/trap.c:396 #5 0xf01e2742 in generic_bcopy () #6 0xf01b865f in ffs_read (ap=0xf589791c) at ../../ufs/ufs/ufs_readwrite.c:205 #7 0xf0104738 in vnstrategy (bp=0xf25a09f8) at vnode_if.h:331 #8 0xf014811e in spec_strategy (ap=0xf58979a4) at ../../miscfs/specfs/spec_vnops.c:556 #9 0xf0147829 in spec_vnoperate (ap=0xf58979a4) at ../../miscfs/specfs/spec_vnops.c:127 #10 0xf01c014d in ufs_vnoperatespec (ap=0xf58979a4) at ../../ufs/ufs/ufs_vnops.c:2305 #11 0xf01347a9 in bread (vp=0xf57f5f80, blkno=1, size=4096, cred=0x0, bpp=0xf58979f8) at vnode_if.h:891 #12 0xf014b161 in fillinusemap (pmp=0xf0cd0000) at ../../msdosfs/msdosfs_fat.c:946 #13 0xf014d16c in mountmsdosfs (devvp=0xf57f5f80, mp=0xf0c49800, p=0xf58095c0, argp=0xf5897ac0) at ../../msdosfs/msdosfs_vfsops.c:715 #14 0xf014ca75 in msdosfs_mount (mp=0xf0c49800, path=0xefbfd969 "/msdos", data=0xefbfd558 "`", ndp=0xf5897ea8, p=0xf58095c0) at ../../msdosfs/msdosfs_vfsops.c:321 #15 0xf013d6fe in mount (p=0xf58095c0, uap=0xf5897f84) at ../../kern/vfs_syscalls.c:280 #16 0xf01e4ab3 in syscall (frame={tf_es = 39, tf_ds = 39, tf_edi = 0, tf_esi = -272639639, tf_ebp = -272639784, tf_isp = -175538220, tf_ebx = 0, tf_edx = 0, tf_ecx = 0, tf_eax = 21, tf_trapno = 12, tf_err = 7, tf_eip = 21157, tf_cs = 31, tf_eflags = 582, tf_esp = -272641896, tf_ss = 39}) at ../../i386/i386/trap.c:1031 #17 0x52a5 in ?? () #18 0x107e in ?? () Cheers, Brian Feldman green@unixhelp.org On Mon, 20 Jul 1998, Jordan K. Hubbard wrote: > > hrm, not really there was some traffic on the lists a few weeks/months > > back about it being broken, but that's all i know. > > Erm, wonderful. Can we have some commentary from someone who's > actually proven this either way now? Like I said, my own usage of the > vn driver has not shown any such instability. If someone who's > _actually used it_ can now comment on its instability, we'll get a lot > further. > > - Jordan > > 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 22 21:01:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA01307 for freebsd-current-outgoing; Wed, 22 Jul 1998 21:01:56 -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 VAA01285 for ; Wed, 22 Jul 1998 21:01: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 VAA16677; Wed, 22 Jul 1998 21:00:30 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: Brian Feldman cc: Alfred Perlstein , Joel Ray Holveck , freebsd-current@FreeBSD.ORG Subject: Re: vn subsystem In-reply-to: Your message of "Wed, 22 Jul 1998 23:21:10 EDT." Date: Wed, 22 Jul 1998 21:00:30 -0700 Message-ID: <16674.901166430@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > mount /dev/vn0 /msdos (oops, should this matter anyway?) > mount_msdos /dev/vn0 /msdos Try it without the bad mount first. This sounds an awful lot like another PR which has nothing to do with vn (e.g. it would do the *same* thing if you tried to do this with a non-vn device). - 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 22 21:02:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA01496 for freebsd-current-outgoing; Wed, 22 Jul 1998 21:02: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 VAA01416 for ; Wed, 22 Jul 1998 21:02:08 -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 OAA09064; Thu, 23 Jul 1998 14:01:38 +1000 Date: Thu, 23 Jul 1998 14:01:38 +1000 From: Bruce Evans Message-Id: <199807230401.OAA09064@godzilla.zeta.org.au> To: bde@zeta.org.au, phk@critter.freebsd.dk Subject: Re: tickadj -t not changing tick Cc: brian@Awfulhak.org, freebsd-current@FreeBSD.ORG, jak@cetlink.net Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>The whole problem may be caused by APM. APM's time handling is of low >>quality. > >As currently designed, there is only the RTC chip which is reliably keeping >track of time on a APMized system, and only reading the registers is reliable, >the number of interrupts and their frequency is subject to change without >notice. The RTC is sufficiently reliable. One reason that APM's time handling is of low quality because it doesn't sync with the RTC; it just reads it. Another reason is that it doesn't honour the current spl; it uses splsoftclock() to force the ipl to the level for timeout routines. This may be just a no-op if suspend/resume are always called as timeout routines. My version of inittodr() syncs with the RTC. This takes a second or two. The delay would be bad if suspension intervals are short enough for the innaccurate reading of the RTC to casue negative times. 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 22 21:10:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA03013 for freebsd-current-outgoing; Wed, 22 Jul 1998 21:10:51 -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 VAA02993 for ; Wed, 22 Jul 1998 21:10:44 -0700 (PDT) (envelope-from tlambert@usr05.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id VAA10629; Wed, 22 Jul 1998 21:10:23 -0700 (MST) Received: from usr05.primenet.com(206.165.6.205) via SMTP by smtp03.primenet.com, id smtpd010609; Wed Jul 22 21:10:16 1998 Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id VAA14655; Wed, 22 Jul 1998 21:10:14 -0700 (MST) From: Terry Lambert Message-Id: <199807230410.VAA14655@usr05.primenet.com> Subject: Re: panic: page fault while in kernel mode - from gcc To: dg@root.com Date: Thu, 23 Jul 1998 04:10:14 +0000 (GMT) Cc: toasty@home.dragondata.com, current@FreeBSD.ORG In-Reply-To: <199807220617.XAA26587@implode.root.com> from "David Greenman" at Jul 21, 98 11:17: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 > >> This seems to indicate that the new process's page directory either hasn't > >> been allocated yet or went away for some reason. Apparantly one of several > >> new bugs that John has left us with. > >> > > > >Is there any reason why someone doesn't back out his last few batches of > >large vm changes? Apparently he was half done with some of it, and what we > >had before seemed more stable than what we have now. > > That may ultimately be what we have to do, but the fixes also fixed some > serious 'leak' style problems with the Mach derived VM system, so I'd rather > that we find the bugs and fix them rather than going back to the previous > code. FreeBSD doesn't currently include the batch of patches that Elvind saved and that John had in his home directory when it was removed, does it? What is the behaviour with those patches added in? 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 22 21:17:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA04167 for freebsd-current-outgoing; Wed, 22 Jul 1998 21:17:52 -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 VAA04159 for ; Wed, 22 Jul 1998 21:17:47 -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 AAA21395; Thu, 23 Jul 1998 00:17:09 -0400 (EDT) Date: Thu, 23 Jul 1998 00:17:09 -0400 (EDT) From: Brian Feldman To: "Jordan K. Hubbard" cc: Alfred Perlstein , Joel Ray Holveck , freebsd-current@FreeBSD.ORG Subject: Re: vn subsystem In-Reply-To: <16674.901166430@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 yep, seems to work now :/ that dang bug... I reported that bug once before I think. oh well /dev/vn0s1c 515288 208 515080 0% /msdos Cheers, Brian Feldman green@unixhelp.org On Wed, 22 Jul 1998, Jordan K. Hubbard wrote: > > mount /dev/vn0 /msdos (oops, should this matter anyway?) > > mount_msdos /dev/vn0 /msdos > > Try it without the bad mount first. This sounds an awful lot like > another PR which has nothing to do with vn (e.g. it would do the *same* > thing if you tried to do this with a non-vn device). > > - 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 22 21:22:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA05101 for freebsd-current-outgoing; Wed, 22 Jul 1998 21:22:15 -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 VAA05092 for ; Wed, 22 Jul 1998 21:22:12 -0700 (PDT) (envelope-from tlambert@usr05.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id VAA04927; Wed, 22 Jul 1998 21:21:50 -0700 (MST) Received: from usr05.primenet.com(206.165.6.205) via SMTP by smtp01.primenet.com, id smtpd004905; Wed Jul 22 21:21:47 1998 Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id VAA15337; Wed, 22 Jul 1998 21:21:43 -0700 (MST) From: Terry Lambert Message-Id: <199807230421.VAA15337@usr05.primenet.com> Subject: Re: Does building current on 2.2.x still work? To: jb@cimlogic.com.au (John Birrell) Date: Thu, 23 Jul 1998 04:21:43 +0000 (GMT) Cc: nik@iii.co.uk, dwhite@resnet.uoregon.edu, jb@cimlogic.com.au, current@FreeBSD.ORG In-Reply-To: <199807221002.UAA04499@cimlogic.com.au> from "John Birrell" at Jul 22, 98 08:02:57 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 > > Every time I see this suggestion posted, someone else jumps in with "But > > it didn't work properly for me.", which is why I haven't put it in the > > tutorial yet. > > I sent a message (the one with the *grumble*) to this list asking people > having trouble to send me private mail with the details of the problem. > So far I've received a total of ZERO private mails on this subject. > I can only conclude that when people follow the procedure, there is no > problem. I can resend this as private email if you don't read it here... 8-). The failure I see is in the if_de.c driver, which uses the version number of the build environment instead of the version number of the target environment. This is because there was code with conditional compilation checked into the 3.x source tree. Specifically, the version number is a gcc and preprocessor builtin that is statically defined, and is not dynamically determined, so even running a FreeeBSD 2.x compiler on a FreeBSD 3.x system will trigger the bug. I realize that this was imported directly to avoid maintenance issues, since the main developement platform is apparently NetBSD and the author wants to maintain a single set of sources. However (and it's a big "however"), this type of this is precisely why CVS supports vendor branches. > I don't think this is the way to word it. Anyone building -current needs > to allow for the possibility that changes might have been made to the > .mk files since the last installation on their machine. We all expect that > sources in the tree are consistent so that /usr/src/Makefile should only > be interpreted by make in conjunction with the .mk include files that are > also in the tree. To ensure that this consistency is maintained and the > world has the best chance of building, novice world builders should > _always_ use the -m argument "just in case" IMHO. Or the buildworld target should add the argument and recall make in a subshell on the user's behalf. > The fact that it is often possible to build without the -m argument > should be the thing that is left undocumented. We shouldn't need to > make special mention about building -current on 2.2.6 when there is > a "command for all seasons" that is backed by logic. Hm. 8-|. The default command (ie: no arguments) should always "do the right thing", in my book... the subshell hack is pretty trivial. > FWIW, when we've got an ELF only build, people building on an aout > system will get even worse errors if they have out of date .mk files. 8-(. 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 22 21:29:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA05911 for freebsd-current-outgoing; Wed, 22 Jul 1998 21:29:26 -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 VAA05877 for ; Wed, 22 Jul 1998 21:29:19 -0700 (PDT) (envelope-from tlambert@usr05.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id VAA06920; Wed, 22 Jul 1998 21:28:40 -0700 (MST) Received: from usr05.primenet.com(206.165.6.205) via SMTP by smtp01.primenet.com, id smtpd006848; Wed Jul 22 21:28:39 1998 Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id VAA15996; Wed, 22 Jul 1998 21:28:28 -0700 (MST) From: Terry Lambert Message-Id: <199807230428.VAA15996@usr05.primenet.com> Subject: Re: Does building current on 2.2.x still work? To: bde@zeta.org.au (Bruce Evans) Date: Thu, 23 Jul 1998 04:28:28 +0000 (GMT) Cc: jb@cimlogic.com.au, paul@originative.co.uk, current@FreeBSD.ORG, dwhite@resnet.uoregon.edu, imp@village.org, nrice@emu.sourcee.com In-Reply-To: <199807221200.WAA17349@godzilla.zeta.org.au> from "Bruce Evans" at Jul 22, 98 10:00:25 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 > Yes, installing .mk files just to bootstrap would cause much the same > problems as making the infamous `includes' target just to bootstrap. OTOH, > src/Makefile is a simple Makefile; there is no reason it can't be written > to work with the current set of .mk files provided they are consistent. I think it should just use the right ones. If necessary, it should build the new make to get the -m option for the reinvocation of make. A "worse than 'includes'" problem is DESTDIR. It means that you can't keep a buildable system while attempting to resolve the gcc 2.8.x world-buildability issues that prevent FreeBSD from switching to 2.8.x. DESTDIR overrides the gcc 2.8.x and g++ 2.8.x default include paths, putting the paths of the previous versions of the compiler ahead of the new versions. It does this because there is no seperation of "build environment" from "build target". This is particularly annoying to people who use C++, the STL, pthreads, C++ exceptions, and a number of other issues. It means that a lot of new code won't work. 8-(. For the same reasons, it's also hard to deal with the TenDRA compiler issues that FreeBSD has. 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 22 22:00:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA09527 for freebsd-current-outgoing; Wed, 22 Jul 1998 22:00:22 -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 WAA09519 for ; Wed, 22 Jul 1998 22:00:18 -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 OAA13389; Thu, 23 Jul 1998 14:59:36 +1000 Date: Thu, 23 Jul 1998 14:59:36 +1000 From: Bruce Evans Message-Id: <199807230459.OAA13389@godzilla.zeta.org.au> To: green@zone.baldcom.net, jkh@time.cdrom.com Subject: Re: vn subsystem Cc: bright@hotjobs.com, freebsd-current@FreeBSD.ORG, joelh@gnu.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> mount /dev/vn0 /msdos (oops, should this matter anyway?) >> mount_msdos /dev/vn0 /msdos > >Try it without the bad mount first. This sounds an awful lot like >another PR which has nothing to do with vn (e.g. it would do the *same* >thing if you tried to do this with a non-vn device). Panicing in the second mount() is normal here. It is caused by stale vm objbufs. 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 22 22:37:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA13842 for freebsd-current-outgoing; Wed, 22 Jul 1998 22:37:05 -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 WAA13701 for ; Wed, 22 Jul 1998 22:32:46 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.8/8.8.7) id PAA01812; Thu, 23 Jul 1998 15:32:59 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199807230532.PAA01812@cimlogic.com.au> Subject: Re: Does building current on 2.2.x still work? In-Reply-To: <199807230421.VAA15337@usr05.primenet.com> from Terry Lambert at "Jul 23, 98 04:21:43 am" To: tlambert@primenet.com (Terry Lambert) Date: Thu, 23 Jul 1998 15:32:59 +1000 (EST) Cc: jb@cimlogic.com.au, nik@iii.co.uk, dwhite@resnet.uoregon.edu, 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 Terry Lambert wrote: > I can resend this as private email if you don't read it here... 8-). Umm, that was meant for people who don't know why their build is failing. > The failure I see is in the if_de.c driver, which uses the version > number of the build environment instead of the version number of the > target environment. > > This is because there was code with conditional compilation checked > into the 3.x source tree. > > Specifically, the version number is a gcc and preprocessor builtin > that is statically defined, and is not dynamically determined, so > even running a FreeeBSD 2.x compiler on a FreeBSD 3.x system will > trigger the bug. > > I realize that this was imported directly to avoid maintenance > issues, since the main developement platform is apparently NetBSD > and the author wants to maintain a single set of sources. This is a problem with a source file, not the build system as such, so I guess it is up to whoever "looks after" the de driver in FreeBSD to comment. > Hm. 8-|. The default command (ie: no arguments) should always > "do the right thing", in my book... the subshell hack is pretty > trivial. Without the -m argument, make grabs the installed sys.mk and if this is the thing that needs to be upgraded, I can't see how it can "do the right thing". Bruce seems to think that it is possible to fix src/Makefile. I don't see how, though. [I'm sounding like a broken record, so I'd better shut up now 8-) ] -- 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 Wed Jul 22 23:29:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA19296 for freebsd-current-outgoing; Wed, 22 Jul 1998 23:29:56 -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 XAA19289 for ; Wed, 22 Jul 1998 23:29:54 -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 0yzEse-00060o-00; Thu, 23 Jul 1998 00:29:32 -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 AAA07851; Thu, 23 Jul 1998 00:32:13 -0600 (MDT) Message-Id: <199807230632.AAA07851@harmony.village.org> To: John Birrell Subject: Re: Does building current on 2.2.x still work? Cc: current@FreeBSD.ORG In-reply-to: Your message of "Thu, 23 Jul 1998 15:32:59 +1000." <199807230532.PAA01812@cimlogic.com.au> References: <199807230532.PAA01812@cimlogic.com.au> Date: Thu, 23 Jul 1998 00:32:12 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199807230532.PAA01812@cimlogic.com.au> John Birrell writes: : Without the -m argument, make grabs the installed sys.mk and if this is : the thing that needs to be upgraded, I can't see how it can "do the : right thing". Bruce seems to think that it is possible to fix src/Makefile. : I don't see how, though. [I'm sounding like a broken record, so I'd better : shut up now 8-) ] I have a silly question. Looking at src/Makefile, I see: .if (!make(world)) && (!make(buildworld)) && (!make(installworld)) .MAKEFLAGS:= -m ${.CURDIR}/share/mk ${.MAKEFLAGS} .endif Why the if? Why wouldn't you want to use share/mk always for make *world? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 22 23:37:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA20551 for freebsd-current-outgoing; Wed, 22 Jul 1998 23:37:08 -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 XAA19946 for ; Wed, 22 Jul 1998 23:33:37 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.8/8.8.7) id QAA01924; Thu, 23 Jul 1998 16:34:38 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199807230634.QAA01924@cimlogic.com.au> Subject: Re: Does building current on 2.2.x still work? In-Reply-To: <199807230632.AAA07851@harmony.village.org> from Warner Losh at "Jul 23, 98 00:32:12 am" To: imp@village.org (Warner Losh) Date: Thu, 23 Jul 1998 16:34:38 +1000 (EST) Cc: jb@cimlogic.com.au, 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: > I have a silly question. Looking at src/Makefile, I see: > > .if (!make(world)) && (!make(buildworld)) && (!make(installworld)) > .MAKEFLAGS:= -m ${.CURDIR}/share/mk ${.MAKEFLAGS} > .endif > > Why the if? Why wouldn't you want to use share/mk always for make > *world? I don't understand this either, so the question isn't silly. 8-) -- 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 Wed Jul 22 23:41:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA21443 for freebsd-current-outgoing; Wed, 22 Jul 1998 23:41:40 -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 XAA21424 for ; Wed, 22 Jul 1998 23:41:38 -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 0yzF40-00061C-00; Thu, 23 Jul 1998 00:41:16 -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 AAA07940; Thu, 23 Jul 1998 00:43:57 -0600 (MDT) Message-Id: <199807230643.AAA07940@harmony.village.org> To: John Birrell Subject: Re: Does building current on 2.2.x still work? Cc: current@FreeBSD.ORG In-reply-to: Your message of "Thu, 23 Jul 1998 16:34:38 +1000." <199807230634.QAA01924@cimlogic.com.au> References: <199807230634.QAA01924@cimlogic.com.au> Date: Thu, 23 Jul 1998 00:43:57 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199807230634.QAA01924@cimlogic.com.au> John Birrell writes: : > .if (!make(world)) && (!make(buildworld)) && (!make(installworld)) : > .MAKEFLAGS:= -m ${.CURDIR}/share/mk ${.MAKEFLAGS} : > .endif : > Why the if? Why wouldn't you want to use share/mk always for make : > *world? : : I don't understand this either, so the question isn't silly. 8-) Some experimentation shows that whem make sees this flag, it doesn't start over building. However, looking again at the problem, why not add: MACHINE_ARC?=${MACHINE} really early in src/Makefile? Would that solve the problem? Don't have a machine handy that would exhibit the problem. Time to checkout a tree on one that does... 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 23 00:01:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA23740 for freebsd-current-outgoing; Thu, 23 Jul 1998 00:01:10 -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 AAA23722 for ; Thu, 23 Jul 1998 00:01:04 -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 0yzFMo-00061e-00; Thu, 23 Jul 1998 01:00:42 -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 BAA08029; Thu, 23 Jul 1998 01:03:23 -0600 (MDT) Message-Id: <199807230703.BAA08029@harmony.village.org> To: John Birrell Subject: Re: Does building current on 2.2.x still work? Cc: current@FreeBSD.ORG In-reply-to: Your message of "Thu, 23 Jul 1998 16:54:32 +1000." <199807230654.QAA01964@cimlogic.com.au> References: <199807230654.QAA01964@cimlogic.com.au> Date: Thu, 23 Jul 1998 01:03:23 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199807230654.QAA01964@cimlogic.com.au> John Birrell writes: : No. Unless you include the correct sys.mk, you won't get the library : path correct since the 2.2.* versions of sys.mk don't know about : /usr/lib/aout. Patching src/Makefile to allow for differences in versions : of sys.mk seems the wrong thing to do. If people don't like using the -m : argument, then the top level makefile should not use anything from sys.mk. Given the number of people that have hit and will hit this problem in the future, I think some efforts should be made. Something like .if !defined(MACHINE_ARCH) MACHINE_ARCH=${MACHINE} # Default executable format .if ${MACHINE} == "alpha" BINFORMAT?= elf .else BINFORMAT?= aout .endif .if ${BINFORMAT} == aout LIBDIR= /usr/lib/aout .else LIBDIR= /usr/lib .endif .endif Would come close to doing the trick. But that's starting to get way evil, and kinda against the grain of being able to specify the LIBDIR stuff (and you'd also have to do SHLIBDIR too and who knows what else). Another option, learned from the ports system, would be to have (presented here in simplified form): world: make real-world buildworld: make real-buildworld installworld: make real-installworld And then rename the current *world targets to real-*world. and ditch the .if ... .endif around the .MAKEFLAGS line. This should ensure that we're building with the right sys.mk file at the cost of one submake (which is relatively minor all things considered). You'd still need to have the MACHINE_ARCH?= line, or need to proect where MACHINE_ARCH was used in the toplevel makefile. 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 23 00:08:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA24715 for freebsd-current-outgoing; Thu, 23 Jul 1998 00:08: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 AAA24701 for ; Thu, 23 Jul 1998 00:08:13 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.8/8.8.7) id RAA01996; Thu, 23 Jul 1998 17:09:45 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199807230709.RAA01996@cimlogic.com.au> Subject: Re: Does building current on 2.2.x still work? In-Reply-To: <199807230703.BAA08029@harmony.village.org> from Warner Losh at "Jul 23, 98 01:03:23 am" To: imp@village.org (Warner Losh) Date: Thu, 23 Jul 1998 17:09:45 +1000 (EST) Cc: jb@cimlogic.com.au, 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: > Another option, learned from the ports system, would be to have > (presented here in simplified form): > > world: > make real-world > buildworld: > make real-buildworld > installworld: > make real-installworld Try: world buildworld installworld: make -m ${.CURDIR}/share/mk -f Makefile.inc0 ${.TARGET} (e&oe) and move the guts of src/Makefile to src/Makefile.inc0 I bet there are a lot of combinations of things that people tack onto the end of the make command though. -- 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 23 00:17:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA25956 for freebsd-current-outgoing; Thu, 23 Jul 1998 00:17:41 -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 AAA25946 for ; Thu, 23 Jul 1998 00:17:37 -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 0yzFcp-00062P-00; Thu, 23 Jul 1998 01:17:15 -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 BAA08221; Thu, 23 Jul 1998 01:19:57 -0600 (MDT) Message-Id: <199807230719.BAA08221@harmony.village.org> To: John Birrell Subject: Re: Does building current on 2.2.x still work? Cc: current@FreeBSD.ORG In-reply-to: Your message of "Thu, 23 Jul 1998 17:09:45 +1000." <199807230709.RAA01996@cimlogic.com.au> References: <199807230709.RAA01996@cimlogic.com.au> Date: Thu, 23 Jul 1998 01:19:57 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199807230709.RAA01996@cimlogic.com.au> John Birrell writes: : Try: : : world buildworld installworld: : make -m ${.CURDIR}/share/mk -f Makefile.inc0 ${.TARGET} : : (e&oe) and move the guts of src/Makefile to src/Makefile.inc0 : : I bet there are a lot of combinations of things that people tack : onto the end of the make command though. What would be needed that isn't covered in ${MAKE} and ${.MAKEFLAGS}? The value of BAZ in make foo BAZ=blah gets passed down to sub-makes, and .MAKEFLAGS takes care of the rest. What would be missing? *: cd ${.CURDIR}; ${MAKE} -m ${.CURDIR}/share/mk -f Makefile.inc0 ${.TARGET} (well, where * gets expanded by humans to all the desirable targets in the current src/Makefile). 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 23 00:26:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA27435 for freebsd-current-outgoing; Thu, 23 Jul 1998 00:26:21 -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 AAA27286 for ; Thu, 23 Jul 1998 00:25:57 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.8/8.8.7) id RAA02053; Thu, 23 Jul 1998 17:27:46 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199807230727.RAA02053@cimlogic.com.au> Subject: Re: Does building current on 2.2.x still work? In-Reply-To: <199807230719.BAA08221@harmony.village.org> from Warner Losh at "Jul 23, 98 01:19:57 am" To: imp@village.org (Warner Losh) Date: Thu, 23 Jul 1998 17:27:46 +1000 (EST) Cc: jb@cimlogic.com.au, 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: > What would be needed that isn't covered in ${MAKE} and ${.MAKEFLAGS}? > The value of BAZ in make foo BAZ=blah gets passed down to sub-makes, > and .MAKEFLAGS takes care of the rest. What would be missing? I don't know of anything that would be missing, but I'm not sure how to test this to avoid making the cure worse than the disease. > > *: > cd ${.CURDIR}; ${MAKE} -m ${.CURDIR}/share/mk -f Makefile.inc0 ${.TARGET} > > (well, where * gets expanded by humans to all the desirable targets in > the current src/Makefile). I guess "desirable targets" could be interpreted as "all targets we want to make visible" to Joe Novice. I don't know if this design would gain popular support. -- 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 23 00:31:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA28111 for freebsd-current-outgoing; Thu, 23 Jul 1998 00:31:12 -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 AAA27862 for ; Thu, 23 Jul 1998 00:29:42 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.8/8.8.7) id QAA01964; Thu, 23 Jul 1998 16:54:32 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199807230654.QAA01964@cimlogic.com.au> Subject: Re: Does building current on 2.2.x still work? In-Reply-To: <199807230643.AAA07940@harmony.village.org> from Warner Losh at "Jul 23, 98 00:43:57 am" To: imp@village.org (Warner Losh) Date: Thu, 23 Jul 1998 16:54:32 +1000 (EST) Cc: jb@cimlogic.com.au, 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: > Some experimentation shows that whem make sees this flag, it doesn't > start over building. > > However, looking again at the problem, why not add: > > MACHINE_ARC?=${MACHINE} > > really early in src/Makefile? Would that solve the problem? Don't > have a machine handy that would exhibit the problem. Time to checkout > a tree on one that does... No. Unless you include the correct sys.mk, you won't get the library path correct since the 2.2.* versions of sys.mk don't know about /usr/lib/aout. Patching src/Makefile to allow for differences in versions of sys.mk seems the wrong thing to do. If people don't like using the -m argument, then the top level makefile should not use anything from 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 23 00:45:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA00854 for freebsd-current-outgoing; Thu, 23 Jul 1998 00:45:46 -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 AAA00842 for ; Thu, 23 Jul 1998 00:45:41 -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 JAA06539 ; Thu, 23 Jul 1998 09:39:09 +0200 (MET DST) Received: by sunw110.oslo.Geco-Prakla.slb.com (SMI-8.6/SMI-SVR4) id JAA23482; Thu, 23 Jul 1998 09:39:09 +0200 To: Julian Elischer Cc: Brian Somers , "Jordan K. Hubbard" , Dag-Erling Coidan Sm rgrav , Alfred Perlstein , Joel Ray Holveck , freebsd-current@FreeBSD.ORG Subject: Re: vn subsystem 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: 23 Jul 1998 09:39:07 +0200 In-Reply-To: Julian Elischer's message of Wed, 22 Jul 1998 11:53:57 -0700 (PDT) Message-ID: Lines: 25 X-Mailer: Gnus v5.3/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Julian Elischer writes: > AHA! > of course, the vn devices don't work any more in a devfs world, without > devfs.. > > as you worked out the trick woudl be to mount a copy of devfs in the right > place in the chroot environment.. > > now, how best to DO that?? I tried the following this morning: # chroot /usr/release bin/sh # mount -t devfs devfs /dev # cd /usr/src/release # make release.8 It got as far as disklabel, where it died with "inappropriate ioctl for device" and rebooted. Unfortunately, I didn't see the panic message since I was in X, and for some mysterious reason there was no dump, though I did have a dump device configured. 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 23 01:25:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA05836 for freebsd-current-outgoing; Thu, 23 Jul 1998 01:25:35 -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 BAA05831 for ; Thu, 23 Jul 1998 01:25:32 -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 KAA08727 ; Thu, 23 Jul 1998 10:24:39 +0200 (MET DST) Received: by sunw110.oslo.Geco-Prakla.slb.com (SMI-8.6/SMI-SVR4) id KAA23548; Thu, 23 Jul 1998 10:24:38 +0200 To: Garance A Drosihn Cc: current@FreeBSD.ORG Subject: Re: Perl5 as default for current 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: 23 Jul 1998 10:24:38 +0200 In-Reply-To: Garance A Drosihn's message of Wed, 22 Jul 1998 19:40:55 -0400 Message-ID: Lines: 18 X-Mailer: Gnus v5.3/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Garance A Drosihn writes: > Are there plans to make the "standard" perl in FreeBSD be perl5? > (yes, I know perl5 is in /usr/local/bin, and that it's very easy > to get to there. I am just wondering if that will ever replace > the perl which is currently perl4). > > I do not pretend that this is critical to the future of mankind, > I'm just curious what the plans are... This has been discussed before, and as I recall, it was agreed that it would not happen until someone volunteered to go through every single Perl script in FreeBSD to make sure it will work with Perl 5. Perl syntax and semantics have been known to change somewhat gratuitously from one release to the next. 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 23 01:33:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA07188 for freebsd-current-outgoing; Thu, 23 Jul 1998 01:33:32 -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 BAA07166 for ; Thu, 23 Jul 1998 01:33:23 -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 KAA09014 ; Thu, 23 Jul 1998 10:31:45 +0200 (MET DST) Received: by sunw110.oslo.Geco-Prakla.slb.com (SMI-8.6/SMI-SVR4) id KAA23550; Thu, 23 Jul 1998 10:31:44 +0200 To: ben@rosengart.com Cc: Kazutaka YOKOTA , current@FreeBSD.ORG Subject: Re: keyboard lights 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: 23 Jul 1998 10:31:44 +0200 In-Reply-To: Snob Art Genre's message of Wed, 22 Jul 1998 12:33:20 -0400 (EDT) Message-ID: Lines: 18 X-Mailer: Gnus v5.3/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Snob Art Genre writes: > On Thu, 23 Jul 1998, Kazutaka YOKOTA wrote: > > The keyboard flashes all LEDs at once when it is resetting. Maybe > > the power to the keyboard is somewhat shaky? > I suppose so, but the connector certainly doesn't feel shaky, and I > never lose keystrokes or anything. One way to tell is to set a high autorepeat rate (and a low autorepeat delay), either in the Keyboard section in /etc/XF86Config or with 'kbdcontrol -r fast' if you don't use X, and see if they revert to normal when the LEDs flash. If they do, it means your keyboard is spuriously resetting, which probably indicates a hardware malfunction (either of the keyboard itself - try a different keyboard - or of the keyboard connector on the motherboard). 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 23 01:51:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA09934 for freebsd-current-outgoing; Thu, 23 Jul 1998 01:51: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 BAA09912 for ; Thu, 23 Jul 1998 01:50:58 -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 BAA18186; Thu, 23 Jul 1998 01:49:44 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: smoergrd@oslo.geco-prakla.slb.com (Dag-Erling Coidan Sm rgrav) cc: Garance A Drosihn , current@FreeBSD.ORG Subject: Re: Perl5 as default for current In-reply-to: Your message of "23 Jul 1998 10:24:38 +0200." Date: Thu, 23 Jul 1998 01:49:44 -0700 Message-ID: <18182.901183784@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > This has been discussed before, and as I recall, it was agreed that it > would not happen until someone volunteered to go through every single > Perl script in FreeBSD to make sure it will work with Perl 5. Perl > syntax and semantics have been known to change somewhat gratuitously > from one release to the next. That's already been done and is not the problem. The problem now is getting the bmake'd perl5 working. Someone submitted something for this and it was found to have a number of problems in how it was generated - the original, pristine sources weren't checked into /usr/src/contrib and modifications made via the framework, nor did all the man pages install correctly. Mark Murray is currently out travelling the world, but when he arrives back at home he's supposed to start working on cleaning up the submitted bmake job or doing it from scratch. Either way, a migration to perl5 in -current IS planned, it's just held up for lack of time and attention. - 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 23 02:04:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA12248 for freebsd-current-outgoing; Thu, 23 Jul 1998 02:04:50 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk ([195.8.135.83]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA12203 for ; Thu, 23 Jul 1998 02:04: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 JAA00373; Thu, 23 Jul 1998 09:15:09 +0200 (CEST) To: Bruce Evans cc: brian@Awfulhak.org, freebsd-current@FreeBSD.ORG, jak@cetlink.net Subject: Re: tickadj -t not changing tick In-reply-to: Your message of "Thu, 23 Jul 1998 14:01:38 +1000." <199807230401.OAA09064@godzilla.zeta.org.au> Date: Thu, 23 Jul 1998 09:15:09 +0200 Message-ID: <371.901178109@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199807230401.OAA09064@godzilla.zeta.org.au>, Bruce Evans writes: >>>The whole problem may be caused by APM. APM's time handling is of low >>>quality. >> >>As currently designed, there is only the RTC chip which is reliably keeping >>track of time on a APMized system, and only reading the registers is reliable, >>the number of interrupts and their frequency is subject to change without >>notice. > >The RTC is sufficiently reliable. One reason that APM's time handling is >of low quality because it doesn't sync with the RTC; it just reads it. You're talking about our APM code, I was talking about the APM bios spec and what it guarantees. Our implementation can be improved, the spec not so. >My version of inittodr() syncs with the RTC. This takes a second or two. >The delay would be bad if suspension intervals are short enough for the >innaccurate reading of the RTC to casue negative times. The problem is the "your clock is probably wrong now" events which I belive we currently ignore, they can happen as frequently as once ever few seconds, so a 1-2 sec delay in synchronizing to the rtc just will not do. -- 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 23 03:07:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA20515 for freebsd-current-outgoing; Thu, 23 Jul 1998 03:07:33 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from www.scancall.no (www.scancall.no [195.139.183.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id DAA20496 for ; Thu, 23 Jul 1998 03:07:29 -0700 (PDT) (envelope-from Marius.Bendiksen@scancall.no) Received: from super2.langesund.scancall.no [195.139.183.29] by www with smtp id GSRBWWMJ; Thu, 23 Jul 98 10:07:07 GMT (PowerWeb version 4.04r6) Message-Id: <3.0.5.32.19980723120553.0092ae50@mail.scancall.no> X-Sender: Marius@mail.scancall.no X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Thu, 23 Jul 1998 12:05:53 +0200 To: freebsd-current@FreeBSD.ORG From: Marius Bendiksen Subject: -Current fails to mount / Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG My -current system, cvsupped 22nd July, fails to boot, telling me that it doesn't find 'mount_' in /sbin, nor /usr/sbin. It then proceeds to drop me into single user, where I get the same error when attempting to remount root as read-write. Since the root_device is read-only, I cannot mount *anything* at all. I do have a boot disk and fix disk, though, but I would like to get my real system to mount / though... I have not seen mention of any such error in the last few weeks, on either current, stable or hackers... The system was built in multi-user mode with: cd /usr/src/share/mk make (install, or something, I think) cd /usr/src make buildworld That didn't cause any errors, and nobody knew of any breakage, so I did an installworld make. My system configuration is: AMD K6/233 64 MB SD-RAM 3.2 UDMA + 1.2 EIDE ATI Rage II+ / 2 MB AWE 32 / 2 MB TeleS S0/16.3 Any help appreciated... --- Marius Bendiksen. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 23 03:48:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA26516 for freebsd-current-outgoing; Thu, 23 Jul 1998 03:48:20 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from vexpert.dbai.tuwien.ac.at (vexpert.dbai.tuwien.ac.at [128.130.111.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA26414 for ; Thu, 23 Jul 1998 03:48:02 -0700 (PDT) (envelope-from ehritz@dbai.tuwien.ac.at) Received: from arcturus.dbai.tuwien.ac.at (arcturus.dbai.tuwien.ac.at [128.130.111.20]) by vexpert.dbai.tuwien.ac.at (8.8.8/8.8.8) with ESMTP id MAA25856 for ; Thu, 23 Jul 1998 12:47:39 +0200 (MET-DST) From: Gerald Ehritz Received: (from ehritz@localhost) by arcturus.dbai.tuwien.ac.at (8.8.5/8.8.5) id MAA07977 for freebsd-current@freebsd.org; Thu, 23 Jul 1998 12:47:40 +0200 (MET DST) Date: Thu, 23 Jul 1998 12:47:40 +0200 (MET DST) Message-Id: <199807231047.MAA07977@arcturus.dbai.tuwien.ac.at> To: freebsd-current@FreeBSD.ORG Subject: pine 3.96 locks 3.0-980621 completely X-Sun-Charset: US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, We use a 3.0-980621 and discovered soem days ago, that writing out an attachment ( > 100k) to a file locks up the machine completely. No login possible and also no log to screen or file. Except this pine works fine. PC: Pentium , 32 MB Mem; Mail dir NSF mounted Is this a known problem, shall i upgrade to a newer Version? Many thanks Gerald ________________________________________________________ Gerald Ehritz ehritz@dbai.tuwien.ac.at Institut f. Informationssysteme Technische Universitaet Wien ________________________________________________________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 23 05:03:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA05010 for freebsd-current-outgoing; Thu, 23 Jul 1998 05:03:01 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from shell.futuresouth.com (fullermd@shell.futuresouth.com [198.78.58.18]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA05005 for ; Thu, 23 Jul 1998 05:03:00 -0700 (PDT) (envelope-from fullermd@shell.futuresouth.com) Received: (from fullermd@localhost) by shell.futuresouth.com (8.8.8/8.8.8) id HAA14746; Thu, 23 Jul 1998 07:02:37 -0500 (CDT) Message-ID: <19980723070236.41943@futuresouth.com> Date: Thu, 23 Jul 1998 07:02:36 -0500 From: "Matthew D. Fuller" To: current@FreeBSD.ORG Subject: NFS and 3.0-RELEASE Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Do we plan to have NFS locking working for 3.0-RELEASE? *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* | FreeBSD; the way computers were meant to be | * "The only reason I'm burning my candle at both ends, is * | that I haven't figured out how to light the middle yet."| * fullermd@futuresouth.com :-} MAtthew Fuller * | http://keystone.westminster.edu/~fullermd | *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 23 05:35:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA08412 for freebsd-current-outgoing; Thu, 23 Jul 1998 05:35:42 -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 FAA08268 for ; Thu, 23 Jul 1998 05:33:57 -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 PAA16762; Thu, 23 Jul 1998 15:29:56 +0300 (EEST) (envelope-from ady@warpnet.ro) Date: Thu, 23 Jul 1998 15:29:56 +0300 (EEST) From: Adrian Penisoara To: Gerald Ehritz cc: freebsd-current@FreeBSD.ORG Subject: Re: pine 3.96 locks 3.0-980621 completely In-Reply-To: <199807231047.MAA07977@arcturus.dbai.tuwien.ac.at> 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, 23 Jul 1998, Gerald Ehritz wrote: > Hi all, > > We use a 3.0-980621 and discovered soem days ago, that writing out an >attachment ( > 100k) to a file locks up the machine completely. No login >possible and also no log to screen or file. > Except this pine works fine. > > PC: Pentium , 32 MB Mem; Mail dir NSF mounted I guess the problem is the NFS mounted mail directory; I used (and still use) Pine 3.96 (no NFS mounts !) for a long time and had no problems whatsoever with saving attachments... You may want to try a newer Pine 4 version (I strongly recommend the 4.02 port which hasn't yet hit the CVS tree -- I can send you the archived port if you need it). > > Is this a known problem, shall i upgrade to a newer Version? > > Many thanks > Gerald > ________________________________________________________ > Gerald Ehritz ehritz@dbai.tuwien.ac.at > Institut f. Informationssysteme > Technische Universitaet Wien > ________________________________________________________ > Just my $0.02 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 Thu Jul 23 05:40:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA09124 for freebsd-current-outgoing; Thu, 23 Jul 1998 05:40:55 -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 FAA09110 for ; Thu, 23 Jul 1998 05:40:46 -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 IAA13565; Thu, 23 Jul 1998 08:40:15 -0400 (EDT) (envelope-from gjp@gjp.erols.com) X-Mailer: exmh version 2.0.1 12/23/97 To: Gerald Ehritz cc: freebsd-current@FreeBSD.ORG From: "Gary Palmer" Subject: Re: pine 3.96 locks 3.0-980621 completely In-reply-to: Your message of "Thu, 23 Jul 1998 12:47:40 +0200." <199807231047.MAA07977@arcturus.dbai.tuwien.ac.at> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 23 Jul 1998 08:40:15 -0400 Message-ID: <13561.901197615@gjp.erols.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Gerald Ehritz wrote in message ID <199807231047.MAA07977@arcturus.dbai.tuwien.ac.at>: > Hi all, > > We use a 3.0-980621 and discovered soem days ago, that writing out an attachm > ent ( > 100k) to a file locks up the machine completely. No login possible an > d also no log to screen or file. > Except this pine works fine. > > PC: Pentium , 32 MB Mem; Mail dir NSF mounted ^^^^^^^^^^^^^^^^^^^^ I know this isn't what you wanted to hear, but that is just *asking* for problems, especially if you are using default mailbox format, because there is probably inadquate locking going on, and you may truncate the mailbox not realizing that sendmail just delivered new mail (not to mention other nasties) Since you are using Pine, try IMAP or POP. Works *much* better, and I bet the machine will stop crashing also :) 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 Thu Jul 23 05:50:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA10526 for freebsd-current-outgoing; Thu, 23 Jul 1998 05:50: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 FAA10521 for ; Thu, 23 Jul 1998 05:50:35 -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 WAA11435; Thu, 23 Jul 1998 22:50:11 +1000 Date: Thu, 23 Jul 1998 22:50:11 +1000 From: Bruce Evans Message-Id: <199807231250.WAA11435@godzilla.zeta.org.au> To: imp@village.org, jb@cimlogic.com.au Subject: Re: Does building current on 2.2.x still work? Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >What would be needed that isn't covered in ${MAKE} and ${.MAKEFLAGS}? >The value of BAZ in make foo BAZ=blah gets passed down to sub-makes, >and .MAKEFLAGS takes care of the rest. What would be missing? > >*: > cd ${.CURDIR}; ${MAKE} -m ${.CURDIR}/share/mk -f Makefile.inc0 ${.TARGET} > >(well, where * gets expanded by humans to all the desirable targets in >the current src/Makefile). The -m arg is already covered by adding it to .MAKEFLAGS. Except of course for world and buildworld where -m can't be used since it doesn't exist in 2.1, and for installworld where there seems to be no reason to avoid it. 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 23 06:01:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA12195 for freebsd-current-outgoing; Thu, 23 Jul 1998 06:01: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 GAA12188 for ; Thu, 23 Jul 1998 06:01:36 -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 XAA12166; Thu, 23 Jul 1998 23:01:13 +1000 Date: Thu, 23 Jul 1998 23:01:13 +1000 From: Bruce Evans Message-Id: <199807231301.XAA12166@godzilla.zeta.org.au> To: imp@village.org, jb@cimlogic.com.au Subject: Re: Does building current on 2.2.x still work? Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >I have a silly question. Looking at src/Makefile, I see: > >.if (!make(world)) && (!make(buildworld)) && (!make(installworld)) >.MAKEFLAGS:= -m ${.CURDIR}/share/mk ${.MAKEFLAGS} >.endif > >Why the if? Why wouldn't you want to use share/mk always for make >*world? Because some versions of make (in particular the one in 2.1) don't support -m. The makefile takes great care not to use it until make is bootstrapped. 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 23 06:33:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA16013 for freebsd-current-outgoing; Thu, 23 Jul 1998 06:33:08 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.gwinnett.com (mail.gwinnett.com [204.89.227.35]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA16005 for ; Thu, 23 Jul 1998 06:33:06 -0700 (PDT) (envelope-from lee@gwinnett.com) Received: from venus.gwinnett.com ([204.89.227.91]) by mail.gwinnett.com (8.8.7/8.8.5) with SMTP id JAA20651 for ; Thu, 23 Jul 1998 09:32:34 -0400 Message-ID: <35B73B60.41C67EA6@gwinnett.com> Date: Thu, 23 Jul 1998 09:32:16 -0400 From: Lee Reese X-Mailer: Mozilla 3.04 (X11; I; FreeBSD 3.0CAM-19980712-0 i386) MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: Viability of -current for Usenet News Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG We have been having quite a bit of trouble running a Usenet News server over the last 8 months. The machine in question is a dual Pentium Pro with 256MB and a DPT 3334UW Raid Controller. What I would like to do is convince the Sysadmin that FreeBSD might be a better platform than Slackware Linux for administering the server. The machine would be running INN 2.0. We have seen severe buffering problems with the RAID controller and Linux in its present state. Could anyone give any reasons why FreeBSD may be a superior OS for such an application so I can convince the Sysadmin to switch? Thanks. Lee Reese To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 23 07:19:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA22946 for freebsd-current-outgoing; Thu, 23 Jul 1998 07:19:57 -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 HAA22938 for ; Thu, 23 Jul 1998 07:19:51 -0700 (PDT) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id KAA16043; Thu, 23 Jul 1998 10:18:26 -0400 (EDT) (envelope-from luoqi) Date: Thu, 23 Jul 1998 10:18:26 -0400 (EDT) From: Luoqi Chen Message-Id: <199807231418.KAA16043@lor.watermarkgroup.com> To: green@zone.baldcom.net, jkh@time.cdrom.com Subject: Re: vn subsystem Cc: bright@hotjobs.com, freebsd-current@FreeBSD.ORG, joelh@gnu.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Alright, it's unstable for large files. observe the following scenario and > appropriate coredump: > -rw-r--r-- 1 green green 528482304 Jul 22 23:11 /home/green/msdos.drv > vnconfig -c -s io -s labels /dev/vn0 /home/green/msdos.drv ^^^^^^ Is there something missing here? Since the option labels is set, should you do a fdisk before newfs? If you don't, vn driver will try to use dosfs boot sector as an MBR, and funny things could happen. > newfs_msdos /dev/vn0 > mount /dev/vn0 /msdos (oops, should this matter anyway?) > mount_msdos /dev/vn0 /msdos > *crash* -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 23 07:54:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA27796 for freebsd-current-outgoing; Thu, 23 Jul 1998 07:54:47 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from falbala.informatik.uni-kiel.de (BaFhDvQQv5tcINibSf6FPoNLoN6AqTHJ@falbala.informatik.uni-kiel.de [134.245.252.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA27784 for ; Thu, 23 Jul 1998 07:54:30 -0700 (PDT) (envelope-from mfi@techfak.uni-kiel.de) Received: from xaphod.techfak.uni-kiel.de (xaphod.techfak.uni-kiel.de [134.245.240.3]) by falbala.informatik.uni-kiel.de (8.9.1/8.9.1) with ESMTP id QAA09342 for ; Thu, 23 Jul 1998 16:53:23 +0200 (MET DST) Received: from crest.techfak.uni-kiel.de (crest [134.245.244.131]) by xaphod.techfak.uni-kiel.de (8.8.8/8.8.8) with SMTP id QAA29777 for ; Thu, 23 Jul 1998 16:50:18 +0200 (MET DST) From: Michael Firnau Received: by crest.techfak.uni-kiel.de (SMI-8.6/client-1.6-SunOS5) id QAA23725; Thu, 23 Jul 1998 16:50:05 +0200 Message-Id: <199807231450.QAA23725@crest.techfak.uni-kiel.de> Subject: I need some help ... To: current@FreeBSD.ORG Date: Thu, 23 Jul 1998 16:50:04 +0200 (MET DST) X-Mailer: ELM [version 2.4ME+ PL37 (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 Hi, I need a hint. I try to install a new dual cpu-server with 3 Seagate 18GB disks on an adaptec 2940U2W controller. The motherboard is an ASUS P2L97-DS. Installing 3.0CAM-19980712-SNAP and building a new kernel went fine :-)). Today I had to power-off the machine and initiated the shutdown-sequence. Wait .. wait ... power off. After a pause of 5 minutes I switched power on, got a whole bunch of startup-messages ... and then SMP: AP CPU #1 Launched! // this is still ok ... panic: ahc0: brkadrint, Data-path Parity Error at seqaddr=0x17d mp_lock = 00000001; cpuid = 0; lapic.id = 01000000 Debugger("panic") Stopped at _Debugger+0x35: movb $0,_in_Debugger,98 I tried all kernels I could get a hand on: - boot.flp / install - kernel.GENERIC / da0 - kernel.CAMSMP / da0 (my own, worked yesterday) No effect. Then I tried the following: - boot dos - fdisk & put a partition on da1 - reboot & format C: - oops, no error !? Any help out there? Mike mfi@techfak.uni-kiel.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 23 08:51:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA06393 for freebsd-current-outgoing; Thu, 23 Jul 1998 08:51:26 -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 IAA06382 for ; Thu, 23 Jul 1998 08:51:20 -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 0yzNdv-0002sd-00; Thu, 23 Jul 1998 08:50:56 -0700 Date: Thu, 23 Jul 1998 08:50:54 -0700 (PDT) From: Tom X-Sender: tom@shell.uniserve.ca To: Lee Reese cc: current@FreeBSD.ORG Subject: Re: Viability of -current for Usenet News In-Reply-To: <35B73B60.41C67EA6@gwinnett.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, 23 Jul 1998, Lee Reese wrote: ... > with 256MB and a DPT 3334UW Raid Controller. ... > machine would be running INN 2.0. We have seen severe buffering > problems with the RAID controller and Linux in its present state. Could ... I've just seen a RedHat 5.1 system with a such a controller, hang. It doesn't seem the Linux DPT driver is very stable. It seems easy to get into a situation where all processes accessing the disk, hang. The FreeBSD DPT driver seems quite a bit more solid than that, although setting it up is more difficult. 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 23 10:52:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA27057 for freebsd-current-outgoing; Thu, 23 Jul 1998 10:52:41 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from er3.rutgers.edu (52348@er3.rutgers.edu [165.230.180.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA27037 for ; Thu, 23 Jul 1998 10:52:33 -0700 (PDT) (envelope-from damascus@er3.rutgers.edu) Received: from localhost (damascus@localhost) by er3.rutgers.edu (8.8.8/8.8.8) with SMTP id NAA20734; Thu, 23 Jul 1998 13:51:45 -0400 (EDT) Date: Thu, 23 Jul 1998 13:51:45 -0400 (EDT) From: Damascus To: Lee Reese cc: current@FreeBSD.ORG Subject: Re: Viability of -current for Usenet News In-Reply-To: <35B73B60.41C67EA6@gwinnett.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, 23 Jul 1998, Lee Reese wrote: > We have been having quite a bit of trouble running a Usenet News server > over the last 8 months. The machine in question is a dual Pentium Pro > with 256MB and a DPT 3334UW Raid Controller. > > What I would like to do is convince the Sysadmin that FreeBSD might be a > better platform than Slackware Linux for administering the server. The > machine would be running INN 2.0. We have seen severe buffering > problems with the RAID controller and Linux in its present state. Could > anyone give any reasons why FreeBSD may be a superior OS for such an > application so I can convince the Sysadmin to switch? Thanks. > > Lee Reese Hardware wise, Linux should have some pretty decent support. I don't know if FreeBSD's drivers for the DPT raid controllers are good.... but I am pretty sure they are good. However, slackware linux as a major server? I do not know about that one... I used to use slackware, then tried Debian. Debian is much better with it's package system. You try upgrading a slackware system in the long run... GOOD luck, at least Debian has an easy time with it :) ... but when it comes down to serious adminning, I like FreeBSD the best. It is the easiest to admin, far more organized than any Linux Distribution, fastest TCP/IP stack, better performance, cvsup makes it the EASIEST to upgrade, both applications and core OS, and a spiffy daemon screen saver too! (sorry if lines are all messed up... pico seems to like doing that even though it look fine here) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 23 11:00:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA28583 for freebsd-current-outgoing; Thu, 23 Jul 1998 11:00:23 -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 LAA28565 for ; Thu, 23 Jul 1998 11:00:20 -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 NAA00655; Thu, 23 Jul 1998 13:59:39 -0400 (EDT) Date: Thu, 23 Jul 1998 13:59:39 -0400 (EDT) From: Brian Feldman To: Luoqi Chen cc: jkh@time.cdrom.com, bright@hotjobs.com, freebsd-current@FreeBSD.ORG, joelh@gnu.org Subject: Re: vn subsystem In-Reply-To: <199807231418.KAA16043@lor.watermarkgroup.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 No, newfs_msdos'ing and then mounting /dev/vn0, tho wrong, would have worked fine, and have previously. What I did later was I booted bochs, formatted the drive from inside bochs, installed DOS, etc. And then realized, stupidly, I couldn't mount the MS-DOS formatted drive because I wasn't using the right _slice_; so I mount dev/vn0s1c, and it works fine then. This is the same old problem as before... last time I saw it was with floppy disks, and I guess I thought it didn't affect other media like vn(4). BTW, if you didn't know, your mremap() for linux band-aid was merged into -CURRENT. Cheers, Brian Feldman green@unixhelp.org On Thu, 23 Jul 1998, Luoqi Chen wrote: > > > > Alright, it's unstable for large files. observe the following scenario and > > appropriate coredump: > > -rw-r--r-- 1 green green 528482304 Jul 22 23:11 /home/green/msdos.drv > > vnconfig -c -s io -s labels /dev/vn0 /home/green/msdos.drv > ^^^^^^ > Is there something missing here? Since the option labels is set, should > you do a fdisk before newfs? If you don't, vn driver will try to use dosfs > boot sector as an MBR, and funny things could happen. > > > newfs_msdos /dev/vn0 > > mount /dev/vn0 /msdos (oops, should this matter anyway?) > > mount_msdos /dev/vn0 /msdos > > *crash* > > -lq > > 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 23 11:15:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA01687 for freebsd-current-outgoing; Thu, 23 Jul 1998 11:15:18 -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 LAA01664 for ; Thu, 23 Jul 1998 11:15:09 -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 OAA00841 for ; Thu, 23 Jul 1998 14:14:41 -0400 (EDT) Date: Thu, 23 Jul 1998 14:14:41 -0400 (EDT) From: Brian Feldman To: freebsd-current@FreeBSD.ORG Subject: More doscmd adventures/lockups 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 Yessiree, doscmd has ways of locking me up without a panic. I'll explore what happened this time: I was using my 5[0-2][0-8]mb dos drive in bochs, installing MS-DOS 6.22. I tried using doscmd to boot it, doscmd -bx... after Starting msdos... the whole computer froze, I waited a few minutes, and hit reset when I was sure it was locked up solid. To recap: bochs was loading dos on the drive, on disk 2 by now, and doscmd -bx tried to boot the drive; this was standard access, no vn(4) problems. Cheers, Brian Feldman green@unixhelp.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 23 11:35:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA06324 for freebsd-current-outgoing; Thu, 23 Jul 1998 11:35:17 -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 LAA06295 for ; Thu, 23 Jul 1998 11:35:08 -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 OAA19868; Thu, 23 Jul 1998 14:34:11 -0400 (EDT) (envelope-from wollman) Date: Thu, 23 Jul 1998 14:34:11 -0400 (EDT) From: Garrett Wollman Message-Id: <199807231834.OAA19868@khavrinen.lcs.mit.edu> To: Lee Reese Cc: current@FreeBSD.ORG Subject: Viability of -current for Usenet News In-Reply-To: <35B73B60.41C67EA6@gwinnett.com> References: <35B73B60.41C67EA6@gwinnett.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > problems with the RAID controller and Linux in its present state. Could > anyone give any reasons why FreeBSD may be a superior OS for such an > application so I can convince the Sysadmin to switch? Thanks. These sorts of questions are always fraught with danger, since they tend to degenerate rather quickly into religious wars. I am personally running what-was-and-will-again-be a major transit news server on a FreeBSD box (what else would I use?) and have noted some good points and some bad points. Good points: with the 640 MB of memory it has now, this box really screams. FreeBSD's agressive filesystem caching ensures that important files like dhistory are kept in memory all of the time. This machine can keep up with 14 simultaneous full feeds and still idle half the time. Bad points: there are still some lingering kernel bugs which are causing instability. There is a VM/buffer-cache coherency problem that I believe is still catching me from time to time, and should I ever actually run out of memory a whole range of problems can be triggered. Right now, top reports: last pid: 765; load averages: 1.21, 1.39, 1.19 14:33:12 130 processes: 1 running, 129 sleeping CPU states: 12.4% user, 0.0% nice, 8.1% system, 1.2% interrupt, 78.3% idle Mem: 450M Active, 13M Inact, 24M Wired, 139M Cache, 8347K Buf, 1288K Free Swap: 256M Total, 128K Used, 256M Free It could be a bit better. -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 Thu Jul 23 11:36:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA06812 for freebsd-current-outgoing; Thu, 23 Jul 1998 11:36:27 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA06803 for ; Thu, 23 Jul 1998 11:36:23 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id LAA00344; Thu, 23 Jul 1998 11:34:46 -0700 (PDT) Message-Id: <199807231834.LAA00344@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Brian Feldman cc: freebsd-current@FreeBSD.ORG Subject: Re: More doscmd adventures/lockups In-reply-to: Your message of "Thu, 23 Jul 1998 14:14:41 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 23 Jul 1998 11:34:46 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Yessiree, doscmd has ways of locking me up without a panic. I'll explore > what happened this time: I was using my 5[0-2][0-8]mb dos drive in bochs, > installing MS-DOS 6.22. I tried using doscmd to boot it, doscmd -bx... > after Starting msdos... the whole computer froze, I waited a few minutes, > and hit reset when I was sure it was locked up solid. To recap: bochs was > loading dos on the drive, on disk 2 by now, and doscmd -bx tried to boot > the drive; this was standard access, no vn(4) problems. Please, if you're going to report problems, try doing it in a fashion that gives us something to work with. For example, here you haven't mentioned what level of -currentness your system is at, or what other options you've got enabled. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 23 11:41:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA07945 for freebsd-current-outgoing; Thu, 23 Jul 1998 11:41:11 -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 LAA07922 for ; Thu, 23 Jul 1998 11:41:07 -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 0yzQI4-0003k8-00; Thu, 23 Jul 1998 11:40:32 -0700 Date: Thu, 23 Jul 1998 11:40:30 -0700 (PDT) From: Tom X-Sender: tom@shell.uniserve.ca To: Damascus cc: Lee Reese , current@FreeBSD.ORG Subject: Re: Viability of -current for Usenet News 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 Thu, 23 Jul 1998, Damascus wrote: > Hardware wise, Linux should have some pretty decent support. I don't know Linux has the same problems as all free unixes, if not worse. Many drivers are less than version 1.0, and only partially completed. You should see the very restrictive list of hardware that RedHat recommends, and DPT is listed as a "Tier 2 Supported", which only means partial support. Only Mylex Multimaster/Flashpoint and Adaptec PCI cards are listed in Tier 1. 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 23 12:13:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA12134 for freebsd-current-outgoing; Thu, 23 Jul 1998 12:13:12 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp03.primenet.com (root@smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA12129 for ; Thu, 23 Jul 1998 12:13:11 -0700 (PDT) (envelope-from tlambert@usr04.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id LAA11549; Thu, 23 Jul 1998 11:31:16 -0700 (MST) Received: from usr04.primenet.com(206.165.6.204) via SMTP by smtp03.primenet.com, id smtpd011309; Thu Jul 23 11:30:58 1998 Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id LAA28303; Thu, 23 Jul 1998 11:30:05 -0700 (MST) From: Terry Lambert Message-Id: <199807231830.LAA28303@usr04.primenet.com> Subject: Re: Does building current on 2.2.x still work? To: imp@village.org (Warner Losh) Date: Thu, 23 Jul 1998 18:30:05 +0000 (GMT) Cc: jb@cimlogic.com.au, current@FreeBSD.ORG In-Reply-To: <199807230703.BAA08029@harmony.village.org> from "Warner Losh" at Jul 23, 98 01:03:23 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 > Another option, learned from the ports system, would be to have > (presented here in simplified form): > > world: > make real-world > buildworld: > make real-buildworld > installworld: > make real-installworld You need to use parenthesis to force an actual reinvocation of make. > And then rename the current *world targets to real-*world. This was the substance of my "subshell" proposal, where the submake would be the built make instead of the installed make to get a working "-m" flag. Alternately, we should consider a chroot build environment as part of the build process, which obviates the need for all of these new relative pathing option arguments to all the old tools. 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 23 12:26:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA14170 for freebsd-current-outgoing; Thu, 23 Jul 1998 12:26:40 -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 MAA14094 for ; Thu, 23 Jul 1998 12:26:24 -0700 (PDT) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by hub.org (8.8.8/8.7.5) with SMTP id PAA11204 for ; Thu, 23 Jul 1998 15:25:54 -0400 (EDT) Date: Thu, 23 Jul 1998 15:25:53 -0400 (EDT) From: The Hermit Hacker To: freebsd-current@FreeBSD.ORG Subject: ps seg faults ... 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 had to ask this, but we installed 3.0-SNAP onto one of our servers several months back, and its run flawlessly ever since. Suddenly, yesterday, 'ps aux' starts to seg fault, where 'ps ax' runs fine... Since it isn't the 'bleeding-edge' 3.0, and since its been working fine for months now, I'm at a lose as to where to look for the problem... Any help is greatly appreciated... Thanks... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 23 12:53:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA19699 for freebsd-current-outgoing; Thu, 23 Jul 1998 12:53:45 -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 MAA19694 for ; Thu, 23 Jul 1998 12:53:43 -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 PAA01980; Thu, 23 Jul 1998 15:53:04 -0400 (EDT) Date: Thu, 23 Jul 1998 15:53:04 -0400 (EDT) From: Brian Feldman To: Mike Smith cc: freebsd-current@FreeBSD.ORG Subject: Re: More doscmd adventures/lockups In-Reply-To: <199807231834.LAA00344@dingo.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 Alright, sorry about that. The CURRENTness is a world from a few days ago, and a kernel from 7/22/98; I don't know exactly what "options" you're referring to, but the only non-normal-and-possibly-unstable things in my kernel are: options "VM86" options SOFTUPDATES I'm pretty sure the problem wasn't with SoftUpdates... the specific conditions were bochs, an i386 emulator, installing DOS on the drive (/home/green/msdos.drv), which uses nothing special, system-wise, and doscmd, trying to boot the drive at the same time, which uses the VM86 system to run. Let me know what else you want to know. Cheers, Brian Feldman green@unixhelp.org On Thu, 23 Jul 1998, Mike Smith wrote: > > Yessiree, doscmd has ways of locking me up without a panic. I'll explore > > what happened this time: I was using my 5[0-2][0-8]mb dos drive in bochs, > > installing MS-DOS 6.22. I tried using doscmd to boot it, doscmd -bx... > > after Starting msdos... the whole computer froze, I waited a few minutes, > > and hit reset when I was sure it was locked up solid. To recap: bochs was > > loading dos on the drive, on disk 2 by now, and doscmd -bx tried to boot > > the drive; this was standard access, no vn(4) problems. > > Please, if you're going to report problems, try doing it in a fashion > that gives us something to work with. > > For example, here you haven't mentioned what level of -currentness your > system is at, or what other options you've got enabled. > > -- > \\ Sometimes you're ahead, \\ Mike Smith > \\ sometimes you're behind. \\ mike@smith.net.au > \\ The race is long, and in the \\ msmith@freebsd.org > \\ end it's only with yourself. \\ msmith@cdrom.com > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 23 13:00:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA21228 for freebsd-current-outgoing; Thu, 23 Jul 1998 13:00:50 -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 NAA21214 for ; Thu, 23 Jul 1998 13:00:38 -0700 (PDT) (envelope-from toasty@home.dragondata.com) Received: (from toasty@localhost) by home.dragondata.com (8.8.8/8.8.5) id OAA24934; Thu, 23 Jul 1998 14:59:09 -0500 (CDT) From: Kevin Day Message-Id: <199807231959.OAA24934@home.dragondata.com> Subject: Re: panic: page fault while in kernel mode - from gcc In-Reply-To: <199807230410.VAA14655@usr05.primenet.com> from Terry Lambert at "Jul 23, 98 04:10:14 am" To: tlambert@primenet.com (Terry Lambert) Date: Thu, 23 Jul 1998 14:59:08 -0500 (CDT) Cc: dg@root.com, 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 > > >> This seems to indicate that the new process's page directory either hasn't > > >> been allocated yet or went away for some reason. Apparantly one of several > > >> new bugs that John has left us with. > > >> > > > > > >Is there any reason why someone doesn't back out his last few batches of > > >large vm changes? Apparently he was half done with some of it, and what we > > >had before seemed more stable than what we have now. > > > > That may ultimately be what we have to do, but the fixes also fixed some > > serious 'leak' style problems with the Mach derived VM system, so I'd rather > > that we find the bugs and fix them rather than going back to the previous > > code. > > FreeBSD doesn't currently include the batch of patches that Elvind > saved and that John had in his home directory when it was removed, > does it? > > What is the behaviour with those patches added in? > Right now, with my -current server, I get a 'panic: page fault while in kernel mode' about once a week.... Dual Processor, P/200 with 256M of ram. Most of the problems seem to occur when the system is starting to swap.. (obviously) Old kernels don't have NFS very stable, and new kernels have these random panic's... Is there a compromise somewhere? Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 23 13:06:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA22874 for freebsd-current-outgoing; Thu, 23 Jul 1998 13:06:52 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sumatra.americantv.com (sumatra.americantv.com [207.170.17.37]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA22816 for ; Thu, 23 Jul 1998 13:06:43 -0700 (PDT) (envelope-from jlemon@americantv.com) Received: from right.PCS (right.PCS [148.105.10.31]) by sumatra.americantv.com (8.8.5/8.8.5) with ESMTP id PAA14490; Thu, 23 Jul 1998 15:06:20 -0500 (CDT) Received: (from jlemon@localhost) by right.PCS (8.6.13/8.6.4) id PAA19992; Thu, 23 Jul 1998 15:05:48 -0500 Message-ID: <19980723150547.60718@right.PCS> Date: Thu, 23 Jul 1998 15:05:47 -0500 From: Jonathan Lemon To: Brian Feldman Cc: freebsd-current@FreeBSD.ORG Subject: Re: More doscmd adventures/lockups References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.61.1 In-Reply-To: ; from Brian Feldman on Jul 07, 1998 at 02:14:41PM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Jul 07, 1998 at 02:14:41PM -0400, Brian Feldman wrote: > Yessiree, doscmd has ways of locking me up without a panic. I'll explore > what happened this time: I was using my 5[0-2][0-8]mb dos drive in bochs, > installing MS-DOS 6.22. I tried using doscmd to boot it, doscmd -bx... > after Starting msdos... the whole computer froze, I waited a few minutes, > and hit reset when I was sure it was locked up solid. To recap: bochs was > loading dos on the drive, on disk 2 by now, and doscmd -bx tried to boot > the drive; this was standard access, no vn(4) problems. Sigh. I've spent the last few weeks trying to track this down, but to no avail. It doesn't _appear_ to be a doscmd specific bug, but rather a problem with the cpl settings. What I'm seeing here is that when the kernel enters vm86 mode, it has cpl == 0, which is all well and good. When an interrupt occurs, and the kernel is entered via one of the INTR() entry points, it seems that cpl != 0. I don't know how this is possible, but that is what I seem to be observing. This cpl is then restored in _doreti right before returning to either user mode, or vm86 mode, which means that we are running in non-kernel mode with AST's blocked. Attached is a gross workaround for the problem that fixes it on my box. Let me know if it also fixes the lockups that you are having. -- Jonathan Index: ipl.s =================================================================== RCS file: /tuna/ncvs/src/sys/i386/isa/ipl.s,v retrieving revision 1.21 diff -u -r1.21 ipl.s --- ipl.s 1998/03/23 19:52:59 1.21 +++ ipl.s 1998/07/23 19:55:53 @@ -169,9 +169,11 @@ * When the cpl problem is solved, this code can disappear. */ ICPL_LOCK - cmpl $0,_cpl + cmpl $0,_cpl /* cpl == 0, skip it */ je 1f - testl $PSL_VM,TF_EFLAGS(%esp) + testl $PSL_VM,TF_EFLAGS(%esp) /* going to VM86 mode? */ + jne doreti_stop + testb $SEL_RPL_MASK,TRAPF_CS_OFF(%esp) /* to user mode? */ je 1f doreti_stop: movl $0,_cpl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 23 13:45:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA02485 for freebsd-current-outgoing; Thu, 23 Jul 1998 13:45:54 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from indigo.ie (nsmart@ts02-017.dublin.indigo.ie [194.125.134.147]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA02479 for ; Thu, 23 Jul 1998 13:45:48 -0700 (PDT) (envelope-from rotel@indigo.ie) Received: (from nsmart@localhost) by indigo.ie (8.8.8/8.8.7) id VAA01568; Thu, 23 Jul 1998 21:40:34 +0100 (IST) (envelope-from rotel@indigo.ie) From: Niall Smart Message-Id: <199807232040.VAA01568@indigo.ie> Date: Thu, 23 Jul 1998 21:40:34 +0000 In-Reply-To: ; The Hermit Hacker 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: The Hermit Hacker , freebsd-current@FreeBSD.ORG Subject: Re: ps seg faults ... Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Jul 23, 3:25pm, The Hermit Hacker wrote: } Subject: ps seg faults ... > > I had to ask this, but we installed 3.0-SNAP onto one of our > servers several months back, and its run flawlessly ever since. Suddenly, > yesterday, 'ps aux' starts to seg fault, where 'ps ax' runs fine... Have you recompiled any part of the system recently, e.g. the kernel or libkvm? Do you run QPopper, if so, which version? 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 Thu Jul 23 16:30:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA25392 for freebsd-current-outgoing; Thu, 23 Jul 1998 16:30:48 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from colin.muc.de (root@colin.muc.de [193.174.4.1]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id QAA25378 for ; Thu, 23 Jul 1998 16:30:40 -0700 (PDT) (envelope-from jhs@jhs.muc.de) Received: from jhs.muc.de ([193.174.4.84]) by colin.muc.de with SMTP id <140566-2>; Fri, 24 Jul 1998 00:05:09 +0200 Received: (from jhs@localhost) by jhs.muc.de (8.8.8/8.8.8) id XAA01455; Thu, 23 Jul 1998 23:20:47 +0200 (MET DST) (envelope-from jhs) Date: Thu, 23 Jul 1998 23:20:47 +0200 Message-Id: <199807232120.XAA01455@jhs.muc.de> To: freebsd-current@FreeBSD.ORG Subject: cvs-cur.4492.gz does not have src/Makefile,v RELENG_2_2_7 cvs tag From: Julian Stacey Reply-To: Julian Stacey X-Net: jhs@freebsd.org jhs@muc.de www.freebsd.org/~jhs/ www.muc.de/~jhs/ X-Tel: Phone: +49.89.268616 Fax: 2608126 Data: 26023276 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm still waiting for something beyond cvs-cur.4492.gz, which after application does not have a src/Makefile,v RELENG_2_2_7 cvs tag I have a CVsuping friend in town, who yesterday already had a 2.2.7 cvs exported & built .... I'm envious ... & still waiting, maybe the ctm generator got overloaded ?. Julian Julian H. Stacey http://www.muc.de/~jhs/freebsd/ FreeBSD: Free legal system software, 1200 packages, server class stability, high performance, X-Windows, KDE desktop, & needs less ram than Micro$oft. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 23 17:47:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA05702 for freebsd-current-outgoing; Thu, 23 Jul 1998 17:47:24 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from thelab.hub.org (tc-15.acadiau.ca [131.162.2.115]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA05687 for ; Thu, 23 Jul 1998 17:47:14 -0700 (PDT) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.8.8/8.8.2) with SMTP id VAA01458; Thu, 23 Jul 1998 21:46:41 -0300 (ADT) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Thu, 23 Jul 1998 21:46:41 -0300 (ADT) From: The Hermit Hacker To: Niall Smart cc: freebsd-current@FreeBSD.ORG Subject: Re: ps seg faults ... In-Reply-To: <199807232040.VAA01568@indigo.ie> 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, 23 Jul 1998, Niall Smart wrote: > On Jul 23, 3:25pm, The Hermit Hacker wrote: > } Subject: ps seg faults ... > > > > I had to ask this, but we installed 3.0-SNAP onto one of our > > servers several months back, and its run flawlessly ever since. Suddenly, > > yesterday, 'ps aux' starts to seg fault, where 'ps ax' runs fine... > > Have you recompiled any part of the system recently, e.g. the kernel > or libkvm? Last recompile of the kernel was June 16th, and I've recompiled libkvm since, but the source tree hasn't changed since we installed it back in April... > Do you run QPopper, if so, which version? No, not on any of the machines I run... Marc G. Fournier Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.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 23 18:14:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA08482 for freebsd-current-outgoing; Thu, 23 Jul 1998 18:14:30 -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 SAA08475 for ; Thu, 23 Jul 1998 18:14:29 -0700 (PDT) (envelope-from tlambert@usr06.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id SAA27539; Thu, 23 Jul 1998 18:14:06 -0700 (MST) Received: from usr06.primenet.com(206.165.6.206) via SMTP by smtp02.primenet.com, id smtpd027519; Thu Jul 23 18:14:02 1998 Received: (from tlambert@localhost) by usr06.primenet.com (8.8.5/8.8.5) id SAA23063; Thu, 23 Jul 1998 18:13:57 -0700 (MST) From: Terry Lambert Message-Id: <199807240113.SAA23063@usr06.primenet.com> Subject: Re: panic: page fault while in kernel mode - from gcc To: toasty@home.dragondata.com (Kevin Day) Date: Fri, 24 Jul 1998 01:13:57 +0000 (GMT) Cc: tlambert@primenet.com, dg@root.com, current@FreeBSD.ORG In-Reply-To: <199807231959.OAA24934@home.dragondata.com> from "Kevin Day" at Jul 23, 98 02:59:08 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 > > FreeBSD doesn't currently include the batch of patches that Elvind > > saved and that John had in his home directory when it was removed, > > does it? > > > > What is the behaviour with those patches added in? > > Right now, with my -current server, I get a 'panic: page fault while in > kernel mode' about once a week.... Dual Processor, P/200 with 256M of ram. > Most of the problems seem to occur when the system is starting to swap.. > (obviously) You are running with John Dyson's patches, which were published in his home directory, but not integrated into FreeBSD itself? Or you are running with FreeBSD-current? If you are running FreeBSD-current, you should try adding John's patches. 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 23 18:44:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA12412 for freebsd-current-outgoing; Thu, 23 Jul 1998 18:44:49 -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 SAA12405 for ; Thu, 23 Jul 1998 18:44:43 -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 LAA02750; Fri, 24 Jul 1998 11:13:31 +0930 (CST) Message-Id: <199807240143.LAA02750@cain.gsoft.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Adrian Penisoara cc: Gerald Ehritz , freebsd-current@FreeBSD.ORG Subject: Re: pine 3.96 locks 3.0-980621 completely In-reply-to: Your message of "Thu, 23 Jul 1998 15:29:56 +0300." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 24 Jul 1998 11:13:31 +0930 From: "Daniel O'Connor" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I guess the problem is the NFS mounted mail directory; I used (and still > use) Pine 3.96 (no NFS mounts !) for a long time and had no problems > whatsoever with saving attachments... > > You may want to try a newer Pine 4 version (I strongly recommend the 4.02 > port which hasn't yet hit the CVS tree -- I can send you the archived port > if you need it). Err.. well isn't it kind of bad that the machine crashes? :) I mean it _pine_ crashed, then OK, upgrading would be fine, but when the machine crashes, maybe he should upgrade his version of -current.. --------------------------------------------------------------------- |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 Thu Jul 23 18:53:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA13497 for freebsd-current-outgoing; Thu, 23 Jul 1998 18:53:41 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA13492 for ; Thu, 23 Jul 1998 18:53:40 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.5/8.8.8) with SMTP id SAA26281; Thu, 23 Jul 1998 18:52:20 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Thu, 23 Jul 1998 18:52:20 -0700 (PDT) From: Doug White To: Bruce Evans cc: imp@village.org, jb@cimlogic.com.au, current@FreeBSD.ORG Subject: Re: Does building current on 2.2.x still work? In-Reply-To: <199807231250.WAA11435@godzilla.zeta.org.au> 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, 23 Jul 1998, Bruce Evans wrote: > The -m arg is already covered by adding it to .MAKEFLAGS. Except of > course for world and buildworld where -m can't be used since it doesn't > exist in 2.1, and for installworld where there seems to be no reason > to avoid it. This begs the question: Can you build from 2.1.x ANYWAY? Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 23 18:55:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA13727 for freebsd-current-outgoing; Thu, 23 Jul 1998 18:55:09 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA13720 for ; Thu, 23 Jul 1998 18:55:07 -0700 (PDT) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id UAA03907; Thu, 23 Jul 1998 20:54:26 -0500 (EST) (envelope-from toor) Message-Id: <199807240154.UAA03907@dyson.iquest.net> Subject: Re: panic: page fault while in kernel mode - from gcc In-Reply-To: <199807230410.VAA14655@usr05.primenet.com> from Terry Lambert at "Jul 23, 98 04:10:14 am" To: tlambert@primenet.com (Terry Lambert) Date: Thu, 23 Jul 1998 20:54:26 -0500 (EST) Cc: toasty@home.dragondata.com, current@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@iquest.net 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 Terry Lambert said: > > >> This seems to indicate that the new process's page directory either hasn't > > >> been allocated yet or went away for some reason. Apparantly one of several > > >> new bugs that John has left us with. > > >> > > > > > >Is there any reason why someone doesn't back out his last few batches of > > >large vm changes? Apparently he was half done with some of it, and what we > > >had before seemed more stable than what we have now. > > > > That may ultimately be what we have to do, but the fixes also fixed some > > serious 'leak' style problems with the Mach derived VM system, so I'd rather > > that we find the bugs and fix them rather than going back to the previous > > code. > > FreeBSD doesn't currently include the batch of patches that Elvind > saved and that John had in his home directory when it was removed, > does it? > > What is the behaviour with those patches added in? > At the end, I was mostly working on the restructuring of the LL stuff to support SMP as well as it could be with a monolithic kernel. Those patches might have some VM fixes in them, but since I left abruptly (for appropriate reasons) the experimental code is probably a little rough. I suggest that the VM traceback that was posted doesn't indicate a severe or subtile problem (other than in the sense of user-inconvienience.) The fix is likely easy, and discussing it by those who might understand the code, takes probably more energy than actually "just making it go away." I don't have a FreeBSD development environment anymore, so those who have one and understand how the code goes together should probably just fix it. (It appears to be a problem with (obviously) vm_map_copy_entry, and the pmap_copy code.) Since it is an unintentional page fault, it is likely a missing page table page. It is either a reference count problem, or a trivial code botch. Remember, that before filling a page table page, it is important that it exist!!! If the problem is being tickled too often, just disable pmap_copy until the problem can be fixed, which is only a code optimization, and the system will likely work fine without it (but without one of the important optimizations, temporarily.) Again, this is only off the top of my head -- I am busy with other kinds of kernel things for now. -- John | Never try to teach a pig to sing, dyson@iquest.net | it makes one look stupid jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 23 18:58:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA14328 for freebsd-current-outgoing; Thu, 23 Jul 1998 18:58:02 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA14301 for ; Thu, 23 Jul 1998 18:57:57 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.5/8.8.8) with SMTP id SAA26634; Thu, 23 Jul 1998 18:57:23 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Thu, 23 Jul 1998 18:57:22 -0700 (PDT) From: Doug White To: Tom cc: Lee Reese , current@FreeBSD.ORG Subject: Re: Viability of -current for Usenet News 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 Thu, 23 Jul 1998, Tom wrote: > > I've just seen a RedHat 5.1 system with a such a controller, hang. It > doesn't seem the Linux DPT driver is very stable. It seems easy to get > into a situation where all processes accessing the disk, hang. The > FreeBSD DPT driver seems quite a bit more solid than that, although > setting it up is more difficult. > Not really anymore, apparently the 2.2.7 boot floppy now has the driver built on it (yay!). Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 23 19:00:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA14863 for freebsd-current-outgoing; Thu, 23 Jul 1998 19:00:19 -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 TAA14726 for ; Thu, 23 Jul 1998 19:00:04 -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 EAA20993; Fri, 24 Jul 1998 04:59:16 +0300 (EEST) (envelope-from ady@warpnet.ro) Date: Fri, 24 Jul 1998 04:59:15 +0300 (EEST) From: Adrian Penisoara To: "Daniel O'Connor" cc: Gerald Ehritz , freebsd-current@FreeBSD.ORG Subject: Re: pine 3.96 locks 3.0-980621 completely In-Reply-To: <199807240143.LAA02750@cain.gsoft.com.au> 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, 24 Jul 1998, Daniel O'Connor wrote: > > > I guess the problem is the NFS mounted mail directory; I used (and still > > use) Pine 3.96 (no NFS mounts !) for a long time and had no problems > > whatsoever with saving attachments... > > > > You may want to try a newer Pine 4 version (I strongly recommend the 4.02 > > port which hasn't yet hit the CVS tree -- I can send you the archived port > > if you need it). > Err.. well isn't it kind of bad that the machine crashes? :) > I mean it _pine_ crashed, then OK, upgrading would be fine, but when the > machine crashes, maybe he should upgrade his version of -current.. Yes, it's clear that the kernel-land/NFS code is the culprit as it shouldn't have failed. But he might want to try Pine 4, who knows, maybe it won't trigger the timebomb explosion or it will behave differently (catching a crushdump?); it also might give a clue to what's wrong... And BTW, I thought Pine reads all the mailbox in memory; if it were to save the attachement to a normal non-NFS filesystem it wouldn't have anything to do with NFS ?... > > --------------------------------------------------------------------- > |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 | > --------------------------------------------------------------------- > Another $0.02 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 Thu Jul 23 19:05:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA16040 for freebsd-current-outgoing; Thu, 23 Jul 1998 19:05: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 TAA16022 for ; Thu, 23 Jul 1998 19:05:26 -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 0yzXE3-0005Qd-00; Thu, 23 Jul 1998 19:04:51 -0700 Date: Thu, 23 Jul 1998 19:04:48 -0700 (PDT) From: Tom X-Sender: tom@shell.uniserve.ca To: Doug White cc: Lee Reese , current@FreeBSD.ORG Subject: Re: Viability of -current for Usenet News 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 Thu, 23 Jul 1998, Doug White wrote: > On Thu, 23 Jul 1998, Tom wrote: > > > I've just seen a RedHat 5.1 system with a such a controller, hang. It > > doesn't seem the Linux DPT driver is very stable. It seems easy to get > > into a situation where all processes accessing the disk, hang. The > > FreeBSD DPT driver seems quite a bit more solid than that, although > > setting it up is more difficult. > > Not really anymore, apparently the 2.2.7 boot floppy now has the driver > built on it (yay!). Yes, but sysinstall bugs will probably force you to do most of the filesystem setup manually. See archives. > Doug White | University of Oregon > Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant > http://gladstone.uoregon.edu/~dwhite | Computer Science Major 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 23 19:21:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA18552 for freebsd-current-outgoing; Thu, 23 Jul 1998 19:21:12 -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 TAA18545 for ; Thu, 23 Jul 1998 19:21:06 -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 TAA23545; Thu, 23 Jul 1998 19:19:17 -0700 (PDT) Message-Id: <199807240219.TAA23545@implode.root.com> To: Terry Lambert cc: toasty@home.dragondata.com (Kevin Day), current@FreeBSD.ORG Subject: Re: panic: page fault while in kernel mode - from gcc In-reply-to: Your message of "Fri, 24 Jul 1998 01:13:57 -0000." <199807240113.SAA23063@usr06.primenet.com> From: David Greenman Reply-To: dg@root.com Date: Thu, 23 Jul 1998 19:19:17 -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> Right now, with my -current server, I get a 'panic: page fault while in >> kernel mode' about once a week.... Dual Processor, P/200 with 256M of ram. >> Most of the problems seem to occur when the system is starting to swap.. >> (obviously) > >You are running with John Dyson's patches, which were published in >his home directory, but not integrated into FreeBSD itself? > >Or you are running with FreeBSD-current? > >If you are running FreeBSD-current, you should try adding John's >patches. All of the reports that I've seen to date (about five) have indicated that the patches that used to be in John's directory caused major instabilities which is the reason why they haven't been committed. -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 Thu Jul 23 19:21:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA18683 for freebsd-current-outgoing; Thu, 23 Jul 1998 19:21: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 TAA18670 for ; Thu, 23 Jul 1998 19:21:49 -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 LAA03068; Fri, 24 Jul 1998 11:51:00 +0930 (CST) Message-Id: <199807240221.LAA03068@cain.gsoft.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Adrian Penisoara cc: Gerald Ehritz , freebsd-current@FreeBSD.ORG Subject: Re: pine 3.96 locks 3.0-980621 completely In-reply-to: Your message of "Fri, 24 Jul 1998 04:59:15 +0300." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 24 Jul 1998 11:50:59 +0930 From: "Daniel O'Connor" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > But he might want to try Pine 4, who knows, maybe it won't trigger the > timebomb explosion or it will behave differently (catching a crushdump?); > it also might give a clue to what's wrong... True.. > And BTW, I thought Pine reads all the mailbox in memory; if it were to > save the attachement to a normal non-NFS filesystem it wouldn't have > anything to do with NFS ?... Hmm ... it may mmap() it which can cause problems, so maybe and upgrade of -current will fix it.. --------------------------------------------------------------------- |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 Thu Jul 23 19:31:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA20729 for freebsd-current-outgoing; Thu, 23 Jul 1998 19:31:54 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dns.webwizard.net.mx (mex17-7.uninet.net.mx [200.38.144.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA20719 for ; Thu, 23 Jul 1998 19:31:47 -0700 (PDT) (envelope-from eculp@webwizard.org.mx) Received: from webwizard.org.mx (mexcom.net.mx [207.249.162.140]) by dns.webwizard.net.mx (8.8.8/8.8.7) with ESMTP id VAA25667 for ; Thu, 23 Jul 1998 21:29:45 -0500 (CDT) Message-ID: <35B7F199.A7A88FA@webwizard.org.mx> Date: Thu, 23 Jul 1998 21:29:45 -0500 From: Edwin Culp X-Mailer: Mozilla 4.5b1 [en] (X11; I; FreeBSD 3.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG Subject: make release 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 building a weekly release with no problems for about a year now. No fun :-) I'm upgrading the machine and was looking at the configuration files and decided that they could be made more efficient by sharing directories such as /usr/src and /a. I have made a mess. I now have problems with nonexistent Attic directories, etc. That's not a big deal and I can always go back to the old , very by the handbook way, but that's too easy. Here is what I have been doing: Daily cvsup -g -L2 cvs-supfile cvsup -g -L2 cvs-rel At least weekly make world and new kernel Twice a month inmediately after the make world and kernel make release here are my new config files cvs-supfile and cvs-rel that are causing the problem although I did get through a make world after manually creating about 6-8 Attic directories. # cat cvs-supfile *default tag=. *default host=cvsup.FreeBSD.org *default base=/a *default prefix=/usr *default release=cvs *default delete compress use-rel-suffix src-all cvs-crypto doc-all src-secure ports-all # cat cvs-rel *default host=cvsup.FreeBSD.org *default base=/a *default prefix=/usr *default release=cvs *default delete compress use-rel-suffix src-all cvs-crypto doc-all src-secure ports-all If someone has a more efficient disk usage setup that works, I would appreciate a copy or corrections. Before both default base and default prefix were different for my release and world. Thanks ed To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 23 20:21:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA28366 for freebsd-current-outgoing; Thu, 23 Jul 1998 20:21:22 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA28360 for ; Thu, 23 Jul 1998 20:21:20 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.5/8.8.8) with SMTP id UAA11330; Thu, 23 Jul 1998 20:20:55 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Thu, 23 Jul 1998 20:20:55 -0700 (PDT) From: Doug White To: Tom cc: Lee Reese , current@FreeBSD.ORG Subject: Re: Viability of -current for Usenet News 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 Thu, 23 Jul 1998, Tom wrote: > > > I've just seen a RedHat 5.1 system with a such a controller, hang. It > > > doesn't seem the Linux DPT driver is very stable. It seems easy to get > > > into a situation where all processes accessing the disk, hang. The > > > FreeBSD DPT driver seems quite a bit more solid than that, although > > > setting it up is more difficult. > > > > Not really anymore, apparently the 2.2.7 boot floppy now has the driver > > built on it (yay!). > > Yes, but sysinstall bugs will probably force you to do most of the > filesystem setup manually. See archives. &#@^! ... In what list? It hasn't hit the archives and I haven't seen anything yet. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 23 20:48:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA02816 for freebsd-current-outgoing; Thu, 23 Jul 1998 20:48:26 -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 UAA02801 for ; Thu, 23 Jul 1998 20:48: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 0yzYpZ-0005iF-00; Thu, 23 Jul 1998 20:47:41 -0700 Date: Thu, 23 Jul 1998 20:47:38 -0700 (PDT) From: Tom X-Sender: tom@shell.uniserve.ca To: Doug White cc: Lee Reese , current@FreeBSD.ORG Subject: Re: Viability of -current for Usenet News 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 Thu, 23 Jul 1998, Doug White wrote: > On Thu, 23 Jul 1998, Tom wrote: > > > > > I've just seen a RedHat 5.1 system with a such a controller, hang. It > > > > doesn't seem the Linux DPT driver is very stable. It seems easy to get > > > > into a situation where all processes accessing the disk, hang. The > > > > FreeBSD DPT driver seems quite a bit more solid than that, although > > > > setting it up is more difficult. > > > > > > Not really anymore, apparently the 2.2.7 boot floppy now has the driver > > > built on it (yay!). > > > > Yes, but sysinstall bugs will probably force you to do most of the > > filesystem setup manually. See archives. > > &#@^! ... In what list? It hasn't hit the archives and I haven't seen > anything yet. This has gone for almost a year. Talked about in frebsd-scsi for sure, and probably freebsd-stable. Basically what happens, is that sysinstall hangs just after newfs'ing the filesystems. The work around is to leave most of the space unallocated, and label it and newfs after booting. Again a very old problem going back to Novemeber or so last year. There has been speculation that since sysinstall uses libdisk, not disklabel to write labels, that the problem might be in the disklabels created by sysinstall on a DPT array, caused by the size and/or geomentry of the DPT array (all the DPT arrays I've under FreeBSD tickled this bug, and all very 16GB or bigger). > Doug White | University of Oregon > Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant > http://gladstone.uoregon.edu/~dwhite | Computer Science Major 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 23 20:58:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA04617 for freebsd-current-outgoing; Thu, 23 Jul 1998 20:58:46 -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 UAA04563 for ; Thu, 23 Jul 1998 20:58:45 -0700 (PDT) (envelope-from sleas@ixion.honeywell.com) Received: from localhost by ixion.honeywell.com with SMTP (1.40.112.8/16.2) id AA251692624; Thu, 23 Jul 1998 22:57:04 -0500 Date: Thu, 23 Jul 1998 22:57:04 -0500 (CDT) From: Shawn Leas To: Doug White Cc: Tom , Lee Reese , current@FreeBSD.ORG Subject: Re: Viability of -current for Usenet News 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 On Thu, 23 Jul 1998, Doug White wrote: > > On Thu, 23 Jul 1998, Tom wrote: > > > > > I've just seen a RedHat 5.1 system with a such a controller, hang. It > > > > doesn't seem the Linux DPT driver is very stable. It seems easy to get > > > > into a situation where all processes accessing the disk, hang. The > > > > FreeBSD DPT driver seems quite a bit more solid than that, although > > > > setting it up is more difficult. > > > > > > Not really anymore, apparently the 2.2.7 boot floppy now has the driver > > > built on it (yay!). > > > > Yes, but sysinstall bugs will probably force you to do most of the > > filesystem setup manually. See archives. > > &#@^! ... In what list? It hasn't hit the archives and I haven't seen > anything yet. I dunno, might he be thinking 2.2.2??? That one had a bug. It's been a little while, so I really don't remember exactly what it did, but it mungled stuff up where you couldn't use sysinstall anymore. -Shawn > Doug White | University of Oregon > Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant > http://gladstone.uoregon.edu/~dwhite | Computer Science Major > > > 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 23 21:03:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA05278 for freebsd-current-outgoing; Thu, 23 Jul 1998 21:03:03 -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 VAA05271 for ; Thu, 23 Jul 1998 21:02:59 -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 AAA17360; Fri, 24 Jul 1998 00:01:57 -0400 (EDT) (envelope-from gjp@gjp.erols.com) X-Mailer: exmh version 2.0.1 12/23/97 To: "Daniel O'Connor" cc: Adrian Penisoara , Gerald Ehritz , freebsd-current@FreeBSD.ORG From: "Gary Palmer" Subject: Re: pine 3.96 locks 3.0-980621 completely In-reply-to: Your message of "Fri, 24 Jul 1998 11:13:31 +0930." <199807240143.LAA02750@cain.gsoft.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 24 Jul 1998 00:01:57 -0400 Message-ID: <17356.901252917@gjp.erols.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Daniel O'Connor" wrote in message ID <199807240143.LAA02750@cain.gsoft.com.au>: > Err.. well isn't it kind of bad that the machine crashes? :) Yep > I mean it _pine_ crashed, then OK, upgrading would be fine, but when the > machine crashes, maybe he should upgrade his version of -current.. It won't change the fact that it is a fundamentally bad idea to rely on NFS locking for mail delivery/reading when we don't impliment said locking in the NFS layer... I know I seem like I'm trying to cover up a bug in freebsd by saying "well, don't do that", but I think anyone who knows anything about e-mail and NFS would agree that it is a fundamentally *bad* idea. (Yes, I know of at least one *large* (like >400,000 users) ISP in the US that uses NFS for mail & news stores. Doesn't mean I don't think they're stupid :) ) 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 Thu Jul 23 21:05:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA05610 for freebsd-current-outgoing; Thu, 23 Jul 1998 21:05:34 -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 VAA05598 for ; Thu, 23 Jul 1998 21:05:27 -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 VAA02204; Thu, 23 Jul 1998 21:04:09 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: Tom cc: Doug White , Lee Reese , current@FreeBSD.ORG Subject: Re: Viability of -current for Usenet News In-reply-to: Your message of "Thu, 23 Jul 1998 19:04:48 PDT." Date: Thu, 23 Jul 1998 21:04:09 -0700 Message-ID: <2200.901253049@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Yes, but sysinstall bugs will probably force you to do most of the > filesystem setup manually. See archives. Please don't spread FUD. The "sysinstall bugs" have already been documented, announced and fixed, nor did they have anything to do with this issue. - 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 23 21:06:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA05914 for freebsd-current-outgoing; Thu, 23 Jul 1998 21:06:55 -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 VAA05909 for ; Thu, 23 Jul 1998 21:06:53 -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 VAA02233; Thu, 23 Jul 1998 21:05:42 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: Tom cc: Doug White , Lee Reese , current@FreeBSD.ORG Subject: Re: Viability of -current for Usenet News In-reply-to: Your message of "Thu, 23 Jul 1998 20:47:38 PDT." Date: Thu, 23 Jul 1998 21:05:42 -0700 Message-ID: <2230.901253142@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > This has gone for almost a year. Talked about in frebsd-scsi for > sure, and probably freebsd-stable. Basically what happens, is that > sysinstall hangs just after newfs'ing the filesystems. The work around is Uh, this sure is news to me. I've *never* seen such symptoms in any of the multiple test systems here nor has anyone sent me a bug report detailing any such behavior. - 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 23 21:16:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA07217 for freebsd-current-outgoing; Thu, 23 Jul 1998 21:16: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 VAA07208 for ; Thu, 23 Jul 1998 21:16:38 -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 VAA27447; Thu, 23 Jul 1998 21:15:56 -0700 (PDT) (envelope-from jdp) Message-Id: <199807240415.VAA27447@austin.polstra.com> To: eculp@webwizard.org.mx Subject: Re: make release In-Reply-To: <35B7F199.A7A88FA@webwizard.org.mx> References: <35B7F199.A7A88FA@webwizard.org.mx> Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Date: Thu, 23 Jul 1998 21:15:55 -0700 From: John Polstra Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <35B7F199.A7A88FA@webwizard.org.mx>, Edwin Culp wrote: > Daily > cvsup -g -L2 cvs-supfile > cvsup -g -L2 cvs-rel > At least weekly > make world and new kernel > Twice a month inmediately after the make world and kernel > make release > > here are my new config files cvs-supfile and cvs-rel that > are causing the problem although I did get through a make > world after manually creating about 6-8 Attic directories. > > # cat cvs-supfile > *default tag=. > *default host=cvsup.FreeBSD.org > *default base=/a > *default prefix=/usr > *default release=cvs > *default delete compress use-rel-suffix > src-all > cvs-crypto > doc-all > src-secure > ports-all > # cat cvs-rel > *default host=cvsup.FreeBSD.org > *default base=/a > *default prefix=/usr > *default release=cvs > *default delete compress use-rel-suffix > src-all > cvs-crypto > doc-all > src-secure > ports-all You are CVSupping both the checked-out -current sources and the CVS repository to the same place ("/usr/{src,doc,ports}"). Why? No wonder you're having problems. For the "cvs-rel" supfile (getting the CVS repository), you should have "*default prefix=/home/ncvs". And if you are getting the CVS repository, you should probably not get the checked-out -current sources ("cvs-supfile") at all. Just check them out of the repository using cvs. I would suggest rereading the CVSup section of the FreeBSD Handbook. -- 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 23 21:21:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA08276 for freebsd-current-outgoing; Thu, 23 Jul 1998 21:21:37 -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 VAA08260; Thu, 23 Jul 1998 21:21:34 -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 VAA27476; Thu, 23 Jul 1998 21:21:12 -0700 (PDT) (envelope-from jdp) Message-Id: <199807240421.VAA27476@austin.polstra.com> To: current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: The Yahoo CVSup link Date: Thu, 23 Jul 1998 21:21:12 -0700 From: John Polstra Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Would the person who submitted the Yahoo link to the CVSup FAQ please contact me? I would like to change the URL to point to the CVSup home page rather than directly to the FAQ. But Yahoo wants the e-mail address of the original submitter for security reasons. OK, the "home page" just has a link to the FAQ, currently. :-) But it might have more stuff in the future. Thanks, 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 23 21:26:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA09360 for freebsd-current-outgoing; Thu, 23 Jul 1998 21:26:32 -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 VAA09350 for ; Thu, 23 Jul 1998 21:26:28 -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 0yzZQZ-0000pE-00; Thu, 23 Jul 1998 21:25:55 -0700 Date: Thu, 23 Jul 1998 21:25:52 -0700 (PDT) From: Tom X-Sender: tom@shell.uniserve.ca To: "Jordan K. Hubbard" cc: Doug White , Lee Reese , current@FreeBSD.ORG Subject: Re: Viability of -current for Usenet News In-Reply-To: <2230.901253142@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 Thu, 23 Jul 1998, Jordan K. Hubbard wrote: > > This has gone for almost a year. Talked about in frebsd-scsi for > > sure, and probably freebsd-stable. Basically what happens, is that > > sysinstall hangs just after newfs'ing the filesystems. The work around is > > Uh, this sure is news to me. I've *never* seen such symptoms in any > of the multiple test systems here nor has anyone sent me a bug report > detailing any such behavior. Strange. I've never had a FreeBSD install onto a DPT system work properly. I was also under the impression that you did not have a DPT card to test with, nor enough hard drives to create a mid-sized array. > - Jordan 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 23 21:27:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA09591 for freebsd-current-outgoing; Thu, 23 Jul 1998 21:27:47 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA09572; Thu, 23 Jul 1998 21:27:42 -0700 (PDT) (envelope-from karl@Mars.mcs.net) Received: from Mars.mcs.net (karl@Mars.mcs.net [192.160.127.85]) by Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id XAA16770; Thu, 23 Jul 1998 23:26:49 -0500 (CDT) Received: (from karl@localhost) by Mars.mcs.net (8.8.7/8.8.2) id XAA01697; Thu, 23 Jul 1998 23:26:49 -0500 (CDT) Message-ID: <19980723232649.30224@mcs.net> Date: Thu, 23 Jul 1998 23:26:49 -0500 From: Karl Denninger To: Gary Palmer Cc: "Daniel O'Connor" , Adrian Penisoara , Gerald Ehritz , freebsd-current@FreeBSD.ORG Subject: Re: pine 3.96 locks 3.0-980621 completely References: <199807240143.LAA02750@cain.gsoft.com.au> <17356.901252917@gjp.erols.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 In-Reply-To: <17356.901252917@gjp.erols.com>; from Gary Palmer on Fri, Jul 24, 1998 at 12:01:57AM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jul 24, 1998 at 12:01:57AM -0400, Gary Palmer wrote: > "Daniel O'Connor" wrote in message ID > <199807240143.LAA02750@cain.gsoft.com.au>: > > Err.. well isn't it kind of bad that the machine crashes? :) > > Yep > > > I mean it _pine_ crashed, then OK, upgrading would be fine, but when the > > machine crashes, maybe he should upgrade his version of -current.. > > It won't change the fact that it is a fundamentally bad idea to rely on NFS > locking for mail delivery/reading when we don't impliment said locking in the > NFS layer... > > I know I seem like I'm trying to cover up a bug in freebsd by saying "well, > don't do that", but I think anyone who knows anything about e-mail and NFS > would agree that it is a fundamentally *bad* idea. > > (Yes, I know of at least one *large* (like >400,000 users) ISP in the > US that uses NFS for mail & news stores. Doesn't mean I don't think they're > stupid :) ) There ARE safe ways to handle email via NFS. We do it here, and other than through abject user stupidity (ie: opening email via both POP3 and Pine at once) or programmatic bugs (ELM has known problems with the folder resync command) it doesn't lose messages or corrupt mailboxes. I get over 1200 emails a DAY. If it wasn't solid and stable you can bet I'd know about it within minutes around here. I will say this - FreeBSD has had problems in the past with NFS which made it impossible to get this to work reliably (primarily during the time period from roughly December '97 to April '98). For this reason we ran pretty old kernels around here for quite some time. Some of the semantics that we rely on to make sure that mail doesn't get smashed do have a couple of potential race conditions under extremely odd circumstances that could lead to trouble - but if we get bit by those, we have far more serious trouble afoot than a lost email message. HOWEVER, "mount and go" DOES NOT WORK SAFELY. In fact, "mount and go" won't work safely even WITH NFS locking on 90% of the machines out there, including Suns. I've yet to see a Sun implementation of rpc.lockd that can't be freaked out under less-than-pleasant circumstances; the usual symptom of such a freak out is a wedged lock that doesn't release, and thus wedged MTAs and MUAa. If you get nailed by that you're going to be rebooting things - not a pleasant thought on production machines. Now NFS for a news store is beyond insane. I don't know why you'd EVER do that on the news server. For *client* access its perfectly fine; client access is read-only, which is completely safe (there is only one *possible* writer). We do that here; the news spool is mounted *read only* on the cluster machines. Never had a single problem with that (nor would I expect to). However, you have to be insane not to have the spool disks LOCAL on the news *server* system. -- -- Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin http://www.mcs.net/ | T1's from $600 monthly / All Lines K56Flex/DOV | NEW! Corporate ISDN Prices dropped by up to 50%! Voice: [+1 312 803-MCS1 x219]| EXCLUSIVE NEW FEATURE ON ALL PERSONAL ACCOUNTS Fax: [+1 312 803-4929] | *SPAMBLOCK* Technology now included at no cost To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 23 21:27:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA09636 for freebsd-current-outgoing; Thu, 23 Jul 1998 21:27:55 -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 VAA09623 for ; Thu, 23 Jul 1998 21:27:51 -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 0yzZRy-0000vZ-00; Thu, 23 Jul 1998 21:27:22 -0700 Date: Thu, 23 Jul 1998 21:27:19 -0700 (PDT) From: Tom X-Sender: tom@shell.uniserve.ca To: "Jordan K. Hubbard" cc: Doug White , Lee Reese , current@FreeBSD.ORG Subject: Re: Viability of -current for Usenet News In-Reply-To: <2200.901253049@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 Thu, 23 Jul 1998, Jordan K. Hubbard wrote: > > Yes, but sysinstall bugs will probably force you to do most of the > > filesystem setup manually. See archives. > > Please don't spread FUD. The "sysinstall bugs" have already been > documented, announced and fixed, nor did they have anything to do with > this issue. Documented? Announced? Gee, I'm on freebsd-stable, freebsd-scsi, and freebsd-scsi and I never saw any "the sysinstall bug that makes installing on DPT arrays is fixed" message. > - Jordan 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 23 21:29:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA09947 for freebsd-current-outgoing; Thu, 23 Jul 1998 21:29:03 -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 VAA09923 for ; Thu, 23 Jul 1998 21:28:49 -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 VAA02524; Thu, 23 Jul 1998 21:27:35 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: Tom cc: Doug White , Lee Reese , current@FreeBSD.ORG Subject: Re: Viability of -current for Usenet News In-reply-to: Your message of "Thu, 23 Jul 1998 21:25:52 PDT." Date: Thu, 23 Jul 1998 21:27:35 -0700 Message-ID: <2520.901254455@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Strange. I've never had a FreeBSD install onto a DPT system work > properly. I was also under the impression that you did not have a DPT card > to test with, nor enough hard drives to create a mid-sized array. The latter is true, but I've certainly heard a fair number of success stories regarding the former. Perhaps Simon would be more inclined to comment at this point. - 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 23 21:30:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA10163 for freebsd-current-outgoing; Thu, 23 Jul 1998 21:30:24 -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 VAA10057 for ; Thu, 23 Jul 1998 21:29:51 -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 VAA02539; Thu, 23 Jul 1998 21:28:36 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: Tom cc: Doug White , Lee Reese , current@FreeBSD.ORG Subject: Re: Viability of -current for Usenet News In-reply-to: Your message of "Thu, 23 Jul 1998 21:27:19 PDT." Date: Thu, 23 Jul 1998 21:28:35 -0700 Message-ID: <2536.901254515@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Documented? Announced? Gee, I'm on freebsd-stable, freebsd-scsi, and > freebsd-scsi and I never saw any "the sysinstall bug that makes installing > on DPT arrays is fixed" message. I'm talking of another set of bugs. I'm on -stable and -scsi too (though I'm only on -scsi once :) and I never saw any "sysinstall is broken on DPT arrays" message either, so there's nothing to refute. :) - 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 23 21:35:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA11446 for freebsd-current-outgoing; Thu, 23 Jul 1998 21:35:23 -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 VAA11417 for ; Thu, 23 Jul 1998 21:35:10 -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 0yzZZ1-0001Uu-00; Thu, 23 Jul 1998 21:34:39 -0700 Date: Thu, 23 Jul 1998 21:34:36 -0700 (PDT) From: Tom X-Sender: tom@shell.uniserve.ca To: "Jordan K. Hubbard" cc: Doug White , Lee Reese , current@FreeBSD.ORG Subject: Re: Viability of -current for Usenet News In-Reply-To: <2520.901254455@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 Thu, 23 Jul 1998, Jordan K. Hubbard wrote: > > Strange. I've never had a FreeBSD install onto a DPT system work > > properly. I was also under the impression that you did not have a DPT card > > to test with, nor enough hard drives to create a mid-sized array. > > The latter is true, but I've certainly heard a fair number of success > stories regarding the former. Perhaps Simon would be more inclined > to comment at this point. I don't think he is on current, but this has been dicussed on freebsd-scsi just after the 2.2.6 release. He has the same problem that I have (sysinstall hanging after newfs), and he uses the same work around that I do. > - Jordan 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 23 23:00:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA23663 for freebsd-current-outgoing; Thu, 23 Jul 1998 23:00:08 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from argus.tfs.net (as2-p90.tfs.net [139.146.205.90] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA23552 for ; Thu, 23 Jul 1998 22:59:57 -0700 (PDT) (envelope-from jbryant@unix.tfs.net) Received: (from jbryant@localhost) by argus.tfs.net (8.8.8/8.8.5) id AAA12707 for freebsd-current@freebsd.org; Fri, 24 Jul 1998 00:34:21 -0500 (CDT) From: Jim Bryant Message-Id: <199807240534.AAA12707@argus.tfs.net> Subject: _inet_addr and _inet_ntoa in libc.a To: freebsd-current@FreeBSD.ORG Date: Fri, 24 Jul 1998 00:34:21 -0500 (CDT) Reply-to: jbryant@unix.tfs.net X-Windows: R00LZ!@# MS-Winbl0wz DR00LZ!@# X-files: The truth is that the X-Files is fiction X-Republican: The best kind!!! X-Operating-System: FreeBSD 3.0-CURRENT #0: Sat Jun 20 11:57:05 CDT 1998 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 oops... forgot to mention that my last kernel and installworld were cvsupped at Jul 23 1998, 0000 CDT. jim -- All opinions expressed are mine, if you | "I will not be pushed, stamped, think otherwise, then go jump into turbid | briefed, debriefed, indexed, or radioactive waters and yell WAHOO !!! | numbered!" - #1, "The Prisoner" ------------------------------------------------------------------------------ Inet: jbryant@tfs.net AX.25: kc5vdj@wv0t.#neks.ks.usa.noam grid: EM28pw voice: KC5VDJ - 6 & 2 Meters AM/FM/SSB, 70cm FM. http://www.tfs.net/~jbryant ------------------------------------------------------------------------------ HF/6M/2M: IC-706-MkII, 2M: HTX-212, 2M: HTX-202, 70cm: HTX-404, Packet: KPC-3+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 23 23:00:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA23733 for freebsd-current-outgoing; Thu, 23 Jul 1998 23:00:15 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from argus.tfs.net (as2-p90.tfs.net [139.146.205.90] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA23612 for ; Thu, 23 Jul 1998 23:00:03 -0700 (PDT) (envelope-from jbryant@unix.tfs.net) Received: (from jbryant@localhost) by argus.tfs.net (8.8.8/8.8.5) id AAA11316 for freebsd-current@freebsd.org; Fri, 24 Jul 1998 00:30:31 -0500 (CDT) From: Jim Bryant Message-Id: <199807240530.AAA11316@argus.tfs.net> Subject: _inet_ntoa and _inet_addr in libc.a To: freebsd-current@FreeBSD.ORG Date: Fri, 24 Jul 1998 00:30:31 -0500 (CDT) Reply-to: jbryant@unix.tfs.net X-Windows: R00LZ!@# MS-Winbl0wz DR00LZ!@# X-files: The truth is that the X-Files is fiction X-Republican: The best kind!!! X-Operating-System: FreeBSD 3.0-CURRENT #0: Sat Jun 20 11:57:05 CDT 1998 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 i have been patiently waiting for the following to be fixed for some time now [note that tcp_wrappers is messed too]: ---- cd /usr/ports/security/ssh ; make . . . cc -pipe -I/usr/local/include -o ssh ssh.o sshconnect.o log-client.o readconf.o hostfile.o readpass.o tildexpand.o clientloop.o canohost.o idea.o rsa.o randoms.o md5.o buffer.o emulate.o packet.o compress.o xmalloc.o ttymodes.o newchannels.o bufaux.o authfd.o authfile.o crc32.o rsaglue.o cipher.o des.o match.o arcfour.o mpaux.o userfile.o signals.o blowfish.o deattack.o -L/usr/lib -lgmp -L/usr/lib -lz -lwrap -lcrypt -L/usr/local/lib -lutil sshconnect.o: Undefined symbol `___inet_addr' referenced from text segment sshconnect.o: Undefined symbol `___inet_ntoa' referenced from text segment sshconnect.o: Undefined symbol `___inet_ntoa' referenced from text segment canohost.o: Undefined symbol `___inet_ntoa' referenced from text segment canohost.o: Undefined symbol `___inet_ntoa' referenced from text segment canohost.o: Undefined symbol `___inet_ntoa' referenced from text segment canohost.o: Undefined symbol `___inet_ntoa' referenced from text segment canohost.o: Undefined symbol `___inet_ntoa' referenced from text segment canohost.o: Undefined symbol `___inet_ntoa' referenced from text segment canohost.o: Undefined symbol `___inet_ntoa' referenced from text segment newchannels.o: Undefined symbol `___inet_addr' referenced from text segment newchannels.o: Undefined symbol `___inet_addr' referenced from text segment newchannels.o: Undefined symbol `___inet_addr' referenced from text segment /usr/local/lib/libwrap.so.7.6: Undefined symbol `___inet_addr' referenced *** Error code 1 Stop. ---- i have come up with two possible reasons for why this is still a problem: 1). i am hopelessly out of sync with -current. 2). -current is hopelessly out of sync with it's own libs. ---- [/usr/include/arpa/inet.h] /* XXX all new diversions!! argh!! */ #define inet_addr __inet_addr #define inet_aton __inet_aton #define inet_lnaof __inet_lnaof #define inet_makeaddr __inet_makeaddr #define inet_neta __inet_neta #define inet_netof __inet_netof #define inet_network __inet_network #define inet_net_ntop __inet_net_ntop #define inet_net_pton __inet_net_pton #define inet_ntoa __inet_ntoa #define inet_pton __inet_pton #define inet_ntop __inet_ntop #define inet_nsap_addr __inet_nsap_addr #define inet_nsap_ntoa __inet_nsap_ntoa ---- [cd /usr/lib/aout ; nm libc.a] . . . 00000000 I _inet_addr . . . 00000000 I _inet_ntoa . . . inet_ntoa.o: 00000020 T ___inet_ntoa U ___inet_ntop inet_addr.o: U __CurrentRuneLocale U __DefaultRuneLocale U ____runetype 00000000 T ___inet_addr 00000030 T ___inet_aton ---- jim -- All opinions expressed are mine, if you | "I will not be pushed, stamped, think otherwise, then go jump into turbid | briefed, debriefed, indexed, or radioactive waters and yell WAHOO !!! | numbered!" - #1, "The Prisoner" ------------------------------------------------------------------------------ Inet: jbryant@tfs.net AX.25: kc5vdj@wv0t.#neks.ks.usa.noam grid: EM28pw voice: KC5VDJ - 6 & 2 Meters AM/FM/SSB, 70cm FM. http://www.tfs.net/~jbryant ------------------------------------------------------------------------------ HF/6M/2M: IC-706-MkII, 2M: HTX-212, 2M: HTX-202, 70cm: HTX-404, Packet: KPC-3+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 23 23:18:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA26455 for freebsd-current-outgoing; Thu, 23 Jul 1998 23:18:43 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA26450 for ; Thu, 23 Jul 1998 23:18:40 -0700 (PDT) (envelope-from kuku@gilberto.physik.RWTH-Aachen.DE) Received: from gilberto.physik.RWTH-Aachen.DE (gilberto.physik.rwth-aachen.de [137.226.30.2]) by freefall.freebsd.org (8.8.8/8.8.5) with ESMTP id XAA08496 for ; Thu, 23 Jul 1998 23:17:57 -0700 (PDT) Received: (from kuku@localhost) by gilberto.physik.RWTH-Aachen.DE (8.8.8/8.8.7) id IAA15706 for freebsd-current@freefall.cdrom.com; Fri, 24 Jul 1998 08:18:11 +0200 (MEST) (envelope-from kuku) Date: Fri, 24 Jul 1998 08:18:11 +0200 (MEST) From: Christoph Kukulies Message-Id: <199807240618.IAA15706@gilberto.physik.RWTH-Aachen.DE> To: freebsd-current@freefall.cdrom.com Subject: more to be done in make bootstrap Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I would suggest to examine again the make bootstrap target in the make world process. While upgrading a one year old 3.0 -current system from a compiled src tree I found that some targets need to be there prior to doing a make install: tree (x)install config size ranlib /usr/lib/aout (make hierarchy first) This is not precise, just a collection of stumbling blocks I came across. -- Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 23 23:21:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA26954 for freebsd-current-outgoing; Thu, 23 Jul 1998 23:21:52 -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 XAA26942 for ; Thu, 23 Jul 1998 23:21:48 -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 CAA23524 for ; Fri, 24 Jul 1998 02:21:23 -0400 (EDT) Date: Fri, 24 Jul 1998 02:21:23 -0400 (EDT) From: Brian Feldman To: freebsd-current@FreeBSD.ORG Subject: fs weirdness 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 Bear in mind through the following that root was mounted normally, not SoftUpdates, not async. I was working with vn(4) drives earlier, and so was doing a lot of dd if=/dev/zero'ing. I wanted to create two pan60 drives, one on wd0, one on wd1, and vnconfiged to vn0 and vn1, to attempt use of ccd for striping (if anyone can help, I still haven't gotten it to work right at all... what's the correct order, disklabel, fdisk, newfs? I can't seem to get newfs to work at all...). The first drive I was making via (in $PWD==/) dd if=/dev/zero of=stripe bs=512 count=121xxx. Inadvertantly, I ran dd again with the exact same parameters; the following weirdness came to be (this is after removing, fscking, mounting, etc... at the time, the free space was -something, but you get the idea): Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/wd0s1a 98479 -40815 131416 -45% / when I fscked /, I saw what I was looking for, an unref file, and I let fsck delete it; of course, mount -u -o update / and sync()'ing didn't help at all, and I had no free space, with no file taking up the space (fsdb, fsck, and ls all verified nothing was taking up this space). To provide the real numbers, via fsck: 2316 files, 22713 used, 75766 free (1502 frags, 9283 blocks, 1.5% fragmentation) So something went wrong; I mounted /dev/wd0a /mnt (root is wd0s1a) and removed the _supposedly_ removed /mnt/stripe which appeared there, synced, and umounted /mnt. /stripe STILL existed, so I rm'ed it again, and now we're up to the present. Something went wrong somewhere... it seems that when dd unlinked the file, the kernel didn't pick up on the fact that there were no links to the file and remove the contents of the inode which /stripe, like it usually does if a file is unlinked and there are no links left, right? So that's basically all I've got about this problem, anyone who wants to comment on it, or try to pry more info from me, go ahead, I think that about does it for relevant info. Cheers, Brian Feldman green@unixhelp.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 24 00:27:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA05631 for freebsd-current-outgoing; Fri, 24 Jul 1998 00:27:33 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from vexpert.dbai.tuwien.ac.at (vexpert.dbai.tuwien.ac.at [128.130.111.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA05626 for ; Fri, 24 Jul 1998 00:27:30 -0700 (PDT) (envelope-from ehritz@dbai.tuwien.ac.at) Received: from arcturus.dbai.tuwien.ac.at (arcturus.dbai.tuwien.ac.at [128.130.111.20]) by vexpert.dbai.tuwien.ac.at (8.8.8/8.8.8) with ESMTP id JAA05271 for ; Fri, 24 Jul 1998 09:27:06 +0200 (MET-DST) From: Gerald Ehritz Received: (from ehritz@localhost) by arcturus.dbai.tuwien.ac.at (8.8.5/8.8.5) id JAA08572 for freebsd-current@freebsd.org; Fri, 24 Jul 1998 09:27:07 +0200 (MET DST) Date: Fri, 24 Jul 1998 09:27:07 +0200 (MET DST) Message-Id: <199807240727.JAA08572@arcturus.dbai.tuwien.ac.at> To: freebsd-current@FreeBSD.ORG Subject: Re: pine 3.96 locks 3.0-980621 completely X-Sun-Charset: US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, to give some more infos: >I guess the problem is the NFS mounted mail directory; We used pine 3.9x on FreeBSD 2.2 for a year (or more) without problems. Our site uses a mix of Sun Sparcs and PC's, holding the home dirs on a Sun with SunOS 4.1.3 (NFS V2), and also holding all mails. On all clients we mount mail and home dir using NFS. > You may want to try a newer Pine 4 version We tested pine 4.0 and it also fails. Could not test 4.02 because of a permission denied on freebsd.org. > Err.. well isn't it kind of bad that the machine crashes? :) This indeed is very bad. But pine also managed to kill Solaris. :) But i want to say here it worked on an old release of FreeBSD and do not work on a 3.0 beta. > Hmm ... it may mmap() it which can cause problems, so maybe and upgrade of -current will fix it. I saw some problems with -current of the last 2-3 weeks. Which -current is stable enough? We have no problems with the version i installed, except pine. Gerald To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 24 00:34:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA06854 for freebsd-current-outgoing; Fri, 24 Jul 1998 00:34:20 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from vexpert.dbai.tuwien.ac.at (vexpert.dbai.tuwien.ac.at [128.130.111.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA06842 for ; Fri, 24 Jul 1998 00:34:13 -0700 (PDT) (envelope-from ehritz@dbai.tuwien.ac.at) Received: from arcturus.dbai.tuwien.ac.at (arcturus.dbai.tuwien.ac.at [128.130.111.20]) by vexpert.dbai.tuwien.ac.at (8.8.8/8.8.8) with ESMTP id JAA05360 for ; Fri, 24 Jul 1998 09:33:48 +0200 (MET-DST) From: Gerald Ehritz Received: (from ehritz@localhost) by arcturus.dbai.tuwien.ac.at (8.8.5/8.8.5) id JAA08600 for freebsd-current@freebsd.org; Fri, 24 Jul 1998 09:33:49 +0200 (MET DST) Date: Fri, 24 Jul 1998 09:33:49 +0200 (MET DST) Message-Id: <199807240733.JAA08600@arcturus.dbai.tuwien.ac.at> To: freebsd-current@FreeBSD.ORG Subject: Re: pine 3.96 locks 3.0-980621 completely X-Sun-Charset: US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi > We use a 3.0-980621 and discovered soem days ago, that writing out an >attachment ( > 100k) to a file locks up the machine completely. No login >possible and also no log to screen or file. I did a new test with pine 3.96. I wrote the attachment to /tmp and it worked. So it looks like NFS is involved, but reading and writing mail across a NFS mounted dir works! Gerald To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 24 00:49:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA08923 for freebsd-current-outgoing; Fri, 24 Jul 1998 00:49:31 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA08918 for ; Fri, 24 Jul 1998 00:49:29 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.5/8.8.8) with SMTP id AAA28136; Fri, 24 Jul 1998 00:49:05 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Fri, 24 Jul 1998 00:49:04 -0700 (PDT) From: Doug White To: Jim Bryant cc: freebsd-current@FreeBSD.ORG Subject: Re: _inet_ntoa and _inet_addr in libc.a In-Reply-To: <199807240530.AAA11316@argus.tfs.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 Fri, 24 Jul 1998, Jim Bryant wrote: > i have been patiently waiting for the following to be fixed for some > time now [note that tcp_wrappers is messed too]: > > cc -pipe -I/usr/local/include -o ssh ssh.o sshconnect.o log-client.o readconf.o hostfile.o readpass.o tildexpand.o clientloop.o canohost.o idea.o rsa.o randoms.o md5.o buffer.o emulate.o packet.o compress.o xmalloc.o ttymodes.o newchannels.o bufaux.o authfd.o authfile.o crc32.o rsaglue.o cipher.o des.o match.o arcfour.o mpaux.o userfile.o signals.o blowfish.o deattack.o -L/usr/lib -lgmp -L/usr/lib -lz -lwrap -lcrypt -L/usr/local/lib -lutil > sshconnect.o: Undefined symbol `___inet_addr' referenced from text segment > sshconnect.o: Undefined symbol `___inet_ntoa' referenced from text segment > sshconnect.o: Undefined symbol `___inet_ntoa' referenced from text segment [...] > 1). i am hopelessly out of sync with -current. > 2). -current is hopelessly out of sync with it's own libs. Hm, I got this to explode on my current box, then did cd /usr/lib mkdir foo mv /usr/lib/lib* foo rebuilt the port and all was well. This was upgraded from a 2.2.6 box, thus the files in /usr/lib. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 24 01:09:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA13527 for freebsd-current-outgoing; Fri, 24 Jul 1998 01:09:04 -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 BAA13522 for ; Fri, 24 Jul 1998 01:09:02 -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 SAA17940; Fri, 24 Jul 1998 18:08:37 +1000 Date: Fri, 24 Jul 1998 18:08:37 +1000 From: Bruce Evans Message-Id: <199807240808.SAA17940@godzilla.zeta.org.au> To: freebsd-current@FreeBSD.ORG, jbryant@unix.tfs.net Subject: Re: _inet_ntoa and _inet_addr in libc.a Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >cc -pipe -I/usr/local/include -o ssh ssh.o sshconnect.o log-client.o readconf.o hostfile.o readpass.o tildexpand.o clientloop.o canohost.o idea.o rsa.o randoms.o md5.o buffer.o emulate.o packet.o compress.o xmalloc.o ttymodes.o newchannels.o bufaux.o authfd.o authfile.o crc32.o rsaglue.o cipher.o des.o match.o arcfour.o mpaux.o userfile.o signals.o blowfish.o deattack.o -L/usr/lib -lgmp -L/usr/lib -lz -lwrap -lcrypt -L/usr/local/lib -lutil Looks like ssh attempts to shoot itself in the foot using -L/usr/lib, and succeeds because of garbage libraries in /usr/lib. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 24 02:47:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA01161 for freebsd-current-outgoing; Fri, 24 Jul 1998 02:47:07 -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 CAA01152 for ; Fri, 24 Jul 1998 02:47:01 -0700 (PDT) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id FAA20438; Fri, 24 Jul 1998 05:45:36 -0400 (EDT) (envelope-from luoqi) Date: Fri, 24 Jul 1998 05:45:36 -0400 (EDT) From: Luoqi Chen Message-Id: <199807240945.FAA20438@lor.watermarkgroup.com> To: green@zone.baldcom.net, jkh@time.cdrom.com Subject: Re: vn subsystem Cc: bright@hotjobs.com, freebsd-current@FreeBSD.ORG, joelh@gnu.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > mount /dev/vn0 /msdos (oops, should this matter anyway?) > > mount_msdos /dev/vn0 /msdos > > Try it without the bad mount first. This sounds an awful lot like > another PR which has nothing to do with vn (e.g. it would do the *same* > thing if you tried to do this with a non-vn device). > > - Jordan > I took a look at this problem, I found there're some bugs in VMIO code when dealing with buf at a non-page-aligned blkno, e.g. reading one page size of data at block 1 from a block device, as Brian Feldman's core dump shows, since the buf does not start at a page bounary, it should span two pages, yet only one page is allocated in the current code, and subsequent write to the 2nd page would result in a fault. I took a shot at fixing this problem, resulted in the patch below. Would any knowledgeable person please take a look at the patch? I've found no ill effect so far (I just finished a successful buildworld with a patched kernel). Thanks -lq Index: vfs_bio.c =================================================================== RCS file: /fun/cvs/src/sys/kern/vfs_bio.c,v retrieving revision 1.167 diff -u -r1.167 vfs_bio.c --- vfs_bio.c 1998/07/13 07:05:55 1.167 +++ vfs_bio.c 1998/07/24 08:14:34 @@ -1325,6 +1325,7 @@ if (vm_page_is_valid(m, (vm_offset_t) ((toff + off) & PAGE_MASK), tinc) == 0) return 0; + tinc = PAGE_SIZE - ((toff + off) & PAGE_MASK); } return 1; } @@ -1367,9 +1368,9 @@ break; } } - boffset = (i << PAGE_SHIFT); + boffset = (i << PAGE_SHIFT) - (bp->b_offset & PAGE_MASK); if (boffset < bp->b_dirtyoff) { - bp->b_dirtyoff = boffset; + bp->b_dirtyoff = max(boffset, 0); } /* @@ -1381,11 +1382,14 @@ } } boffset = (i + 1); +#if 0 offset = boffset + bp->b_pages[0]->pindex; if (offset >= object->size) boffset = object->size - bp->b_pages[0]->pindex; - if (bp->b_dirtyend < (boffset << PAGE_SHIFT)) - bp->b_dirtyend = (boffset << PAGE_SHIFT); +#endif + boffset = (boffset << PAGE_SHIFT) - (bp->b_offset & PAGE_MASK); + if (bp->b_dirtyend < boffset) + bp->b_dirtyend = min(boffset, bp->b_bufsize); } } @@ -1398,21 +1402,9 @@ struct buf *bp; int i, s; struct bufhashhdr *bh; - int maxsize; int generation; int checksize; - if (vp->v_mount) { - maxsize = vp->v_mount->mnt_stat.f_iosize; - /* - * This happens on mount points. - */ - if (maxsize < size) - maxsize = size; - } else { - maxsize = size; - } - #if !defined(MAX_PERF) if (size > MAXBSIZE) panic("getblk: size(%d) > MAXBSIZE(%d)\n", size, MAXBSIZE); @@ -1503,7 +1495,22 @@ splx(s); return (bp); } else { - vm_object_t obj; + int bsize, maxsize, vmio; + off_t offset; + + if (vp->v_type == VBLK) + bsize = DEV_BSIZE; + else if (vp->v_mountedhere) + bsize = vp->v_mountedhere->mnt_stat.f_iosize; + else if (vp->v_mount) + bsize = vp->v_mount->mnt_stat.f_iosize; + else + bsize = size; + + offset = (off_t)blkno * bsize; + vmio = (vp->v_object != 0) && (vp->v_flag & VOBJBUF); + maxsize = vmio ? size + (offset & PAGE_MASK) : size; + maxsize = imax(maxsize, bsize); if ((bp = getnewbuf(vp, blkno, slpflag, slptimeo, size, maxsize)) == 0) { @@ -1531,18 +1538,14 @@ * be found by incore. */ bp->b_blkno = bp->b_lblkno = blkno; - - if (vp->v_type != VBLK) - bp->b_offset = (off_t) blkno * maxsize; - else - bp->b_offset = (off_t) blkno * DEV_BSIZE; + bp->b_offset = offset; bgetvp(vp, bp); LIST_REMOVE(bp, b_hash); bh = BUFHASH(vp, blkno); LIST_INSERT_HEAD(bh, bp, b_hash); - if ((obj = vp->v_object) && (vp->v_flag & VOBJBUF)) { + if (vmio) { bp->b_flags |= (B_VMIO | B_CACHE); #if defined(VFS_BIO_DEBUG) if (vp->v_type != VREG && vp->v_type != VBLK) @@ -1695,7 +1698,8 @@ int desiredpages; newbsize = (size + DEV_BSIZE - 1) & ~(DEV_BSIZE - 1); - desiredpages = (round_page(newbsize) >> PAGE_SHIFT); + desiredpages = size == 0 ? 0 : + num_pages((bp->b_offset & PAGE_MASK) + newbsize); #if !defined(NO_B_MALLOC) if (bp->b_flags & B_MALLOC) @@ -1744,8 +1748,6 @@ if (bp->b_npages < desiredpages) { obj = vp->v_object; tinc = PAGE_SIZE; - if (tinc > bsize) - tinc = bsize; off = bp->b_offset; #ifdef DIAGNOSTIC @@ -1759,10 +1761,9 @@ bp->b_validend = orig_validend; bp->b_flags |= B_CACHE; for (toff = 0; toff < newbsize; toff += tinc) { - int bytesinpage; - - pageindex = toff >> PAGE_SHIFT; objoff = OFF_TO_IDX(off + toff); + pageindex = objoff - OFF_TO_IDX(off); + tinc = PAGE_SIZE - ((off + toff) & PAGE_MASK); if (pageindex < curbpnpages) { m = bp->b_pages[pageindex]; @@ -1770,11 +1771,10 @@ if (m->pindex != objoff) panic("allocbuf: page changed offset??!!!?"); #endif - bytesinpage = tinc; if (tinc > (newbsize - toff)) - bytesinpage = newbsize - toff; + tinc = newbsize - toff; if (bp->b_flags & B_CACHE) - vfs_buf_set_valid(bp, off, toff, bytesinpage, m); + vfs_buf_set_valid(bp, off, toff, tinc, m); continue; } m = vm_page_lookup(obj, objoff); @@ -1782,7 +1782,7 @@ m = vm_page_alloc(obj, objoff, VM_ALLOC_NORMAL); if (!m) { VM_WAIT; - vm_pageout_deficit += (desiredpages - bp->b_npages); + vm_pageout_deficit += (desiredpages - curbpnpages); goto doretry; } @@ -1805,11 +1805,10 @@ (cnt.v_free_min + cnt.v_cache_min))) { pagedaemon_wakeup(); } - bytesinpage = tinc; if (tinc > (newbsize - toff)) - bytesinpage = newbsize - toff; + tinc = newbsize - toff; if (bp->b_flags & B_CACHE) - vfs_buf_set_valid(bp, off, toff, bytesinpage, m); + vfs_buf_set_valid(bp, off, toff, tinc, m); m->flags &= ~PG_ZERO; vm_page_wire(m); } @@ -2154,7 +2153,7 @@ * This only bothers with the first valid range in the * page. */ - svalid = off; + svalid = trunc_page(foff + off) - foff; while (validbits && !(validbits & 1)) { svalid += DEV_BSIZE; validbits >>= 1; @@ -2164,6 +2163,7 @@ evalid += DEV_BSIZE; validbits >>= 1; } + evalid = min(evalid, off + size); /* * Make sure this range is contiguous with the range * built up from previous pages. If not, then we will @@ -2192,15 +2192,14 @@ vm_ooffset_t soff, eoff; soff = off; - eoff = off + min(PAGE_SIZE, bp->b_bufsize); + eoff = min(off + PAGE_SIZE, bp->b_offset + bp->b_bufsize); if (vp->v_tag == VT_NFS && vp->v_type != VBLK) { vm_ooffset_t sv, ev; vm_page_set_invalid(m, (vm_offset_t) (soff & PAGE_MASK), (vm_offset_t) (eoff - soff)); - off = off - pageno * PAGE_SIZE; - sv = off + ((bp->b_validoff + DEV_BSIZE - 1) & ~(DEV_BSIZE - 1)); - ev = off + ((bp->b_validend + DEV_BSIZE - 1) & ~(DEV_BSIZE - 1)); + sv = (bp->b_offset + bp->b_validoff + DEV_BSIZE - 1) & ~(DEV_BSIZE - 1); + ev = (bp->b_offset + bp->b_validend) & ~(DEV_BSIZE - 1); soff = qmax(sv, soff); eoff = qmin(ev, eoff); } @@ -2285,18 +2284,21 @@ panic("vfs_clean_pages: no buffer offset"); #endif - for (i = 0; i < bp->b_npages; i++, foff += PAGE_SIZE) { + for (i = 0; i < bp->b_npages; i++) { vm_page_t m = bp->b_pages[i]; vfs_page_set_valid(bp, foff, i, m); + foff = trunc_page(foff + PAGE_SIZE); } } } void vfs_bio_clrbuf(struct buf *bp) { - int i; + int i, size; + caddr_t sa, ea; if ((bp->b_flags & (B_VMIO | B_MALLOC)) == B_VMIO) { - if( (bp->b_npages == 1) && (bp->b_bufsize < PAGE_SIZE)) { + if( (bp->b_npages == 1) && (bp->b_bufsize < PAGE_SIZE) && + (bp->b_offset & PAGE_MASK) == 0) { int mask; mask = 0; for(i=0;ib_bufsize;i+=DEV_BSIZE) @@ -2309,19 +2311,23 @@ bp->b_resid = 0; return; } - for(i=0;ib_npages;i++) { + ea = sa = bp->b_data; + for(i=0;ib_npages;i++,sa=ea) { + ea = (caddr_t)trunc_page((vm_offset_t)sa + PAGE_SIZE); + ea = (caddr_t)ulmin((u_long)ea, + (u_long)bp->b_data + bp->b_bufsize); if( bp->b_pages[i]->valid == VM_PAGE_BITS_ALL) continue; if( bp->b_pages[i]->valid == 0) { if ((bp->b_pages[i]->flags & PG_ZERO) == 0) { - bzero(bp->b_data + (i << PAGE_SHIFT), PAGE_SIZE); + bzero(sa, ea - sa); } } else { int j; - for(j=0;jb_pages[i]->flags & PG_ZERO) == 0) && (bp->b_pages[i]->valid & (1<b_data + (i << PAGE_SHIFT) + j * DEV_BSIZE, DEV_BSIZE); + bzero(sa, DEV_BSIZE); } } bp->b_pages[i]->valid = VM_PAGE_BITS_ALL; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 24 03:19:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA06740 for freebsd-current-outgoing; Fri, 24 Jul 1998 03:19:38 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA06730 for ; Fri, 24 Jul 1998 03:19:33 -0700 (PDT) (envelope-from kuku@gilberto.physik.RWTH-Aachen.DE) Received: from gilberto.physik.RWTH-Aachen.DE (gilberto.physik.rwth-aachen.de [137.226.30.2]) by freefall.freebsd.org (8.8.8/8.8.5) with ESMTP id DAA16941 for ; Fri, 24 Jul 1998 03:18:48 -0700 (PDT) Received: (from kuku@localhost) by gilberto.physik.RWTH-Aachen.DE (8.8.8/8.8.7) id MAA16826 for freebsd-current@freefall.cdrom.com; Fri, 24 Jul 1998 12:19:09 +0200 (MEST) (envelope-from kuku) Date: Fri, 24 Jul 1998 12:19:09 +0200 (MEST) From: Christoph Kukulies Message-Id: <199807241019.MAA16826@gilberto.physik.RWTH-Aachen.DE> To: freebsd-current@freefall.cdrom.com Subject: /usr/lib/aout Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I assume /usr/lib/aout has been invented to tell from elm vs. aout based systems. When I upgrade a 1 year old -current system to a -current, what should happen with the libs /usr/lib. Should I remove them all? And should I remove /usr/lib in the ldconfig path arguments at any rate? -- Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 24 03:28:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA08414 for freebsd-current-outgoing; Fri, 24 Jul 1998 03:28:48 -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 DAA08398 for ; Fri, 24 Jul 1998 03:28:36 -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 UAA25308; Fri, 24 Jul 1998 20:28:09 +1000 Date: Fri, 24 Jul 1998 20:28:09 +1000 From: Bruce Evans Message-Id: <199807241028.UAA25308@godzilla.zeta.org.au> To: bde@zeta.org.au, dwhite@resnet.uoregon.edu Subject: Re: Does building current on 2.2.x still work? Cc: current@FreeBSD.ORG, imp@village.org, jb@cimlogic.com.au Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> The -m arg is already covered by adding it to .MAKEFLAGS. Except of >> course for world and buildworld where -m can't be used since it doesn't >> exist in 2.1, and for installworld where there seems to be no reason >> to avoid it. > >This begs the question: > >Can you build from 2.1.x ANYWAY? Don't know. It was reported to work from 2.1.5 when building from old versions was first supported in rev.1.133 (1997/08/05). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 24 04:18:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA17746 for freebsd-current-outgoing; Fri, 24 Jul 1998 04:18:05 -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 EAA17590 for ; Fri, 24 Jul 1998 04:18:00 -0700 (PDT) (envelope-from rkw@dataplex.net) Received: from [208.2.87.5] (user5.dataplex.net [208.2.87.5]) by shrimp.dataplex.net (8.8.8/8.8.5) with ESMTP id GAA20200; Fri, 24 Jul 1998 06:17:31 -0500 (CDT) X-Sender: rkw@mail.dataplex.net Message-Id: In-Reply-To: <199807230428.VAA15996@usr05.primenet.com> References: <199807221200.WAA17349@godzilla.zeta.org.au> from "Bruce Evans" at Jul 22, 98 10:00:25 pm Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Fri, 24 Jul 1998 06:17:08 -0500 To: Terry Lambert From: Richard Wackerbarth Subject: Re: Does building current on 2.2.x still work? Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 11:28 PM -0500 7/22/98, Terry Lambert wrote: >> Yes, installing .mk files just to bootstrap would cause much the same >> problems as making the infamous `includes' target just to bootstrap. >I think it should just use the right ones. If necessary, it should >build the new make to get the -m option for the reinvocation of make. > >A "worse than 'includes'" problem is DESTDIR. It means that you can't >keep a buildable system while attempting to resolve >It does this because there is no seperation of >"build environment" from "build target". Keep preaching, Terry. Perhaps you can eventually gain some converts and they will allow the reorganization necessary to catch up with the capabilities that we had 35 years ago. Needless to say, I tried and gave up. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 24 04:33:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA19935 for freebsd-current-outgoing; Fri, 24 Jul 1998 04:33:20 -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 EAA19929 for ; Fri, 24 Jul 1998 04:33:17 -0700 (PDT) (envelope-from rkw@dataplex.net) Received: from [208.2.87.5] (user5.dataplex.net [208.2.87.5]) by shrimp.dataplex.net (8.8.8/8.8.5) with ESMTP id GAA20237; Fri, 24 Jul 1998 06:32:44 -0500 (CDT) X-Sender: rkw@mail.dataplex.net Message-Id: In-Reply-To: <199807230532.PAA01812@cimlogic.com.au> References: <199807230421.VAA15337@usr05.primenet.com> from Terry Lambert at "Jul 23, 98 04:21:43 am" Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Fri, 24 Jul 1998 06:32:18 -0500 To: John Birrell From: Richard Wackerbarth Subject: Re: Does building current on 2.2.x still work? Cc: current@FreeBSD.ORG, tlambert@primenet.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Terry Lambert wrote: >This is a problem with a source file, not the build system as such, so >I guess it is up to whoever "looks after" the de driver in FreeBSD to >comment. Yes. This is yet another case of using the wrong thing that looks right because they are the same in the trivial case. >Without the -m argument, make grabs the installed sys.mk and if this is >the thing that needs to be upgraded, I can't see how it can "do the >right thing". You NEVER use ANY of the defaults to actually build a new system. ALL of the definitions are self contained in the source. The "correct" invocation of 'make' specifies the collection of mk files to be used. As a bootstrap, you "wrap" the top level call into a simple one that doesn't really care what is in the default set but uses the system-installed 'make' (without all the arguments) to call one with all the context specified. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 24 05:39:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA28920 for freebsd-current-outgoing; Fri, 24 Jul 1998 05:39:48 -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 FAA28908 for ; Fri, 24 Jul 1998 05:39:39 -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 WAA31742; Fri, 24 Jul 1998 22:38:42 +1000 Date: Fri, 24 Jul 1998 22:38:42 +1000 From: Bruce Evans Message-Id: <199807241238.WAA31742@godzilla.zeta.org.au> To: green@zone.baldcom.net, jkh@time.cdrom.com, luoqi@watermarkgroup.com Subject: Re: vn subsystem Cc: bright@hotjobs.com, freebsd-current@FreeBSD.ORG, joelh@gnu.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> > mount /dev/vn0 /msdos (oops, should this matter anyway?) >> > mount_msdos /dev/vn0 /msdos >> >> Try it without the bad mount first. This sounds an awful lot like >> another PR which has nothing to do with vn (e.g. it would do the *same* >> thing if you tried to do this with a non-vn device). >> >> - Jordan >> >I took a look at this problem, I found there're some bugs in VMIO code >when dealing with buf at a non-page-aligned blkno, e.g. reading one page >size of data at block 1 from a block device, as Brian Feldman's core dump >shows, since the buf does not start at a page bounary, it should span >two pages, yet only one page is allocated in the current code, and >subsequent write to the 2nd page would result in a fault. I took a shot >at fixing this problem, resulted in the patch below. Would any knowledgeable >person please take a look at the patch? I've found no ill effect so far I don't think the bug can be fixed at this level. The size of a B_VMIO buffer is supposed to be a multiple of PAGE_SIZE. Smaller buffers are supposed to be malloced. msdosfs_mount() only gets as far as having misaligned blkno's because of incomplete cleanup from a previous (usually failed) mount. (IIRC, vp->v_object (where vp is the vnode for the block device) is not cleared even when all references to vp go away, and this somehow causes use of a stale block size.) I think the correct fix is to get rid of the stale v_object and improve the block size guessing (don't guess). I'm not sure what the deblocking stuff in allocbuf() is for. Is it only for NFS? FFS with its >= 4K block size never goes near any of the complications there. >Index: vfs_bio.c >=================================================================== >RCS file: /fun/cvs/src/sys/kern/vfs_bio.c,v >retrieving revision 1.167 >diff -u -r1.167 vfs_bio.c >--- vfs_bio.c 1998/07/13 07:05:55 1.167 >+++ vfs_bio.c 1998/07/24 08:14:34 >@@ -2192,15 +2192,14 @@ > vm_ooffset_t soff, eoff; > > soff = off; >- eoff = off + min(PAGE_SIZE, bp->b_bufsize); >+ eoff = min(off + PAGE_SIZE, bp->b_offset + bp->b_bufsize); This may overflow. off and bp->b_offset have type off_t, while min() truncates to u_int. Many other new and old uses of [il]min() and [il]max() may overflow for possible but not so likely combinations of type sizes. >@@ -2285,18 +2284,21 @@ > panic("vfs_clean_pages: no buffer offset"); > #endif > >- for (i = 0; i < bp->b_npages; i++, foff += PAGE_SIZE) { >+ for (i = 0; i < bp->b_npages; i++) { > vm_page_t m = bp->b_pages[i]; > vfs_page_set_valid(bp, foff, i, m); >+ foff = trunc_page(foff + PAGE_SIZE); This may overflow. foff has type vm_ooffset_t, while trunc_page() is only designed to work on core addresses, and in fact truncates to u_int. > } > } > } Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 24 06:47:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA08700 for freebsd-current-outgoing; Fri, 24 Jul 1998 06:47:02 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA08691 for ; Fri, 24 Jul 1998 06:46:56 -0700 (PDT) (envelope-from karl@Mars.mcs.net) Received: from Mars.mcs.net (karl@Mars.mcs.net [192.160.127.85]) by Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id IAA02119; Fri, 24 Jul 1998 08:46:33 -0500 (CDT) Received: (from karl@localhost) by Mars.mcs.net (8.8.7/8.8.2) id IAA06002; Fri, 24 Jul 1998 08:46:33 -0500 (CDT) Message-ID: <19980724084633.05251@mcs.net> Date: Fri, 24 Jul 1998 08:46:33 -0500 From: Karl Denninger To: jbryant@unix.tfs.net Cc: freebsd-current@FreeBSD.ORG Subject: Re: _inet_ntoa and _inet_addr in libc.a References: <199807240530.AAA11316@argus.tfs.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 In-Reply-To: <199807240530.AAA11316@argus.tfs.net>; from Jim Bryant on Fri, Jul 24, 1998 at 12:30:31AM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG You are out of sync. I saw the same thing a couple of days ago. A "make world" fixed it. -- -- Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin http://www.mcs.net/ | T1's from $600 monthly / All Lines K56Flex/DOV | NEW! Corporate ISDN Prices dropped by up to 50%! Voice: [+1 312 803-MCS1 x219]| EXCLUSIVE NEW FEATURE ON ALL PERSONAL ACCOUNTS Fax: [+1 312 803-4929] | *SPAMBLOCK* Technology now included at no cost On Fri, Jul 24, 1998 at 12:30:31AM -0500, Jim Bryant wrote: > i have been patiently waiting for the following to be fixed for some > time now [note that tcp_wrappers is messed too]: > > ---- > cd /usr/ports/security/ssh ; make > . > . > . > cc -pipe -I/usr/local/include -o ssh ssh.o sshconnect.o log-client.o readconf.o hostfile.o readpass.o tildexpand.o clientloop.o canohost.o idea.o rsa.o randoms.o md5.o buffer.o emulate.o packet.o compress.o xmalloc.o ttymodes.o newchannels.o bufaux.o authfd.o authfile.o crc32.o rsaglue.o cipher.o des.o match.o arcfour.o mpaux.o userfile.o signals.o blowfish.o deattack.o -L/usr/lib -lgmp -L/usr/lib -lz -lwrap -lcrypt -L/usr/local/lib -lutil > sshconnect.o: Undefined symbol `___inet_addr' referenced from text segment > sshconnect.o: Undefined symbol `___inet_ntoa' referenced from text segment > sshconnect.o: Undefined symbol `___inet_ntoa' referenced from text segment > canohost.o: Undefined symbol `___inet_ntoa' referenced from text segment > canohost.o: Undefined symbol `___inet_ntoa' referenced from text segment > canohost.o: Undefined symbol `___inet_ntoa' referenced from text segment > canohost.o: Undefined symbol `___inet_ntoa' referenced from text segment > canohost.o: Undefined symbol `___inet_ntoa' referenced from text segment > canohost.o: Undefined symbol `___inet_ntoa' referenced from text segment > canohost.o: Undefined symbol `___inet_ntoa' referenced from text segment > newchannels.o: Undefined symbol `___inet_addr' referenced from text segment > newchannels.o: Undefined symbol `___inet_addr' referenced from text segment > newchannels.o: Undefined symbol `___inet_addr' referenced from text segment > /usr/local/lib/libwrap.so.7.6: Undefined symbol `___inet_addr' referenced > *** Error code 1 > > Stop. > > ---- > > i have come up with two possible reasons for why this is still a > problem: > > 1). i am hopelessly out of sync with -current. > 2). -current is hopelessly out of sync with it's own libs. > > ---- > > [/usr/include/arpa/inet.h] > > /* XXX all new diversions!! argh!! */ > #define inet_addr __inet_addr > #define inet_aton __inet_aton > #define inet_lnaof __inet_lnaof > #define inet_makeaddr __inet_makeaddr > #define inet_neta __inet_neta > #define inet_netof __inet_netof > #define inet_network __inet_network > #define inet_net_ntop __inet_net_ntop > #define inet_net_pton __inet_net_pton > #define inet_ntoa __inet_ntoa > #define inet_pton __inet_pton > #define inet_ntop __inet_ntop > #define inet_nsap_addr __inet_nsap_addr > #define inet_nsap_ntoa __inet_nsap_ntoa > > ---- > [cd /usr/lib/aout ; nm libc.a] > . > . > . > 00000000 I _inet_addr > . > . > . > 00000000 I _inet_ntoa > . > . > . > inet_ntoa.o: > 00000020 T ___inet_ntoa > U ___inet_ntop > > inet_addr.o: > U __CurrentRuneLocale > U __DefaultRuneLocale > U ____runetype > 00000000 T ___inet_addr > 00000030 T ___inet_aton > > ---- > > jim > -- > All opinions expressed are mine, if you | "I will not be pushed, stamped, > think otherwise, then go jump into turbid | briefed, debriefed, indexed, or > radioactive waters and yell WAHOO !!! | numbered!" - #1, "The Prisoner" > ------------------------------------------------------------------------------ > Inet: jbryant@tfs.net AX.25: kc5vdj@wv0t.#neks.ks.usa.noam grid: EM28pw > voice: KC5VDJ - 6 & 2 Meters AM/FM/SSB, 70cm FM. http://www.tfs.net/~jbryant > ------------------------------------------------------------------------------ > HF/6M/2M: IC-706-MkII, 2M: HTX-212, 2M: HTX-202, 70cm: HTX-404, Packet: KPC-3+ > > 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 24 07:32:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA15689 for freebsd-current-outgoing; Fri, 24 Jul 1998 07:32:13 -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 HAA15681 for ; Fri, 24 Jul 1998 07:32:10 -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 KAA04422; Fri, 24 Jul 1998 10:32:29 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.ny.otec.com: bright owned process doing -bs Date: Fri, 24 Jul 1998 10:32:29 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.ny.otec.com To: Marius Bendiksen cc: freebsd-current@FreeBSD.ORG Subject: Re: -Current fails to mount / In-Reply-To: <3.0.5.32.19980723120553.0092ae50@mail.scancall.no> 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 urm, you rebuilt your kernel right? -alfred On Thu, 23 Jul 1998, Marius Bendiksen wrote: > My -current system, cvsupped 22nd July, fails to boot, telling me that it > doesn't > find 'mount_' in /sbin, nor /usr/sbin. It then proceeds to drop me into single > user, where I get the same error when attempting to remount root as > read-write. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 24 08:02:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA21155 for freebsd-current-outgoing; Fri, 24 Jul 1998 08:02:53 -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 IAA21149 for ; Fri, 24 Jul 1998 08:02:50 -0700 (PDT) (envelope-from eculp@webwizard.org.mx) Received: from webwizard.org.mx (mexcom.net.mx [207.249.162.140]) by dns.webwizard.net.mx (8.8.8/8.8.7) with ESMTP id KAA03377; Fri, 24 Jul 1998 10:00:31 -0500 (CDT) Message-ID: <35B8A18F.DD92180D@webwizard.org.mx> Date: Fri, 24 Jul 1998 10:00:31 -0500 From: Edwin Culp X-Mailer: Mozilla 4.5b1 [en] (X11; I; FreeBSD 3.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: John Polstra CC: current@FreeBSD.ORG Subject: Re: make release References: <35B7F199.A7A88FA@webwizard.org.mx> <199807240415.VAA27447@austin.polstra.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Polstra wrote: > In article <35B7F199.A7A88FA@webwizard.org.mx>, > Edwin Culp wrote: > > > Daily > > cvsup -g -L2 cvs-supfile > > cvsup -g -L2 cvs-rel > > At least weekly > > make world and new kernel > > Twice a month inmediately after the make world and kernel > > make release > > > > here are my new config files cvs-supfile and cvs-rel that > > are causing the problem although I did get through a make > > world after manually creating about 6-8 Attic directories. > > > > # cat cvs-supfile > > *default tag=. > > *default host=cvsup.FreeBSD.org > > *default base=/a > > *default prefix=/usr > > *default release=cvs > > *default delete compress use-rel-suffix > > src-all > > cvs-crypto > > doc-all > > src-secure > > ports-all > > # cat cvs-rel > > *default host=cvsup.FreeBSD.org > > *default base=/a > > *default prefix=/usr > > *default release=cvs > > *default delete compress use-rel-suffix > > src-all > > cvs-crypto > > doc-all > > src-secure > > ports-all > > You are CVSupping both the checked-out -current sources and the CVS > repository to the same place ("/usr/{src,doc,ports}"). Why? No > wonder you're having problems. > > For the "cvs-rel" supfile (getting the CVS repository), you should > have "*default prefix=/home/ncvs". And if you are getting the CVS > repository, you should probably not get the checked-out -current > sources ("cvs-supfile") at all. Just check them out of the > repository using cvs. > > I would suggest rereading the CVSup section of the FreeBSD Handbook. Will do, and with your orientation I think I see what my problems were and are with the new configuration files. Thanks ed To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 24 08:10:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA22724 for freebsd-current-outgoing; Fri, 24 Jul 1998 08:10:23 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA22716 for ; Fri, 24 Jul 1998 08:10:21 -0700 (PDT) (envelope-from fn@trinity.radio-do.de) Received: from trinity.radio-do.de (fn@trinity.Radio-do.de [193.101.164.3]) by freefall.freebsd.org (8.8.8/8.8.5) with ESMTP id IAA26356 for ; Fri, 24 Jul 1998 08:09:29 -0700 (PDT) Received: (from fn@localhost) by trinity.radio-do.de (8.8.8/8.8.5/RADIO-1.1) id RAA15163; Fri, 24 Jul 1998 17:08:55 +0200 (CEST) Message-ID: <19980724170855.A12806@radio-do.de> Date: Fri, 24 Jul 1998 17:08:55 +0200 From: Frank Nobis To: Christoph Kukulies , freebsd-current@freefall.cdrom.com Subject: Re: /usr/lib/aout References: <199807241019.MAA16826@gilberto.physik.RWTH-Aachen.DE> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.91.1i In-Reply-To: <199807241019.MAA16826@gilberto.physik.RWTH-Aachen.DE>; from Christoph Kukulies on Fri, Jul 24, 1998 at 12:19:09PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jul 24, 1998 at 12:19:09PM +0200, Christoph Kukulies wrote: > > I assume /usr/lib/aout has been invented to tell from > elm vs. aout based systems. > > When I upgrade a 1 year old -current system to a -current, > what should happen with the libs /usr/lib. Should I > remove them all? I moved them to something like /usr/lib/old/ > > And should I remove /usr/lib in the ldconfig path arguments > at any rate? That is the suggested method as in /etc/rc* > Gruß Frank -- Frank Nobis Email: PGP AVAILABLE Landgrafenstr. 130 dg3dcn http://www.radio-do.de/~fn/ 44139 Dortmund Powered by FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 24 08:15:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA23618 for freebsd-current-outgoing; Fri, 24 Jul 1998 08:15:57 -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 IAA23612 for ; Fri, 24 Jul 1998 08:15:55 -0700 (PDT) (envelope-from toasty@home.dragondata.com) Received: (from toasty@localhost) by home.dragondata.com (8.8.8/8.8.5) id KAA11803; Fri, 24 Jul 1998 10:14:52 -0500 (CDT) From: Kevin Day Message-Id: <199807241514.KAA11803@home.dragondata.com> Subject: Re: panic: page fault while in kernel mode - from gcc In-Reply-To: <199807240113.SAA23063@usr06.primenet.com> from Terry Lambert at "Jul 24, 98 01:13:57 am" To: tlambert@primenet.com (Terry Lambert) Date: Fri, 24 Jul 1998 10:14:52 -0500 (CDT) Cc: tlambert@primenet.com, dg@root.com, 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 > > > FreeBSD doesn't currently include the batch of patches that Elvind > > > saved and that John had in his home directory when it was removed, > > > does it? > > > > > > What is the behaviour with those patches added in? > > > > Right now, with my -current server, I get a 'panic: page fault while in > > kernel mode' about once a week.... Dual Processor, P/200 with 256M of ram. > > Most of the problems seem to occur when the system is starting to swap.. > > (obviously) > > You are running with John Dyson's patches, which were published in > his home directory, but not integrated into FreeBSD itself? > > Or you are running with FreeBSD-current? > > If you are running FreeBSD-current, you should try adding John's > patches. > No, sorry, I misread your question. :) (somehow I saw 'without' in there). :) I've pulled the second processor out, and recompiled without SMP, and the system hasn't crashed since, so for now, that's my solution. 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 24 08:25:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA25345 for freebsd-current-outgoing; Fri, 24 Jul 1998 08:25:58 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA25338 for ; Fri, 24 Jul 1998 08:25:57 -0700 (PDT) (envelope-from tomdean@ix.netcom.com) Received: from ix.netcom.com (sil-wa2-13.ix.netcom.com [206.214.137.45]) by freefall.freebsd.org (8.8.8/8.8.5) with ESMTP id IAA26788 for ; Fri, 24 Jul 1998 08:25:18 -0700 (PDT) Received: (from tomdean@localhost) by ix.netcom.com (8.8.8/8.8.8) id IAA00723; Fri, 24 Jul 1998 08:24:58 -0700 (PDT) (envelope-from tomdean) Date: Fri, 24 Jul 1998 08:24:58 -0700 (PDT) Message-Id: <199807241524.IAA00723@ix.netcom.com> From: Thomas Dean To: kuku@gilberto.physik.RWTH-Aachen.DE CC: freebsd-current@freefall.cdrom.com In-reply-to: <199807241019.MAA16826@gilberto.physik.RWTH-Aachen.DE> (message from Christoph Kukulies on Fri, 24 Jul 1998 12:19:09 +0200 (MEST)) Subject: Re: /usr/lib/aout Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I copied all the libs in /usr/lib to /usr/lib/aout. I changed /usr/lib to /usr/lib/aout in ldconfig statements. After I was sure my upgrade worked, I moved the libs in /usr/lib to /usr/lib/old. After I checked that everything worked, I rm'ed /usr/lib/old. Maybe I am too cautious. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 24 08:38:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA27104 for freebsd-current-outgoing; Fri, 24 Jul 1998 08:38:38 -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 IAA27025 for ; Fri, 24 Jul 1998 08:38:27 -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 IAA01444; Fri, 24 Jul 1998 08:37:35 -0700 (PDT) (envelope-from jdp) Message-Id: <199807241537.IAA01444@austin.polstra.com> To: kuku@gilberto.physik.RWTH-Aachen.DE Subject: Re: /usr/lib/aout In-Reply-To: <199807241019.MAA16826@gilberto.physik.RWTH-Aachen.DE> References: <199807241019.MAA16826@gilberto.physik.RWTH-Aachen.DE> Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Date: Fri, 24 Jul 1998 08:37:35 -0700 From: John Polstra Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199807241019.MAA16826@gilberto.physik.RWTH-Aachen.DE>, Christoph Kukulies wrote: > > I assume /usr/lib/aout has been invented to tell from > elm vs. aout based systems. > > When I upgrade a 1 year old -current system to a -current, > what should happen with the libs /usr/lib. Should I > remove them all? Yes. > And should I remove /usr/lib in the ldconfig path arguments > at any rate? I would. But it doesn't really matter, if there aren't any files in /usr/lib. :-) -- 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 Fri Jul 24 08:46:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA28930 for freebsd-current-outgoing; Fri, 24 Jul 1998 08:46:34 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles238.castles.com [208.214.165.238]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA28868 for ; Fri, 24 Jul 1998 08:46:21 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id IAA00798; Fri, 24 Jul 1998 08:45:01 -0700 (PDT) Message-Id: <199807241545.IAA00798@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Tom cc: Doug White , Lee Reese , current@FreeBSD.ORG Subject: Re: Viability of -current for Usenet News In-reply-to: Your message of "Thu, 23 Jul 1998 19:04:48 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 24 Jul 1998 08:45:01 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > On Thu, 23 Jul 1998, Doug White wrote: > > > On Thu, 23 Jul 1998, Tom wrote: > > > > > I've just seen a RedHat 5.1 system with a such a controller, hang. It > > > doesn't seem the Linux DPT driver is very stable. It seems easy to get > > > into a situation where all processes accessing the disk, hang. The > > > FreeBSD DPT driver seems quite a bit more solid than that, although > > > setting it up is more difficult. > > > > Not really anymore, apparently the 2.2.7 boot floppy now has the driver > > built on it (yay!). > > Yes, but sysinstall bugs will probably force you to do most of the > filesystem setup manually. See archives. Please try to keep your comments accurate and relevant. The sysinstall bugs have been fixed, and had nothing whatsoever to do with "filesystem setup". -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 24 08:48:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA29517 for freebsd-current-outgoing; Fri, 24 Jul 1998 08:48:20 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles238.castles.com [208.214.165.238]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA29432 for ; Fri, 24 Jul 1998 08:48:05 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id IAA00820; Fri, 24 Jul 1998 08:47:12 -0700 (PDT) Message-Id: <199807241547.IAA00820@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Doug White cc: Tom , Lee Reese , current@FreeBSD.ORG Subject: Re: Viability of -current for Usenet News In-reply-to: Your message of "Thu, 23 Jul 1998 20:20:55 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 24 Jul 1998 08:47:12 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > On Thu, 23 Jul 1998, Tom wrote: > > > > > I've just seen a RedHat 5.1 system with a such a controller, hang. It > > > > doesn't seem the Linux DPT driver is very stable. It seems easy to get > > > > into a situation where all processes accessing the disk, hang. The > > > > FreeBSD DPT driver seems quite a bit more solid than that, although > > > > setting it up is more difficult. > > > > > > Not really anymore, apparently the 2.2.7 boot floppy now has the driver > > > built on it (yay!). > > > > Yes, but sysinstall bugs will probably force you to do most of the > > filesystem setup manually. See archives. > > &#@^! ... In what list? It hasn't hit the archives and I haven't seen > anything yet. Mostly private whining at me. It's been fixed; ignore it. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 24 08:52:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA00947 for freebsd-current-outgoing; Fri, 24 Jul 1998 08:52:40 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA00883 for ; Fri, 24 Jul 1998 08:52:26 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by freefall.freebsd.org (8.8.8/8.8.5) with ESMTP id IAA27475 for ; Fri, 24 Jul 1998 08:51:39 -0700 (PDT) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.5/8.8.8) with SMTP id IAA21562; Fri, 24 Jul 1998 08:51:43 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Fri, 24 Jul 1998 08:51:42 -0700 (PDT) From: Doug White To: Christoph Kukulies cc: freebsd-current@freefall.cdrom.com Subject: Re: /usr/lib/aout In-Reply-To: <199807241019.MAA16826@gilberto.physik.RWTH-Aachen.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 Fri, 24 Jul 1998, Christoph Kukulies wrote: > > I assume /usr/lib/aout has been invented to tell from > elm vs. aout based systems. > > When I upgrade a 1 year old -current system to a -current, > what should happen with the libs /usr/lib. Should I > remove them all? /usr/lib/lib* can disappear once you've rebooted with new /etc/rc* and libs in aout. ldconfig will DTRT (and stop complaining about /usr/lib). For security I moved them into /usr/lib/foo temporarily. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 24 08:57:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA02140 for freebsd-current-outgoing; Fri, 24 Jul 1998 08:57:51 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles238.castles.com [208.214.165.238]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA02056 for ; Fri, 24 Jul 1998 08:57:31 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id HAA00254; Fri, 24 Jul 1998 07:59:22 -0700 (PDT) Message-Id: <199807241459.HAA00254@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Lee Reese cc: current@FreeBSD.ORG Subject: Re: Viability of -current for Usenet News In-reply-to: Your message of "Thu, 23 Jul 1998 09:32:16 EDT." <35B73B60.41C67EA6@gwinnett.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 24 Jul 1998 07:59:22 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > We have been having quite a bit of trouble running a Usenet News server > over the last 8 months. The machine in question is a dual Pentium Pro > with 256MB and a DPT 3334UW Raid Controller. > > What I would like to do is convince the Sysadmin that FreeBSD might be a > better platform than Slackware Linux for administering the server. The > machine would be running INN 2.0. We have seen severe buffering > problems with the RAID controller and Linux in its present state. Could > anyone give any reasons why FreeBSD may be a superior OS for such an > application so I can convince the Sysadmin to switch? Thanks. You might want to talk to Matt Dillon from Best Internet, who is I understand evalutating a similar system at the moment. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 24 09:00:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA02919 for freebsd-current-outgoing; Fri, 24 Jul 1998 09:00:52 -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 JAA02810 for ; Fri, 24 Jul 1998 09:00:29 -0700 (PDT) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id LAA21864; Fri, 24 Jul 1998 11:58:12 -0400 (EDT) (envelope-from luoqi) Date: Fri, 24 Jul 1998 11:58:12 -0400 (EDT) From: Luoqi Chen Message-Id: <199807241558.LAA21864@lor.watermarkgroup.com> To: bde@zeta.org.au, green@zone.baldcom.net, jkh@time.cdrom.com, luoqi@watermarkgroup.com Subject: Re: vn subsystem Cc: bright@hotjobs.com, freebsd-current@FreeBSD.ORG, joelh@gnu.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >I took a look at this problem, I found there're some bugs in VMIO code > >when dealing with buf at a non-page-aligned blkno, e.g. reading one page > >size of data at block 1 from a block device, as Brian Feldman's core dump > >shows, since the buf does not start at a page bounary, it should span > >two pages, yet only one page is allocated in the current code, and > >subsequent write to the 2nd page would result in a fault. I took a shot > >at fixing this problem, resulted in the patch below. Would any knowledgeable > >person please take a look at the patch? I've found no ill effect so far > > I don't think the bug can be fixed at this level. The size of a B_VMIO > buffer is supposed to be a multiple of PAGE_SIZE. Smaller buffers are > supposed to be malloced. msdosfs_mount() only gets as far as having > misaligned blkno's because of incomplete cleanup from a previous (usually > failed) mount. (IIRC, vp->v_object (where vp is the vnode for the block > device) is not cleared even when all references to vp go away, and this > somehow causes use of a stale block size.) > >From my understanding of the code, multiple of DEV_BSIZE but not PAGE_SIZE is supported through the valid and dirty bitmap in vm_page structure. That's why VMIO for a block device is possible. BTW, VMIO bufs cannot be malloced, there is a check in allocbuf() that panic's when it sees one. The msdosfs_mount() was actually a victim of a failed FFS mount. FFS mount enables VMIO on the block device, and the effect is permanent even when the mount fails. MSDOSFS needs non-page-aligned block bufs, for one, FAT starts at block 1, and in fact it was reading the FAT blocks that killed msdosfs_mount(). Normally MSDOSFS operates on a non-VMIO block device. > I think the correct fix is to get rid of the stale v_object and improve > the block size guessing (don't guess). > > I'm not sure what the deblocking stuff in allocbuf() is for. Is it only > for NFS? FFS with its >= 4K block size never goes near any of the > complications there. I don't know what the initial intention for the deblocking stuff was. It may well be designed just for NFS, but it makes possible the handling of non-page-aligned bufs, so why don't take advantage of that:) And for NFS' sake, we want to have these bugs fixed. The portion of the code that handles aligning buffer cache and its vm pages are well localized in a couple of functions in vfs_bio.c, I have good confidence that I understand the code well. I hope people could try out the patch (of course, I will correct the overflow problems, I'm completely clueless about all these different sized integers:). -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 24 09:02:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA03289 for freebsd-current-outgoing; Fri, 24 Jul 1998 09:02:18 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles238.castles.com [208.214.165.238]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA03178 for ; Fri, 24 Jul 1998 09:01:56 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id JAA00922; Fri, 24 Jul 1998 09:00:54 -0700 (PDT) Message-Id: <199807241600.JAA00922@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Tom cc: Doug White , Lee Reese , current@FreeBSD.ORG Subject: Re: Viability of -current for Usenet News In-reply-to: Your message of "Thu, 23 Jul 1998 20:47:38 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 24 Jul 1998 09:00:54 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Oops; I appear to have seriously confused you with someone else, Tom. We're aware of the problem you've described - none of the other developers that have DPT controllers have offered any suggestions, and it's not a symptom that we've seen under any other circumstances, so we can't fix that one. Again; my apologies for the mixup. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 24 09:08:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA04528 for freebsd-current-outgoing; Fri, 24 Jul 1998 09:08:43 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA04417 for ; Fri, 24 Jul 1998 09:08:06 -0700 (PDT) (envelope-from kuku@gilberto.physik.RWTH-Aachen.DE) Received: from gilberto.physik.RWTH-Aachen.DE (gilberto.physik.rwth-aachen.de [137.226.30.2]) by freefall.freebsd.org (8.8.8/8.8.5) with ESMTP id JAA28003 for ; Fri, 24 Jul 1998 09:06:51 -0700 (PDT) Received: (from kuku@localhost) by gilberto.physik.RWTH-Aachen.DE (8.8.8/8.8.7) id SAA18247; Fri, 24 Jul 1998 18:07:14 +0200 (MEST) (envelope-from kuku) Message-ID: <19980724180714.A18189@gil.physik.rwth-aachen.de> Date: Fri, 24 Jul 1998 18:07:14 +0200 From: Christoph Kukulies To: Doug White , Christoph Kukulies Cc: freebsd-current@freefall.cdrom.com Subject: Re: /usr/lib/aout References: <199807241019.MAA16826@gilberto.physik.RWTH-Aachen.DE> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91 In-Reply-To: ; from Doug White on Fri, Jul 24, 1998 at 08:51:42AM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jul 24, 1998 at 08:51:42AM -0700, Doug White wrote: > > On Fri, 24 Jul 1998, Christoph Kukulies wrote: > > > > > I assume /usr/lib/aout has been invented to tell from > > elm vs. aout based systems. > > > > When I upgrade a 1 year old -current system to a -current, > > what should happen with the libs /usr/lib. Should I > > remove them all? > > /usr/lib/lib* can disappear once you've rebooted with new /etc/rc* and > libs in aout. ldconfig will DTRT (and stop complaining about /usr/lib). > For security I moved them into /usr/lib/foo temporarily. > The man page of ldconfig is still talking about a builtin /usr/lib. This should disappear then, right? I had a problem this morning after moving from 3.0-current of July 1997 to 3.0-current of yesterday. Had to rebuild (at least) elm. And when the user started elm he said he couldn't move up down to the messages with the cursor keys. I was blaming this to a possible mess I may have had with /usr/lib still being in the ldconfig path. Right now I'm gonna reboot that machine with all stuff in /usr/lib removed and the right /etc/rc setting as what LDC_ is concerned. > Doug White | University of Oregon > Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant > http://gladstone.uoregon.edu/~dwhite | Computer Science Major -- Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 24 09:13:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA05602 for freebsd-current-outgoing; Fri, 24 Jul 1998 09:13:25 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from elephants.dyn.ml.org (jake@mki2-pl-ri5.kos.net [206.186.40.144]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA05540 for ; Fri, 24 Jul 1998 09:12:51 -0700 (PDT) (envelope-from jake@elephants.dyn.ml.org) Received: from elephants.dyn.ml.org (jake@localhost [127.0.0.1]) by elephants.dyn.ml.org (8.8.8/8.8.8) with ESMTP id IAA00294 for ; Fri, 24 Jul 1998 08:44:06 -0400 (EDT) (envelope-from jake@elephants.dyn.ml.org) Message-Id: <199807241244.IAA00294@elephants.dyn.ml.org> X-Mailer: exmh version 2.0.2 2/24/98 To: current@FreeBSD.ORG Subject: current.freebsd.org & XFree86 3323 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 24 Jul 1998 08:44:05 -0400 From: Jake Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG could someome update the XFree86 files on current.freebsd.org ( make.ican.net ) to the latest version that is in 2.2.7-release? its in the /pub/current/XF86332 directory, the one there is from January. Has the bug in the boot floppies that caused X to be left out of ftp installs been fixed? I know this was fixed in -release, but what about -current? I'll be installing the latest SNAP as soon as my new drive gets here and don't want to have to screw around with X again. also, as an aside, I think the cvsup on that machine should be updated too, seems like its still running version 15.4, :)~ cvsup -g -L 2 current-supfile Parsing supfile "current-supfile" Looking up address of cvsup.ca.FreeBSD.org Connecting to cvsup.ca.FreeBSD.org Connected to cvsup.ca.FreeBSD.org Server software version: REL_15_2 Falling back to protocol version 15.4 Negotiating file attribute support Exchanging collection information Establishing active-mode data connection Running Updating collection src-base/cvs Thanks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 24 09:14:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA05757 for freebsd-current-outgoing; Fri, 24 Jul 1998 09:14:06 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA05693 for ; Fri, 24 Jul 1998 09:13:45 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by freefall.freebsd.org (8.8.8/8.8.5) with ESMTP id JAA28147 for ; Fri, 24 Jul 1998 09:13:01 -0700 (PDT) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.5/8.8.8) with SMTP id JAA24558; Fri, 24 Jul 1998 09:13:06 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Fri, 24 Jul 1998 09:13:06 -0700 (PDT) From: Doug White To: Christoph Kukulies cc: freebsd-current@freefall.cdrom.com Subject: Re: /usr/lib/aout In-Reply-To: <19980724180714.A18189@gil.physik.rwth-aachen.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 Fri, 24 Jul 1998, Christoph Kukulies wrote: > On Fri, Jul 24, 1998 at 08:51:42AM -0700, Doug White wrote: > > > > On Fri, 24 Jul 1998, Christoph Kukulies wrote: > > > > > > > > I assume /usr/lib/aout has been invented to tell from > > > elm vs. aout based systems. > > > > > > When I upgrade a 1 year old -current system to a -current, > > > what should happen with the libs /usr/lib. Should I > > > remove them all? > > > > /usr/lib/lib* can disappear once you've rebooted with new /etc/rc* and > > libs in aout. ldconfig will DTRT (and stop complaining about /usr/lib). > > For security I moved them into /usr/lib/foo temporarily. > > > > The man page of ldconfig is still talking about a builtin /usr/lib. > This should disappear then, right? Yes. > I had a problem this morning after moving from 3.0-current of July 1997 > to 3.0-current of yesterday. Had to rebuild (at least) elm. > And when the user started elm he said he couldn't move > up down to the messages with the cursor keys. Could be a curses thing. Ouch, a year migration of CURRENT? Not fun. > I was blaming this to a possible mess I may have had with /usr/lib still > being in the ldconfig path. Right now I'm gonna reboot that machine > with all stuff in /usr/lib removed and the right /etc/rc setting > as what LDC_ is concerned. Copy in the new /etc/rc* from /usr/src/etc/rc* and /usr/src/etc/i386/rc.i386 and that will get you pointed right. (don't spam rc.conf!) Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 24 09:27:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA08381 for freebsd-current-outgoing; Fri, 24 Jul 1998 09:27:01 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA08352 for ; Fri, 24 Jul 1998 09:26:47 -0700 (PDT) (envelope-from kuku@gilberto.physik.RWTH-Aachen.DE) Received: from gilberto.physik.RWTH-Aachen.DE (gilberto.physik.rwth-aachen.de [137.226.30.2]) by freefall.freebsd.org (8.8.8/8.8.5) with ESMTP id JAA28534 for ; Fri, 24 Jul 1998 09:24:34 -0700 (PDT) Received: (from kuku@localhost) by gilberto.physik.RWTH-Aachen.DE (8.8.8/8.8.7) id SAA18333; Fri, 24 Jul 1998 18:23:23 +0200 (MEST) (envelope-from kuku) Message-ID: <19980724182322.A18313@gil.physik.rwth-aachen.de> Date: Fri, 24 Jul 1998 18:23:22 +0200 From: Christoph Kukulies To: Doug White , Christoph Kukulies Cc: freebsd-current@freefall.cdrom.com Subject: Re: /usr/lib/aout References: <19980724180714.A18189@gil.physik.rwth-aachen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91 In-Reply-To: ; from Doug White on Fri, Jul 24, 1998 at 09:13:06AM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jul 24, 1998 at 09:13:06AM -0700, Doug White wrote: > > On Fri, 24 Jul 1998, Christoph Kukulies wrote: > > > On Fri, Jul 24, 1998 at 08:51:42AM -0700, Doug White wrote: > > > > > > On Fri, 24 Jul 1998, Christoph Kukulies wrote: > > > > > > > > > > > I assume /usr/lib/aout has been invented to tell from > > > > elm vs. aout based systems. > > > > > > > > When I upgrade a 1 year old -current system to a -current, > > > > what should happen with the libs /usr/lib. Should I > > > > remove them all? > > > > > > /usr/lib/lib* can disappear once you've rebooted with new /etc/rc* and > > > libs in aout. ldconfig will DTRT (and stop complaining about /usr/lib). > > > For security I moved them into /usr/lib/foo temporarily. > > > > > > > The man page of ldconfig is still talking about a builtin /usr/lib. > > This should disappear then, right? > > Yes. > > > I had a problem this morning after moving from 3.0-current of July 1997 > > to 3.0-current of yesterday. Had to rebuild (at least) elm. > > And when the user started elm he said he couldn't move > > up down to the messages with the cursor keys. > > Could be a curses thing. > Yes, thought so, too. > Ouch, a year migration of CURRENT? Not fun. > Well, it went smoother than I initially feared. It was an iterative mix of make bootstrap, make hierarchy, make install, build certain key programs like config, install , ranlib, size, strip etc. I must say that I had built the world on a -current system first and then mounted /usr/src, /usr/obj to do just the install. > > I was blaming this to a possible mess I may have had with /usr/lib still > > being in the ldconfig path. Right now I'm gonna reboot that machine > > with all stuff in /usr/lib removed and the right /etc/rc setting > > as what LDC_ is concerned. > > Copy in the new /etc/rc* from /usr/src/etc/rc* and > /usr/src/etc/i386/rc.i386 and that will get you pointed right. (don't > spam rc.conf!) > > Doug White | University of Oregon > Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant > http://gladstone.uoregon.edu/~dwhite | Computer Science Major -- --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 24 09:36:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA10132 for freebsd-current-outgoing; Fri, 24 Jul 1998 09:36:50 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA10085 for ; Fri, 24 Jul 1998 09:36:30 -0700 (PDT) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id LAA05611; Fri, 24 Jul 1998 11:35:41 -0500 (EST) (envelope-from toor) Message-Id: <199807241635.LAA05611@dyson.iquest.net> Subject: Re: panic: page fault while in kernel mode - from gcc In-Reply-To: <199807240219.TAA23545@implode.root.com> from David Greenman at "Jul 23, 98 07:19:17 pm" To: dg@root.com Date: Fri, 24 Jul 1998 11:35:41 -0500 (EST) Cc: tlambert@primenet.com, toasty@home.dragondata.com, current@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@iquest.net 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 David Greenman said: > >> Right now, with my -current server, I get a 'panic: page fault while in > >> kernel mode' about once a week.... Dual Processor, P/200 with 256M of ram. > >> Most of the problems seem to occur when the system is starting to swap.. > >> (obviously) > > > >You are running with John Dyson's patches, which were published in > >his home directory, but not integrated into FreeBSD itself? > > > >Or you are running with FreeBSD-current? > > > >If you are running FreeBSD-current, you should try adding John's > >patches. > > All of the reports that I've seen to date (about five) have indicated that > the patches that used to be in John's directory caused major instabilities > which is the reason why they haven't been committed. > As I said earlier, those "fixes" are a little rough, and the SMP "improvements", need to be distilled from the patches for review. Most of the SMP changes were to start improving the granularity of SMP, not to actually fix bugs. (However, some bugfixing might be in the code -- I don't even remember what is in the patch kits. One note: the -current patchkit is really bad, and the "b" version is more workable. Right now, the code that I have been running for the last few months is rock-solid stable, with NO crashes from anything except the ancient softupdates that I am running, and a heat problem from a broken air conditioner.) I don't have a patchkit for the code that I am running though, but probably has some fixes relative to the "current" version that is sitting on Eivind's site.) The bug in traceback is either a reference count problem left over from previous usage of the code, or a problem with pmap_copy. (I suspect pmap_copy.) Take a look at the patches that I had provided earlier, and see if there are any pmap_copy bugs fixed. If there aren't, the bug is likely fairly easy to fix. -- John | Never try to teach a pig to sing, dyson@iquest.net | it makes one look stupid jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 24 10:02:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA15274 for freebsd-current-outgoing; Fri, 24 Jul 1998 10:02:16 -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 KAA15265 for ; Fri, 24 Jul 1998 10:02:13 -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 KAA18756; Fri, 24 Jul 1998 10:01:03 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: Jake cc: current@FreeBSD.ORG Subject: Re: current.freebsd.org & XFree86 3323 In-reply-to: Your message of "Fri, 24 Jul 1998 08:44:05 EDT." <199807241244.IAA00294@elephants.dyn.ml.org> Date: Fri, 24 Jul 1998 10:01:02 -0700 Message-ID: <18751.901299662@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > could someome update the XFree86 files on current.freebsd.org ( make.ican.net ) > to the latest version that is in 2.2.7-release? That wouldn't be a very good idea since current.freebsd.org produces only 3.0 releases now. :) As soon as we have updated binaries for 3.0 on ftp.cdrom.com, I'll sync up. - 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 24 10:31:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA20791 for freebsd-current-outgoing; Fri, 24 Jul 1998 10:31:47 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from kong.dorms.spbu.ru (root@kong.dorms.spbu.ru [195.19.252.147]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA20689 for ; Fri, 24 Jul 1998 10:31:10 -0700 (PDT) (envelope-from kong@kong.dorms.spbu.ru) Received: from localhost (kong@localhost) by kong.dorms.spbu.ru (8.8.8/kong/0.01) with SMTP id TAA00315 for ; Fri, 24 Jul 1998 19:36:14 +0400 (MSD) (envelope-from kong@kong.dorms.spbu.ru) Date: Fri, 24 Jul 1998 19:36:13 +0400 (MSD) From: Hostas Red To: current@FreeBSD.ORG Subject: Strange idle times 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! About one month or so i have a strange idle times on my -current (really current - 1 hour or so :) - whenever i use 'w' or 'finger' idle time of users equivalent to uptime (maybe 1 minute less). ;-( 'apm' disabled in kernel, nothing changed ever since. It just happend one time and lasts till now. Anybody have such a problem? Adios, /KONG To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 24 10:42:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA23500 for freebsd-current-outgoing; Fri, 24 Jul 1998 10:42:53 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zeus.ip.lt (zeus.ip.lt [194.176.42.34]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA23436 for ; Fri, 24 Jul 1998 10:42:26 -0700 (PDT) (envelope-from rch@ip.lt) Received: from ip.lt (194.176.42.2) by zeus.ip.lt (EMWAC SMTPRS 0.81) with SMTP id ; Fri, 24 Jul 1998 19:41:55 +0200 Message-ID: <35B8C76A.DAA5775B@ip.lt> Date: Fri, 24 Jul 1998 19:42:02 +0200 From: Ricardas Cepas X-Mailer: Mozilla 4.05 [en] (X11; U; FreeBSD 3.0-980520-SNAP i386) MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: Mozilla and lesstif Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, Does somebody succeeded to compile Mozilla with Lesstif? I found in Mozilla docs that lesstif can be used "with limited succsess". For my it ends by: .... gmake[4]: Leaving directory `/usr/ports/www/mozilla/work/19980429/mozilla/nsprpub/lib/msgc/include' cd src; gmake libs ../../dist/FreeBSD3.0_OPT.OBJ/bin/libXfeWidgets.so.1.0: Undefined symbol `_XmListGetSelectedPos' referenced ../../dist/FreeBSD3.0_OPT.OBJ/bin/libXfeWidgets.so.1.0: More undefined `_XmGetColors' refs follow ../../dist/FreeBSD3.0_OPT.OBJ/bin/libXfeWidgets.so.1.0: Undefined symbol `_XmAddProtocolCallback' referenced ../../dist/FreeBSD3.0_OPT.OBJ/bin/libXfeWidgets.so.1.0: Undefined symbol `_XmGetPixmapByDepth' referenced ../../dist/FreeBSD3.0_OPT.OBJ/bin/libXfeWidgets.so.1.0: More undefined `_XmListSelectPos' refs follow ../../dist/FreeBSD3.0_OPT.OBJ/bin/libXfeWidgets.so.1.0: Undefined symbol `_XmStringExtent' referenced ../../dist/FreeBSD3.0_OPT.OBJ/bin/libXfeWidgets.so.1.0: Undefined symbol `_XmStringGetLtoR' referenced ../../dist/FreeBSD3.0_OPT.OBJ/bin/libXfeWidgets.so.1.0: Undefined symbol `_XmGetXmDisplay' referenced ../../dist/FreeBSD3.0_OPT.OBJ/bin/libXfeWidgets.so.1.0: Undefined symbol `_XmTextFieldSetString' referenced gmake[2]: *** [FreeBSD3.0_OPT.OBJ/moz-export] Error 1 gmake[2]: Leaving directory `/usr/ports/www/mozilla/work/19980429/mozilla/cmd/xfe' gmake[1]: *** [install] Error 2 gmake[1]: Leaving directory `/usr/ports/www/mozilla/work/19980429/mozilla/cmd' gmake: *** [install] Error 2 *** Error code 2 Thank you, -- Ricardas Cepas ~~ ~ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 24 10:54:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA26758 for freebsd-current-outgoing; Fri, 24 Jul 1998 10:54:30 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA26676 for ; Fri, 24 Jul 1998 10:54:18 -0700 (PDT) (envelope-from karl@Mars.mcs.net) Received: from Mars.mcs.net (karl@Mars.mcs.net [192.160.127.85]) by Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id MAA18121 for ; Fri, 24 Jul 1998 12:53:54 -0500 (CDT) Received: (from karl@localhost) by Mars.mcs.net (8.8.7/8.8.2) id MAA10189; Fri, 24 Jul 1998 12:53:54 -0500 (CDT) Message-ID: <19980724125354.63118@mcs.net> Date: Fri, 24 Jul 1998 12:53:54 -0500 From: Karl Denninger To: current@FreeBSD.ORG Subject: 3.0 stability - much improved Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am pleased to report that a number of fairly serious problems which we have had to work around in 3.0 for the last couple of months seem to be gone in the last week or two. These included some libc difficulties as well as various kernel issues. Kudos to those making the changes involved; it appears that code in the 7/22/98 area is stable. -- -- Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin http://www.mcs.net/ | T1's from $600 monthly / All Lines K56Flex/DOV | NEW! Corporate ISDN Prices dropped by up to 50%! Voice: [+1 312 803-MCS1 x219]| EXCLUSIVE NEW FEATURE ON ALL PERSONAL ACCOUNTS Fax: [+1 312 803-4929] | *SPAMBLOCK* Technology now included at no cost To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 24 10:56:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA27260 for freebsd-current-outgoing; Fri, 24 Jul 1998 10:56:48 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from vader.cs.berkeley.edu (vader.CS.Berkeley.EDU [128.32.38.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA27249 for ; Fri, 24 Jul 1998 10:56:40 -0700 (PDT) (envelope-from asami@vader.cs.berkeley.edu) Received: from silvia.HIP.Berkeley.EDU (sji-ca7-188.ix.netcom.com [209.109.235.188]) by vader.cs.berkeley.edu (8.8.7/8.7.3) with ESMTP id KAA13075; Fri, 24 Jul 1998 10:56:11 -0700 (PDT) Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.8/8.6.9) id KAA15269; Fri, 24 Jul 1998 10:56:05 -0700 (PDT) Date: Fri, 24 Jul 1998 10:56:05 -0700 (PDT) Message-Id: <199807241756.KAA15269@silvia.HIP.Berkeley.EDU> To: bde@zeta.org.au CC: bde@zeta.org.au, dwhite@resnet.uoregon.edu, current@FreeBSD.ORG, imp@village.org, jb@cimlogic.com.au In-reply-to: <199807241028.UAA25308@godzilla.zeta.org.au> (message from Bruce Evans on Fri, 24 Jul 1998 20:28:09 +1000) Subject: Re: Does building current on 2.2.x still work? From: asami@FreeBSD.ORG (Satoshi Asami) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Don't know. It was reported to work from 2.1.5 when building from old * versions was first supported in rev.1.133 (1997/08/05). That was me. In fact, one of the first principles when I started the buildworld/installword split work was to make -current and -stable "world" work on as old FreeBSD versions as possible. Unfortunately, I don't have 2.1.5 installations anymore. If someone can test it, it will be greatly appreciated. Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 24 14:42:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA05966 for freebsd-current-outgoing; Fri, 24 Jul 1998 14:42:24 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.gwinnett.com (mail.gwinnett.com [204.89.227.35]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA05942 for ; Fri, 24 Jul 1998 14:42:14 -0700 (PDT) (envelope-from lee@gwinnett.com) Received: from venus.gwinnett.com ([204.89.227.91]) by mail.gwinnett.com (8.8.7/8.8.5) with SMTP id RAA17035 for ; Fri, 24 Jul 1998 17:41:39 -0400 Message-ID: <35B8FF86.41C67EA6@gwinnett.com> Date: Fri, 24 Jul 1998 17:41:26 -0400 From: Lee Reese X-Mailer: Mozilla 3.04 (X11; I; FreeBSD 3.0CAM-19980712-0 i386) MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: Re: Viability of -current for Usenet News References: <199807231626.SAA23494@bowtie.nl> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Marc van Kempen wrote: > > > We have been having quite a bit of trouble running a Usenet News server > > over the last 8 months. The machine in question is a dual Pentium Pro > > with 256MB and a DPT 3334UW Raid Controller. > > > > What I would like to do is convince the Sysadmin that FreeBSD might be a > > better platform than Slackware Linux for administering the server. The > > machine would be running INN 2.0. We have seen severe buffering > > problems with the RAID controller and Linux in its present state. Could > > anyone give any reasons why FreeBSD may be a superior OS for such an > > application so I can convince the Sysadmin to switch? Thanks. > > > > I did it! Thanks, guys. Now for some stupid questions... I already have the machine set up with two arrays: 2 - 2GB Drives in RAID 1 and Six 4.5GB Drives in RAID 5. I have a CAM boot floppy for the 7-12-98 Snapshot, which cannot access the array to install. I know there used to be a boot floppy for the DPT controller, but I do not see it in the /floppies directory or a link to one when searching the mailing list archives. Is there a place I can download a floppy or has instructions to make it myself? Thanks. Lee To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 24 15:08:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA09508 for freebsd-current-outgoing; Fri, 24 Jul 1998 15:08:58 -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 PAA09497 for ; Fri, 24 Jul 1998 15:08:51 -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 0yzq0a-00052q-00; Fri, 24 Jul 1998 15:08:12 -0700 Date: Fri, 24 Jul 1998 15:08:10 -0700 (PDT) From: Tom X-Sender: tom@shell.uniserve.ca To: Lee Reese cc: current@FreeBSD.ORG Subject: Re: Viability of -current for Usenet News In-Reply-To: <35B8FF86.41C67EA6@gwinnett.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 Fri, 24 Jul 1998, Lee Reese wrote: > Marc van Kempen wrote: > > > > > We have been having quite a bit of trouble running a Usenet News server > > > over the last 8 months. The machine in question is a dual Pentium Pro > > > with 256MB and a DPT 3334UW Raid Controller. > > > > > > What I would like to do is convince the Sysadmin that FreeBSD might be a > > > better platform than Slackware Linux for administering the server. The > > > machine would be running INN 2.0. We have seen severe buffering > > > problems with the RAID controller and Linux in its present state. Could > > > anyone give any reasons why FreeBSD may be a superior OS for such an > > > application so I can convince the Sysadmin to switch? Thanks. > > > > > > > I did it! Thanks, guys. > > Now for some stupid questions... > > I already have the machine set up with two arrays: 2 - 2GB Drives in > RAID 1 and Six 4.5GB Drives in RAID 5. I have a CAM boot floppy for > the 7-12-98 Snapshot, which cannot access the array to install. I know There is no CAMified DPT driver, so that floppy will not work. > there used to be a boot floppy for the DPT controller, but I do not see > it in the /floppies directory or a link to one when searching the > mailing list archives. Is there a place I can download a floppy or has > instructions to make it myself? Thanks. Yes, the standard boot.flp has it in it. BTW, you are apparently attempting to run -current? Be aware of all implications of using -current on a production system. > Lee 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 24 15:40:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA13948 for freebsd-current-outgoing; Fri, 24 Jul 1998 15:40:15 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA13874 for ; Fri, 24 Jul 1998 15:39:57 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id PAA00608; Fri, 24 Jul 1998 15:38:48 -0700 (PDT) Message-Id: <199807242238.PAA00608@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Lee Reese cc: current@FreeBSD.ORG Subject: Re: Viability of -current for Usenet News In-reply-to: Your message of "Fri, 24 Jul 1998 17:41:26 EDT." <35B8FF86.41C67EA6@gwinnett.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 24 Jul 1998 15:38:48 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I already have the machine set up with two arrays: 2 - 2GB Drives in > RAID 1 and Six 4.5GB Drives in RAID 5. I have a CAM boot floppy for > the 7-12-98 Snapshot, which cannot access the array to install. I know > there used to be a boot floppy for the DPT controller, but I do not see > it in the /floppies directory or a link to one when searching the > mailing list archives. Is there a place I can download a floppy or has > instructions to make it myself? Thanks. The 2.2.7-RELEASE boot floppy has DPT support enabled by default. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 24 15:41:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA14207 for freebsd-current-outgoing; Fri, 24 Jul 1998 15:41:39 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from thing.dyn.ml.org (dyn-max10-191.chicago.il.ameritech.net [206.141.212.191] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA14139 for ; Fri, 24 Jul 1998 15:41:13 -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 SAA12976 for ; Fri, 24 Jul 1998 18:40:34 -0400 (EDT) (envelope-from mcdougall@ameritech.net) Message-ID: <35B90D60.3FE563F0@ameritech.net> Date: Fri, 24 Jul 1998 18:40:32 -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: strange src tree corruption Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This seems to happen now a few times each time I attempt a buildworld, the compile bombs out with something like this: /asynch/src/gnu/usr.bin/perl/perl/perl.c:1478: unterminated string or character constant/asynch/src/gnu/usr.bin/perl/perl/perl.c:1239: possible real start of unterminated constant /asynch/src/gnu/usr.bin/perl/perl/perl.c:1236: unterminated `#if' conditional /asynch/src/gnu/usr.bin/perl/perl/perl.c: In function `do_eval': /asynch/src/gnu/usr.bin/perl/perl/perl.c:1236: parse error at end of input/asynch/src/gnu/usr.bin/perl/perl/perl.c:118: warning: `moreswitches' declared `static' but never defined *** Error code 1 this is right after a cvsup. if I rm the file, and cvsup, its magically fixed. The filesystem this partition is on has softupdates, but thats the only thing special I can think about it. I recently copied my src tree off it and newfs'ed but the problem remains. Is there something that may be stopping cvsup from properly checking or updating corrupted files? Maybe I should just nuke the src tree and cvsup the whole tree again (not on the top of my list of things I'd like to do) Any input on this mystery would be appreciated :) Thanks in advance. The diff from the file before rm, and the resulting file after cvsup is this: --- perl.c Fri Jul 24 17:10:31 1998 +++ goodperl.c Fri Jul 24 17:14:01 1998 @@ -1236,7 +1236,50 @@ #ifdef DEBUGGING if (debug & 4) { char *tmps = loop_stack[loop_ptr].loop_label; - deb("(Popping label SPAT * VOLATILE oldlspat = lastspat; + deb("(Popping label #%d %s)\n",loop_ptr, + tmps ? tmps : "" ); + } +#endif + loop_ptr--; + tmps_base = oldtmps_base; + curspat = oldspat; + lastspat = oldlspat; + if (savestack->ary_fill > oldsave) /* let them use local() */ + restorelist(oldsave); + + if (optype != O_EVAL) { + if (retval) { + if (optype == O_REQUIRE) + fatal("%s", str_get(stab_val(stabent("@",TRUE)))); + } + else { + curcmd = oldcurcmd; + if (gimme == G_SCALAR ? str_true(st[sp]) : sp > arglast[0]) { + (void)hstore(stab_hash(incstab), specfilename, + strlen(specfilename), str_smake(stab_val(curcmd->c_filestab)), + 0 ); + } + else if (optype == O_REQUIRE) + fatal("%s did not return a true value", specfilename); + } + } + curcmd = oldcurcmd; + return sp; +} + +int +do_try(cmd,gimme,arglast) +CMD *cmd; +int gimme; +int *arglast; +{ + STR **st = stack->ary_array; + + CMD * VOLATILE oldcurcmd = curcmd; + VOLATILE int oldtmps_base = tmps_base; + VOLATILE int oldsave = savestack->ary_fill; + SPAT * VOLATILE oldspat = curspat; + SPAT * VOLATILE oldlspat = lastspat; VOLATILE int sp = arglast[0]; tmps_base = tmps_max; @@ -1456,25 +1499,3 @@ #endif } -^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^ -static const char *filesave[] = { -" 14 14 3 1", -". c #040404", -"# c #808304", -"a c #bfc2bf", -"..............", -".#.aaaaaaaa.a.", -".#.aaaaaaaa...", -".#.aaaaaaaa.#.", -".#.aaaaaaaa.#.", -".#.aaaaaaaa.#.", -".#.aaaaaaaa.#.", -".##........##.", -".############.", -".##.........#.", -".##......aa.#.", -".##......aa.#.", -".##......aa.#.", -"a............." -}; -^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^ \ No newline at end of file To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 24 16:03:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA18795 for freebsd-current-outgoing; Fri, 24 Jul 1998 16:03:05 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA18703 for ; Fri, 24 Jul 1998 16:02:28 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.5/8.8.8) with SMTP id QAA06154; Fri, 24 Jul 1998 16:01:51 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Fri, 24 Jul 1998 16:01:51 -0700 (PDT) From: Doug White To: Hostas Red cc: current@FreeBSD.ORG Subject: Re: Strange idle times 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, 24 Jul 1998, Hostas Red wrote: > Hi! > > About one month or so i have a strange idle times on my -current (really > current - 1 hour or so :) - whenever i use 'w' or 'finger' idle time of > users equivalent to uptime (maybe 1 minute less). ;-( > > 'apm' disabled in kernel, nothing changed ever since. It just happend one > time and lasts till now. > > Anybody have such a problem? Corrupted utmp/wtmp perhaps? Something trying to use the old format? Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 24 16:16:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA21179 for freebsd-current-outgoing; Fri, 24 Jul 1998 16:16:05 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from tower.my.domain (nscs21p13.remote.umass.edu [128.119.179.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA21107 for ; Fri, 24 Jul 1998 16:15:51 -0700 (PDT) (envelope-from gp@philos.umass.edu) Received: from localhost (gp@localhost) by tower.my.domain (8.8.8/8.8.8) with SMTP id TAA00246 for ; Fri, 24 Jul 1998 19:18:41 -0400 (EDT) (envelope-from gp@tower.my.domain) Date: Fri, 24 Jul 1998 19:18:41 -0400 (EDT) From: Greg Pavelcak X-Sender: gp@tower.my.domain To: freebsd-current@FreeBSD.ORG Subject: Directory removal problem. 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 am running current from about 2 days ago. I was moving my ports directory from one disk to another and all seemed to go well except that the directory ports/games/xpat2 wasn't removed from the first disk. Even when I try to rm -R as root, it says: rm: /usr/d2/ports/games/xpat2/: Directory not empty rm: /usr/d2/ports/games: Directory not empty rm: /usr/d2/ports: Directory not empty xpat2 looks empty to me: ls -Rl /usr/d2/ports total 2 drwxr-xr-x 3 root wheel 2048 Jul 24 18:58 games /usr/d2/ports/games: total 1 drwxr-xr-x 1 root wheel 512 Jul 24 19:01 xpat2 /usr/d2/ports/games/xpat2: I always worried that rm -Rf as root was dangerous. Now I can't even remove an empty directory with it. Any ideas? Greg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 24 16:46:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA27157 for freebsd-current-outgoing; Fri, 24 Jul 1998 16:46:41 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.cable.com (mail.cable.com [198.38.0.27]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA27086 for ; Fri, 24 Jul 1998 16:46:14 -0700 (PDT) (envelope-from jan@cable.com) Received: from korgi (console.cable.com [198.38.2.67]) by mail.cable.com (8.8.7/8.8.7) with SMTP id TAA02285 for ; Fri, 24 Jul 1998 19:45:45 -0400 (EDT) (envelope-from jan@cable.com) Message-ID: <033c01bdb75d$ede15110$c8c8c8c8@korgi.cable.com> From: "Jan T Pajak" To: Subject: Fw: Directory removal problem. Date: Fri, 24 Jul 1998 19:51:07 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is it possible you were playing the game, and left an executing process whose current directory was within the hierarchy you were trying to remove? -----Original Message----- From: Greg Pavelcak To: freebsd-current@freebsd.org Date: Friday, July 24, 1998 7:35 PM Subject: Directory removal problem. >I am running current from about 2 days ago. > >I was moving my ports directory from one disk to another and all >seemed to go well except that the directory ports/games/xpat2 >wasn't removed from the first disk. Even when I try to rm -R as >root, it says: > > rm: /usr/d2/ports/games/xpat2/: Directory not empty > rm: /usr/d2/ports/games: Directory not empty > rm: /usr/d2/ports: Directory not empty > >xpat2 looks empty to me: > > ls -Rl /usr/d2/ports > total 2 > drwxr-xr-x 3 root wheel 2048 Jul 24 18:58 games > > /usr/d2/ports/games: > total 1 > drwxr-xr-x 1 root wheel 512 Jul 24 19:01 xpat2 > > /usr/d2/ports/games/xpat2: > >I always worried that rm -Rf as root was dangerous. Now I can't >even remove an empty directory with it. > >Any ideas? > >Greg > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 24 17:35:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA07630 for freebsd-current-outgoing; Fri, 24 Jul 1998 17:35:39 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp-gw.BayNetworks.COM (ns1.BayNetworks.COM [134.177.3.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA07519 for ; Fri, 24 Jul 1998 17:34:55 -0700 (PDT) (envelope-from thomma@BayNetworks.COM) Received: from mailhost.BayNetworks.COM (h016b.s86b1.BayNetworks.COM [134.177.1.107] (may be forged)) by smtp-gw.BayNetworks.COM (8.8.8/8.8.8) with ESMTP id RAA11968; Fri, 24 Jul 1998 17:33:50 -0700 (PDT) Received: from fedex.engwest.baynetworks.com (fedex.engwest.baynetworks.com [134.177.110.46]) by mailhost.BayNetworks.COM (8.8.8/8.8.8) with SMTP id RAA25718; Fri, 24 Jul 1998 17:33:39 -0700 (PDT) Received: from carrera.engwest ([134.177.160.237]) by fedex.engwest.baynetworks.com (4.1/SMI-4.1) Received: from localhost by carrera.engwest (SMI-8.6/SMI-SVR4) id RAA24396; Fri, 24 Jul 1998 17:31:33 -0700 To: gpavelcak@philos.umass.edu Cc: freebsd-current@FreeBSD.ORG Subject: Re: Directory removal problem. In-Reply-To: Your message of "Fri, 24 Jul 1998 19:18:41 -0400 (EDT)" References: X-Mailer: Mew version 1.92 on Emacs 19.28 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19980724173132Z.thomma@baynetworks.com> Date: Fri, 24 Jul 1998 17:31:32 -0700 From: Tamiji Homma X-Dispatcher: imput version 971024 Lines: 28 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greg, > I am running current from about 2 days ago. > > I was moving my ports directory from one disk to another and all > seemed to go well except that the directory ports/games/xpat2 > wasn't removed from the first disk. Even when I try to rm -R as > root, it says: > > rm: /usr/d2/ports/games/xpat2/: Directory not empty > rm: /usr/d2/ports/games: Directory not empty > rm: /usr/d2/ports: Directory not empty I have seen similar stuff... Do you use softupdates? In early days of softupdates, when the system crashed, fsck didn't seem to fix it cleanly. The fsck appeared to correct the problem but it really didn't. So I turned off softupdates (tunefs -n disable /dev/xxxx) and did fsck manually. It found the problem and fixed it. Then I turned back softupdates on. I'm not sure this helps but you might want to try it. Tammy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 24 18:34:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA17136 for freebsd-current-outgoing; Fri, 24 Jul 1998 18:34:16 -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 SAA17127 for ; Fri, 24 Jul 1998 18:34:11 -0700 (PDT) (envelope-from tlambert@usr06.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id SAA01910; Fri, 24 Jul 1998 18:33:47 -0700 (MST) Received: from usr06.primenet.com(206.165.6.206) via SMTP by smtp01.primenet.com, id smtpd001884; Fri Jul 24 18:33:43 1998 Received: (from tlambert@localhost) by usr06.primenet.com (8.8.5/8.8.5) id SAA21242; Fri, 24 Jul 1998 18:33:40 -0700 (MST) From: Terry Lambert Message-Id: <199807250133.SAA21242@usr06.primenet.com> Subject: Re: Does building current on 2.2.x still work? To: rkw@dataplex.net (Richard Wackerbarth) Date: Sat, 25 Jul 1998 01:33:40 +0000 (GMT) Cc: tlambert@primenet.com, current@FreeBSD.ORG In-Reply-To: from "Richard Wackerbarth" at Jul 24, 98 06:17:08 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 > >> Yes, installing .mk files just to bootstrap would cause much the same > >> problems as making the infamous `includes' target just to bootstrap. > > > >I think it should just use the right ones. If necessary, it should > >build the new make to get the -m option for the reinvocation of make. > > > >A "worse than 'includes'" problem is DESTDIR. It means that you can't > >keep a buildable system while attempting to resolve > > > >It does this because there is no seperation of > >"build environment" from "build target". > > Keep preaching, Terry. Perhaps you can eventually gain some converts > and they will allow the reorganization necessary to catch up with the > capabilities that we had 35 years ago. > > Needless to say, I tried and gave up. This was intended as a bug report, not a preach. As David Wolfskill pointed out, building version X on version Y is precisely analogous to cross-building version X for a non-Intel platform on a version X Intel platform. You have to encapsulate everything. The new -m option (and the option 2.2.x added to the linker or whatever to strip symbols) are both very dissatisfying, compared to using the seperate tools and not overloading tool functionality and smearing part of "strip" functionality into other toold to make the .mk files look pretty. This becomes more obvious when you go to build version Y for a non-Intel platform on a version X Intel platform. Unlike the native compilation case, where you can build a subset of the tree needed to build the full tree, chroot down to avoid -m and other "let's embed knowledge of the relative path everywhere" hacks, you *can't* chroott an Intel machine into a non-Intel tree subset and then expect to be able to run the tools. It doesn't work. This is even more annoying when you have to deal with system calls that SIG 12 you because they don't exist and some fool had the bright idea to "enhance" the POSIX specification, instead of doing the proper error return, and setting errno to ENOSYS so that the library can compensate for the gratuitous extension. The default behaviour now requires programs to not only do that, but to ignore SIGSYS (name one program that does this). The library can't easily compensate because it would have to diddle signals around each and every new system call, until some future time when there are nothing but diddled calls littering the library. 8-(. OK, not a preach, but a rant... 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 Fri Jul 24 20:48:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA29607 for freebsd-current-outgoing; Fri, 24 Jul 1998 20:48:20 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from kong.dorms.spbu.ru (kong@kong.dorms.spbu.ru [195.19.252.147]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA29601 for ; Fri, 24 Jul 1998 20:48:09 -0700 (PDT) (envelope-from kong@kong.dorms.spbu.ru) Received: from localhost (kong@localhost) by kong.dorms.spbu.ru (8.8.8/kong/0.01) with SMTP id HAA00378; Sat, 25 Jul 1998 07:47:14 +0400 (MSD) (envelope-from kong@kong.dorms.spbu.ru) Date: Sat, 25 Jul 1998 07:47:14 +0400 (MSD) From: Hostas Red To: Doug White cc: current@FreeBSD.ORG Subject: Re: Strange idle times 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, 24 Jul 1998, Doug White wrote: > > About one month or so i have a strange idle times on my -current (really > > current - 1 hour or so :) - whenever i use 'w' or 'finger' idle time of > > users equivalent to uptime (maybe 1 minute less). ;-( > > > > 'apm' disabled in kernel, nothing changed ever since. It just happend one > > time and lasts till now. > > > > Anybody have such a problem? > > Corrupted utmp/wtmp perhaps? Something trying to use the old format? But why? I'm sitting on -current for more than half a year already and i'm rebooting sometimes :). wtmp rolls daily, utmp brand new after rebooting half an hour ago. And problem still exitst, after one more 'make world'. Adios, /KONG To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 24 21:16:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA02993 for freebsd-current-outgoing; Fri, 24 Jul 1998 21:16:12 -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 VAA02988 for ; Fri, 24 Jul 1998 21:16:10 -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 0yzvkH-0007G5-00; Fri, 24 Jul 1998 22:15:45 -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 WAA20098; Fri, 24 Jul 1998 22:18:49 -0600 (MDT) Message-Id: <199807250418.WAA20098@harmony.village.org> To: Mike Smith Subject: Re: More doscmd adventures/lockups Cc: Brian Feldman , freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Thu, 23 Jul 1998 11:34:46 PDT." <199807231834.LAA00344@dingo.cdrom.com> References: <199807231834.LAA00344@dingo.cdrom.com> Date: Fri, 24 Jul 1998 22:18:49 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199807231834.LAA00344@dingo.cdrom.com> Mike Smith writes: : > Yessiree, doscmd has ways of locking me up without a panic. I'll explore : > what happened this time: I was using my 5[0-2][0-8]mb dos drive in bochs, : > installing MS-DOS 6.22. I tried using doscmd to boot it, doscmd -bx... : > after Starting msdos... the whole computer froze, I waited a few minutes, : > and hit reset when I was sure it was locked up solid. To recap: bochs was : > loading dos on the drive, on disk 2 by now, and doscmd -bx tried to boot : > the drive; this was standard access, no vn(4) problems. : : Please, if you're going to report problems, try doing it in a fashion : that gives us something to work with. : : For example, here you haven't mentioned what level of -currentness your : system is at, or what other options you've got enabled. I've recently done a lot of work on doscmd and would be very interested in things like this... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 24 22:10:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA08126 for freebsd-current-outgoing; Fri, 24 Jul 1998 22:10:59 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ishtar (dialup191.wr.com.au [203.27.69.191]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id WAA08104 for ; Fri, 24 Jul 1998 22:10:43 -0700 (PDT) (envelope-from davidh@wr.com.au) Received: (qmail 819 invoked by uid 1411); 25 Jul 1998 05:11:03 -0000 Message-ID: <19980725151103.27564@wr.com.au> Date: Sat, 25 Jul 1998 15:11:03 +1000 From: David Hobley To: Ricardas Cepas Cc: current@FreeBSD.ORG Subject: Re: Mozilla and lesstif References: <35B8C76A.DAA5775B@ip.lt> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <35B8C76A.DAA5775B@ip.lt>; from Ricardas Cepas on Fri, Jul 24, 1998 at 07:42:02PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jul 24, 1998 at 07:42:02PM +0200, Ricardas Cepas wrote: > Hello, > > Does somebody succeeded to compile Mozilla with Lesstif? > I found in Mozilla docs that lesstif can be used "with limited > succsess". For my it ends by: > .... > gmake: *** [install] Error 2 > *** Error code 2 > > Thank you, > -- > > Ricardas Cepas I have compiled Mozilla with the latest binary release of lesstif (0.84 I think) from www.lesstif.org but it is inordinately buggy unfortunately. I have just finished compiling a debugged one, (66 Meg exe) but I don't I have the Motif skills to work out where the bugs are. -- Cheers, david -- http://www.angelfire.com/wa/hobley To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 24 22:36:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA10841 for freebsd-current-outgoing; Fri, 24 Jul 1998 22:36:53 -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 WAA10817 for ; Fri, 24 Jul 1998 22:36:44 -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 WAA06339; Fri, 24 Jul 1998 22:36:16 -0700 (PDT) (envelope-from jdp) Message-Id: <199807250536.WAA06339@austin.polstra.com> To: mcdougall@ameritech.net Subject: Re: strange src tree corruption In-Reply-To: <35B90D60.3FE563F0@ameritech.net> References: <35B90D60.3FE563F0@ameritech.net> Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Date: Fri, 24 Jul 1998 22:36:16 -0700 From: John Polstra Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <35B90D60.3FE563F0@ameritech.net>, Adam McDougall wrote: > This seems to happen now a few times each time I attempt a buildworld, > the compile bombs out with something like this: > /asynch/src/gnu/usr.bin/perl/perl/perl.c:1478: unterminated string or > character constant/asynch/src/gnu/usr.bin/perl/perl/perl.c:1239: > possible real start of unterminated constant > /asynch/src/gnu/usr.bin/perl/perl/perl.c:1236: unterminated `#if' > conditional > /asynch/src/gnu/usr.bin/perl/perl/perl.c: In function `do_eval': > /asynch/src/gnu/usr.bin/perl/perl/perl.c:1236: parse error at end of > input/asynch/src/gnu/usr.bin/perl/perl/perl.c:118: warning: > `moreswitches' declared `static' but never defined > *** Error code 1 > > this is right after a cvsup. if I rm the file, and cvsup, its magically > fixed. > The filesystem this partition is on has softupdates, but thats the only > thing special I can think about it. I recently copied my src tree off it > and newfs'ed but the problem remains. Is there something that may be > stopping cvsup from properly checking or updating corrupted files? This really sounds like hardware problems and/or filesystem damage. The next time it happens, look at the bad file with "hd". I bet you'll find that the corruption begins and ends exactly at a 4K boundary in your file (4K = 1 page). To understand CVSup's behavior in the presence of this kind of corruption, you have to realize two things. 1. CVSup first decides which files _might_ need updating, by examining the information it can get from a call to stat(2). This includes the modtime of the file and its size. If there's no difference between the stat() information on the client and on the server, then CVSup decides that the file is up to date. In that case, it never even opens the file, and it doesn't consider it any further. Unfortunately, the kind of corruption caused by filesystem damage or hardware problems often doesn't change the file's modtime or its size at all. Such corruption goes unnoticed by CVSup until the next time the file is changed on the server, which could be a very long time from now. Around this point in the lecture, a few people always pipe up and say, "That's too dangerous! It should MD5 each file every time you run it!" Nope, wrong answer. Try it some time. You _cannot_ achieve reasonable update performance if you do that. You _must_ cull out the unchanged files based on stat() information first. Also, c'mon -- it's unreasonable to expect a file update program to be robust in the face of hardware problems and/or filesystem damage. No program is robust under those conditions. 2. Whenever CVSup updates a file in any way, it computes the MD5 checksum of the updated file and checks it against the server's version of the file. So at the time CVSup writes the new file, it is certain that what it is writing it is correct. BUT as an application program, it can only check the data that it sends to the write() system call. In a flakey system, a lot can happen to that data before it gets physically written to the disk drive. Believe me, I've seen it all. I've seen 1-bit errors in files, and I've seen page-size blocks of zeros or page-size chunks of completely unrelated files splatted into the middle of other files. There's no way for CVSup to check for that kind of damage. Even if it re-opened the file and read it back again, the data would most likely come out of the kernel's buffer cache, which still wouldn't reflect what was actually on the disk. So: suspect your hardware, and suspect soft-updates. 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 Sat Jul 25 00:17:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA19751 for freebsd-current-outgoing; Sat, 25 Jul 1998 00:17:25 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA19746 for ; Sat, 25 Jul 1998 00:17:22 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id QAA08209 for ; Sat, 25 Jul 1998 16:46:55 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id QAA02170; Sat, 25 Jul 1998 16:46:50 +0930 (CST) Message-ID: <19980725164649.P716@freebie.lemis.com> Date: Sat, 25 Jul 1998 16:46:49 +0930 From: Greg Lehey To: FreeBSD current users Subject: Ridiculous CPU time usage in -CURRENT? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i 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 I'm just doing a backup on my laptop, and I've noticed the following stuff from top: last pid: 6742; load averages: 0.88, 0.99, 0.93 16:41:59 48 processes: 2 running, 46 sleeping CPU states: 0.8% user, 0.0% nice, 34.7% system, 51.1% interrupt, 13.4% idle Mem: 6660K Active, 4976K Inact, 7204K Wired, 2660K Cache, 2445K Buf, 480K Free Swap: 128M Total, 25M Used, 103M Free, 19% Inuse PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND 6672 root 66 0 588K 336K RUN 195:30 64.93% 64.93% tar last pid: 6742; load averages: 0.94, 0.99, 0.93 16:42:57 (same old blurb) PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND 6672 root 56 0 588K 336K RUN 219:09 46.46% 46.46% tar In other words, in the space of 58 seconds the CPU time usage has gone up by 23 minutes. This happens in sudden jumps; the rest of the time things look OK. Any ideas what could be causing it? I'm running a -CURRENT kernel built round 25 June, and probably supped within a day of building. I'm running xntpd, but that doesn't seem to be the reason: the time's been OK for weeks. The machine's been running since 29 June. 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 25 01:18:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA23735 for freebsd-current-outgoing; Sat, 25 Jul 1998 01:18:42 -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 BAA23692 for ; Sat, 25 Jul 1998 01:18:16 -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 LAA02441; Sat, 25 Jul 1998 11:16:30 +0300 (EEST) (envelope-from ady@warpnet.ro) Date: Sat, 25 Jul 1998 11:16:30 +0300 (EEST) From: Adrian Penisoara To: Gerald Ehritz cc: freebsd-current@FreeBSD.ORG Subject: Re: pine 3.96 locks 3.0-980621 completely In-Reply-To: <199807240727.JAA08572@arcturus.dbai.tuwien.ac.at> 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, 24 Jul 1998, Gerald Ehritz wrote: > > You may want to try a newer Pine 4 version > We tested pine 4.0 and it also fails. Could not test 4.02 because of a >permission denied on freebsd.org. Other people complained about persmission issues too; it seems like ftp.FreeBSD.org changes the permissions of the uploaded files in /pub/FreeBSD/incoming to smth. like o-rwx ; strangely I can get the file with Netscape but not with wget or ftp... Who's in charge with ftp.FreeBSD.org/pub/FreeBSD maintainance ? I'll send it to you in another message anyway. > > Gerald > 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 25 04:14:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA08924 for freebsd-current-outgoing; Sat, 25 Jul 1998 04:14:12 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from tower.my.domain (nscs26p16.remote.umass.edu [128.119.179.122]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA08919 for ; Sat, 25 Jul 1998 04:14:09 -0700 (PDT) (envelope-from gp@philos.umass.edu) Received: from localhost (gp@localhost) by tower.my.domain (8.8.8/8.8.8) with SMTP id HAA04103 for ; Sat, 25 Jul 1998 07:17:03 -0400 (EDT) (envelope-from gp@tower.my.domain) Date: Sat, 25 Jul 1998 07:16:42 -0400 (EDT) From: Greg Pavelcak To: freebsd-current@FreeBSD.ORG Subject: Re: Fw: Directory removal problem. In-Reply-To: <033c01bdb75d$ede15110$c8c8c8c8@korgi.cable.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 >I am running current from about 2 days ago. > >I was moving my ports directory from one disk to another and all >seemed to go well except that the directory ports/games/xpat2 >wasn't removed from the first disk. Even when I try to rm -R as >root, it says: > > rm: /usr/d2/ports/games/xpat2/: Directory not empty > rm: /usr/d2/ports/games: Directory not empty > rm: /usr/d2/ports: Directory not empty > Thanks for all the suggestions on this. I should have reported that I had softupdates on and had to use reset to reboot shortly before I noticed this problem. Turned out a manual fsck with softupdates off got rid of the problem. Greg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 25 07:26:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA22637 for freebsd-current-outgoing; Sat, 25 Jul 1998 07:26:52 -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 HAA22630 for ; Sat, 25 Jul 1998 07:26:50 -0700 (PDT) (envelope-from eculp@webwizard.org.mx) Received: from webwizard.org.mx (mexcom.net.mx [207.249.162.140]) by dns.webwizard.net.mx (8.8.8/8.8.7) with ESMTP id JAA14718; Sat, 25 Jul 1998 09:24:47 -0500 (CDT) Message-ID: <35B9EAAF.69F49579@webwizard.org.mx> Date: Sat, 25 Jul 1998 09:24:47 -0500 From: Edwin Culp X-Mailer: Mozilla 4.5b1 [en] (X11; I; FreeBSD 3.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: John Polstra CC: freebsd-current@FreeBSD.ORG Subject: Re: make release References: <35B7F199.A7A88FA@webwizard.org.mx> <199807240415.VAA27447@austin.polstra.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Polstra wrote: > In article <35B7F199.A7A88FA@webwizard.org.mx>, > Edwin Culp wrote: > > > > C U T > > > > You are CVSupping both the checked-out -current sources and the CVS > repository to the same place ("/usr/{src,doc,ports}"). Why? No > wonder you're having problems. > > For the "cvs-rel" supfile (getting the CVS repository), you should > have "*default prefix=/home/ncvs". And if you are getting the CVS > repository, you should probably not get the checked-out -current > sources ("cvs-supfile") at all. Just check them out of the > repository using cvs. > > I would suggest rereading the CVSup section of the FreeBSD Handbook. > I did, but I think I got more from man cvs which I know nothing about. I would like to confirm that with this configuration if I do a # cvs -d /home/ncvs checkout src from the /usr/src directory, I will have updated sources to be able to do a make world? I tried it and it seems to work, but it checks out everything. Is that what I want to do or do I want only the changes? Once I understand this, make release is not a problem. It will be just like before Thanks. ed To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 25 07:47:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA24758 for freebsd-current-outgoing; Sat, 25 Jul 1998 07:47:15 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA24746 for ; Sat, 25 Jul 1998 07:47:14 -0700 (PDT) (envelope-from chuckr@glue.umd.edu) Received: from picnic.mat.net ([209.118.174.117]) by freefall.freebsd.org (8.8.8/8.8.5) with ESMTP id HAA02805 for ; Sat, 25 Jul 1998 07:46:26 -0700 (PDT) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.8.8/8.8.5) with SMTP id JAA17052; Sat, 25 Jul 1998 09:44:46 -0400 (EDT) Date: Sat, 25 Jul 1998 09:44:46 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@picnic.mat.net To: Thomas Dean cc: kuku@gilberto.physik.RWTH-Aachen.DE, freebsd-current@freefall.cdrom.com Subject: Re: /usr/lib/aout In-Reply-To: <199807241524.IAA00723@ix.netcom.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 Fri, 24 Jul 1998, Thomas Dean wrote: > I copied all the libs in /usr/lib to /usr/lib/aout. I changed > /usr/lib to /usr/lib/aout in ldconfig statements. After I was sure my > upgrade worked, I moved the libs in /usr/lib to /usr/lib/old. After I > checked that everything worked, I rm'ed /usr/lib/old. > > Maybe I am too cautious. That approach would undoubtedly work, but when things move over to elf, I hope important stuff like ssh doesn't do straight down the tubes. I can't figure out why it wants /usr/lib/libc, but I can sure verify that it does. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 25 07:59:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA26284 for freebsd-current-outgoing; Sat, 25 Jul 1998 07:59:13 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from picnic.mat.net ([209.118.174.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA26266 for ; Sat, 25 Jul 1998 07:59:07 -0700 (PDT) (envelope-from chuckr@glue.umd.edu) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.8.8/8.8.5) with SMTP id JAA17081; Sat, 25 Jul 1998 09:57:20 -0400 (EDT) Date: Sat, 25 Jul 1998 09:57:20 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@picnic.mat.net To: "Jordan K. Hubbard" cc: freebsd-current@FreeBSD.ORG Subject: release plans 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 Jordan, you've probably announced this already (and I missed it because I've lost so much time this summer) but could you please give your notion of FreeBSD's release plans, even rough ones? If you don't have dates, then just the release numbering? I'm looking for your opinion here, so if core hasn't agreed, that's fine (though you better point that out clearly so you don't get called on it). I've curious about when 3.0 is going to make it, actually. I was under the impression that it was going to be the next one. I remember a heated argument about that some time back, where the fact that "it's already been decided in core, so stop arguing" was the final result, but then 2.2.7 arrives, and I got kinda confused. The idea of getting both smp and soft updates in a release, well, it'd be worth quite a bit of my time pushing upgrade-fever on my friends. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 25 12:29:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA19311 for freebsd-current-outgoing; Sat, 25 Jul 1998 12:29:27 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from vader.cs.berkeley.edu (vader.CS.Berkeley.EDU [128.32.38.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA19301 for ; Sat, 25 Jul 1998 12:29:22 -0700 (PDT) (envelope-from asami@vader.cs.berkeley.edu) Received: from silvia.HIP.Berkeley.EDU (sji-ca7-188.ix.netcom.com [209.109.235.188]) by vader.cs.berkeley.edu (8.8.7/8.7.3) with ESMTP id MAA17549; Sat, 25 Jul 1998 12:28:54 -0700 (PDT) Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.8/8.6.9) id MAA07432; Sat, 25 Jul 1998 12:28:51 -0700 (PDT) Date: Sat, 25 Jul 1998 12:28:51 -0700 (PDT) Message-Id: <199807251928.MAA07432@silvia.HIP.Berkeley.EDU> To: chuckr@glue.umd.edu CC: jkh@time.cdrom.com, freebsd-current@FreeBSD.ORG In-reply-to: (message from Chuck Robey on Sat, 25 Jul 1998 09:57:20 -0400 (EDT)) Subject: Re: release plans From: asami@FreeBSD.ORG (Satoshi Asami) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Jordan, you've probably announced this already (and I missed it because * I've lost so much time this summer) but could you please give your * notion of FreeBSD's release plans, even rough ones? If you don't have * dates, then just the release numbering? I'm looking for your opinion * here, so if core hasn't agreed, that's fine (though you better point * that out clearly so you don't get called on it). I'm not Jordan but I know he collapsed in an unconscious heap just a few hours ago so I'm going to chime in here. :) You can find out about 3.0 in the Really-Quick NewsLetter: http://www.freebsd.org/news/qnewsletter-1-3.html It says: "Release Information: The latest RELEASE is 2.2.6-RELEASE. FreeBSD 2.2.7 is scheduled to be released July 21st. FreeBSD 3.0 is scheduled to be released October 15th." Beyond that, all core has decided is that there is going to be just one more release (2.2.8) along the 2.2 branch, then it's onto 3.0-land. We haven't decided on the 2.2.8 release date, but if you ask me to guess, it's going to be about 3 months after 3.0. As far as ports are concerned (btw, I'm not speaking for core anymore), the ports team will support both the 2.2 and 3.0 branches, with the preference going to 2.2 in case of conflict, at least until the second release from the 3.0 branch. From there on (official) support for 2.2 will likely be discontinued. Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 25 13:24:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA24203 for freebsd-current-outgoing; Sat, 25 Jul 1998 13:24:53 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from picnic.mat.net ([209.118.174.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA24195; Sat, 25 Jul 1998 13:24:46 -0700 (PDT) (envelope-from chuckr@glue.umd.edu) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.8.8/8.8.5) with SMTP id PAA17843; Sat, 25 Jul 1998 15:23:00 -0400 (EDT) Date: Sat, 25 Jul 1998 15:22:59 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@picnic.mat.net To: Satoshi Asami cc: jkh@time.cdrom.com, freebsd-current@FreeBSD.ORG Subject: Re: release plans In-Reply-To: <199807251928.MAA07432@silvia.HIP.Berkeley.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 Sat, 25 Jul 1998, Satoshi Asami wrote: > * Jordan, you've probably announced this already (and I missed it because > * I've lost so much time this summer) but could you please give your > * notion of FreeBSD's release plans, even rough ones? If you don't have > * dates, then just the release numbering? I'm looking for your opinion > * here, so if core hasn't agreed, that's fine (though you better point > * that out clearly so you don't get called on it). > > I'm not Jordan but I know he collapsed in an unconscious heap just a > few hours ago so I'm going to chime in here. :) > > You can find out about 3.0 in the Really-Quick NewsLetter: > > http://www.freebsd.org/news/qnewsletter-1-3.html > > It says: > > "Release Information: The latest RELEASE is 2.2.6-RELEASE. FreeBSD > 2.2.7 is scheduled to be released July 21st. FreeBSD 3.0 is scheduled > to be released October 15th." > > Beyond that, all core has decided is that there is going to be just > one more release (2.2.8) along the 2.2 branch, then it's onto > 3.0-land. We haven't decided on the 2.2.8 release date, but if you > ask me to guess, it's going to be about 3 months after 3.0. > > As far as ports are concerned (btw, I'm not speaking for core > anymore), the ports team will support both the 2.2 and 3.0 branches, > with the preference going to 2.2 in case of conflict, at least until > the second release from the 3.0 branch. From there on (official) > support for 2.2 will likely be discontinued. That's what I was looking for, thanks. I'd wondered why Jordan got so short, guessing maybe it was some kinda hot topic in core or something like that. Thanks for filling in the gaps. > > Satoshi > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 25 13:41:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA25698 for freebsd-current-outgoing; Sat, 25 Jul 1998 13:41:52 -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 NAA25690; Sat, 25 Jul 1998 13:41:49 -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 WAA11713; Sat, 25 Jul 1998 22:41:22 +0200 (MET DST) Received: (from dag-erli@localhost) by hrotti.ifi.uio.no ; Sat, 25 Jul 1998 22:41:20 +0200 (MET DST) Mime-Version: 1.0 To: hackers@FreeBSD.ORG, current@FreeBSD.ORG Subject: sysexits 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: 25 Jul 1998 22:41:19 +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 NAA25694 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The style(9) man page recommends the use of values defined in to indicate failure conditions. However, there is no predefined value for what is probably the most common error condition, at least in some applications - a failed malloc(), calloc() or realloc(). I therefore suggest adding the constant EX_NOMEM, with the value 79, to /usr/include/sysexits.h, and bumping EX__MAX to 79 (as well as updating the sysexits(3) man page, of course). Unless somebody strenuously objects, I'll commit the changes to -current in a couple of days. DES -- Dag-Erling Smørgrav - dag-erli@ifi.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 25 13:52:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA26879 for freebsd-current-outgoing; Sat, 25 Jul 1998 13:52:21 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA26849 for ; Sat, 25 Jul 1998 13:52:14 -0700 (PDT) (envelope-from karl@Mars.mcs.net) Received: from Mars.mcs.net (karl@Mars.mcs.net [192.160.127.85]) by Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id PAA04137 for ; Sat, 25 Jul 1998 15:51:49 -0500 (CDT) Received: (from karl@localhost) by Mars.mcs.net (8.8.7/8.8.2) id PAA02587; Sat, 25 Jul 1998 15:51:49 -0500 (CDT) Message-ID: <19980725155148.43084@mcs.net> Date: Sat, 25 Jul 1998 15:51:48 -0500 From: Karl Denninger To: current@FreeBSD.ORG Subject: MMAP problems Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi folks, I believe I have found a rather serious MMAP problem in -CURRENT. Diablo (the news system) is the test case; with MMAP enabled it will randomly write exactly one block (512 bytes) of zeros into the article spool files rather than the proper data - its almost like an update via MMAP isn't actually happening when it should, and is being thrown away. This shows up as a corrupted batch when you try to transmit to others. I'm working on trying to isolate this, and will have more when I know better what is going on. -- -- Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin http://www.mcs.net/ | T1's from $600 monthly / All Lines K56Flex/DOV | NEW! Corporate ISDN Prices dropped by up to 50%! Voice: [+1 312 803-MCS1 x219]| EXCLUSIVE NEW FEATURE ON ALL PERSONAL ACCOUNTS Fax: [+1 312 803-4929] | *SPAMBLOCK* Technology now included at no cost To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 25 14:03:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA28076 for freebsd-current-outgoing; Sat, 25 Jul 1998 14:03:56 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.gwinnett.com (mail.gwinnett.com [204.89.227.35]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA28061 for ; Sat, 25 Jul 1998 14:03:53 -0700 (PDT) (envelope-from lee@gwinnett.com) Received: from venus.gwinnett.com ([204.89.227.91]) by mail.gwinnett.com (8.8.7/8.8.5) with SMTP id RAA29971 for ; Sat, 25 Jul 1998 17:03:26 -0400 Message-ID: <35BA480F.41C67EA6@gwinnett.com> Date: Sat, 25 Jul 1998 17:03:11 -0400 From: Lee Reese X-Mailer: Mozilla 3.04 (X11; I; FreeBSD 3.0CAM-19980712-0 i386) MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: Thanks-Re: Viability/Usenet News References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks for your help, guys. I now have INN-2.0 running on my Dual-Processor Usenet News Server. It has been running for an hour now and everything looks good so far. I wound up using yesterday's snapshot release on the server. I will wait until Monday Morning to put it into full production. FreeBSD is going to be installed on our main web server, since we need Frontpage Extensions (UGH!). 2.2.7 will be used on that machine since it is a uniprocessor machine. Lee To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 25 14:27:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA00913 for freebsd-current-outgoing; Sat, 25 Jul 1998 14:27:20 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.kersur.net (root@mail.kersur.net [199.79.199.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA00907 for ; Sat, 25 Jul 1998 14:27:16 -0700 (PDT) (envelope-from dswartz@druber.com) Received: from manticore (manticore.druber.com [207.180.95.108]) by mail.kersur.net (8.8.8/8.8.8) with SMTP id RAA01588; Sat, 25 Jul 1998 17:27:10 -0400 (EDT) Message-Id: <3.0.5.32.19980725172640.00944ac0@mail.kersur.net> X-Sender: druber@mail.kersur.net X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Sat, 25 Jul 1998 17:26:40 -0400 To: Karl Denninger From: Dan Swartzendruber Subject: Re: MMAP problems Cc: current@FreeBSD.ORG In-Reply-To: <19980725155148.43084@mcs.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I wonder if this is related to the corruption I've seen in 2.2 with the CAM patches. Only, in that case what is getting corrupted is the active file. An entry with binary garbage is being slammed into the file. I've seen this twice now. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 25 14:33:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA01604 for freebsd-current-outgoing; Sat, 25 Jul 1998 14:33:10 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA01599 for ; Sat, 25 Jul 1998 14:33:08 -0700 (PDT) (envelope-from karl@Mars.mcs.net) Received: from Mars.mcs.net (karl@Mars.mcs.net [192.160.127.85]) by Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id QAA04796; Sat, 25 Jul 1998 16:32:44 -0500 (CDT) Received: (from karl@localhost) by Mars.mcs.net (8.8.7/8.8.2) id QAA03112; Sat, 25 Jul 1998 16:32:43 -0500 (CDT) Message-ID: <19980725163243.36509@mcs.net> Date: Sat, 25 Jul 1998 16:32:43 -0500 From: Karl Denninger To: Dan Swartzendruber Cc: current@FreeBSD.ORG Subject: Re: MMAP problems References: <19980725155148.43084@mcs.net> <3.0.5.32.19980725172640.00944ac0@mail.kersur.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 In-Reply-To: <3.0.5.32.19980725172640.00944ac0@mail.kersur.net>; from Dan Swartzendruber on Sat, Jul 25, 1998 at 05:26:40PM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Jul 25, 1998 at 05:26:40PM -0400, Dan Swartzendruber wrote: > > I wonder if this is related to the corruption I've seen in 2.2 with the > CAM patches. Only, in that case what is getting corrupted is the active > file. An entry with binary garbage is being slammed into the file. > I've seen this twice now. I can verify that CAM is not related to this; it happens with NON-CAM kernels as well. -- -- Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin http://www.mcs.net/ | T1's from $600 monthly / All Lines K56Flex/DOV | NEW! Corporate ISDN Prices dropped by up to 50%! Voice: [+1 312 803-MCS1 x219]| EXCLUSIVE NEW FEATURE ON ALL PERSONAL ACCOUNTS Fax: [+1 312 803-4929] | *SPAMBLOCK* Technology now included at no cost To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 25 14:37:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA02235 for freebsd-current-outgoing; Sat, 25 Jul 1998 14:37:04 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freefall.pipeline.ch (intranet.pipeline.ch [195.134.128.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA02227 for ; Sat, 25 Jul 1998 14:36:59 -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 AAA304; Sat, 25 Jul 1998 23:35:39 +0200 Message-ID: <35BA4F9A.3E28B29E@pipeline.ch> Date: Sat, 25 Jul 1998 23:35:22 +0200 From: "IBS / Andre Oppermann" Organization: Internet Business Solutions Ltd. (AG) X-Mailer: Mozilla 4.03 [en] (WinNT; U) MIME-Version: 1.0 To: Karl Denninger CC: current@FreeBSD.ORG Subject: Re: MMAP problems References: <19980725155148.43084@mcs.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Karl Denninger wrote: > > Hi folks, > > I believe I have found a rather serious MMAP problem in -CURRENT. > > Diablo (the news system) is the test case; with MMAP enabled it will randomly > write exactly one block (512 bytes) of zeros into the article spool files > rather than the proper data - its almost like an update via MMAP isn't > actually happening when it should, and is being thrown away. This shows > up as a corrupted batch when you try to transmit to others. > > I'm working on trying to isolate this, and will have more when I know > better what is going on. Terry mentioned something like this some time ago, he looked a little bit more into it and said it is also broken on -stable. You might check the archives. -- 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 Sat Jul 25 14:45:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA03851 for freebsd-current-outgoing; Sat, 25 Jul 1998 14:45:25 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.kersur.net (root@mail.kersur.net [199.79.199.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA03846 for ; Sat, 25 Jul 1998 14:45:24 -0700 (PDT) (envelope-from dswartz@druber.com) Received: from manticore (manticore.druber.com [207.180.95.108]) by mail.kersur.net (8.8.8/8.8.8) with SMTP id RAA01987; Sat, 25 Jul 1998 17:45:26 -0400 (EDT) Message-Id: <3.0.5.32.19980725174458.00959ec0@mail.kersur.net> X-Sender: druber@mail.kersur.net X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Sat, 25 Jul 1998 17:44:58 -0400 To: Karl Denninger From: Dan Swartzendruber Subject: Re: MMAP problems Cc: current@FreeBSD.ORG In-Reply-To: <19980725163243.36509@mcs.net> References: <3.0.5.32.19980725172640.00944ac0@mail.kersur.net> <19980725155148.43084@mcs.net> <3.0.5.32.19980725172640.00944ac0@mail.kersur.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 04:32 PM 7/25/98 -0500, Karl Denninger wrote: >On Sat, Jul 25, 1998 at 05:26:40PM -0400, Dan Swartzendruber wrote: >> >> I wonder if this is related to the corruption I've seen in 2.2 with the >> CAM patches. Only, in that case what is getting corrupted is the active >> file. An entry with binary garbage is being slammed into the file. >> I've seen this twice now. > >I can verify that CAM is not related to this; it happens with NON-CAM >kernels as well. Didn't think so either. Just didn't want to get hollered at by someone if it did turn out to be CAM related and I left off that detail... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 25 15:12:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA06898 for freebsd-current-outgoing; Sat, 25 Jul 1998 15:12:35 -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 PAA06893 for ; Sat, 25 Jul 1998 15:12:32 -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 SAA06775 for ; Sat, 25 Jul 1998 18:11:47 -0400 (EDT) Date: Sat, 25 Jul 1998 18:11:47 -0400 (EDT) From: Brian Feldman To: freebsd-current@FreeBSD.ORG Subject: New LINT options: what is VM coloring? 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 anyone mind letting me in on exactly what "VM coloring" is, and especially whether or not I should define one of these?: # 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 As far as I can tell, it would seem these would be options to set certain parameters to optimal as far as the VM subsystem goes, and if so, is it safe to use one? Cheers, Brian Feldman green@unixhelp.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 25 15:21:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA07932 for freebsd-current-outgoing; Sat, 25 Jul 1998 15:21:14 -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 PAA07921 for ; Sat, 25 Jul 1998 15:21:08 -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 SAA06877; Sat, 25 Jul 1998 18:20:19 -0400 (EDT) Date: Sat, 25 Jul 1998 18:20:19 -0400 (EDT) From: Brian Feldman To: IBS / Andre Oppermann cc: Karl Denninger , current@FreeBSD.ORG Subject: Re: MMAP problems In-Reply-To: <35BA4F9A.3E28B29E@pipeline.ch> 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 Hmm, what is the default behavior of msync()? Is it handled automatically, say, in-kernel? If so, maybe it needs to be explicitly called; also is this daemon using a drive with async/softupdates by any chance? Cheers, Brian Feldman green@unixhelp.org On Sat, 25 Jul 1998, IBS / Andre Oppermann wrote: > Karl Denninger wrote: > > > > Hi folks, > > > > I believe I have found a rather serious MMAP problem in -CURRENT. > > > > Diablo (the news system) is the test case; with MMAP enabled it will randomly > > write exactly one block (512 bytes) of zeros into the article spool files > > rather than the proper data - its almost like an update via MMAP isn't > > actually happening when it should, and is being thrown away. This shows > > up as a corrupted batch when you try to transmit to others. > > > > I'm working on trying to isolate this, and will have more when I know > > better what is going on. > > Terry mentioned something like this some time ago, he looked a little > bit more into it and said it is also broken on -stable. > You might check the archives. > > -- > 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 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 25 15:52:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA11230 for freebsd-current-outgoing; Sat, 25 Jul 1998 15:52:07 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from localhost.my.domain (ppp6543.on.bellglobal.com [206.172.208.135]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA11225; Sat, 25 Jul 1998 15:52:04 -0700 (PDT) (envelope-from ac199@hwcn.org) Received: from localhost (tim@localhost) by localhost.my.domain (8.8.8/8.8.8) with ESMTP id SAA27414; Sat, 25 Jul 1998 18:52:15 -0400 (EDT) (envelope-from ac199@hwcn.org) X-Authentication-Warning: localhost.my.domain: tim owned process doing -bs Date: Sat, 25 Jul 1998 18:52:14 -0400 (EDT) From: Tim Vanderhoek X-Sender: tim@localhost Reply-To: ac199@hwcn.org To: Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= cc: hackers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: sysexits In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 25 Jul 1998, Dag-Erling Coidan [iso-8859-1] Smørgrav wrote: > to indicate failure conditions. However, there is no > predefined value for what is probably the most common error condition, > at least in some applications - a failed malloc(), calloc() or What's wrong with EX_OSERR and EX_TEMPFAIL? ;-) -- 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 Sat Jul 25 17:12:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA17986 for freebsd-current-outgoing; Sat, 25 Jul 1998 17:12:49 -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 RAA17980 for ; Sat, 25 Jul 1998 17:12:48 -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 RAA27997; Sat, 25 Jul 1998 17:10:54 -0700 (PDT) Message-Id: <199807260010.RAA27997@implode.root.com> To: Brian Feldman cc: freebsd-current@FreeBSD.ORG Subject: Re: New LINT options: what is VM coloring? In-reply-to: Your message of "Sat, 25 Jul 1998 18:11:47 EDT." From: David Greenman Reply-To: dg@root.com Date: Sat, 25 Jul 1998 17:10:54 -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Would anyone mind letting me in on exactly what "VM coloring" is, and >especially whether or not I should define one of these?: ># 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 >As far as I can tell, it would seem these would be options to set certain >parameters to optimal as far as the VM subsystem goes, and if so, is it >safe to use one? Page coloring is the process of allocating pages that have physical alignment that provides optimal utilization of the memory cache. This can be a big win for direct-mapped caches (e.g. most Pentium L2 caches), but loses effectiveness with set-associative caches (e.g. Pentium Pro, which has a set size of 4). -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 Sat Jul 25 18:42:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA23755 for freebsd-current-outgoing; Sat, 25 Jul 1998 18:42:14 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA23747 for ; Sat, 25 Jul 1998 18:42:08 -0700 (PDT) (envelope-from karl@Mars.mcs.net) Received: from Mars.mcs.net (karl@Mars.mcs.net [192.160.127.85]) by Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id UAA08316; Sat, 25 Jul 1998 20:41:41 -0500 (CDT) Received: (from karl@localhost) by Mars.mcs.net (8.8.7/8.8.2) id UAA05246; Sat, 25 Jul 1998 20:41:41 -0500 (CDT) Message-ID: <19980725204141.39635@mcs.net> Date: Sat, 25 Jul 1998 20:41:41 -0500 From: Karl Denninger To: Brian Feldman Cc: IBS / Andre Oppermann , current@FreeBSD.ORG Subject: Re: MMAP problems References: <35BA4F9A.3E28B29E@pipeline.ch> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 In-Reply-To: ; from Brian Feldman on Sat, Jul 25, 1998 at 06:20:19PM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Jul 25, 1998 at 06:20:19PM -0400, Brian Feldman wrote: > Hmm, what is the default behavior of msync()? Is it handled automatically, > say, in-kernel? If so, maybe it needs to be explicitly called; also is > this daemon using a drive with async/softupdates by any chance? > > Cheers, > Brian Feldman > green@unixhelp.org Its not using a drive which is mounted async or with softupdates. Msync is *NOT* called anywhere in the code that I can find. However, this code is reported to work on a lot of other platforms/systems, and on *SOME* versions of FreeBSD without trouble. It is definitely broken on -current, although not "badly"; the problem happens infrequently, but often enough to piss me off. The real problem is that I don't know what the bad sequence of calls is, and therefore, I have to consider mmap() and friends (including the SYSVSHM implementation, which uses it) unusable. This is a *bad* thing over all, and something that the FreeBSD folks really need to consider doing something about - not having usable and reliable mmap/SHM capability basically destroys FreeBSD as a DBMS or news server if you care about minor things like data integrity. -- -- Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin http://www.mcs.net/ | T1's from $600 monthly / All Lines K56Flex/DOV | NEW! Corporate ISDN Prices dropped by up to 50%! Voice: [+1 312 803-MCS1 x219]| EXCLUSIVE NEW FEATURE ON ALL PERSONAL ACCOUNTS Fax: [+1 312 803-4929] | *SPAMBLOCK* Technology now included at no cost To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 25 19:07:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA25672 for freebsd-current-outgoing; Sat, 25 Jul 1998 19:07: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 TAA25664 for ; Sat, 25 Jul 1998 19:07:15 -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 EAA06305; Sun, 26 Jul 1998 04:06:46 +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 CAA08285; Sun, 26 Jul 1998 02:22:55 +0200 (CEST) (envelope-from roberto) Message-ID: <19980726022254.A7530@keltia.freenix.fr> Date: Sun, 26 Jul 1998 02:22:54 +0200 From: Ollivier Robert To: freebsd-current@FreeBSD.ORG Cc: Julian Stacey Subject: Re: cvs-cur.4492.gz does not have src/Makefile,v RELENG_2_2_7 cvs tag Mail-Followup-To: freebsd-current@FreeBSD.ORG, Julian Stacey References: <199807232120.XAA01455@jhs.muc.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93i In-Reply-To: <199807232120.XAA01455@jhs.muc.de>; from Julian Stacey on Thu, Jul 23, 1998 at 11:20:47PM +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 Julian Stacey: > I'm still waiting for something beyond cvs-cur.4492.gz, > which after application does not have a src/Makefile,v RELENG_2_2_7 cvs tag Check that you're still subscribed to the list, unsubscribing sometimes happen... -rw-r--r-- 1 daemon wheel 3579 Jul 22 19:10 cvs-cur.4492.gz -rw-r--r-- 1 daemon wheel 1199514 Jul 24 19:11 cvs-cur.4493.gz -rw-r--r-- 1 daemon wheel 38625 Jul 24 19:11 cvs-cur.4494.gz -rw-r--r-- 1 daemon wheel 13056 Jul 25 11:30 cvs-cur.4495.gz -rw-r--r-- 1 daemon wheel 3771 Jul 25 11:30 cvs-cur.4496.gz -rw-r--r-- 1 daemon wheel 49262 Jul 25 19:09 cvs-cur.4497.gz -- 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 25 19:07:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA25704 for freebsd-current-outgoing; Sat, 25 Jul 1998 19:07:25 -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 TAA25671; Sat, 25 Jul 1998 19:07:19 -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 MAA29472; Sun, 26 Jul 1998 12:06:52 +1000 Date: Sun, 26 Jul 1998 12:06:52 +1000 From: Bruce Evans Message-Id: <199807260206.MAA29472@godzilla.zeta.org.au> To: current@FreeBSD.ORG, dag-erli@ifi.uio.no, hackers@FreeBSD.ORG Subject: Re: sysexits Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >The style(9) man page recommends the use of values defined in > to indicate failure conditions. However, there is no That's a bug in style(9) :-)/2. The only non-contrib'ed 4.4-Lite source files that use it are rmail/rmail.c, mail.local/mail.local.c and sccs/sccs.c. >predefined value for what is probably the most common error condition, >at least in some applications - a failed malloc(), calloc() or >realloc(). I therefore suggest adding the constant EX_NOMEM, with the What's wrong with errx(1, "[mcre]alloc failed")? The error string will be understood by most humans and approximately 0 progams. EX_NOMEM will be understood by few humans and approximately 1 program (sendmail, but only after you change it to recognise the new error). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 25 19:07:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA25760 for freebsd-current-outgoing; Sat, 25 Jul 1998 19:07:38 -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 TAA25735 for ; Sat, 25 Jul 1998 19:07:29 -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 EAA06306 for freebsd-current@FreeBSD.ORG; Sun, 26 Jul 1998 04:07:02 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (VMailer, from userid 101) id 14061E0C7; Sun, 26 Jul 1998 02:30:04 +0200 (CEST) Message-ID: <19980726023004.B7530@keltia.freenix.fr> Date: Sun, 26 Jul 1998 02:30:04 +0200 From: Ollivier Robert To: freebsd-current@FreeBSD.ORG Subject: Re: New LINT options: what is VM coloring? Mail-Followup-To: freebsd-current@FreeBSD.ORG References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93i In-Reply-To: ; from Brian Feldman on Sat, Jul 25, 1998 at 06:11:47PM -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 Brian Feldman: > As far as I can tell, it would seem these would be options to set certain > parameters to optimal as far as the VM subsystem goes, and if so, is it > safe to use one? I've been using PQ_LARGECACHE on my K6/L1 @ 64 KB/L2 @ 512 KB for more than one year without problem. I don't know if it is really useful but it gives me a warm feeling :-) -- 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 25 19:17:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA27665 for freebsd-current-outgoing; Sat, 25 Jul 1998 19:17:46 -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 TAA27646; Sat, 25 Jul 1998 19:17:44 -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 WAA05555; Sat, 25 Jul 1998 22:17:12 -0400 (EDT) (envelope-from wollman) Date: Sat, 25 Jul 1998 22:17:12 -0400 (EDT) From: Garrett Wollman Message-Id: <199807260217.WAA05555@khavrinen.lcs.mit.edu> To: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= ) Cc: hackers@FreeBSD.ORG, current@FreeBSD.ORG Subject: sysexits In-Reply-To: References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < at least in some applications - a failed malloc(), calloc() or > realloc(). I therefore suggest adding the constant EX_NOMEM, with the > value 79, to /usr/include/sysexits.h, and bumping EX__MAX to 79 (as Good idea. I would also add EX_NOGROUP (parallel to EX_NOUSER). Don't forget to update the table of names in sendmail. -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 Sat Jul 25 19:53:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA00871 for freebsd-current-outgoing; Sat, 25 Jul 1998 19:53:03 -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 TAA00866 for ; Sat, 25 Jul 1998 19:53:01 -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 WAA05646; Sat, 25 Jul 1998 22:52:34 -0400 (EDT) (envelope-from wollman) Date: Sat, 25 Jul 1998 22:52:34 -0400 (EDT) From: Garrett Wollman Message-Id: <199807260252.WAA05646@khavrinen.lcs.mit.edu> To: Karl Denninger Cc: Dan Swartzendruber , current@FreeBSD.ORG Subject: Re: MMAP problems In-Reply-To: <19980725163243.36509@mcs.net> References: <19980725155148.43084@mcs.net> <3.0.5.32.19980725172640.00944ac0@mail.kersur.net> <19980725163243.36509@mcs.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > I can verify that CAM is not related to this; it happens with NON-CAM > kernels as well. I've been seeing it for several months. I believe it to be a coherency problem. The relevant operations here are: 1) A diablo server process appends to a spool file using explicit I/O. (Note that the file is not opened in O_APPEND mode.) 2) A boatload of dnewslink processes simultaneously mmap the pages of the spool file containing the article in question, suck the article out of it, and blast it over to the remote feed. Here's my particular guess... I think this happens when the dnewslink processes are reading another, short, article in the last page of the file, while a diablo server is writing a new article. Somewhere, there is a race condition in which the kernel has copied the new data into the buffer, but blocks before it updates the valid length; this then allows one of the mmaps to succeed, and since that part of the buffer is marked invalid, it gets zeroed. Then the diablo process resumes, and marks the end of the buffer valid, although the data it was writing has just gotten clobbered. It looks, from an inspection of the relevant code in ufs_readwrite.c and ffs_balloc.c, that this cannot happen, because the data are always copied in last. It does appear that there are potential windows, if ffs_balloc() blocks, where other processes might see invalid data in the file through mmap as a result of vnode_pager_setsize() having already been run, but it does not appear such garbage could possibly persist and be written back to disk, and I certainly see it directly on the disk, not just in memory. -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 Sat Jul 25 21:33:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA10254 for freebsd-current-outgoing; Sat, 25 Jul 1998 21:33:41 -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 VAA10242 for ; Sat, 25 Jul 1998 21:33:39 -0700 (PDT) (envelope-from toasty@home.dragondata.com) Received: (from toasty@localhost) by home.dragondata.com (8.8.8/8.8.5) id XAA29040 for current@freebsd.org; Sat, 25 Jul 1998 23:33:13 -0500 (CDT) From: Kevin Day Message-Id: <199807260433.XAA29040@home.dragondata.com> Subject: Last batch of -current bug reports To: current@FreeBSD.ORG Date: Sat, 25 Jul 1998 23:33:12 -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 I assumed that these problems were well known, but in talking to a few people, they'd never heard of any of this. I apologize if I'm getting annoying with these bug reports that are probably already known by those who care, but since October 15th is getting closer, I thought I'd repeat... Random occurances of: swap_pager: suggest more swap space: 254 MB When there obviously is plenty of ram/swap available. I happened to be in 'top' the last time this occurred. I saw a flash of 'k_getuid: kvm_getprocs' fly across the screen, and the above message suggesting more swap. The last printout from top before it exited was: last pid: 15377; load averages: 1.63, 1.44, 1.40 23:07:02 153 processes: 1 running, 152 sleeping Mem: 75M Active, 10M Inact, 23M Wired, 9116K Cache, 8348K Buf, 6396K Free Swap: 164M Total, 46M Used, 118M Free, 28% Inuse pindent complains a lot about bad addresses, and kvm_getprocs not working.. (yet still works 90% of the time) Processes get stuck randomly in 'vmwait'. (can be killed with -9 though) Processes can get stuck in 'nfsrcv' when an nfs server dies and comes back. (are unkillable) 'killall -HUP mountd' causes 'panic: vfs_unlock: not locked' if the server is busy. (this occurs in -STABLE, too) de0 driver is still unstable under heavy (full-duplex 100mb 60-70% utilization) traffic. (causes random page fault while in kernel mode) This will probably be one of my last bug reports before I go back to -STABLE. We bit the bullet and just bought some fast PII/400 servers instead of dealing with the problems of SMP pentium/pentium pro's. (as much as I like -current, our customers are complaining heavily about the once-a-week crashes) If there's any information anyone wants before we newfs our drives, please tell me know. :) Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message