From owner-freebsd-current Sun Apr 5 00:12:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA14168 for freebsd-current-outgoing; Sun, 5 Apr 1998 00:12:30 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from arh0300.urh.uiuc.edu (arh0300.urh.uiuc.edu [130.126.72.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA14134; Sun, 5 Apr 1998 00:12:24 -0800 (PST) (envelope-from dannyman@arh0300.urh.uiuc.edu) Received: (from dannyman@localhost) by arh0300.urh.uiuc.edu (8.8.8/8.8.5) id IAA11235; Sun, 5 Apr 1998 08:12:20 -0500 (CDT) Date: Sun, 5 Apr 1998 08:12:20 -0500 (CDT) From: dannyman Message-Id: <199804051312.IAA11235@arh0300.urh.uiuc.edu> To: FreeBSD-gnats-submit@FreeBSD.ORG Subject: usleep is hosed, timezone problems in current Cc: dannyman@arh0300.urh.uiuc.edu, freebsd-current@FreeBSD.ORG Reply-To: dannyman@arh0300.urh.uiuc.edu X-send-pr-version: 3.2 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Submitter-Id: current-users >Originator: dannyman >Synopsis: problems with usleep and adjkerntz >Severity: serious >Priority: high >Category: i386 >Release: FreeBSD 3.0-CURRENT i386 >Class: sw-bug >Environment: FreeBSD arh0300.urh.uiuc.edu 3.0-CURRENT FreeBSD 3.0-CURRENT #8: Sun Apr 5 01:22:12 CST 1998 dannyman@arh0300.urh.uiuc.edu:/newhome/src/sys/compile/STUMPY i386 >Description: just did a make buildowld ; make installworld on CVSup run at 0430h saturday morning localtime. :) usleep is not returning proper return codes. even when it works just fine, it returns -1 consistently, and appears to set errno at whimsy (i've gotten 35 and 2) ... also, I appear to be on what I guess to be UTC ... i tried to reset my tz with tzsetup ... no avail ... I ran ntpdate and things were corrected, after my X display went blank for awhile. awhile later the screen went blank for a few seconds again and I'm back now ... well, should be 0309h CDT (just should have shifted from CST 0209h ...) 5 April ... date says; Sun Apr 5 08:10:13 CDT 1998 UTC afaik :) >How-To-Repeat: #include #include main() { extern int errno; printf("usleep return: %d\n", usleep(1)); printf("errno: %d\n", errno); } I had a program that was running while(!usleep(val)) and is currently kludged to while(usleep(val)) just fine ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 5 01:14:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA19495 for freebsd-current-outgoing; Sun, 5 Apr 1998 01:14:11 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from helios.dnttm.ru (root@dnttm-gw.rssi.ru [193.232.0.205]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA19463 for ; Sun, 5 Apr 1998 01:13:57 -0800 (PST) (envelope-from dima@tejblum.dnttm.rssi.ru) Received: (from uucp@localhost) by helios.dnttm.ru (8.8.5/8.8.5/IP-3) with UUCP id NAA28970; Sun, 5 Apr 1998 13:09:03 +0400 Received: from tejblum.dnttm.rssi.ru (localhost [127.0.0.1]) by tejblum.dnttm.rssi.ru (8.8.8/8.8.7) with ESMTP id NAA01196; Sun, 5 Apr 1998 13:15:57 +0400 (MSD) (envelope-from dima@tejblum.dnttm.rssi.ru) Message-Id: <199804050915.NAA01196@tejblum.dnttm.rssi.ru> X-Mailer: exmh version 2.0gamma 1/27/96 To: Gianmarco Giovannelli cc: current@FreeBSD.ORG Subject: Re: is msdos fs broken ? In-reply-to: Your message of "Sun, 05 Apr 1998 09:25:50 -0000." <35274E1E.F6178EB0@giovannelli.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 05 Apr 1998 13:15:57 +0400 From: Dmitrij Tejblum Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Gianmarco Giovannelli wrote: > I am trying to mount a fat32 slice with : > > gmarco:/usr/tmp#mount -t msdos /dev/sd0s1 /mnt/dos > msdos: /dev/sd0s1: Invalid argument > gmarco:/usr/tmp#fdisk sd0 .... > The data for partition 1 is: > sysid 11,(DOS or Windows 95 with 32 bit FAT) > start 63, size 9590742 (4682 Meg), flag 0 I'm afraid your disk is slightly too big for msdosfs. Anyway, to know for sure, apply the following patch and watch the console messages. (I think such patch should be committed. Hint...) Dima --- msdosfs_vfsops.c Sun Apr 5 12:42:03 1998 +++ msdosfs_vfsops.c Sun Apr 5 12:52:58 1998 @@ -459,6 +459,7 @@ || bsp->bs50.bsBootSectSig1 != BOOTSIG1) { #endif error = EINVAL; + printf("mountmsdosfs(): bad signature\n"); goto error_exit; } #ifndef __FreeBSD__ @@ -497,6 +498,7 @@ || !pmp->pm_SecPerTrack || pmp->pm_SecPerTrack > 63) { #endif error = EINVAL; + printf("mountmsdosfs(): bad bpb\n"); goto error_exit; } #ifndef __FreeBSD__ @@ -517,6 +519,7 @@ * msdosfs_readdir) */ error = EINVAL; + printf("mountmsdosfs(): disk too big, sorry\n"); goto error_exit; } @@ -527,6 +530,7 @@ || pmp->pm_FATsecs || getushort(b710->bpbFSVers)) { error = EINVAL; + printf("mountmsdosfs(): bad FAT32 filesystem\n"); goto error_exit; } pmp->pm_fatmask = FAT32_MASK; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 5 03:55:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA01808 for freebsd-current-outgoing; Sun, 5 Apr 1998 03:55:55 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ache.relcom.ru (ache.relcom.ru [193.125.20.108]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA01753; Sun, 5 Apr 1998 03:54:49 -0700 (PDT) (envelope-from ache@ache.relcom.ru) Received: (from ache@localhost) by ache.relcom.ru (8.8.8/8.8.8) id OAA00252; Sun, 5 Apr 1998 14:54:28 +0400 (MSD) (envelope-from ache) Message-ID: <19980405145427.14961@nagual.pp.ru> Date: Sun, 5 Apr 1998 14:54:27 +0400 From: =?koi8-r?B?4c7E0sXKIP7F0s7P1w==?= To: phk@FreeBSD.ORG, current@FreeBSD.ORG Subject: dead hang after ppp started (with workaround) Mail-Followup-To: phk@freebsd.org, current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i Organization: Biomechanoid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This change in kern_time.c 1.46 cause dead hang after ppp started, stack looks like: vec1(...) softclock(...) doreti_swi(...) below is workaround (I not shure it is right, just back out to 1.45 code, but it work!) Index: kern_time.c =================================================================== RCS file: /home/ncvs/src/sys/kern/kern_time.c,v retrieving revision 1.46 retrieving revision 1.45 diff -c -r1.46 -r1.45 *** kern_time.c 1998/04/04 18:46:13 1.46 --- kern_time.c 1998/04/04 13:25:25 1.45 *************** *** 536,544 **** if (uap->which == ITIMER_REAL) { if (timerisset(&p->p_realtimer.it_value)) untimeout(realitexpire, (caddr_t)p, p->p_ithandle); ! if (timerisset(&aitv.it_value)) p->p_ithandle = timeout(realitexpire, (caddr_t)p, ! tvtohz(&aitv.it_value)); p->p_realtimer = aitv; } else p->p_stats->p_timer[uap->which] = aitv; --- 536,547 ---- if (uap->which == ITIMER_REAL) { if (timerisset(&p->p_realtimer.it_value)) untimeout(realitexpire, (caddr_t)p, p->p_ithandle); ! if (timerisset(&aitv.it_value)) { ! getmicrotime(&ctv); ! timevaladd(&aitv.it_value, &ctv); p->p_ithandle = timeout(realitexpire, (caddr_t)p, ! hzto(&aitv.it_value)); ! } p->p_realtimer = aitv; } else p->p_stats->p_timer[uap->which] = aitv; -- Andrey A. Chernov http://www.nagual.pp.ru/~ache/ MTH/SH/HE S-- W-- N+ PEC>+ D A a++ C G>+ QH+(++) 666+>++ Y To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 5 04:32:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA07675 for freebsd-current-outgoing; Sun, 5 Apr 1998 04:32:31 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA07670 for ; Sun, 5 Apr 1998 04:32:28 -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 NAA07188; Sun, 5 Apr 1998 13:31:35 +0200 (CEST) To: =?koi8-r?B?4c7E0sXKIP7F0s7P1w==?= cc: current@FreeBSD.ORG Subject: Re: dead hang after ppp started (with workaround) In-reply-to: Your message of "Sun, 05 Apr 1998 14:54:27 +0400." <19980405145427.14961@nagual.pp.ru> Date: Sun, 05 Apr 1998 13:31:35 +0200 Message-ID: <7186.891775895@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Try this patch... I overlooked something in the itimer handling... Index: kern_time.c =================================================================== RCS file: /home/ncvs/src/sys/kern/kern_time.c,v retrieving revision 1.48 diff -u -r1.48 kern_time.c --- kern_time.c 1998/04/05 10:28:01 1.48 +++ kern_time.c 1998/04/05 11:30:46 @@ -102,10 +102,6 @@ ts.tv_nsec = tv->tv_usec * 1000; set_timecounter(&ts); (void) splsoftclock(); - for (p = allproc.lh_first; p != 0; p = p->p_list.le_next) { - if (timerisset(&p->p_realtimer.it_value)) - timevaladd(&p->p_realtimer.it_value, &delta); - } lease_updatetime(delta.tv_sec); splx(s); resettodr(); @@ -479,7 +475,7 @@ */ aitv = p->p_realtimer; if (timerisset(&aitv.it_value)) { - getmicrotime(&ctv); + getmicroruntime(&ctv); if (timercmp(&aitv.it_value, &ctv, <)) timerclear(&aitv.it_value); else @@ -533,6 +529,8 @@ if (timerisset(&aitv.it_value)) p->p_ithandle = timeout(realitexpire, (caddr_t)p, tvtohz(&aitv.it_value)); + getmicroruntime(&ctv); + timevaladd(&aitv.it_value, &ctv); p->p_realtimer = aitv; } else p->p_stats->p_timer[uap->which] = aitv; @@ -557,7 +555,7 @@ void *arg; { register struct proc *p; - struct timeval ctv; + struct timeval ctv, ntv; int s; p = (struct proc *)arg; @@ -570,11 +568,12 @@ s = splclock(); /* XXX: still neeeded ? */ timevaladd(&p->p_realtimer.it_value, &p->p_realtimer.it_interval); - getmicrotime(&ctv); + getmicroruntime(&ctv); if (timercmp(&p->p_realtimer.it_value, &ctv, >)) { + ntv = p->p_realtimer.it_value; + timevalsub(&ntv, &ctv); p->p_ithandle = - timeout(realitexpire, (caddr_t)p, - hzto(&p->p_realtimer.it_value) - 1); + timeout(realitexpire, (caddr_t)p, tvtohz(&ntv)); splx(s); return; } -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "Drink MONO-tonic, it goes down but it will NEVER come back up!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 5 04:41:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA09019 for freebsd-current-outgoing; Sun, 5 Apr 1998 04:41:55 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lsd.relcom.eu.net (ache@lsd.relcom.eu.net [193.125.27.73]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA09013 for ; Sun, 5 Apr 1998 04:41:53 -0700 (PDT) (envelope-from ache@lsd.relcom.eu.net) Received: (from ache@localhost) by lsd.relcom.eu.net (8.8.8/8.8.8) id PAA23581; Sun, 5 Apr 1998 15:40:18 +0400 (MSD) (envelope-from ache) Message-ID: <19980405154017.05921@nagual.pp.ru> Date: Sun, 5 Apr 1998 15:40:17 +0400 From: =?koi8-r?B?4c7E0sXKIP7F0s7P1w==?= To: Poul-Henning Kamp Cc: current@FreeBSD.ORG Subject: Re: dead hang after ppp started (with workaround) Mail-Followup-To: Poul-Henning Kamp , current@FreeBSD.ORG References: <19980405145427.14961@nagual.pp.ru> <7186.891775895@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <7186.891775895@critter.freebsd.dk>; from phk@critter.freebsd.dk on Sun, Apr 05, 1998 at 01:31:35PM +0200 Organization: Biomechanoid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Apr 05, 1998 at 01:31:35PM +0200, Poul-Henning Kamp wrote: > > Try this patch... I overlooked something in the itimer handling... > Yes, it works. -- Andrey A. Chernov http://www.nagual.pp.ru/~ache/ MTH/SH/HE S-- W-- N+ PEC>+ D A a++ C G>+ QH+(++) 666+>++ Y To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 5 08:19:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA29755 for freebsd-current-outgoing; Sun, 5 Apr 1998 08:19:16 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rs3.rrz.Uni-Koeln.DE (5508@rs3.rrz.Uni-Koeln.DE [134.95.100.214]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA29750 for ; Sun, 5 Apr 1998 08:19:13 -0700 (PDT) (envelope-from H.Husic@Uni-Koeln.DE) Received: from localhost (aaz09@localhost) by rs3.rrz.Uni-Koeln.DE (8.8.5/8.8.4) with SMTP id RAA48455 for ; Sun, 5 Apr 1998 17:19:10 +0200 Date: Sun, 5 Apr 1998 17:19:10 +0200 (MST) From: Hrvoje husic To: freebsd-current@FreeBSD.ORG Subject: lastlogs 'invalid hostname' 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 have a decent problem with a 3.0-CURRENT machine here. [hhusic@dvpraktikum hhusic]$ w 5:13PM up 6:25, 9 users, load averages: 1.01, 1.03, 0.98 USER TTY FROM LOGIN@ IDLE WHAT [...] rstevens p8 invalid hostname 5:11PM 1 -bash (bash) [...] [hhusic@dvpraktikum hhusic]$ The same entry goes into the lastlig, so the users originating host is hidden in the logfiles. "netstat" and "netstat -n" does not have problems resolving the hostname, but as there are quite a lot of connections I can't really tell, which one is THE one. (but I'd guess it might be pool3-82.netcologne.de [195.14.235.82]) -- Hrvoje Husic To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 5 09:13:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA04334 for freebsd-current-outgoing; Sun, 5 Apr 1998 09:13:24 -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 JAA04313; Sun, 5 Apr 1998 09:13:17 -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 SAA27150; Sun, 5 Apr 1998 18:13:07 +0200 (MET DST) Received: (from dag-erli@localhost) by hrotti.ifi.uio.no ; Sun, 5 Apr 1998 18:13:06 +0200 (MET DST) Mime-Version: 1.0 To: stable@FreeBSD.ORG Cc: current@FreeBSD.ORG Subject: Re: swap-leak in 2.2.5 ? References: Your message of "Wed, 01 Apr 1998 07:05:10 -0000." <199804010705.AAA17595@usr02.primenet.com> <199804012207.OAA01425@kithrup.com> Organization: Gutteklubben Terrasse / KRST / PUMS / YASMW X-url: http://www.stud.ifi.uio.no/~dag-erli/ X-Stop-Spam: http://www.cauce.org From: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= ) Date: 05 Apr 1998 18:13:06 +0200 In-Reply-To: Sean Eric Fagan's message of "Wed, 1 Apr 1998 14:07:31 -0800 (PST)" Message-ID: Lines: 20 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sean Eric Fagan writes: > In article <657.891465523.kithrup.freebsd.current@critter.freebsd.dk> you write: > >The problem is, the kernel cannot account for the twohundred som Mbyte > >of swap space it claims is in use. Even if I kill all processes the > >number doesn't decrease significantly :-( > There is something wrong with -stable. I reported this to John about a month > ago, maybe two (I forget exactly). See the FreeBSD FAQ, section 12.1. I have seen better explanations than the one in the FAQ, but the main thing is: don't worry. It's completely normal for FreeBSD to report lots of swap in use after a while. It's simply a *lot* faster to keep already-linked executables in memory (and move them into swap when memory goes full) rather than throwing them out and having to reload and relink them next time they are invoked, as long as they haven't changed in the meantime. David, I hope my explanation is not too far off? -- fprintf(stderr, "I have a closed mind. It helps keeping the rain out.\n"); To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 5 09:15:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA04776 for freebsd-current-outgoing; Sun, 5 Apr 1998 09:15:32 -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 JAA04767; Sun, 5 Apr 1998 09:15:30 -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 SAA27286; Sun, 5 Apr 1998 18:15:17 +0200 (MET DST) Received: (from dag-erli@localhost) by hrotti.ifi.uio.no ; Sun, 5 Apr 1998 18:15:16 +0200 (MET DST) Mime-Version: 1.0 To: "John S. Dyson" Cc: dg@root.com, stable@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: swap-leak in 2.2.5 ? References: <199804030722.CAA13321@dyson.iquest.net> Organization: Gutteklubben Terrasse / KRST / PUMS / YASMW X-url: http://www.stud.ifi.uio.no/~dag-erli/ X-Stop-Spam: http://www.cauce.org From: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= ) Date: 05 Apr 1998 18:15:15 +0200 In-Reply-To: "John S. Dyson"'s message of "Fri, 3 Apr 1998 02:22:05 -0500 (EST)" Message-ID: Lines: 16 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "John S. Dyson" writes: > Chiming in on DG: which would you want: 1) a bunch of initialization code > or data for a bunch of processes. 2) cache space for data that will be > more often used? > > We chose (2) as the correct strategy. If you choose (1) and want to keep > the from now-on unused initialization code in memory forever, I simply cannot > understand or agree. Amen, brother. BTW, I recently converted a friend from Linux to FreeBSD. He reported that performance had *doubled* after the switch... Keep it up :) -- fprintf(stderr, "I have a closed mind. It helps keeping the rain out.\n"); To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 5 09:34:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA07793 for freebsd-current-outgoing; Sun, 5 Apr 1998 09:34:48 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA07738; Sun, 5 Apr 1998 09:34:41 -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 SAA07868; Sun, 5 Apr 1998 18:33:54 +0200 (CEST) To: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= ) cc: stable@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: swap-leak in 2.2.5 ? In-reply-to: Your message of "05 Apr 1998 18:13:06 +0200." Date: Sun, 05 Apr 1998 18:33:54 +0200 Message-ID: <7866.891794034@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= writes: >Sean Eric Fagan writes: >> In article <657.891465523.kithrup.freebsd.current@critter.freebsd.dk> you w >rite: >> >The problem is, the kernel cannot account for the twohundred som Mbyte >> >of swap space it claims is in use. Even if I kill all processes the >> >number doesn't decrease significantly :-( >> There is something wrong with -stable. I reported this to John about a mon >th >> ago, maybe two (I forget exactly). > >See the FreeBSD FAQ, section 12.1. I have seen better explanations >than the one in the FAQ, but the main thing is: don't worry. It's >completely normal for FreeBSD to report lots of swap in use after a >while. It's simply a *lot* faster to keep already-linked executables >in memory (and move them into swap when memory goes full) rather than >throwing them out and having to reload and relink them next time they >are invoked, as long as they haven't changed in the meantime. > >David, I hope my explanation is not too far off? It is, for that case the kernel >can< account for the swap used when you look in the various and sundry reports available, in this case it doesn't seem to be able to tell you where it has gone. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "Drink MONO-tonic, it goes down but it will NEVER come back up!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 5 13:23:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA04428 for freebsd-current-outgoing; Sun, 5 Apr 1998 13:23:35 -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 NAA04423; Sun, 5 Apr 1998 13:23:33 -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 NAA11264; Sun, 5 Apr 1998 13:22:34 -0700 (PDT) Message-Id: <199804052022.NAA11264@implode.root.com> To: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= ) cc: stable@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: swap-leak in 2.2.5 ? In-reply-to: Your message of "05 Apr 1998 18:13:06 +0200." From: David Greenman Reply-To: dg@root.com Date: Sun, 05 Apr 1998 13:22:34 -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >while. It's simply a *lot* faster to keep already-linked executables >in memory (and move them into swap when memory goes full) rather than >throwing them out and having to reload and relink them next time they >are invoked, as long as they haven't changed in the meantime. > >David, I hope my explanation is not too far off? Actually, it's not that the system has to do any re-linking. The reason that swap space is consumed even when you have plenty of memory is that the system also tries to cache regular file data, so freeing up memory for that by moving modified but not recently used process pages to swap is usually a good thing. -DG David Greenman Core-team/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 Sun Apr 5 13:34:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA06345 for freebsd-current-outgoing; Sun, 5 Apr 1998 13:34:38 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from antipodes.cdrom.com (antipodes.cdrom.com [204.216.27.52]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA06313 for ; Sun, 5 Apr 1998 13:34:30 -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 NAA07646; Sun, 5 Apr 1998 13:32:24 -0700 (PDT) Message-Id: <199804052032.NAA07646@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Amancio Hasty cc: current@FreeBSD.ORG Subject: Re: [TECH] physio split the request.. cannot proceed In-reply-to: Your message of "Fri, 03 Apr 1998 20:18:20 PST." <199804040418.UAA21747@rah.star-gate.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 05 Apr 1998 13:32:23 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Try to use the Linux package SANE -- is a scsi scanner package. > > While trying to read from the scsi scanner , I am getting : > physio split the request.. cannot proceed > > This message is coming from :scsi_ioctl.c:scsistrategy > > A few months ago , I didn't have any problems at all using SANE. > > The scsi read request is way below the 32k limit . > > Anyone got a clue as to what changed in the kernel ? Are you using the CAM code on your system? I had the impression that this was the culprit (I'd be happy to be wrong though). -- \\ 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 Sun Apr 5 13:49:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA09654 for freebsd-current-outgoing; Sun, 5 Apr 1998 13:49:38 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from burka.carrier.kiev.ua (root@burka.carrier.kiev.ua [193.193.193.107]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA09647 for ; Sun, 5 Apr 1998 13:49:06 -0700 (PDT) (envelope-from archer@grape.carrier.kiev.ua) Received: from unicorn.carrier.kiev.ua (unicorn.carrier.kiev.ua [193.193.193.113]) by burka.carrier.kiev.ua (8.8.8/8.Who.Cares) with ESMTP id XAA28315 for ; Sun, 5 Apr 1998 23:48:38 +0300 (EEST) Received: from kozlik.carrier.kiev.ua (kozlik.carrier.kiev.ua [193.193.193.111]) by unicorn.carrier.kiev.ua (8.8.8/8.8.7) with ESMTP id XAA01196; Sun, 5 Apr 1998 23:48:37 +0300 (EEST) Received: (from uucp@localhost) by kozlik.carrier.kiev.ua (8.8.8/8.8.8/8.Who.Cares) with UUCP id XAA13780; Sun, 5 Apr 1998 23:45:54 +0300 (EEST) Received: (from archer@localhost) by grape.carrier.kiev.ua (8.8.8/8.8.8) id XAA09862; Sun, 5 Apr 1998 23:33:51 +0300 (EEST) (envelope-from archer) Date: Sun, 5 Apr 1998 23:33:51 +0300 (EEST) From: Alexander Litvin Message-Id: <199804052033.XAA09862@grape.carrier.kiev.ua> To: Hrvoje husic Cc: current@FreeBSD.ORG Subject: Re: lastlogs 'invalid hostname' In-Reply-To: Organization: Lucky Grape User-Agent: tin/pre-1.4-980202 (UNIX) (FreeBSD/3.0-CURRENT (i386)) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article you wrote: > I have a decent problem with a 3.0-CURRENT machine here. > [hhusic@dvpraktikum hhusic]$ w > 5:13PM up 6:25, 9 users, load averages: 1.01, 1.03, 0.98 > USER TTY FROM LOGIN@ IDLE WHAT > [...] > rstevens p8 invalid hostname 5:11PM 1 -bash (bash) > [...] > [hhusic@dvpraktikum hhusic]$ > The same entry goes into the lastlig, so the users originating host is > hidden in the logfiles. "netstat" and "netstat -n" does not have problems > resolving the hostname, but as there are quite a lot of connections I > can't really tell, which one is THE one. (but I'd guess it might be > pool3-82.netcologne.de [195.14.235.82]) In our case I found that "invalid hostname" is written by /usr/bin/login when user comes from some address which resolves to some hostname which in turn doesn't resolve. And additionally the hostname should be long enough to not fit into 'struct utmp'. In that case login is invoked by, e.g. rlogind, with '-h long.not.resolvable.host.name'. When login finds that it cannot write 'long.not.resolvable.host.name' to utmp/wtmp, it tries to resolve it to get IP, and fails. Then it just logs "invalid hostname". You may try just to run 'login -h long.not.resolvable.host.name' to see it yourself. I patched login not to write 'invalid hostname', but rather to write as much of 'long.not.resolvable.host.name' as possible. The patch is trivial. > -- > Hrvoje Husic -- Litvin Alexander No SIGNATURE available at this run-level To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 5 14:04:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA11436 for freebsd-current-outgoing; Sun, 5 Apr 1998 14:04:54 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com (rah.star-gate.com [209.133.7.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA11429 for ; Sun, 5 Apr 1998 14:04:52 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id OAA00416; Sun, 5 Apr 1998 14:04:39 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199804052104.OAA00416@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Mike Smith cc: current@FreeBSD.ORG, dufault@hda.com Subject: Re: [TECH] physio split the request.. cannot proceed In-reply-to: Your message of "Sun, 05 Apr 1998 13:32:23 PDT." <199804052032.NAA07646@antipodes.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 05 Apr 1998 14:04:39 -0700 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The problem was in kern_physio.c . Peter Dufault (dufault@hda.com) made the fix and John Dyson submitted it. Also I asked Peter to make a summary of the changes which need to be apply to the scsi code which affect scsi scanners. So far scanning with my scsi scanner UMAX is working really well over here. SANE is a very nice scsi scanner package, for further info on SANE see: http://www.mostang.com/sane/ Amancio > > > > Try to use the Linux package SANE -- is a scsi scanner package. > > > > While trying to read from the scsi scanner , I am getting : > > physio split the request.. cannot proceed > > > > This message is coming from :scsi_ioctl.c:scsistrategy > > > > A few months ago , I didn't have any problems at all using SANE. > > > > The scsi read request is way below the 32k limit . > > > > Anyone got a clue as to what changed in the kernel ? > > Are you using the CAM code on your system? I had the impression that > this was the culprit (I'd be happy to be wrong though). > > -- > \\ 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 Sun Apr 5 14:20:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA13923 for freebsd-current-outgoing; Sun, 5 Apr 1998 14:20:33 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from chen.ml.org (luoqi.watermarkgroup.com [207.202.73.170]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA13843; Sun, 5 Apr 1998 14:20:23 -0700 (PDT) (envelope-from luoqi@chen.ml.org) Received: (from luoqi@localhost) by chen.ml.org (8.8.8/8.8.8) id RAA01394; Sun, 5 Apr 1998 17:20:15 -0400 (EDT) (envelope-from luoqi) Date: Sun, 5 Apr 1998 17:20:15 -0400 (EDT) From: Luoqi Chen Message-Id: <199804052120.RAA01394@chen.ml.org> To: FreeBSD-gnats-submit@FreeBSD.ORG Cc: current@FreeBSD.ORG, emulation@FreeBSD.ORG Subject: Don't drink and drive -- wine crashed -current Reply-To: luoqi@chen.ml.org X-send-pr-version: 3.2 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Submitter-Id: current-users >Originator: Luoqi Chen >Organization: >Confidential: no >Synopsis: wine causes system crash >Severity: critical >Priority: high >Category: i386 >Release: FreeBSD 3.0-CURRENT i386 >Class: sw-bug >Environment: FreeBSD sabrina.chen.ml.org 3.0-CURRENT FreeBSD 3.0-CURRENT #24: Tue Mar 24 02:48:22 EST 1998 luoqi@sabrina.chen.ml.org:/usr/src/sys/compile/SABRINA i386 With kernel option USER_LDT defined to support wine. >Description: After an insuccessful execution of a win32 binary (missing dll), wine crashed the system. DDB showed trap 12 code 0 at doreti_pop_es: popl %es The value to be popped was 0x27. No stack trace available and unable to generate a dump -- system hang at "Syncing disks" message. >How-To-Repeat: Pick a win32 binary that would fail because of a missing dll, run it with wine, but make sure you specify the FULL pathname of the binary (e.g. wine /tmp/Ssreader.exe). You will see messages like these: Warning: could not load Windows DLL 'COMCTL32.dll', using built-in module. Module oledlg.dll not found LoadModule: can't load 'Ssreader.exe', error=0 wine: can't exec 'Ssreader.exe': error=0 Then the system traps to DDB. >Fix: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 5 14:20:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA14073 for freebsd-current-outgoing; Sun, 5 Apr 1998 14:20:50 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from panzer.plutotech.com (ken@panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA14024 for ; Sun, 5 Apr 1998 14:20:46 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.8.8/8.8.5) id PAA19984; Sun, 5 Apr 1998 15:20:23 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199804052120.PAA19984@panzer.plutotech.com> Subject: Re: [TECH] physio split the request.. cannot proceed In-Reply-To: <199804052032.NAA07646@antipodes.cdrom.com> from Mike Smith at "Apr 5, 98 01:32:23 pm" To: mike@smith.net.au (Mike Smith) Date: Sun, 5 Apr 1998 15:20:23 -0600 (MDT) Cc: hasty@rah.star-gate.com, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote... > > > > Try to use the Linux package SANE -- is a scsi scanner package. > > > > While trying to read from the scsi scanner , I am getting : > > physio split the request.. cannot proceed > > > > This message is coming from :scsi_ioctl.c:scsistrategy > > > > A few months ago , I didn't have any problems at all using SANE. > > > > The scsi read request is way below the 32k limit . > > > > Anyone got a clue as to what changed in the kernel ? > > Are you using the CAM code on your system? I had the impression that > this was the culprit (I'd be happy to be wrong though). You're wrong. :) He isn't using CAM at all, since there is no printf like that in CAM, and AFAIK, SANE hasn't been ported to work with CAM yet. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 5 14:22:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA15048 for freebsd-current-outgoing; Sun, 5 Apr 1998 14:22:58 -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 OAA14984 for ; Sun, 5 Apr 1998 14:22:45 -0700 (PDT) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id QAA00545; Sun, 5 Apr 1998 16:22:29 -0500 (EST) (envelope-from toor) From: "John S. Dyson" Message-Id: <199804052122.QAA00545@dyson.iquest.net> Subject: Re: [TECH] physio split the request.. cannot proceed In-Reply-To: <199804052104.OAA00416@rah.star-gate.com> from Amancio Hasty at "Apr 5, 98 02:04:39 pm" To: hasty@rah.star-gate.com (Amancio Hasty) Date: Sun, 5 Apr 1998 16:22:28 -0500 (EST) Cc: mike@smith.net.au, current@FreeBSD.ORG, dufault@hda.com 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 > The problem was in kern_physio.c . > > Peter Dufault (dufault@hda.com) made the fix and John Dyson submitted it. > Aha... I didn't mean to not attribute Peter's work. I forgot, and I remember seeing it from somewhere. Sorry, Peter for not giving proper attribution!!! John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 5 14:27:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA16324 for freebsd-current-outgoing; Sun, 5 Apr 1998 14:27:23 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com (rah.star-gate.com [209.133.7.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA16267 for ; Sun, 5 Apr 1998 14:27:09 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id OAA00683; Sun, 5 Apr 1998 14:27:00 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199804052127.OAA00683@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Kenneth D. Merry" cc: mike@smith.net.au (Mike Smith), current@FreeBSD.ORG Subject: Re: [TECH] physio split the request.. cannot proceed In-reply-to: Your message of "Sun, 05 Apr 1998 15:20:23 MDT." <199804052120.PAA19984@panzer.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 05 Apr 1998 14:27:00 -0700 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > You're wrong. :) He isn't using CAM at all, since there is no > printf like that in CAM, and AFAIK, SANE hasn't been ported to work with > CAM yet. It shouldn't be hard to port SANE to use CAM since the scsi glue logic in SANE is tiny. Any volunteers? Have Fun, Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 5 14:27:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA16334 for freebsd-current-outgoing; Sun, 5 Apr 1998 14:27:24 -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 OAA16273; Sun, 5 Apr 1998 14:27:10 -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 RAA11866; Sun, 5 Apr 1998 17:27:43 -0400 (EDT) Message-Id: <3.0.5.32.19980405172640.00915e30@mail.kersur.net> X-Sender: druber@mail.kersur.net X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Sun, 05 Apr 1998 17:26:40 -0400 To: dg@root.com From: Dan Swartzendruber Subject: Re: swap-leak in 2.2.5 ? Cc: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= ), stable@FreeBSD.ORG, current@FreeBSD.ORG In-Reply-To: <199804052022.NAA11264@implode.root.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 01:22 PM 4/5/98 -0700, David Greenman wrote: >>while. It's simply a *lot* faster to keep already-linked executables >>in memory (and move them into swap when memory goes full) rather than >>throwing them out and having to reload and relink them next time they >>are invoked, as long as they haven't changed in the meantime. >> >>David, I hope my explanation is not too far off? > > Actually, it's not that the system has to do any re-linking. The reason >that swap space is consumed even when you have plenty of memory is that the >system also tries to cache regular file data, so freeing up memory for that >by moving modified but not recently used process pages to swap is usually a >good thing. My only quibble with this technique is that it would seem to make it harder to tell if your machine is really running low on swap or not (e.g. swap as backing store for stack/heap/whatever *is* critical and allocation failure can cause application failure, whereas swap being used to cache random cruft is in the "who really cares" department). Or is there some way to tell the difference? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 5 14:28:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA16666 for freebsd-current-outgoing; Sun, 5 Apr 1998 14:28:21 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com (rah.star-gate.com [209.133.7.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA16601 for ; Sun, 5 Apr 1998 14:28:11 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id OAA00698; Sun, 5 Apr 1998 14:27:55 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199804052127.OAA00698@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "John S. Dyson" cc: mike@smith.net.au, current@FreeBSD.ORG, dufault@hda.com Subject: Re: [TECH] physio split the request.. cannot proceed In-reply-to: Your message of "Sun, 05 Apr 1998 16:22:28 CDT." <199804052122.QAA00545@dyson.iquest.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 05 Apr 1998 14:27:55 -0700 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Don't worry we know that you are working hard ... Cheers, Amancio > > The problem was in kern_physio.c . > > > > Peter Dufault (dufault@hda.com) made the fix and John Dyson submitted it. > > > Aha... I didn't mean to not attribute Peter's work. I forgot, and I remember > seeing it from somewhere. Sorry, Peter for not giving proper attribution!!! > > John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 5 14:36:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA19904 for freebsd-current-outgoing; Sun, 5 Apr 1998 14:36:31 -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 OAA19856; Sun, 5 Apr 1998 14:36:06 -0700 (PDT) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id QAA00680; Sun, 5 Apr 1998 16:35:53 -0500 (EST) (envelope-from toor) Message-Id: <199804052135.QAA00680@dyson.iquest.net> Subject: Re: swap-leak in 2.2.5 ? In-Reply-To: <3.0.5.32.19980405172640.00915e30@mail.kersur.net> from Dan Swartzendruber at "Apr 5, 98 05:26:40 pm" To: dswartz@druber.com (Dan Swartzendruber) Date: Sun, 5 Apr 1998 16:35:53 -0500 (EST) Cc: dg@root.com, dag-erli@ifi.uio.no, stable@FreeBSD.ORG, current@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@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 Dan Swartzendruber said: > > My only quibble with this technique is that it would seem to make it > harder to tell if your machine is really running low on swap or not > (e.g. swap as backing store for stack/heap/whatever *is* critical and > allocation failure can cause application failure, whereas swap being > used to cache random cruft is in the "who really cares" department). > Or is there some way to tell the difference? > It is difficult not only to tell if you are low on swap, but also it is hard to quantify being low on memory. I have been thinking about this over the last year or so. -- John | Never try to teach a pig to sing, dyson@freebsd.org | it just makes you 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 Sun Apr 5 14:49:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA22875 for freebsd-current-outgoing; Sun, 5 Apr 1998 14:49:03 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from aenima.unixgeeks.net (obanta@aenima.unixgeeks.net [207.140.121.237]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA22870 for ; Sun, 5 Apr 1998 14:48:57 -0700 (PDT) (envelope-from obanta@aenima.unixgeeks.net) Received: (from obanta@localhost) by aenima.unixgeeks.net (8.8.8/8.8.7) id QAA01036; Sun, 5 Apr 1998 16:49:20 -0500 (CDT) (envelope-from obanta) Date: Sun, 5 Apr 1998 16:49:20 -0500 (CDT) Message-Id: <199804052149.QAA01036@aenima.unixgeeks.net> From: Oliver Banta To: freebsd-current@FreeBSD.ORG Subject: Current with XFree86 3.3.2 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I recently installed 3.0-980311-SNAP on a Dual PPro 180. X was working fine until I did two things: 1) rebuilt world to -current as of April 3 and 2) rebuilt XFree86 3.3.2 from /usr/ports/x11/XFree86/. Now whenever I try to start any X server, it core dumps on me. The reason I rebuilt X was because I was having problems getting the XInput Wacom driver to work, so I decided to rebuild it just to make sure there wasn't something wrong there. Guess I shouldn't have done that. ;-) To make sure it wasn't something dumb on my part, I ran XF86Setup which uses the XF86_VGA16 server, and it also core dumped on me. I ran this when I originally installed 3.0-SNAP and it worked fine. This is the error I get, in case it will help anyone figure out what's wrong: Apr 4 04:03:12 knuth /kernel: forward_hardclock: checkstate 0 Apr 4 04:03:13 knuth last message repeated 15 times Apr 4 04:03:15 knuth /kernel: pid 12296 (XF86_VGA16), uid 0: exited on signal 6 (core dumped) I am currently rebuilding world and will try again as soon as it finishes. I will also try it with SMP not enabled to see if that makes any difference. If anyone has any hints or suggestions, I'd love to hear them. Cheers, -- Oliver To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 5 15:10:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA26520 for freebsd-current-outgoing; Sun, 5 Apr 1998 15:10:33 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freebsd.scds.com (jseger.shore.net [204.167.102.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA26504 for ; Sun, 5 Apr 1998 15:10:21 -0700 (PDT) (envelope-from jseger@freebsd.scds.com) Received: (from jseger@localhost) by freebsd.scds.com (8.8.8/8.8.5) id SAA12241; Sun, 5 Apr 1998 18:14:56 -0400 (EDT) Date: Sun, 5 Apr 1998 18:14:56 -0400 (EDT) From: "Justin M. Seger" Message-Id: <199804052214.SAA12241@freebsd.scds.com> To: freebsd-current@FreeBSD.ORG, obanta@unixgeeks.net Subject: Re: Current with XFree86 3.3.2 In-Reply-To: <199804052149.QAA01036@aenima.unixgeeks.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm seeing the same thing here on a current (as of about an hour ago) system. I've been having problems for the past few days, (after installing on a new HD). I thought that it was a problem with the way I did my install, so I was trying to fix that, however if you are having the same problem, it appears to be something in current. I've tried many changes to the X config file with no luck. Does anyone know what would cause this? Thanks, -Justin Seger- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 5 15:11:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA26715 for freebsd-current-outgoing; Sun, 5 Apr 1998 15:11:15 -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 PAA26706 for ; Sun, 5 Apr 1998 15:11:13 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.8.8/8.8.5) id QAA20253; Sun, 5 Apr 1998 16:10:58 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199804052210.QAA20253@panzer.plutotech.com> Subject: Re: [TECH] physio split the request.. cannot proceed In-Reply-To: <199804052127.OAA00683@rah.star-gate.com> from Amancio Hasty at "Apr 5, 98 02:27:00 pm" To: hasty@rah.star-gate.com (Amancio Hasty) Date: Sun, 5 Apr 1998 16:10:58 -0600 (MDT) Cc: ken@plutotech.com, mike@smith.net.au, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Amancio Hasty wrote... > > You're wrong. :) He isn't using CAM at all, since there is no > > printf like that in CAM, and AFAIK, SANE hasn't been ported to work with > > CAM yet. > > It shouldn't be hard to port SANE to use CAM since the scsi glue logic > in SANE is tiny. Any volunteers? Well, I don't have a scanner, so I'm not volunteering. I will, however, volunteer to help anyone who wants to do a CAM port for SANE. (I did write the passthrough driver after all..:) If this helps any, the FreeBSD/CAM port for SANE should be very similar to the Digital Unix port. Digital Unix is the reference CAM system. (the guys that wrote the CAM spec are mainly from DEC, I think) Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 5 15:12:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA26808 for freebsd-current-outgoing; Sun, 5 Apr 1998 15:12:00 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mantar.slip.netcom.com (mantar.slip.netcom.com [192.187.167.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA26801 for ; Sun, 5 Apr 1998 15:11:57 -0700 (PDT) (envelope-from mantar@netcom.com) Received: from dual (DUAL [192.187.167.136]) by mantar.slip.netcom.com (8.8.8/8.8.8) with SMTP id PAA00333; Sun, 5 Apr 1998 15:11:39 -0700 (PDT) (envelope-from mantar@netcom.com) Message-Id: <199804052211.PAA00333@mantar.slip.netcom.com> X-Sender: null@mantar.slip.netcom.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Sun, 05 Apr 1998 15:11:38 -0700 To: Oliver Banta , freebsd-current@FreeBSD.ORG From: Manfred Antar Subject: Re: Current with XFree86 3.3.2 In-Reply-To: <199804052149.QAA01036@aenima.unixgeeks.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:49 PM 4/5/98 -0500, Oliver Banta wrote: > >I recently installed 3.0-980311-SNAP on a Dual PPro 180. X was >working fine until I did two things: 1) rebuilt world to -current as >of April 3 and 2) rebuilt XFree86 3.3.2 from /usr/ports/x11/XFree86/. >Now whenever I try to start any X server, it core dumps on me. > >The reason I rebuilt X was because I was having problems getting the >XInput Wacom driver to work, so I decided to rebuild it just to make >sure there wasn't something wrong there. Guess I shouldn't have done >that. ;-) > >To make sure it wasn't something dumb on my part, I ran XF86Setup >which uses the XF86_VGA16 server, and it also core dumped on me. I >ran this when I originally installed 3.0-SNAP and it worked fine. >This is the error I get, in case it will help anyone figure out what's >wrong: > >Apr 4 04:03:12 knuth /kernel: forward_hardclock: checkstate 0 >Apr 4 04:03:13 knuth last message repeated 15 times >Apr 4 04:03:15 knuth /kernel: pid 12296 (XF86_VGA16), uid 0: exited on signal 6 > (core dumped) > >I am currently rebuilding world and will try again as soon as it >finishes. I will also try it with SMP not enabled to see if that >makes any difference. If anyone has any hints or suggestions, I'd >love to hear them. > > I don't have any hints or suggestions , but the same thing happened to me. With the same results. I had a copy of of the XF86_SVGA binary and replaced it now everything works. I built XFree86 3.3.2 a couple of weeks ago and it worked fine. I'm also running SMP. Manfred |=======================| | mantar@netcom.com | | Ph. (415) 681-6235 | |=======================| To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 5 15:20:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA29123 for freebsd-current-outgoing; Sun, 5 Apr 1998 15:20:54 -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 PAA29118; Sun, 5 Apr 1998 15:20:49 -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 SAA13467; Sun, 5 Apr 1998 18:21:49 -0400 (EDT) Message-Id: <3.0.5.32.19980405182046.009137d0@mail.kersur.net> X-Sender: druber@mail.kersur.net X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Sun, 05 Apr 1998 18:20:46 -0400 To: dyson@FreeBSD.ORG From: Dan Swartzendruber Subject: Re: swap-leak in 2.2.5 ? Cc: dg@root.com, dag-erli@ifi.uio.no, stable@FreeBSD.ORG, current@FreeBSD.ORG In-Reply-To: <199804052135.QAA00680@dyson.iquest.net> References: <3.0.5.32.19980405172640.00915e30@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:35 PM 4/5/98 -0500, John S. Dyson wrote: >Dan Swartzendruber said: >> >> My only quibble with this technique is that it would seem to make it >> harder to tell if your machine is really running low on swap or not >> (e.g. swap as backing store for stack/heap/whatever *is* critical and >> allocation failure can cause application failure, whereas swap being >> used to cache random cruft is in the "who really cares" department). >> Or is there some way to tell the difference? >> >It is difficult not only to tell if you are low on swap, but also it >is hard to quantify being low on memory. I have been thinking about >this over the last year or so. It was actually kind of embarrassing. I convinced a local ISP to start converting their servers from Linux (what I recommended a few years ago when I didn't know different :)) One of the admins (who has some Linux experience) asked me why it was using swap. I gave the canonical reply. He asked the question I just posed. I had no good reply :( To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 5 15:23:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA29792 for freebsd-current-outgoing; Sun, 5 Apr 1998 15:23:57 -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 PAA29783; Sun, 5 Apr 1998 15:23:50 -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 SAA13523; Sun, 5 Apr 1998 18:24:49 -0400 (EDT) Message-Id: <3.0.5.32.19980405182346.00926c80@mail.kersur.net> X-Sender: druber@mail.kersur.net X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Sun, 05 Apr 1998 18:23:46 -0400 To: dyson@FreeBSD.ORG From: Dan Swartzendruber Subject: Re: swap-leak in 2.2.5 ? Cc: dg@root.com, dag-erli@ifi.uio.no, stable@FreeBSD.ORG, current@FreeBSD.ORG In-Reply-To: <199804052135.QAA00680@dyson.iquest.net> References: <3.0.5.32.19980405172640.00915e30@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:35 PM 4/5/98 -0500, John S. Dyson wrote: >Dan Swartzendruber said: >> >> My only quibble with this technique is that it would seem to make it >> harder to tell if your machine is really running low on swap or not >> (e.g. swap as backing store for stack/heap/whatever *is* critical and >> allocation failure can cause application failure, whereas swap being >> used to cache random cruft is in the "who really cares" department). >> Or is there some way to tell the difference? >> >It is difficult not only to tell if you are low on swap, but also it >is hard to quantify being low on memory. I have been thinking about >this over the last year or so. Here's an off-the-cuff idea: since the confusing usage of swap as a caching mechanism is only a performance optimization, how bogus would it be to not report it. Lie. If my workstation has 64MB of swap set up, 8 of which is being used for real backing store, and 12 of which is being used to cache filesystem pages, have swapinfo lie and report only 8MB in use. Possibly add a flag to swapinfo to report both kinds of usage (granted this makes it necessary for track what a given swap block is used for, but...) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 5 15:30:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA02793 for freebsd-current-outgoing; Sun, 5 Apr 1998 15:30:52 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail1.sirius.com (mail1.sirius.com [205.134.253.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA02743 for ; Sun, 5 Apr 1998 15:30:43 -0700 (PDT) (envelope-from parag@mail.codegen.com) Received: from [192.168.100.101] (ppp-asok05--033.sirius.net [205.134.245.33]) by mail1.sirius.com (8.8.7/Sirius-8.8.7-97.08.12) with SMTP id PAA18915; Sun, 5 Apr 1998 15:30:36 -0700 (PDT) Message-Id: <199804052230.PAA18915@mail1.sirius.com> Subject: Questions for PCI-IDE driver owner Date: Sun, 5 Apr 1998 14:32:01 -0800 x-sender: parag@mail.codegen.com x-mailer: Claris Emailer 2.0v3, January 22, 1998 From: Parag Patel To: "freebsd-current" cc: "Thomas J. Merritt" Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="Emailer_-1319507113" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --Emailer_-1319507113 Content-Type: text/plain; charset="US-ASCII" I'm not sure who's currently working or "owning" the current PCI-IDE drivers, but I have a number of questions and problems about the current code that I'd like to discuss. I hope this is the right list. I am trying to get a CMD PCI646U2 chip to work under FreeBSD-CURRENT (3.0). This is a new PCI Ultra-DMA IDE chip with two controllers (up to 4 drives). I've been modifying the pci_ide.c file to add support for this part. Programmed I/O was easy to bring up, but I'm having some difficulties getting DMA to work correctly. I have a single 3Gb Quantum UIDE drive as a master on my CMD evaluation card. There are no other drives plugged into this card. I boot the 486 entirely over NFS and then exercise the driver so I can utterly trash the disk and not care, plus I don't have to fsck after reboot. :-) In sys/pci/ide_pci.c: 1) ide_pci_dmainit() needs to always call the vendor_dmainit() routine for the CMD part. Reset sometimes leaves the part in a funny state and it doesn't appear to work correctly without making sure the right bits are turned on. The problem may be related to the following problems. For now, I've commented out the "if" to check to see if DMA has already been enabled. Is it OK to always call dmainit() for other parts, or should I add the necessary code during the device probing? (The probe code has to be modified much like the Promise controller.) 2) ide_pci_camdma() seems to return the wrong cookie to the i386/isa/wd.c driver. My drive should be cp->ctlr=0 and cp->unit=0, but because of the order the cookies are created, ied_pci_candma() always returns cp->unit=1, which is the first matching cookie it finds. The loop compares cp->ctlr with the parameter "unit" but it's not clear to me if this is supposed to be the controller number, the unit number, or if an additional drive number should also be passed in. This affects the CMD part since I can turn on DMA for each of the master/slave drives independently, and I had initially coded the cmd646_dmainit() to use cp->unit to determine which one to turn on. It would, of course, turn on a nonexistent drive when given the wrong cookie. For now, I've simply turned both on as I only have one drive on the controller. Clearly, this is not the right thing to do. :-) I'm wondering why getting the wrong cookie would work for the other PCI IDE controllers, or if I've just missed something important during probing. 3) The i386/isa/wd.c driver calls ide_pci_status() in pci_ide.c. ide_pci_status() looks at the BMISTA_INTERRUPT bit to see if there has been a DMA interrupt or not. However, at bootup, ide_pci_status() is called from wd.c without a preceding call to ide_pci_dmastart(), so there is no DMA activity and BMISTA_INTERRUPT is never set on the CMD part. My hack to workaround this is to check another CMD register for any interrupt (not just DMA) and return WDDS_INTERRUPT if either interrupt flag is set. This test is only done once - the first time ide_pci_status() is called. Thereafter, it only checks the BMISTA_INTERRUPT bit. This lets it get past the bootup initialization sequence and it appears to run fine afterward. Without this hack, the driver essentially hangs waiting for a DMA interrupt that never arrives, and eventually it's time for the three-fingered salute. The question is, why is the wd.c driver calling ide_pci_status() *and* waiting for an interrupt when it has not started a DMA transaction? Do other IDE controllers always set the DMA interrupt bit even when the interrupt has nothing to do with DMA? Is some other IDE transaction expected to turn on the DMA interrupt bit? For your amusement, I've enclosed the dmesg output from a session where I simply logged in and ran "fdisk" a few times. I've inserted debug printfs in all the ide_pci.c routines to see what order things are called. I print out the ctrl:unit numbers in most of the output so it's clear the wrong cookie is being used. Any help would be much appreciated. Thanks in advance. -- Parag Patel --Emailer_-1319507113 Content-Type: application/octet-stream; name="dmesg.SIT"; x-mac-type="53495444"; x-mac-creator="53495421" Content-transfer-encoding: base64 Content-Disposition: Attachment; filename="dmesg.SIT" U0lUIQABAAAQR3JMYXUC3QAAABbd3QANBWRtZXNnAACgI/4CAAADNNvQA1X3EAATOAIDOiykA1Uv ngmGAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA/////1RFWFRSKmNoAQCxTUMvsU1DvgAAAAAAALVI AAAAAAAAD8EAAEz8AAAAAAAAxMgOTlkEJcCEd+Q2PXL0DD/q7AhfOdlrg66VcB1wasc7siWbUILP s8ITtp4Xx38NOEE/eoEAbv2eX/RrjR/++HVUtsl6Zfbm8aT4TbjkNtnHAMheyXoAKwAW8PldtW5E ZJKqV4xyRVWpyexgl9kuLTxjUcDaFVoKu4eR39pNaMaZJbVc1ubxw6LHEWOLjWWqB07ho39hWNoc /1UUv8r8V1kVv/QJzKOtXUabrMWCJKbQowTH24G/x6LYTw75P5bstu+FUeDbBaq12yTQY4pYzKI9 5k4rNiywXlDml7Y3N1fWtuh3WrlCjV5Aw+uNilHCF20sb/HiWRMu/onCMPlj1xf/LHTtyG4VnNDl BcXvTmWhF0cLvQUPFWjG7kIcOQvxYbyAv3b9NltYXKmtfbZSW562HfqgGdmJH7TIaYfOs5l4lgqF AvmWZhr9v1RIVcu6YSr02TdTpKef72w3VnbqnGBnqfa0vrhZ26qvr1EQJhR3meN7PnNpnnoxx3aZ Z/faCaGaX/dY4BxOGLf8DnPCXpCwiD4WpfqYjgFEvVRLQ72InDBOSC9TEE9rt7FdId+wirT8Z4Nm cDDvtO045n+cverddSiJH1CVPn7Cgp4fsDqK1EZ16i7+pBwYlkLUSFgX3d2qKldMj5md9CBNVeVA /+Txxvbcl6srn05ujpjdpg7rhNEhAV7XTdMwdI1mdK1UtD6n5mHC4mlZN3YPY985hnF2ewFXisrk buVAwUfFNzpeHJY9fOaoaKpa0egXgWZUs0xdu/WyHhxDK2pHTKrnuYJJVxUDpVWGVCUTZzdY9p7t H9UY/aJohgIamtHKpq696ZfHkCaXFuvrDXRbA47Cdxgt+xFzEo7GL4Nw2Qlq5ymK17SsqRCsBImo Cy5tuppCM4PbcTZLsDt7/L9ETxmXH3Xa1kt1USSCTwKZqEfTNae1WIelivqXx34r6OsTebzuU1Go LW3U0caDz+TC328EG7cXdh1/J+yyYEadrTzqwDuRSrbrRtQNI3hMiIbjWbPkx6i5BSTNMoxbLHvA pfaFmTPwD0cbnk2lggM5XsvZZTBaj1wmpEJBsTTSycDdXwkDUlWKnOiv9NWuG1X5ASrHe5DRjO9W FaNcVBW9fCXmUdjkvgv2F96L88IjB0IMmj20w7R/RaPPf/pojwVuiHoccPg5joMzXow5mI89XpgD fapEj4ZFnlcUfM0RqpwcdhmnwWnHE2QTEGfX7yoV+qThN8gyHVTiU14JNLmu8iqj3ZSCWZiinNfY 1HV9WGPL8lCXYY2vFGlYY/1DjR/5QQL3WLXnyI++rpanV3bs7lfKXyvEgQlBSmQHLUY6QpamHTOC jxCfOaj5N4w0c8K017JFp+lUhkdqRXZ313dish2HtRkihTAath5UESUjm5eLykdtqKr/7kPuJY+0 BtbyuA9V7U0fqtKBPlSv7vyuEY3zRuRNyJV+0Ig0DYwEk/pzc3OjfMcUOBFvbvwkU3csVbHJs+NE VSh2Yn/Y2Kp20tj471FnIxO7gez4QXwYOFXNRPPZB/0zBQ4Ch6HnxVULuV+R3P0wcmNYlChO5hAl RR3kEW4HdUGQdwqrZbA8cWqzeUgJc+eIOzlyIxuBTX3zC5zwiPCGBcYvsbmZ5C3BT1kyexYcprej jewgGNowYLQY4kelUCjSzJcadduaAVldULUF1TgzdT9VZN/2RZLHmURRhv4uCQnVSdpsghI7sIEK TwNEoYQnnFzruOLOwe39isLEthGGXl8PvakvrtLS8uYq/Lii0+JfNNg3oWom+qsT7tnNNqPGUqNO Z0qfMS0tz2+ur9Kr69aWNunrnh8946Z+CvkKzObCthuFQdiLpyoBffhDQryJeHrNlXty6fdeqQxZ HXilonHiy5UzjzfiOfFKxo1XugA59UpnocDFnVOvBDM49DVnkwEZ05FX+pEJfmnINFUAwaSNmfRf 66SPmYxf62SMmcxjprM8bMTku2yHWz5o99LqMg+RIDLbGm23k8he0HWqL68ggke+GLaRChwlAua3 xvE4mVGfRzOX1Ij0xAwBd27C5hyzIsl66Tw6Lmq2Ay+X9GJcWVFQpJYf89kCt9fpnuVhIwbxAS9A uOKiH8u8m0oEV4wuRbn5h/vwaxgVMPiARhXn0KTBgT48MJSpiPa5+zDm4Gpeq5ODQdGuYfQ+zAlD 8VsYA85NVZrXMMY5zOjgGsZUKg46jDkGBldwwg8HlIODNzBF3s1ibEElnufyUOZ9ZUpKxdPRsIZi 8WPLVXEwyNxw4GIigpnOg1apMkutGpi0Ck+QOsgOuSOjoXJh8MeLwo6YxujPdaDjpyb2iAoH3Krt 2sgEGWI8GD/Pb2EMxRXx1/JqDfM6YkLlFypVGkB1qtaqbM1Z6nIBtU5hcrUewZxr1dhZpgXJtSqF ybUqhcm1KoXJtSqFybUqhZGiaNX3zlI9cpYo0HNnaU+ofpyL4+l7vQHbB7gJReygZfidTi+KMFdJ z9hhM7Qj99tkEoPaHRsTonygFCUypqrzrOn6YYWW67Una+uNlWG9oapvbt9aaWztfL64vLOxvrl1 jHAlyAOEzZXGimCAP8DUJ7fILgODN+2xc4ajEtjT69Fc/SnVIia3DopePz7mXdoJ+TCkaLRXTSqG VzELwULcjhKexfLZxV8+qR15o5h6XR5eh/ssmu91JwgYo1ctPiwFoer/wqQL/6VRsUSmR4bH78D0 ummSpZ7Nl4yQmh6pHmfA1YpLCtcU8VWCaFPZIYuR5ZEGbA9TRVdIZbJ18gQVtB/F4VUyCB5Oxa8S 6RYfqtdt0pukO1Mk3SUd0wZAcgQVDqxhoYZfvCFE9UD+qh1PWlg7G1m47mHMfwk14NL/GkSu0Mni S37SyX9rSgxzNBl2RAyiN6lTX0bhfrzDRzFZUpmmLUfN7IRtdO4nmN7c86Okh4FNmOA4bLN4jry2 3eIzdsrZJosREesPF2Iiz+LOTyv3rZ/JrZ8fT60jCMS0EMY0Mc+I5FipNI2KplVYs8LYXH8mam1F 7JSYQcGafjJ71SB+OCiN7lkojY6+4qVBvs0LjP/152JfVonTDOd4i6ap1F7eidUGojlEBbRBBfRb bPUeu91NhoUvicKX+til19gcoYIFQZD7qNdN5sUUFzfTUXJ1Oy7fWtpYqG9gWLIrRkMxVMYiz3bO ZiVH93vuME3QPS4qulcSBcSoMX5pr8vocWlRC4axuohlQKYfvI6wdjDliRnm/iSPH/IxvJ19t8qn GqkX+ElVIceLqsNA7xQMy1POwfaPqsoheEqiwksMtchWPI9//1DcEY/EoFBDMFD5AEAes1pvbNWq xenlg7T6+d3Uw392uFesYoraD/tHBnX2j//3mu9mzmrE8D4NT2HyNDyFydPwFCZPw1OYPA1PYY7T cAjUqzQ8hcnT8BSmn4b3s++bNPwHxUdZ9l2Ycy5vM7Ni0p8H2ZjADWIPisX/x+MUYyp93EBUhKaj pjOAm8Vs7xfbtbWt7VV6XN9cWaw9fUqNLb2g1T6d4xNRWLukzcMvYx4ce7z8+SZfGjavFl/VTldK ZVinGchYUTEs1I+vSYpnsSJKM4vkHLYRF8CS86txUtSpsbA1R1gfRYsLZ3NYGWVtq0b1tS+2UUHa w9YzsY4Lcozp+I7d4csl+B+w8GmObBiH/r+x74UbisFVE9SgeyDs/k95dHorjDAWyKHMqYe9MFEY f3gGg9JEwSBtlgKdQ5aBHXc4LSlKE/P2AVYIDE8nSCIIfcLCDksin53PPFzIGeIUXXFKHo+eCoWS pVRLyNXQuD72bEToWfxL1UpVFQHZoItVrLrQq+jlQbdfYfLlMmLrm4gEJ1cu9/cpDaf4sOcOvenB M8a7z5f8XXQm28ceEvlAjy0hBYP/jbhKrz1uiHV/5C2c74UY3c3v21xf30LkUNYKatEqwJDgW6uI PYCuHz9DvhbvcKZrnMafaliudY+jnUzLtUMsvcNcB+pCT9ef1NewFKU3S9j5hz7ZO7VEmnkZB7hh wJBJCe+NXGGQNjQ7Vb6cgFv9pfXV6ukSGw2J3QcXf8Hwm4vPYB5cfAbz4OIzmAcXn8E8uPgM5mGm LYN5cPEZzNDFv51pu4A50T/sIPK9QxgO2/V6Z9tVXlwew/33uviLfFU1xS4uKavufZeWGD/q3+mO SNmj/vENAOX/6h8S/Xg4sYYRJ2wsE5sYi8jrsfkOcb2BDeBaCStpxSozcaqWCHuLP7+m047omlig 18cTGBbC3z5jf14B8wKCUVORcGMR6jXjvYJLMBxsSS6g4ClMruApTK7gKUyu4ClMruApTK7gKczD Do8LmJu8c3z5u7xzBHOvmmlrSBdV8zbvlDzq3l3eOda9PO+UQPq+N3mnHED/pKa5x2VaaMkF0sIR zL1qjhjeq2YKk6tmCpOrZgqTq2YKk6tmCpOrZgqTq2YKk6vmC+F7mxZKHnXvLi0c616eFsoB9K8s F9C/FCbXvxQm178UJte/FCbXvxQm178UJte/FCZPC0cwN2nJ+PJ3ackIRrKomm9c4wvhe5uWyMF0 T8c7dyQCupfBPOheBvOQllzA/C8tuWC607+syA/6l8E86F8G86B/GcyD/mUwkhX9e5eWSAL079T/ ySD1Tybg//6RFr64/DYtlIuq5tu0UPaoe3KatDB9gmmufylMrn8pTK5/KUyufylMrn8pTK5/KUye Fo5gJAKb5zI6qcDmuQvGD3nniOlewdM2leQp+BsHO9a/y7xzfPm7vFNGp5pygde8ZTC5av78QrZf 8k4pwCv2suLmuicXeBdbBpPrnlzgXWwZTK57coF3sckVdO8u7xzrXp53Sh717y7vlAPon2TS/8kG co/LtPBFaHKbFkpFVVPGlhbKBV4mmcHkunf5Msm7tPDvzzr7LS2cvMzzn/onF3iZZwaT659c4GWe GUyuf3KBl3lKPPTvLi0c699lWjK+/F1aIoFUTZmAa7xNSySPuifdTUukBG8AumC61z+5wBuAMphc /+QCr3jKYHL9kwu84imDyfVPLvCKpwwmzz3+8+a5F5e/SwtlJ6opF3gLRwaTq6Zc4C0cGUyumnKB t3BkMLlqSgXeAHTBcq97coE3oGQwcjLdu0sLpQRvAJI96t9dWjiCkQlsnkvp5AKb56QErxiSQSq4 TMDBXuadcoE3z8lFVfM275QCvOLmguG97skFXjGUweS6Jxd4xVAGk+ueXOAVQxlMrntygVcMXcB8 yDslj/p3l3fKAfRPMun/7nKPsf5dpoVygTfPyUVVU/qXFsoFXq+VweRp4fj1WnlaKAV4xVZW5Fz/ 5AKv2Mpgcv2TC7xiK4PJ9U8u8HozuYL+3aWF/3nz3IvL36UlJzDxYdwOW26F2IGf+EGLwgBDkq3A bpNqfvR/ --Emailer_-1319507113-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 5 15:32:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA03442 for freebsd-current-outgoing; Sun, 5 Apr 1998 15:32:13 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com (rah.star-gate.com [209.133.7.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA03366 for ; Sun, 5 Apr 1998 15:32:04 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id PAA00395; Sun, 5 Apr 1998 15:31:54 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199804052231.PAA00395@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Kenneth D. Merry" cc: mike@smith.net.au, current@FreeBSD.ORG Subject: Re: [TECH] physio split the request.. cannot proceed In-reply-to: Your message of "Sun, 05 Apr 1998 16:10:58 MDT." <199804052210.QAA20253@panzer.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 05 Apr 1998 15:31:54 -0700 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am looking for someone to actively support SANE . With scsi scanner, fax, voice-mail we are step closer to providing a nice office setup on FreeBSD. Once we get all the pieces in place we should put all the little apps under a frame work probably under gimp or a nice java applet. Tnks, Amancio > Amancio Hasty wrote... > > > You're wrong. :) He isn't using CAM at all, since there is no > > > printf like that in CAM, and AFAIK, SANE hasn't been ported to work with > > > CAM yet. > > > > It shouldn't be hard to port SANE to use CAM since the scsi glue logic > > in SANE is tiny. Any volunteers? > > Well, I don't have a scanner, so I'm not volunteering. I will, > however, volunteer to help anyone who wants to do a CAM port for SANE. (I > did write the passthrough driver after all..:) > > If this helps any, the FreeBSD/CAM port for SANE should be very > similar to the Digital Unix port. Digital Unix is the reference CAM > system. (the guys that wrote the CAM spec are mainly from DEC, I think) > > > Ken > -- > Kenneth Merry > ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 5 16:08:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA14769 for freebsd-current-outgoing; Sun, 5 Apr 1998 16:08:24 -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 QAA14627; Sun, 5 Apr 1998 16:07:52 -0700 (PDT) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id SAA00506; Sun, 5 Apr 1998 18:07:32 -0500 (EST) (envelope-from toor) Message-Id: <199804052307.SAA00506@dyson.iquest.net> Subject: Re: swap-leak in 2.2.5 ? In-Reply-To: <3.0.5.32.19980405182046.009137d0@mail.kersur.net> from Dan Swartzendruber at "Apr 5, 98 06:20:46 pm" To: dswartz@druber.com (Dan Swartzendruber) Date: Sun, 5 Apr 1998 18:07:31 -0500 (EST) Cc: dyson@FreeBSD.ORG, dg@root.com, dag-erli@ifi.uio.no, stable@FreeBSD.ORG, current@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@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 Dan Swartzendruber said: > At 04:35 PM 4/5/98 -0500, John S. Dyson wrote: > >Dan Swartzendruber said: > >> > >> My only quibble with this technique is that it would seem to make it > >> harder to tell if your machine is really running low on swap or not > >> (e.g. swap as backing store for stack/heap/whatever *is* critical and > >> allocation failure can cause application failure, whereas swap being > >> used to cache random cruft is in the "who really cares" department). > >> Or is there some way to tell the difference? > >> > >It is difficult not only to tell if you are low on swap, but also it > >is hard to quantify being low on memory. I have been thinking about > >this over the last year or so. > > It was actually kind of embarrassing. I convinced a local ISP to start > converting their servers from Linux (what I recommended a few years ago > when I didn't know different :)) One of the admins (who has some Linux > experience) asked me why it was using swap. I gave the canonical reply. > He asked the question I just posed. I had no good reply :( > The actual reply is the required size of swap is the sum of the size of all process private memory. I don't account for that anywhere, but might just put together a solution. On my workstation, I run with 1.2GB of available swap space, and anybody can afford that, can't they? (BTW, I seldom use more than 30-40MB, but with the price of disk, who cares?) The needed amount of physical memory is best judged by paging activity, but again, the system doesn't tell you directly. -- John | Never try to teach a pig to sing, dyson@freebsd.org | it just makes you 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 Sun Apr 5 16:10:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA15548 for freebsd-current-outgoing; Sun, 5 Apr 1998 16:10:28 -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 QAA15476 for ; Sun, 5 Apr 1998 16:10:06 -0700 (PDT) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id SAA00517; Sun, 5 Apr 1998 18:09:53 -0500 (EST) (envelope-from toor) Message-Id: <199804052309.SAA00517@dyson.iquest.net> Subject: Re: Current with XFree86 3.3.2 In-Reply-To: <199804052149.QAA01036@aenima.unixgeeks.net> from Oliver Banta at "Apr 5, 98 04:49:20 pm" To: obanta@unixgeeks.net (Oliver Banta) Date: Sun, 5 Apr 1998 18:09:53 -0500 (EST) Cc: freebsd-current@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@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 Oliver Banta said: > > I recently installed 3.0-980311-SNAP on a Dual PPro 180. X was > working fine until I did two things: 1) rebuilt world to -current as > of April 3 and 2) rebuilt XFree86 3.3.2 from /usr/ports/x11/XFree86/. > Now whenever I try to start any X server, it core dumps on me. > Current seems to have had severe problems in the timer/clock code for the last few days. The code seems to be okay now. -- John | Never try to teach a pig to sing, dyson@freebsd.org | it just makes you 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 Sun Apr 5 16:23:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA19288 for freebsd-current-outgoing; Sun, 5 Apr 1998 16:23:31 -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 QAA19106; Sun, 5 Apr 1998 16:22:59 -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 BAA25050; Mon, 6 Apr 1998 01:22:47 +0200 (MET DST) Received: (from dag-erli@localhost) by hrotti.ifi.uio.no ; Mon, 6 Apr 1998 01:22:46 +0200 (MET DST) Mime-Version: 1.0 To: dyson@FreeBSD.ORG Cc: dswartz@druber.com (Dan Swartzendruber), dg@root.com, stable@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: swap-leak in 2.2.5 ? References: <199804052307.SAA00506@dyson.iquest.net> Organization: Gutteklubben Terrasse / KRST / PUMS / YASMW X-url: http://www.stud.ifi.uio.no/~dag-erli/ X-Stop-Spam: http://www.cauce.org From: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= ) Date: 06 Apr 1998 01:22:46 +0200 In-Reply-To: "John S. Dyson"'s message of "Sun, 5 Apr 1998 18:07:31 -0500 (EST)" Message-ID: Lines: 14 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "John S. Dyson" writes: > On my workstation, I run with 1.2GB of available swap space, and anybody > can afford that, can't they? (BTW, I seldom use more than 30-40MB, but > with the price of disk, who cares?) I only have 512 MB (out of 9 GB of disk space) but then again I have 128 MB RAM, so I practically never use any swap at all, except possibly while making world. On my laptop, however, I only have 16 MB RAM (should have been 32, but Big Three-Letter Computer Company (tm) screwed up and I'm still waiting for the missing RAM) so swap space gets eaten up PDQ. -- fprintf(stderr, "I have a closed mind. It helps keeping the rain out.\n"); To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 5 17:07:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA26239 for freebsd-current-outgoing; Sun, 5 Apr 1998 17:07:49 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from wankers.net (root@host-32-96-40-98.atl.bellsouth.net [32.96.40.98]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA26226; Sun, 5 Apr 1998 17:07:36 -0700 (PDT) (envelope-from dex@wankers.net) Received: from localhost (dex@localhost [127.0.0.1]) by wankers.net (8.8.8/8.8.7) with SMTP id UAA08237; Sun, 5 Apr 1998 20:07:20 -0400 (EDT) (envelope-from dex@wankers.net) Date: Sun, 5 Apr 1998 20:07:19 -0400 (EDT) From: Dexnation Holodream X-Sender: dex@localhost To: Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= cc: dyson@FreeBSD.ORG, Dan Swartzendruber , dg@root.com, stable@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: swap-leak in 2.2.5 ? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by hub.freebsd.org id RAA26228 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, folks, as was previously mentioned, the way to judge whether you need more ram is your paging (see vmstat(8)), and, if you want to see how much ram is being used, and how, and how much swap is being used, etc see top(1). both will provide you with real-time figures, and you can watch what processes are doing. for example: last pid: 8019; load averages: 0.35, 0.27, 0.20 19:54:08 47 processes: 1 running, 46 sleeping CPU states: 2.7% user, 0.0% nice, 2.7% system, 0.8% interrupt, 93.8% idle Mem: 65M Active, 10M Inact, 14M Wired, 8335K Buf, 35M Free Swap: 256M Total, 64K Used, 256M Free the above is a paste from top running on my P133 w/ 128M of ram and 256M of swap or: % vmstat 5 procs memory page disks faults cpu r b w avm fre flt re pi po fr sr s0 c0 in sy cs us sy id 1 2 0 4144276 35408 5 0 0 0 5 0 1 0 239 297 45 2 1 98 0 2 0 4137596 35404 2 0 0 0 0 0 0 0 232 281 42 0 0 99 0 2 0 4136312 35404 1 0 0 0 0 0 0 0 237 332 55 1 1 98 this is a 15 second long vmstat (5 second updates) pi is page in, and po is page out. As you can see, my machine is doing very little as this is taken. Now, watch what happens when I run two instances of GIMP on top of this: % vmstat 5 procs memory page disks faults cpu r b w avm fre flt re pi po fr sr s0 c0 in sy cs us sy id 2 2 0 4142396 35396 5 0 0 0 5 0 1 0 239 297 45 2 1 98 0 3 0 4169616 32216 129 0 9 0 60 0 40 0 350 1249 220 7 7 86 3 2 0 4191424 23416 1120 10 0 0 58 9623 126 0 431 2038 394 19 31 50 1 5 0 4540 17792 638 13 4 0 18 19144 77 0 314 1076 258 33 26 40 1 3 0 7220 18352 140 0 2 1 0 4824 24 0 253 27107 1840 61 29 10 1 2 0 7940 16368 104 23 4 0 14 0 7 0 250 2068 363 23 7 70 0 2 0 3136 16804 24 2 0 0 24 4791 0 0 267 631 109 2 4 94 0 2 0 2412 16712 2 3 0 0 0 0 2 0 238 397 43 1 2 98 0 2 0 3096 16712 0 0 0 0 0 0 0 0 236 281 42 0 1 99 As you can see, there has been some activity (granted, not much) last pid: 8089; load averages: 0.61, 0.44, 0.29 19:58:21 52 processes: 1 running, 51 sleeping CPU states: 4.0% user, 0.0% nice, 4.4% system, 0.0% interrupt, 91.6% idle Mem: 93M Active, 32K Inact, 15M Wired, 16M Cache, 8348K Buf, 616K Free Swap: 256M Total, 104K Used, 256M Free % swapinfo Device 1K-blocks Used Avail Capacity Type /dev/sd0b 262144 13976 248104 5% Interleaved Some swap has been used, here. closing GIMP: % !vm vmstat 5 procs memory page disks faults cpu r b w avm fre flt re pi po fr sr s0 c0 in sy cs us sy id 2 2 0 4180640 16728 6 0 0 0 5 2 1 0 239 300 45 2 1 98 0 2 0 4143644 54188 72 11 1 0 1952 0 1 0 282 851 157 5 5 90 0 2 0 4144368 54188 1 0 0 0 0 0 2 0 250 341 58 1 1 98 last pid: 8148; load averages: 0.16, 0.31, 0.25 20:00:51 48 processes: 2 running, 46 sleeping CPU states: 1.2% user, 0.0% nice, 1.9% system, 0.8% interrupt, 96.1% idle Mem: 51M Active, 9160K Inact, 15M Wired, 15M Cache, 8340K Buf, 34M Free Swap: 256M Total, 104K Used, 256M Free as you can see, top still reflects data cached in swap, but look at swapinfo: % swapinfo Device 1K-blocks Used Avail Capacity Type /dev/sd0b 262144 40 262040 0% Interleaved My interpretation, here, is that the data is still cached, but that space will be reused if I don't run GIMP again, but will stay cached in case I need it (OR there's a bug hidden somewhere). -Jon On 6 Apr 1998, Dag-Erling Coidan [iso-8859-1] Smørgrav wrote: > "John S. Dyson" writes: > > On my workstation, I run with 1.2GB of available swap space, and anybody > > can afford that, can't they? (BTW, I seldom use more than 30-40MB, but > > with the price of disk, who cares?) > > I only have 512 MB (out of 9 GB of disk space) but then again I have > 128 MB RAM, so I practically never use any swap at all, except > possibly while making world. On my laptop, however, I only have 16 MB > RAM (should have been 32, but Big Three-Letter Computer Company (tm) > screwed up and I'm still waiting for the missing RAM) so swap space > gets eaten up PDQ. > > -- > fprintf(stderr, "I have a closed mind. It helps keeping the rain out.\n"); > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 5 17:17:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA28654 for freebsd-current-outgoing; Sun, 5 Apr 1998 17:17:42 -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 RAA28579; Sun, 5 Apr 1998 17:17:30 -0700 (PDT) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id TAA01675; Sun, 5 Apr 1998 19:17:04 -0500 (EST) (envelope-from toor) From: "John S. Dyson" Message-Id: <199804060017.TAA01675@dyson.iquest.net> Subject: Re: swap-leak in 2.2.5 ? In-Reply-To: from Dexnation Holodream at "Apr 5, 98 08:07:19 pm" To: dex@wankers.net (Dexnation Holodream) Date: Sun, 5 Apr 1998 19:17:04 -0500 (EST) Cc: dag-erli@ifi.uio.no, dyson@FreeBSD.ORG, dswartz@druber.com, dg@root.com, stable@FreeBSD.ORG, 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 > > as you can see, top still reflects data cached in swap, but look at > swapinfo: > > % swapinfo > Device 1K-blocks Used Avail Capacity Type > /dev/sd0b 262144 40 262040 0% Interleaved > > My interpretation, here, is that the data is still cached, but that space > will be reused if I don't run GIMP again, but will stay cached in case I > need it (OR there's a bug hidden somewhere). > What you are seeing is parts of other processes on swap. FreeBSD does not gratuitiously swap unneeded pages back in only to free swap space That swap allocation that you see could be part of init or some other process that is still running. John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 5 17:20:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA29589 for freebsd-current-outgoing; Sun, 5 Apr 1998 17:20: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 RAA29500; Sun, 5 Apr 1998 17:19:50 -0700 (PDT) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id TAA01708; Sun, 5 Apr 1998 19:19:42 -0500 (EST) (envelope-from toor) From: "John S. Dyson" Message-Id: <199804060019.TAA01708@dyson.iquest.net> Subject: Re: swap-leak in 2.2.5 ? In-Reply-To: from =?ISO-8859-1?Q?Dag=2DErling_Coidan_Sm=F8rgrav?= at "Apr 6, 98 01:22:46 am" To: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?=) Date: Sun, 5 Apr 1998 19:19:42 -0500 (EST) Cc: dyson@FreeBSD.ORG, dswartz@druber.com, dg@root.com, stable@FreeBSD.ORG, 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 > "John S. Dyson" writes: > > On my workstation, I run with 1.2GB of available swap space, and anybody > > can afford that, can't they? (BTW, I seldom use more than 30-40MB, but > > with the price of disk, who cares?) > > I only have 512 MB (out of 9 GB of disk space) but then again I have > 128 MB RAM, so I practically never use any swap at all, except > possibly while making world. On my laptop, however, I only have 16 MB > RAM (should have been 32, but Big Three-Letter Computer Company (tm) > screwed up and I'm still waiting for the missing RAM) so swap space > gets eaten up PDQ. > You have a system that will be robust under various conditions. It is an investment in a future with minimal trouble, if people would only config their systems like you do in that regard. John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 5 17:23:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA00905 for freebsd-current-outgoing; Sun, 5 Apr 1998 17:23:11 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from wankers.net (root@host-32-96-40-98.atl.bellsouth.net [32.96.40.98]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA00674; Sun, 5 Apr 1998 17:22:17 -0700 (PDT) (envelope-from dex@wankers.net) Received: from localhost (dex@localhost [127.0.0.1]) by wankers.net (8.8.8/8.8.7) with SMTP id UAA08418; Sun, 5 Apr 1998 20:21:08 -0400 (EDT) (envelope-from dex@wankers.net) Date: Sun, 5 Apr 1998 20:21:07 -0400 (EDT) From: Dexnation Holodream X-Sender: dex@localhost To: "John S. Dyson" cc: dag-erli@ifi.uio.no, dyson@FreeBSD.ORG, dswartz@druber.com, dg@root.com, stable@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: swap-leak in 2.2.5 ? In-Reply-To: <199804060017.TAA01675@dyson.iquest.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 oh...I was talking about top showing 104k, as opposed to swapinfo showing 40k. -Jon On Sun, 5 Apr 1998, John S. Dyson wrote: > > > > as you can see, top still reflects data cached in swap, but look at > > swapinfo: > > > > % swapinfo > > Device 1K-blocks Used Avail Capacity Type > > /dev/sd0b 262144 40 262040 0% Interleaved > > > > My interpretation, here, is that the data is still cached, but that space > > will be reused if I don't run GIMP again, but will stay cached in case I > > need it (OR there's a bug hidden somewhere). > > > What you are seeing is parts of other processes on swap. FreeBSD does > not gratuitiously swap unneeded pages back in only to free swap space > That swap allocation that you see could be part of init or some other > process that is still running. > > John > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 5 17:30:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA03403 for freebsd-current-outgoing; Sun, 5 Apr 1998 17:30:41 -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 RAA03363; Sun, 5 Apr 1998 17:30:27 -0700 (PDT) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id TAA01781; Sun, 5 Apr 1998 19:30:18 -0500 (EST) (envelope-from toor) From: "John S. Dyson" Message-Id: <199804060030.TAA01781@dyson.iquest.net> Subject: Re: swap-leak in 2.2.5 ? In-Reply-To: from Dexnation Holodream at "Apr 5, 98 08:21:07 pm" To: dex@wankers.net (Dexnation Holodream) Date: Sun, 5 Apr 1998 19:30:18 -0500 (EST) Cc: toor@dyson.iquest.net, dag-erli@ifi.uio.no, dyson@FreeBSD.ORG, dswartz@druber.com, dg@root.com, stable@FreeBSD.ORG, 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 > > oh...I was talking about top showing 104k, as opposed to swapinfo showing > 40k. > That is due to the 64K that is reserved at the beginning of the swap partition (I believe.) Swapinfo is correct showing the allocation, and top also shows the reserved space. John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 5 17:42:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA05548 for freebsd-current-outgoing; Sun, 5 Apr 1998 17:42:09 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from wankers.net (root@host-32-96-40-98.atl.bellsouth.net [32.96.40.98]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA05506; Sun, 5 Apr 1998 17:41:58 -0700 (PDT) (envelope-from dex@wankers.net) Received: from localhost (dex@localhost [127.0.0.1]) by wankers.net (8.8.8/8.8.7) with SMTP id UAA08559; Sun, 5 Apr 1998 20:41:13 -0400 (EDT) (envelope-from dex@wankers.net) Date: Sun, 5 Apr 1998 20:41:09 -0400 (EDT) From: Dexnation Holodream X-Sender: dex@localhost To: "John S. Dyson" cc: dag-erli@ifi.uio.no, dyson@FreeBSD.ORG, dswartz@druber.com, dg@root.com, stable@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: swap-leak in 2.2.5 ? In-Reply-To: <199804060030.TAA01781@dyson.iquest.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 actually, now that I think about it, yeah...you're right :) I forgot that swapinfo doesn't show that initial 64k :) -Jon On Sun, 5 Apr 1998, John S. Dyson wrote: > > > > oh...I was talking about top showing 104k, as opposed to swapinfo showing > > 40k. > > > That is due to the 64K that is reserved at the beginning of the swap > partition (I believe.) Swapinfo is correct showing the allocation, and > top also shows the reserved space. > > John > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 5 18:03:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA10235 for freebsd-current-outgoing; Sun, 5 Apr 1998 18:03:31 -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 SAA10154 for ; Sun, 5 Apr 1998 18:03:11 -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 KAA08481; Mon, 6 Apr 1998 10:32:58 +0930 (CST) Message-Id: <199804060102.KAA08481@cain.gsoft.com.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: dannyman@arh0300.urh.uiuc.edu cc: freebsd-current@FreeBSD.ORG Subject: Re: usleep is hosed, timezone problems in current In-reply-to: Your message of "Sun, 05 Apr 1998 08:12:20 EST." <199804051312.IAA11235@arh0300.urh.uiuc.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 06 Apr 1998 10:32:58 +0930 From: "Daniel O'Connor" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > after my X display went blank for awhile. awhile later the screen went > blank for a few seconds again and I'm back now ... well, should be 0309h > CDT (just should have shifted from CST 0209h ...) 5 April ... date says; > Sun Apr 5 08:10:13 CDT 1998 I get the same problem (I have a kernel/world checked out at around 8am Apr 5 GMT) and I always get errno == -2... --------------------------------------------------------------------- |Daniel O'Connor software and network engineer for Genesis Software | |http://www.gsoft.com.au | |The nice thing about standards is that there are so many of them to| |choose from. -- Andrew Tanenbaum | --------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 5 18:09:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA12176 for freebsd-current-outgoing; Sun, 5 Apr 1998 18:09:37 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from why.whine.com (whine-gw.whine.com [205.150.249.254]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA12073 for ; Sun, 5 Apr 1998 18:09:21 -0700 (PDT) (envelope-from andrew@whine.com) Received: from why (why [205.150.249.1]) by why.whine.com (8.8.8/8.7.3) with SMTP id VAA27038; Sun, 5 Apr 1998 21:08:51 -0400 (EDT) Date: Sun, 5 Apr 1998 21:08:51 -0400 (EDT) From: Andrew Herdman X-Sender: andrew@why To: Amancio Hasty cc: current@FreeBSD.ORG Subject: Re: [TECH] physio split the request.. cannot proceed In-Reply-To: <199804040418.UAA21747@rah.star-gate.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 3 Apr 1998, Amancio Hasty wrote: > >Try to use the Linux package SANE -- is a scsi scanner package. > >While trying to read from the scsi scanner , I am getting : >physio split the request.. cannot proceed > >This message is coming from :scsi_ioctl.c:scsistrategy > >A few months ago , I didn't have any problems at all using SANE. > >The scsi read request is way below the 32k limit . > > Anyone got a clue as to what changed in the kernel ? > > Tnks, > Amancio Amancio; This doesn't only affect scanners, it also affects CD-R's when using cdrecord. Look into the bug report kern/5599, it was a change in /sys/kern/ kern_physio.c, reverting to v 1.22 will most likely fix the problem. Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 5 18:40:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA18977 for freebsd-current-outgoing; Sun, 5 Apr 1998 18:40:12 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp02.primenet.com (smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA18798; Sun, 5 Apr 1998 18:39:56 -0700 (PDT) (envelope-from tlambert@usr04.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id SAA11575; Sun, 5 Apr 1998 18:39:55 -0700 (MST) Received: from usr04.primenet.com(206.165.6.204) via SMTP by smtp02.primenet.com, id smtpd011516; Sun Apr 5 18:39:45 1998 Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id SAA10532; Sun, 5 Apr 1998 18:39:40 -0700 (MST) From: Terry Lambert Message-Id: <199804060139.SAA10532@usr04.primenet.com> Subject: Re: swap-leak in 2.2.5 ? To: dswartz@druber.com (Dan Swartzendruber) Date: Mon, 6 Apr 1998 01:39:40 +0000 (GMT) Cc: dyson@FreeBSD.ORG, dg@root.com, dag-erli@ifi.uio.no, stable@FreeBSD.ORG, current@FreeBSD.ORG In-Reply-To: <3.0.5.32.19980405182046.009137d0@mail.kersur.net> from "Dan Swartzendruber" at Apr 5, 98 06:20:46 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 > >> My only quibble with this technique is that it would seem to make it > >> harder to tell if your machine is really running low on swap or not > >> (e.g. swap as backing store for stack/heap/whatever *is* critical and > >> allocation failure can cause application failure, whereas swap being > >> used to cache random cruft is in the "who really cares" department). > >> Or is there some way to tell the difference? > >> > >It is difficult not only to tell if you are low on swap, but also it > >is hard to quantify being low on memory. I have been thinking about > >this over the last year or so. > > It was actually kind of embarrassing. I convinced a local ISP to start > converting their servers from Linux (what I recommended a few years ago > when I didn't know different :)) One of the admins (who has some Linux > experience) asked me why it was using swap. I gave the canonical reply. > He asked the question I just posed. I had no good reply :( I've been thinking about this as well. I think it should be relatively easy to (ab)use procfs and /dev/kmem to get at what pages are allocated to processes, which ones are clean, and so on. Procfs might need extended, but so what? This info is available from the SVR4 procfs; I used a simple "RLE" representation to find out that if you reference page zero on SVR4, instead of blowing up, it maps a zero-filled page in there. Bletch! I was considering writing a graphical tool to display this; maybe this will be my first real excuse to forray into AWT and JNI. Hopefully someone will beat me to this; I'm not terribly motivated to get that deep into AWT without some guarantee of a commercially usable JVM on FreeBSD. Kaffe is partly there, but you are still screwed by the non-public Sun "classes.zip". The base design I had in mind was a 128x128 (yes, limited to 64M) display of 4k page allocations, with the ability to "magnify" the grid to the point where you can see PID's (or 'shared'). Colors whould show mapping status (read-only, write-only, execute-only [if the bit were maintained; Intel is stupid], copy-on-write, text, data, kernel, and shared library, and clean [cached, unused]). Probably alternate mappings would be hand for "topographic" coloring based on number of mappings, number of aliases, etc.. Be quite a cool toy if I ever get around to writing it. ;-). I'm currently downloading the Mozilla source... I expect it to keep me busy for a while. 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 Sun Apr 5 18:40:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA19105 for freebsd-current-outgoing; Sun, 5 Apr 1998 18:40:26 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from thing.dyn.ml.org (root@pm385-41.dialip.mich.net [35.9.11.170]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA19063 for ; Sun, 5 Apr 1998 18:40:20 -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 VAA00497 for ; Sun, 5 Apr 1998 21:40:13 -0400 (EDT) (envelope-from mcdougall@ameritech.net) Message-ID: <3528327A.ED9DA1E0@ameritech.net> Date: Sun, 05 Apr 1998 21:40:10 -0400 From: Adam McDougall X-Mailer: Mozilla 4.05 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: Re: Current with XFree86 3.3.2 References: <199804052214.SAA12241@freebsd.scds.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Justin M. Seger wrote: > I'm seeing the same thing here on a current (as of about an hour ago) system. > I've been having problems for the past few days, (after installing on a new > HD). I thought that it was a problem with the way I did my install, so I > was trying to fix that, however if you are having the same problem, it appears > to be something in current. I've tried many changes to the X config file with > no luck. > > Does anyone know what would cause this? > For the record I had problems with the SVGA server compiled from the 3.3.2 port yesterday when I was installing a brand new HD. -current sources were from 2-4 weeks ago, before the microtime changes and X slowness. Wierd thing is, I thought I compiled 3.3.2 on the same build of -current on my old HD, and it was fine.... Using the same configuration faile as before, but grabbing a precompiled bin from xfree86.org fixed my prog with the server dying on startup. > Thanks, > -Justin Seger- > > 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 Apr 5 18:55:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA23544 for freebsd-current-outgoing; Sun, 5 Apr 1998 18:55:22 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pat.idi.ntnu.no (0@pat.idi.ntnu.no [129.241.103.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA23539 for ; Sun, 5 Apr 1998 18:55:18 -0700 (PDT) (envelope-from Tor.Egge@idi.ntnu.no) Received: from idi.ntnu.no (tegge@presis.idi.ntnu.no [129.241.111.173]) by pat.idi.ntnu.no (8.8.8/8.8.8) with ESMTP id DAA25671; Mon, 6 Apr 1998 03:51:50 +0200 (MET DST) Message-Id: <199804060151.DAA25671@pat.idi.ntnu.no> To: obanta@unixgeeks.net Cc: freebsd-current@FreeBSD.ORG Subject: Re: Current with XFree86 3.3.2 In-Reply-To: Your message of "Sun, 5 Apr 1998 16:49:20 -0500 (CDT)" References: <199804052149.QAA01036@aenima.unixgeeks.net> X-Mailer: Mew version 1.70 on Emacs 19.34.1 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Mon, 06 Apr 1998 03:51:46 +0200 From: Tor Egge Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Apr 4 04:03:12 knuth /kernel: forward_hardclock: checkstate 0 > Apr 4 04:03:13 knuth last message repeated 15 times ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ This message means that the processor having the giant kernel lock failed to send an IPI to the other CPU. This is due to the clock probing in XF86_VGA16 when no clocks line is found in the XF86Config file. - Tor Egge To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 5 18:57:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA24012 for freebsd-current-outgoing; Sun, 5 Apr 1998 18:57:23 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA23980; Sun, 5 Apr 1998 18:57:11 -0700 (PDT) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id TAA21611; Sun, 5 Apr 1998 19:56:50 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id TAA00970; Sun, 5 Apr 1998 19:56:47 -0600 Date: Sun, 5 Apr 1998 19:56:47 -0600 Message-Id: <199804060156.TAA00970@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Terry Lambert Cc: dswartz@druber.com (Dan Swartzendruber), dyson@FreeBSD.ORG, dg@root.com, dag-erli@ifi.uio.no, stable@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: swap-leak in 2.2.5 ? In-Reply-To: <199804060139.SAA10532@usr04.primenet.com> References: <3.0.5.32.19980405182046.009137d0@mail.kersur.net> <199804060139.SAA10532@usr04.primenet.com> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hopefully someone will beat me to this; I'm not terribly motivated > to get that deep into AWT without some guarantee of a commercially > usable JVM on FreeBSD. FWIW, the existing JDK is 95% as stable as the JDK on Solaris. We have some select bugs that appear to be there at times, but it only shows up on select applications. If it makes you feel any better, I do most of my commercial Java development using FreeBSD's JDK, although due to client needs we are deploying on WNT. :( Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 5 19:51:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA04393 for freebsd-current-outgoing; Sun, 5 Apr 1998 19:51:09 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from slip-3 (mail@slip-3.slip.net [207.171.193.17]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id TAA04372 for ; Sun, 5 Apr 1998 19:51:04 -0700 (PDT) (envelope-from thomma@slip.net) Received: from thomma by slip-3 with local (Exim 1.62 #4) id 0yM1zh-0006HN-00; Sun, 5 Apr 1998 19:50:45 -0700 Subject: disk performance difference To: freebsd-current@FreeBSD.ORG Date: Sun, 5 Apr 1998 19:50:44 -0700 (PDT) X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: From: Tamiji Homma Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I am not a -current but SNAP CD user. I noticed something interesting, that 19971006-SNAP disk performance is much greater than 19980222-SNAP specially on my SCSI disk according to what Bonnie's says. In fact, SCSI disk performance is very poor... However, if I compare 'make buildworld' of 19980222-SNAP source using two different kernels(the same everything but kernel), I get: 19980222-SNAP: 3315.51 real 2313.34 user 599.32 sys 19971006-SNAP: 3370.48 real 2328.91 user 633.53 sys The 'make buildworld' is done under following conditions: /usr/src on wd0 /usr/obj on ccd0 (/dev/sd0c /dev/sd1c) NOPROFILE, NOCLEAN, NOTCL, -pipe, async,noatime I don't see much difference (actually faster on newer SNAP, which is good:) between two SNAPs when I do make buildworld. Can anybody elaborate why? Here is Bonnie's result on my system: -------Sequential Output-------- ---Sequential Input-- --Random-- -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks--- Machine MB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec %CPU wd0-98 100 7606 75.3 3325 11.2 2513 15.5 9722 81.9 9872 24.2 162.9 3.3 wd0-97 100 7852 83.1 4507 17.0 2134 16.7 9773 93.7 9804 35.0 160.9 4.4 wd2-98 100 9326 94.4 8837 32.2 4193 20.4 10137 94.1 11244 33.5 148.4 3.2 wd2-97 100 8926 95.9 10799 44.5 3158 23.4 9014 93.4 11279 47.9 153.3 4.2 sd0c-98 100 2078 16.8 1503 3.6 1823 6.7 5133 41.6 5160 12.8 154.3 3.0 sd0c-97 100 6209 53.8 6295 18.4 2998 13.5 6237 50.6 6282 15.4 174.6 4.7 sd1c-98 100 2039 16.4 1489 3.5 1795 6.6 5094 40.7 5117 12.8 159.5 3.1 sd1c-97 100 5993 51.4 6110 17.8 2921 13.2 6060 49.2 6071 15.2 182.4 4.9 ccd0-98 100 2142 17.4 2030 5.0 1367 5.4 5136 42.1 5149 13.5 243.6 5.1 ccd0-97 100 9374 84.6 9801 31.8 3914 19.9 8515 71.6 8641 23.8 261.4 7.2 98: 19980222-SNAP kernel 97: 19971006-SNAP kernel CPU: AMD-K6tm w/ multimedia extensions (262.50-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x562 Stepping=2 Features=0x8001bf real memory = 67108864 (65536K bytes) avail memory = 62513152 (61048K bytes) Probing for devices on PCI bus 0: chip0: rev 0x03 on pci0.0.0 chip1: rev 0x25 on pci0.7.0 ide_pci0: rev 0x06 on pci0.7.1 wdc0 at 0x1f0-0x1f7 irq 14 flags 0xa0ffa0ff on isa wdc0: unit 0 (wd0): , DMA, 32-bit, multi-block-16 wd0: 6197MB (12692736 sectors), 12592 cyls, 16 heads, 63 S/T, 512 B/S wdc1 at 0x170-0x177 irq 15 flags 0xa0ffa0ff on isa wdc1: unit 0 (wd2): , DMA, 32-bit, multi-block-16 wd2: 6149MB (12594960 sectors), 13328 cyls, 15 heads, 63 S/T, 512 B/S ... ncr0: rev 0x03 int a irq 11 on pci0.8.0 ncr0: waiting for scsi devices to settle scbus0 at ncr0 bus 0 sd0 at scbus0 target 0 lun 0 sd0: type 0 fixed SCSI 2 sd0: Direct-Access sd0: WIDE SCSI (16 bit) enabled sd0: 20.0 MB/s (100 ns, offset 15) 2048MB (4194304 512 byte sectors) sd1 at scbus0 target 1 lun 0 sd1: type 0 fixed SCSI 2 sd1: Direct-Access sd1: WIDE SCSI (16 bit) enabled sd1: 20.0 MB/s (100 ns, offset 15) 2048MB (4194304 512 byte sectors) Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/wd0a 31743 17319 11885 59% / /dev/wd0s1f 5737885 1358996 3919859 26% /usr (used for bonnie) /dev/wd0s1e 127023 1440 115422 1% /var /dev/wd2a 31743 15785 13419 54% /w/root /dev/wd2e 127023 1201 115661 1% /w/var /dev/wd2f 5690005 1563145 3671660 30% /w/usr (used for bonnie) procfs 4 4 0 100% /proc /dev/sd0c 2032623 1 1870013 0% /u1 (used for bonnie) /dev/sd1c 2032623 1 1870013 0% /u2 (used for bonnie) Thanks Tammy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 5 20:04:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA06635 for freebsd-current-outgoing; Sun, 5 Apr 1998 20:04:02 -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 UAA06607 for ; Sun, 5 Apr 1998 20:03:45 -0700 (PDT) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id WAA07645; Sun, 5 Apr 1998 22:03:36 -0500 (EST) (envelope-from toor) From: "John S. Dyson" Message-Id: <199804060303.WAA07645@dyson.iquest.net> Subject: Re: disk performance difference In-Reply-To: from Tamiji Homma at "Apr 5, 98 07:50:44 pm" To: thomma@slip.net (Tamiji Homma) Date: Sun, 5 Apr 1998 22:03:36 -0500 (EST) Cc: freebsd-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 > Hi, > > I am not a -current but SNAP CD user. I noticed something interesting, > that 19971006-SNAP disk performance is much greater than 19980222-SNAP > specially on my SCSI disk according to what Bonnie's says. In fact, > SCSI disk performance is very poor... > Try building a -current kernel, and I wonder if you see such a regression now. There have been several improvements (and fixes) lately. (It is fairly easy to build a -current kernel, running on a recent snapshot. Sometimes, you'll have to rebuild libkvm and ps, but shouldn't be a major problem, once you go through the learning curve.) > > 19980222-SNAP: 3315.51 real 2313.34 user 599.32 sys > 19971006-SNAP: 3370.48 real 2328.91 user 633.53 sys > > The 'make buildworld' is done under following conditions: > /usr/src on wd0 > /usr/obj on ccd0 (/dev/sd0c /dev/sd1c) > NOPROFILE, NOCLEAN, NOTCL, -pipe, async,noatime > > I don't see much difference (actually faster on newer SNAP, which is > good:) between two SNAPs when I do make buildworld. > > Can anybody elaborate why? > I don't have any details, but there have been numerous problems introduced in the name of improvements. It is likely that you are running a snap with the ioopt feature enabled, and that option was not well thought out before including in the tree. (I know, I implemented it.) John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 5 20:43:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA11578 for freebsd-current-outgoing; Sun, 5 Apr 1998 20:43:22 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com (rah.star-gate.com [209.133.7.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA11573; Sun, 5 Apr 1998 20:43:20 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id UAA01650; Sun, 5 Apr 1998 20:42:55 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199804060342.UAA01650@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Stephen Hocking-Senior Programmer PGS Tensor Perth cc: multimedia@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Quake2'able linux layer in current yet? In-reply-to: Your message of "Mon, 06 Apr 1998 10:14:56 +0800." <199804060214.KAA00982@ariadne.tensor.pgs.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 05 Apr 1998 20:42:54 -0700 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have zero more work to do take it with current's Prima Donas. Cheers, Amancio > > I noticed that with current's latest linux updates quake2 starts, displays the > loading screen and then dies with a bad system call error. This is the 3.10 > binary. Has anyone else had any luck, or does Amancio have some more work to > do? 8^) > > > Stephen > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-multimedia" 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 Apr 5 20:56:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA12936 for freebsd-current-outgoing; Sun, 5 Apr 1998 20:56:03 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from shadow.worldbank.org (shadow.worldbank.org [138.220.104.78]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA12902 for ; Sun, 5 Apr 1998 20:55:58 -0700 (PDT) (envelope-from adhir@worldbank.org) Received: from localhost (adhir@localhost) by shadow.worldbank.org (8.8.8/8.8.8) with SMTP id XAA28300; Sun, 5 Apr 1998 23:53:14 -0400 (EDT) (envelope-from adhir@worldbank.org) X-Authentication-Warning: shadow.worldbank.org: adhir owned process doing -bs Date: Sun, 5 Apr 1998 23:53:13 -0400 (EDT) From: "Alok K. Dhir" To: mike@smith.net.au cc: hasty@rah.star-gate.com, current@FreeBSD.ORG Subject: Re: [TECH] physio split the request.. cannot proceed In-Reply-To: <9D9F385E771FD292852565DD00713AA2.00709147852565DD@worldbank.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 Interestingly, this "physio split the reuest" error is the exact same error I get from -current when trying to write a CD using cdrecord 1.6 on a Yamaha CDR400... On Sun, 5 Apr 1998 mike@smith.net.au wrote: > > > > > > Try to use the Linux package SANE -- is a scsi scanner package. > > > > While trying to read from the scsi scanner , I am getting : > > physio split the request.. cannot proceed > > > > This message is coming from :scsi_ioctl.c:scsistrategy > > > > A few months ago , I didn't have any problems at all using SANE. > > > > The scsi read request is way below the 32k limit . > > > > Anyone got a clue as to what changed in the kernel ? > > Are you using the CAM code on your system? I had the impression that > this was the culprit (I'd be happy to be wrong though). > > -- > \\ 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 > -------------------------------------------------------------------- \||/_ Alok K. Dhir Phone: +1.202.473.2446 oo \ S13-069, ISGMC Email: adhir@worldbank.org L_ The World Bank Group Washington, DC \/ ------------------------------------------------------------------------| "Unix _is_ user friendly - it just chooses friends selectively..." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 5 21:46:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA18322 for freebsd-current-outgoing; Sun, 5 Apr 1998 21:46:22 -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 VAA18308 for ; Sun, 5 Apr 1998 21:46:18 -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 VAA01356; Sun, 5 Apr 1998 21:45:57 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: Stephen Hocking-Senior Programmer PGS Tensor Perth Cc: current@FreeBSD.ORG Subject: Re: Quake2'able linux layer in current yet? In-reply-to: Your message of "Sun, 05 Apr 1998 20:42:54 PDT." <199804060342.UAA01650@rah.star-gate.com> Date: Sun, 05 Apr 1998 21:45:56 -0700 Message-ID: <1352.891837956@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I have zero more work to do take it with current's Prima Donas. For the benefit of those who don't know Amancio, allow me to translate: "I have no idea what's wrong but I'm in a bad mood and feel like blaming some vaguely specified 3rd-party for whatever the problem is in hopes that you'll just go away and stop bothering me." Gosh, wouldn't communication be so much simpler if people just said what they really meant? :-) Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 5 21:51:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA18998 for freebsd-current-outgoing; Sun, 5 Apr 1998 21:51:18 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from limbo.rtfm.net (nathan@rtfm.net [204.141.125.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA18991 for ; Sun, 5 Apr 1998 21:51:14 -0700 (PDT) (envelope-from nathan@limbo.rtfm.net) Received: (from nathan@localhost) by limbo.rtfm.net (8.8.8/8.8.8) id AAA03546; Mon, 6 Apr 1998 00:50:28 -0400 (EDT) Message-ID: <19980406005026.62264@rtfm.net> Date: Mon, 6 Apr 1998 00:50:26 -0400 From: Nathan Dorfman To: "Jordan K. Hubbard" , Stephen Hocking-Senior Programmer PGS Tensor Perth Cc: current@FreeBSD.ORG Subject: Re: Quake2'able linux layer in current yet? References: <199804060342.UAA01650@rah.star-gate.com> <1352.891837956@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <1352.891837956@time.cdrom.com>; from Jordan K. Hubbard on Sun, Apr 05, 1998 at 09:45:56PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Apr 05, 1998 at 09:45:56PM -0700, Jordan K. Hubbard wrote: > > I have zero more work to do take it with current's Prima Donas. > > For the benefit of those who don't know Amancio, allow me to translate: > > "I have no idea what's wrong but I'm in a bad mood and feel like > blaming some vaguely specified 3rd-party for whatever the problem is > in hopes that you'll just go away and stop bothering me." > > Gosh, wouldn't communication be so much simpler if people just said > what they really meant? :-) Yes, but it would be just *so* much less fun :P > Jordan > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- ________________ _______________________________ / Nathan Dorfman V PGP: finger nathan@rtfm.net / / nathan@rtfm.net | http://www.rtfm.net / To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 5 21:54:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA19605 for freebsd-current-outgoing; Sun, 5 Apr 1998 21:54:34 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com (rah.star-gate.com [209.133.7.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA19599 for ; Sun, 5 Apr 1998 21:54:32 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id VAA01953; Sun, 5 Apr 1998 21:54:22 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199804060454.VAA01953@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Jordan K. Hubbard" cc: Stephen Hocking-Senior Programmer PGS Tensor Perth , current@FreeBSD.ORG Subject: Re: Quake2'able linux layer in current yet? In-reply-to: Your message of "Sun, 05 Apr 1998 21:45:56 PDT." <1352.891837956@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 05 Apr 1998 21:54:22 -0700 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Try again, Because I have no clue as to why you are translating my message that way given that I provided the few mods needed to play Quake2 and that a few multimedia guys are playing Quake2. Amancio > > I have zero more work to do take it with current's Prima Donas. > > For the benefit of those who don't know Amancio, allow me to translate: > > "I have no idea what's wrong but I'm in a bad mood and feel like > blaming some vaguely specified 3rd-party for whatever the problem is > in hopes that you'll just go away and stop bothering me." > > Gosh, wouldn't communication be so much simpler if people just said > what they really meant? :-) > > 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 Sun Apr 5 21:57:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA20085 for freebsd-current-outgoing; Sun, 5 Apr 1998 21:57:14 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cimlogic.com.au ([203.36.2.25]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA20078 for ; Sun, 5 Apr 1998 21:57:10 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.5/8.8.7) id OAA17661; Mon, 6 Apr 1998 14:57:29 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199804060457.OAA17661@cimlogic.com.au> Subject: Re: Quake2'able linux layer in current yet? In-Reply-To: <1352.891837956@time.cdrom.com> from "Jordan K. Hubbard" at "Apr 5, 98 09:45:56 pm" To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Mon, 6 Apr 1998 14:57:29 +1000 (EST) Cc: current@FreeBSD.ORG 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 Jordan K. Hubbard wrote: > > I have zero more work to do take it with current's Prima Donas. > > For the benefit of those who don't know Amancio, allow me to translate: > > "I have no idea what's wrong but I'm in a bad mood and feel like > blaming some vaguely specified 3rd-party for whatever the problem is > in hopes that you'll just go away and stop bothering me." > > Gosh, wouldn't communication be so much simpler if people just said > what they really meant? :-) Is _that_ what he meant?! I was sitting here playing "let's try putting a punctuation mark here and see if it makes the statement mean anything". I had considered the possibility that the Prima Donas might have been a soccer team from some country I've never heard of. 8-) -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org 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 Sun Apr 5 22:43:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA24909 for freebsd-current-outgoing; Sun, 5 Apr 1998 22:43:41 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from wcc.wcc.net (wcc.wcc.net [208.6.232.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA24890; Sun, 5 Apr 1998 22:43:37 -0700 (PDT) (envelope-from piquan@wcc.wcc.net) Received: from detlev.UUCP (tnt13.wcc.net [208.10.139.13]) by wcc.wcc.net (8.8.8/8.8.8) with ESMTP id AAA15380; Mon, 6 Apr 1998 00:39:09 -0500 (CDT) Received: (from joelh@localhost) by detlev.UUCP (8.8.8/8.8.8) id AAA02003; Mon, 6 Apr 1998 00:43:18 -0500 (CDT) (envelope-from joelh) Date: Mon, 6 Apr 1998 00:43:18 -0500 (CDT) Message-Id: <199804060543.AAA02003@detlev.UUCP> To: dyson@FreeBSD.ORG CC: dswartz@druber.com, dg@root.com, dag-erli@ifi.uio.no, stable@FreeBSD.ORG, current@FreeBSD.ORG In-reply-to: <199804052135.QAA00680@dyson.iquest.net> Subject: Re: swap-leak in 2.2.5 ? From: Joel Ray Holveck Reply-to: joelh@gnu.org References: <199804052135.QAA00680@dyson.iquest.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> My only quibble with this technique is that it would seem to make it >> harder to tell if your machine is really running low on swap or not >> (e.g. swap as backing store for stack/heap/whatever *is* critical and >> allocation failure can cause application failure, whereas swap being >> used to cache random cruft is in the "who really cares" department). >> Or is there some way to tell the difference? > It is difficult not only to tell if you are low on swap, but also it > is hard to quantify being low on memory. I have been thinking about > this over the last year or so. I don't know much about the FreeBSD VM system, but it is my understanding that in stock 4.4BSD, you can tell kinda by a high number of page outs but mostly by swap outs if you are low on RAM. Is this not the case also with FreeBSD? I've been considering writing a utility to watch several performance-related stats (including *why* pages are being paged out, and processes swapped out, etc), and watch whether MINFREE is being approached, or what have you. Has this already been done? 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 Sun Apr 5 22:53:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA28087 for freebsd-current-outgoing; Sun, 5 Apr 1998 22:53:34 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from arh0300.urh.uiuc.edu (arh0300.urh.uiuc.edu [130.126.72.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA28068 for ; Sun, 5 Apr 1998 22:53:19 -0700 (PDT) (envelope-from dannyman@arh0300.urh.uiuc.edu) Received: (from dannyman@localhost) by arh0300.urh.uiuc.edu (8.8.8/8.8.5) id AAA14098; Mon, 6 Apr 1998 00:53:14 -0500 (CDT) Message-ID: <19980406005314.31853@arh0300.urh.uiuc.edu> Date: Mon, 6 Apr 1998 00:53:14 -0500 From: dannyman To: "Daniel O'Connor" Cc: freebsd-current@FreeBSD.ORG Subject: Re: usleep is hosed, timezone problems in current Mail-Followup-To: Daniel O'Connor , freebsd-current@FreeBSD.ORG References: <199804051312.IAA11235@arh0300.urh.uiuc.edu> <199804060102.KAA08481@cain.gsoft.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <199804060102.KAA08481@cain.gsoft.com.au>; from Daniel O'Connor on Mon, Apr 06, 1998 at 10:32:58AM +0930 X-Loop: djhoward@uiuc.edu X-URL: http://www.uiuc.edu/ph/www/djhoward/ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Apr 06, 1998 at 10:32:58AM +0930, Daniel O'Connor wrote: > > > after my X display went blank for awhile. awhile later the screen went > > blank for a few seconds again and I'm back now ... well, should be 0309h > > CDT (just should have shifted from CST 0209h ...) 5 April ... date says; > > Sun Apr 5 08:10:13 CDT 1998 > I get the same problem (I have a kernel/world checked out at around 8am > Apr 5 GMT) and I always get errno == -2... I've set my CMOS to UCT and tzsetup accordingly, things seem normal. I will be doing make installworld soon off of 5 April @0430h CDT build. -dan -- // dannyman yori aiokomete || Our Honored Symbol deserves \\/ http://www.dannyland.org/~dannyman/ || an Honorable Retirement (UIUC) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 5 22:57:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA28809 for freebsd-current-outgoing; Sun, 5 Apr 1998 22:57:39 -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 WAA28797; Sun, 5 Apr 1998 22:57:26 -0700 (PDT) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id AAA08923; Mon, 6 Apr 1998 00:57:20 -0500 (EST) (envelope-from toor) From: "John S. Dyson" Message-Id: <199804060557.AAA08923@dyson.iquest.net> Subject: Re: swap-leak in 2.2.5 ? In-Reply-To: <199804060543.AAA02003@detlev.UUCP> from Joel Ray Holveck at "Apr 6, 98 00:43:18 am" To: joelh@gnu.org Date: Mon, 6 Apr 1998 00:57:20 -0500 (EST) Cc: dyson@FreeBSD.ORG, dswartz@druber.com, dg@root.com, dag-erli@ifi.uio.no, stable@FreeBSD.ORG, 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 > >> My only quibble with this technique is that it would seem to make it > >> harder to tell if your machine is really running low on swap or not > >> (e.g. swap as backing store for stack/heap/whatever *is* critical and > >> allocation failure can cause application failure, whereas swap being > >> used to cache random cruft is in the "who really cares" department). > >> Or is there some way to tell the difference? > > It is difficult not only to tell if you are low on swap, but also it > > is hard to quantify being low on memory. I have been thinking about > > this over the last year or so. > > I don't know much about the FreeBSD VM system, but it is my > understanding that in stock 4.4BSD, you can tell kinda by a high > number of page outs but mostly by swap outs if you are low on RAM. Is > this not the case also with FreeBSD? > Yes, that is about the only way. I think that high (swap) pageout activity along with a small cache queue length would seem to be a good (and sensitive) indicator. We have no utility that informs users simply though. > > I've been considering writing a utility to watch several > performance-related stats (including *why* pages are being paged out, > and processes swapped out, etc), and watch whether MINFREE is being > approached, or what have you. > Very good idea!!! If you need pointers to the info, let me know. Most of the info is available under sysctl vm and sysctl vfs, along with some of the cnt.* variables (which should likely be accessible with sysctl also.) John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 5 22:58:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA29065 for freebsd-current-outgoing; Sun, 5 Apr 1998 22:58:14 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from wcc.wcc.net (wcc.wcc.net [208.6.232.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA29013; Sun, 5 Apr 1998 22:58:06 -0700 (PDT) (envelope-from piquan@wcc.wcc.net) Received: from detlev.UUCP (tnt39.wcc.net [208.10.139.39]) by wcc.wcc.net (8.8.8/8.8.8) with ESMTP id AAA16010; Mon, 6 Apr 1998 00:53:19 -0500 (CDT) Received: (from joelh@localhost) by detlev.UUCP (8.8.8/8.8.8) id AAA02073; Mon, 6 Apr 1998 00:56:49 -0500 (CDT) (envelope-from joelh) Date: Mon, 6 Apr 1998 00:56:49 -0500 (CDT) Message-Id: <199804060556.AAA02073@detlev.UUCP> To: dyson@FreeBSD.ORG CC: dswartz@druber.com, dyson@FreeBSD.ORG, dg@root.com, dag-erli@ifi.uio.no, stable@FreeBSD.ORG, current@FreeBSD.ORG In-reply-to: <199804052307.SAA00506@dyson.iquest.net> Subject: Re: swap-leak in 2.2.5 ? From: Joel Ray Holveck Reply-to: joelh@gnu.org References: <199804052307.SAA00506@dyson.iquest.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The needed amount of physical memory is best judged by paging activity, > but again, the system doesn't tell you directly. Perhaps I'm confused, then... Doesn't vmstat tell you paging activity? Granted, it doesn't tell you whether it's paging to get rid of unused pages, or whether it's paging to free up needed memory, but at least it's a start. 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 Sun Apr 5 23:05:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA01657 for freebsd-current-outgoing; Sun, 5 Apr 1998 23:05:31 -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 XAA01628 for ; Sun, 5 Apr 1998 23:05:19 -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 PAA10056; Mon, 6 Apr 1998 15:34:52 +0930 (CST) Message-Id: <199804060604.PAA10056@cain.gsoft.com.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: dannyman cc: "Daniel O'Connor" , freebsd-current@FreeBSD.ORG Subject: Re: usleep is hosed, timezone problems in current In-reply-to: Your message of "Mon, 06 Apr 1998 00:53:14 EST." <19980406005314.31853@arh0300.urh.uiuc.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 06 Apr 1998 15:34:52 +0930 From: "Daniel O'Connor" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > Sun Apr 5 08:10:13 CDT 1998 > > I get the same problem (I have a kernel/world checked out at around 8am > > Apr 5 GMT) and I always get errno == -2... > I've set my CMOS to UCT and tzsetup accordingly, things seem normal. > I will be doing make installworld soon off of 5 April @0430h CDT build. Hmm.. I ran my with the local time zone so it would work with Windows.. Although I don't see why changing my CMOS clock to UTC would fix usleep.. --------------------------------------------------------------------- |Daniel O'Connor software and network engineer for Genesis Software | |http://www.gsoft.com.au | |The nice thing about standards is that there are so many of them to| |choose from. -- Andrew Tanenbaum | --------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 5 23:05:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA01673 for freebsd-current-outgoing; Sun, 5 Apr 1998 23:05:38 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from wcc.wcc.net (wcc.wcc.net [208.6.232.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA01639 for ; Sun, 5 Apr 1998 23:05:24 -0700 (PDT) (envelope-from piquan@wcc.wcc.net) Received: from detlev.UUCP (tnt39.wcc.net [208.10.139.39]) by wcc.wcc.net (8.8.8/8.8.8) with ESMTP id AAA16227; Mon, 6 Apr 1998 00:58:06 -0500 (CDT) Received: (from joelh@localhost) by detlev.UUCP (8.8.8/8.8.8) id BAA02173; Mon, 6 Apr 1998 01:02:15 -0500 (CDT) (envelope-from joelh) Date: Mon, 6 Apr 1998 01:02:15 -0500 (CDT) Message-Id: <199804060602.BAA02173@detlev.UUCP> To: archer@lucky.net CC: H.Husic@Uni-Koeln.DE, current@FreeBSD.ORG In-reply-to: <199804052033.XAA09862@grape.carrier.kiev.ua> (message from Alexander Litvin on Sun, 5 Apr 1998 23:33:51 +0300 (EEST)) Subject: Re: lastlogs 'invalid hostname' From: Joel Ray Holveck Reply-to: joelh@gnu.org References: <199804052033.XAA09862@grape.carrier.kiev.ua> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> I have a decent problem with a 3.0-CURRENT machine here. >> [hhusic@dvpraktikum hhusic]$ w >> 5:13PM up 6:25, 9 users, load averages: 1.01, 1.03, 0.98 >> USER TTY FROM LOGIN@ IDLE WHAT >> rstevens p8 invalid hostname 5:11PM 1 -bash (bash) > In our case I found that "invalid hostname" is written by /usr/bin/login > when user comes from some address which resolves to some hostname which > in turn doesn't resolve. Wouldn't the Right Thing actually be to log the IP quad in that case instead, like it does with overly long hostnames? > I patched login not to write 'invalid hostname', but rather to > write as much of 'long.not.resolvable.host.name' as possible. > The patch is trivial. In our copious free time, we may want to actually change it to log 'long...host.name' instead. Normally, in my experience, I need either the TLD or the first name of a machine, and the rest is just fluff. If this seems to be useful to the others, I'll write a patch and submit a pr. Others? -- 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 Sun Apr 5 23:09:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA02662 for freebsd-current-outgoing; Sun, 5 Apr 1998 23:09:46 -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 XAA02616; Sun, 5 Apr 1998 23:09:39 -0700 (PDT) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id BAA09011; Mon, 6 Apr 1998 01:09:32 -0500 (EST) (envelope-from toor) From: "John S. Dyson" Message-Id: <199804060609.BAA09011@dyson.iquest.net> Subject: Re: swap-leak in 2.2.5 ? In-Reply-To: <199804060556.AAA02073@detlev.UUCP> from Joel Ray Holveck at "Apr 6, 98 00:56:49 am" To: joelh@gnu.org Date: Mon, 6 Apr 1998 01:09:32 -0500 (EST) Cc: dyson@FreeBSD.ORG, dswartz@druber.com, dg@root.com, dag-erli@ifi.uio.no, stable@FreeBSD.ORG, 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 > > > The needed amount of physical memory is best judged by paging activity, > > but again, the system doesn't tell you directly. > > Perhaps I'm confused, then... Doesn't vmstat tell you paging activity? > Granted, it doesn't tell you whether it's paging to get rid of unused > pages, or whether it's paging to free up needed memory, but at least > it's a start. > It doesn't quantify the amount of paging that is excessive. How does one judge that a certain amount of paging is too much? The work would be to quantify and interpret the raw status that the system provides. It is similar to the difference between "understanding" and "being able to design." I suggest that this would be a good project, but creating a reliable measure of system paging load where a measurement of excessive paging is translated into an understandable and accurage judgement is interesting, and the information is not provided directly by the system. It would have to be calculated somehow. John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 5 23:15:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA03906 for freebsd-current-outgoing; Sun, 5 Apr 1998 23:15:53 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com (rah.star-gate.com [209.133.7.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA03901 for ; Sun, 5 Apr 1998 23:15:50 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id XAA02328; Sun, 5 Apr 1998 23:15:36 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199804060615.XAA02328@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: John Birrell cc: current@FreeBSD.ORG Subject: Re: Quake2'able linux layer in current yet? In-reply-to: Your message of "Mon, 06 Apr 1998 14:57:29 +1000." <199804060457.OAA17661@cimlogic.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 05 Apr 1998 23:15:36 -0700 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi John, We just need someone to tender to the linux emulation layer in -current. Quake2 is a good target since the original linux emulation layer came about to support Doom. The original poster's question was when is current's linux emulation layer going to be up to the job of supporting Quake2? A good starting place to resolve the issues with -current's linux emulation with respect to Quake2 is: ftp://rah.star-gate.com/pub/README.GLQUAKE. Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 5 23:22:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA05271 for freebsd-current-outgoing; Sun, 5 Apr 1998 23:22:07 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from arh0300.urh.uiuc.edu (arh0300.urh.uiuc.edu [130.126.72.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA05216 for ; Sun, 5 Apr 1998 23:22:00 -0700 (PDT) (envelope-from dannyman@arh0300.urh.uiuc.edu) Received: (from dannyman@localhost) by arh0300.urh.uiuc.edu (8.8.8/8.8.5) id BAA21937; Mon, 6 Apr 1998 01:21:56 -0500 (CDT) Message-ID: <19980406012156.56128@arh0300.urh.uiuc.edu> Date: Mon, 6 Apr 1998 01:21:56 -0500 From: dannyman To: "Daniel O'Connor" Cc: freebsd-current@FreeBSD.ORG Subject: Re: usleep is hosed, timezone problems in current Mail-Followup-To: Daniel O'Connor , freebsd-current@FreeBSD.ORG References: <19980406005314.31853@arh0300.urh.uiuc.edu> <199804060604.PAA10056@cain.gsoft.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <199804060604.PAA10056@cain.gsoft.com.au>; from Daniel O'Connor on Mon, Apr 06, 1998 at 03:34:52PM +0930 X-Loop: djhoward@uiuc.edu X-URL: http://www.uiuc.edu/ph/www/djhoward/ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Apr 06, 1998 at 03:34:52PM +0930, Daniel O'Connor wrote: > > > > > Sun Apr 5 08:10:13 CDT 1998 > > > I get the same problem (I have a kernel/world checked out at around 8am > > > Apr 5 GMT) and I always get errno == -2... > > I've set my CMOS to UCT and tzsetup accordingly, things seem normal. > > I will be doing make installworld soon off of 5 April @0430h CDT build. > Hmm.. I ran my with the local time zone so it would work with Windows.. > Although I don't see why changing my CMOS clock to UTC would fix usleep.. afaik, usleep is still hosed. i should make buildworld *now* coz i wanna go to sleep. i don't run windows, so i don't care about localtime CMOS. :) -dan -- // dannyman yori aiokomete || Our Honored Symbol deserves \\/ http://www.dannyland.org/~dannyman/ || an Honorable Retirement (UIUC) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 5 23:23:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA05890 for freebsd-current-outgoing; Sun, 5 Apr 1998 23:23:46 -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 XAA05864 for ; Sun, 5 Apr 1998 23:23:40 -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 PAA10213; Mon, 6 Apr 1998 15:53:30 +0930 (CST) Message-Id: <199804060623.PAA10213@cain.gsoft.com.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: dannyman cc: "Daniel O'Connor" , freebsd-current@FreeBSD.ORG Subject: Re: usleep is hosed, timezone problems in current In-reply-to: Your message of "Mon, 06 Apr 1998 01:21:56 EST." <19980406012156.56128@arh0300.urh.uiuc.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 06 Apr 1998 15:53:30 +0930 From: "Daniel O'Connor" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > afaik, usleep is still hosed. Ahh, OK :) > i should make buildworld *now* coz i wanna go to sleep. Heheh :) > i don't run windows, so i don't care about localtime CMOS. :) Huh.. need to play games =) --------------------------------------------------------------------- |Daniel O'Connor software and network engineer for Genesis Software | |http://www.gsoft.com.au | |The nice thing about standards is that there are so many of them to| |choose from. -- Andrew Tanenbaum | --------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 5 23:28:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA07288 for freebsd-current-outgoing; Sun, 5 Apr 1998 23:28:25 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA07277 for ; Sun, 5 Apr 1998 23:28:13 -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 IAA09185; Mon, 6 Apr 1998 08:27:16 +0200 (CEST) To: dannyman cc: "Daniel O'Connor" , freebsd-current@FreeBSD.ORG Subject: Re: usleep is hosed, timezone problems in current In-reply-to: Your message of "Mon, 06 Apr 1998 01:21:56 CDT." <19980406012156.56128@arh0300.urh.uiuc.edu> Date: Mon, 06 Apr 1998 08:27:15 +0200 Message-ID: <9183.891844035@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19980406012156.56128@arh0300.urh.uiuc.edu>, dannyman writes: >On Mon, Apr 06, 1998 at 03:34:52PM +0930, Daniel O'Connor wrote: >> >> > > > Sun Apr 5 08:10:13 CDT 1998 >> > > I get the same problem (I have a kernel/world checked out at around 8am > >> > > Apr 5 GMT) and I always get errno == -2... >> > I've set my CMOS to UCT and tzsetup accordingly, things seem normal. >> > I will be doing make installworld soon off of 5 April @0430h CDT build. >> Hmm.. I ran my with the local time zone so it would work with Windows.. >> Although I don't see why changing my CMOS clock to UTC would fix usleep.. > >afaik, usleep is still hosed. Please test with -current sources, it should work now, it is based on nanosleep(2) which is belived to DTRT now. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "Drink MONO-tonic, it goes down but it will NEVER come back up!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 5 23:39:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA08479 for freebsd-current-outgoing; Sun, 5 Apr 1998 23:39:52 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from arh0300.urh.uiuc.edu (arh0300.urh.uiuc.edu [130.126.72.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA08460 for ; Sun, 5 Apr 1998 23:39:51 -0700 (PDT) (envelope-from dannyman@arh0300.urh.uiuc.edu) Received: (from dannyman@localhost) by arh0300.urh.uiuc.edu (8.8.8/8.8.5) id BAA27380; Mon, 6 Apr 1998 01:39:48 -0500 (CDT) Message-ID: <19980406013947.48457@arh0300.urh.uiuc.edu> Date: Mon, 6 Apr 1998 01:39:47 -0500 From: dannyman To: "Daniel O'Connor" Cc: freebsd-current@FreeBSD.ORG Subject: Re: usleep is hosed, timezone problems in current Mail-Followup-To: Daniel O'Connor , freebsd-current@FreeBSD.ORG References: <19980406012156.56128@arh0300.urh.uiuc.edu> <199804060623.PAA10213@cain.gsoft.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <199804060623.PAA10213@cain.gsoft.com.au>; from Daniel O'Connor on Mon, Apr 06, 1998 at 03:53:30PM +0930 X-Loop: djhoward@uiuc.edu X-URL: http://www.uiuc.edu/ph/www/djhoward/ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Apr 06, 1998 at 03:53:30PM +0930, Daniel O'Connor wrote: > > i don't run windows, so i don't care about localtime CMOS. :) > Huh.. need to play games =) Games are obseleted here. :) -- // dannyman yori aiokomete || Our Honored Symbol deserves \\/ http://www.dannyland.org/~dannyman/ || an Honorable Retirement (UIUC) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 6 00:31:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA15664 for freebsd-current-outgoing; Mon, 6 Apr 1998 00:31:00 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA15654 for ; Mon, 6 Apr 1998 00:30:57 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.5) with ESMTP id JAA09396 for ; Mon, 6 Apr 1998 09:30:11 +0200 (CEST) To: current@FreeBSD.ORG Subject: LINT broken in brooktree848.c ? From: Poul-Henning Kamp Date: Mon, 06 Apr 1998 09:30:11 +0200 Message-ID: <9394.891847811@critter.freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG cc -c -O -pipe -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wuninitialized -nostdinc -I- -I. -I../.. -I/usr/include -DKERNEL -include opt_global.h ../../pci/brooktree848.c ../../pci/brooktree848.c:232: opt_bktr.h: No such file or directory -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 6 00:40:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA17364 for freebsd-current-outgoing; Mon, 6 Apr 1998 00:40:37 -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 AAA17336 for ; Mon, 6 Apr 1998 00:40:18 -0700 (PDT) (envelope-from toasty@home.dragondata.com) Received: (from toasty@localhost) by home.dragondata.com (8.8.8/8.8.5) id CAA08690 for current@freebsd.org; Mon, 6 Apr 1998 02:40:11 -0500 (CDT) From: Kevin Day Message-Id: <199804060740.CAA08690@home.dragondata.com> Subject: panic: freeing a free page To: current@FreeBSD.ORG Date: Mon, 6 Apr 1998 02:40:10 -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 Kernel cvsupped on the 25th... (kgdb) core-file vmcore.7 IdlePTD 258000 initial pcb at 204ee0 panicstr: vm_page_free: freeing free page panic messages: --- panic: vm_page_free: freeing free page mp_lock = 00000001; cpuid = 0; lapic.id = 00000000 panic: from debugger mp_lock = 00000002; cpuid = 0; lapic.id = 00000000 boot() called on cpu#0 dumping to dev 20011, offset 118532 dump 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 --- #0 boot (howto=260) at ../../kern/kern_shutdown.c:296 296 dumppcb.pcb_cr3 = rcr3(); (kgdb) backtrace #0 boot (howto=260) at ../../kern/kern_shutdown.c:296 #1 0xf0114312 in panic (fmt=0xf0101568 "from debugger") at ../../kern/kern_shutdown.c:436 #2 0xf0101585 in db_panic (addr=-266618167, have_addr=0, count=-1, modif=0xf8d01c94 "") at ../../ddb/db_command.c:432 #3 0xf0101465 in db_command (last_cmdp=0xf01f5ae4, cmd_table=0xf01f5944, aux_cmd_tablep=0xf0202318) at ../../ddb/db_command.c:332 #4 0xf01015f2 in db_command_loop () at ../../ddb/db_command.c:454 #5 0xf0103cb3 in db_trap (type=3, code=0) at ../../ddb/db_trap.c:71 #6 0xf01bb864 in kdb_trap (type=3, code=0, regs=0xf8d01d84) at ../../i386/i386/db_interface.c:157 #7 0xf01cc748 in trap (frame={tf_es = 16, tf_ds = 16, tf_edi = -121241336, tf_esi = 256, tf_ebp = -120578616, tf_isp = -120578644, tf_ebx = -266661581, tf_edx = -266618220, tf_ecx = 1, tf_eax = 18, tf_trapno = 3, tf_err = 0, tf_eip = -266618167, tf_cs = 8, tf_eflags = 582, tf_esp = -266618236, tf_ss = -267304333}) at ../../i386/i386/trap.c:506 #8 0xf01bbac9 in Debugger (msg=0xf0114273 "panic") at ../../i386/i386/db_interface.c:316 #9 0xf0114309 in panic (fmt=0xf01b1133 "vm_page_free: freeing free page") at ../../kern/kern_shutdown.c:434 #10 0xf01b1209 in vm_page_freechk_and_unqueue (m=0xf048f790) at ../../vm/vm_page.c:1090 ---Type to continue, or q to quit--- #11 0xf01b1304 in vm_page_free (m=0xf048f790) at ../../vm/vm_page.c:1179 #12 0xf01af420 in vm_object_collapse (object=0xf8b425ac) at ../../vm/vm_object.c:1073 #13 0xf01ae920 in vm_object_deallocate (object=0xf8a364a4) at ../../vm/vm_object.c:361 #14 0xf01ac053 in vm_map_entry_delete (map=0xf8c71400, entry=0xf8c17558) at ../../vm/vm_map.c:1724 #15 0xf01ac1cd in vm_map_delete (map=0xf8c71400, start=0, end=4022329344) at ../../vm/vm_map.c:1825 #16 0xf01ac251 in vm_map_remove (map=0xf8c71400, start=0, end=4022329344) at ../../vm/vm_map.c:1850 #17 0xf010cf28 in exit1 (p=0xf8c92740, rv=11) at ../../kern/kern_exit.c:214 #18 0xf01155da in sigexit (p=0xf8c92740, signum=11) at ../../kern/kern_sig.c:1240 #19 0xf01153d7 in postsig (signum=11) at ../../kern/kern_sig.c:1147 #20 0xf01cc7e4 in trap (frame={tf_es = 39, tf_ds = 39, tf_edi = 2, tf_esi = 5, tf_ebp = -272638756, tf_isp = -120578076, tf_ebx = 0, tf_edx = -272638712, tf_ecx = 348207, tf_eax = -272638712, tf_trapno = 12, tf_err = 5, tf_eip = 13770, tf_cs = 31, tf_eflags = 66054, tf_esp = -272638776, tf_ss = 39}) at ../../i386/i386/trap.c:162 #21 0x35ca in ?? () Cannot access memory at address 0xefbfdcdc. (kgdb) quit Anything anyone wants me to do with this core file? :) On a completely unrelated note, is *anyone* else unable to get pidentd to work without spewing lots and lots of k_getuid retries: 1 and getbuf: bad address messages... Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 6 04:13:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA08939 for freebsd-current-outgoing; Mon, 6 Apr 1998 04:13:20 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from org.chem.msu.su (org.chem.msu.su [158.250.32.94]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA08444; Mon, 6 Apr 1998 04:11:42 -0700 (PDT) (envelope-from genie@qsar.chem.msu.su) Received: from org-qsar2.chem.msu.su (org-qsar2.chem.msu.su [158.250.48.99]) by org.chem.msu.su (8.8.7/8.8.5) with SMTP id PAA16109; Mon, 6 Apr 1998 15:03:38 +0400 (MSD) Message-ID: <005f01bd614b$b01d65c0$6330fa9e@org-qsar2.chem.msu.su> From: "Eugene Radchenko" To: "Alex" , Cc: , Subject: Re: SCSI errors with latest -current Date: Mon, 6 Apr 1998 15:03:38 +0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! -----Original Message----- From: Alex Date: Sunday, April 05, 1998 12:43 AM Subject: Re: SCSI errors with latest -current On Sat, 4 Apr 1998, Andrey Chernov wrote: > With latest -current I start to get this sort of errors for my several > SCSI drives. Since they started at once for several drives, I suppose it > is not hardware problem. Any ideas? I find that if your disk system is pushed hard enough, that you will get errors like that with SCB paging and/or TAGGED_QUEUING enabled even before PHKs commits. This is one of the things the CAM code (dunno if it's stable enough to use) fixes. In essence it's a combination hardware and software problem... I think. As I tried to shout all over the SCSI list recently (to no avail), this is not limited to -current or 2.2.5. I had something like this even in 2.1 (though not as drastic -- just dump died and not the whole system). I have the feeling that 2.1 had not done tagged queueing yet. I hope now that one of the core team was bitten, this problem will be solved sooner ;-) BTW this definitely would classify as bug fix and as such, should be put in -stable, yes? I think many people are somewhat disappointed to obtain a release CD just to begin patching the system right after installation... Cheers Genie --- ######################################################### Eugene V. Radchenko Research associate, Computer Chemistry E-mail: genie@qsar.chem.msu.su http://org.chem.msu.su/~genie =================================================== "There are now new criminals out there that don't have guns. They have computers and many have other weapons of mass destruction." -- Janet Reno, Attorney General of the United States To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 6 05:11:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA15407 for freebsd-current-outgoing; Mon, 6 Apr 1998 05:11:53 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA15401; Mon, 6 Apr 1998 05:11:50 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id FAA04001; Mon, 6 Apr 1998 05:04:03 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: "Eugene Radchenko" cc: "Alex" , ache@nagual.pp.ru, scsi@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: SCSI errors with latest -current In-reply-to: Your message of "Mon, 06 Apr 1998 15:03:38 +0400." <005f01bd614b$b01d65c0$6330fa9e@org-qsar2.chem.msu.su> Date: Mon, 06 Apr 1998 05:04:03 -0700 Message-ID: <3997.891864243@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > As I tried to shout all over the SCSI list recently (to no avail), this is > not limited to -current or 2.2.5. I had something like this even in 2.1 > (though not as drastic -- just dump died and not the whole system). I have > the feeling that 2.1 had not done tagged queueing yet. Things don't get fixed by shouting, they get fixed by fixing. That's free software. Feel free, Eugene! ;-) Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 6 05:47:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA19591 for freebsd-current-outgoing; Mon, 6 Apr 1998 05:47:22 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from psasolar.psa.pencom.com (psasolar.colltech.com [208.229.236.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA19586 for ; Mon, 6 Apr 1998 05:47:21 -0700 (PDT) (envelope-from ejon@colltech.com) Received: (from ejon@localhost) by psasolar.psa.pencom.com (VER/What/1.0) id HAA17043; Mon, 6 Apr 1998 07:43:59 -0500 (CDT) Message-Id: <199804061243.HAA17043@psasolar.psa.pencom.com> Subject: Re: Current with XFree86 3.3.2 In-Reply-To: <199804052149.QAA01036@aenima.unixgeeks.net> from Oliver Banta at "Apr 5, 98 04:49:20 pm" To: obanta@unixgeeks.net (Oliver Banta) Date: Mon, 6 Apr 1998 07:43:58 -0500 (CDT) Cc: freebsd-current@FreeBSD.ORG From: Eric "Two Cats" Jones 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 Oliver, I had what I think is the same problem (although I was building directly from the XF86 source base, not the port: the port may avoid this problem). My problem was that the XF86 server code implements their own malloc, for which they need the hardware pagesize. The code checks whether to use sysconf(5) for this info by doing #ifdef _SC_PAGESIZE, which until about 3/28 was false. After 3/28, this value is defined, however the backend code would cause sysconf(_SC_PAGESIZE) to return -1, which XF86 didn't bother to check. It would later use this pagesize to calculate what size chunk to allocate off the heap, with disasterous consequences. There's a way to force the code to use the getpagesize(3) call, but I can't remember off the top of my head and I've deleted my distribution. Check xc/programs/Xserver/os/xalloc.c and look for _SC_PAGESIZE... you should be able to figure it out from there. I suspect your log messages are coincidental. Eric Jones Collective Technology Strange sunspot activity caused Oliver Banta to write: > I recently installed 3.0-980311-SNAP on a Dual PPro 180. X was > working fine until I did two things: 1) rebuilt world to -current as > of April 3 and 2) rebuilt XFree86 3.3.2 from /usr/ports/x11/XFree86/. > Now whenever I try to start any X server, it core dumps on me. > [...] > > To make sure it wasn't something dumb on my part, I ran XF86Setup > which uses the XF86_VGA16 server, and it also core dumped on me. I > ran this when I originally installed 3.0-SNAP and it worked fine. > This is the error I get, in case it will help anyone figure out what's > wrong: > > Apr 4 04:03:12 knuth /kernel: forward_hardclock: checkstate 0 > Apr 4 04:03:13 knuth last message repeated 15 times > Apr 4 04:03:15 knuth /kernel: pid 12296 (XF86_VGA16), uid 0: exited on signal 6 > (core dumped) > > I am currently rebuilding world and will try again as soon as it > finishes. I will also try it with SMP not enabled to see if that > makes any difference. If anyone has any hints or suggestions, I'd > love to hear them. > > Cheers, > -- Oliver > > 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 Apr 6 06:52:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA27016 for freebsd-current-outgoing; Mon, 6 Apr 1998 06:52:53 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.newbridge.com (ns.newbridge.com [192.75.23.67]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA27011 for ; Mon, 6 Apr 1998 06:52:50 -0700 (PDT) (envelope-from karaki@ca.newbridge.com) Received: (from smap@localhost) by ns.newbridge.com (8.8.8/8.6.12) id JAA17311 for ; Mon, 6 Apr 1998 09:52:50 -0400 (EDT) Received: from kanata-gw1(192.75.23.72) by ns via smap (V1.3) id sma017192; Mon Apr 6 09:52:14 1998 Received: from kanmaster.ca.newbridge.com by kanata-gw1.ca.newbridge.com via smtpd (for ns.newbridge.com [192.75.23.67]) with SMTP; 6 Apr 1998 13:52:14 UT Received: from thor.ca.newbridge.com (thor143.ca.newbridge.com [138.120.143.14]) by ca.newbridge.com. (8.8.6/8.8.6) with SMTP id JAA08637 for ; Mon, 6 Apr 1998 09:52:13 -0400 (EDT) Received: from ticws001.newbridge (ticws001 [192.168.226.2]) by thor.ca.newbridge.com (8.6.12/8.6.12) with ESMTP id JAA11266 for ; Mon, 6 Apr 1998 09:52:12 -0400 Received: from ticws001 by ticws001.newbridge (SMI-8.6/SMI-SVR4) id JAA16235; Mon, 6 Apr 1998 09:52:07 -0400 Message-ID: <3528DE07.1761@newbridge.com> Date: Mon, 06 Apr 1998 09:52:07 -0400 From: Kenichi Araki Organization: Newbridge Networks Corporation X-Mailer: Mozilla 3.01 (X11; I; SunOS 5.5.1 sun4u) MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: Re: current-digest V4 #81 References: <199804040418.UAA19873@hub.freebsd.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG unsubscribe freebsd-current To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 6 07:04:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA27709 for freebsd-current-outgoing; Mon, 6 Apr 1998 07:04:23 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from aldan.ziplink.net (mi@kot.ne.mediaone.net [24.128.29.55]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA27701 for ; Mon, 6 Apr 1998 07:04:20 -0700 (PDT) (envelope-from mi@rtfm.ziplink.net) Received: from rtfm.ziplink.net (rtfm [199.232.255.52]) by aldan.ziplink.net (8.8.8/8.8.7) with ESMTP id OAA05560 for ; Mon, 6 Apr 1998 14:04:13 GMT (envelope-from mi@rtfm.ziplink.net) Received: (from mi@localhost) by rtfm.ziplink.net (8.8.8/8.8.5) id KAA06627 for freebsd-current@freebsd.org; Mon, 6 Apr 1998 10:04:08 -0400 (EDT) From: Mikhail Teterin Message-Id: <199804061404.KAA06627@rtfm.ziplink.net> Subject: When /usr/src and /usr/obj are symlinks To: freebsd-current@FreeBSD.ORG Date: Mon, 6 Apr 1998 10:04:08 -0400 (EDT) X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli" /ccd/obj lrwxrwxrwx 1 root wheel 12 Mar 8 16:23 /usr/src -> /home/mi/src Now it fails right away trying to "bootstrap" make: make: don't know how to make /usr/obj/home/mi/src/tmp/usr/include/sys/types.h. Stop And NULLFS appears broken, because my attempts to mount /ccd/obj over /usr/obj resulted in system crash. Besides, this is probably much more CPU intensive and will slow down the build on the poor P90 ... The world is cvsuped a couple of hours ago. The system currently runs the new (todays) kernel with the rest of the world from Mar 11 (I know, I should do the world first, it just happened that way). Thanks for clues! -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 6 08:34:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA06977 for freebsd-current-outgoing; Mon, 6 Apr 1998 08:34:04 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zuul.dsndata.com (root@zuul.dsndata.com [198.183.3.2]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id IAA06953 for ; Mon, 6 Apr 1998 08:33:59 -0700 (PDT) (envelope-from obanta@dsndata.com) Received: from humpy.dsndata.com by zuul.dsndata.com with smtp (Smail3.1.28.1 #5) id m0yMDuI-000N69C; Mon, 6 Apr 98 10:33 WET DST Received: by humpy.dsndata.com (Smail3.1.28.1 #5) id m0yMDuH-00158NC; Mon, 6 Apr 98 10:33 CDT Message-Id: Date: Mon, 6 Apr 98 10:33 CDT From: obanta@dsndata.com (Oliver Banta) To: freebsd-current@FreeBSD.ORG Subject: XFree86 3.3.2 install. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Can all of you who are having problems after installing XFree86 3.3.2 from the ports collection check the permissions on the X Servers after the install? I am almost positive this is the problem I am running into and will verify it as soon as I get a chance. The servers should be 4755, but are 0755 after the install on my system. Cheers, -- Oliver To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 6 08:39:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA07773 for freebsd-current-outgoing; Mon, 6 Apr 1998 08:39:38 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.atipa.com (altrox.atipa.com [208.128.22.34]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id IAA07766 for ; Mon, 6 Apr 1998 08:39:33 -0700 (PDT) (envelope-from freebsd@atipa.com) Received: (qmail 6757 invoked by uid 1017); 6 Apr 1998 14:37:04 -0000 Date: Mon, 6 Apr 1998 08:37:04 -0600 (MDT) From: Atipa To: Oliver Banta cc: freebsd-current@FreeBSD.ORG Subject: Re: XFree86 3.3.2 install. 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 There was a security hole in XFree, so they removed the setuid bit. You should either use xdm or their wrapper that comes with the package. See release notes for details. Regards, Kevin On Mon, 6 Apr 1998, Oliver Banta wrote: > Can all of you who are having problems after installing XFree86 3.3.2 > from the ports collection check the permissions on the X Servers after > the install? I am almost positive this is the problem I am running into > and will verify it as soon as I get a chance. > > The servers should be 4755, but are 0755 after the install on my system. > > Cheers, > -- Oliver > > 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 Apr 6 09:43:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA14439 for freebsd-current-outgoing; Mon, 6 Apr 1998 09:43:53 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail3.sirius.com (mail3.sirius.com [205.134.253.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA14429 for ; Mon, 6 Apr 1998 09:43:47 -0700 (PDT) (envelope-from parag@mail.codegen.com) Received: from [192.168.100.101] (ppp-asok04--200.sirius.net [205.134.244.200]) by mail3.sirius.com (8.8.7/Sirius-8.8.7-97.08.12) with SMTP id JAA18298; Mon, 6 Apr 1998 09:43:22 -0700 (PDT) Message-Id: <199804061643.JAA18298@mail3.sirius.com> Subject: Re: Questions for PCI-IDE driver owner Date: Mon, 6 Apr 1998 08:44:51 -0800 x-sender: parag@mail.codegen.com x-mailer: Claris Emailer 2.0v3, January 22, 1998 From: Parag Patel To: "Philippe Regnauld" , Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 4/5/98 11:26 PM, Philippe Regnauld (regnauld@deepo.prosa.dk) said: > I am amused :-) : > > [-- Attachment #2: dmesg.SIT --] > [-- Type: application/octet-stream, Encoding: base64, Size: 5.5K --] > > file dmesg.SIT: > > dmesg.SIT: StuffIt (macintosh) text Whoops. Well, I got it half-right anyway - at least it was Base-64 and not BinHex. I use a Mac for day-to-day work. :-) Here it is in plain text. -- Parag Patel Apr 5 13:49:11 beanhead /kernel: Copyright (c) 1992-1998 FreeBSD Inc. Apr 5 13:49:11 beanhead /kernel: Copyright (c) 1982, 1986, 1989, 1991, 1993 Apr 5 13:49:11 beanhead /kernel: The Regents of the University of California. All rights reserved. Apr 5 13:49:11 beanhead /kernel: FreeBSD 3.0-CURRENT #29: Sun Apr 5 14:47:47 PDT 1998 Apr 5 13:49:11 beanhead /kernel: root@pinhead.parag.codegen.com:/usr/u/freebsd/src/sys/compile/BEANHEAD Apr 5 13:49:11 beanhead /kernel: Calibrating clock(s) ... i8254 clock: 1193450 Hz Apr 5 13:49:11 beanhead /kernel: CLK_USE_I8254_CALIBRATION not specified - using default frequency Apr 5 13:49:11 beanhead /kernel: Timecounter "i8254" frequency 1193182 Hz cost 39 ns Apr 5 13:49:11 beanhead /kernel: CPU: i486 DX4 (486-class CPU) Apr 5 13:49:11 beanhead /kernel: Origin = "GenuineIntel" Id = 0x480 Stepping=0 Apr 5 13:49:11 beanhead /kernel: Features=0x3 Apr 5 13:49:11 beanhead /kernel: real memory = 33554432 (32768K bytes) Apr 5 13:49:11 beanhead /kernel: Physical memory chunk(s): Apr 5 13:49:11 beanhead /kernel: 0x00001000 - 0x0009ffff, 651264 bytes (159 pages) Apr 5 13:49:11 beanhead /kernel: 0x00262000 - 0x01ffdfff, 31047680 bytes (7580 pages) Apr 5 13:49:11 beanhead /kernel: avail memory = 30240768 (29532K bytes) Apr 5 13:49:11 beanhead /kernel: Found BIOS32 Service Directory header at 0xf00fb880 Apr 5 13:49:11 beanhead /kernel: Entry = 0xfbd20 (0xf00fbd20) Rev = 0 Len = 1 Apr 5 13:49:11 beanhead /kernel: PCI BIOS entry at 0xbd50 Apr 5 13:49:11 beanhead /kernel: Other BIOS signatures found: Apr 5 13:49:11 beanhead /kernel: ACPI: 00000000 Apr 5 13:49:11 beanhead /kernel: $PnP: 00000000 Apr 5 13:49:11 beanhead /kernel: pci_open(1): mode 1 addr port (0x0cf8) is 0x80002844 Apr 5 13:49:11 beanhead /kernel: pci_open(1a): mode1res=0x80000000 (0x80000000) Apr 5 13:49:11 beanhead /kernel: pci_cfgcheck: device 0 1 2 3 4 5 [class=060000] [hdr=00] is there (id=04961039) Apr 5 13:49:11 beanhead /kernel: Probing for devices on PCI bus 0: Apr 5 13:49:11 beanhead /kernel: found-> vendor=0x1039, dev=0x0496, revid=0x31 Apr 5 13:49:11 beanhead /kernel: class=06-00-00, hdrtype=0x00, mfdev=0 Apr 5 13:49:11 beanhead /kernel: chip0: rev 0x31 on pci0.5.0 Apr 5 13:49:11 beanhead /kernel: found-> vendor=0x5333, dev=0x88f0, revid=0x00 Apr 5 13:49:11 beanhead /kernel: class=03-00-00, hdrtype=0x00, mfdev=0 Apr 5 13:49:11 beanhead /kernel: intpin=a, irq=9 Apr 5 13:49:11 beanhead /kernel: map[0]: type 1, range 32, base f0000000, size 25 Apr 5 13:49:11 beanhead /kernel: vga0: rev 0x00 int a irq 9 on pci0.11.0 Apr 5 13:49:11 beanhead /kernel: found-> vendor=0x1000, dev=0x0001, revid=0x12 Apr 5 13:49:11 beanhead /kernel: class=01-00-00, hdrtype=0x00, mfdev=0 Apr 5 13:49:11 beanhead /kernel: intpin=a, irq=10 Apr 5 13:49:11 beanhead /kernel: map[0]: type 4, range 32, base 00006000, size 8 Apr 5 13:49:11 beanhead /kernel: map[1]: type 1, range 32, base f2000000, size 8 Apr 5 13:49:11 beanhead /kernel: ncr0: rev 0x12 int a irq 10 on pci0.13.0 Apr 5 13:49:11 beanhead /kernel: ncr0: minsync=25, maxsync=206, maxoffs=8, 16 dwords burst, normal dma fifo Apr 5 13:49:12 beanhead /kernel: ncr0: single-ended, open drain IRQ driver Apr 5 13:49:12 beanhead /kernel: ncr0: restart (scsi reset). Apr 5 13:49:12 beanhead /kernel: ncr0 scanning for targets 0..6 (V2 pl24 96/12/14) Apr 5 13:49:12 beanhead /kernel: ncr0: waiting for scsi devices to settle Apr 5 13:49:12 beanhead /kernel: scbus0 at ncr0 bus 0 Apr 5 13:49:12 beanhead /kernel: cd0 at scbus0 target 2 lun 0 Apr 5 13:49:12 beanhead /kernel: cd0: type 5 removable SCSI 2 Apr 5 13:49:12 beanhead /kernel: cd0: CD-ROM Apr 5 13:49:12 beanhead /kernel: cd0: NCR quirks=0x2 Apr 5 13:49:12 beanhead /kernel: Apr 5 13:49:12 beanhead /kernel: cd0: asynchronous. Apr 5 13:49:12 beanhead /kernel: can't get the size Apr 5 13:49:12 beanhead /kernel: found-> vendor=0x1095, dev=0x0646, revid=0x05 Apr 5 13:49:12 beanhead /kernel: class=01-04-00, hdrtype=0x00, mfdev=0 Apr 5 13:49:12 beanhead /kernel: intpin=a, irq=11 Apr 5 13:49:12 beanhead /kernel: map[0]: type 4, range 32, base 00006100, size 3 Apr 5 13:49:12 beanhead /kernel: map[1]: type 4, range 32, base 00006200, size 2 Apr 5 13:49:12 beanhead /kernel: map[2]: type 4, range 32, base 00006300, size 3 Apr 5 13:49:12 beanhead /kernel: map[3]: type 4, range 32, base 00006400, size 2 Apr 5 13:49:12 beanhead /kernel: map[4]: type 4, range 32, base 00006500, size 4 Apr 5 13:49:12 beanhead /kernel: ide_pci0: rev 0x05 int a irq 11 on pci0.15.0 Apr 5 13:49:12 beanhead /kernel: ide_pci0: adding drives to controller 0: 0 Apr 5 13:49:12 beanhead /kernel: cmd646_status: 0:0 register dump: Apr 5 13:49:12 beanhead /kernel: 0: 6461095 2900007 1040005 2000 Apr 5 13:49:12 beanhead /kernel: 10: 6101 6201 6301 6401 Apr 5 13:49:12 beanhead /kernel: 20: 6501 0 0 6461095 Apr 5 13:49:12 beanhead /kernel: 30: 0 60 0 402010b Apr 5 13:49:12 beanhead /kernel: 40: 0 0 0 0 Apr 5 13:49:12 beanhead /kernel: 50:c000ec44 cc00c000 4000 0 Apr 5 13:49:12 beanhead /kernel: 60: 6010001 80006000 0 0 Apr 5 13:49:12 beanhead /kernel: 70:f3640408 8d108 f0000008 fd9ffe5c Apr 5 13:49:12 beanhead /kernel: cmd646_status: 0:1 register dump: Apr 5 13:49:12 beanhead /kernel: 0: 6461095 2900007 1040005 2000 Apr 5 13:49:12 beanhead /kernel: 10: 6101 6201 6301 6401 Apr 5 13:49:12 beanhead /kernel: 20: 6501 0 0 6461095 Apr 5 13:49:12 beanhead /kernel: 30: 0 60 0 402010b Apr 5 13:49:12 beanhead /kernel: 40: 0 0 0 0 Apr 5 13:49:12 beanhead /kernel: 50:c000ec44 cc00c000 4000 0 Apr 5 13:49:12 beanhead /kernel: 60: 6010001 80006000 0 0 Apr 5 13:49:12 beanhead /kernel: 70:f3640408 8d108 f0000008 fd9ffe5c Apr 5 13:49:12 beanhead /kernel: ide_pci: busmaster 0 status: 64 from port: 00006502 Apr 5 13:49:12 beanhead /kernel: ide_pci: ide0:0 has been configured for DMA by BIOS Apr 5 13:49:12 beanhead /kernel: ide_pci: ide0:1 has been configured for DMA by BIOS Apr 5 13:49:12 beanhead /kernel: cmd646_status: 1:0 register dump: Apr 5 13:49:12 beanhead /kernel: 0: 6461095 2900007 1040005 2000 Apr 5 13:49:12 beanhead /kernel: 10: 6101 6201 6301 6401 Apr 5 13:49:12 beanhead /kernel: 20: 6501 0 0 6461095 Apr 5 13:49:12 beanhead /kernel: 30: 0 60 0 402010b Apr 5 13:49:12 beanhead /kernel: 40: 0 0 0 0 Apr 5 13:49:12 beanhead /kernel: 50:c000ec44 cc00c000 4000 0 Apr 5 13:49:13 beanhead /kernel: 60: 6010001 80006000 0 0 Apr 5 13:49:13 beanhead /kernel: 70:f3640408 8d108 f0000008 fd9ffe5c Apr 5 13:49:13 beanhead /kernel: cmd646_status: 1:1 register dump: Apr 5 13:49:13 beanhead /kernel: 0: 6461095 2900007 1040005 2000 Apr 5 13:49:13 beanhead /kernel: 10: 6101 6201 6301 6401 Apr 5 13:49:13 beanhead /kernel: 20: 6501 0 0 6461095 Apr 5 13:49:13 beanhead /kernel: 30: 0 60 0 402010b Apr 5 13:49:13 beanhead /kernel: 40: 0 0 0 0 Apr 5 13:49:13 beanhead /kernel: 50:c000ec44 cc00c000 4000 0 Apr 5 13:49:13 beanhead /kernel: 60: 6010001 80006000 0 0 Apr 5 13:49:13 beanhead /kernel: 70:f3640408 8d108 f0000008 fd9ffe5c Apr 5 13:49:13 beanhead /kernel: ide_pci: busmaster 1 status: 00 from port: 0000650a Apr 5 13:49:13 beanhead /kernel: Probing for devices on the ISA bus: Apr 5 13:49:13 beanhead /kernel: sc0: the current keyboard controller command byte 0045 Apr 5 13:49:13 beanhead /kernel: kbdio: DIAGNOSE status:0055 Apr 5 13:49:13 beanhead /kernel: kbdio: TEST_KBD_PORT status:0000 Apr 5 13:49:13 beanhead /kernel: kbdio: RESET_KBD return code:00fa Apr 5 13:49:13 beanhead /kernel: kbdio: RESET_KBD status:00aa Apr 5 13:49:13 beanhead /kernel: sc0 at 0x60-0x6f irq 1 on motherboard Apr 5 13:49:13 beanhead /kernel: sc0: BIOS video mode:3 Apr 5 13:49:13 beanhead /kernel: sc0: VGA registers upon power-up Apr 5 13:49:13 beanhead /kernel: 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 Apr 5 13:49:13 beanhead /kernel: bf 1f 00 4f 0d 0e 00 00 07 80 9c 8e 8f 28 1f 96 Apr 5 13:49:13 beanhead /kernel: b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c Apr 5 13:49:13 beanhead /kernel: 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff Apr 5 13:49:13 beanhead /kernel: sc0: video mode:24 Apr 5 13:49:13 beanhead /kernel: sc0: VGA registers in BIOS for mode:24 Apr 5 13:49:13 beanhead /kernel: 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 Apr 5 13:49:13 beanhead /kernel: bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 Apr 5 13:49:13 beanhead /kernel: b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c Apr 5 13:49:13 beanhead /kernel: 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff Apr 5 13:49:13 beanhead /kernel: sc0: VGA registers to be used for mode:24 Apr 5 13:49:13 beanhead /kernel: 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 Apr 5 13:49:13 beanhead /kernel: bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 Apr 5 13:49:13 beanhead /kernel: b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c Apr 5 13:49:13 beanhead /kernel: 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff Apr 5 13:49:13 beanhead /kernel: sc0: rows_offset:1 Apr 5 13:49:13 beanhead /kernel: sc0: VGA color <16 virtual consoles, flags=0x0> Apr 5 13:49:13 beanhead /kernel: ed0 at 0x280-0x29f irq 5 on isa Apr 5 13:49:13 beanhead /kernel: ed0: address 00:00:b4:22:eb:ee, type NE2000 (16 bit) Apr 5 13:49:13 beanhead /kernel: sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa Apr 5 13:49:13 beanhead /kernel: sio0: type 16550A Apr 5 13:49:13 beanhead /kernel: sio1 at 0x2f8-0x2ff irq 3 on isa Apr 5 13:49:13 beanhead /kernel: sio1: type 16550A Apr 5 13:49:13 beanhead /kernel: lpt0 at 0x378-0x37f irq 7 on isa Apr 5 13:49:13 beanhead /kernel: lpt0: Interrupt-driven port Apr 5 13:49:13 beanhead /kernel: lp0: TCP/IP capable interface Apr 5 13:49:13 beanhead /kernel: fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa Apr 5 13:49:13 beanhead /kernel: fd0: 1.44MB 3.5in Apr 5 13:49:13 beanhead /kernel: ide_pci_candma: 0:1 iobase_wd=6100 unit=0 cfr=c000ec44 Apr 5 13:49:14 beanhead /kernel: wdc0 at 0x6100-0x6107 flags 0xa0ffa0ff on isa Apr 5 13:49:14 beanhead /kernel: ide_pci_candma: 0:1 iobase_wd=6100 unit=0 cfr=c000ec44 Apr 5 13:49:14 beanhead /kernel: ide_pci_dmainit: BMISTA=64 Apr 5 13:49:14 beanhead /kernel: cmd646_dmainit: BMISTA=64 udma_mode=2 pio_mode=4 mwdma_mode=2 Apr 5 13:49:14 beanhead /kernel: cmd646_status: 0:1 register dump: Apr 5 13:49:14 beanhead /kernel: 0: 6461095 2900007 1040005 2000 Apr 5 13:49:14 beanhead /kernel: 10: 6101 6201 6301 6401 Apr 5 13:49:14 beanhead /kernel: 20: 6501 0 0 6461095 Apr 5 13:49:14 beanhead /kernel: 30: 0 60 0 402010b Apr 5 13:49:14 beanhead /kernel: 40: 0 0 0 0 Apr 5 13:49:14 beanhead /kernel: 50:c000ec40 cc00c000 4000 0 Apr 5 13:49:14 beanhead /kernel: 60: 6010001 80006000 0 0 Apr 5 13:49:14 beanhead /kernel: 70:f3600008 8d108 f0000008 fd9ffe5c Apr 5 13:49:14 beanhead /kernel: wd0: wdsetmode() setting transfer mode to 42 Apr 5 13:49:14 beanhead /kernel: wdc0: unit 0 (wd0): , DMA, 32-bit, multi-block-16 Apr 5 13:49:14 beanhead /kernel: wd0: 3079MB (6306048 sectors), 6256 cyls, 16 heads, 63 S/T, 512 B/S Apr 5 13:49:14 beanhead /kernel: wd0: ATA INQUIRE valid = 0007, dmamword = 0407, apio = 0003, udma = 0007 Apr 5 13:49:14 beanhead /kernel: npx0 on motherboard Apr 5 13:49:14 beanhead /kernel: npx0: INT 16 interface Apr 5 13:49:14 beanhead /kernel: imasks: bio c0080c40, tty c00700ba, net c00700ba Apr 5 13:49:14 beanhead /kernel: BIOS Geometries: Apr 5 13:49:14 beanhead /kernel: 0:030c7f3f 0..780=781 cylinders, 0..127=128 heads, 1..63=63 sectors Apr 5 13:49:14 beanhead /kernel: 0 accounted for Apr 5 13:49:14 beanhead /kernel: Device configuration finished. Apr 5 13:49:14 beanhead /kernel: new masks: bio c0080c40, tty c00700ba, net c00700ba Apr 5 13:49:14 beanhead /kernel: Considering NFS root f/s. Apr 5 13:49:14 beanhead /kernel: NFS ROOT: 192.168.100.102:/src/diskless_root Apr 5 13:49:14 beanhead /kernel: NFS SWAP: 192.168.100.102:/src/diskless_root Apr 5 13:49:22 beanhead login: ROOT LOGIN (su) ON ttyv0 Apr 5 13:49:25 beanhead /kernel: ide_pci_dmadone: status=0 iobase_bm=6500 BMICOM=8 Apr 5 13:49:26 beanhead /kernel: cmd646_status: 0:1 register dump: Apr 5 13:49:26 beanhead /kernel: 0: 6461095 2900007 1040005 2000 Apr 5 13:49:26 beanhead /kernel: 10: 6101 6201 6301 6401 Apr 5 13:49:26 beanhead /kernel: 20: 6501 0 0 6461095 Apr 5 13:49:26 beanhead /kernel: 30: 0 60 0 402010b Apr 5 13:49:26 beanhead /kernel: 40: 0 0 0 0 Apr 5 13:49:26 beanhead /kernel: 50:c000ec44 cc00c000 4000 0 Apr 5 13:49:26 beanhead /kernel: 60: 6010001 80006000 0 0 Apr 5 13:49:26 beanhead /kernel: 70:f3600408 8d108 f0000008 fd9ffe5c Apr 5 13:49:26 beanhead /kernel: ide_pci_dmaverify: badfu=0 Apr 5 13:49:26 beanhead /kernel: ide_pci_dmassetup: iobase_bm=6500 BMICOM=8 Apr 5 13:49:26 beanhead /kernel: cmd646_status: 0:1 register dump: Apr 5 13:49:26 beanhead /kernel: 0: 6461095 2900007 1040005 2000 Apr 5 13:49:26 beanhead /kernel: 10: 6101 6201 6301 6401 Apr 5 13:49:26 beanhead /kernel: 20: 6501 0 0 6461095 Apr 5 13:49:26 beanhead /kernel: 30: 0 60 0 402010b Apr 5 13:49:26 beanhead /kernel: 40: 0 0 0 0 Apr 5 13:49:26 beanhead /kernel: 50:c000ec44 cc00c000 4000 0 Apr 5 13:49:26 beanhead /kernel: 60: 6010001 80006000 0 0 Apr 5 13:49:26 beanhead /kernel: 70:f3600408 8d108 f0000008 fd9ffe5c Apr 5 13:49:26 beanhead /kernel: ide_pci_dmastart: iobase_bm=6500 BMICOM=8 Apr 5 13:49:26 beanhead /kernel: cmd646_status: 0:1 register dump: Apr 5 13:49:26 beanhead /kernel: 0: 6461095 2900007 1040005 2000 Apr 5 13:49:26 beanhead /kernel: 10: 6101 6201 6301 6401 Apr 5 13:49:26 beanhead /kernel: 20: 6501 0 0 6461095 Apr 5 13:49:26 beanhead /kernel: 30: 0 60 0 402010b Apr 5 13:49:26 beanhead /kernel: 40: 0 0 0 0 Apr 5 13:49:26 beanhead /kernel: 50:c000ec44 cc00c000 4000 0 Apr 5 13:49:26 beanhead /kernel: 60: 6010001 80006000 0 0 Apr 5 13:49:26 beanhead /kernel: 70:f3600408 8d108 f0000008 fd9ffe5c Apr 5 13:49:26 beanhead /kernel: ide_pci_dmadone: status=4 iobase_bm=6500 BMICOM=9 Apr 5 13:49:26 beanhead /kernel: cmd646_status: 0:1 register dump: Apr 5 13:49:26 beanhead /kernel: 0: 6461095 2900007 1040005 2000 Apr 5 13:49:26 beanhead /kernel: 10: 6101 6201 6301 6401 Apr 5 13:49:26 beanhead /kernel: 20: 6501 0 0 6461095 Apr 5 13:49:26 beanhead /kernel: 30: 0 60 0 402010b Apr 5 13:49:26 beanhead /kernel: 40: 0 0 0 0 Apr 5 13:49:26 beanhead /kernel: 50:c000ec44 cc00c000 4000 0 Apr 5 13:49:26 beanhead /kernel: 60: 6010001 80006000 0 0 Apr 5 13:49:26 beanhead /kernel: 70:f3640409 8d108 f0000008 fd9ffe5c Apr 5 13:49:26 beanhead /kernel: wd0s1: type 0x6, start 63, end = 4193279, size 4193217 : OK Apr 5 13:49:26 beanhead /kernel: wd0s2: type 0xb5, start 4193280, end = 6306047, size 2112768 : OK Apr 5 13:49:26 beanhead /kernel: ide_pci_dmadone: status=4 iobase_bm=6500 BMICOM=8 Apr 5 13:49:26 beanhead /kernel: cmd646_status: 0:1 register dump: Apr 5 13:49:26 beanhead /kernel: 0: 6461095 2900007 1040005 2000 Apr 5 13:49:27 beanhead /kernel: 10: 6101 6201 6301 6401 Apr 5 13:49:27 beanhead /kernel: 20: 6501 0 0 6461095 Apr 5 13:49:27 beanhead /kernel: 30: 0 60 0 402010b Apr 5 13:49:27 beanhead /kernel: 40: 0 0 0 0 Apr 5 13:49:27 beanhead /kernel: 50:c000ec44 cc00c000 4000 0 Apr 5 13:49:27 beanhead /kernel: 60: 6010001 80006000 0 0 Apr 5 13:49:27 beanhead /kernel: 70:f3640408 8d108 f0000008 fd9ffe5c Apr 5 13:49:27 beanhead /kernel: ide_pci_dmaverify: badfu=0 Apr 5 13:49:27 beanhead /kernel: ide_pci_dmassetup: iobase_bm=6500 BMICOM=8 Apr 5 13:49:27 beanhead /kernel: cmd646_status: 0:1 register dump: Apr 5 13:49:27 beanhead /kernel: 0: 6461095 2900007 1040005 2000 Apr 5 13:49:27 beanhead /kernel: 10: 6101 6201 6301 6401 Apr 5 13:49:27 beanhead /kernel: 20: 6501 0 0 6461095 Apr 5 13:49:27 beanhead /kernel: 30: 0 60 0 402010b Apr 5 13:49:27 beanhead /kernel: 40: 0 0 0 0 Apr 5 13:49:27 beanhead /kernel: 50:c000ec44 cc00c000 4000 0 Apr 5 13:49:27 beanhead /kernel: 60: 6010001 80006000 0 0 Apr 5 13:49:27 beanhead /kernel: 70:f3640408 8d108 f0000008 fd9ffe5c Apr 5 13:49:27 beanhead /kernel: ide_pci_dmastart: iobase_bm=6500 BMICOM=8 Apr 5 13:49:27 beanhead /kernel: cmd646_status: 0:1 register dump: Apr 5 13:49:27 beanhead /kernel: 0: 6461095 2900007 1040005 2000 Apr 5 13:49:27 beanhead /kernel: 10: 6101 6201 6301 6401 Apr 5 13:49:27 beanhead /kernel: 20: 6501 0 0 6461095 Apr 5 13:49:27 beanhead /kernel: 30: 0 60 0 402010b Apr 5 13:49:27 beanhead /kernel: 40: 0 0 0 0 Apr 5 13:49:27 beanhead /kernel: 50:c000ec44 cc00c000 4000 0 Apr 5 13:49:27 beanhead /kernel: 60: 6010001 80006000 0 0 Apr 5 13:49:27 beanhead /kernel: 70:f3600408 8d108 f0000008 fd9ffe5c Apr 5 13:49:27 beanhead /kernel: ide_pci_dmadone: status=4 iobase_bm=6500 BMICOM=9 Apr 5 13:49:27 beanhead /kernel: cmd646_status: 0:1 register dump: Apr 5 13:49:27 beanhead /kernel: 0: 6461095 2900007 1040005 2000 Apr 5 13:49:27 beanhead /kernel: 10: 6101 6201 6301 6401 Apr 5 13:49:27 beanhead /kernel: 20: 6501 0 0 6461095 Apr 5 13:49:27 beanhead /kernel: 30: 0 60 0 402010b Apr 5 13:49:27 beanhead /kernel: 40: 0 0 0 0 Apr 5 13:49:27 beanhead /kernel: 50:c000ec44 cc00c000 4000 0 Apr 5 13:49:27 beanhead /kernel: 60: 6010001 80006000 0 0 Apr 5 13:49:27 beanhead /kernel: 70:f3640409 8d108 f0000008 fd9ffe5c Apr 5 13:49:27 beanhead /kernel: ide_pci_dmadone: status=4 iobase_bm=6500 BMICOM=8 Apr 5 13:49:27 beanhead /kernel: cmd646_status: 0:1 register dump: Apr 5 13:49:27 beanhead /kernel: 0: 6461095 2900007 1040005 2000 Apr 5 13:49:27 beanhead /kernel: 10: 6101 6201 6301 6401 Apr 5 13:49:27 beanhead /kernel: 20: 6501 0 0 6461095 Apr 5 13:49:27 beanhead /kernel: 30: 0 60 0 402010b Apr 5 13:49:27 beanhead /kernel: 40: 0 0 0 0 Apr 5 13:49:27 beanhead /kernel: 50:c000ec44 cc00c000 4000 0 Apr 5 13:49:27 beanhead /kernel: 60: 6010001 80006000 0 0 Apr 5 13:49:27 beanhead /kernel: 70:f3640408 8d108 f0000008 fd9ffe5c Apr 5 13:49:27 beanhead /kernel: ide_pci_dmaverify: badfu=0 Apr 5 13:49:28 beanhead /kernel: ide_pci_dmassetup: iobase_bm=6500 BMICOM=8 Apr 5 13:49:28 beanhead /kernel: cmd646_status: 0:1 register dump: Apr 5 13:49:28 beanhead /kernel: 0: 6461095 2900007 1040005 2000 Apr 5 13:49:28 beanhead /kernel: 10: 6101 6201 6301 6401 Apr 5 13:49:28 beanhead /kernel: 20: 6501 0 0 6461095 Apr 5 13:49:28 beanhead /kernel: 30: 0 60 0 402010b Apr 5 13:49:28 beanhead /kernel: 40: 0 0 0 0 Apr 5 13:49:28 beanhead /kernel: 50:c000ec44 cc00c000 4000 0 Apr 5 13:49:28 beanhead /kernel: 60: 6010001 80006000 0 0 Apr 5 13:49:28 beanhead /kernel: 70:f3640408 8d108 f0000008 fd9ffe5c Apr 5 13:49:28 beanhead /kernel: ide_pci_dmastart: iobase_bm=6500 BMICOM=8 Apr 5 13:49:28 beanhead /kernel: cmd646_status: 0:1 register dump: Apr 5 13:49:28 beanhead /kernel: 0: 6461095 2900007 1040005 2000 Apr 5 13:49:28 beanhead /kernel: 10: 6101 6201 6301 6401 Apr 5 13:49:28 beanhead /kernel: 20: 6501 0 0 6461095 Apr 5 13:49:28 beanhead /kernel: 30: 0 60 0 402010b Apr 5 13:49:28 beanhead /kernel: 40: 0 0 0 0 Apr 5 13:49:28 beanhead /kernel: 50:c000ec44 cc00c000 4000 0 Apr 5 13:49:28 beanhead /kernel: 60: 6010001 80006000 0 0 Apr 5 13:49:28 beanhead /kernel: 70:f3600408 8d108 f0000008 fd9ffe5c Apr 5 13:49:28 beanhead /kernel: ide_pci_dmadone: status=4 iobase_bm=6500 BMICOM=9 Apr 5 13:49:28 beanhead /kernel: cmd646_status: 0:1 register dump: Apr 5 13:49:29 beanhead /kernel: 0: 6461095 2900007 1040005 2000 Apr 5 13:49:29 beanhead /kernel: 10: 6101 6201 6301 6401 Apr 5 13:49:29 beanhead /kernel: 20: 6501 0 0 6461095 Apr 5 13:49:29 beanhead /kernel: 30: 0 60 0 402010b Apr 5 13:49:29 beanhead /kernel: 40: 0 0 0 0 Apr 5 13:49:29 beanhead /kernel: 50:c000ec44 cc00c000 4000 0 Apr 5 13:49:29 beanhead /kernel: 60: 6010001 80006000 0 0 Apr 5 13:49:29 beanhead /kernel: 70:f3640409 8d108 f0000008 fd9ffe5c Apr 5 13:49:29 beanhead /kernel: ide_pci_dmaverify: badfu=0 Apr 5 13:49:29 beanhead /kernel: ide_pci_dmassetup: iobase_bm=6500 BMICOM=8 Apr 5 13:49:29 beanhead /kernel: cmd646_status: 0:1 register dump: Apr 5 13:49:29 beanhead /kernel: 0: 6461095 2900007 1040005 2000 Apr 5 13:49:29 beanhead /kernel: 10: 6101 6201 6301 6401 Apr 5 13:49:29 beanhead /kernel: 20: 6501 0 0 6461095 Apr 5 13:49:29 beanhead /kernel: 30: 0 60 0 402010b Apr 5 13:49:29 beanhead /kernel: 40: 0 0 0 0 Apr 5 13:49:29 beanhead /kernel: 50:c000ec44 cc00c000 4000 0 Apr 5 13:49:29 beanhead /kernel: 60: 6010001 80006000 0 0 Apr 5 13:49:29 beanhead /kernel: 70:f3640408 8d108 f0000008 fd9ffe5c Apr 5 13:49:29 beanhead /kernel: ide_pci_dmastart: iobase_bm=6500 BMICOM=8 Apr 5 13:49:29 beanhead /kernel: cmd646_status: 0:1 register dump: Apr 5 13:49:29 beanhead /kernel: 0: 6461095 2900007 1040005 2000 Apr 5 13:49:29 beanhead /kernel: 10: 6101 6201 6301 6401 Apr 5 13:49:29 beanhead /kernel: 20: 6501 0 0 6461095 Apr 5 13:49:29 beanhead /kernel: 30: 0 60 0 402010b Apr 5 13:49:29 beanhead /kernel: 40: 0 0 0 0 Apr 5 13:49:30 beanhead /kernel: 50:c000ec44 cc00c000 4000 0 Apr 5 13:49:30 beanhead /kernel: 60: 6010001 80006000 0 0 Apr 5 13:49:30 beanhead /kernel: 70:f3600408 8d108 f0000008 fd9ffe5c Apr 5 13:49:30 beanhead /kernel: ide_pci_dmadone: status=4 iobase_bm=6500 BMICOM=9 Apr 5 13:49:30 beanhead /kernel: cmd646_status: 0:1 register dump: Apr 5 13:49:30 beanhead /kernel: 0: 6461095 2900007 1040005 2000 Apr 5 13:49:30 beanhead /kernel: 10: 6101 6201 6301 6401 Apr 5 13:49:30 beanhead /kernel: 20: 6501 0 0 6461095 Apr 5 13:49:30 beanhead /kernel: 30: 0 60 0 402010b Apr 5 13:49:30 beanhead /kernel: 40: 0 0 0 0 Apr 5 13:49:30 beanhead /kernel: 50:c000ec44 cc00c000 4000 0 Apr 5 13:49:30 beanhead /kernel: 60: 6010001 80006000 0 0 Apr 5 13:49:30 beanhead /kernel: 70:f3640409 8d108 f0000008 fd9ffe5c Apr 5 13:49:30 beanhead /kernel: ide_pci_dmadone: status=4 iobase_bm=6500 BMICOM=8 Apr 5 13:49:30 beanhead /kernel: cmd646_status: 0:1 register dump: Apr 5 13:49:30 beanhead /kernel: 0: 6461095 2900007 1040005 2000 Apr 5 13:49:30 beanhead /kernel: 10: 6101 6201 6301 6401 Apr 5 13:49:30 beanhead /kernel: 20: 6501 0 0 6461095 Apr 5 13:49:30 beanhead /kernel: 30: 0 60 0 402010b Apr 5 13:49:30 beanhead /kernel: 40: 0 0 0 0 Apr 5 13:49:30 beanhead /kernel: 50:c000ec44 cc00c000 4000 0 Apr 5 13:49:30 beanhead /kernel: 60: 6010001 80006000 0 0 Apr 5 13:49:30 beanhead /kernel: 70:f3640408 8d108 f0000008 fd9ffe5c Apr 5 13:49:30 beanhead /kernel: ide_pci_dmaverify: badfu=0 Apr 5 13:49:30 beanhead /kernel: ide_pci_dmassetup: iobase_bm=6500 BMICOM=8 Apr 5 13:49:30 beanhead /kernel: cmd646_status: 0:1 register dump: Apr 5 13:49:30 beanhead /kernel: 0: 6461095 2900007 1040005 2000 Apr 5 13:49:30 beanhead /kernel: 10: 6101 6201 6301 6401 Apr 5 13:49:30 beanhead /kernel: 20: 6501 0 0 6461095 Apr 5 13:49:30 beanhead /kernel: 30: 0 60 0 402010b Apr 5 13:49:30 beanhead /kernel: 40: 0 0 0 0 Apr 5 13:49:30 beanhead /kernel: 50:c000ec44 cc00c000 4000 0 Apr 5 13:49:30 beanhead /kernel: 60: 6010001 80006000 0 0 Apr 5 13:49:30 beanhead /kernel: 70:f3640408 8d108 f0000008 fd9ffe5c Apr 5 13:49:30 beanhead /kernel: ide_pci_dmastart: iobase_bm=6500 BMICOM=8 Apr 5 13:49:30 beanhead /kernel: cmd646_status: 0:1 register dump: Apr 5 13:49:30 beanhead /kernel: 0: 6461095 2900007 1040005 2000 Apr 5 13:49:30 beanhead /kernel: 10: 6101 6201 6301 6401 Apr 5 13:49:30 beanhead /kernel: 20: 6501 0 0 6461095 Apr 5 13:49:30 beanhead /kernel: 30: 0 60 0 402010b Apr 5 13:49:30 beanhead /kernel: 40: 0 0 0 0 Apr 5 13:49:30 beanhead /kernel: 50:c000ec44 cc00c000 4000 0 Apr 5 13:49:30 beanhead /kernel: 60: 6010001 80006000 0 0 Apr 5 13:49:30 beanhead /kernel: 70:f3600408 8d108 f0000008 fd9ffe5c Apr 5 13:49:30 beanhead /kernel: ide_pci_dmadone: status=4 iobase_bm=6500 BMICOM=9 Apr 5 13:49:30 beanhead /kernel: cmd646_status: 0:1 register dump: Apr 5 13:49:30 beanhead /kernel: 0: 6461095 2900007 1040005 2000 Apr 5 13:49:31 beanhead /kernel: 10: 6101 6201 6301 6401 Apr 5 13:49:31 beanhead /kernel: 20: 6501 0 0 6461095 Apr 5 13:49:31 beanhead /kernel: 30: 0 60 0 402010b Apr 5 13:49:31 beanhead /kernel: 40: 0 0 0 0 Apr 5 13:49:31 beanhead /kernel: 50:c000ec44 cc00c000 4000 0 Apr 5 13:49:31 beanhead /kernel: 60: 6010001 80006000 0 0 Apr 5 13:49:31 beanhead /kernel: 70:f3640409 8d108 f0000008 fd9ffe5c Apr 5 13:49:31 beanhead /kernel: wd0s1: type 0x6, start 63, end = 4193279, size 4193217 : OK Apr 5 13:49:31 beanhead /kernel: wd0s2: type 0xb5, start 4193280, end = 6306047, size 2112768 : OK Apr 5 13:49:31 beanhead /kernel: ide_pci_dmadone: status=4 iobase_bm=6500 BMICOM=8 Apr 5 13:49:31 beanhead /kernel: cmd646_status: 0:1 register dump: Apr 5 13:49:31 beanhead /kernel: 0: 6461095 2900007 1040005 2000 Apr 5 13:49:31 beanhead /kernel: 10: 6101 6201 6301 6401 Apr 5 13:49:31 beanhead /kernel: 20: 6501 0 0 6461095 Apr 5 13:49:31 beanhead /kernel: 30: 0 60 0 402010b Apr 5 13:49:31 beanhead /kernel: 40: 0 0 0 0 Apr 5 13:49:31 beanhead /kernel: 50:c000ec44 cc00c000 4000 0 Apr 5 13:49:31 beanhead /kernel: 60: 6010001 80006000 0 0 Apr 5 13:49:31 beanhead /kernel: 70:f3640408 8d108 f0000008 fd9ffe5c Apr 5 13:49:31 beanhead /kernel: ide_pci_dmaverify: badfu=0 Apr 5 13:49:31 beanhead /kernel: ide_pci_dmassetup: iobase_bm=6500 BMICOM=8 Apr 5 13:49:31 beanhead /kernel: cmd646_status: 0:1 register dump: Apr 5 13:49:31 beanhead /kernel: 0: 6461095 2900007 1040005 2000 Apr 5 13:49:31 beanhead /kernel: 10: 6101 6201 6301 6401 Apr 5 13:49:31 beanhead /kernel: 20: 6501 0 0 6461095 Apr 5 13:49:31 beanhead /kernel: 30: 0 60 0 402010b Apr 5 13:49:31 beanhead /kernel: 40: 0 0 0 0 Apr 5 13:49:31 beanhead /kernel: 50:c000ec44 cc00c000 4000 0 Apr 5 13:49:32 beanhead /kernel: 60: 6010001 80006000 0 0 Apr 5 13:49:32 beanhead /kernel: 70:f3640408 8d108 f0000008 fd9ffe5c Apr 5 13:49:32 beanhead /kernel: ide_pci_dmastart: iobase_bm=6500 BMICOM=8 Apr 5 13:49:32 beanhead /kernel: cmd646_status: 0:1 register dump: Apr 5 13:49:32 beanhead /kernel: 0: 6461095 2900007 1040005 2000 Apr 5 13:49:32 beanhead /kernel: 10: 6101 6201 6301 6401 Apr 5 13:49:32 beanhead /kernel: 20: 6501 0 0 6461095 Apr 5 13:49:32 beanhead /kernel: 30: 0 60 0 402010b Apr 5 13:49:32 beanhead /kernel: 40: 0 0 0 0 Apr 5 13:49:32 beanhead /kernel: 50:c000ec44 cc00c000 4000 0 Apr 5 13:49:32 beanhead /kernel: 60: 6010001 80006000 0 0 Apr 5 13:49:32 beanhead /kernel: 70:f3600408 8d108 f0000008 fd9ffe5c Apr 5 13:49:32 beanhead /kernel: ide_pci_dmadone: status=4 iobase_bm=6500 BMICOM=9 Apr 5 13:49:32 beanhead /kernel: cmd646_status: 0:1 register dump: Apr 5 13:49:32 beanhead /kernel: 0: 6461095 2900007 1040005 2000 Apr 5 13:49:32 beanhead /kernel: 10: 6101 6201 6301 6401 Apr 5 13:49:32 beanhead /kernel: 20: 6501 0 0 6461095 Apr 5 13:49:32 beanhead /kernel: 30: 0 60 0 402010b Apr 5 13:49:32 beanhead /kernel: 40: 0 0 0 0 Apr 5 13:49:32 beanhead /kernel: 50:c000ec44 cc00c000 4000 0 Apr 5 13:49:32 beanhead /kernel: 60: 6010001 80006000 0 0 Apr 5 13:49:32 beanhead /kernel: 70:f3640409 8d108 f0000008 fd9ffe5c Apr 5 13:49:32 beanhead /kernel: ide_pci_dmadone: status=4 iobase_bm=6500 BMICOM=8 Apr 5 13:49:32 beanhead /kernel: cmd646_status: 0:1 register dump: Apr 5 13:49:32 beanhead /kernel: 0: 6461095 2900007 1040005 2000 Apr 5 13:49:32 beanhead /kernel: 10: 6101 6201 6301 6401 Apr 5 13:49:32 beanhead /kernel: 20: 6501 0 0 6461095 Apr 5 13:49:32 beanhead /kernel: 30: 0 60 0 402010b Apr 5 13:49:32 beanhead /kernel: 40: 0 0 0 0 Apr 5 13:49:32 beanhead /kernel: 50:c000ec44 cc00c000 4000 0 Apr 5 13:49:32 beanhead /kernel: 60: 6010001 80006000 0 0 Apr 5 13:49:32 beanhead /kernel: 70:f3640408 8d108 f0000008 fd9ffe5c Apr 5 13:49:32 beanhead /kernel: ide_pci_dmaverify: badfu=0 Apr 5 13:49:32 beanhead /kernel: ide_pci_dmassetup: iobase_bm=6500 BMICOM=8 Apr 5 13:49:32 beanhead /kernel: cmd646_status: 0:1 register dump: Apr 5 13:49:32 beanhead /kernel: 0: 6461095 2900007 1040005 2000 Apr 5 13:49:32 beanhead /kernel: 10: 6101 6201 6301 6401 Apr 5 13:49:32 beanhead /kernel: 20: 6501 0 0 6461095 Apr 5 13:49:32 beanhead /kernel: 30: 0 60 0 402010b Apr 5 13:49:32 beanhead /kernel: 40: 0 0 0 0 Apr 5 13:49:32 beanhead /kernel: 50:c000ec44 cc00c000 4000 0 Apr 5 13:49:32 beanhead /kernel: 60: 6010001 80006000 0 0 Apr 5 13:49:32 beanhead /kernel: 70:f3640408 8d108 f0000008 fd9ffe5c Apr 5 13:49:32 beanhead /kernel: ide_pci_dmastart: iobase_bm=6500 BMICOM=8 Apr 5 13:49:32 beanhead /kernel: cmd646_status: 0:1 register dump: Apr 5 13:49:32 beanhead /kernel: 0: 6461095 2900007 1040005 2000 Apr 5 13:49:32 beanhead /kernel: 10: 6101 6201 6301 6401 Apr 5 13:49:32 beanhead /kernel: 20: 6501 0 0 6461095 Apr 5 13:49:32 beanhead /kernel: 30: 0 60 0 402010b Apr 5 13:49:32 beanhead /kernel: 40: 0 0 0 0 Apr 5 13:49:33 beanhead /kernel: 50:c000ec44 cc00c000 4000 0 Apr 5 13:49:33 beanhead /kernel: 60: 6010001 80006000 0 0 Apr 5 13:49:33 beanhead /kernel: 70:f3600408 8d108 f0000008 fd9ffe5c Apr 5 13:49:33 beanhead /kernel: ide_pci_dmadone: status=4 iobase_bm=6500 BMICOM=9 Apr 5 13:49:33 beanhead /kernel: cmd646_status: 0:1 register dump: Apr 5 13:49:33 beanhead /kernel: 0: 6461095 2900007 1040005 2000 Apr 5 13:49:33 beanhead /kernel: 10: 6101 6201 6301 6401 Apr 5 13:49:33 beanhead /kernel: 20: 6501 0 0 6461095 Apr 5 13:49:33 beanhead /kernel: 30: 0 60 0 402010b Apr 5 13:49:33 beanhead /kernel: 40: 0 0 0 0 Apr 5 13:49:33 beanhead /kernel: 50:c000ec44 cc00c000 4000 0 Apr 5 13:49:33 beanhead /kernel: 60: 6010001 80006000 0 0 Apr 5 13:49:33 beanhead /kernel: 70:f3640409 8d108 f0000008 fd9ffe5c Apr 5 13:49:33 beanhead /kernel: ide_pci_dmaverify: badfu=0 Apr 5 13:49:33 beanhead /kernel: ide_pci_dmassetup: iobase_bm=6500 BMICOM=8 Apr 5 13:49:33 beanhead /kernel: cmd646_status: 0:1 register dump: Apr 5 13:49:33 beanhead /kernel: 0: 6461095 2900007 1040005 2000 Apr 5 13:49:33 beanhead /kernel: 10: 6101 6201 6301 6401 Apr 5 13:49:33 beanhead /kernel: 20: 6501 0 0 6461095 Apr 5 13:49:33 beanhead /kernel: 30: 0 60 0 402010b Apr 5 13:49:33 beanhead /kernel: 40: 0 0 0 0 Apr 5 13:49:33 beanhead /kernel: 50:c000ec44 cc00c000 4000 0 Apr 5 13:49:33 beanhead /kernel: 60: 6010001 80006000 0 0 Apr 5 13:49:33 beanhead /kernel: 70:f3640408 8d108 f0000008 fd9ffe5c Apr 5 13:49:33 beanhead /kernel: ide_pci_dmastart: iobase_bm=6500 BMICOM=8 Apr 5 13:49:33 beanhead /kernel: cmd646_status: 0:1 register dump: Apr 5 13:49:33 beanhead /kernel: 0: 6461095 2900007 1040005 2000 Apr 5 13:49:33 beanhead /kernel: 10: 6101 6201 6301 6401 Apr 5 13:49:33 beanhead /kernel: 20: 6501 0 0 6461095 Apr 5 13:49:33 beanhead /kernel: 30: 0 60 0 402010b Apr 5 13:49:33 beanhead /kernel: 40: 0 0 0 0 Apr 5 13:49:33 beanhead /kernel: 50:c000ec44 cc00c000 4000 0 Apr 5 13:49:33 beanhead /kernel: 60: 6010001 80006000 0 0 Apr 5 13:49:33 beanhead /kernel: 70:f3600408 8d108 f0000008 fd9ffe5c Apr 5 13:49:33 beanhead /kernel: ide_pci_dmadone: status=4 iobase_bm=6500 BMICOM=9 Apr 5 13:49:33 beanhead /kernel: cmd646_status: 0:1 register dump: Apr 5 13:49:33 beanhead /kernel: 0: 6461095 2900007 1040005 2000 Apr 5 13:49:33 beanhead /kernel: 10: 6101 6201 6301 6401 Apr 5 13:49:33 beanhead /kernel: 20: 6501 0 0 6461095 Apr 5 13:49:33 beanhead /kernel: 30: 0 60 0 402010b Apr 5 13:49:33 beanhead /kernel: 40: 0 0 0 0 Apr 5 13:49:33 beanhead /kernel: 50:c000ec44 cc00c000 4000 0 Apr 5 13:49:33 beanhead /kernel: 60: 6010001 80006000 0 0 Apr 5 13:49:33 beanhead /kernel: 70:f3640409 8d108 f0000008 fd9ffe5c Apr 5 13:49:36 beanhead /kernel: ide_pci_dmadone: status=4 iobase_bm=6500 BMICOM=8 Apr 5 13:49:36 beanhead /kernel: cmd646_status: 0:1 register dump: Apr 5 13:49:36 beanhead /kernel: 0: 6461095 2900007 1040005 2000 Apr 5 13:49:36 beanhead /kernel: 10: 6101 6201 6301 6401 Apr 5 13:49:36 beanhead /kernel: 20: 6501 0 0 6461095 Apr 5 13:49:36 beanhead /kernel: 30: 0 60 0 402010b Apr 5 13:49:36 beanhead /kernel: 40: 0 0 0 0 Apr 5 13:49:36 beanhead /kernel: 50:c000ec44 cc00c000 4000 0 Apr 5 13:49:36 beanhead /kernel: 60: 6010001 80006000 0 0 Apr 5 13:49:36 beanhead /kernel: 70:f3640408 8d108 f0000008 fd9ffe5c Apr 5 13:49:36 beanhead /kernel: ide_pci_dmaverify: badfu=0 Apr 5 13:49:36 beanhead /kernel: ide_pci_dmassetup: iobase_bm=6500 BMICOM=8 Apr 5 13:49:36 beanhead /kernel: cmd646_status: 0:1 register dump: Apr 5 13:49:36 beanhead /kernel: 0: 6461095 2900007 1040005 2000 Apr 5 13:49:36 beanhead /kernel: 10: 6101 6201 6301 6401 Apr 5 13:49:37 beanhead /kernel: 20: 6501 0 0 6461095 Apr 5 13:49:37 beanhead /kernel: 30: 0 60 0 402010b Apr 5 13:49:37 beanhead /kernel: 40: 0 0 0 0 Apr 5 13:49:37 beanhead /kernel: 50:c000ec44 cc00c000 4000 0 Apr 5 13:49:37 beanhead /kernel: 60: 6010001 80006000 0 0 Apr 5 13:49:37 beanhead /kernel: 70:f3640408 8d108 f0000008 fd9ffe5c Apr 5 13:49:37 beanhead /kernel: ide_pci_dmastart: iobase_bm=6500 BMICOM=8 Apr 5 13:49:37 beanhead /kernel: cmd646_status: 0:1 register dump: Apr 5 13:49:37 beanhead /kernel: 0: 6461095 2900007 1040005 2000 Apr 5 13:49:37 beanhead /kernel: 10: 6101 6201 6301 6401 Apr 5 13:49:37 beanhead /kernel: 20: 6501 0 0 6461095 Apr 5 13:49:37 beanhead /kernel: 30: 0 60 0 402010b Apr 5 13:49:37 beanhead /kernel: 40: 0 0 0 0 Apr 5 13:49:37 beanhead /kernel: 50:c000ec44 cc00c000 4000 0 Apr 5 13:49:37 beanhead /kernel: 60: 6010001 80006000 0 0 Apr 5 13:49:37 beanhead /kernel: 70:f3600408 8d108 f0000008 fd9ffe5c Apr 5 13:49:37 beanhead /kernel: ide_pci_dmadone: status=4 iobase_bm=6500 BMICOM=9 Apr 5 13:49:37 beanhead /kernel: cmd646_status: 0:1 register dump: Apr 5 13:49:37 beanhead /kernel: 0: 6461095 2900007 1040005 2000 Apr 5 13:49:37 beanhead /kernel: 10: 6101 6201 6301 6401 Apr 5 13:49:37 beanhead /kernel: 20: 6501 0 0 6461095 Apr 5 13:49:37 beanhead /kernel: 30: 0 60 0 402010b Apr 5 13:49:37 beanhead /kernel: 40: 0 0 0 0 Apr 5 13:49:37 beanhead /kernel: 50:c000ec44 cc00c000 4000 0 Apr 5 13:49:37 beanhead /kernel: 60: 6010001 80006000 0 0 Apr 5 13:49:37 beanhead /kernel: 70:f3640409 8d108 f0000008 fd9ffe5c Apr 5 13:49:37 beanhead /kernel: wd0s1: type 0x6, start 63, end = 4193279, size 4193217 : OK Apr 5 13:49:37 beanhead /kernel: wd0s2: type 0xb5, start 4193280, end = 6306047, size 2112768 : OK Apr 5 13:49:37 beanhead /kernel: ide_pci_dmadone: status=4 iobase_bm=6500 BMICOM=8 Apr 5 13:49:37 beanhead /kernel: cmd646_status: 0:1 register dump: Apr 5 13:49:37 beanhead /kernel: 0: 6461095 2900007 1040005 2000 Apr 5 13:49:37 beanhead /kernel: 10: 6101 6201 6301 6401 Apr 5 13:49:37 beanhead /kernel: 20: 6501 0 0 6461095 Apr 5 13:49:37 beanhead /kernel: 30: 0 60 0 402010b Apr 5 13:49:37 beanhead /kernel: 40: 0 0 0 0 Apr 5 13:49:37 beanhead /kernel: 50:c000ec44 cc00c000 4000 0 Apr 5 13:49:37 beanhead /kernel: 60: 6010001 80006000 0 0 Apr 5 13:49:37 beanhead /kernel: 70:f3640408 8d108 f0000008 fd9ffe5c Apr 5 13:49:37 beanhead /kernel: ide_pci_dmaverify: badfu=0 Apr 5 13:49:37 beanhead /kernel: ide_pci_dmassetup: iobase_bm=6500 BMICOM=8 Apr 5 13:49:37 beanhead /kernel: cmd646_status: 0:1 register dump: Apr 5 13:49:37 beanhead /kernel: 0: 6461095 2900007 1040005 2000 Apr 5 13:49:37 beanhead /kernel: 10: 6101 6201 6301 6401 Apr 5 13:49:37 beanhead /kernel: 20: 6501 0 0 6461095 Apr 5 13:49:37 beanhead /kernel: 30: 0 60 0 402010b Apr 5 13:49:37 beanhead /kernel: 40: 0 0 0 0 Apr 5 13:49:37 beanhead /kernel: 50:c000ec44 cc00c000 4000 0 Apr 5 13:49:37 beanhead /kernel: 60: 6010001 80006000 0 0 Apr 5 13:49:37 beanhead /kernel: 70:f3640408 8d108 f0000008 fd9ffe5c Apr 5 13:49:37 beanhead /kernel: ide_pci_dmastart: iobase_bm=6500 BMICOM=8 Apr 5 13:49:38 beanhead /kernel: cmd646_status: 0:1 register dump: Apr 5 13:49:38 beanhead /kernel: 0: 6461095 2900007 1040005 2000 Apr 5 13:49:38 beanhead /kernel: 10: 6101 6201 6301 6401 Apr 5 13:49:38 beanhead /kernel: 20: 6501 0 0 6461095 Apr 5 13:49:38 beanhead /kernel: 30: 0 60 0 402010b Apr 5 13:49:38 beanhead /kernel: 40: 0 0 0 0 Apr 5 13:49:38 beanhead /kernel: 50:c000ec44 cc00c000 4000 0 Apr 5 13:49:38 beanhead /kernel: 60: 6010001 80006000 0 0 Apr 5 13:49:38 beanhead /kernel: 70:f3600408 8d108 f0000008 fd9ffe5c Apr 5 13:49:38 beanhead /kernel: ide_pci_dmadone: status=4 iobase_bm=6500 BMICOM=9 Apr 5 13:49:38 beanhead /kernel: cmd646_status: 0:1 register dump: Apr 5 13:49:38 beanhead /kernel: 0: 6461095 2900007 1040005 2000 Apr 5 13:49:38 beanhead /kernel: 10: 6101 6201 6301 6401 Apr 5 13:49:38 beanhead /kernel: 20: 6501 0 0 6461095 Apr 5 13:49:38 beanhead /kernel: 30: 0 60 0 402010b Apr 5 13:49:38 beanhead /kernel: 40: 0 0 0 0 Apr 5 13:49:38 beanhead /kernel: 50:c000ec44 cc00c000 4000 0 Apr 5 13:49:38 beanhead /kernel: 60: 6010001 80006000 0 0 Apr 5 13:49:38 beanhead /kernel: 70:f3640409 8d108 f0000008 fd9ffe5c Apr 5 13:49:38 beanhead /kernel: ide_pci_dmadone: status=4 iobase_bm=6500 BMICOM=8 Apr 5 13:49:38 beanhead /kernel: cmd646_status: 0:1 register dump: Apr 5 13:49:38 beanhead /kernel: 0: 6461095 2900007 1040005 2000 Apr 5 13:49:38 beanhead /kernel: 10: 6101 6201 6301 6401 Apr 5 13:49:38 beanhead /kernel: 20: 6501 0 0 6461095 Apr 5 13:49:38 beanhead /kernel: 30: 0 60 0 402010b Apr 5 13:49:38 beanhead /kernel: 40: 0 0 0 0 Apr 5 13:49:38 beanhead /kernel: 50:c000ec44 cc00c000 4000 0 Apr 5 13:49:38 beanhead /kernel: 60: 6010001 80006000 0 0 Apr 5 13:49:38 beanhead /kernel: 70:f3640408 8d108 f0000008 fd9ffe5c Apr 5 13:49:38 beanhead /kernel: ide_pci_dmaverify: badfu=0 Apr 5 13:49:38 beanhead /kernel: ide_pci_dmassetup: iobase_bm=6500 BMICOM=8 Apr 5 13:49:38 beanhead /kernel: cmd646_status: 0:1 register dump: Apr 5 13:49:38 beanhead /kernel: 0: 6461095 2900007 1040005 2000 Apr 5 13:49:38 beanhead /kernel: 10: 6101 6201 6301 6401 Apr 5 13:49:38 beanhead /kernel: 20: 6501 0 0 6461095 Apr 5 13:49:38 beanhead /kernel: 30: 0 60 0 402010b Apr 5 13:49:38 beanhead /kernel: 40: 0 0 0 0 Apr 5 13:49:38 beanhead /kernel: 50:c000ec44 cc00c000 4000 0 Apr 5 13:49:38 beanhead /kernel: 60: 6010001 80006000 0 0 Apr 5 13:49:38 beanhead /kernel: 70:f3640408 8d108 f0000008 fd9ffe5c Apr 5 13:49:38 beanhead /kernel: ide_pci_dmastart: iobase_bm=6500 BMICOM=8 Apr 5 13:49:38 beanhead /kernel: cmd646_status: 0:1 register dump: Apr 5 13:49:38 beanhead /kernel: 0: 6461095 2900007 1040005 2000 Apr 5 13:49:38 beanhead /kernel: 10: 6101 6201 6301 6401 Apr 5 13:49:38 beanhead /kernel: 20: 6501 0 0 6461095 Apr 5 13:49:38 beanhead /kernel: 30: 0 60 0 402010b Apr 5 13:49:38 beanhead /kernel: 40: 0 0 0 0 Apr 5 13:49:38 beanhead /kernel: 50:c000ec44 cc00c000 4000 0 Apr 5 13:49:39 beanhead /kernel: 60: 6010001 80006000 0 0 Apr 5 13:49:39 beanhead /kernel: 70:f3600408 8d108 f0000008 fd9ffe5c Apr 5 13:49:39 beanhead /kernel: ide_pci_dmadone: status=4 iobase_bm=6500 BMICOM=9 Apr 5 13:49:39 beanhead /kernel: cmd646_status: 0:1 register dump: Apr 5 13:49:39 beanhead /kernel: 0: 6461095 2900007 1040005 2000 Apr 5 13:49:39 beanhead /kernel: 10: 6101 6201 6301 6401 Apr 5 13:49:39 beanhead /kernel: 20: 6501 0 0 6461095 Apr 5 13:49:39 beanhead /kernel: 30: 0 60 0 402010b Apr 5 13:49:39 beanhead /kernel: 40: 0 0 0 0 Apr 5 13:49:39 beanhead /kernel: 50:c000ec44 cc00c000 4000 0 Apr 5 13:49:39 beanhead /kernel: 60: 6010001 80006000 0 0 Apr 5 13:49:39 beanhead /kernel: 70:f3640409 8d108 f0000008 fd9ffe5c Apr 5 13:49:39 beanhead /kernel: ide_pci_dmaverify: badfu=0 Apr 5 13:49:39 beanhead /kernel: ide_pci_dmassetup: iobase_bm=6500 BMICOM=8 Apr 5 13:49:39 beanhead syslogd: exiting on signal 15 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 6 09:43:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA14484 for freebsd-current-outgoing; Mon, 6 Apr 1998 09:43:59 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from org.chem.msu.su (org.chem.msu.su [158.250.32.94]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA14346; Mon, 6 Apr 1998 09:41:50 -0700 (PDT) (envelope-from genie@qsar.chem.msu.su) Received: from org-qsar2 (org-qsar2.chem.msu.su [158.250.48.99]) by org.chem.msu.su (8.8.7/8.8.5) with SMTP id UAA16807; Mon, 6 Apr 1998 20:19:37 +0400 (MSD) Message-ID: <002001bd6177$dc5c9760$6330fa9e@org-qsar2.chem.msu.su> From: "Eugene Radchenko" To: "Jordan K. Hubbard" Cc: "Alex" , , , Subject: Re: SCSI errors with latest -current Date: Mon, 6 Apr 1998 20:19:35 +0400 MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Jordan, Don't (and did not) mean any flame, but if you had read my messages, you would know that they were not about 'Hey do fix this yesterday!'. I just asked someone (you know, not every user of the system has the expertise and time and a free machine to be SCSI hacker) to at least explain what this error means and what (in general terms) might be causing it and are there any ways to overcome this. The list archive search shows that this problem pops up every now and then, but I have seen no positive analysis except 'it should have been fixed in the previous version already'. I was disappointed not by the not-fixing of the problem (though I would appreciate seeing it fixed as the server dying in the middle of the night during backup is not a pleasant view for sysadmin). What gave me the unpleasant surprise was the complete indifference of readers (quite unusual for the FreeBSD _community_). Yours Genie -----Original Message----- From: Jordan K. Hubbard To: Eugene Radchenko Cc: Alex ; ache@nagual.pp.ru ; scsi@FreeBSD.ORG ; current@FreeBSD.ORG Date: Monday, April 06, 1998 4:05 PM Subject: Re: SCSI errors with latest -current >> As I tried to shout all over the SCSI list recently (to no avail), this is >> not limited to -current or 2.2.5. I had something like this even in 2.1 >> (though not as drastic -- just dump died and not the whole system). I have >> the feeling that 2.1 had not done tagged queueing yet. > >Things don't get fixed by shouting, they get fixed by fixing. That's >free software. Feel free, Eugene! ;-) > > Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 6 10:02:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA17270 for freebsd-current-outgoing; Mon, 6 Apr 1998 10:02:59 -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 KAA17253 for ; Mon, 6 Apr 1998 10:02:40 -0700 (PDT) (envelope-from kong@kong.spb.ru) Received: from localhost (kong@localhost) by kong.dorms.spbu.ru (8.8.8/kong/0.01) with SMTP id VAA11003 for ; Mon, 6 Apr 1998 21:02:28 +0400 (MSD) (envelope-from kong@kong.spb.ru) Date: Mon, 6 Apr 1998 21:02:27 +0400 (MSD) From: Hostas Red X-Sender: kong@kong.dorms.spbu.ru To: current@FreeBSD.ORG Subject: Communicator 4.05 doesn't installs with 128bit security 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! 'make -DUSE_128BIT install' fail after installing all files, but before registering package. Seems that this is the problem with Fortify, because 'make;make install' works fine. ============================================================================= [........] The Netscape Communicator software installation is complete. mv -f /usr/local/lib/netscape/netscape /usr/local/lib/netscape/communicator-4.05.bin install -c -o bin -g bin -m 555 /usr/ports/www/netscape4-communicator/work/communicator-v405.x86-unknown-freebsd/netscape /usr/local/bin/communicator-4.05 ln -sf communicator-4.05 /usr/local/bin/communicator-4 ln -sf communicator-4 /usr/local/bin/netscape if [ ! -f /usr/local/lib/netscape/mailcap ] ; then install -c -o bin -g bin -m 444 /usr/ports/www/netscape4-communicator/files/mailcap /usr/local/lib/netscape; fi rm -rf /usr/local/lib/netscape/movemail-src cd /usr/ports/www/netscape4-communicator/work/Fortify-1.2.1-unix && (echo yes ; echo no) | ./Fortify.sh /usr/local/lib/netscape/communicator-4.05.bin ==== Fortify 1.2.1; Copyright (C) 1997,1998 Farrell McKay ==== "/usr/local/lib/netscape/communicator-4.05.bin" is .... not recognisable. It is either not a copy of Netscape, or it is a version of Netscape that is not listed in the Index file. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. ======================================================================= Adios, /KONG To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 6 10:07:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA18097 for freebsd-current-outgoing; Mon, 6 Apr 1998 10:07:13 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA18071 for ; Mon, 6 Apr 1998 10:07:11 -0700 (PDT) (envelope-from tlambert@usr04.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id KAA29202; Mon, 6 Apr 1998 10:07:09 -0700 (MST) Received: from usr04.primenet.com(206.165.6.204) via SMTP by smtp04.primenet.com, id smtpd029178; Mon Apr 6 10:06:59 1998 Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id KAA22288; Mon, 6 Apr 1998 10:06:58 -0700 (MST) From: Terry Lambert Message-Id: <199804061706.KAA22288@usr04.primenet.com> Subject: Re: Quake2'able linux layer in current yet? To: jb@cimlogic.com.au (John Birrell) Date: Mon, 6 Apr 1998 17:06:58 +0000 (GMT) Cc: jkh@time.cdrom.com, current@FreeBSD.ORG In-Reply-To: <199804060457.OAA17661@cimlogic.com.au> from "John Birrell" at Apr 6, 98 02:57:29 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > I have zero more work to do take it with current's Prima Donas. > > > > For the benefit of those who don't know Amancio, allow me to translate: > > > > "I have no idea what's wrong but I'm in a bad mood and feel like > > blaming some vaguely specified 3rd-party for whatever the problem is > > in hopes that you'll just go away and stop bothering me." > > > > Gosh, wouldn't communication be so much simpler if people just said > > what they really meant? :-) > > Is _that_ what he meant?! I was sitting here playing "let's try > putting a punctuation mark here and see if it makes the statement > mean anything". I had considered the possibility that the Prima Donas > might have been a soccer team from some country I've never heard of. I had trouble parsing it without a colon following the "do". It becomes readable, then. ] I have zero more work to do: take it with current's Prima Donas. I took this to mean that it ran on his machine, and that the reason it didn't run for the poster was that the patches Amancio did to make it work for himself have not been integrated into FreeBSD-current. And that Amancio was slightly miffed about this fact. Oh, and while we are criticising grammar, he probably should have put the word "up" before the word "with"; but it's the message that's important, not the grammar. 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 Mon Apr 6 10:31:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA21540 for freebsd-current-outgoing; Mon, 6 Apr 1998 10:31:08 -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 KAA21504 for ; Mon, 6 Apr 1998 10:30:49 -0700 (PDT) (envelope-from kong@kong.spb.ru) Received: from localhost (kong@localhost) by kong.dorms.spbu.ru (8.8.8/kong/0.01) with SMTP id VAA13385 for ; Mon, 6 Apr 1998 21:30:41 +0400 (MSD) (envelope-from kong@kong.spb.ru) Date: Mon, 6 Apr 1998 21:30:41 +0400 (MSD) From: Hostas Red X-Sender: kong@kong.dorms.spbu.ru To: current@FreeBSD.ORG Subject: kernel 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 Hi! kernel won't build (cvsup few minutes ago): =============================== exception.o: Undefined symbol `_my_tr' referenced from text segment exception.o: Undefined symbol `_my_tr' referenced from text segment machdep.o: Undefined symbol `_common_tssd' referenced from text segment machdep.o: Undefined symbol `_common_tssd' referenced from text segment machdep.o: Undefined symbol `_private_tss' referenced from text segment machdep.o: Undefined symbol `_my_tr' referenced from text segment swtch.o: Undefined symbol `_my_tr' referenced from text segment swtch.o: Undefined symbol `_private_tss' referenced from text segment swtch.o: Undefined symbol `_common_tssd' referenced from text segment swtch.o: Undefined symbol `_my_tr' referenced from text segment swtch.o: Undefined symbol `_private_tss' referenced from text segment swtch.o: Undefined symbol `_private_tss' referenced from text segment swtch.o: Undefined symbol `_common_tssd' referenced from text segment *** Error code 1 =============================== Adios, /KONG To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 6 10:34:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA22038 for freebsd-current-outgoing; Mon, 6 Apr 1998 10:34:05 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sos.freebsd.dk (sos.freebsd.dk [195.8.129.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA22030 for ; Mon, 6 Apr 1998 10:34:02 -0700 (PDT) (envelope-from sos@sos.freebsd.dk) Received: (from sos@localhost) by sos.freebsd.dk (8.8.8/8.8.8) id TAA07811; Mon, 6 Apr 1998 19:33:15 +0200 (MEST) (envelope-from sos) Message-Id: <199804061733.TAA07811@sos.freebsd.dk> Subject: Re: Quake2'able linux layer in current yet? In-Reply-To: <199804061706.KAA22288@usr04.primenet.com> from Terry Lambert at "Apr 6, 98 05:06:58 pm" To: tlambert@primenet.com (Terry Lambert) Date: Mon, 6 Apr 1998 19:33:15 +0200 (MEST) Cc: jb@cimlogic.com.au, jkh@time.cdrom.com, current@FreeBSD.ORG From: Søren Schmidt Reply-to: sos@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL30 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In reply to Terry Lambert who wrote: > I took this to mean that it ran on his machine, and that the reason > it didn't run for the poster was that the patches Amancio did to make > it work for himself have not been integrated into FreeBSD-current. > > And that Amancio was slightly miffed about this fact. Hmm, havn't looked at the stuff, but maybe those that did, found out it still needed work before it could be put into current ?? -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end .. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 6 10:36:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA22617 for freebsd-current-outgoing; Mon, 6 Apr 1998 10:36:15 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from trinity.radio-do.de (trinity.Radio-do.de [193.101.164.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA22467; Mon, 6 Apr 1998 10:35:56 -0700 (PDT) (envelope-from fn@trinity.radio-do.de) Received: (from fn@localhost) by trinity.radio-do.de (8.8.8/8.8.5/RADIO-1.1) id TAA13185; Mon, 6 Apr 1998 19:35:34 +0200 (CEST) From: Frank Nobis Message-Id: <199804061735.TAA13185@trinity.radio-do.de> Subject: Re: LINT broken in brooktree848.c ? In-Reply-To: <9394.891847811@critter.freebsd.dk> from Poul-Henning Kamp at "Apr 6, 98 09:30:11 am" To: phk@FreeBSD.ORG (Poul-Henning Kamp) Date: Mon, 6 Apr 1998 19:35:34 +0200 (CEST) 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 > > cc -c -O -pipe -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wuninitialized -nostdinc -I- -I. -I../.. -I/usr/include -DKERNEL -include opt_global.h ../../pci/brooktree848.c > ../../pci/brooktree848.c:232: opt_bktr.h: No such file or directory Oops, my fault. The last patch was incomplete. I forget to update options.i386 since I need to override the tuner detection. Here is a patch: *** /usr/src/sys/i386/conf/options.i386.orig Mon Apr 6 19:20:15 1998 --- /usr/src/sys/i386/conf/options.i386 Mon Apr 6 19:22:14 1998 *************** *** 120,122 **** --- 120,125 ---- PCVT_SCREENSAVER opt_pcvt.h PCVT_USEKBDSEC opt_pcvt.h PCVT_VT220KEYB opt_pcvt.h + + # give bktr an opt_bktr.h file + OVERRIDE_TUNER opt_bktr.h *** /usr/src/sys/i386/conf/LINT.orig Mon Apr 6 19:29:43 1998 --- /usr/src/sys/i386/conf/LINT Mon Apr 6 19:32:53 1998 *************** *** 1329,1335 **** # for initialization of fps routine when a signal is not present. # # The 'bktr' device is a PCI video capture board. It also has a TV tuner ! # on board. # controller pci0 controller ahc1 --- 1329,1337 ---- # for initialization of fps routine when a signal is not present. # # The 'bktr' device is a PCI video capture board. It also has a TV tuner ! # on board. To override the tuner detection use ! # options OVERRIDE_TUNER=x ! # The current values are found in /usr/src/sys/pci/brooktree848.c # controller pci0 controller ahc1 Regards 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 Mon Apr 6 11:02:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA26322 for freebsd-current-outgoing; Mon, 6 Apr 1998 11:02:10 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from shell3.ba.best.com (root@shell3.ba.best.com [206.184.139.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA26307 for ; Mon, 6 Apr 1998 11:02:04 -0700 (PDT) (envelope-from schrade@schrade.com) Received: from localhost (schrade@localhost [127.0.0.1]) by shell3.ba.best.com (8.8.8/8.8.BEST) with SMTP id LAA24144; Mon, 6 Apr 1998 11:01:33 -0700 (PDT) Date: Mon, 6 Apr 1998 11:01:33 -0700 (PDT) From: Ken Krebs To: Hostas Red cc: current@FreeBSD.ORG Subject: Re: kernel problem 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 Mon, 6 Apr 1998, Hostas Red wrote: >kernel won't build (cvsup few minutes ago): I get the exact same thing. Last cvsup I did was at 10:31am, PDT today. >=============================== >exception.o: Undefined symbol `_my_tr' referenced from text segment >exception.o: Undefined symbol `_my_tr' referenced from text segment >machdep.o: Undefined symbol `_common_tssd' referenced from text segment >machdep.o: Undefined symbol `_common_tssd' referenced from text segment >machdep.o: Undefined symbol `_private_tss' referenced from text segment >machdep.o: Undefined symbol `_my_tr' referenced from text segment >swtch.o: Undefined symbol `_my_tr' referenced from text segment >swtch.o: Undefined symbol `_private_tss' referenced from text segment >swtch.o: Undefined symbol `_common_tssd' referenced from text segment >swtch.o: Undefined symbol `_my_tr' referenced from text segment >swtch.o: Undefined symbol `_private_tss' referenced from text segment >swtch.o: Undefined symbol `_private_tss' referenced from text segment >swtch.o: Undefined symbol `_common_tssd' referenced from text segment >*** Error code 1 >=============================== >Adios, >/KONG *********** NewOrderDepecheModeUltravoxViolentFemmesKillingJoke ************* * Ken * NineInchNailsFront242TangerineDreamTheBreedersTekno * * * Krebs * SkinnyPuppyLaTourBauhausBookOfLoveModernEnglishB52s * * *********** FishBoneBigCountryJoyDivisonSiouxsie&TheBansheesXTC ************* ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ IRC: Schrade E-Mail: schrade@schrade.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 6 11:11:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA28520 for freebsd-current-outgoing; Mon, 6 Apr 1998 11:11:00 -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 LAA28416; Mon, 6 Apr 1998 11:10:40 -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 NAA29194; Mon, 6 Apr 1998 13:10:10 -0500 (CDT) Received: (from jlemon@localhost) by right.PCS (8.6.13/8.6.4) id NAA25167; Mon, 6 Apr 1998 13:09:39 -0500 Message-ID: <19980406130938.10795@right.PCS> Date: Mon, 6 Apr 1998 13:09:38 -0500 From: Jonathan Lemon To: sos@FreeBSD.ORG Cc: Terry Lambert , jb@cimlogic.com.au, jkh@time.cdrom.com, current@FreeBSD.ORG Subject: Re: Quake2'able linux layer in current yet? References: <199804061706.KAA22288@usr04.primenet.com> <199804061733.TAA07811@sos.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.61.1 In-Reply-To: =?iso-8859-1?Q?=3C199804061733=2ETAA07811=40sos=2Efreebsd=2Edk=3E=3B_fro?= =?iso-8859-1?Q?m_S=F8ren_Schmidt_on_Apr_04=2C_1998_at_07=3A33=3A15PM_+02?= =?iso-8859-1?Q?00?= Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Apr 04, 1998 at 07:33:15PM +0200, Søren Schmidt wrote: > In reply to Terry Lambert who wrote: > > > I took this to mean that it ran on his machine, and that the reason > > it didn't run for the poster was that the patches Amancio did to make > > it work for himself have not been integrated into FreeBSD-current. > > > > And that Amancio was slightly miffed about this fact. > > Hmm, havn't looked at the stuff, but maybe those that did, found out > it still needed work before it could be put into current ?? Maybe because the README.GLQUAKE file (dated 98.02.11) says: ********************IMPORTANT**************************************** When we are done wrapping up the support for Quake2 the changes will be roll back to 3.0 -current. ********************IMPORTANT**************************************** which would tend to imply that they haven't finished yet? -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 6 11:33:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA04137 for freebsd-current-outgoing; Mon, 6 Apr 1998 11:33:05 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA04065 for ; Mon, 6 Apr 1998 11:32:57 -0700 (PDT) (envelope-from mark@grondar.za) Received: from greenpeace.grondar.za (Ru5nliCKIfHQC4BrgMM48C6WVCwdcNDp@greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.8.8/8.8.8) with ESMTP id UAA23030; Mon, 6 Apr 1998 20:32:49 +0200 (SAST) (envelope-from mark@grondar.za) Received: from grondar.za (vJqFaFPvEk0R6hHyBN3mZicIZxk37tPk@localhost [127.0.0.1]) by greenpeace.grondar.za (8.8.8/8.8.8) with ESMTP id UAA05417; Mon, 6 Apr 1998 20:32:43 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199804061832.UAA05417@greenpeace.grondar.za> X-Mailer: exmh version 2.0.2 2/24/98 To: Hostas Red cc: current@FreeBSD.ORG Subject: Re: Communicator 4.05 doesn't installs with 128bit security Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 06 Apr 1998 20:32:42 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hostas Red wrote: > Hi! > > 'make -DUSE_128BIT install' fail after installing all files, but before > registering package. Seems that this is the problem with Fortify, because > 'make;make install' works fine. Fortify is not aware of netscape 4.05 yet. > "/usr/local/lib/netscape/communicator-4.05.bin" is .... not recognisable. > It is either not a copy of Netscape, or it is a version > of Netscape that is not listed in the Index file. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 6 11:50:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA07396 for freebsd-current-outgoing; Mon, 6 Apr 1998 11:50:31 -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 LAA07358 for ; Mon, 6 Apr 1998 11:50:19 -0700 (PDT) (envelope-from kong@kong.spb.ru) Received: from localhost (kong@localhost) by kong.dorms.spbu.ru (8.8.8/kong/0.01) with SMTP id WAA13770; Mon, 6 Apr 1998 22:49:29 +0400 (MSD) (envelope-from kong@kong.spb.ru) Date: Mon, 6 Apr 1998 22:49:28 +0400 (MSD) From: Hostas Red X-Sender: kong@kong.dorms.spbu.ru To: Lutz Albers cc: current@FreeBSD.ORG Subject: Re: Communicator 4.05 doesn't installs with 128bit security In-Reply-To: <35291981.3C39FD8A@muc.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 Hi! On Mon, 6 Apr 1998, Lutz Albers wrote: > > 'make -DUSE_128BIT install' fail after installing all files, but before > > ==== Fortify 1.2.1; Copyright (C) 1997,1998 Farrell McKay ==== > Isn't that obvious ? Fortify 1.2.1 doesn't know this netscape version > (yet), so it can't patch it for 128-bit encryption. So take out the > fortify step till a new version is released :-) That's what i did at first. :) Adios, /KONG To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 6 11:58:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA08831 for freebsd-current-outgoing; Mon, 6 Apr 1998 11:58:14 -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 LAA08790 for ; Mon, 6 Apr 1998 11:57:55 -0700 (PDT) (envelope-from kong@kong.spb.ru) Received: from localhost (kong@localhost) by kong.dorms.spbu.ru (8.8.8/kong/0.01) with SMTP id WAA14427 for ; Mon, 6 Apr 1998 22:57:52 +0400 (MSD) (envelope-from kong@kong.spb.ru) Date: Mon, 6 Apr 1998 22:57:52 +0400 (MSD) From: Hostas Red X-Sender: kong@kong.dorms.spbu.ru To: current@FreeBSD.ORG Subject: Re: kernel problem In-Reply-To: <19980406124953.50107@right.PCS> 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 Mon, 6 Apr 1998, Jonathan Lemon wrote: > > kernel won't build (cvsup few minutes ago): > > Try putting line right after the copyright in src/sys/i386/i386/global.s: > > #include "opt_vm86.h" Almost worked: exception.o: Undefined symbol `_my_tr' referenced from text segment exception.o: Undefined symbol `_my_tr' referenced from text segment machdep.o: Undefined symbol `_my_tr' referenced from text segment swtch.o: Undefined symbol `_my_tr' referenced from text segment swtch.o: Undefined symbol `_my_tr' referenced from text segment *** Error code 1 :-) Adios, /KONG To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 6 12:00:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA09554 for freebsd-current-outgoing; Mon, 6 Apr 1998 12:00:26 -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 MAA09503 for ; Mon, 6 Apr 1998 12:00:07 -0700 (PDT) (envelope-from lutz@muc.de) Received: from tavari.muc.de ([193.174.4.22]) by colin.muc.de with SMTP id <140570-1>; Mon, 6 Apr 1998 20:38:09 +0200 Received: from muc.de (ripley [192.168.42.202]) by tavari.muc.de (8.8.7/8.8.7) with ESMTP id UAA22079; Mon, 6 Apr 1998 20:07:11 +0200 (CEST) Message-ID: <35291981.3C39FD8A@muc.de> Date: Mon, 6 Apr 1998 20:05:53 +0200 From: Lutz Albers X-Mailer: Mozilla 4.04 [en] (WinNT; U) MIME-Version: 1.0 To: Hostas Red CC: current@FreeBSD.ORG Subject: Re: Communicator 4.05 doesn't installs with 128bit security References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hostas Red wrote: > 'make -DUSE_128BIT install' fail after installing all files, but before > registering package. Seems that this is the problem with Fortify, because > 'make;make install' works fine. .... > ==== Fortify 1.2.1; Copyright (C) 1997,1998 Farrell McKay ==== > > "/usr/local/lib/netscape/communicator-4.05.bin" is .... not recognisable. > It is either not a copy of Netscape, or it is a version > of Netscape that is not listed in the Index file. Isn't that obvious ? Fortify 1.2.1 doesn't know this netscape version (yet), so it can't patch it for 128-bit encryption. So take out the fortify step till a new version is released :-) ciao lutz -- Lutz Albers, lutz@muc.de, pgp key available from Do not take life too seriously, you will never get out of it alive. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 6 12:14:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA11837 for freebsd-current-outgoing; Mon, 6 Apr 1998 12:14:04 -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 MAA11803 for ; Mon, 6 Apr 1998 12:13:39 -0700 (PDT) (envelope-from kong@kong.spb.ru) Received: from localhost (kong@localhost) by kong.dorms.spbu.ru (8.8.8/kong/0.01) with SMTP id XAA14486; Mon, 6 Apr 1998 23:12:38 +0400 (MSD) (envelope-from kong@kong.spb.ru) Date: Mon, 6 Apr 1998 23:12:38 +0400 (MSD) From: Hostas Red X-Sender: kong@kong.dorms.spbu.ru To: Jonathan Lemon cc: current@FreeBSD.ORG Subject: Re: kernel problem In-Reply-To: <19980406141026.18111@right.PCS> 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 Mon, 6 Apr 1998, Jonathan Lemon wrote: > > exception.o: Undefined symbol `_my_tr' referenced from text segment > > exception.o: Undefined symbol `_my_tr' referenced from text segment > > machdep.o: Undefined symbol `_my_tr' referenced from text segment > > swtch.o: Undefined symbol `_my_tr' referenced from text segment > > swtch.o: Undefined symbol `_my_tr' referenced from text segment > > *** Error code 1 > > Yup, I noticed that when doing a test-build here. The correct fix > just hit the tree a few minutes ago, so your next cvsup run should > fix it. Thanks a lot. We'll wait and see. :-) Adios, /KONG To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 6 12:39:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA18128 for freebsd-current-outgoing; Mon, 6 Apr 1998 12:39:46 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.webspan.net (root@mail.webspan.net [206.154.70.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA18047 for ; Mon, 6 Apr 1998 12:39:32 -0700 (PDT) (envelope-from opsys@mail.webspan.net) Received: from orion.webspan.net (orion.webspan.net [206.154.70.5]) by mail.webspan.net (WEBSPAN/970608) with SMTP id PAA19274; Mon, 6 Apr 1998 15:35:35 -0400 (EDT) Date: Mon, 6 Apr 1998 15:39:10 -0400 (EDT) From: Open Systems Networking X-Sender: opsys@orion.webspan.net To: Hostas Red cc: current@FreeBSD.ORG Subject: Re: Communicator 4.05 doesn't installs with 128bit security 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 Mon, 6 Apr 1998, Hostas Red wrote: I mailed ache about this the day after he comited 4.05 to nav and communicator. the fortify people do not have checksums in their Index file for 4.05 yet. so its borke. So until the fortify people add 4.05 to their Index it wont work :) Chris -- "I am closed minded. It keeps the rain out." ===================================| Open Systems Networking And Consulting. FreeBSD 2.2.6 is available now! | Phone: 316-326-6800 -----------------------------------| 1402 N. Washington, Wellington, KS-67152 FreeBSD: The power to serve! | E-Mail: opsys@open-systems.net http://www.freebsd.org | Consulting-Network Engineering-Security ===================================| http://open-systems.net -----BEGIN PGP PUBLIC KEY BLOCK----- Version: 2.6.2 mQENAzPemUsAAAEH/06iF0BU8pMtdLJrxp/lLk3vg9QJCHajsd25gYtR8X1Px1Te gWU0C4EwMh4seDIgK9bzFmjjlZOEgS9zEgia28xDgeluQjuuMyUFJ58MzRlC2ONC foYIZsFyIqdjEOCBdfhH5bmgB5/+L5bjDK6lNdqD8OAhtC4Xnc1UxAKq3oUgVD/Z d5UJXU2xm+f08WwGZIUcbGcaonRC/6Z/5o8YpLVBpcFeLtKW5WwGhEMxl9WDZ3Kb NZH6bx15WiB2Q/gZQib3ZXhe1xEgRP+p6BnvF364I/To9kMduHpJKU97PH3dU7Mv CXk2NG3rtOgLTEwLyvtBPqLnbx35E0JnZc0k5YkABRO0JU9wZW4gU3lzdGVtcyA8 b3BzeXNAb3Blbi1zeXN0ZW1zLm5ldD4= =BBjp -----END PGP PUBLIC KEY BLOCK----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 6 15:37:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA25582 for freebsd-current-outgoing; Mon, 6 Apr 1998 15:37:10 -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 PAA25576; Mon, 6 Apr 1998 15:37:08 -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 PAA00765; Mon, 6 Apr 1998 15:34:06 -0700 (PDT) Message-Id: <199804062234.PAA00765@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Dan Swartzendruber cc: dyson@FreeBSD.ORG, dg@root.com, dag-erli@ifi.uio.no, stable@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: swap-leak in 2.2.5 ? In-reply-to: Your message of "Sun, 05 Apr 1998 18:20:46 EDT." <3.0.5.32.19980405182046.009137d0@mail.kersur.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 06 Apr 1998 15:34:04 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > It was actually kind of embarrassing. I convinced a local ISP to start > converting their servers from Linux (what I recommended a few years ago > when I didn't know different :)) One of the admins (who has some Linux > experience) asked me why it was using swap. I gave the canonical reply. > He asked the question I just posed. I had no good reply :( The simplest answer to this is "because the system has found a better use for memory than holding the data". It can't throw it away (it's data, after all), so it parks it in the swap partition. -- \\ 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 Mon Apr 6 20:07:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA08649 for freebsd-current-outgoing; Mon, 6 Apr 1998 20:07:37 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mantar.slip.netcom.com (mantar.slip.netcom.com [192.187.167.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA08576 for ; Mon, 6 Apr 1998 20:07:32 -0700 (PDT) (envelope-from mantar@netcom.com) Received: from dual (DUAL [192.187.167.136]) by mantar.slip.netcom.com (8.8.8/8.8.8) with SMTP id UAA24404; Mon, 6 Apr 1998 20:06:17 -0700 (PDT) (envelope-from mantar@netcom.com) Message-Id: <199804070306.UAA24404@mantar.slip.netcom.com> X-Sender: null@mantar.slip.netcom.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Mon, 06 Apr 1998 20:06:16 -0700 To: Eric "Two Cats" Jones , obanta@unixgeeks.net (Oliver Banta) From: Manfred Antar Subject: Re: Current with XFree86 3.3.2 Cc: freebsd-current@FreeBSD.ORG In-Reply-To: <199804061243.HAA17043@psasolar.psa.pencom.com> References: <199804052149.QAA01036@aenima.unixgeeks.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 07:43 AM 4/6/98 -0500, Eric "Two Cats" Jones wrote: > >Oliver, > I had what I think is the same problem (although I was >building directly from the XF86 source base, not the port: the port >may avoid this problem). My problem was that the XF86 server >code implements their own malloc, for which they need the hardware >pagesize. The code checks whether to use sysconf(5) for this >info by doing #ifdef _SC_PAGESIZE, which until about 3/28 >was false. After 3/28, this value is defined, however the >backend code would cause sysconf(_SC_PAGESIZE) to return -1, >which XF86 didn't bother to check. It would later use this >pagesize to calculate what size chunk to allocate off the heap, >with disasterous consequences. There's a way to force the >code to use the getpagesize(3) call, but I can't remember >off the top of my head and I've deleted my distribution. Check >xc/programs/Xserver/os/xalloc.c and look for _SC_PAGESIZE... >you should be able to figure it out from there. > I suspect your log messages are coincidental. > >Eric Jones >Collective Technology > >Strange sunspot activity caused Oliver Banta to write: >> I recently installed 3.0-980311-SNAP on a Dual PPro 180. X was >> working fine until I did two things: 1) rebuilt world to -current as >> of April 3 and 2) rebuilt XFree86 3.3.2 from /usr/ports/x11/XFree86/. >> Now whenever I try to start any X server, it core dumps on me. >> >[...] >> >> To make sure it wasn't something dumb on my part, I ran XF86Setup >> which uses the XF86_VGA16 server, and it also core dumped on me. I >> ran this when I originally installed 3.0-SNAP and it worked fine. >> This is the error I get, in case it will help anyone figure out what's >> wrong: >> >> Apr 4 04:03:12 knuth /kernel: forward_hardclock: checkstate 0 >> Apr 4 04:03:13 knuth last message repeated 15 times >> Apr 4 04:03:15 knuth /kernel: pid 12296 (XF86_VGA16), uid 0: exited on signal 6 >> (core dumped) >> >> I am currently rebuilding world and will try again as soon as it >> finishes. I will also try it with SMP not enabled to see if that >> makes any difference. If anyone has any hints or suggestions, I'd >> love to hear them. >> >> Cheers, >> -- Oliver >> I changed line 682 in xc/programs/Xserver/os/xalloc.c to read pagesize = getpagesize(); and the XF86_SVGA server now works. I tried changing the permissions on the file but that didn't work. Changing the above line and rebuilding the server works so far up all day Manfred |=======================| | mantar@netcom.com | | Ph. (415) 681-6235 | |=======================| To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 6 23:31:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA02557 for freebsd-current-outgoing; Mon, 6 Apr 1998 23:31:33 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from tohokugw.tohoku.iij.ad.jp (firewall-user@tohokugw.tohoku.iij.ad.jp [202.232.14.98]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA02552 for ; Mon, 6 Apr 1998 23:31:32 -0700 (PDT) (envelope-from taguchi@tohoku.iij.ad.jp) Received: by tohokugw.tohoku.iij.ad.jp; id PAA20165; Tue, 7 Apr 1998 15:31:30 +0900 (JST) Received: from unknown(192.168.144.5) by tohokugw.tohoku.iij.ad.jp via smap (3.2) id xma020161; Tue, 7 Apr 98 15:31:23 +0900 Received: from localhost (hoya.tohoku.iij.ad.jp [192.168.144.34]) by yubeshi.tohoku.iij.ad.jp (8.7.4/3.4W2) with ESMTP id PAA01414 for ; Tue, 7 Apr 1998 15:31:23 +0900 (JST) To: freebsd-current@FreeBSD.ORG Subject: Re: Current with XFree86 3.3.2 From: Taguchi Takeshi In-Reply-To: Your message of "Mon, 06 Apr 1998 20:06:16 -0700" <199804070306.UAA24404@mantar.slip.netcom.com> References: <199804070306.UAA24404@mantar.slip.netcom.com> X-Mailer: Mew version 1.93b26 on XEmacs 20.4 (Emerald) X-Prom-Mew: Prom-Mew 1.92.9 (procmail reader for Mew) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19980407153257G.taguchi@tohoku.iij.ad.jp> Date: Tue, 07 Apr 1998 15:32:57 +0900 X-Dispatcher: imput version 980302 Lines: 8 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I changed line 682 in xc/programs/Xserver/os/xalloc.c to read > > pagesize = getpagesize(); > > and the XF86_SVGA server now works. -STABLE with XFree86 3.3.2 also needs this modification. XF86_SVGA seem work fine, but XF86_S3V still dump core ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 6 23:53:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA06674 for freebsd-current-outgoing; Mon, 6 Apr 1998 23:53:12 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from chen.ml.org (luoqi.watermarkgroup.com [207.202.73.170]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA06640 for ; Mon, 6 Apr 1998 23:52:58 -0700 (PDT) (envelope-from luoqi@chen.ml.org) Received: (from luoqi@localhost) by chen.ml.org (8.8.8/8.8.8) id CAA05290 for current@freebsd.org; Tue, 7 Apr 1998 02:52:55 -0400 (EDT) (envelope-from luoqi) Date: Tue, 7 Apr 1998 02:52:55 -0400 (EDT) From: Luoqi Chen Message-Id: <199804070652.CAA05290@chen.ml.org> To: current@FreeBSD.ORG Subject: Re: Communicator 4.05 doesn't installs with 128bit security Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Untar this in your Fortify folder... begin 644 405.tgz M'XL(`!7+*34``]2:2V\=N7:%>^Q?<8">)(!E5>Z^=Q^GQW^_M=_73__C2O M/X[3_?5_C_M3O>FG3SV<_JP?OX[[#^]^Y??_[7I\[/SH;O#1N]M/IX]C?CE] MN3W=7?_^QY=_64O\0'B__?;]YWKS_@'G/9\XK?7Z5_WR_O3GN+N_ON4#+-_7 M;]S>??[C?L-X?_K\L7Z9MW>?WI_T]M.GW]Y._ M/UV]"R%&'ST_[-9&-Y,FP%/0,%5K3D4\?RW3IN=@?WS^7.6#7/WQF7^__@66 MBU&R75C)JKC@C),KKS?_=7/[]YNK=M\!\X9U MD^6'H80>;!S3Y5R\"Z74FDJV5FLMW8<78/X1V,?KFVUO/EKO9,&-*3%J3=%6 M:WR(U;@X?31Y]);DY=X^77^^O[K__?KJ^N[ZK_#!KH.&`"<$?FB=B39[UVQS MOBJG'9*LRX.D-%9\#G9W'XTQ5]?MTU6]_LMM:-Y+<'F%;3K'R6R9K4^"&8+: MZ;26X4L4,?,Y&H5VIU?W7V^N[F\_UKOK>_O!K>V9Y$-89[5]Y&I"DI)&59.+ MM)A;'C/$9HW:"P#]VF$B!QM@=QPP"-]MC]-HG&-.8ZLF;ZKHB^`]`OQZ;;)K#F26$I;, M'O.T]<7&]FJ8ALAVHQ'CR9Y(U!EM3+HV56P*HUIU.27_'.V@AKV48K=41E>* M#\ZEJJ[#,):6#=Y.:3K"3/$"P%7#`2:+&SD-&=5[",1H=Q1OBRE8IVTFL6GF M\0K@DWK[I[_]]N__#*ZU658=!UBN%.=41^?8,<5JFV^C9A8RKV[T*>Z__@U< MGVTXU[+OT@K$+,Z[W(JIR<]24_?0G^/^]9)+`Y46UA['H*5HO3QR\EIZ M&"7W+))7KU%?KV%M5'HU/LY%,3D6']?NI,?2-4JKC8QDZ3/+U%RC']1^?%$] M"_$EP?!1_MNZI!OX;R5'DF2H(!4WX9IF9(;ZHGP>;_!>;ZG&/\,'L]6D+=GD MK2:%R1%"M6G`A?2R;%$K>].2@IP*(]"OU8A%@26IBF]EY]ZD]1]VDA&FNV M';9A9@ABZ+2>U8;>2LNNJ4ZK\3G6HQWN\D,!9Z&Z)#/[6BJSEQ&ZPM"CVC9Z M:4YM>;[#?7Y@R&WC-T]?[0Q6LH,J?*8"&Z4<9QBH!QF'>SPB"FN60%^U3;7U MZKKQM;9$9WBW@FJ<+52":3^#_)0Q3*!'O"M6Z#WOS*-*\V.YNLN,NSP M''V7/O`N+;%Q".=AT9N>R1(XC M[FWV[E<;..W(*^NIX%Z?YW*_6[,ML@D62M:5J6T4?C\-A$5MIK!ITVBX/@]# MOLM1S)_%444#K-DI0'8H*#V$4''#V9$(4;`7@3XF*Y@EATUJ*.40`X(#T38: MLD.+U9F&;-]ZVSO^`;L\(@:&^NRABV>@UQC4&$9\G=-&]FN&>T"5-XGAH9EM MB4P/HW4X#ZTBL(:?KA+A[BM:Y!!UIYD?VH]94GMJ#NDFVE(,R#>IIEDWC&B( MAZAOMA^%@%8UN3;T!/3H.S*`6J@,;24!/X/\M/V(+>0PF%*./BS>5FHAPN;P MG4]3=Y%_MOU69Z,%IMI>&(P=:=$P1TQ+)$&H1R]KOH5^*,FD+VA&>-IP) M16G#=*PX:Z(C#V/T6K]0:$LU,QY1S(SY8M0L:0DPNKRVBT`?]PL;3D:VI$KT M$TF(H^PAF!42?-V8^`HMR03S'?O8%&*L$-1KGVFF.5+4U)`,.E%*801%-##< MNWO07?:"Z10BJ)L41LU0N\B1E(S/BKLS.%=5#\^5V2]$C6[$FR+]2OLAF&5,?E! M=4F0-"..#D,7&`K5^?(4=9^9RKK_60YK3;_8[+KP@HRC#SC6."BX[=K('^[P MU4*NLGPUY@H9-V.$XT81F8QRVK&W?AEJ_.[6\^I;SCU1XM5AK@WV/U?4K@&X M3)^[J$O/S_U4C:\-TA)YN\QIB$#O:N74MB"5+0K:H._9+$U=PG.H0PE@Q6V# MNC$JT&M,'40@8D741H8W/`09Y0?:>7'B-YNLT;2HBIYK9J>!,K%(4V>_O^4A1 M6`3;1I89C^=M1W%%JB-W)ZFU9/.2BUW-1:!/%'@P2;9;L+CN@`6Q7<493']$ M@]IE`5&*J<^Q=_QC!?Z=8H:G81FK]`!5`7UUI8^3F6)ID?((]0(%_@,5/:QN M5IG,"D:T7]=:5=JZ4ZUY&'<9ZIFX'L@&,D!3S.6[EO8K?3V&JDA,M9B';@]1 M7R4;+T[%4%"C2YW("R:Q[PV^K868Z&6HWZ?F]X96_&C%Y<;D0\'NAG4Y;:=) MO;D<8SU$?;.A`X23<>8P%A;4S[*JK+CM4L#:QY3[OYB:WQN:\=^2I\=J*(P< MGTL9KMMU/Z?%Z7Y97*KIOW=@2VY$Z)SL82,S,T[4:]%.+FI-QS%ZK0/-:,0: M4UJ:^D"(4+6#PNYX[29I7@3Z1-/;X/`@6^@;'M4MFL=!="1+Q;W7VJ&_CD:O MI]]O/_:CRW%$M64_R^_E]7C"=WJ"(DOP#44MR%M5OLLWF-=OQX-'+&X7$W;@ M"D9H'NM%0+>[)BT!=]D;]M>_0-N9YQE9MT4/(SZ7\S8EX9X34?0FMX25:ZR" MW7L.MM-:F3)"^JQX!8M+6DYT=G^5?GO1H[*;HRF;2DM24S5@7L'F=,767G)H(!_CL MG%R"N+HS>@SEQB:1N9>0!FGXP#`G([C+E8]U;Z[M96Y?[\CH>N=(CQ23^<3;CM8E0CPX!^P)X M=ZX&BY\YBS?MI=@*95-`;5V[.!1P1^8G4JXO([#3S5#=^9$CQ9=+AS'6$*0P MK2(Q:S>)HJ+UXJM@3^9H68_VXIF9LX7L.RR<-5+JU#ZF>MV[57I?Z$&F#V,][I'%:OAP?B!,YR3G)2&BU;:*[PDN5K>\ M*W;MQ1X/R`(EN(F%@O[`G7#B=>@Z5"JVLN7>,7Y#CG=YS!KA7.%T,UQ&O\\5 MAS%'TUS6:!>61E3^%/13^G!]1AUD/JYK+0DM+]^-O^AIK`7VH2^;[@]<0AU8 MTUQ$ZU4)P_N^;JHZE>NKZG#[JUPXWAV+?'M>,7PWK4X9*21E3#&:*[E$3T#= MS\-T3"RQ;&.SM3P-^XS,7NF%L1!:':CXQBK!C^.P[S*,,YNK0)8%1AT#JQL) M=&UM,(OK(5MK&:"7H3ZE&EGW.FN:9@?#J)G&0XJ!H(<\//JRX@NP-;L1.-+L M#R114?YQ8'Y@;*E(FP`O(B3X0T9YUT>P%XCVA[Z6S%8EIXY6)[H6/3;)U9BB MF4(YAMWIZX=&Q$1@VRK#&UL/OT67&1"9@$_Z)N9CV#<;489$_@Z@?[818>*DZZZ*U7`< M1J%Z,[I;,GQ1X?XJES7B0^/X8;.E>V@;D]9U&#IB(!_M'))\"\=A>JUQ`C)X M5FTN2:N*"8F(8[4QFMDF)7\9ZA.E'4!/Y\=-ZYV%.K-'W18L0M)<[7KPOMZO M*H]TZ/'U.0&(*(_MQBLSZ=9K%=ER^#!T/4KHN+%A;/91?Z"YMYGC$>QLJ$@W MFN^Y(E%LK"K+1#8$BGB51[!OQI7VMN'\.`@RNTV28\JQK&X]IEO\:U8/ M-,QQ;X5H&I/>,9*S+5[6`=DF/V^7QH-1VW M!:/7,B=3N1<419G=VYB8=\>'/B3'$NTY3<:W2AAQ3;"X4_PG`BA.>*RF:=T^ M](7D&,C0%I)(H9J@:RWQZQTK_`,::'2SGI:,O+_*I2JEQ+2-IX)/0YVD"".N MEUPP"6Z$-"PS9<[\_"R'*N4[*13ZH3,N,R%?;YFBKLL@X#Y3%!H/=GU$MBX' ML[W?&/M%&>32.+K]8Q`Z8[3(;,5$0/KG2#`B>ZM6: M..&:]8&F+TOO=97RG<8HAO5Z(RH0UDUE>>#M66AQL=AH'S?=VRKE@<9PTF;= MJ?887/`:!7&%PW2%>4T+M@MAO]F%'\Q#487N?%D/N$K&JN-^VT#;YXS5R?X8 M]E7FP=-8:7XJWTR.L4EUII*VL#R(?R4(>[>+/WH;8VB7GZ9F@S+$G$8ZPLZ0 MF?73O1*$-WL[:,UQ72C"$KAM;=Y3$!"SS%B3FGWHG^UM^"*-MM[,;05_6V,/ M<\1%=M[HD(.X7"I\OO=B:^MML-1GLQ./T-?37#45CAK%]CJ/P_1:+U)N&9E, M9^.@`F8]K#2@"S?3'U_)Z:'P$1?QDQL?9?)HE80J_!1Z[]A@-#K;7T]3NME> M;S_YL_*Q#^CV>2&N:2`.VB.R)]W+I,-PRJ7MQZ)Y!*8K-Q9_?TD?P`B?:,6MV.G\[LEZY:%13+2J!A%T1&UOMBVB9'6]Y1G4BOK_B46E:5EXHS9S3C0 MN>MV--6@%^*^2"VDNE[5FK&Y]6:EEY+^A[5SUY%D28ZHSJ]8<5=8(MX/G:#& M;R#B":Q"+D@J_'L>JZJ9KNZN[,KD7>E>S`P\LR+YSG+3[;6L10%`<,N@"9$CR3HT.O=TJ/=;GK767MW;K-(4,VCT$WI+] MT>=[5[^=3FW;:]N7MS:JI*H,XSO(.[V3I`4O,C[55)/_^C$GM[9$2<7;M2N. M.@#\A1CMJ(4.ITEEM[KL'+G?K]O"73J^V]AB3$CWLY;*,MM81$)-*GW[99M( M1_.;U+C/6;UO:W(0@_LQ;QEY@;^J:T#F&IQ\N`WY!$5M>O2#O+)ZQ`I<4".' MZ%%'X.P12ZEUZXY$!W#D\D0B7/514GG2UL+T/!>3-&\HK$&'3U&\"N. M@#B#ZNJPK[]^ZW/N4DQ\R-2<\<()TF;5;EAXHS>>E?:I&:A`>OF0<\X2:TCQ MYOD`F3J0%DG0$%'36D<&&1"RH*.1?+A*WXB!O:OLG$V^%' M?'8+<''&LF80@_.6?U71VWBOHD=N(MDM/)H=4!=+&W"^:0VB$U]?GRV_N&"1 MP3_/__V/?_O/__G;_A0ZC3?%(>&]:B-PD,<224<[(9I[+4]K_C[=?80.RKV1 MUVQ("X%;!V\-SJ+JB<\%_SUG]6OH.#)G4N>,CB=S0!*2.,1A5N)5'R7PKZR^ M#9TEE-V0S@&%K@102ZU-]BR:56/@1=).T1RA^ M+'))RX>K]#9TTBBH#(B&!UIZ(I&&N8`<9Z89XU$4?\KR/72>'+QLDF;4_>MJ M(.U4(;QWUDGM&Q+'A^GW2?_#P2.RMH&WM?56MT6%NHAQ$S>9`B<]9_6K@Z_, MHFY7$(FQ>=1S(*OA,R[6B9`TAU;?.C@YS*Y>)/--8"%",O#/8G.>%1%3KEC^ MZN#3(<'Y_=B>;>:<<7@2FAHF5YE^OK1].3=`I#*ZG[=N!/[J,$8/=J7>=9)7 M7S[DJH-WQ.@B7E'N$U*WNN]MRF^*L=$]^L=>K=);!R?HC>F#B"S\ADU>SCGL M%K(!?2'5YRT_'+S>>/\M.6S#+H<):N'H/J?;=5!+T9,NVO[]TN%KVGEQUJ(R MS'N_]'`#L4_F:H$4-B.">O'"BSCUUH5Y:/55V#A4RJUTA1>RVT4=,-19XR1X MK$R(H.S2L+L;SPLCMWH:T3BWKUA^A`V_\U[&,P!_9%J>T+\2\\##4NW3 MN3R+[>WU6IP,&TC^O>>Z&>2@2UW%_@/?&RBXNA)XLHQ9\_5#SH5-\C77&P#8 M@5K>QNT,W:S-Z.C>J?QEI-&\/_85.7?_[_FWQ_%-"M$^"F*1#<[QYNR@0Q^/ M.29\<"W`'&2TIRS>*HL-BN=6_!%ZW!4)WH!41"#<.ZA%/C:(Q(8L_VCR5P3N M_UKK_JY1?5OW.S:6%GX6B3Y@B=\="1KK@T&*2)6?,OP,&J64>S>3:7"<#CU5 M9Z;Q+L=1^VZ9)?6ZNCUO^4$HJQ#S=CN]G4M[S4H61[IZ:(FW(7CTGYW.YL^6 M3Q#*#SC:>:YJHXZ]T]@Q&?5J`GP$*72XM0_3]@(;SH=4?04.U;S9%IRK/NE5H/2N4 M?72OE.72.:M?06,!.#FO`6EAIU*M:'X5];::UL[I^%W?@L;*JL!(1$NT]372W,5-)I!:^82&IHKNN!UUN#0SI/-B'&-PU4Z!`W;84.V MP.=:F,/OQ-(@/=<:O;I?W;#O+'X&#;@/>SE*JQDFU#"XPU+]=M8M3#UVO7>@ MH5$65K>@TI\1\<"N.L%^@R?T6D\9?@D:@D[/XD80`F\>CF05PLXJYU8)R7G+ M7T!#+!'I$`:\+@Q37=BL29@)8HNN4LW_$3_ZZUX$P'?L^/._ZL__>M3G3T2E>'-([X!R>]'/.#D1DQ+G]XFE68M6,B.>#F\ MMPQ5O_1^Y1'IZ5>``&A,<_L5.KX-V^\,'.ZIDRWK=DK3;!*O.23HCT>\A)BG MQQ"'M\?@*L6!.Y;7SR/T!)DBPQ=PV.Q5#EG[\6.$-Q]+=D>=6]F"SZVIB@=! M`Z(EM]@4';0F'9^\?M`#=KX_[!OX_/7W$\'YG/YT.S4V/J_F>TOE5AC8';2_ MK-S=[/E`N#XPZ-T3]<\>3]39?;E[GEVU6?G:SK=A'*T[5_U*:HO, M_=SK%\F(C4G@URA^_X"7_^B,;Y5AMDGHZ"U8OXF\U/O M<`]IH-V#"`*$-0FR#5[AWABMOVWF[$U^V(RJ$YD(&_ MVOS[W\>_?Z[E^O#92#:)=U=2)*3MMG$285V7)KLL3`.H)(P4D^\KJP6[]]87*NKTW$3TT,P-N&TUM M).`Q`XI@PJ7J(7^\@'TD%Z]VD^DS[K]Z1"H."4_^7-U\;QYQ!ON,R2R/9GN1 M%KTEG&*W?H]E%WH]Q"N/.,`^X&&RI27ZW535A'WUYF6$CDZ#W_V*T]A7IF^J MMLL)^JK^QURJT\R1N)-OA^3X,O;5O:=5^SWYV@'B!NVD0H*1Q00.U,T?PCX_ MVE:#P')H\*PI@NBIW%&?4-357JO./X1])'.35;Y#`"V5>N@<._2:O(T\^[46 M/8E]ST$TS3*(3Z0B2BQZ',+&A6J"R$.01P<7@G5+5Q*3*,J5 MG5.%T[9O'G$FB,;4W6Q5]8$F>J#C\8S(DWB::^'2(XX(A"EUAN:;QNK91F)O MO:\6XM@AQES>/.)L$`W39AKRK+C)4>A8E;*X5>/P*89#RGPYB-2+N=V,*QH- M8@)Z"DR_FQ`UWBWUEP_Z8P1BFJF[N)F]'W[E6I%,G1_>>\@VOOYI?RB(0F/9 MBDO@D$8\;G4*JH&W:Q[2LH>*\E0065P.OG6_F>D-6$AICZSK[^VRQK:2])J5 MG/A=XW&F^L(BHDN\UZ8Z=91I6D6-Y/>00=49^D)V9RAE.&GW5UF-@U_?N[X; MFAW7)9D!*J6OQ9N[QLK,#A,RQW:/RFJLRC#OYZH$(3]A.>M;4%5QJC'MZ?@G M(7J3+MF^BVWK$4^/+GC^6W4`B`K4B;"*`6R+I$Y+8MX';WZR:,>;8._5!CO. M-0?PJ]&O_)`TJM'(LZH[+#?FZ\><$]QJ*K+QGOO!K)$0!FW=YH:.#H_K93F2 M,]'^@]\K3 M@H,B`;P&R`"R-67-V`T-!&E?;)\X/'\*)MXUM&)M[[IJWBP$8ID?UI:Z0??S MVI\I/_P=3+KM@&RQKP;AHE(RS:5J$\'?;9OUI-UOP20:[2?.#9#EMO>V:4HA ME1OM&C^\[_M@*C&JSX5J]#Z:D4X\8^ZJ#3*EF,ET^6/*(;H;]#[YS=(;SY/!S MY1&;"<&IJ%V=NDWSEE.:VV^H^I/Q,T69OQT^>75T6_']DJ;+AAAJ3LW/IK)N MY:3=;P[/VR$CK+ID09<5U#VA.C*@T>0DD4(U3UPA1 M'61_RJ1GCVJ?'#[%-FW+FLR06O!IS&;\[3IMD)'[07;OQP^)K3+K5I80].J[1H*&,%WS0RT&AJ!`$F`Z?IM M_$R]!GPK/*8`HUV2JGHU6+GY#OB:[.:(/@<5^\QCNR\#R6L,?[G1I3!5>QAM M4N,H"`:K+455E.C0IX+X,S4;U@8<\K8.FLYI&ABB>:4UJ$%(#E,T2V&HR.K0 M[F$@8?L^^LLD33")ZN>.QI4^EDTM`KADJKI6O63[5R#9FN_S+E)IH5HUU-G8 MAD?)(?SGK`(#W:N\MGXVD*".Z5:N/C3M`@H\?`AUXI&A-Q7W1FB`-4\2/`\R-&^-8:XU2&OANS4HAB#JT^]+&?K%]3_9!^B!TM6??2(71A' M#2.[O%ORQ2`:GI+?V0J&'-7O<#]B8]$1AMD95$X>MD%#)M)==R*@SE=_/T/# M/H+4]E3A&4T3K'J?;IBIR=`J;UNQC&?G?%_%\!2DTT_H=)D)7$E(W$'RZ-9F MMT?((_ECNS\':6[!^>V:B["9ICO918(%"N?0I(1ZTNZW(*T>361V[[F7YM4T MZ&--$]I8IT5V'-M]'Z1MZ\QR-RG&GF>8H::1R:'+;O7:7++]+4C-;AO6O,:P MW1N\HQFD!E(F^+9F#J^M7P[2'?U&5L2:MT$I;:MYNA7\R4L'U>[U8RX'J5G0 M@92;F7MIZ%<#U7RW:L*&CCRUF)R]U7\*4@GWV=TB`ZDQ)N^BJY2N<4MCF_K# M/IS(=J5M$[;&).OJPI"3$#[5H2V9Q42 M9G0'8+".[?X<2#VYV0!99&[(_`RGMF96)945EW'[I-UO@13\F-8ATO?,71,, MU7]4"P1Z)23D#^OP/I#PN$U M8U34L[Y6L7<&P`EB[&&X(T+XM1F/%ZK]X$D9(D5I(%OD.[4`!\R/-ZNI(_2^`NV MOP<27KW(U'NS8NHP"XLX\K!A]%(%=?0%IFNL\:Z"50:Z\*4-Q`#UGG1D@@.& M!T$+ESDR^W,8L;":UCCRAI.O:3?KTH>ID6CJ<.ES9I^CZ/X-!/0*-D:[#?6]0@\=?X-9#`\JPDW;]CVR@?6*Z6\Q!,TM M>9/[2RO(4=S#6.=6U(D,JQY>&K\<0M:3C?!SI!AZ/96A%NKAJ[K79NC^Y5,N M1%"YW9E`@P9N%]"/82@=D9J\08.%"*J[XZW]!]#%TZ:OL\5/IJ^1Q4%X[^TW M4C1T8,O5U9%&FMJ.]_OR8?LL5RSWR359.2/B+"KF,M&$:;(-^E2'YGX?FOTY M-$-`!<6R=0YB\0J3S2*#.(?CK.3'.;/?0G/7"8%8ZMS)OEA7A\:NC9FUQBV$ M0[/O0Y.T,UG*'8F?A8,X4A!RL>IC+<5?,_TM-+N^W@2K;\[698J*!`O$Y]83 M4DK=+XU?#LV4QD8U>@?XW;[+I$IC\HX+19^K>.TBET-S391A-'T.5D_S&60Q-.FOZ>V!A?2!\RB6N]]KLEYZ+,.C7+5P.G.'9G^.GV6Z#D%A*26P=?+M-8?7U]?6UK20 M4V:_Q<_,V^(M;L=TFSV`Z=QOWXBIJG;IAV;?QX\FSNF--41GJFX0W"XZ"U1P MNGG\QJ=2&WNU%W2DIEJC?!S7T(V:OG!0XFOCUV66YYUU;:EF8-,7$$X&U5@P MT''/]/(IE^.GEYR7FMK2AH,Q-_O9)\_7"A_@'<\+3I7_%C-*GW$3_- MEZ9OX"")9D^EC#F7NAJZ=:8=G$?IIO?VG9//%:Q__A?]V5_^J9KP*W=6EPPI M)\Y"T!=]0\"87H?5C-*9R_%)W0O[[O<#K,D:0WD[8@RU[MENOQV@/-/+@3[=))=,@Z+J.MJ(*][9%A26GBI:4CD](7SSF M@Q,\GG/C&O?B`D_R[R%V`B/#B:J')<4,)]NCF];/GDS=##]7?SUMN:;V+_6/ MS45V-3[.06;1AU9PM-H.3C?.;SG@/B$P5:.7+'NAFB^SB]IDTEJ?#M?>VG^Y MY=".I@\IS$IX09L\X!K,[:MQ78,LSSS@Q);G8&+1T:G3-_B&`6#-\CTMB&6, M\?A<[,R6/V_(0HPM31+S?9+EU9$S.CIJ-'T>PASK^Y,;THM*J%M`\HVXBL8W M+Y*:O@\5^O-=Z`G[+S<$1JP9*&MOH5[7M8V^HU%S*\.73R=]AP\XL2'J$\!7 M]7&HI=Y]TL=8=0^[W?^U=RV]C2-'>*[RKR!F#]D!/+/];O:>$FP2(`@V`9+< M!_VTN2M+7HD>VPGVO^B^0I"FVL1T MV"@5D3SDBF>PFTH6P(D.:O2FQ=BN(7EW@B$EG^8ABW".\BW`D[U\V M:$L^KX,C!E.;RTQ%G>&N2HAQL+4\`F<8WS6P2N"%\,ZPQN0O0<:HZBBBJ2E8 M`P[E#NX?'N`U]+XUY>2!]5,4G`@*SX4R4'04GO+U\1W[>H='>&$R=?5[NUT* M$#84:V#>T^E;;RG5"VUU6PMS3[U%S]$0+]I+Y_#'N[:23 M:K`)Z$`T[)E7"]KN('&NNBS[W?Z6@;_L'17K@YV25(;5JV2@+(HPS\W+V3,2 M)4YI8NA4%DU[.G.IBU644!-:DA*\*-ASA3L#5?=RNHR'B5-1&[V*3'21,AE& M#QM7.7@61&<-/S134:E7-M!HG#A,!;T*E-?)4AH7#F&!S2/AXU,A5VZ"H;36 M[#4-]@P4'RA"Z\A9,UR21TMYG@L5+'8Z),6Q>.S>PCE`$4)!1:,4%6%56#6L M9`4Z%Z"U<77,(^;"_HJ04G>E4J=:4PR],P5.AJ+S'J9.W#Y;.0Z+%1\H0BJH M1K1AE$VAP.P56!T+A8X(22DAW\+85Q'6.>;:F-RE\H91B#&`B'7=3"8E*"P)=FNA MLK)D:3/&`]4P*%X697:;+_M/)I],#C;``>)6>EUG#2GGN$?"G]9JQ!+;?S(9 M2]7:J`2/*O!_J/83"2'LP4!OBT?,L/TG4\X\PRHR5(.7TO?#7XQ.8?75 M$NMAU-Z7753[JLFD*%.YARW."]!%8J1GP2^A895[8[=#?M5DRJ%0F&\H-5Q8 M^&70MLE101=H*P.U_A8]QR>3@$])$7KL`5/G(WO@"7X?N\2'`K^??<\>)-7; MK$H6E-"&;%SH+MV=683!42B[ORAL=['O0066S0J,#@87Y4+65,VF4)9D1=77J+B6LR8S MX9Y*F;VJO?IL8/MAU1E+/8Q[+F$APHV0/N5D:]J4IPU/OL$:'U@7=+T'IK@R<*#A7R:* M)Z\=G&A5T\I*AR:%&("-#ZT[8C!`6VNK'(?S#.L=O5^D&`"='+_0-G6 M.0S+T4(9@Z'M"29MMBQ0(I^8K"L`C!P3#2Y+CMZ/EL\X>&@I">T*I:+E7F#Y MD<+3@6$Z0%Q82&PT@_ZA0R.I3\Q031I6BA(.-U%DKC/!:?NLFL/8T&KH/;41 M?U%\KXHE3)T.K4MM5EFA2TTO'A4EKQ,VR1A,E]W.\F`'+SSYELWMIZ'M"1:A M$HU/T/@&NE]F2FTD.?CGX76XR`9@K[?K#@:+)DB*4U6UKZ$3H?RMIG!;22EB M!ML/?,O>QI".FM7U`"VH-9I9H5'!)G#314/N/O1O<71`A`J$0+/`%N>#8"?N MQPFY%UHM`T4,%@ZE7YM4X$K#J:4S4>`;&]A"0!NEY%YH<%VLHF54:SAJ$E8( MAWNKZ+TRS-W:#M'&2.GZ.@QK.+A#*SBCZQ[.$.-@AAB7E*!PCACAO1A-QYJP MCEKM893LS@H_'-N^8$E1^"5YA$6#=8&*6*;H5:!J6V/YSX\`PT)M2V+<1)BQ M@I8""[N(]O:236808_\J<_8S^P`VEARNV1YK?Z=(XLK*4@H*I?(U'5RS5,I3 M8D%+-2.+5?M(+W>'`6?32LEF+(-;/FFA]PS7>5ZS-5 M5/04_!-4=U0[PMV"YE0;]VK;H;V-B.P'QCU,`0>IR;&FZA/0'1$N/&99J#4T MU^BAID/!J+H,)>,J@8)V'9T3]`7F>,0*2J0=/5#R3!XI^G7`M;CF6CW@&LN8 M7SJP6DC,9)5*EXX.!C*<./)?G[@V1L=]P9*CU%J1/"CYPB&:#M"\9J98)0%!P$LG'),--H M]Y#QB('F\0CO0\%,'1AE#BE0DG5*5/,X8\TA%4F9XW:\57@EC["CW`"-"D/W M7,M1]%RC9$R5EDY2CG%)6?.HNBSL"!@*6423,N/BB6MC=-P7#-8QIB3\3@ZQ M@-<;,N=P9T+,--56R2K>HN/>8%T>46B-3+\I*!_LH?*% M#YY.!7>YA\"_1"]7"[WO\J*/P3J5/):&"LGF&4*<,L8C.T<$#JM)JU`#L MZ^71YEP\3Y2?.\"ZHVK;MC`*4"STHB\,P$;HR*'QM.V"M)QS6123A;',8AGV M419*JLN"+J4>G-'6^V5['3S:2PHZRHK"UX*'P:0EDY1TF$I[ZH&YJ\=">3:/ M?G=NO[FV11*^(['Y2&+SW49DO@8#/II1JGI7514ET!S^1N-4`:ZJ:';"#N'6 MXI+67+VKV*D&.=;NEJU?5-6[Y2*.?N^M__^?MHMOJA_FMX^+YNJZK;[]X0,5 MR;67^%%7?_:+19Y.JQ_C7_TCOO<'?.Z^MZP6>9D77W+Z=/$-_O&OZV99E6:: M*_R^]8NVFI>JO<[5G^>+MBF/56J6[:()=VTSGUU6OFKG\^G/35N5^0*WW]U> M+7QJ9E?=/7'Q>-O.<>7VNHD5[LNSJ_9Z_<2_Y789_2T^^"_-E6^[!]SG4(7% M_!Y]PM/OVNOY(JCOO`!8Y-K=-GK75W2SE!5W# M764^G<[ONR[FQ+]>WKWMWXQ\U-Z&>ZB_U]S2Q.[ZC/S0P]>>S4 M?%[$QD^[!U&[R:GQ+^B..S??K&[OPK2)GOY5?0M&5/G!W]R"AS_\\>,__O[C MY=.C\)"?+ZLPG^/GC;_R_VYF^;+Z:7ZWF/GIA^J^`;WOP,MF@4'.0^N;V9J7 M/2]^MWQZ5GZXA>B`ZJ!BLUP"NQ^[?#'VKK.KH=W.9\2.3@"&W]B0Y^GQF^%- M'TE&Y]-TB=\I?\G3^6WN_KA?-&V;08X\N_:S%47GZ.WBOEEN'G6WQ'_\LAM& M\$L2\.?T^X).W2U`B1T$>'K2D!`[":!`@'_>A9]R;->2Z`/D9"!E&"C1=1[Z MJ5=]RS_*#Y?/B+)A/V@#L2&%WE%B*#V@QUHLUJ*GU^1?SDM[[Q?YVF)6/Q)S%!WUA\L! MNUY,072U%P::PGC.LGVE*WK5\DS;3-"`V?K8_K[T:O#3++<7%Q".MOK/Q00: M[N;&+R83_HE?3+`&7>5V,GG?K;U?%%,?067<]VG+`OT>W\\/[>=Y*4OH&PYBLOGXQ@<3G";Y>)Y?2Q61U M.RYD_#%-G[_XZ5V>O/]3U\5+]&>6[]<75TK_/6`^WV`N/`.@?F\>SQU,;S=\ M/KI,5,.WNK_HE2^]AGX0_:>+"5TV3Y?-@9?1IU_$2(=T<2*H88>L&8Z8/41+ M+@3]X*Q_/KU+6_6T_S&DQM8;^,L;T"MV4*]J]F:OV&BO'%U<_>AO&%[I+Z-7 M;DNO:+%&M\18_YQXWK_:K?LGV&2RNROXWZ\7"_:<&+U(OH;U@O)##&&]>@[; M#UWL(D)_L7[&B.71X)%M`]_)@6U2L,3%X\!S/`&X.!*<\_H$Z/)8=+65ZP>B MJV/1[2G8KH]%=Z?@N]F-SD?1XRGX;H]%+Z?@>WTDNA"GX+L[DN]"G8#O_%A- M)^P)^,Z/575BNY8_$'U$UXWS/9V`[WQ$UXVCEU/P?437C:)+<0J^C^BZ<71] M"KZ/Z+I1J9,O3:ZCT$=TW3BZ/P7?1W3=.'HZ!=^/U75*GV#LXEA=I^H3C%T< MJ^M4.(',BV/M.I5/(//B6+M.LU/P_5B[3LNOY_O_^MWNN9W;N9W;N9W;N9W; =N9W;N9W;N9W;N9W;N9W;N?VVVW\!.E]LU`#(``#_ ` end To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 7 02:18:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA23527 for freebsd-current-outgoing; Tue, 7 Apr 1998 02:18:02 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from solaric.UkrCard.COM (ukrcard-gu.gu.net [194.93.170.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA23495 for ; Tue, 7 Apr 1998 02:17:51 -0700 (PDT) (envelope-from alex@UkrCard.COM) Received: from localhost (alex@localhost) by solaric.UkrCard.COM (8.8.8/8.8.8) with SMTP id MAA16934; Tue, 7 Apr 1998 12:17:10 +0300 (EEST) (envelope-from alex@solaric.UkrCard.COM) Date: Tue, 7 Apr 1998 12:17:08 +0300 (EEST) From: Alexander Tatmaniants To: Taguchi Takeshi cc: freebsd-current@FreeBSD.ORG Subject: Re: Current with XFree86 3.3.2 In-Reply-To: <19980407153257G.taguchi@tohoku.iij.ad.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 Tue, 7 Apr 1998, Taguchi Takeshi wrote: > > I changed line 682 in xc/programs/Xserver/os/xalloc.c to read > > > > pagesize = getpagesize(); > > > > and the XF86_SVGA server now works. > > -STABLE with XFree86 3.3.2 also needs this modification. > XF86_SVGA seem work fine, but XF86_S3V still dump core ... As XFree86 3.3.2 RELNOTES says -- you should not use XF86_S3V, you should use XF86_SVGA server instead for S3ViRGE support. > > 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 Apr 7 02:56:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA27650 for freebsd-current-outgoing; Tue, 7 Apr 1998 02:56:08 -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 CAA27591; Tue, 7 Apr 1998 02:55:16 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [194.198.43.36]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id KAA14103; Tue, 7 Apr 1998 10:54:29 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id LAA05875; Tue, 7 Apr 1998 11:55:12 +0200 (MET DST) Message-ID: <19980407115512.57503@follo.net> Date: Tue, 7 Apr 1998 11:55:12 +0200 From: Eivind Eklund To: Frank Nobis , Poul-Henning Kamp Cc: current@FreeBSD.ORG Subject: Re: LINT broken in brooktree848.c ? References: <9394.891847811@critter.freebsd.dk> <199804061735.TAA13185@trinity.radio-do.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <199804061735.TAA13185@trinity.radio-do.de>; from Frank Nobis on Mon, Apr 06, 1998 at 07:35:34PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Apr 06, 1998 at 07:35:34PM +0200, Frank Nobis wrote: > > > > cc -c -O -pipe -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wuninitialized -nostdinc -I- -I. -I../.. -I/usr/include -DKERNEL -include opt_global.h ../../pci/brooktree848.c > > ../../pci/brooktree848.c:232: opt_bktr.h: No such file or directory > > Oops, my fault. > > The last patch was incomplete. I forget to update options.i386 > since I need to override the tuner detection. > > Here is a patch: This is a style-violation compared to the description at the start of conf/options. First of all, it's option definition should go in conf/options, not i386/conf/options.i386, as the cards are not i386 specific. Secondly, the #define should end up in opt_brooktree848.h (or in opt_override_tuner.h if more files in brooktree848.c is in the loop for using it). Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 7 06:01:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA20235 for freebsd-current-outgoing; Tue, 7 Apr 1998 06:01:44 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cons.org (knight.cons.org [194.233.237.86]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA20224 for ; Tue, 7 Apr 1998 06:01:31 -0700 (PDT) (envelope-from cracauer@cons.org) Received: (from cracauer@localhost) by cons.org (8.8.5/8.7.3) id PAA07388; Tue, 7 Apr 1998 15:00:45 +0200 (CEST) Message-ID: <19980407150043.03815@cons.org> Date: Tue, 7 Apr 1998 15:00:43 +0200 From: Martin Cracauer To: Bruce Evans , cracauer@cons.org Cc: freebsd-current@FreeBSD.ORG Subject: Re: make/SIGINT (Re: cvs commit: src/bin/sh jobs.c) Mail-Followup-To: Bruce Evans , cracauer@cons.org, freebsd-current@FreeBSD.ORG References: <199803131513.CAA27634@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary=fdj2RfSjLxBAspz7 X-Mailer: Mutt 0.89i In-Reply-To: <199803131513.CAA27634@godzilla.zeta.org.au>; from Bruce Evans on Sat, Mar 14, 1998 at 02:13:11AM +1100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --fdj2RfSjLxBAspz7 Content-Type: text/plain; charset=us-ascii In <199803131513.CAA27634@godzilla.zeta.org.au>, Bruce Evans wrote: > SIGQUIT handling is still buggy. For the simple Makefile: > --- > foo: > sleep 1000 > --- > killing make with SIGQUIT gives the following behaviours: > > 1. make: exits with status 3 (SIGQUIT) (per the above change). > 2. make -j4: hangs (broken). > 3: gmake: exits with status 1. > 3: gmake -j4: exits with status 1. > > POSIX.2 only requires a nonzero exit status for SIGQUIT. We've just > fixed the handling of SIGINT, SIGTERM and SIGHUP. The appended diff fixes the hangs for `make -j4`->SIGQUIT by exiting with SIGINT exit status. I don't consider it that ugly to report exit on SIGINT to the calling process when the actual signal was SIGQUIT. Alternativly, we could limit coredumpsize = 0 and then exit with SIGQUIT. Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer cracauer@wavehh.hanse.de (batched, preferred for large mails) Tel.: (daytime) +4940 41478712 Fax.: (daytime) +4940 41478715 Tel.: (private) +4940 5221829 Fax.: (private) +4940 5228536 Paper: (private) Waldstrasse 200, 22846 Norderstedt, Germany --fdj2RfSjLxBAspz7 Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=diff diff -c -r /usr/src/usr.bin/make/compat.c make.work/compat.c *** /usr/src/usr.bin/make/compat.c Thu Mar 26 15:41:48 1998 --- make.work/compat.c Tue Apr 7 14:44:31 1998 *************** *** 125,131 **** } } ! exit (signo); } /*- --- 125,134 ---- } } ! if (signo == SIGQUIT) ! exit(signo); ! (void) signal(signo, SIG_DFL); ! (void) kill(getpid(), signo); } /*- diff -c -r /usr/src/usr.bin/make/job.c make.work/job.c *** /usr/src/usr.bin/make/job.c Thu Mar 26 15:41:53 1998 --- make.work/job.c Tue Apr 7 14:53:37 1998 *************** *** 395,401 **** * Leave gracefully if SIGQUIT, rather than core dumping. */ if (signo == SIGQUIT) { ! Finish(0); } /* --- 395,401 ---- * Leave gracefully if SIGQUIT, rather than core dumping. */ if (signo == SIGQUIT) { ! signo = SIGINT; } /* *************** *** 2904,2910 **** } } (void) eunlink(tfile); - exit(signo); } /* --- 2904,2909 ---- --fdj2RfSjLxBAspz7-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 7 07:26:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA02146 for freebsd-current-outgoing; Tue, 7 Apr 1998 07:26:25 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from d182-89.uoregon.edu (d182-89.uoregon.edu [128.223.182.89]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA02140 for ; Tue, 7 Apr 1998 07:26:24 -0700 (PDT) (envelope-from gurney_j@efn.org) Received: (from jmg@localhost) by d182-89.uoregon.edu (8.8.7/8.8.7) id HAA11366; Tue, 7 Apr 1998 07:26:24 -0700 (PDT) Message-ID: <19980407072623.51939@hydrogen.nike.efn.org> Date: Tue, 7 Apr 1998 07:26:23 -0700 From: John-Mark Gurney To: FreeBSD Current Subject: kernel support for memory semaphores/locks... Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 Reply-To: John-Mark Gurney Organization: Cu Networking X-Operating-System: FreeBSD 2.2.1-RELEASE i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have writen a memory block based dynamic allocation system (mmalloc).. I was planning on using a lock to prevent multiple processes from accessing the allocation strutures... but the only real way is using SYSV semaphores... so, how do we go about locking on a shared memory areas? after discussing this with a friend, ther HAS to be a lock based on a shared memory location... the problem with storing the SYSV semaphore semid is that there isn't an atomic way of obtaining the new semid and putting it in a shared location after a machine reboot... so, there are a couple ways we can do this... a) create a new type of file descriptor that is opened on a memory range... there are a couple of features with this... you could use the poll mechanism to obtain a lock on that region, or you could use read/write to this memory location... this could be useful for allowing another process to read/write into your data area... b) create two new sysctl's that do locking/unlocking on a region of memory... this is a simpler method but less powerful... using assembly to do atomic locking isn't an option as you would have to spin on the lock... or is there already a way to do locks using the kernel already? -- John-Mark Gurney Modem Rev/FAX: +1 541 346 9237 Cu Networking P.O. Box 5693, 97405 Live in Peace, destroy Micro$oft, support free software, run FreeBSD Don't trust anyone you don't have the source for To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 7 09:08:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA13204 for freebsd-current-outgoing; Tue, 7 Apr 1998 09:08:01 -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 JAA13170 for ; Tue, 7 Apr 1998 09:07:58 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [194.198.43.36]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id QAA22309 for ; Tue, 7 Apr 1998 16:07:56 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id SAA10679; Tue, 7 Apr 1998 18:07:55 +0200 (MET DST) Message-ID: <19980407180754.16757@follo.net> Date: Tue, 7 Apr 1998 18:07:54 +0200 From: Eivind Eklund To: current@FreeBSD.ORG Subject: /usr/include/pwd.h Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Does anybody know why the uid and gid field here are int's? (Looks like hystorical raisons, as they haven't been changed since 4.4Lite). Can I change them to uid_t/gid_t, or at least to 'unsigned int' so they match with chown(2)? Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 7 10:44:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA27967 for freebsd-current-outgoing; Tue, 7 Apr 1998 10:44:35 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from trinity.radio-do.de (trinity.Radio-do.de [193.101.164.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA27905 for ; Tue, 7 Apr 1998 10:44:27 -0700 (PDT) (envelope-from fn@trinity.radio-do.de) Received: (from fn@localhost) by trinity.radio-do.de (8.8.8/8.8.5/RADIO-1.1) id TAA16050; Tue, 7 Apr 1998 19:44:15 +0200 (CEST) To: Eivind Eklund Cc: current@FreeBSD.ORG Subject: Re: LINT broken in brooktree848.c ? References: <9394.891847811@critter.freebsd.dk> <199804061735.TAA13185@trinity.radio-do.de> <19980407115512.57503@follo.net> From: Frank Nobis Date: 07 Apr 1998 19:44:15 +0200 In-Reply-To: Eivind Eklund's message of "Tue, 7 Apr 1998 11:55:12 +0200" Message-ID: Lines: 79 X-Mailer: Gnus v5.6.4/XEmacs 20.3 - "Vatican City" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "Eivind" == Eivind Eklund writes: Eivind> On Mon, Apr 06, 1998 at 07:35:34PM +0200, Frank Nobis wrote: Eivind> This is a style-violation compared to the description at the start of Eivind> conf/options. Eivind> First of all, it's option definition should go in conf/options, not Eivind> i386/conf/options.i386, as the cards are not i386 specific. Eivind> Secondly, the #define should end up in opt_brooktree848.h (or in Eivind> opt_override_tuner.h if more files in brooktree848.c is in the loop Eivind> for using it). Eivind> Eivind. Your are absolutly right. I tried to do a good job and missed the right place to patch. So I hope this patch would do the job as desired Please don't judge too hard, because this is really the first time I did a patch which influenced more than one file. So again, here is the hopefully correct path. Please test it and commit it, if it's ok now. *** /usr/src/sys/conf/options.orig Tue Apr 7 19:23:33 1998 --- /usr/src/sys/conf/options Tue Apr 7 19:25:21 1998 *************** *** 227,229 **** --- 227,233 ---- # sys/netkey KEY KEY_DEBUG opt_key.h + + # sys/pci/brooktree848.c + # Look into the source for explanation of available values + OVERRIDE_TUNER opt_brooktree848.h *** /usr/src/sys/pci/brooktree848.c.orig Tue Apr 7 19:26:11 1998 --- /usr/src/sys/pci/brooktree848.c Tue Apr 7 19:26:45 1998 *************** *** 229,235 **** #ifdef __FreeBSD__ #include "bktr.h" ! #include "opt_bktr.h" #include "opt_devfs.h" #include "pci.h" #endif /* __FreeBSD__ */ --- 229,235 ---- #ifdef __FreeBSD__ #include "bktr.h" ! #include "opt_brooktree848.h" #include "opt_devfs.h" #include "pci.h" #endif /* __FreeBSD__ */ *** /usr/src/sys/i386/conf/LINT.orig Mon Apr 6 19:29:43 1998 --- /usr/src/sys/i386/conf/LINT Tue Apr 7 19:37:17 1998 *************** *** 1330,1335 **** --- 1330,1339 ---- # # The 'bktr' device is a PCI video capture board. It also has a TV tuner # on board. + # Sometimes it is necessary to override the tuner detection. + # Use the next option for this purpose. + # options OVERRIDE_TUNER=x + # The current values are found in /usr/src/sys/pci/brooktree848.c # controller pci0 controller ahc1 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 Tue Apr 7 11:40:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA11978 for freebsd-current-outgoing; Tue, 7 Apr 1998 11:40:28 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from aldan.ziplink.net (mi@kot.ne.mediaone.net [24.128.29.55]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA11943 for ; Tue, 7 Apr 1998 11:40:21 -0700 (PDT) (envelope-from mi@rtfm.ziplink.net) Received: from rtfm.ziplink.net (rtfm [199.232.255.52]) by aldan.ziplink.net (8.8.8/8.8.7) with ESMTP id SAA08716 for ; Tue, 7 Apr 1998 18:40:11 GMT (envelope-from mi@rtfm.ziplink.net) Received: (from mi@localhost) by rtfm.ziplink.net (8.8.8/8.8.5) id OAA00778 for freebsd-current@freebsd.org; Tue, 7 Apr 1998 14:40:10 -0400 (EDT) From: Mikhail Teterin Message-Id: <199804071840.OAA00778@rtfm.ziplink.net> Subject: /usr/obj and /usr/src To: freebsd-current@FreeBSD.ORG Date: Tue, 7 Apr 1998 14:40:10 -0400 (EDT) X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli" Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA27723 for freebsd-current-outgoing; Tue, 7 Apr 1998 12:58:21 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from solaris.matti.ee (root@solaris.matti.ee [194.126.98.135]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA27617 for ; Tue, 7 Apr 1998 12:58:07 -0700 (PDT) (envelope-from vallo@matti.ee) Received: from localhost (vallo@localhost [127.0.0.1]) by solaris.matti.ee (8.8.8/8.8.8.s) with SMTP id WAA22200 for ; Tue, 7 Apr 1998 22:57:39 +0300 (EET DST) Date: Tue, 7 Apr 1998 22:57:38 +0300 (EET DST) From: Vallo Kallaste X-Sender: vallo@solaris To: freebsd-current@FreeBSD.ORG Subject: Buildworld dated 98.04.07 fails 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 Make buildworld fails for me over a long time with error message: --- yp_xdr.o --- --- yp_xdr.so --- --- yp_xdr.o --- cc -nostdinc -O -pipe -m486 -DLIBC_RCS -DSYSLIBC_RCS -I/opt/src/lib/libc/include -D__DBINTERFACE_PRIVATE -DPOSIX_MISTAKE -I/opt/src/lib/libc/../libc/locale -DBROKEN_DES -DYP -I/obj/usr/src/tmp/usr/include -c yp_xdr.c -o yp_xdr.o --- yp_xdr.so --- cc -nostdinc -fpic -DPIC -O -pipe -m486 -DLIBC_RCS -DSYSLIBC_RCS -I/opt/src/lib/libc/include -D__DBINTERFACE_PRIVATE -DPOSIX_MISTAKE -I/opt/src/lib/libc/../libc/locale -DBROKEN_DES -DYP -I/obj/usr/src/tmp/usr/include -c yp_xdr.c -o yp_xdr.so --- libc.a --- building standard c library --- libc.so.3.1 --- --- libc_pic.a --- --- libc.a --- ranlib libc.a ranlib: libc.a: No such file or directory building shared c library (version 3.1) building special pic c library *** Error code 1 --- libc_pic.a --- ranlib libc_pic.a ranlib: libc_pic.a: No such file or directory *** Error code 1 2 errors *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error Vallo Kallaste vallo@matti.ee To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 7 13:30:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA06196 for freebsd-current-outgoing; Tue, 7 Apr 1998 13:30:59 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA05972 for ; Tue, 7 Apr 1998 13:30:07 -0700 (PDT) (envelope-from mark@grondar.za) Received: from greenpeace.grondar.za (oy0Ac7vAESxXcHzA+F6xkBEM4lfWpHqc@greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.8.8/8.8.8) with ESMTP id WAA09766; Tue, 7 Apr 1998 22:29:59 +0200 (SAST) (envelope-from mark@grondar.za) Received: from grondar.za (mfiZqzsLCrkVxsz6EHUA/U18qgwSw1y5@localhost [127.0.0.1]) by greenpeace.grondar.za (8.8.8/8.8.8) with ESMTP id WAA11147; Tue, 7 Apr 1998 22:29:53 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199804072029.WAA11147@greenpeace.grondar.za> X-Mailer: exmh version 2.0.2 2/24/98 To: Mikhail Teterin cc: freebsd-current@FreeBSD.ORG Subject: Re: /usr/obj and /usr/src Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 07 Apr 1998 22:29:48 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mikhail Teterin wrote: > I received zero responses on this. I suppose, that's because > the answer is obvious, and everybody assumed _someone_ else > has already tald me. No :( > > Please, if the sum of three numbers obtained by > > cat < /dev/random | wc > > happened to be dividable by, say, 7 for you, send me the answer. As the person who put /dev/random into FreeBSD, I may have an interest in the answer to your question. However, I do not understand your question. :-) Please let me know what you are attempting to achieve, and I'll try to help you. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 7 13:49:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA11939 for freebsd-current-outgoing; Tue, 7 Apr 1998 13:49:51 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from limbo.rtfm.net (nathan@rtfm.net [204.141.125.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA11871 for ; Tue, 7 Apr 1998 13:49:33 -0700 (PDT) (envelope-from nathan@limbo.rtfm.net) Received: (from nathan@localhost) by limbo.rtfm.net (8.8.8/8.8.8) id QAA01776; Tue, 7 Apr 1998 16:49:22 -0400 (EDT) Message-ID: <19980407164921.30295@rtfm.net> Date: Tue, 7 Apr 1998 16:49:21 -0400 From: Nathan Dorfman To: current@FreeBSD.ORG Subject: panic from userland via /proc Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG FreeBSD limbo 3.0-CURRENT FreeBSD 3.0-CURRENT #1: Sat Mar 28 16:07:39 EST 1998 nathan@limbo:/usr/src/sys/compile/LIMBO i386 Not *quite* current but the system will reboot after something like: cd /proc/[pid] ./file as any user. The process in question was x11amp, however it was *not* running suid 0 and even if it was a panic from uid > 0 is not a nice thing to have :) there was no kernel panic message left in the logs. -- ________________ _______________________________ / Nathan Dorfman V PGP: finger nathan@rtfm.net / / nathan@rtfm.net | http://www.rtfm.net / To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 7 14:22:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA19080 for freebsd-current-outgoing; Tue, 7 Apr 1998 14:22:52 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA18691 for ; Tue, 7 Apr 1998 14:20:38 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.5) with ESMTP id SAA02167; Tue, 7 Apr 1998 18:44:36 +0200 (CEST) To: John-Mark Gurney cc: FreeBSD Current Subject: Re: kernel support for memory semaphores/locks... In-reply-to: Your message of "Tue, 07 Apr 1998 07:26:23 PDT." <19980407072623.51939@hydrogen.nike.efn.org> Date: Tue, 07 Apr 1998 18:44:35 +0200 Message-ID: <2165.891967475@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >so, how do we go about locking on a shared memory areas? > >after discussing this with a friend, ther HAS to be a lock based on a >shared memory location... the problem with storing the SYSV semaphore >semid is that there isn't an atomic way of obtaining the new semid >and putting it in a shared location after a machine reboot... Make your own lock with the cmp8xchg instruction, just like the kernel does. Check the "lock" instruction on the i386. Also check out the "mplock.[schwhatever]" somewhere in the kernel. >using assembly to do atomic locking isn't an option as you would have >to spin on the lock... No, you'd go to sleep for a jiffy and check again... I belive a yield() syscall is in the pipeline or maybe already in. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "Drink MONO-tonic, it goes down but it will NEVER come back up!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 7 14:25:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA19863 for freebsd-current-outgoing; Tue, 7 Apr 1998 14:25:21 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA19837 for ; Tue, 7 Apr 1998 14:25:14 -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 XAA00436; Tue, 7 Apr 1998 23:15:17 +0200 (CEST) To: Mikhail Teterin cc: freebsd-current@FreeBSD.ORG Subject: Re: /usr/obj and /usr/src In-reply-to: Your message of "Tue, 07 Apr 1998 14:40:10 EDT." <199804071840.OAA00778@rtfm.ziplink.net> Date: Tue, 07 Apr 1998 23:15:17 +0200 Message-ID: <434.891983717@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > cat < /dev/random | wc Is this enough ? cicero1# cat < /dev/random | wc 0 0 0 cicero1# cat < /dev/random | wc 0 1 4 cicero1# cat < /dev/random | wc 0 0 0 cicero1# cat < /dev/random | wc 0 1 3 cicero1# cat < /dev/random | wc 0 0 0 -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "Drink MONO-tonic, it goes down but it will NEVER come back up!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 7 15:01:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA00183 for freebsd-current-outgoing; Tue, 7 Apr 1998 15:01:39 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA29989 for ; Tue, 7 Apr 1998 15:01:08 -0700 (PDT) (envelope-from michaelh@cet.co.jp) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.8/CET-v2.2) with SMTP id WAA07018; Tue, 7 Apr 1998 22:00:08 GMT Date: Wed, 8 Apr 1998 07:00:07 +0900 (JST) From: Michael Hancock To: John-Mark Gurney cc: FreeBSD Current Subject: Re: kernel support for memory semaphores/locks... In-Reply-To: <19980407072623.51939@hydrogen.nike.efn.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 7 Apr 1998, John-Mark Gurney wrote: > I have writen a memory block based dynamic allocation system (mmalloc).. > I was planning on using a lock to prevent multiple processes from > accessing the allocation strutures... but the only real way is using > SYSV semaphores... and these are bad because it's silly to have all the overhead of a syscall to do locking. > so, how do we go about locking on a shared memory areas? > > after discussing this with a friend, ther HAS to be a lock based on a > shared memory location... the problem with storing the SYSV semaphore > semid is that there isn't an atomic way of obtaining the new semid > and putting it in a shared location after a machine reboot... /usr/src/share/doc/papers/newvm.ascii.gz describes an interface that was never implemented, but worth reading. Regards, Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 7 15:07:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA02104 for freebsd-current-outgoing; Tue, 7 Apr 1998 15:07:48 -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 PAA02048 for ; Tue, 7 Apr 1998 15:07:36 -0700 (PDT) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id RAA00583; Tue, 7 Apr 1998 17:07:08 -0500 (EST) (envelope-from toor) From: "John S. Dyson" Message-Id: <199804072207.RAA00583@dyson.iquest.net> Subject: Re: kernel support for memory semaphores/locks... In-Reply-To: from Michael Hancock at "Apr 8, 98 07:00:07 am" To: michaelh@cet.co.jp (Michael Hancock) Date: Tue, 7 Apr 1998 17:07:08 -0500 (EST) Cc: gurney_j@resnet.uoregon.edu, freebsd-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 > On Tue, 7 Apr 1998, John-Mark Gurney wrote: > > > I have writen a memory block based dynamic allocation system (mmalloc).. > > I was planning on using a lock to prevent multiple processes from > > accessing the allocation strutures... but the only real way is using > > SYSV semaphores... > > and these are bad because it's silly to have all the overhead of a syscall > to do locking. > > > so, how do we go about locking on a shared memory areas? > > > > after discussing this with a friend, ther HAS to be a lock based on a > > shared memory location... the problem with storing the SYSV semaphore > > semid is that there isn't an atomic way of obtaining the new semid > > and putting it in a shared location after a machine reboot... > > /usr/src/share/doc/papers/newvm.ascii.gz describes an interface that was > never implemented, but worth reading. > I believe that POSIX has a reasonable scheme. John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 7 15:10:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA02989 for freebsd-current-outgoing; Tue, 7 Apr 1998 15:10:53 -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 PAA02888 for ; Tue, 7 Apr 1998 15:09:59 -0700 (PDT) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id RAA00588; Tue, 7 Apr 1998 17:07:34 -0500 (EST) (envelope-from toor) From: "John S. Dyson" Message-Id: <199804072207.RAA00588@dyson.iquest.net> Subject: Re: kernel support for memory semaphores/locks... In-Reply-To: <2165.891967475@critter.freebsd.dk> from Poul-Henning Kamp at "Apr 7, 98 06:44:35 pm" To: phk@critter.freebsd.dk (Poul-Henning Kamp) Date: Tue, 7 Apr 1998 17:07:34 -0500 (EST) Cc: gurney_j@resnet.uoregon.edu, freebsd-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 > > >so, how do we go about locking on a shared memory areas? > > > >after discussing this with a friend, ther HAS to be a lock based on a > >shared memory location... the problem with storing the SYSV semaphore > >semid is that there isn't an atomic way of obtaining the new semid > >and putting it in a shared location after a machine reboot... > > Make your own lock with the cmp8xchg instruction, just like the kernel > does. Check the "lock" instruction on the i386. Also check out the > "mplock.[schwhatever]" somewhere in the kernel. > > >using assembly to do atomic locking isn't an option as you would have > >to spin on the lock... > > No, you'd go to sleep for a jiffy and check again... I belive a yield() > syscall is in the pipeline or maybe already in. > Yield is in the kernel. John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 7 16:05:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA14221 for freebsd-current-outgoing; Tue, 7 Apr 1998 16:05:43 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from wcc.wcc.net (wcc.wcc.net [208.6.232.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA14190 for ; Tue, 7 Apr 1998 16:05:37 -0700 (PDT) (envelope-from piquan@wcc.wcc.net) Received: from detlev.UUCP (tnt40.wcc.net [208.10.139.40]) by wcc.wcc.net (8.8.8/8.8.8) with ESMTP id RAA22268; Tue, 7 Apr 1998 17:53:44 -0500 (CDT) Received: (from joelh@localhost) by detlev.UUCP (8.8.8/8.8.8) id RAA26476; Tue, 7 Apr 1998 17:57:15 -0500 (CDT) (envelope-from joelh) Date: Tue, 7 Apr 1998 17:57:15 -0500 (CDT) Message-Id: <199804072257.RAA26476@detlev.UUCP> To: toor@dyson.iquest.net CC: phk@critter.freebsd.dk, gurney_j@resnet.uoregon.edu, freebsd-current@FreeBSD.ORG In-reply-to: <199804072207.RAA00588@dyson.iquest.net> (toor@dyson.iquest.net) Subject: Re: kernel support for memory semaphores/locks... From: Joel Ray Holveck Reply-to: joelh@gnu.org References: <199804072207.RAA00588@dyson.iquest.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> No, you'd go to sleep for a jiffy and check again... I belive a >> yield() syscall is in the pipeline or maybe already in. > Yield is in the kernel. Is yield() the same as sleep(0)? 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 Apr 7 16:39:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA19885 for freebsd-current-outgoing; Tue, 7 Apr 1998 16:39:55 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cabri.obs-besancon.fr (cabri.obs-besancon.fr [193.52.184.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id QAA19877 for ; Tue, 7 Apr 1998 16:39:52 -0700 (PDT) (envelope-from jmz@cabri.obs-besancon.fr) Received: by cabri.obs-besancon.fr (5.57/Ultrix3.0-C) id AA21754; Wed, 8 Apr 98 01:23:10 +0100 Date: Wed, 8 Apr 98 01:23:10 +0100 Message-Id: <9804080023.AA21754@cabri.obs-besancon.fr> From: Jean-Marc Zucconi To: freebsd-current@FreeBSD.ORG Subject: no more CTM deltas?? X-Mailer: Emacs Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I did not receive any (cvs-cur) delta in the last 2 days. What is happening? Jean-Marc _____________________________________________________________________________ Jean-Marc Zucconi Observatoire de Besancon F 25010 Besancon cedex PGP Key: finger jmz@cabri.obs-besancon.fr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 7 16:59:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA24209 for freebsd-current-outgoing; Tue, 7 Apr 1998 16:59:46 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ziplink.net (relay-0.ziplink.net [206.15.168.49]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA24202 for ; Tue, 7 Apr 1998 16:59:39 -0700 (PDT) (envelope-from mi@xxx.video-collage.com) Received: from xxx.video-collage.com (xxx.video-collage.com [199.232.254.68]) by ziplink.net (8.8.7/8.8.7) with ESMTP id TAA24181 for ; Tue, 7 Apr 1998 19:59:35 -0400 (EDT) Received: (from mi@localhost) by xxx.video-collage.com (8.8.8/8.8.7) id TAA02729 for freebsd-current@freebsd.org; Tue, 7 Apr 1998 19:58:03 -0400 (EDT) (envelope-from mi) From: Mikhail Teterin Message-Id: <199804072358.TAA02729@xxx.video-collage.com> Subject: Re: /usr/obj and /usr/src are symlinks In-Reply-To: from "stephane@lituus.fr" at "Apr 8, 98 00:21:22 am" To: freebsd-current@FreeBSD.ORG Date: Tue, 7 Apr 1998 19:58:03 -0400 (EDT) X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli" Please, if the sum of three numbers obtained by => => cat < /dev/random | wc => => happened to be dividable by, say, 7 for you, send me the answer. => = =Here is my output : = [...] I believe, I owe everyone an apology. My todays e-mail was confusing. I meant to repeat a question I asked yesterday about buildworld failure in case of /usr/src being a symlink. 'wc < /dev/random' was just a "clever" way of limiting the number of responses. My thinking was: "Ok, so nobody answered, so everybody thought this is an easy question, and is probably already answered". I was afraid, that by asking it again, I'll receive an explanations from every subscriber... Meanwhile, I'm still stuck with "do not know how to make /usr/obj/home/mi/src/tmp/usr/include/sys/types.h" error while trying to bootstrap make for buildworld. /home/mi/src is what /usr/src points to... -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 7 18:11:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA06020 for freebsd-current-outgoing; Tue, 7 Apr 1998 18:11:28 -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 SAA05935 for ; Tue, 7 Apr 1998 18:11:23 -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 KAA22245; Wed, 8 Apr 1998 10:39:20 +0930 (CST) Message-Id: <199804080109.KAA22245@cain.gsoft.com.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Poul-Henning Kamp cc: dannyman , freebsd-current@FreeBSD.ORG Subject: Re: usleep is hosed, timezone problems in current In-reply-to: Your message of "Mon, 06 Apr 1998 08:27:15 +0200." <9183.891844035@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 08 Apr 1998 10:39:19 +0930 From: "Daniel O'Connor" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >afaik, usleep is still hosed. > Please test with -current sources, it should work now, it is based > on nanosleep(2) which is belived to DTRT now. Well, I updated my tree, and recompiled, but no luck.. Though I couldn't run config because it kept saying my config file had a syntax error.. This is real strange since according to cvs log config hasn't changed since March, and my config file hasn't changed since it last worked :( (It also gives the same output for the LINT config file..) [holly 10:28am] /usr/src/sys/i386/conf> config HOLLY config: line 2: syntax error (If I move the lines around it still gives the same output, soooo.. I think something else it screwed, but I don't know what :( So the end result is that I don't think nanosleep was fixed, but I couldn't properly test it because I'm not sure if my reusing my old compile directory (I did make clean on it tho..) used the new sources.. --------------------------------------------------------------------- |Daniel O'Connor software and network engineer for Genesis Software | |http://www.gsoft.com.au | |The nice thing about standards is that there are so many of them to| |choose from. -- Andrew Tanenbaum | --------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 7 18:38:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA13114 for freebsd-current-outgoing; Tue, 7 Apr 1998 18:38:02 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sendero.simon-shapiro.org (sendero-fddi.Simon-Shapiro.ORG [206.190.148.2]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id SAA13083 for ; Tue, 7 Apr 1998 18:37:55 -0700 (PDT) (envelope-from shimon@simon-shapiro.org) Received: (qmail 6005 invoked from network); 8 Apr 1998 01:47:19 -0000 Received: from localhost.simon-shapiro.org (HELO sendero-fxp0.simon-shapiro.org) (@127.0.0.1) by localhost.simon-shapiro.org with SMTP; 8 Apr 1998 01:47:19 -0000 Message-ID: X-Mailer: XFMail 1.3-alpha-032998 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <19980407072623.51939@hydrogen.nike.efn.org> Date: Tue, 07 Apr 1998 18:47:19 -0700 (PDT) Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: John-Mark Gurney Subject: RE: kernel support for memory semaphores/locks... Cc: FreeBSD Current Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 07-Apr-98 John-Mark Gurney wrote: > I have writen a memory block based dynamic allocation system (mmalloc).. > I was planning on using a lock to prevent multiple processes from > accessing the allocation strutures... but the only real way is using > SYSV semaphores... Not true. Try the DLM driver. Faster, cleaner, and distributed (well, remote host is almost done). You can lock anything you want in ways more sophisticated than semaphores can. > so, how do we go about locking on a shared memory areas? > > after discussing this with a friend, ther HAS to be a lock based on a > shared memory location... the problem with storing the SYSV semaphore > semid is that there isn't an atomic way of obtaining the new semid > and putting it in a shared location after a machine reboot... > > so, there are a couple ways we can do this... > a) create a new type of file descriptor that is opened on a memory > range... there are a couple of features with this... you could > use the poll mechanism to obtain a lock on that region, or you > could use read/write to this memory location... this could be > useful for allowing another process to read/write into your data > area... > b) create two new sysctl's that do locking/unlocking on a region > of memory... this is a simpler method but less powerful... > > using assembly to do atomic locking isn't an option as you would have > to spin on the lock... > > or is there already a way to do locks using the kernel already? > > -- > John-Mark Gurney Modem Rev/FAX: +1 541 346 9237 > Cu Networking P.O. Box 5693, 97405 > > Live in Peace, destroy Micro$oft, support free software, run FreeBSD > Don't trust anyone you don't have the source for > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message ---------- Sincerely Yours, Simon Shapiro Shimon@Simon-Shapiro.ORG Voice: 503.799.2313 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 7 19:16:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA21964 for freebsd-current-outgoing; Tue, 7 Apr 1998 19:16:57 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from prairiecomm.prairiecommunications.com (mail.prairiecommunications.com [208.141.230.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA21933 for ; Tue, 7 Apr 1998 19:16:47 -0700 (PDT) (envelope-from alk@pobox.com) Received: from COMPOUND by prairiecomm.prairiecommunications.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.0.1457.7) id 2P498HNA; Tue, 7 Apr 1998 21:12:34 -0500 Received: (from alk@localhost) by pobox.com (8.8.8/8.7.3) id VAA05672; Tue, 7 Apr 1998 21:17:46 -0500 (CDT) Date: Tue, 7 Apr 1998 21:17:46 -0500 (CDT) Message-Id: <199804080217.VAA05672@pobox.com> From: Tony Kimball MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Face: O9M"E%K;(f-Go/XDxL+pCxI5*gr[=FN@Y`cl1.Tn Reply-To: alk@pobox.com To: current@FreeBSD.ORG Subject: cvs-cur deltas have stopped again X-Mailer: VM 6.34 under 20.3 "Vatican City" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG cvs-cur.4200.gz Sun 5 Apr was the last one. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 7 19:35:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA26066 for freebsd-current-outgoing; Tue, 7 Apr 1998 19:35:52 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from toybox.cc.iastate.edu (toybox.cc.iastate.edu [129.186.142.95]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA26059 for ; Tue, 7 Apr 1998 19:35:44 -0700 (PDT) (envelope-from graphix@toybox.cc.iastate.edu) Received: (from graphix@localhost) by toybox.cc.iastate.edu (8.8.7/8.8.7) id VAA19587 for freebsd-current@freebsd.org; Tue, 7 Apr 1998 21:35:43 -0500 (CDT) Date: Tue, 7 Apr 1998 21:35:43 -0500 (CDT) From: Kent Vander Velden Message-Id: <199804080235.VAA19587@toybox.cc.iastate.edu> To: freebsd-current@FreeBSD.ORG Subject: Linking with threads Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG What is the currect way to link a program that is using threads? ' Thanks. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 7 19:41:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA27091 for freebsd-current-outgoing; Tue, 7 Apr 1998 19:41:43 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cimlogic.com.au ([203.36.2.25]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA27084 for ; Tue, 7 Apr 1998 19:41:39 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.5/8.8.7) id MAA22708; Wed, 8 Apr 1998 12:42:31 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199804080242.MAA22708@cimlogic.com.au> Subject: Re: Linking with threads In-Reply-To: <199804080235.VAA19587@toybox.cc.iastate.edu> from Kent Vander Velden at "Apr 7, 98 09:35:43 pm" To: graphix@toybox.cc.iastate.edu (Kent Vander Velden) Date: Wed, 8 Apr 1998 12:42:31 +1000 (EST) Cc: freebsd-current@FreeBSD.ORG 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 Kent Vander Velden wrote: > > What is the currect way to link a program that is using threads? ' gcc -pthread -o progname ... -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org 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 Apr 7 20:07:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA29741 for freebsd-current-outgoing; Tue, 7 Apr 1998 20:07:18 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from shadow.worldbank.org (shadow.worldbank.org [138.220.104.78]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA29731 for ; Tue, 7 Apr 1998 20:07:15 -0700 (PDT) (envelope-from adhir@worldbank.org) Received: from localhost (adhir@localhost) by shadow.worldbank.org (8.8.8/8.8.8) with SMTP id XAA11104; Tue, 7 Apr 1998 23:06:12 -0400 (EDT) (envelope-from adhir@worldbank.org) X-Authentication-Warning: shadow.worldbank.org: adhir owned process doing -bs Date: Tue, 7 Apr 1998 23:06:12 -0400 (EDT) From: "Alok K. Dhir" To: graphix@toybox.cc.iastate.edu cc: freebsd-current@FreeBSD.ORG Subject: Re: Linking with threads In-Reply-To: <5E7FF673975632A2852565E0000E7DAC.000DB676852565E0@worldbank.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 If there is an option to use native pthreads, use it (there is no mit-threads that works with -current to my knowledge), and link with libc_r. On Tue, 7 Apr 1998 graphix@toybox.cc.iastate.edu wrote: > What is the currect way to link a program that is using threads? ' > > Thanks. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -------------------------------------------------------------------- \||/_ Alok K. Dhir Phone: +1.202.473.2446 oo \ S13-069, ISGMC Email: adhir@worldbank.org L_ The World Bank Group Washington, DC \/ ------------------------------------------------------------------------| "Unix _is_ user friendly - it just chooses friends selectively..." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 7 20:10:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA00382 for freebsd-current-outgoing; Tue, 7 Apr 1998 20:10:28 -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 UAA00369 for ; Tue, 7 Apr 1998 20:10:27 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id UAA08526; Tue, 7 Apr 1998 20:02:57 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd008523; Wed Apr 8 03:02:54 1998 Date: Tue, 7 Apr 1998 19:57:54 -0700 (PDT) From: Julian Elischer To: John Birrell cc: Kent Vander Velden , freebsd-current@FreeBSD.ORG Subject: Re: Linking with threads In-Reply-To: <199804080242.MAA22708@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 weellll you should also compile with -DTHREAD_SAFE no? On Wed, 8 Apr 1998, John Birrell wrote: > Kent Vander Velden wrote: > > > > What is the currect way to link a program that is using threads? ' > > gcc -pthread -o progname ... > > -- > John Birrell - jb@cimlogic.com.au; jb@freebsd.org > 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 Tue Apr 7 20:12:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA00899 for freebsd-current-outgoing; Tue, 7 Apr 1998 20:12:05 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cimlogic.com.au ([203.36.2.25]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA00794 for ; Tue, 7 Apr 1998 20:11:59 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.5/8.8.7) id NAA22780; Wed, 8 Apr 1998 13:12:59 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199804080312.NAA22780@cimlogic.com.au> Subject: Re: Linking with threads In-Reply-To: from Julian Elischer at "Apr 7, 98 07:57:54 pm" To: julian@whistle.com (Julian Elischer) Date: Wed, 8 Apr 1998 13:12:59 +1000 (EST) Cc: jb@cimlogic.com.au, graphix@toybox.cc.iastate.edu, freebsd-current@FreeBSD.ORG 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 Julian Elischer wrote: > weellll you should also compile with -DTHREAD_SAFE no? Yes, until errno.h gets fixed (soon). I did answer the question though. 8-) -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org 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 Apr 7 20:23:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA02945 for freebsd-current-outgoing; Tue, 7 Apr 1998 20:23:03 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from shadow.worldbank.org (shadow.worldbank.org [138.220.104.78]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA02939 for ; Tue, 7 Apr 1998 20:22:58 -0700 (PDT) (envelope-from adhir@worldbank.org) Received: from localhost (adhir@localhost) by shadow.worldbank.org (8.8.8/8.8.8) with SMTP id XAA11191; Tue, 7 Apr 1998 23:21:14 -0400 (EDT) (envelope-from adhir@worldbank.org) X-Authentication-Warning: shadow.worldbank.org: adhir owned process doing -bs Date: Tue, 7 Apr 1998 23:21:13 -0400 (EDT) From: "Alok K. Dhir" To: julian@whistle.com cc: jb@cimlogic.com.au, graphix@toybox.cc.iastate.edu, freebsd-current@FreeBSD.ORG Subject: Re: Linking with threads 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, 7 Apr 1998 julian@whistle.com wrote: > > gcc -pthread -o progname ... The -pthread option to gcc does not appear in the man page. What am I missing? Thanks... -------------------------------------------------------------------- \||/_ Alok K. Dhir Phone: +1.202.473.2446 oo \ S13-069, ISGMC Email: adhir@worldbank.org L_ The World Bank Group Washington, DC \/ ------------------------------------------------------------------------| "Unix _is_ user friendly - it just chooses friends selectively..." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 7 20:34:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA04359 for freebsd-current-outgoing; Tue, 7 Apr 1998 20:34:21 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cimlogic.com.au ([203.36.2.25]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA04341 for ; Tue, 7 Apr 1998 20:34:10 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.5/8.8.7) id NAA22844; Wed, 8 Apr 1998 13:35:01 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199804080335.NAA22844@cimlogic.com.au> Subject: Re: Linking with threads In-Reply-To: from "Alok K. Dhir" at "Apr 7, 98 11:21:13 pm" To: adhir@worldbank.org (Alok K. Dhir) Date: Wed, 8 Apr 1998 13:35:01 +1000 (EST) Cc: julian@whistle.com, jb@cimlogic.com.au, graphix@toybox.cc.iastate.edu, freebsd-current@FreeBSD.ORG 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 Alok K. Dhir wrote: > The -pthread option to gcc does not appear in the man page. What am I > missing? It's defined in the FreeBSD-specific LIB_SPEC definition. I thought it was in the pthread man file... I'll fix that. I'm not sure what the policy is for fiddling with gnu man files. -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org 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 Apr 7 22:27:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA20756 for freebsd-current-outgoing; Tue, 7 Apr 1998 22:27:06 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from taliesin.cs.ucla.edu (Taliesin.CS.UCLA.EDU [131.179.96.166]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id WAA20750 for ; Tue, 7 Apr 1998 22:27:05 -0700 (PDT) (envelope-from scottm@mordred.cs.ucla.edu) Received: (qmail 9839 invoked from network); 8 Apr 1998 05:26:13 -0000 Received: from mordred.cs.ucla.edu (131.179.48.34) by taliesin.cs.ucla.edu with SMTP; 8 Apr 1998 05:26:13 -0000 Received: (from scottm@localhost) by mordred.cs.ucla.edu (8.8.8/8.8.8) id WAA28699 for freebsd-current@freebsd.org; Tue, 7 Apr 1998 22:27:04 -0700 (PDT) (envelope-from scottm) Date: Tue, 7 Apr 1998 22:27:04 -0700 (PDT) From: Scott Michel Message-Id: <199804080527.WAA28699@mordred.cs.ucla.edu> To: freebsd-current@FreeBSD.ORG Subject: Stabler current Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a kernel cvsup'd from this morning, on or about 10am PDT. Was able to do a buildworld w/o strange warning or compiler aborts (I don't want to hear about bad RAM -- I've actually replaced the SIMMs twice and duplicated the same symptoms. I don't think that's a coincidence.) There was one weird hang on NFS, but was unable to duplicate that. Will see how much uptime I can get out of it before I have to actually reboot. -scooter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 8 01:29:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA18269 for freebsd-current-outgoing; Wed, 8 Apr 1998 01:29:49 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.webspan.net (root@mail.webspan.net [206.154.70.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA18262 for ; Wed, 8 Apr 1998 01:29:48 -0700 (PDT) (envelope-from opsys@mail.webspan.net) Received: from orion.webspan.net (orion.webspan.net [206.154.70.5]) by mail.webspan.net (WEBSPAN/970608) with SMTP id EAA00441 for ; Wed, 8 Apr 1998 04:26:09 -0400 (EDT) Date: Wed, 8 Apr 1998 04:29:47 -0400 (EDT) From: Open Systems Networking X-Sender: opsys@orion.webspan.net To: freebsd-current@FreeBSD.ORG Subject: Odd problem with current as of today 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 Is ANYONE seeing this "problem" ? When doing a buildworld it totally wedges on /gnu/usr.bin/cc/doc gcc.info It just hangs then eventually bombs out after sitting on that file for like an hour or so. I do make clean always before doing a make buildworld. So I dont think its from crufty obj code :) My entire current box is kind of in a state of flux :) top and things are vomiting because of the "time" change but that was no big deal since i cvsup daily, but when I went to make a buildworld to fix all of the recent snafu's I've been having It keeps wedging on on /gnu/usr.bin/cc/doc gcc.info. I'm more than sure this is just some STUPID error on my part but ill be damned if I know what it is. I don't recall seeing anything in the current mail that would account for this. Anyone? anybody? Ferris Bueler? Bueler? Bueler? Bueler? Bueler? Bueler? Chris -- "I am closed minded. It keeps the rain out." ===================================| Open Systems Networking And Consulting. FreeBSD 2.2..6 is available now! | Phone: 316-326-6800 -----------------------------------| 1402 N. Washington, Wellington, KS-67152 FreeBSD: The power to serve! | E-Mail: opsys@open-systems.net http://www.freebsd.org | Consulting-Network Engineering-Security ===================================| http://open-systems.net -----BEGIN PGP PUBLIC KEY BLOCK----- Version: 2.6.2 mQENAzPemUsAAAEH/06iF0BU8pMtdLJrxp/lLk3vg9QJCHajsd25gYtR8X1Px1Te gWU0C4EwMh4seDIgK9bzFmjjlZOEgS9zEgia28xDgeluQjuuMyUFJ58MzRlC2ONC foYIZsFyIqdjEOCBdfhH5bmgB5/+L5bjDK6lNdqD8OAhtC4Xnc1UxAKq3oUgVD/Z d5UJXU2xm+f08WwGZIUcbGcaonRC/6Z/5o8YpLVBpcFeLtKW5WwGhEMxl9WDZ3Kb NZH6bx15WiB2Q/gZQib3ZXhe1xEgRP+p6BnvF364I/To9kMduHpJKU97PH3dU7Mv CXk2NG3rtOgLTEwLyvtBPqLnbx35E0JnZc0k5YkABRO0JU9wZW4gU3lzdGVtcyA8 b3BzeXNAb3Blbi1zeXN0ZW1zLm5ldD4= =BBjp -----END PGP PUBLIC KEY BLOCK----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 8 04:29:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA16320 for freebsd-current-outgoing; Wed, 8 Apr 1998 04:29:19 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from second.dialup.access.net (lsmarso.dialup.access.net [166.84.254.60]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA16312; Wed, 8 Apr 1998 04:29:14 -0700 (PDT) (envelope-from larry@marso.com) Received: (from larry@localhost) by second.dialup.access.net (8.8.8/8.8.8) id HAA01031; Wed, 8 Apr 1998 07:28:32 -0400 (EDT) (envelope-from larry) Message-ID: <19980408072827.50306@marso.com> Date: Wed, 8 Apr 1998 07:28:27 -0400 From: "Larry S. Marso" To: freebsd-questions@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: kvm_open: proc size mismatch (22712 total, 664 chunks) Mail-Followup-To: freebsd-questions@freebsd.org, freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i x-no-archive: yes Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I refreshed my current installation with a "minimal" binary install. Now I'm getting errors like this: kvm_open: proc size mismatch (22712 total, 664 chunks) top: Out of memory. when I run top, and the certain virtual terminals just freeze up. Any suggestions? Best regards -- Larry S. Marso larry@marso.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 8 04:32:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA17248 for freebsd-current-outgoing; Wed, 8 Apr 1998 04:32:04 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA17239; Wed, 8 Apr 1998 04:32:01 -0700 (PDT) (envelope-from kpielorz@tdx.co.uk) Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242]) by caladan.tdx.co.uk (8.8.8/8.8.8) with ESMTP id MAA03977; Wed, 8 Apr 1998 12:31:51 +0100 (BST) (envelope-from kpielorz@tdx.co.uk) Message-ID: <352B601F.33F01747@tdx.co.uk> Date: Wed, 08 Apr 1998 12:31:43 +0100 From: Karl Pielorz Organization: TDX X-Mailer: Mozilla 4.04 [en] (WinNT; I) MIME-Version: 1.0 To: "Larry S. Marso" CC: freebsd-questions@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: kvm_open: proc size mismatch (22712 total, 664 chunks) References: <19980408072827.50306@marso.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is the 'binary' install you did compatible with the kernel your running? - i.e. if you install the binaries from 2.2.6-RELEASE you need to be running a 2.2.6-RELEASE kernel ideally... Regards, Karl Larry S. Marso wrote: > > I refreshed my current installation with a "minimal" binary install. > > Now I'm getting errors like this: > > kvm_open: proc size mismatch (22712 total, 664 chunks) > top: Out of memory. > > when I run top, and the certain virtual terminals just freeze up. Any > suggestions? > > Best regards > -- > Larry S. Marso > larry@marso.com > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 8 04:57:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA21165 for freebsd-current-outgoing; Wed, 8 Apr 1998 04:57:00 -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 EAA21160 for ; Wed, 8 Apr 1998 04:56:56 -0700 (PDT) (envelope-from dufault@hda.hda.com) Received: (from dufault@localhost) by hda.hda.com (8.8.5/8.8.5) id HAA02444; Wed, 8 Apr 1998 07:53:59 -0400 (EDT) From: Peter Dufault Message-Id: <199804081153.HAA02444@hda.hda.com> Subject: Re: kernel support for memory semaphores/locks... In-Reply-To: <199804072257.RAA26476@detlev.UUCP> from Joel Ray Holveck at "Apr 7, 98 05:57:15 pm" To: joelh@gnu.org Date: Wed, 8 Apr 1998 07:53:59 -0400 (EDT) Cc: 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 > >> No, you'd go to sleep for a jiffy and check again... I belive a > >> yield() syscall is in the pipeline or maybe already in. > > Yield is in the kernel. > > Is yield() the same as sleep(0)? No, in that the behavior is standard. "man sched_yield" on current. At least for now you need: options "P1003_1B" options "_KPOSIX_PRIORITY_SCHEDULING" 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 Apr 8 05:05:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA22225 for freebsd-current-outgoing; Wed, 8 Apr 1998 05:05:14 -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 FAA22219 for ; Wed, 8 Apr 1998 05:05:11 -0700 (PDT) (envelope-from dufault@hda.hda.com) Received: (from dufault@localhost) by hda.hda.com (8.8.5/8.8.5) id HAA02471; Wed, 8 Apr 1998 07:59:56 -0400 (EDT) From: Peter Dufault Message-Id: <199804081159.HAA02471@hda.hda.com> Subject: Re: kernel support for memory semaphores/locks... In-Reply-To: <2165.891967475@critter.freebsd.dk> from Poul-Henning Kamp at "Apr 7, 98 06:44:35 pm" To: phk@critter.freebsd.dk (Poul-Henning Kamp) Date: Wed, 8 Apr 1998 07:59:55 -0400 (EDT) Cc: gurney_j@resnet.uoregon.edu, freebsd-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 > Make your own lock with the cmp8xchg instruction, just like the kernel > does. Check the "lock" instruction on the i386. Also check out the > "mplock.[schwhatever]" somewhere in the kernel. > > >using assembly to do atomic locking isn't an option as you would have > >to spin on the lock... > > No, you'd go to sleep for a jiffy and check again... I belive a yield() > syscall is in the pipeline or maybe already in. Someone has done this - who remembers? I think at Sarnoff. Search the archives. I think it trys first and then sleeps if busy. You could also use a try first then enqueu a request to a server if you want FIFO behavior, etc. There are many ways to skin this cat. P1003.1B semaphore semantics are in progress. 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 Apr 8 06:57:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA05437 for freebsd-current-outgoing; Wed, 8 Apr 1998 06:57:38 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from d183-205.uoregon.edu (d183-205.uoregon.edu [128.223.183.205]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA05432 for ; Wed, 8 Apr 1998 06:57:36 -0700 (PDT) (envelope-from gurney_j@efn.org) Received: (from jmg@localhost) by d183-205.uoregon.edu (8.8.7/8.8.7) id GAA02490; Wed, 8 Apr 1998 06:55:42 -0700 (PDT) Message-ID: <19980408065541.03335@hydrogen.nike.efn.org> Date: Wed, 8 Apr 1998 06:55:41 -0700 From: John-Mark Gurney To: Poul-Henning Kamp Cc: FreeBSD Current Subject: Re: kernel support for memory semaphores/locks... References: <19980407072623.51939@hydrogen.nike.efn.org> <2165.891967475@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 In-Reply-To: <2165.891967475@critter.freebsd.dk>; from Poul-Henning Kamp on Tue, Apr 07, 1998 at 06:44:35PM +0200 Reply-To: John-Mark Gurney Organization: Cu Networking X-Operating-System: FreeBSD 2.2.1-RELEASE i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Poul-Henning Kamp scribbled this message on Apr 7: > >so, how do we go about locking on a shared memory areas? > > > >after discussing this with a friend, ther HAS to be a lock based on a > >shared memory location... the problem with storing the SYSV semaphore > >semid is that there isn't an atomic way of obtaining the new semid > >and putting it in a shared location after a machine reboot... > > Make your own lock with the cmp8xchg instruction, just like the kernel > does. Check the "lock" instruction on the i386. Also check out the actually, I used the xchg instruction which is even on the 386 and all xchg instructions already assert lock, so it isn't necessary... > "mplock.[schwhatever]" somewhere in the kernel. > > >using assembly to do atomic locking isn't an option as you would have > >to spin on the lock... > > No, you'd go to sleep for a jiffy and check again... I belive a yield() > syscall is in the pipeline or maybe already in. thanks, I've done it this way... and leached most of the source from sys/i386/i386/simplelock.s... also, I decided to back port the yield syscall (note, we now have sched_yield and yield syscalls) to 2.2.1-R and it works great... as a side effect, I found out that my k6/225 can do about 111k context switch + syscalls/sec... now to start testing my mmalloc library now that I have locking in... -- John-Mark Gurney Modem Rev/FAX: +1 541 346 9237 Cu Networking P.O. Box 5693, 97405 Live in Peace, destroy Micro$oft, support free software, run FreeBSD Don't trust anyone you don't have the source for To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 8 07:15:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA07976 for freebsd-current-outgoing; Wed, 8 Apr 1998 07:15:36 -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 HAA07966 for ; Wed, 8 Apr 1998 07:15:33 -0700 (PDT) (envelope-from dufault@hda.hda.com) Received: (from dufault@localhost) by hda.hda.com (8.8.5/8.8.5) id KAA02721; Wed, 8 Apr 1998 10:12:53 -0400 (EDT) From: Peter Dufault Message-Id: <199804081412.KAA02721@hda.hda.com> Subject: Re: kernel support for memory semaphores/locks... In-Reply-To: <19980408065541.03335@hydrogen.nike.efn.org> from John-Mark Gurney at "Apr 8, 98 06:55:41 am" To: gurney_j@resnet.uoregon.edu Date: Wed, 8 Apr 1998 10:12:52 -0400 (EDT) Cc: 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 > > thanks, I've done it this way... and leached most of the source from > sys/i386/i386/simplelock.s... also, I decided to back port the yield > syscall (note, we now have sched_yield and yield syscalls) to 2.2.1-R > and it works great... Yield sinks you to the bottom of the priorities, which is wrong for the fixed priority flavor schedulers, and may be more aggressive than you want. If someone writes a man page for this they should document this behavior. (IMHO) This should be moved to kern_synch since it modifies the priority. Was this added for compatability with another system? 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 Apr 8 08:25:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA19435 for freebsd-current-outgoing; Wed, 8 Apr 1998 08:25:19 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp1.xs4all.nl (smtp1.xs4all.nl [194.109.6.51]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA19425 for ; Wed, 8 Apr 1998 08:25:16 -0700 (PDT) (envelope-from stephw@xs4all.nl) From: stephw@xs4all.nl Received: from xs1.xs4all.nl (stephw@xs1.xs4all.nl [194.109.6.42]) by smtp1.xs4all.nl (8.8.8/8.8.8) with ESMTP id RAA10722 for ; Wed, 8 Apr 1998 17:25:15 +0200 (MET DST) Received: (from stephw@localhost) by xs1.xs4all.nl (8.8.8/8.8.6) id RAA09418; Wed, 8 Apr 1998 17:25:14 +0200 (MET DST) Message-ID: <19980408172513.64392@xs1.xs4all.nl> Date: Wed, 8 Apr 1998 17:25:13 +0200 To: freebsd-current@FreeBSD.ORG Subject: ipsec 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 Hi, I was wondering if there is any recent development putting ipsec support into freebsd. The least recent stuff I've seen was done last june for 2.2 bye, @rak ----------------------------<> _@r4k.net <>-----------------<> xs4all <>--- An idea is not responsible for the people who believe in it. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 8 11:28:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA26364 for freebsd-current-outgoing; Wed, 8 Apr 1998 11:28:46 -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 LAA26350 for ; Wed, 8 Apr 1998 11:28:33 -0700 (PDT) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id NAA07514; Wed, 8 Apr 1998 13:28:11 -0500 (EST) (envelope-from toor) From: "John S. Dyson" Message-Id: <199804081828.NAA07514@dyson.iquest.net> Subject: Re: kernel support for memory semaphores/locks... In-Reply-To: <199804081412.KAA02721@hda.hda.com> from Peter Dufault at "Apr 8, 98 10:12:52 am" To: dufault@hda.com (Peter Dufault) Date: Wed, 8 Apr 1998 13:28:11 -0500 (EST) Cc: gurney_j@resnet.uoregon.edu, 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 > > > > thanks, I've done it this way... and leached most of the source from > > sys/i386/i386/simplelock.s... also, I decided to back port the yield > > syscall (note, we now have sched_yield and yield syscalls) to 2.2.1-R > > and it works great... > > Yield sinks you to the bottom of the priorities, which is wrong for > the fixed priority flavor schedulers, and may be more aggressive > than you want. If someone writes a man page for this they should > document this behavior. > > (IMHO) This should be moved to kern_synch since it modifies the priority. > It only modifies the priority temporarily. Our priority scheme is really silly anyway (with the action of tsleep on the priority scheme.) When the process is waken up, the priority is really odd (temporarily high, but long-term correct.) > > Was this added for compatability with another system? > It was added to support some threads work. John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 8 11:52:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA01309 for freebsd-current-outgoing; Wed, 8 Apr 1998 11:52:21 -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 LAA01213; Wed, 8 Apr 1998 11:52:13 -0700 (PDT) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id NAA07638; Wed, 8 Apr 1998 13:52:09 -0500 (EST) (envelope-from toor) From: "John S. Dyson" Message-Id: <199804081852.NAA07638@dyson.iquest.net> Subject: Re: kvm_open: proc size mismatch (22712 total, 664 chunks) In-Reply-To: <19980408072827.50306@marso.com> from "Larry S. Marso" at "Apr 8, 98 07:28:27 am" To: larry@marso.com (Larry S. Marso) Date: Wed, 8 Apr 1998 13:52:09 -0500 (EST) Cc: freebsd-questions@FreeBSD.ORG, freebsd-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 > I refreshed my current installation with a "minimal" binary install. > > Now I'm getting errors like this: > > kvm_open: proc size mismatch (22712 total, 664 chunks) > top: Out of memory. > > when I run top, and the certain virtual terminals just freeze up. Any > suggestions? > If you are running the kernel that you really want to be running, then you need to rebuild libkvm, ps, w, systat, etc. John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 8 13:08:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA10877 for freebsd-current-outgoing; Wed, 8 Apr 1998 13:08:54 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sos.freebsd.dk (sos.freebsd.dk [195.8.129.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA10870 for ; Wed, 8 Apr 1998 13:08:49 -0700 (PDT) (envelope-from sos@sos.freebsd.dk) Received: (from sos@localhost) by sos.freebsd.dk (8.8.8/8.8.8) id WAA00304 for current@freebsd.org; Wed, 8 Apr 1998 22:08:48 +0200 (MEST) (envelope-from sos) Message-Id: <199804082008.WAA00304@sos.freebsd.dk> Subject: Large IDE drive support added (I hope) To: current@FreeBSD.ORG (FreeBSD current) Date: Wed, 8 Apr 1998 22:08:48 +0200 (MEST) From: Søren Schmidt Reply-to: sos@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL30 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've just added support for LBA mode addressing to the wd driver. I works on "dangerously dedicated" drives, I'm not so certain on fdisk partitioned drives YMMW... Enjoy, and let me know the results -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end .. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 8 13:18:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA11946 for freebsd-current-outgoing; Wed, 8 Apr 1998 13:18:41 -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 NAA11941 for ; Wed, 8 Apr 1998 13:18:40 -0700 (PDT) (envelope-from ljo@Mercury.mcs.net) Received: from Mercury.mcs.net (ljo@Mercury.mcs.net [192.160.127.80]) by Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id PAA17741; Wed, 8 Apr 1998 15:18:38 -0500 (CDT) Received: (from ljo@localhost) by Mercury.mcs.net (8.8.7/8.8.2) id PAA06998; Wed, 8 Apr 1998 15:18:37 -0500 (CDT) From: Lars Jonas Olsson Message-Id: <199804082018.PAA06998@Mercury.mcs.net> Subject: Current boot.flp fails To: current@FreeBSD.ORG Date: Wed, 8 Apr 1998 15:18:37 -0500 (CDT) Cc: ljo@mcs.net X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm trying to install current on a test machine. The same machine has no trouble with 2.2.5 and 2.2.6 installations in exactly same configuration.. With 980408 and 980312 boot.flp's the installation times out after: adding default route to 10.0.0.15 The system is a Texas Microsystems Dual PII SBC w modified Phoenix BIOS, 256MB, SMC 9332BDT, connected to Netgear fast ethernet hub, IP # 10.0.0.17 on a 10.0.0.X network behind a NATD firewall/gateway/DNS server at 10.0.0.15. I'm doing the install in passive FTP mode. Any ideas on what's wrong? Should I try some other SNAP? Jonas To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 8 14:14:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA19605 for freebsd-current-outgoing; Wed, 8 Apr 1998 14:14:30 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cimlogic.com.au ([203.36.2.25]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA19571 for ; Wed, 8 Apr 1998 14:14:23 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.5/8.8.7) id HAA24748; Thu, 9 Apr 1998 07:14:58 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199804082114.HAA24748@cimlogic.com.au> Subject: Re: kernel support for memory semaphores/locks... In-Reply-To: <199804081828.NAA07514@dyson.iquest.net> from "John S. Dyson" at "Apr 8, 98 01:28:11 pm" To: toor@dyson.iquest.net (John S. Dyson) Date: Thu, 9 Apr 1998 07:14:58 +1000 (EST) Cc: dufault@hda.com, gurney_j@resnet.uoregon.edu, current@FreeBSD.ORG 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 John S. Dyson wrote: > > > > Was this added for compatability with another system? > > > It was added to support some threads work. I think that yield() needs to be replaced by the sched_yield() that Peter has coded. We are not currently building libc support for yield(). Any POSIX compatible threads work needs to use sched_yield(). yield() polutes the user's name space, so it should be renamed before being built into libc. I'd like to see any new syscalls named with leading underscores from now on and a weak symbol for the name that the user is allowed to re-define. -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org 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 Apr 8 14:20:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA21765 for freebsd-current-outgoing; Wed, 8 Apr 1998 14:20:30 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.atipa.com (altrox.atipa.com [208.128.22.34]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id OAA21735 for ; Wed, 8 Apr 1998 14:20:12 -0700 (PDT) (envelope-from freebsd@atipa.com) Received: (qmail 17850 invoked by uid 1017); 8 Apr 1998 20:17:37 -0000 Date: Wed, 8 Apr 1998 14:17:37 -0600 (MDT) From: Atipa To: "Søren" Schmidt cc: FreeBSD current Subject: Re: Large IDE drive support added (I hope) In-Reply-To: <199804082008.WAA00304@sos.freebsd.dk> 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 OAA21743 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Will this matter, or only when sharing the disk w/ dumb OSes (DOS/95/NT, et al) that can't handle cylinders over 1024? Kevin On Wed, 8 Apr 1998, Søren Schmidt wrote: > > I've just added support for LBA mode addressing to the wd driver. > I works on "dangerously dedicated" drives, I'm not so certain on > fdisk partitioned drives YMMW... > > Enjoy, and let me know the results > > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- > Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team > Even more code to hack -- will it ever end > .. > > 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 Apr 8 14:49:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA27687 for freebsd-current-outgoing; Wed, 8 Apr 1998 14:49:55 -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 OAA27676 for ; Wed, 8 Apr 1998 14:49:44 -0700 (PDT) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id QAA08206; Wed, 8 Apr 1998 16:48:29 -0500 (EST) (envelope-from toor) From: "John S. Dyson" Message-Id: <199804082148.QAA08206@dyson.iquest.net> Subject: Re: kernel support for memory semaphores/locks... In-Reply-To: <199804082114.HAA24748@cimlogic.com.au> from John Birrell at "Apr 9, 98 07:14:58 am" To: jb@cimlogic.com.au (John Birrell) Date: Wed, 8 Apr 1998 16:48:29 -0500 (EST) Cc: toor@dyson.iquest.net, dufault@hda.com, gurney_j@resnet.uoregon.edu, 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 > John S. Dyson wrote: > > > > > > Was this added for compatability with another system? > > > > > It was added to support some threads work. > > I think that yield() needs to be replaced by the sched_yield() that > Peter has coded. We are not currently building libc support for yield(). > > Any POSIX compatible threads work needs to use sched_yield(). yield() > polutes the user's name space, so it should be renamed before being > built into libc. > > I'd like to see any new syscalls named with leading underscores from > now on and a weak symbol for the name that the user is allowed to > re-define. > Well, I don't mind renaming it, but I need it. (Unless sched_yield does what I need.) John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 8 15:33:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA04500 for freebsd-current-outgoing; Wed, 8 Apr 1998 15:33:29 -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 PAA04441 for ; Wed, 8 Apr 1998 15:33:18 -0700 (PDT) (envelope-from dufault@hda.hda.com) Received: (from dufault@localhost) by hda.hda.com (8.8.5/8.8.5) id SAA03924; Wed, 8 Apr 1998 18:29:59 -0400 (EDT) From: Peter Dufault Message-Id: <199804082229.SAA03924@hda.hda.com> Subject: Re: kernel support for memory semaphores/locks... In-Reply-To: <199804082148.QAA08206@dyson.iquest.net> from "John S. Dyson" at "Apr 8, 98 04:48:29 pm" To: toor@dyson.iquest.net (John S. Dyson) Date: Wed, 8 Apr 1998 18:29:58 -0400 (EDT) Cc: 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 > Well, I don't mind renaming it, but I need it. (Unless sched_yield does > what I need.) sched_yield only does this: > need_resched(); In practice this works the way it should by the spec - it places the current process at the end of any equal priority processes. I've got a regression test that verifies that it works as it should for the fixed priority schedulers. It won't lower the priority so it is different from yield. Can you use "setpriority" to the lowest priority do the same thing as yield does now? (I haven't looked at the source so I don't know if it is changed from the man page) 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 Apr 8 18:25:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA22950 for freebsd-current-outgoing; Wed, 8 Apr 1998 18:25:09 -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 SAA22944 for ; Wed, 8 Apr 1998 18:25:05 -0700 (PDT) (envelope-from grog@lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.8.7/8.8.5) with ESMTP id KAA15120 for ; Thu, 9 Apr 1998 10:55:01 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.8.8/8.8.7) id KAA18356; Thu, 9 Apr 1998 10:55:00 +0930 (CST) (envelope-from grog) Message-ID: <19980409105459.22004@freebie.lemis.com> Date: Thu, 9 Apr 1998 10:54:59 +0930 From: Greg Lehey To: FreeBSD current users Subject: Any big problems with -CURRENT at the moment? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i 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 planning to upgrade my machine to the latest -CURRENT. In view of the problems we've been having lately, I'd like to ask if there are any to be expected at the moment. The mailing list seems relatively quiet. Greg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 8 18:34:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA24516 for freebsd-current-outgoing; Wed, 8 Apr 1998 18:34:29 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.webspan.net (root@mail.webspan.net [206.154.70.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA24503 for ; Wed, 8 Apr 1998 18:34:22 -0700 (PDT) (envelope-from opsys@mail.webspan.net) Received: from orion.webspan.net (orion.webspan.net [206.154.70.5]) by mail.webspan.net (WEBSPAN/970608) with SMTP id VAA09106; Wed, 8 Apr 1998 21:30:36 -0400 (EDT) Date: Wed, 8 Apr 1998 21:34:10 -0400 (EDT) From: Open Systems Networking X-Sender: opsys@orion.webspan.net To: Greg Lehey cc: FreeBSD current users Subject: Re: Any big problems with -CURRENT at the moment? In-Reply-To: <19980409105459.22004@freebie.lemis.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, 9 Apr 1998, Greg Lehey wrote: > I'm planning to upgrade my machine to the latest -CURRENT. In view of > the problems we've been having lately, I'd like to ask if there are > any to be expected at the moment. The mailing list seems relatively > quiet. The calm before the storm. :) I had problems recently in the last 36 hours but It was because my tree was hosed or something so i blew it away and re-cvsup'ed the current tree as of 5am this morning or so, and it built fine im running it now. No problems so far. I've gone back to running sync. softupdates was wedging my machine every 24-36 hours and I kinda just got tired of it. So I went back to sync but everything is running fine so far. It should be safe(tm) right now. Chris -- "I am closed minded. It keeps the rain out." ===================================| Open Systems Networking And Consulting. FreeBSD 2.2.6 is available now! | Phone: 316-326-6800 -----------------------------------| 1402 N. Washington, Wellington, KS-67152 FreeBSD: The power to serve! | E-Mail: opsys@open-systems.net http://www.freebsd.org | Consulting-Network Engineering-Security ===================================| http://open-systems.net -----BEGIN PGP PUBLIC KEY BLOCK----- Version: 2.6.2 mQENAzPemUsAAAEH/06iF0BU8pMtdLJrxp/lLk3vg9QJCHajsd25gYtR8X1Px1Te gWU0C4EwMh4seDIgK9bzFmjjlZOEgS9zEgia28xDgeluQjuuMyUFJ58MzRlC2ONC foYIZsFyIqdjEOCBdfhH5bmgB5/+L5bjDK6lNdqD8OAhtC4Xnc1UxAKq3oUgVD/Z d5UJXU2xm+f08WwGZIUcbGcaonRC/6Z/5o8YpLVBpcFeLtKW5WwGhEMxl9WDZ3Kb NZH6bx15WiB2Q/gZQib3ZXhe1xEgRP+p6BnvF364I/To9kMduHpJKU97PH3dU7Mv CXk2NG3rtOgLTEwLyvtBPqLnbx35E0JnZc0k5YkABRO0JU9wZW4gU3lzdGVtcyA8 b3BzeXNAb3Blbi1zeXN0ZW1zLm5ldD4= =BBjp -----END PGP PUBLIC KEY BLOCK----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 8 18:48:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA27547 for freebsd-current-outgoing; Wed, 8 Apr 1998 18:48:26 -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 SAA27541 for ; Wed, 8 Apr 1998 18:48:22 -0700 (PDT) (envelope-from doconnor@cain.gsoft.com.au) Received: from cain (localhost [127.0.0.1]) by cain.gsoft.com.au (8.8.8/8.6.9) with ESMTP id LAA29494; Thu, 9 Apr 1998 11:17:56 +0930 (CST) Message-Id: <199804090147.LAA29494@cain.gsoft.com.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Greg Lehey cc: FreeBSD current users Subject: Re: Any big problems with -CURRENT at the moment? In-reply-to: Your message of "Thu, 09 Apr 1998 10:54:59 +0930." <19980409105459.22004@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 09 Apr 1998 11:17:55 +0930 From: "Daniel O'Connor" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm planning to upgrade my machine to the latest -CURRENT. In view of > the problems we've been having lately, I'd like to ask if there are > any to be expected at the moment. The mailing list seems relatively > quiet. Well, it seems OK, except that nanosleep() doesn't work for me, but no-one else seems to get it.. Also the fact that I can't run config on my kernel config is kind of annoying, but no-one else seems to be getting these problems, so it could just be me.. --------------------------------------------------------------------- |Daniel O'Connor software and network engineer for Genesis Software | |http://www.gsoft.com.au | |The nice thing about standards is that there are so many of them to| |choose from. -- Andrew Tanenbaum | --------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 8 18:56:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA28663 for freebsd-current-outgoing; Wed, 8 Apr 1998 18:56:13 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from thing.dyn.ml.org (root@pm386-14.dialip.mich.net [35.9.11.207]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA28658; Wed, 8 Apr 1998 18:56:08 -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 VAA04670; Wed, 8 Apr 1998 21:56:02 -0400 (EDT) (envelope-from mcdougall@ameritech.net) Message-ID: <352C2AB1.4E7BE56C@ameritech.net> Date: Wed, 08 Apr 1998 21:56:01 -0400 From: Adam McDougall Reply-To: mcdougall@ameritech.net X-Mailer: Mozilla 4.05 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: current@FreeBSD.ORG CC: FreeBSD current users Subject: Re: Any big problems with -CURRENT at the moment? References: <19980409105459.22004@freebie.lemis.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greg Lehey wrote: > I'm planning to upgrade my machine to the latest -CURRENT. In view of > the problems we've been having lately, I'd like to ask if there are > any to be expected at the moment. The mailing list seems relatively > quiet. > > Greg > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message Nothing out of the ordinary here,... FreeBSD bsdx.dyn.ml.org 3.0-CURRENT FreeBSD 3.0-CURRENT #8: Mon Apr 6 15:50:35 EDT 1998 user1@bsdx.dyn.ml.org:/usr/src/sys/compile/BSDXKRNL i386 Anyone know if the 'Right Thing' was committed to fix the xterm/netscape slowness? I didnt notice it myself on this build, but it may have been fixed behind my back? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 8 19:23:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA01035 for freebsd-current-outgoing; Wed, 8 Apr 1998 19:23:37 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from arh0300.urh.uiuc.edu (arh0300.urh.uiuc.edu [130.126.72.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA01026; Wed, 8 Apr 1998 19:23:33 -0700 (PDT) (envelope-from dannyman@arh0300.urh.uiuc.edu) Received: (from dannyman@localhost) by arh0300.urh.uiuc.edu (8.8.8/8.8.5) id VAA07341; Wed, 8 Apr 1998 21:23:26 -0500 (CDT) Message-ID: <19980408212325.63643@urh.uiuc.edu> Date: Wed, 8 Apr 1998 21:23:25 -0500 From: dannyman To: mcdougall@ameritech.net, current@FreeBSD.ORG Cc: FreeBSD current users Subject: Re: Any big problems with -CURRENT at the moment? Mail-Followup-To: mcdougall@ameritech.net, current@FreeBSD.ORG, FreeBSD current users References: <19980409105459.22004@freebie.lemis.com> <352C2AB1.4E7BE56C@ameritech.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <352C2AB1.4E7BE56C@ameritech.net>; from Adam McDougall on Wed, Apr 08, 1998 at 09:56:01PM -0400 X-Loop: djhoward@uiuc.edu X-URL: http://www.uiuc.edu/ph/www/djhoward/ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Apr 08, 1998 at 09:56:01PM -0400, Adam McDougall wrote: > Anyone know if the 'Right Thing' was committed to fix the xterm/netscape > slowness? I didnt notice it myself on this build, but it may have been > fixed behind my back? Those troubles passed, and brouht me a usleep() bug, which is now fine. -dan -- // dannyman yori aiokomete || Our Honored Symbol deserves \\/ http://www.dannyland.org/~dannyman/ || an Honorable Retirement (UIUC) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 8 19:26:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA01837 for freebsd-current-outgoing; Wed, 8 Apr 1998 19:26:07 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [206.246.122.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA01777; Wed, 8 Apr 1998 19:25:57 -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 VAA00917; Wed, 8 Apr 1998 21:24:36 -0400 (EDT) Date: Wed, 8 Apr 1998 21:24:36 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@localhost To: Adam McDougall cc: current@FreeBSD.ORG, FreeBSD current users Subject: Re: Any big problems with -CURRENT at the moment? In-Reply-To: <352C2AB1.4E7BE56C@ameritech.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 8 Apr 1998, Adam McDougall wrote: > Greg Lehey wrote: > > > I'm planning to upgrade my machine to the latest -CURRENT. In view of > > the problems we've been having lately, I'd like to ask if there are > > any to be expected at the moment. The mailing list seems relatively > > quiet. > > > > Greg > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > Nothing out of the ordinary here,... > > FreeBSD bsdx.dyn.ml.org 3.0-CURRENT FreeBSD 3.0-CURRENT #8: Mon Apr 6 > 15:50:35 EDT 1998 > user1@bsdx.dyn.ml.org:/usr/src/sys/compile/BSDXKRNL i386 > > > Anyone know if the 'Right Thing' was committed to fix the xterm/netscape > slowness? I didnt notice it myself on this build, but it may have been > fixed behind my back? Yeah, Poul committed it over a couple days, with much testing, and several reports of success. > > > 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, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 8 19:48:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA05359 for freebsd-current-outgoing; Wed, 8 Apr 1998 19:48:00 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from taliesin.cs.ucla.edu (Taliesin.CS.UCLA.EDU [131.179.96.166]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id TAA05338 for ; Wed, 8 Apr 1998 19:47:59 -0700 (PDT) (envelope-from scottm@mordred.cs.ucla.edu) Received: (qmail 11316 invoked from network); 9 Apr 1998 02:47:06 -0000 Received: from mordred.cs.ucla.edu (131.179.48.34) by taliesin.cs.ucla.edu with SMTP; 9 Apr 1998 02:47:06 -0000 Received: (from scottm@localhost) by mordred.cs.ucla.edu (8.8.8/8.8.8) id TAA00277 for freebsd-current@freebsd.org; Wed, 8 Apr 1998 19:47:58 -0700 (PDT) (envelope-from scottm) Date: Wed, 8 Apr 1998 19:47:58 -0700 (PDT) From: Scott Michel Message-Id: <199804090247.TAA00277@mordred.cs.ucla.edu> To: freebsd-current@FreeBSD.ORG Subject: Speaking of which Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG When will the patch to ffs_softdeps.c get put in that gets rid of the "time" miscompile? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 8 20:05:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA07791 for freebsd-current-outgoing; Wed, 8 Apr 1998 20:05:44 -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 UAA07786 for ; Wed, 8 Apr 1998 20:05:43 -0700 (PDT) (envelope-from toasty@home.dragondata.com) Received: (from toasty@localhost) by home.dragondata.com (8.8.8/8.8.5) id WAA28898 for current@freebsd.org; Wed, 8 Apr 1998 22:05:34 -0500 (CDT) From: Kevin Day Message-Id: <199804090305.WAA28898@home.dragondata.com> Subject: wdtimeout() To: current@FreeBSD.ORG Date: Wed, 8 Apr 1998 22:05:27 -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 Since sometime in Feb. I've been getting: wd0: Last time I say: interrupt timeout. Probably a portable PC.: wd0: status 58 error 1 wd0: wdtimeout() DMA status 4 Going back to older kernels stops this from happening. Is this a known problem? Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 8 20:09:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA08763 for freebsd-current-outgoing; Wed, 8 Apr 1998 20:09:11 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA08754 for ; Wed, 8 Apr 1998 20:09:07 -0700 (PDT) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id UAA18129; Wed, 8 Apr 1998 20:08:59 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp04.primenet.com, id smtpd018092; Wed Apr 8 20:08:50 1998 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id UAA25433; Wed, 8 Apr 1998 20:08:48 -0700 (MST) From: Terry Lambert Message-Id: <199804090308.UAA25433@usr02.primenet.com> Subject: Re: /usr/include/pwd.h To: eivind@yes.no (Eivind Eklund) Date: Thu, 9 Apr 1998 03:08:47 +0000 (GMT) Cc: current@FreeBSD.ORG In-Reply-To: <19980407180754.16757@follo.net> from "Eivind Eklund" at Apr 7, 98 06:07:54 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 > Does anybody know why the uid and gid field here are int's? (Looks > like hystorical raisons, as they haven't been changed since 4.4Lite). > > Can I change them to uid_t/gid_t, or at least to 'unsigned int' so > they match with chown(2)? I think there are two reasons: Non-opacity. The type is not opaque because of NIS. History. The value of "nobody" on old SunOS systems was "-1". I don't know if the 65534/65535 values are short-converted and sign extended and compared, as in "if( uid < 0)", but there used to be a lot of code that did this. You would really need to look hard to find this. I'm also not sure if there aren't libraries that overload uid return values with "-1" to return an error. I would guess that the value *must* be signed in case there were. 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 Apr 8 23:02:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA25170 for freebsd-current-outgoing; Wed, 8 Apr 1998 23:02:30 -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 XAA25164 for ; Wed, 8 Apr 1998 23:02:16 -0700 (PDT) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.8.8/frmug-2.2/nospam) with UUCP id IAA07467 for freebsd-current@FreeBSD.ORG; Thu, 9 Apr 1998 08:02:12 +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 HAA01797; Thu, 9 Apr 1998 07:58:27 +0200 (CEST) (envelope-from roberto) Message-ID: <19980409075826.A1582@keltia.freenix.fr> Date: Thu, 9 Apr 1998 07:58:26 +0200 From: Ollivier Robert To: freebsd-current@FreeBSD.ORG Subject: Re: Speaking of which Mail-Followup-To: freebsd-current@FreeBSD.ORG References: <199804090247.TAA00277@mordred.cs.ucla.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.90.4i In-Reply-To: <199804090247.TAA00277@mordred.cs.ucla.edu>; from Scott Michel on Wed, Apr 08, 1998 at 07:47:58PM -0700 X-Operating-System: FreeBSD 3.0-CURRENT ctm#4180 AMD-K6 MMX @ 225 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Scott Michel: > When will the patch to ffs_softdeps.c get put in that gets rid of the > "time" miscompile? The main problem is that we do not maintain the code and it is not in the repository. Take it from the list archive. I can send it to the list again or I can send it to anyone who ask. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #0: Mon Mar 30 22:21:31 CEST 1998 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Apr 8 23:22:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA27888 for freebsd-current-outgoing; Wed, 8 Apr 1998 23:22:34 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com (rah.star-gate.com [209.133.7.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA27873 for ; Wed, 8 Apr 1998 23:22:31 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id XAA05205; Wed, 8 Apr 1998 23:22:21 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199804090622.XAA05205@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Ollivier Robert cc: freebsd-current@FreeBSD.ORG Subject: Re: Speaking of which In-reply-to: Your message of "Thu, 09 Apr 1998 07:58:26 +0200." <19980409075826.A1582@keltia.freenix.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 08 Apr 1998 23:22:21 -0700 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just send the code to Julian Elisher julian@whistle.com Have Fun, Amancio roberto@keltia.freenix.fr said: > The main problem is that we do not maintain the code and it is not in > the repository. Take it from the list archive. I can send it to the > list again or I can send it to anyone who ask. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 9 00:30:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA15137 for freebsd-current-outgoing; Thu, 9 Apr 1998 00:30:13 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA15128 for ; Thu, 9 Apr 1998 00:30:08 -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 JAA05122; Thu, 9 Apr 1998 09:28:58 +0200 (CEST) To: "Daniel O'Connor" cc: Greg Lehey , FreeBSD current users Subject: Re: Any big problems with -CURRENT at the moment? In-reply-to: Your message of "Thu, 09 Apr 1998 11:17:55 +0930." <199804090147.LAA29494@cain.gsoft.com.au> Date: Thu, 09 Apr 1998 09:28:58 +0200 Message-ID: <5120.892106938@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199804090147.LAA29494@cain.gsoft.com.au>, "Daniel O'Connor" writes: > >> I'm planning to upgrade my machine to the latest -CURRENT. In view of >> the problems we've been having lately, I'd like to ask if there are >> any to be expected at the moment. The mailing list seems relatively >> quiet. >Well, it seems OK, except that nanosleep() doesn't work for me, but no-one >else seems to get it.. Last I heard from you you were not running -current sources... >Also the fact that I can't run config on my kernel config is kind of annoying >, >but no-one else seems to be getting these problems, so it could just be me.. post a testcase program and lets test it... -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "Drink MONO-tonic, it goes down but it will NEVER come back up!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 9 00:39:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA16315 for freebsd-current-outgoing; Thu, 9 Apr 1998 00:39:25 -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 AAA16305 for ; Thu, 9 Apr 1998 00:39:21 -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 RAA01883; Thu, 9 Apr 1998 17:06:58 +0930 (CST) Message-Id: <199804090736.RAA01883@cain.gsoft.com.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Poul-Henning Kamp cc: Greg Lehey , FreeBSD current users Subject: Re: Any big problems with -CURRENT at the moment? In-reply-to: Your message of "Thu, 09 Apr 1998 09:28:58 +0200." <5120.892106938@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 09 Apr 1998 17:06:57 +0930 From: "Daniel O'Connor" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >Well, it seems OK, except that nanosleep() doesn't work for me, but no-one > >else seems to get it.. > Last I heard from you you were not running -current sources... Aaaaarrgh.. *smacks head* I just realised that since nanosleep doesn't work, cron doesn't, so my tree wasn't getting re-suped everyday.. Hehehe :) Sorry guys.. I'll get back to you and see what happens.. --------------------------------------------------------------------- |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 Apr 9 00:43:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA16991 for freebsd-current-outgoing; Thu, 9 Apr 1998 00:43:13 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from arh0300.urh.uiuc.edu (arh0300.urh.uiuc.edu [130.126.72.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA16986 for ; Thu, 9 Apr 1998 00:43:11 -0700 (PDT) (envelope-from dannyman@arh0300.urh.uiuc.edu) Received: (from dannyman@localhost) by arh0300.urh.uiuc.edu (8.8.8/8.8.5) id CAA16210; Thu, 9 Apr 1998 02:41:07 -0500 (CDT) Message-ID: <19980409024107.49254@urh.uiuc.edu> Date: Thu, 9 Apr 1998 02:41:07 -0500 From: dannyman To: "Daniel O'Connor" , Poul-Henning Kamp Cc: Greg Lehey , FreeBSD current users Subject: Re: Any big problems with -CURRENT at the moment? Mail-Followup-To: Daniel O'Connor , Poul-Henning Kamp , Greg Lehey , FreeBSD current users References: <5120.892106938@critter.freebsd.dk> <199804090736.RAA01883@cain.gsoft.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <199804090736.RAA01883@cain.gsoft.com.au>; from Daniel O'Connor on Thu, Apr 09, 1998 at 05:06:57PM +0930 X-Loop: djhoward@uiuc.edu X-URL: http://www.uiuc.edu/ph/www/djhoward/ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Apr 09, 1998 at 05:06:57PM +0930, Daniel O'Connor wrote: > > > >Well, it seems OK, except that nanosleep() doesn't work for me, but no-one > > >else seems to get it.. > > Last I heard from you you were not running -current sources... > Aaaaarrgh.. *smacks head* > I just realised that since nanosleep doesn't work, cron doesn't, so my tree > wasn't getting re-suped everyday.. Ohhhhh! I had a similar problem a few days ago. :D -- // dannyman yori aiokomete || Our Honored Symbol deserves \\/ http://www.dannyland.org/~dannyman/ || an Honorable Retirement (UIUC) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 9 00:54:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA18308 for freebsd-current-outgoing; Thu, 9 Apr 1998 00:54:17 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from btp1da.phy.uni-bayreuth.de (btp1da.phy.uni-bayreuth.de [132.180.20.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA18293 for ; Thu, 9 Apr 1998 00:54:07 -0700 (PDT) (envelope-from croot@btp1da.phy.uni-bayreuth.de) Received: (from root@localhost) by btp1da.phy.uni-bayreuth.de (8.8.8/8.7.3) id JAA05331; Thu, 9 Apr 1998 09:53:40 +0200 (MEST) Message-ID: X-Mailer: XFMail 1.2 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <19980409105459.22004@freebie.lemis.com> Date: Thu, 09 Apr 1998 09:53:40 +0200 (MEST) Organization: university of bayreuth From: Werner Griessl To: Greg Lehey Subject: RE: Any big problems with -CURRENT at the moment? Cc: FreeBSD current users Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 09-Apr-98 Greg Lehey wrote: > I'm planning to upgrade my machine to the latest -CURRENT. In view of > the problems we've been having lately, I'd like to ask if there are > any to be expected at the moment. The mailing list seems relatively > quiet. > > Greg > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message ---------------------------------- E-Mail: Werner Griessl Date: 09-Apr-98 Time: 09:48:42 This message was sent by XFMail ---------------------------------- Don't use mfs ! With a mfs mounted tmp on my test machine i had two problems: 1. mounting a ide-cdrom freezes the system. 2. dump/restore to a scsi DAT don't work. Without mfs tmp i have no problems in the moment. Werner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 9 01:11:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA21202 for freebsd-current-outgoing; Thu, 9 Apr 1998 01:11:00 -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 BAA21194 for ; Thu, 9 Apr 1998 01:10:53 -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 KAA14400 for ; Thu, 9 Apr 1998 10:13:51 +0200 (CEST) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Thu, 9 Apr 1998 10:13:51 +0200 (CEST) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: freebsd-current@FreeBSD.ORG Subject: FYI: Upgrading 2.2-STABLE -> 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 Hi! Just FYI: I upgraded one of my machines from 2.2-STABLE to 3.0-current by simple 'make world'. The whole process went flawlessly. :-)) The only things I did before rebooting to the new system was: ldconfig -m /usr/lib to start using the new libraries, and making/installing new kernel. I write this because of two reasons: one is to inform others it's a no-problem thing with current source trees, and the second is to thank all the developers who made this possible - especially those (I think) who worked on the build process. Keep up the good work! Andrzej Bialecki ---------------------+--------------------------------------------------------- abial@warman.org.pl | if(halt_per_mth > 0) { fetch("http://www.freebsd.org") } Research & Academic | "Be open-minded, but don't let your brains to fall out." Network in Poland | All of the above (and more) is just my personal opinion. ---------------------+--------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 9 01:20:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA22516 for freebsd-current-outgoing; Thu, 9 Apr 1998 01:20:01 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sos.freebsd.dk (sos.freebsd.dk [195.8.129.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA22471; Thu, 9 Apr 1998 01:19:58 -0700 (PDT) (envelope-from sos@sos.freebsd.dk) Received: (from sos@localhost) by sos.freebsd.dk (8.8.8/8.8.8) id KAA01254; Thu, 9 Apr 1998 10:19:48 +0200 (MEST) (envelope-from sos) Message-Id: <199804090819.KAA01254@sos.freebsd.dk> Subject: Re: Large IDE drive support added (I hope) In-Reply-To: from Atipa at "Apr 8, 98 02:17:37 pm" To: freebsd@atipa.com (Atipa) Date: Thu, 9 Apr 1998 10:19:48 +0200 (MEST) Cc: sos@FreeBSD.ORG, current@FreeBSD.ORG From: Søren Schmidt Reply-to: sos@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL30 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In reply to Atipa who wrote: > > Will this matter, or only when sharing the disk w/ dumb OSes (DOS/95/NT, > et al) that can't handle cylinders over 1024? Only when sharing, dedicated disk has never been affected by this geomerty mess... -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end .. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 9 02:25:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA29447 for freebsd-current-outgoing; Thu, 9 Apr 1998 02:25:49 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.webspan.net (root@mail.webspan.net [206.154.70.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA29441 for ; Thu, 9 Apr 1998 02:25:47 -0700 (PDT) (envelope-from opsys@mail.webspan.net) Received: from orion.webspan.net (orion.webspan.net [206.154.70.5]) by mail.webspan.net (WEBSPAN/970608) with SMTP id FAA19237 for ; Thu, 9 Apr 1998 05:22:03 -0400 (EDT) Date: Thu, 9 Apr 1998 05:25:39 -0400 (EDT) From: Open Systems Networking X-Sender: opsys@orion.webspan.net To: freebsd-current@FreeBSD.ORG Subject: Softupdates code with time fix 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 Someone asked yesterday if anyone had the softupdates code with the time patch. I have put up the patched version of ffs_softdep.c at http://open-systems.net/consultant.html As well as a link to julians page so that they READ and acknowledge the copyright as well. Chris -- "I am closed minded. It keeps the rain out." ===================================| Open Systems Networking And Consulting. FreeBSD 2.2.6 is available now! | Phone: 316-326-6800 -----------------------------------| 1402 N. Washington, Wellington, KS-67152 FreeBSD: The power to serve! | E-Mail: opsys@open-systems.net http://www.freebsd.org | Consulting-Network Engineering-Security ===================================| http://open-systems.net -----BEGIN PGP PUBLIC KEY BLOCK----- Version: 2.6.2 mQENAzPemUsAAAEH/06iF0BU8pMtdLJrxp/lLk3vg9QJCHajsd25gYtR8X1Px1Te gWU0C4EwMh4seDIgK9bzFmjjlZOEgS9zEgia28xDgeluQjuuMyUFJ58MzRlC2ONC foYIZsFyIqdjEOCBdfhH5bmgB5/+L5bjDK6lNdqD8OAhtC4Xnc1UxAKq3oUgVD/Z d5UJXU2xm+f08WwGZIUcbGcaonRC/6Z/5o8YpLVBpcFeLtKW5WwGhEMxl9WDZ3Kb NZH6bx15WiB2Q/gZQib3ZXhe1xEgRP+p6BnvF364I/To9kMduHpJKU97PH3dU7Mv CXk2NG3rtOgLTEwLyvtBPqLnbx35E0JnZc0k5YkABRO0JU9wZW4gU3lzdGVtcyA8 b3BzeXNAb3Blbi1zeXN0ZW1zLm5ldD4= =BBjp -----END PGP PUBLIC KEY BLOCK----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 9 02:33:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA01132 for freebsd-current-outgoing; Thu, 9 Apr 1998 02:33:45 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from serv.unibest.ru (serv.unibest.ru [194.87.33.9]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id CAA01127 for ; Thu, 9 Apr 1998 02:33:40 -0700 (PDT) (envelope-from osa@unibest.ru) Received: (qmail 16898 invoked from network); 9 Apr 1998 08:38:40 -0000 Received: from unknown (HELO hole.etrust.ru) (192.168.30.2) by serv.unibest.ru with SMTP; 9 Apr 1998 08:38:40 -0000 Date: Thu, 9 Apr 1998 13:35:24 +0400 (MSD) From: Ozz!!! X-Sender: osa@hole.etrust.ru To: freebsd-current@FreeBSD.ORG Subject: dmesg say : CPU: Pentium (0.00-MHz 586-class CPU ) 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 Hello! Some stranges in my FreeBSD-3.0-980311-SNAP.... After reboot dmesg say : ... CPU: Pentium (0.00-MHz 586-class CPU ) ^^^^ <- strange ???? What can i do ? Rgdz, oZZ, osa@unibest.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 9 02:39:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA02637 for freebsd-current-outgoing; Thu, 9 Apr 1998 02:39:45 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA02631 for ; Thu, 9 Apr 1998 02:39:41 -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 LAA05569; Thu, 9 Apr 1998 11:37:38 +0200 (CEST) To: Ozz!!! cc: freebsd-current@FreeBSD.ORG Subject: Re: dmesg say : CPU: Pentium (0.00-MHz 586-class CPU ) In-reply-to: Your message of "Thu, 09 Apr 1998 13:35:24 +0400." Date: Thu, 09 Apr 1998 11:37:37 +0200 Message-ID: <5567.892114657@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Ozz!!! writ es: >Hello! > >Some stranges in my FreeBSD-3.0-980311-SNAP.... >After reboot dmesg say : >... >CPU: Pentium (0.00-MHz 586-class CPU ) > ^^^^ <- strange ???? > >What can i do ? 1. Don't worry 2. Run more recent code. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "Drink MONO-tonic, it goes down but it will NEVER come back up!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 9 02:43:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA03240 for freebsd-current-outgoing; Thu, 9 Apr 1998 02:43:15 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.webspan.net (root@mail.webspan.net [206.154.70.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA03235 for ; Thu, 9 Apr 1998 02:43:13 -0700 (PDT) (envelope-from opsys@mail.webspan.net) Received: from orion.webspan.net (orion.webspan.net [206.154.70.5]) by mail.webspan.net (WEBSPAN/970608) with SMTP id FAA20622; Thu, 9 Apr 1998 05:39:21 -0400 (EDT) Date: Thu, 9 Apr 1998 05:42:58 -0400 (EDT) From: Open Systems Networking X-Sender: opsys@orion.webspan.net To: Ozz!!! cc: freebsd-current@FreeBSD.ORG Subject: Re: dmesg say : CPU: Pentium (0.00-MHz 586-class CPU ) 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, 9 Apr 1998, Ozz!!! wrote: > Hello! > > Some stranges in my FreeBSD-3.0-980311-SNAP.... > After reboot dmesg say : > ... > CPU: Pentium (0.00-MHz 586-class CPU ) > ^^^^ <- strange ???? 0 Mhz pentium? I'd say get a faster pentium upgrade :) I think it's just a snafu in that snap and doesnt really mean much. you can upgrade your snap and it should be fixed. Its just a typo. Chris -- "I am closed minded. It keeps the rain out." ===================================| Open Systems Networking And Consulting. FreeBSD 2.2.6 is available now! | Phone: 316-326-6800 -----------------------------------| 1402 N. Washington, Wellington, KS-67152 FreeBSD: The power to serve! | E-Mail: opsys@open-systems.net http://www.freebsd.org | Consulting-Network Engineering-Security ===================================| http://open-systems.net -----BEGIN PGP PUBLIC KEY BLOCK----- Version: 2.6.2 mQENAzPemUsAAAEH/06iF0BU8pMtdLJrxp/lLk3vg9QJCHajsd25gYtR8X1Px1Te gWU0C4EwMh4seDIgK9bzFmjjlZOEgS9zEgia28xDgeluQjuuMyUFJ58MzRlC2ONC foYIZsFyIqdjEOCBdfhH5bmgB5/+L5bjDK6lNdqD8OAhtC4Xnc1UxAKq3oUgVD/Z d5UJXU2xm+f08WwGZIUcbGcaonRC/6Z/5o8YpLVBpcFeLtKW5WwGhEMxl9WDZ3Kb NZH6bx15WiB2Q/gZQib3ZXhe1xEgRP+p6BnvF364I/To9kMduHpJKU97PH3dU7Mv CXk2NG3rtOgLTEwLyvtBPqLnbx35E0JnZc0k5YkABRO0JU9wZW4gU3lzdGVtcyA8 b3BzeXNAb3Blbi1zeXN0ZW1zLm5ldD4= =BBjp -----END PGP PUBLIC KEY BLOCK----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 9 03:40:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA07556 for freebsd-current-outgoing; Thu, 9 Apr 1998 03:40:12 -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 DAA07543 for ; Thu, 9 Apr 1998 03:40:11 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id DAA21164; Thu, 9 Apr 1998 03:30:49 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd021162; Thu Apr 9 10:30:45 1998 Date: Thu, 9 Apr 1998 03:25:44 -0700 (PDT) From: Julian Elischer To: Scott Michel cc: freebsd-current@FreeBSD.ORG Subject: Re: Speaking of which In-Reply-To: <199804090247.TAA00277@mordred.cs.ucla.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 yes tomorrow On Wed, 8 Apr 1998, Scott Michel wrote: > When will the patch to ffs_softdeps.c get put in that gets rid of the > "time" miscompile? > > 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 Apr 9 03:53:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA09018 for freebsd-current-outgoing; Thu, 9 Apr 1998 03:53: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 DAA09013 for ; Thu, 9 Apr 1998 03:53:52 -0700 (PDT) (envelope-from julian@FreeBSD.org) From: Julian Elischer Received: (from julian@localhost) by freefall.freebsd.org (8.8.8/8.8.5) id DAA06401 for current; Thu, 9 Apr 1998 03:51:09 -0700 (PDT) Date: Thu, 9 Apr 1998 03:51:09 -0700 (PDT) Message-Id: <199804091051.DAA06401@freefall.freebsd.org> To: current@FreeBSD.ORG Subject: ffs_softdep.c updated Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG www.freebsd.org/~julian should point to a new version of ffs_softdep.c that should compile cleanly against -current again. julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 9 08:12:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA08661 for freebsd-current-outgoing; Thu, 9 Apr 1998 08:12:05 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.visint.co.uk (wakko.visint.co.uk [194.207.134.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA08656 for ; Thu, 9 Apr 1998 08:12:01 -0700 (PDT) (envelope-from steve@visint.co.uk) Received: from dylan (dylan.visint.co.uk [194.207.134.180]) by mail.visint.co.uk (8.8.8/8.8.5) with SMTP id QAA07991 for ; Thu, 9 Apr 1998 16:11:59 +0100 (BST) Date: Thu, 9 Apr 1998 16:11:54 +0100 (BST) From: Stephen Roome X-Sender: steve@dylan To: freebsd-current@FreeBSD.ORG Subject: ps segfaults since I overclocked. and worries. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just overclocked my board up to a 75Mhz bus speed and a 189ish Mhz processor, it's running fine apart from ps mysteriously segfaults all the time now. I'm using pci ide as well, and noticed that on line 360 of /sys/pci/ide_pci.c there's something about overclocking causing some sort of problem.. anyone know if this is going to hamper me as well ? Thanks in advance, Steve Steve Roome - Vision Interactive Ltd. Tel:+44(0)117 9730597 Home:+44(0)976 241342 WWW: http://dylan.visint.co.uk/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 9 08:36:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA12473 for freebsd-current-outgoing; Thu, 9 Apr 1998 08:36:06 -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 IAA12453 for ; Thu, 9 Apr 1998 08:36:02 -0700 (PDT) (envelope-from dhw@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id IAA28040 for ; Thu, 9 Apr 1998 08:35:33 -0700 (PDT) Received: from pau-amma.whistle.com(207.76.205.64) by whistle.com via smap (V1.3) id sma028038; Thu Apr 9 08:35:14 1998 Received: (from dhw@localhost) by pau-amma.whistle.com (8.8.7/8.8.7) id IAA25798 for current@freebsd.org; Thu, 9 Apr 1998 08:35:13 -0700 (PDT) (envelope-from dhw) Date: Thu, 9 Apr 1998 08:35:13 -0700 (PDT) From: David Wolfskill Message-Id: <199804091535.IAA25798@pau-amma.whistle.com> To: current@FreeBSD.ORG Subject: Re: /usr/include/pwd.h Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >From: Terry Lambert >Date: Thu, 9 Apr 1998 03:08:47 +0000 (GMT) >> Does anybody know why the uid and gid field here are int's? (Looks >> like hystorical raisons, as they haven't been changed since 4.4Lite). >History. The value of "nobody" on old SunOS systems was "-1". Quibble: it was -2 (65534). david -- David Wolfskill dhw@whistle.com (650) 577-7158 pager: (650) 401-0168 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 9 09:43:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA06861 for freebsd-current-outgoing; Thu, 9 Apr 1998 09:43:41 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ix.netcom.com (sil-wa4-15.ix.netcom.com [207.93.136.79]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA06846 for ; Thu, 9 Apr 1998 09:43:38 -0700 (PDT) (envelope-from tomdean@ix.netcom.com) Received: (from tomdean@localhost) by ix.netcom.com (8.8.8/8.8.8) id JAA00637; Thu, 9 Apr 1998 09:43:36 -0700 (PDT) (envelope-from tomdean) Date: Thu, 9 Apr 1998 09:43:36 -0700 (PDT) Message-Id: <199804091643.JAA00637@ix.netcom.com> From: Thomas Dean To: FreeBSD-current@FreeBSD.ORG In-reply-to: <19980409024107.49254@urh.uiuc.edu> (message from dannyman on Thu, 9 Apr 1998 02:41:07 -0500) Subject: Re: Any big problems with -CURRENT at the moment? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I cvsup'd lastnight ~2200 PDT. make -j4 world worked. rebuilt and rebooted the kernel. Everything seems OK. Things seem to work better, now, vs about three months ago. Thanks, keep up the good work. tomdean To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 9 10:05:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA08914 for freebsd-current-outgoing; Thu, 9 Apr 1998 10:05:12 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from relay.ucb.crimea.ua (relay.ucb.crimea.ua [194.93.177.113]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA08796 for ; Thu, 9 Apr 1998 10:03:56 -0700 (PDT) (envelope-from ru@ucb.crimea.ua) Received: (from ru@localhost) by relay.ucb.crimea.ua (8.8.8/8.8.8) id UAA07555; Thu, 9 Apr 1998 20:01:27 +0300 (EEST) (envelope-from ru) Message-ID: <19980409200127.06861@ucb.crimea.ua> Date: Thu, 9 Apr 1998 20:01:27 +0300 From: Ruslan Ermilov To: current@FreeBSD.ORG Subject: Committers, wake up!!! Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! A week ago I've sent PR conf/6226 of class change-request with patch attached. Would you be so kind to follow-up on this one? Thank you, -- Ruslan Ermilov System Administrator ru@ucb.crimea.ua United Commercial Bank +380-652-247647 Simferopol, Crimea 2426679 ICQ Network, UIN To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 9 10:25:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA11614 for freebsd-current-outgoing; Thu, 9 Apr 1998 10:25:49 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from slip-3 (mail@slip-3.slip.net [207.171.193.17]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA11608 for ; Thu, 9 Apr 1998 10:25:46 -0700 (PDT) (envelope-from thomma@slip.net) Received: from thomma by slip-3 with local (Exim 1.62 #4) id 0yNL4b-0002IT-00; Thu, 9 Apr 1998 10:25:13 -0700 Subject: FAILSAFE and NCR To: freebsd-current@FreeBSD.ORG Date: Thu, 9 Apr 1998 10:25:08 -0700 (PDT) X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: From: Tamiji Homma Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I posted about SCSI disk performance difference(three times) between 19980222-SNAP and 19971006-SNAP. It turned out to be the FAILSAFE option made the difference. It slows SCSI disk access down significantly. Thanks to Geoff Buckingham and John Dyson, I could dig into a little deeper. I noticed that MAX_START is now hardcoded to 32, which used to be (MAX_TARGET + 7 * SCSI_NCR_DFLT_TAGS) in sys/pci/ncr.c. Is this going to be this way from now on? Or is it anything to do with CAM? So that it will be resolved differently? It is a little annoying everytime I have to patch sys/pci/ncr.c. Thanks Tammy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 9 12:25:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA25030 for freebsd-current-outgoing; Thu, 9 Apr 1998 12:25:23 -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 MAA25024 for ; Thu, 9 Apr 1998 12:25:22 -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 MAA00461; Thu, 9 Apr 1998 12:17:11 -0700 (PDT) Message-Id: <199804091917.MAA00461@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Ruslan Ermilov cc: current@FreeBSD.ORG Subject: Re: Committers, wake up!!! In-reply-to: Your message of "Thu, 09 Apr 1998 20:01:27 +0300." <19980409200127.06861@ucb.crimea.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 09 Apr 1998 12:17:10 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi! > > A week ago I've sent PR conf/6226 of class > change-request with patch attached. > > Would you be so kind to follow-up on this one? You should probably have pointed out that this is relating to the sendmail antispam rules. It needs attention from the appropriate quarters. -- \\ 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 Apr 9 15:21:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA23448 for freebsd-current-outgoing; Thu, 9 Apr 1998 15:21:23 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from fang.cs.sunyit.edu (root@fang.cs.sunyit.edu [192.52.220.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA23426 for ; Thu, 9 Apr 1998 15:21:20 -0700 (PDT) (envelope-from perlsta@cs.sunyit.edu) Received: from win95.local.sunyit.edu (A-T34.rh.sunyit.edu [150.156.210.241]) by fang.cs.sunyit.edu (8.8.5/8.7.3) with SMTP id RAA13778; Thu, 9 Apr 1998 17:22:49 GMT Message-ID: <02f001bd6404$e9e22280$0600a8c0@win95.local.sunyit.edu> From: "Alfred Perlstein" To: "Stephen Roome" , Subject: Re: ps segfaults since I overclocked. and worries. Date: Thu, 9 Apr 1998 18:14:49 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG overclocking is a problem with most all machines, don't do it. <-- period -Alfred -----Original Message----- From: Stephen Roome To: freebsd-current@FreeBSD.ORG Date: Thursday, April 09, 1998 6:18 AM Subject: ps segfaults since I overclocked. and worries. > >Just overclocked my board up to a 75Mhz bus speed and a 189ish Mhz >processor, it's running fine apart from ps mysteriously segfaults all the >time now. > >I'm using pci ide as well, and noticed that on line 360 of >/sys/pci/ide_pci.c there's something about overclocking causing some sort >of problem.. anyone know if this is going to hamper me as well ? > >Thanks in advance, > > Steve > >Steve Roome - Vision Interactive Ltd. >Tel:+44(0)117 9730597 Home:+44(0)976 241342 >WWW: http://dylan.visint.co.uk/ > > >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 Apr 9 15:40:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA27109 for freebsd-current-outgoing; Thu, 9 Apr 1998 15:40:56 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.mishkei.org.il (host3-64.mishkei.org.il [62.0.64.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA27100 for ; Thu, 9 Apr 1998 15:40:52 -0700 (PDT) (envelope-from lickyou@ein-hashofet.co.il) Received: from box.from.hell (host42-68.mishkei.org.il [62.0.68.42]) by mail.mishkei.org.il (8.8.5/8.8.5) with SMTP id BAA13167; Fri, 10 Apr 1998 01:40:26 +0300 Date: Fri, 10 Apr 1998 01:41:03 +0000 (GMT) From: Gilad Rom X-Sender: lickyou@box.from.hell To: Alfred Perlstein cc: Stephen Roome , freebsd-current@FreeBSD.ORG Subject: Re: ps segfaults since I overclocked. and worries. In-Reply-To: <02f001bd6404$e9e22280$0600a8c0@win95.local.sunyit.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 Alfred, I dont agree. Ive been overclocking my P200 to 233 for quite sometime, and it hasnt caused any errors until now. But ofcourse, it all depends on the CPU quality, so I cant really tell. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 9 15:42:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA27225 for freebsd-current-outgoing; Thu, 9 Apr 1998 15:42:02 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail1.sirius.com (mail1.sirius.com [205.134.253.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA27189 for ; Thu, 9 Apr 1998 15:41:52 -0700 (PDT) (envelope-from parag@mail.codegen.com) Received: from [192.168.100.101] (ppp-asok08--166.sirius.net [205.134.245.166]) by mail1.sirius.com (8.8.7/Sirius-8.8.7-97.08.12) with SMTP id PAA17868; Thu, 9 Apr 1998 15:41:26 -0700 (PDT) Message-Id: <199804092241.PAA17868@mail1.sirius.com> Subject: Re: Questions for PCI-IDE driver owner Date: Thu, 9 Apr 1998 15:42:54 -0700 x-sender: parag@mail.codegen.com x-mailer: Claris Emailer 2.0v3, January 22, 1998 From: Parag Patel To: cc: "Thomas J. Merritt" Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, since I haven't gotten any responses, I went ahead and changed some IDE files the way I thought they should have been done. Anyone feel like trying them out to see if I broke anything, and then hopefully merging them into the main sources? Thanks in advance. The three files changed are pci/ide_pci.c, i386/isa/wdreg.h, and i386/isa/wd.c. The changes are small but necessary for the CMD646 controller to work in DMA mode. The diffs are relative to the current release, ie the latest checked-in code. If there's a preferred format for the diffs, please let me know - I just ran "cvs diff -c ". -- Parag Patel Index: ide_pci.c =================================================================== RCS file: /src/freebsd/src/sys/pci/ide_pci.c,v retrieving revision 1.9 diff -c -r1.9 ide_pci.c *** ide_pci.c 1998/02/06 12:14:06 1.9 --- ide_pci.c 1998/04/09 22:19:37 *************** *** 61,66 **** --- 61,67 ---- #endif #define PROMISE_ULTRA33 0x4d33105a + #define CMD_PCI646U2_ID 0x06461095 struct ide_pci_cookie; /* structs vendor_fns, ide_pci_cookie are recursive */ *************** *** 150,156 **** static void ide_pci_attach(pcici_t tag, int unit); ! static void *ide_pci_candma(int, int); static int ide_pci_dmainit(void *, struct wdparams *, int (*)(int, void *), --- 151,157 ---- static void ide_pci_attach(pcici_t tag, int unit); ! static void *ide_pci_candma(int, int, int); static int ide_pci_dmainit(void *, struct wdparams *, int (*)(int, void *), *************** *** 537,542 **** --- 538,632 ---- promise_status }; + static void + cmd646_status(struct ide_pci_cookie *cookie) + { + int iobase_bm = cookie->iobase_bm; + pcici_t tag = cookie->tag; + int i; + + printf("cmd646_status: %d:%d register dump:\n", + cookie->ctlr, cookie->unit); + + for (i = 0; i < 0x80; i += 16) + { + printf(" %2x:%8x %8x %8x %8x\n", + i, pci_conf_read(tag, i), pci_conf_read(tag, i + 4), + pci_conf_read(tag, i + 8), pci_conf_read(tag, i + 12)); + } + } + + static int + cmd646_dmainit(struct ide_pci_cookie *cookie, + struct wdparams *wp, + int(*wdcmd)(int, void *), + void *wdinfo) + { + int iobase_bm = cookie->iobase_bm; + int ctlr = cookie->ctlr; + int unit = cookie->unit; + int mrdmode, bmista, udidetcr, r; + #define BMRDMODE 1 + #define BUDIDETCR 3 + + if (udma_mode(wp) >= 2) + { + mrdmode = inb(iobase_bm + BMRDMODE); + udidetcr = inb(iobase_bm + BUDIDETCR); + bmista = inb(iobase_bm + BMISTA_PORT); + + outb(iobase_bm + BMRDMODE, mrdmode | 0x08C); + outb(iobase_bm + BUDIDETCR, udidetcr | (unit ? 0x2 : 0x1)); + outb(iobase_bm + BMISTA_PORT, + bmista | (unit ? BMISTA_DMA1CAP : BMISTA_DMA0CAP) | + BMISTA_DMA_ERROR); + + if (bootverbose) + cmd646_status(cookie); + + /* set the drive to Ultra-DMA mode */ + r = wdcmd(WDDMA_UDMA2, wdinfo); + + if (!r) + { + printf("cmd646_dmainit: setting DMA mode failed\n"); + return 0; + } + + return 1; + } + + if (pio_mode(wp) >= 4 && mwdma_mode(wp) >= 2) + { + bmista = inb(iobase_bm + BMISTA_PORT); + outb(iobase_bm + BMISTA_PORT, + bmista | (unit ? BMISTA_DMA1CAP : BMISTA_DMA0CAP) | + BMISTA_DMA_ERROR); + + if (bootverbose) + cmd646_status(cookie); + + /* set the drive to DMA mode */ + r = wdcmd(WDDMA_MDMA2, wdinfo); + + if (!r) + { + printf("cmd646_dmainit: setting DMA mode failed\n"); + return 0; + } + + return 1; + } + + return 0; + } + + static struct vendor_fns vs_cmd646 = + { + cmd646_dmainit, + cmd646_status + }; + /* Intel PIIX, PIIX3, and PIIX4 IDE controller subfunctions */ static void intel_piix_dump_drive(char *ctlr, *************** *** 916,921 **** --- 1006,1013 ---- return ("Promise Ultra/33 IDE controller"); if (type == 0x05711106) return ("VIA 82C586x (Apollo) Bus-master IDE controller"); + if (type == CMD_PCI646U2_ID) + return "CMD PCI646U2 Ultra/33 IDE controller"; if (data & 0x8000) return ("PCI IDE controller (busmaster capable)"); #ifndef CMD640 *************** *** 947,953 **** /* set up vendor-specific stuff */ type = pci_conf_read(tag, PCI_ID_REG); ! if (type != PROMISE_ULTRA33) { /* is it busmaster capable? bail if not */ class = pci_conf_read(tag, PCI_CLASS_REG); if (!(class & 0x8000)) { --- 1039,1045 ---- /* set up vendor-specific stuff */ type = pci_conf_read(tag, PCI_ID_REG); ! if (type != PROMISE_ULTRA33 && type != CMD_PCI646U2_ID) { /* is it busmaster capable? bail if not */ class = pci_conf_read(tag, PCI_CLASS_REG); if (!(class & 0x8000)) { *************** *** 979,991 **** vp = &vs_promise; break; default: /* everybody else */ vp = &vs_generic; break; } ! if (type != PROMISE_ULTRA33) { if ((class & 0x100) == 0) { iobase_wd_1 = IO_WD1; altiobase_wd_1 = iobase_wd_1 + wd_altsts; --- 1071,1088 ---- vp = &vs_promise; break; + case CMD_PCI646U2_ID: + /* CMD PCI646U2-based controllers */ + vp = &vs_cmd646; + break; + default: /* everybody else */ vp = &vs_generic; break; } ! if (type != PROMISE_ULTRA33 && type != CMD_PCI646U2_ID) { if ((class & 0x100) == 0) { iobase_wd_1 = IO_WD1; altiobase_wd_1 = iobase_wd_1 + wd_altsts; *************** *** 1187,1199 **** * Return a cookie if we can do DMA on the specified (iobase_wd, unit). */ static void * ! ide_pci_candma(int iobase_wd, int unit) { struct ide_pci_cookie *cp; cp = softc.cookies.lh_first; while(cp) { ! if (cp->ctlr == unit && ((iobase_wd == 0) || (cp->iobase_wd == iobase_wd))) break; cp = cp->le.le_next; --- 1284,1296 ---- * Return a cookie if we can do DMA on the specified (iobase_wd, unit). */ static void * ! ide_pci_candma(int iobase_wd, int ctlr, int unit) { struct ide_pci_cookie *cp; cp = softc.cookies.lh_first; while(cp) { ! if (cp->ctlr == ctlr && cp->unit == unit && ((iobase_wd == 0) || (cp->iobase_wd == iobase_wd))) break; cp = cp->le.le_next; *************** *** 1214,1225 **** void *wdinfo) { struct ide_pci_cookie *cp = cookie; /* * If the controller status indicates that DMA is configured already, * we flounce happily away */ ! if (inb(cp->iobase_bm + BMISTA_PORT) & ! ((cp->unit == 0) ? BMISTA_DMA0CAP : BMISTA_DMA1CAP)) return 1; /* We take a stab at it with device-dependent code */ --- 1311,1325 ---- void *wdinfo) { struct ide_pci_cookie *cp = cookie; + /* * If the controller status indicates that DMA is configured already, * we flounce happily away + * [CMD 646 part should always be initialized] */ ! if (cp->type != CMD_PCI646U2_ID && ! inb(cp->iobase_bm + BMISTA_PORT) & ! ((cp->unit == 0) ? BMISTA_DMA0CAP : BMISTA_DMA1CAP)) return 1; /* We take a stab at it with device-dependent code */ Index: wdreg.h =================================================================== RCS file: /src/freebsd/src/sys/i386/isa/wdreg.h,v retrieving revision 1.21 diff -c -r1.21 wdreg.h *** wdreg.h 1998/01/14 08:08:42 1.21 --- wdreg.h 1998/04/09 22:18:29 *************** *** 261,267 **** */ struct wddma { void *(*wdd_candma) /* returns a cookie if PCI */ ! __P((int ctlr, int drive)); int (*wdd_dmaverify) /* verify that request is DMA-able */ __P((void *cookie, char *vaddr, u_long len, int direction)); int (*wdd_dmaprep) /* prepare DMA hardware */ --- 261,267 ---- */ struct wddma { void *(*wdd_candma) /* returns a cookie if PCI */ ! __P((int iobase, int ctlr, int drive)); int (*wdd_dmaverify) /* verify that request is DMA-able */ __P((void *cookie, char *vaddr, u_long len, int direction)); int (*wdd_dmaprep) /* prepare DMA hardware */ Index: wd.c =================================================================== RCS file: /src/freebsd/src/sys/i386/isa/wd.c,v retrieving revision 1.152 diff -c -r1.152 wd.c *** wd.c 1998/04/02 02:10:47 1.152 --- wd.c 1998/04/09 22:18:52 *************** *** 297,303 **** du->dk_interface = interface; #if !defined(DISABLE_PCI_IDE) && (NPCI > 0) if (wddma[interface].wdd_candma) { ! du->dk_dmacookie = wddma[interface].wdd_candma(dvp->id_iobase, du->dk_ctrlr); du->dk_port = dvp->id_iobase; du->dk_altport = wddma[interface].wdd_altiobase(du->dk_dmacookie); } else { --- 297,304 ---- du->dk_interface = interface; #if !defined(DISABLE_PCI_IDE) && (NPCI > 0) if (wddma[interface].wdd_candma) { ! du->dk_dmacookie = wddma[interface].wdd_candma(dvp->id_iobase, ! du->dk_ctrlr, unit); du->dk_port = dvp->id_iobase; du->dk_altport = wddma[interface].wdd_altiobase(du->dk_dmacookie); } else { *************** *** 1070,1076 **** du = wddrives[dkunit(bp->b_dev)]; /* finish off DMA */ ! if (du->dk_flags & (DKFL_DMA|DKFL_USEDMA)) { /* XXX SMP boxes sometimes generate an early intr. Why? */ if ((wddma[du->dk_interface].wdd_dmastatus(du->dk_dmacookie) & WDDS_INTERRUPT) == 0) --- 1071,1077 ---- du = wddrives[dkunit(bp->b_dev)]; /* finish off DMA */ ! if (du->dk_flags & DKFL_DMA) { /* XXX SMP boxes sometimes generate an early intr. Why? */ if ((wddma[du->dk_interface].wdd_dmastatus(du->dk_dmacookie) & WDDS_INTERRUPT) == 0) *************** *** 1861,1867 **** * check drive's DMA capability */ if (wddma[du->dk_interface].wdd_candma) { ! du->dk_dmacookie = wddma[du->dk_interface].wdd_candma(du->dk_port, du->dk_ctrlr); /* does user want this? */ if ((du->cfg_flags & WDOPT_DMA) && /* have we got a DMA controller? */ --- 1862,1869 ---- * check drive's DMA capability */ if (wddma[du->dk_interface].wdd_candma) { ! du->dk_dmacookie = wddma[du->dk_interface].wdd_candma(du->dk_port, ! du->dk_ctrlr, du->dk_unit); /* does user want this? */ if ((du->cfg_flags & WDOPT_DMA) && /* have we got a DMA controller? */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 9 16:24:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA01559 for freebsd-current-outgoing; Thu, 9 Apr 1998 16:24:43 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from obiwan.TerraNova.net (root@obiwan.TerraNova.net [209.4.59.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA01535 for ; Thu, 9 Apr 1998 16:24:30 -0700 (PDT) (envelope-from bofh@terranova.net) Received: from guenhwyvar (tog@guenhwyvar.TerraNova.net [209.4.59.4]) by obiwan.TerraNova.net (8.8.8/TNN/3.1) with SMTP id TAA03332; Thu, 9 Apr 1998 19:24:15 -0400 (EDT) Message-ID: <352D58A4.115B@terranova.net> Date: Thu, 09 Apr 1998 19:24:20 -0400 From: Travis Mikalson Organization: TerraNovaNet X-Mailer: Mozilla 3.04 (Win95; I) MIME-Version: 1.0 To: Gilad Rom CC: freebsd-current@FreeBSD.ORG Subject: Re: ps segfaults since I overclocked. and worries. References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Gilad Rom wrote: > > Alfred, I dont agree. Ive been overclocking my P200 to 233 for quite > sometime, and it hasnt caused any errors until now. > But ofcourse, it all depends on the CPU quality, so I cant really tell. Overclocking either works perfectly or you should put it back. If you clock it back to the original setting that it's supposed to be at and ps stops segfaulting then leave it :) "Doctor, my foot hurts when I kick my computer for segfaulting" "Well then don't kick your computer" -- TerraNovaNet Internet Services - Key Largo, FL Voice: (305)453-4011 Fax: (305)451-5991 http://www.terranova.net/ ---------------------------------------------- Duct tape is like the force. It has a light side, and a dark side, and it holds the universe together ... -- Carl Zwanzig To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 9 18:30:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA19941 for freebsd-current-outgoing; Thu, 9 Apr 1998 18:30:26 -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 SAA19908; Thu, 9 Apr 1998 18:30:18 -0700 (PDT) (envelope-from grog@lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.8.7/8.8.5) with ESMTP id LAA16647; Fri, 10 Apr 1998 11:00:14 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.8.8/8.8.7) id LAA00633; Fri, 10 Apr 1998 11:00:13 +0930 (CST) (envelope-from grog) Message-ID: <19980410110013.59919@freebie.lemis.com> Date: Fri, 10 Apr 1998 11:00:13 +0930 From: Greg Lehey To: mcdougall@ameritech.net, current@FreeBSD.ORG Cc: FreeBSD current users Subject: Re: Any big problems with -CURRENT at the moment? References: <19980409105459.22004@freebie.lemis.com> <352C2AB1.4E7BE56C@ameritech.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <352C2AB1.4E7BE56C@ameritech.net>; from Adam McDougall on Wed, Apr 08, 1998 at 09:56:01PM -0400 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 8 April 1998 at 21:56:01 -0400, Adam McDougall wrote: > Greg Lehey wrote: > >> I'm planning to upgrade my machine to the latest -CURRENT. In view of >> the problems we've been having lately, I'd like to ask if there are >> any to be expected at the moment. The mailing list seems relatively >> quiet. >> >> Greg >> >> To Unsubscribe: send mail to majordomo@FreeBSD.org >> with "unsubscribe freebsd-current" in the body of the message > > Nothing out of the ordinary here,... > > FreeBSD bsdx.dyn.ml.org 3.0-CURRENT FreeBSD 3.0-CURRENT #8: Mon Apr 6 > 15:50:35 EDT 1998 > user1@bsdx.dyn.ml.org:/usr/src/sys/compile/BSDXKRNL i386 > > Anyone know if the 'Right Thing' was committed to fix the xterm/netscape > slowness? I didnt notice it myself on this build, but it may have been > fixed behind my back? I To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 9 18:31:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA20517 for freebsd-current-outgoing; Thu, 9 Apr 1998 18:31:41 -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 SAA20509; Thu, 9 Apr 1998 18:31:36 -0700 (PDT) (envelope-from grog@lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.8.7/8.8.5) with ESMTP id LAA16651; Fri, 10 Apr 1998 11:01:33 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.8.8/8.8.7) id LAA00651; Fri, 10 Apr 1998 11:01:33 +0930 (CST) (envelope-from grog) Message-ID: <19980410110133.39635@freebie.lemis.com> Date: Fri, 10 Apr 1998 11:01:33 +0930 From: Greg Lehey To: mcdougall@ameritech.net, current@FreeBSD.ORG Cc: FreeBSD current users Subject: Re: Any big problems with -CURRENT at the moment? References: <19980409105459.22004@freebie.lemis.com> <352C2AB1.4E7BE56C@ameritech.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <352C2AB1.4E7BE56C@ameritech.net>; from Adam McDougall on Wed, Apr 08, 1998 at 09:56:01PM -0400 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 8 April 1998 at 21:56:01 -0400, Adam McDougall wrote: > Anyone know if the 'Right Thing' was committed to fix the xterm/netscape > slowness? I didnt notice it myself on this build, but it may have been > fixed behind my back? (Oops--finger trouble with the previous message. Sorry.) I built a new world. It looks like it's fine now, anyway. I don't see any slowness. Greg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 9 18:54:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA25599 for freebsd-current-outgoing; Thu, 9 Apr 1998 18:54:30 -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 SAA25594; Thu, 9 Apr 1998 18:54:21 -0700 (PDT) (envelope-from grog@lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.8.7/8.8.5) with ESMTP id LAA16680; Fri, 10 Apr 1998 11:24:09 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.8.8/8.8.7) id LAA00741; Fri, 10 Apr 1998 11:24:08 +0930 (CST) (envelope-from grog) Message-ID: <19980410112408.01873@freebie.lemis.com> Date: Fri, 10 Apr 1998 11:24:08 +0930 From: Greg Lehey To: ip@mcc.ac.uk, questions@FreeBSD.ORG, scsi@FreeBSD.ORG, FreeBSD current users Subject: Re: compression on Exabyte 8700LT? Reply-To: FreeBSD current users References: <199804091527.QAA09483@albatross.mcc.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <199804091527.QAA09483@albatross.mcc.ac.uk>; from Ian Pallfreeman on Thu, Apr 09, 1998 at 04:27:31PM +0100 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 Thu, 9 April 1998 at 16:27:31 +0100, Ian Pallfreeman wrote: > I've recently acquired another Exabyte drive, an 8700LT. This drive claims to > be able to write 10Gb to a 112m tape in compressed mode, but I'm getting just > the 5Gb I'd expect uncompressed. > > ... > > FreeBSD 3.0-CURRENT #9: Thu Apr 9 16:06:09 BST 1998 > ip@lurch:/usr/src/sys/compile/LURCH Please don't discuss CURRENT topics on -questions. Send them to -current instead (to which I hope you are subscribed). I'm copying -questions on this reply only to show where I've sent the thread. I think there's a general problem with tape compression under -CURRENT. A few months back, I used to be able to back up a complete 8 GB on my DDS-2 drives, but now I've done some testing and found it gives up somewhere round 3.4 GB. I don't understand that, since the native tape capacity is 4 GB. -CURRENT people: I'm using the old SCSI driver. The tape is set to start up in compressed mode, and the DC LED is illuminated all the time. This looks to me as if something in the driver is explicitly disabling compression, or just possibly that the driver is guessing the size of the tape and stopping (with EIO) when it reaches this point. The other point is that it's still returning EIO. I know there's been some discussion about this before, and ISTR that it was inconclusive ("that's the way our grandfathers did it"). While looking at the problem, I came across a program I wrote in my BSD/OS days back in 1992, and I note that even then BSD/OS returned ENOSPC when it got to the end of the tape. This makes a whole lot more sense, and it obviously seems to have withstood the test of time. How about it? Would I get an improvement on either of these points if I installed CAM? I know that CAM can't handle compression switching yet, but can it do compression if it's enabled on the drive? Greg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 9 20:42:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA18124 for freebsd-current-outgoing; Thu, 9 Apr 1998 20:42:44 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from enigami.com (enigami.com [208.140.182.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA18114 for ; Thu, 9 Apr 1998 20:42:40 -0700 (PDT) (envelope-from ckempf@enigami.com) Received: from [208.140.182.45] (symphony.enigami.com [208.140.182.45]) by enigami.com (8.8.7/8.8.7) with ESMTP id XAA00252 for ; Thu, 9 Apr 1998 23:42:08 -0400 (EDT) X-Sender: ckempfm@enigami.com Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Thu, 9 Apr 1998 23:13:55 -0400 To: freebsd-current@FreeBSD.ORG From: Cory Kempf Subject: Sound on DK440LX? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As per Greg's request, this is being re-sent to -current. Sorry if you are seeing this twice. Does anyone have sound working on a DK440LX motherboard? If so, how did you get it to work? I have tried both the SB (sound blaster) and the CSS (crystal) devices, but neither seems to work. At least they do not seem to be found on startup. FWIW, I am running a slightly old current. Thanks, +C -- Thinking of purchasing RAM from the Chip Merchant? Please read this first: Cory Kempf Macintosh / Unix Consulting & Software Development ckempf@enigami.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 9 20:47:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA19798 for freebsd-current-outgoing; Thu, 9 Apr 1998 20:47:28 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com (rah.star-gate.com [209.133.7.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA19737; Thu, 9 Apr 1998 20:47:23 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id UAA09169; Thu, 9 Apr 1998 20:47:00 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199804100347.UAA09169@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Cory Kempf cc: multimedia@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: Sound on DK440LX? In-reply-to: Your message of "Thu, 09 Apr 1998 23:13:55 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 09 Apr 1998 20:47:00 -0700 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greg should have forwarded you to the multimedia mailing list :( Amancio > As per Greg's request, this is being re-sent to -current. Sorry if you are > seeing this twice. > > > > Does anyone have sound working on a DK440LX motherboard? > > If so, how did you get it to work? > > I have tried both the SB (sound blaster) and the CSS (crystal) devices, but > neither seems to work. At least they do not seem to be found on startup. > > FWIW, I am running a slightly old current. > > Thanks, > > +C > > > -- > Thinking of purchasing RAM from the Chip Merchant? Please read this first: > > > Cory Kempf Macintosh / Unix Consulting & Software Development > ckempf@enigami.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 Thu Apr 9 21:14:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA26027 for freebsd-current-outgoing; Thu, 9 Apr 1998 21:14:31 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nnd.itfs.nsk.su (nnd.itfs.nsk.su [193.124.36.42]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA26022 for ; Thu, 9 Apr 1998 21:14:28 -0700 (PDT) (envelope-from nnd@nnd.itfs.nsk.su) Received: (from nnd@localhost) by nnd.itfs.nsk.su (8.8.8/8.8.5) id LAA05584; Fri, 10 Apr 1998 11:18:58 +0700 (NSS) Date: Fri, 10 Apr 1998 11:18:58 +0700 (NSS) From: "Nickolay N. Dudorov" Message-Id: <199804100418.LAA05584@nnd.itfs.nsk.su> To: freebsd-current@FreeBSD.ORG Subject: Re: no more CTM deltas?? In-Reply-To: <9804080023.AA21754@cabri.obs-besancon.fr> User-Agent: tin/pre-1.4-980117 (UNIX) (FreeBSD/3.0-CURRENT (i386)) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In <9804080023.AA21754@cabri.obs-besancon.fr> Jean-Marc Zucconi wrote: > I did not receive any (cvs-cur) delta in the last 2 days. What is > happening? An I still can only see cvs-cur.4200.gz on ftp://ctm.freebsd.org/pub/FreeBSD/CTM/cvs-cur and ftp://ftp.freebsd.org/pub/FreeBSD/CTM/cvs-cur. Is there any chance to revive CTM service ? N.Dudorov To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 9 21:53:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA09060 for freebsd-current-outgoing; Thu, 9 Apr 1998 21:53:04 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA09043; Thu, 9 Apr 1998 21:53:01 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.8.8/8.7.3) id WAA16931; Thu, 9 Apr 1998 22:49:14 -0600 (MDT) Date: Thu, 9 Apr 1998 22:49:14 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199804100449.WAA16931@narnia.plutotech.com> To: FreeBSD current users cc: FreeBSD-scsi@FreeBSD.ORG Subject: Re: compression on Exabyte 8700LT? Newsgroups: pluto.freebsd.scsi In-Reply-To: <199804091527.QAA09483@albatross.mcc.ac.uk> <19980410112408.01873@freebie.lemis.com> User-Agent: tin/pre-1.4-971204 (UNIX) (FreeBSD/3.0-CURRENT (i386)) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I don't know why this was sent to questions. It was started on SCSI which seems to be where it belongs... > -CURRENT people: I'm using the old SCSI driver. The tape is set to > start up in compressed mode, and the DC LED is illuminated all the > time. This looks to me as if something in the driver is explicitly > disabling compression, or just possibly that the driver is guessing > the size of the tape and stopping (with EIO) when it reaches this > point. Neither the old driver, nor the CAM driver performs any type of guessing about the size of the tape. > The other point is that it's still returning EIO. I know there's been > some discussion about this before, and ISTR that it was inconclusive > ("that's the way our grandfathers did it"). While looking at the > problem, I came across a program I wrote in my BSD/OS days back in > 1992, and I note that even then BSD/OS returned ENOSPC when it got to > the end of the tape. This makes a whole lot more sense, and it > obviously seems to have withstood the test of time. How about it? The decision was that it should return ENOSPC. The CAM driver does return ENOSPC. I have patches, in my CAM tree, to ensure that dump and restore correctly deal with ENOSPC as an EOT condition. Someone should probably check pax, cpio, and tar. > Would I get an improvement on either of these points if I installed > CAM? Probably. You may want to wait for the weekend though. I'm "this close" to finishing the BusLogic driver, and I intend to release a new snapshot at that time. This will also include some improvements to the tape driver. > I know that CAM can't handle compression switching yet, but can > it do compression if it's enabled on the drive? The next snapshot will have compression and density control support. Ken's already implemented, and tested it. > Greg -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 9 21:58:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA11469 for freebsd-current-outgoing; Thu, 9 Apr 1998 21:58:40 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id VAA11438 for ; Thu, 9 Apr 1998 21:58:30 -0700 (PDT) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id FAA07398; Fri, 10 Apr 1998 05:27:25 +0200 From: Luigi Rizzo Message-Id: <199804100327.FAA07398@labinfo.iet.unipi.it> Subject: Re: Sound on DK440LX? To: ckempf@enigami.com (Cory Kempf) Date: Fri, 10 Apr 1998 05:27:25 +0200 (MET DST) Cc: freebsd-current@FreeBSD.ORG In-Reply-To: from "Cory Kempf" at Apr 9, 98 11:13:36 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > If so, how did you get it to work? > > I have tried both the SB (sound blaster) and the CSS (crystal) devices, but > neither seems to work. At least they do not seem to be found on startup. have you tried to replace the "controller snd0" and associated devices with "device pcm0" ? cheers luigi -----------------------------+-------------------------------------- Luigi Rizzo | Dip. di Ingegneria dell'Informazione email: luigi@iet.unipi.it | Universita' di Pisa tel: +39-50-568533 | via Diotisalvi 2, 56126 PISA (Italy) fax: +39-50-568522 | http://www.iet.unipi.it/~luigi/ _____________________________|______________________________________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 9 22:34:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA20951 for freebsd-current-outgoing; Thu, 9 Apr 1998 22:34:27 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from www.giovannelli.it (www.giovannelli.it [194.184.65.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA20858 for ; Thu, 9 Apr 1998 22:34:08 -0700 (PDT) (envelope-from gmarco@giovannelli.it) Received: from giovannelli.it (modem00.masternet.it [194.184.65.254]) by www.giovannelli.it (8.8.8/8.8.5) with ESMTP id HAA00235 for ; Fri, 10 Apr 1998 07:31:23 +0200 (MET DST) Message-ID: <352DCC05.499C044F@giovannelli.it> Date: Fri, 10 Apr 1998 07:36:37 +0000 From: Gianmarco Giovannelli X-Mailer: Mozilla 4.05 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: make world fails 980409 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I don't know it's my fault but ... ===> usr.sbin/stallion/stlstats --- .depend --- rm -f .depend mkdep -f .depend -a -I/usr/obj/usr/src/tmp/usr/include /usr/src/usr.sbin/stallion/st lstats/stlstats.c cd /usr/src/usr.sbin/stallion/stlstats; /usr/obj/usr/src/tmp/usr/bin/make _EXTRADEPEND --- _EXTRADEPEND --- echo stlstats: `cc -nostdinc -Wl,-f -O -pipe -I/usr/obj/usr/src/tmp/usr/include -Wl ,-lncurses -Wl,-lmytinfo` >> .depend ===> usr.sbin/vidcontrol --- .depend --- rm -f .depend mkdep -f .depend -a -I/usr/obj/usr/src/tmp/usr/include /usr/src/usr.sbin/vidcontrol/ vidcontrol.c /usr/src/usr.sbin/vidcontrol/decode.c cd /usr/src/usr.sbin/vidcontrol; /usr/obj/usr/src/tmp/usr/bin/make _EXTRADEPEND --- _EXTRADEPEND --- echo vidcontrol: `cc -nostdinc -Wl,-f -O -pipe -Wall -I/usr/obj/usr/src/tmp/usr/includ e ` >> .depend 1 error *** Error code 2 -- Regards... Gianmarco "Unix expert since yesterday" http://www.giovannelli.it To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 9 22:46:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA23540 for freebsd-current-outgoing; Thu, 9 Apr 1998 22:46:41 -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 WAA23530; Thu, 9 Apr 1998 22:46:37 -0700 (PDT) (envelope-from grog@lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.8.7/8.8.5) with ESMTP id PAA16901; Fri, 10 Apr 1998 15:16:33 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.8.8/8.8.7) id PAA01558; Fri, 10 Apr 1998 15:16:33 +0930 (CST) (envelope-from grog) Message-ID: <19980410151633.34010@freebie.lemis.com> Date: Fri, 10 Apr 1998 15:16:33 +0930 From: Greg Lehey To: "Justin T. Gibbs" , FreeBSD current users Cc: FreeBSD-scsi@FreeBSD.ORG Subject: Re: compression on Exabyte 8700LT? References: <199804091527.QAA09483@albatross.mcc.ac.uk> <199804100449.WAA16931@narnia.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <199804100449.WAA16931@narnia.plutotech.com>; from Justin T. Gibbs on Thu, Apr 09, 1998 at 10:49:14PM -0600 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 Thu, 9 April 1998 at 22:49:14 -0600, Justin T. Gibbs wrote: > I don't know why this was sent to questions. It was started on SCSI > which seems to be where it belongs... I saw it on -scsi and -questions. Since it related to -current, I followed up there. The copy to -questions was a one-off to tell people where it had gone. >> -CURRENT people: I'm using the old SCSI driver. The tape is set to >> start up in compressed mode, and the DC LED is illuminated all the >> time. This looks to me as if something in the driver is explicitly >> disabling compression, or just possibly that the driver is guessing >> the size of the tape and stopping (with EIO) when it reaches this >> point. > > Neither the old driver, nor the CAM driver performs any type of guessing > about the size of the tape. I didn't think so. I was just wondering why the capacity was so much less than the nominal capacity. >> The other point is that it's still returning EIO. I know there's been >> some discussion about this before, and ISTR that it was inconclusive >> ("that's the way our grandfathers did it"). While looking at the >> problem, I came across a program I wrote in my BSD/OS days back in >> 1992, and I note that even then BSD/OS returned ENOSPC when it got to >> the end of the tape. This makes a whole lot more sense, and it >> obviously seems to have withstood the test of time. How about it? > > The decision was that it should return ENOSPC. The CAM driver does > return ENOSPC. I have patches, in my CAM tree, to ensure that dump > and restore correctly deal with ENOSPC as an EOT condition. Good. > Someone should probably check pax, cpio, and tar. I'll definitely check tar. >> Would I get an improvement on either of these points if I installed >> CAM? > > Probably. You may want to wait for the weekend though. I'm "this close" > to finishing the BusLogic driver, and I intend to release a new snapshot > at that time. This will also include some improvements to the tape > driver. Good. I'll do that. Is it now in -CURRENT? >> I know that CAM can't handle compression switching yet, but can >> it do compression if it's enabled on the drive? > > The next snapshot will have compression and density control support. > Ken's already implemented, and tested it. Great 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 Thu Apr 9 23:45:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA06265 for freebsd-current-outgoing; Thu, 9 Apr 1998 23:45:54 -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 XAA06235 for ; Thu, 9 Apr 1998 23:45:51 -0700 (PDT) (envelope-from toasty@home.dragondata.com) Received: (from toasty@localhost) by home.dragondata.com (8.8.8/8.8.5) id BAA19234; Fri, 10 Apr 1998 01:45:49 -0500 (CDT) From: Kevin Day Message-Id: <199804100645.BAA19234@home.dragondata.com> Subject: Re: wdtimeout() In-Reply-To: <199804090305.WAA28898@home.dragondata.com> from Kevin Day at "Apr 8, 98 10:05:27 pm" To: toasty@home.dragondata.com (Kevin Day) Date: Fri, 10 Apr 1998 01:45:47 -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 > > Since sometime in Feb. I've been getting: > > wd0: Last time I say: interrupt timeout. Probably a portable PC.: > wd0: status 58 error 1 > wd0: wdtimeout() DMA status 4 > > Going back to older kernels stops this from happening. Is this a known > problem? > To add a bit more, I'm also getting these messages, but not at exactly the same time. vm_fault: pager input (probably hardware) error, PID 24793 failure /kernel: pid 24793 (bash), uid 1143: exited on signal 11 I usually get a 'burst' of two or three of those messages at a time, too. I'm not sure if this is related or not. I've ruled out the swap being bad by; 1) replacing the drive 2) Doing some pretty extensive pattern testing on the entire drive Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 9 23:47:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA07211 for freebsd-current-outgoing; Thu, 9 Apr 1998 23:47:56 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from quokka.prth.tensor.pgs.com (quokka1.prth.tensor.pgs.com [157.147.224.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA07131; Thu, 9 Apr 1998 23:47:41 -0700 (PDT) (envelope-from shocking@ariadne.prth.tensor.pgs.com) Received: from ariadne.tensor.pgs.com (ariadne [157.147.227.36]) by quokka.prth.tensor.pgs.com (8.8.7/8.8.7) with SMTP id OAA19738; Fri, 10 Apr 1998 14:46:53 +0800 (WST) Received: from ariadne by ariadne.tensor.pgs.com (SMI-8.6/SMI-SVR4) id OAA27390; Fri, 10 Apr 1998 14:46:45 +0800 Message-Id: <199804100646.OAA27390@ariadne.tensor.pgs.com> X-Mailer: exmh version 2.0.2 2/24/98 To: current@FreeBSD.ORG cc: multimedia@FreeBSD.ORG Subject: Patches to Linux emulator enc. Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 10 Apr 1998 14:46:45 +0800 From: Stephen Hocking-Senior Programmer PGS Tensor Perth Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG These diffs implement the mremap & ioperm system calls for Linux, which is sufficient to allow a certain Linux 3d visualisation & simulation program to run. The work was done by Amancio Hasty & another whose name I can't recall at the moment. I would've sent it in as a PR, but don't have a machine with send-pr attached to the net at the moment. begin 644 linuxdiffs.tar.gz M'XL(".^_+34" VQI;G5X9&EF9G,N=&%R .U9:W/:1A3U5_E7;)M)AG?T!D2; M#HY)R@0,8XA#VW0TLK083?2J'J[=)/^]=W5V7YB.=YD6\+Y#\IV7]!%M4C7E4$2>(516T? MD2I! ?S1/U"2*#9"&#):^>8'V[O:A0M]/][K)/%.7COW'RFU6@VU6L\=N@TL M.XK3RQ4W2SS4#T*$%"2T-5G0%!X)W6[GN-ELH@ST*K0I2( V2>-Y3109J%8L MY!X):K$(U9Y#PQ-VAT;# ML[<+_G^O1\> ']<#@AGW?QI/+@:X'LP-RWLV:# M\63*P7-'_YM" UFW$M>];9D/E 7NX7]>5<6,_R5%)?6"(BGB@?\?C_^S'<'- M5PEZA2^!U.&C*5U(!%M9((>^PQ:#$H0FR_#9EPL$R 4BHP_&,R&.D]!#@[/) M[*=9#RH_D_AM(MN+C[.Q;#_ H5N)XC Q8Q2$OHEJ00.E]YL8W0BO(,C)=Q4> M_PA_I 0A=+>L?#LBT"9V$Z?RU*IJ*.VXBCP_1E$2!'X88^N]]VT#!*_X%F1>R^)?YML3B7Q0.\?^(\9_NB"^)_SM0D( 0 M_%U-4G?'?T=M-SI9_).^:$57SN0#1W9_\X7I6NA[=#'7W_6'\_[+^?!B0)B! M2T,0T;$K$$=98-&*-("J-((('I0"*:81W5%R&M-NA?'RQAYI2YRS4@ZY$@?Y'EJ=][4RYI2 MZRNU9>*9UF85FA'E>?D4Z [3(OML:D&E0KK]]1+:3VE9M $+N& MYT"6&8D3:UM>,+*EB,_Y%)*K-(44%YB)?XV1\?8"L\;>_TCJ[>%_UX[,!Z/_ M^_A?;HNY_I.EMDCY7U"4 _\_(O^S'<&-_?1' *#R#ASN-;Z[3?^E2(G7Y#WL M+W:Z#;&K;JH_5"/Z24/QRHX0?(@.,WTW<'",6\@&4;;R$\="Y@J;'Y"9A"$& MXDPBXPJCZ>CM;-U-O,+ %Y&?A"8<\SR,+1"FE[>L9\>^#(WPMI7#GQ]_PVAX M":RK^TD,M*O'^"9&+]"XOYC/AC^C3Y\ Q.6MEA$;J(XNHTB/[#\P *E$#!W; MM>-?SD?#\7"NG_;G_5];I$X'8PF- P?A,/1#X!_0N./!F&:R*S_VD>E@PTN" MWG'&:&1ZLTE*,^*_?Y+0GAD"U.F.J:P_Y$26[3ZU*S?:/)_M/II@Z!34UW/G6BW7@ADD#L5+'2\= T;]]#V: MSD;Z<#(=;0C(>PZ9]4SV;)TSP2SG7H>=@KNEZR.KC:XB;*R/ A7=]4[\4G_6 M2\9G*T0PWFF%*5HD& T.ZB9=C8,X^4A%[[=L6/ $:D^EKB!L= M.L5>+WWX,\PF$)5%G\LJB2;/*(8GE4_L)4A2=#HX>?LZ6]$=&R-UYRG?N6F@ M[>\JV2#009W+]@3LDT:ZQXF5V;7O6#I8F=UZ^/?-6SK15"D_P1ZHMM2D A9, M#_W$L_0 V+]2:*KV"@^D8Y4]D#;E#] $4!CE1;&3]+QRARKXS:-4QMKUM7[? MU?UWI=UGZ]4B4Y9S!+VI%V>A5X S+XM>-TL>R-:>;:F48U@?U1*S[WC+GO\! M\4AC)+DVL%>,[Y2;=X6S9YMX?V001"$N_IK^BVXCTW" V^#-]X&BIBB:LN=]H @Y7Y2ZF0X3 M5)$[FTS/)_,)-YW,A@ON(R5BS_#\R,$XJ)B^%\79]J=R)\ 0$N%O,43%>Y)K M.&XC(6P@W#B ;/R9:2!!E;BW9\/Q=,3>&W&,LJD)>"KS6?;\1SV=S4]3D]@@A:2;_OJ"6.HAS7GB>4^$.A1J @6)9^R$V:?.@8#S%A1X=R*(=R*(?R\.5/I_BA%P F "" end To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 10 01:43:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA25899 for freebsd-current-outgoing; Fri, 10 Apr 1998 01:43:53 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.aloha.com (root@leahi.aloha.com [206.127.224.94]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA25894 for ; Fri, 10 Apr 1998 01:43:51 -0700 (PDT) (envelope-from knowtree@aloha.com) Received: from 209.84.67.71 (behemoth1-69.pixi.net [209.84.67.71]) by mail.aloha.com (8.8.7/8.8.7/PIXI-5.2) with SMTP id WAA27470; Thu, 9 Apr 1998 22:43:44 -1000 (HST) Message-ID: <352DDC16.67F@aloha.com> Date: Thu, 09 Apr 1998 22:45:10 -1000 From: Gary Dunn Reply-To: knowtree@aloha.com Organization: Knowledge Tree X-Mailer: Mozilla 3.01Gold (Macintosh; I; 68K) MIME-Version: 1.0 To: Lars Jonas Olsson CC: current@FreeBSD.ORG Subject: Re: Current boot.flp fails References: <199804082018.PAA06998@Mercury.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 Lars Jonas Olsson wrote: > > I'm trying to install current on a test machine. The same machine has > no trouble with 2.2.5 and 2.2.6 installations in exactly same > configuration.. With 980408 and 980312 boot.flp's the installation > times out after: > > adding default route to 10.0.0.15 > > The system is a Texas Microsystems Dual PII SBC w modified Phoenix > BIOS, 256MB, SMC 9332BDT, connected to Netgear fast ethernet hub, IP # > 10.0.0.17 on a 10.0.0.X network behind a NATD firewall/gateway/DNS > server at 10.0.0.15. I'm doing the install in passive FTP mode. > Any ideas on what's wrong? Should I try some other SNAP? > > Jonas I got that when installing 2.2.6 with a non-standard i/o port setting on an SMC8000 ethernet board. Fixed by changing the port setting in the kernel configuration section. Look for something that makes the system think it has a network connection but which is broken, even a bad cable. -- Gary Dunn Knowledge Tree Honolulu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 10 01:44:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA26210 for freebsd-current-outgoing; Fri, 10 Apr 1998 01:44:58 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from Mail.Everyware.SE (Mail.Everyware.SE [192.71.91.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA26191 for ; Fri, 10 Apr 1998 01:44:55 -0700 (PDT) (envelope-from nasten@Everyware.SE) Received: (from mail@localhost) by Mail.Everyware.SE (8.8.5/8.8.5) id KAA00476 for ; Fri, 10 Apr 1998 10:44:54 +0200 (MET DST) Received: from tott.everyware.se(192.71.91.113) by Mail.Everyware.SE via smap (V1.3) id sma000473; Fri Apr 10 10:44:25 1998 Received: (from nasten@localhost) by Tott.Everyware.SE (8.8.5/8.8.5) id KAA11914 for FreeBSD-current@FreeBSD.ORG; Fri, 10 Apr 1998 10:44:21 +0200 (MET DST) From: Hans Nasten Message-Id: <199804100844.KAA11914@Tott.Everyware.SE> Subject: Re: Sound on DK440LX? To: FreeBSD-current@FreeBSD.ORG Date: Fri, 10 Apr 1998 10:44:20 +0200 (MET DST) In-Reply-To: <199804100327.FAA07398@labinfo.iet.unipi.it> from "Luigi Rizzo" at Apr 10, 98 05:27:25 am Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Luigi Rizzo writes : > >> If so, how did you get it to work? >> >> I have tried both the SB (sound blaster) and the CSS (crystal) devices, but >> neither seems to work. At least they do not seem to be found on startup. > >have you tried to replace the "controller snd0" and associated devices >with "device pcm0" ? > > cheers > luigi Yes, I have sound working on my DK440LX. Using Luigi's driver patched so that the CS4236 chip gets recognized. The pnp id differs from what the driver expects. The pnp id of the chip is 0x350b630e, but the driver expects 0x360b630e. I have sent a suggested patch to Luigi a few weeks ago. /Hans *** /usr/src/sys/i386/isa/snd/ad1848.c.orig Tue Feb 17 22:24:11 1998 --- /usr/src/sys/i386/isa/snd/ad1848.c Thu Apr 9 11:09:30 1998 *************** *** 1354,1360 **** u_long id = vend_id & 0xff00ffff; if ( id == 0x3700630e ) s = "CS4237" ; ! else if ( id == 0x3600630e ) s = "CS4236" ; else if ( id == 0x3200630e) s = "CS4232" ; --- 1354,1360 ---- u_long id = vend_id & 0xff00ffff; if ( id == 0x3700630e ) s = "CS4237" ; ! else if ( id == 0x3500630e || id == 0x3600630e ) s = "CS4236" ; else if ( id == 0x3200630e) s = "CS4232" ; *************** *** 1431,1436 **** --- 1431,1437 ---- tmp_d.bd_id = MD_CS4237 ; break; + case 0x3500630e: /* CS4236 */ case 0x3600630e: /* CS4236 */ tmp_d.bd_id = MD_CS4236 ; break; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 10 07:21:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA15179 for freebsd-current-outgoing; Fri, 10 Apr 1998 07:21:43 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.visint.co.uk (wakko.visint.co.uk [194.207.134.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA15174 for ; Fri, 10 Apr 1998 07:21:41 -0700 (PDT) (envelope-from steve@visint.co.uk) Received: from dylan (dylan.visint.co.uk [194.207.134.180]) by mail.visint.co.uk (8.8.8/8.8.5) with SMTP id PAA13707; Fri, 10 Apr 1998 15:21:37 +0100 (BST) Date: Fri, 10 Apr 1998 15:21:44 +0100 (BST) From: Stephen Roome X-Sender: steve@dylan To: Alfred Perlstein cc: freebsd-current@FreeBSD.ORG Subject: Re: ps segfaults since I overclocked. and worries. In-Reply-To: <02f001bd6404$e9e22280$0600a8c0@win95.local.sunyit.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 Thu, 9 Apr 1998, Alfred Perlstein wrote: > overclocking is a problem with most all machines, don't do it. <-- period This isn't a hardware problem, everything works fine, the machine runs solidly all day. Every ISA/PCI device (all disks included, all the ram everything is fine), even under heavy load (I made about 10 different kernels in a row to try and find the problem, all make -j8, and nothing crashed at all, just the normal builds) Anyway, All I've done is upped the bus speed slightly and the processor is running only a little bit faster (it's a 166 really), besides I've been informed that the 166MMX i've got is probably a 200, because the suppliers in the UK apparently ran out of 166's and rebadged 200's at the time I bought mine. Don't know whetyher I beleive this or not, but then it's only at most 11% faster than it should be. So, I'm pretty certain the hardware isn't failing, but that something in FreeBSD might just not like using an odd bus speed. Which is fine, apart from it's quite okay to clock some processors and busses at these speeds and someone else is probably going to have much the same problem when these settings are the default. (e.g an owner of a 6x86MX at 188Mhz with a bus speed of 75Mhz.) Steve. Steve Roome - Vision Interactive Ltd. Tel:+44(0)117 9730597 Home:+44(0)976 241342 WWW: http://dylan.visint.co.uk/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 10 07:30:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA16678 for freebsd-current-outgoing; Fri, 10 Apr 1998 07:30:35 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.mishkei.org.il (host3-64.mishkei.org.il [62.0.64.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA16668 for ; Fri, 10 Apr 1998 07:30:29 -0700 (PDT) (envelope-from lickyou@ein-hashofet.co.il) Received: from box.from.hell (host44-68.mishkei.org.il [62.0.68.44]) by mail.mishkei.org.il (8.8.5/8.8.5) with SMTP id RAA11855; Fri, 10 Apr 1998 17:30:17 +0300 Date: Fri, 10 Apr 1998 17:30:55 +0000 (GMT) From: Gilad Rom X-Sender: lickyou@box.from.hell To: Stephen Roome cc: Alfred Perlstein , freebsd-current@FreeBSD.ORG Subject: Re: ps segfaults since I overclocked. and worries. 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 Stephen, Ive had wierder problems. When I purchased this box and installed FreeBSD on it, w/o over clocking even, it would fail. reboot all of the sudden. Sometimes a 'make world' would finish successfuly, sometimes it would reboot 10 minutes in. Ive replaced the RAM, Ive even replaced the CPU (Gone from 166MMX to 200 one). Didnt help. I suggest you try a change of motherboards. Helped for me. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 10 07:43:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA18554 for freebsd-current-outgoing; Fri, 10 Apr 1998 07:43:08 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA18548 for ; Fri, 10 Apr 1998 07:43:05 -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 QAA08008; Fri, 10 Apr 1998 16:41:51 +0200 (CEST) To: Stephen Roome cc: Alfred Perlstein , freebsd-current@FreeBSD.ORG Subject: Re: ps segfaults since I overclocked. and worries. In-reply-to: Your message of "Fri, 10 Apr 1998 15:21:44 BST." Date: Fri, 10 Apr 1998 16:41:51 +0200 Message-ID: <8006.892219311@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Stephen Roome write s: >On Thu, 9 Apr 1998, Alfred Perlstein wrote: >> overclocking is a problem with most all machines, don't do it. <-- period > >Anyway, All I've done is upped the bus speed slightly and the processor is >running only a little bit faster (it's a 166 really), besides I've been >informed that the 166MMX i've got is probably a 200, because the suppliers >in the UK apparently ran out of 166's and rebadged 200's at the time I >bought mine. Don't know whetyher I beleive this or not, but then it's only >at most 11% faster than it should be. Steve, and everybody else: If you overclock, we don't want to waste time on your trouble before you convince us that the same problem occur if you run your hardware inside spec. End of story! Run it inside spec, if you still have problems, tell us, if they disappear you will probably be able to draw your own conclusions from that. DO NOT EVEN BOTHER REPLY UNTIL YOU HAVE DONE THIS! -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "Drink MONO-tonic, it goes down but it will NEVER come back up!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 10 08:13:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA24212 for freebsd-current-outgoing; Fri, 10 Apr 1998 08:13:37 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.visint.co.uk (wakko.visint.co.uk [194.207.134.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA24198 for ; Fri, 10 Apr 1998 08:13:34 -0700 (PDT) (envelope-from steve@visint.co.uk) Received: from dylan (dylan.visint.co.uk [194.207.134.180]) by mail.visint.co.uk (8.8.8/8.8.5) with SMTP id QAA13881; Fri, 10 Apr 1998 16:11:25 +0100 (BST) Date: Fri, 10 Apr 1998 16:11:32 +0100 (BST) From: Stephen Roome X-Sender: steve@dylan To: Poul-Henning Kamp cc: current@FreeBSD.ORG Subject: Re: ps segfaults since I overclocked. and worries. In-Reply-To: <8006.892219311@critter.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 10 Apr 1998, Poul-Henning Kamp wrote: > Steve, and everybody else: > > If you overclock, we don't want to waste time on your trouble before you > convince us that the same problem occur if you run your hardware inside > spec. > > End of story! > > Run it inside spec, if you still have problems, tell us, if they disappear > you will probably be able to draw your own conclusions from that. > > DO NOT EVEN BOTHER REPLY UNTIL YOU HAVE DONE THIS! My machine is fine at normal speeds, without the overclocking, I already mentioned this. I was wondering if there was a problem with FreeBSD on computers with non 66MHz bus speeds. There is some mention of this in /sys/pci/ide_pci.c, I am 100% certain that the hardware I have is performing fine at these speeds, however it would be handy if FreeBSD is able to cope with the new higher limits that are going to be in place fairly soon. It's silly to assume we'll be stuck with 66MHz busses forever and anyone who actually owns a 188MHz 6x86MX will be clocking at 75MHz buss speed anyway. If there are hardcoded limits that prevent these people from using FreeBSD then that is a problem. Isn't it ? I'm not asking for for anyone to solve this problem for me specifically. I'm just asking whether FreeBSD will actually run properly on a standard PC that is by default running at frequencies and with timing values that people are not used to. Does the following mean that some new PC's are not going to work properly? And that FreeBSD just won't support them ? from src/sys/pci/ide_pci.c: 355- } 356-} 357- 358-/* 359- * XXX timing values set here are only good for 30/33MHz buses; should deal 360: * with slower ones too (BTW: you overclock-- you lose) 361- */ 362- 363-static int 364-via_571_dmainit(struct ide_pci_cookie *cookie, 365- struct wdparams *wp, -- 660- } 661-} 662- 663-/* 664- * XXX timing values set hereare only good for 30/33MHz buses; should deal 665: * with slower ones too (BTW: you overclock-- you lose) 666- */ 667- 668-static int 669-intel_piix_dmainit(struct ide_pci_cookie *cookie, 670- struct wdparams *wp, I'll shut up now, but if FreeBSD isn't going to be supporting hardware that will be becoming standard soon then I'm slightly worried, I'd have thought current- was the testing ground for stuff such as this Steve Steve Roome - Vision Interactive Ltd. Tel:+44(0)117 9730597 Home:+44(0)976 241342 WWW: http://dylan.visint.co.uk/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 10 08:21:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA25630 for freebsd-current-outgoing; Fri, 10 Apr 1998 08:21:57 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA25620 for ; Fri, 10 Apr 1998 08:21:55 -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 RAA08070; Fri, 10 Apr 1998 17:20:58 +0200 (CEST) To: Stephen Roome cc: current@FreeBSD.ORG Subject: Re: ps segfaults since I overclocked. and worries. In-reply-to: Your message of "Fri, 10 Apr 1998 16:11:32 BST." Date: Fri, 10 Apr 1998 17:20:58 +0200 Message-ID: <8068.892221658@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Stephen Roome write s: >On Fri, 10 Apr 1998, Poul-Henning Kamp wrote: >> Steve, and everybody else: >> >> If you overclock, we don't want to waste time on your trouble before you >> convince us that the same problem occur if you run your hardware inside >> spec. >> >> End of story! >> >> Run it inside spec, if you still have problems, tell us, if they disappear >> you will probably be able to draw your own conclusions from that. >> >> DO NOT EVEN BOTHER REPLY UNTIL YOU HAVE DONE THIS! > >My machine is fine at normal speeds, without the overclocking, I already >mentioned this. Good, then you are wasting the time of a couple of thousand people, which is bad. Now stop it please! Don't overclock. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "Drink MONO-tonic, it goes down but it will NEVER come back up!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 10 08:26:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA26832 for freebsd-current-outgoing; Fri, 10 Apr 1998 08:26:48 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from serv.unibest.ru (serv.unibest.ru [194.87.33.9]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id IAA26823 for ; Fri, 10 Apr 1998 08:26:45 -0700 (PDT) (envelope-from osa@unibest.ru) Received: (qmail 24581 invoked from network); 10 Apr 1998 14:32:02 -0000 Received: from unknown (HELO hole.etrust.ru) (192.168.30.2) by serv.unibest.ru with SMTP; 10 Apr 1998 14:32:02 -0000 Date: Fri, 10 Apr 1998 19:28:32 +0400 (MSD) From: Ozz!!! X-Sender: osa@hole.etrust.ru To: freebsd-current@FreeBSD.ORG Subject: What version of PPP in FreeBSD-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 Hello! What version of PPP in FreeBSD-current ??? What do you think about of ppp-2.3.2 version ?? That containes files for FreeBSD-2.X, but what about FreeBSD-3.0 ? Rgdz, oZZ, osa@unibest.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 10 08:31:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA28219 for freebsd-current-outgoing; Fri, 10 Apr 1998 08:31:16 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from serv.unibest.ru (serv.unibest.ru [194.87.33.9]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id IAA28188 for ; Fri, 10 Apr 1998 08:31:08 -0700 (PDT) (envelope-from osa@unibest.ru) Received: (qmail 24591 invoked from network); 10 Apr 1998 14:36:24 -0000 Received: from unknown (HELO hole.etrust.ru) (192.168.30.2) by serv.unibest.ru with SMTP; 10 Apr 1998 14:36:24 -0000 Date: Fri, 10 Apr 1998 19:33:00 +0400 (MSD) From: Ozz!!! X-Sender: osa@hole.etrust.ru To: freebsd-current@FreeBSD.ORG Subject: About PPP-2.3.4 ... 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! Sorry, but now avaliable ppp-2.3.4 ... ftp://cs.anu.edu.au/pub/software/ppp/ppp-2.3.4.tar.gz Rgdz, oZZ, osa@unibest.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 10 08:31:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA28299 for freebsd-current-outgoing; Fri, 10 Apr 1998 08:31:32 -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 IAA28273 for ; Fri, 10 Apr 1998 08:31: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 IAA08623; Fri, 10 Apr 1998 08:29:19 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: Stephen Roome cc: Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: ps segfaults since I overclocked. and worries. In-reply-to: Your message of "Fri, 10 Apr 1998 16:11:32 BST." Date: Fri, 10 Apr 1998 08:29:18 -0700 Message-ID: <8619.892222158@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'll shut up now, but if FreeBSD isn't going to be supporting hardware > that will be becoming standard soon then I'm slightly worried, I'd have > thought current- was the testing ground for stuff such as this Certainly, though clocking pre-standard hardware up to the standard and testing that would only constitute poor testing methodology. Before becoming even slightly worried, I'd first want to see test failures on hardware where all components are rated for the conditions of the test. Considering the number of manufacturers involved just in getting all the components on a motherboard to work properly together at some target clock speed, it's often surprising to consider that the whole mess works 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 Fri Apr 10 08:36:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA29365 for freebsd-current-outgoing; Fri, 10 Apr 1998 08:36:47 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from awfulhak.org (awfulhak.demon.co.uk [158.152.17.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA29359 for ; Fri, 10 Apr 1998 08:36:43 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from gate.lan.awfulhak.org (localhost [127.0.0.1]) by awfulhak.org (8.8.8/8.8.7) with ESMTP id QAA13701; Fri, 10 Apr 1998 16:36:11 +0100 (BST) (envelope-from brian@gate.lan.awfulhak.org) Message-Id: <199804101536.QAA13701@awfulhak.org> X-Mailer: exmh version 2.0.1 12/23/97 To: Ozz!!! cc: freebsd-current@FreeBSD.ORG Subject: Re: What version of PPP in FreeBSD-current ??? In-reply-to: Your message of "Fri, 10 Apr 1998 19:28:32 +0400." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 10 Apr 1998 16:36:11 +0100 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hello! > What version of PPP in FreeBSD-current ??? 2.3.3. > What do you think about of ppp-2.3.2 version ?? > That containes files for FreeBSD-2.X, but what about > FreeBSD-3.0 ? > > Rgdz, > oZZ, > osa@unibest.ru -- 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 Fri Apr 10 08:39:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA00408 for freebsd-current-outgoing; Fri, 10 Apr 1998 08:39:58 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ebene.inrialpes.fr (ebene.inrialpes.fr [194.199.18.70]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA00337 for ; Fri, 10 Apr 1998 08:39:51 -0700 (PDT) (envelope-from claude.castelluccia@inrialpes.fr) Received: from palmier.inrialpes.fr (palmier.inrialpes.fr [194.199.18.71]) by ebene.inrialpes.fr (8.8.5/8.8.5) with ESMTP id RAA28051; Fri, 10 Apr 1998 17:39:31 +0200 (MET DST) Received: from guadalupe (guadalupe.inrialpes.fr [194.199.20.37]) by palmier.inrialpes.fr (8.8.5/8.8.5) with SMTP id RAA01821; Fri, 10 Apr 1998 17:39:31 +0200 (MET DST) Message-ID: <352E3D32.2534@inrialpes.fr> Date: Fri, 10 Apr 1998 17:39:30 +0200 From: Claude Castelluccia Organization: Inria Rhone-Alpes X-Mailer: Mozilla 3.01Gold (X11; I; SunOS 5.5 sun4m) MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG CC: claude.castelluccia@inrialpes.fr Subject: -looking for a WaveLAN driver- Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, We are looking for a WaveLAN driver for the PA0-971211/2.2.5-Release FreeBSD. Does anybody know where we can get it? Thanks a lot for your help! Claude. ---------------------------------------- Claude CASTELLUCCIA, INRIA Rhone-Alpes ph: +33 4.76.61.52.15 (fax: 52.52) ------- http://sirac.inrialpes.fr/------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 10 10:29:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA15953 for freebsd-current-outgoing; Fri, 10 Apr 1998 10:29:36 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA15898 for ; Fri, 10 Apr 1998 10:29:08 -0700 (PDT) (envelope-from mark@grondar.za) Received: from greenpeace.grondar.za (greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.8.8/8.8.8) with ESMTP id TAA12537; Fri, 10 Apr 1998 19:28:18 +0200 (SAST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by greenpeace.grondar.za (8.8.8/8.8.8) with ESMTP id TAA10399; Fri, 10 Apr 1998 19:28:18 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199804101728.TAA10399@greenpeace.grondar.za> To: "Nickolay N. Dudorov" cc: freebsd-current@FreeBSD.ORG Subject: Re: no more CTM deltas?? Date: Fri, 10 Apr 1998 19:28:18 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Nickolay N. Dudorov" wrote: > In <9804080023.AA21754@cabri.obs-besancon.fr> Jean-Marc Zucconi wrote: > > I did not receive any (cvs-cur) delta in the last 2 days. What is > > happening? The machine that was generating the CTM's had space problems in $TMPDIR. I've fixed that. Apologies! M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 10 11:11:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA24523 for freebsd-current-outgoing; Fri, 10 Apr 1998 11:11:35 -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 LAA24507 for ; Fri, 10 Apr 1998 11:11:32 -0700 (PDT) (envelope-from toasty@home.dragondata.com) Received: (from toasty@localhost) by home.dragondata.com (8.8.8/8.8.5) id NAA29718; Fri, 10 Apr 1998 13:09:19 -0500 (CDT) From: Kevin Day Message-Id: <199804101809.NAA29718@home.dragondata.com> Subject: Re: ps segfaults since I overclocked. and worries. In-Reply-To: <8619.892222158@time.cdrom.com> from "Jordan K. Hubbard" at "Apr 10, 98 08:29:18 am" To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Fri, 10 Apr 1998 13:09:18 -0500 (CDT) Cc: steve@visint.co.uk, phk@critter.freebsd.dk, 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'll shut up now, but if FreeBSD isn't going to be supporting hardware > > that will be becoming standard soon then I'm slightly worried, I'd have > > thought current- was the testing ground for stuff such as this > > Certainly, though clocking pre-standard hardware up to the standard > and testing that would only constitute poor testing methodology. > Before becoming even slightly worried, I'd first want to see test > failures on hardware where all components are rated for the conditions > of the test. Considering the number of manufacturers involved just in > getting all the components on a motherboard to work properly together > at some target clock speed, it's often surprising to consider that the > whole mess works at all. > > Jordan If perhaps the sumbitter doesn't understand the error of overclocking: You just purchased a 1979 Ford Pinto station wagon. However, you are upset after driving it for a while that it won't go above 65 MPH. Feeling smart, you go and purchase soe rocket fuel. You pour it in your gas tank, and all seems well until hit a steep hill, at which time the engine explodes. This is not the fault of: Ford, the card dealer where you bought the car, or the hill itself. Likewise, Overclocking your processor and having things fail is not the fault of: Intel, your board manufacturer, or FreeBSD. Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 10 11:30:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA00699 for freebsd-current-outgoing; Fri, 10 Apr 1998 11:30:35 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from shell3.ba.best.com (root@shell3.ba.best.com [206.184.139.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA00673; Fri, 10 Apr 1998 11:30:32 -0700 (PDT) (envelope-from schrade@schrade.com) Received: from localhost (schrade@localhost [127.0.0.1]) by shell3.ba.best.com (8.8.8/8.8.BEST) with SMTP id LAA16591; Fri, 10 Apr 1998 11:29:25 -0700 (PDT) Date: Fri, 10 Apr 1998 11:29:23 -0700 (PDT) From: Ken Krebs To: Stephen Hocking-Senior Programmer PGS Tensor Perth cc: current@FreeBSD.ORG, multimedia@FreeBSD.ORG Subject: Re: Patches to Linux emulator enc. In-Reply-To: <199804100646.OAA27390@ariadne.tensor.pgs.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, 10 Apr 1998, Stephen Hocking-Senior Programmer PGS Tensor Perth wrote: >These diffs implement the mremap & ioperm system calls for Linux, which is >sufficient to allow a certain Linux 3d visualisation & simulation program to >run. The work was done by Amancio Hasty & another whose name I can't recall at >the moment. I would've sent it in as a PR, but don't have a machine with >send-pr attached to the net at the moment. With the source cvsupped to the very latest and the diffs applied: (doing a 'make depend && make all install' in /usr/src/lkm/linux) cc -O -pipe -DLKM -DCOMPAT_LINUX -DKERNEL -DACTUALLY_LKM_NOT_KERNEL -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wuninitialized -nostdinc -I- -I/usr/src/lkm/linux -I/usr/src/lkm/linux/@ -c /usr/src/lkm/linux/../../sys/i386/linux/linux_misc.c /usr/src/lkm/linux/../../sys/i386/linux/linux_misc.c:961: warning: `struct linux_mremap_args' declared inside parameter list /usr/src/lkm/linux/../../sys/i386/linux/linux_misc.c:961: warning: its scope is only this definition or declaration, /usr/src/lkm/linux/../../sys/i386/linux/linux_misc.c:961: warning: which is probably not what you want. /usr/src/lkm/linux/../../sys/i386/linux/linux_misc.c:962: warning: no previous prototype for `linux_mremap' /usr/src/lkm/linux/../../sys/i386/linux/linux_misc.c: In function `linux_mremap': /usr/src/lkm/linux/../../sys/i386/linux/linux_misc.c:972: dereferencing pointer to incomplete type /usr/src/lkm/linux/../../sys/i386/linux/linux_misc.c:972: dereferencing pointer to incomplete type /usr/src/lkm/linux/../../sys/i386/linux/linux_misc.c:973: dereferencing pointer to incomplete type /usr/src/lkm/linux/../../sys/i386/linux/linux_misc.c:973: dereferencing pointer to incomplete type /usr/src/lkm/linux/../../sys/i386/linux/linux_misc.c:974: dereferencing pointer to incomplete type /usr/src/lkm/linux/../../sys/i386/linux/linux_misc.c:974: dereferencing pointer to incomplete type /usr/src/lkm/linux/../../sys/i386/linux/linux_misc.c:979: dereferencing pointer to incomplete type /usr/src/lkm/linux/../../sys/i386/linux/linux_misc.c:979: dereferencing pointer to incomplete type /usr/src/lkm/linux/../../sys/i386/linux/linux_misc.c:980: dereferencing pointer to incomplete type /usr/src/lkm/linux/../../sys/i386/linux/linux_misc.c:980: dereferencing pointer to incomplete type /usr/src/lkm/linux/../../sys/i386/linux/linux_misc.c:981: dereferencing pointer to incomplete type /usr/src/lkm/linux/../../sys/i386/linux/linux_misc.c:981: dereferencing pointer to incomplete type /usr/src/lkm/linux/../../sys/i386/linux/linux_misc.c:985: dereferencing pointer to incomplete type *** Error code 1 *********** NewOrderDepecheModeUltravoxViolentFemmesKillingJoke ************* * Ken * NineInchNailsFront242TangerineDreamTheBreedersTekno * * * Krebs * SkinnyPuppyLaTourBauhausBookOfLoveModernEnglishB52s * * *********** FishBoneBigCountryJoyDivisonSiouxsie&TheBansheesXTC ************* IRC: Schrade E-Mail: schrade@schrade.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 10 12:03:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA09082 for freebsd-current-outgoing; Fri, 10 Apr 1998 12:03:16 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from set.spradley.tmi.net (set.spradley.tmi.net [207.170.107.99]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id MAA09076 for ; Fri, 10 Apr 1998 12:03:14 -0700 (PDT) (envelope-from tsprad@set.spradley.tmi.net) Received: from localhost (set.spradley.tmi.net) [127.0.0.1] by set.spradley.tmi.net with esmtp (Exim 1.82 #2) id 0yNj2W-0007PT-00; Fri, 10 Apr 1998 14:00:40 -0500 X-Mailer: exmh version 2.0zeta 7/24/97 To: Kevin Day cc: jkh@time.cdrom.com (Jordan K. Hubbard), steve@visint.co.uk, phk@critter.freebsd.dk, current@FreeBSD.ORG Subject: Re: ps segfaults since I overclocked. and worries. In-reply-to: Your message of "Fri, 10 Apr 1998 13:09:18 CDT." <199804101809.NAA29718@home.dragondata.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 10 Apr 1998 14:00:40 -0500 From: Ted Spradley Message-Id: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > If perhaps the sumbitter doesn't understand the error of overclocking: > > You just purchased a 1979 Ford Pinto station wagon. However, you are upset > after driving it for a while that it won't go above 65 MPH. Feeling smart, > you go and purchase soe rocket fuel. You pour it in your gas tank, and all > seems well until hit a steep hill, at which time the engine explodes. > > This is not the fault of: Ford, the card dealer where you bought the car, or > the hill itself. Oh, come on now. Nobody is looking to find fault with anybody else. None of us need to reach for our attorneys and insurance adjusters. Have you never heard of the fine old American tradition of hot-rodding? Putting better quality fuel into your car is analogous to putting better quality software into your computer. Your warranty is void, you're responsible for fixing the problems yourself, but there's nothing wrong with asking your friends for their advice and experiences. If your friends tell you, "Take it to the dealer service department", well, maybe you asked the wrong friends. Some people will buy the fastest regular-production car on the market, and some will hot-rod a twenty-year-old Ford. There's room for diversity. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 10 12:52:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA22575 for freebsd-current-outgoing; Fri, 10 Apr 1998 12:52:39 -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 MAA22543 for ; Fri, 10 Apr 1998 12:52:36 -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 MAA00847; Fri, 10 Apr 1998 12:47:13 -0700 (PDT) Message-Id: <199804101947.MAA00847@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Stephen Roome cc: Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: ps segfaults since I overclocked. and worries. In-reply-to: Your message of "Fri, 10 Apr 1998 16:11:32 BST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 10 Apr 1998 12:47:12 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > My machine is fine at normal speeds, without the overclocking, I already > mentioned this. So what's your problem? It works at "normal speeds", and fails when you overclock. Doesn't this tell you something? > I was wondering if there was a problem with FreeBSD on computers with non > 66MHz bus speeds. No. > There is some mention of this in /sys/pci/ide_pci.c, I This is a timing issue related to conformance with the various IDE standards. > am 100% certain that the hardware I have is performing fine at these > speeds, You have an observed aberration, yet you are "100% certain"? Who are you kidding? > If there are hardcoded limits that prevent these people from using FreeBSD > then that is a problem. Isn't it ? There aren't, so your argument is baseless. > Does the following mean that some new PC's are not going to work properly? > And that FreeBSD just won't support them ? No. It means that you are expected to run the parts involved (the VIA571 and Intel PIIXn) at their rated speeds. If you correctly configure your system, this is what will happen. -- \\ 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 Apr 10 14:29:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA18362 for freebsd-current-outgoing; Fri, 10 Apr 1998 14:29:00 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.mishkei.org.il (host3-64.mishkei.org.il [62.0.64.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA18207 for ; Fri, 10 Apr 1998 14:28:07 -0700 (PDT) (envelope-from lickyou@ein-hashofet.co.il) Received: from box.from.hell (host40-68.mishkei.org.il [62.0.68.40]) by mail.mishkei.org.il (8.8.5/8.8.5) with SMTP id AAA17623; Sat, 11 Apr 1998 00:24:54 +0300 Date: Sat, 11 Apr 1998 00:25:33 +0000 (GMT) From: Gilad Rom X-Sender: lickyou@box.from.hell To: Kevin Day cc: "Jordan K. Hubbard" , steve@visint.co.uk, phk@critter.freebsd.dk, current@FreeBSD.ORG Subject: Re: ps segfaults since I overclocked. and worries. In-Reply-To: <199804101809.NAA29718@home.dragondata.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 10 Apr 1998, Kevin Day wrote: > > > I'll shut up now, but if FreeBSD isn't going to be supporting hardware > > > that will be becoming standard soon then I'm slightly worried, I'd have > > > thought current- was the testing ground for stuff such as this > > > > Certainly, though clocking pre-standard hardware up to the standard > > and testing that would only constitute poor testing methodology. > > Before becoming even slightly worried, I'd first want to see test > > failures on hardware where all components are rated for the conditions > > of the test. Considering the number of manufacturers involved just in > > getting all the components on a motherboard to work properly together > > at some target clock speed, it's often surprising to consider that the > > whole mess works at all. > > > > Jordan > > If perhaps the sumbitter doesn't understand the error of overclocking: > > You just purchased a 1979 Ford Pinto station wagon. However, you are upset > after driving it for a while that it won't go above 65 MPH. Feeling smart, > you go and purchase soe rocket fuel. You pour it in your gas tank, and all > seems well until hit a steep hill, at which time the engine explodes. > > This is not the fault of: Ford, the card dealer where you bought the car, or > the hill itself. > > Likewise, Overclocking your processor and having things fail is not the > fault of: Intel, your board manufacturer, or FreeBSD. > > > Kevin > Well, to the best of my knowledge, the p166 and p200 were almost identical except the fact that intel test these prior to shipment, to make sure what processor can achieve what clock speed without burning. I think overclocking is a 99% fail-proof way to achieve better performance from your CPU(To a limited extent, ofcourse) without paying more money for something which is about the same. The comparison to an old car being raced is not applicable here, as processors at that level are Identical. Please correct me if Im wrong, Thanks :) Gilad. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 10 14:40:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA20419 for freebsd-current-outgoing; Fri, 10 Apr 1998 14:40:51 -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 OAA20414 for ; Fri, 10 Apr 1998 14:40:49 -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 OAA01260; Fri, 10 Apr 1998 14:38:05 -0700 (PDT) Message-Id: <199804102138.OAA01260@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Gilad Rom cc: current@FreeBSD.ORG Subject: Re: ps segfaults since I overclocked. and worries. In-reply-to: Your message of "Sat, 11 Apr 1998 00:25:33 -0000." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 10 Apr 1998 14:38:05 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Well, to the best of my knowledge, the p166 and p200 were almost > identical except the fact that intel test these prior to shipment, to make > sure what processor can achieve what clock speed without burning. > I think overclocking is a 99% fail-proof way to achieve better performance > from your CPU(To a limited extent, ofcourse) without paying more money > for something which is about the same. The comparison to an old car being > raced is not applicable here, as processors at that level are Identical. > Please correct me if Im wrong, Thanks :) You're wrong. There are a limited number of cases where the situation you describe is valid. The typical error is to assume that this is universal, which is completely fallacious. Exceeding the rated specification of electronic components exposes you to the risk of functional or catastrophic failure. By doing so, you *must* accept sole responsibility for your situation. -- \\ 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 Apr 10 14:44:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA21154 for freebsd-current-outgoing; Fri, 10 Apr 1998 14:44:38 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from biggusdiskus.flyingfox.com (biggusdiskus.flyingfox.com [205.162.1.28]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA21149 for ; Fri, 10 Apr 1998 14:44:36 -0700 (PDT) (envelope-from jas@flyingfox.com) Received: (from jas@localhost) by biggusdiskus.flyingfox.com (8.8.5/8.8.5) id OAA06116; Fri, 10 Apr 1998 14:43:57 -0700 (PDT) Date: Fri, 10 Apr 1998 14:43:57 -0700 (PDT) From: Jim Shankland Message-Id: <199804102143.OAA06116@biggusdiskus.flyingfox.com> To: lickyou@ein-hashofet.co.il, toasty@home.dragondata.com Subject: Re: ps segfaults since I overclocked. and worries. Cc: current@FreeBSD.ORG, jkh@time.cdrom.com, phk@critter.freebsd.dk, steve@visint.co.uk Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Well, to the best of my knowledge, the p166 and p200 were almost > identical except the fact that intel test these prior to shipment, to > make sure what processor can achieve what clock speed without burning. > I think overclocking is a 99% fail-proof way to achieve better > performance from your CPU(To a limited extent, ofcourse) without > paying more money for something which is about the same. Let me make sure I got this right. 1. Intel makes chip. 2. Intel tests chip at 200 MHz; it fails. 3. Intel tests chip at 166 MHz; it works. 4. Intel sells chip as a P166. 5. Customer buys this P166. 6. Customer overclocks chip to 200 MHz. 7. Customer experiences failures. 8. Customer gripes to FreeBSD mailing lists about "inherent limits" in FreeBSD. Jim Shankland Flying Fox Computer Systems, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 10 15:10:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA24661 for freebsd-current-outgoing; Fri, 10 Apr 1998 15:10:36 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from horst.bfd.com (horst.bfd.com [204.160.242.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA24630 for ; Fri, 10 Apr 1998 15:10:32 -0700 (PDT) (envelope-from ejs@bfd.com) Received: from harlie.bfd.com (bastion.bfd.com [204.160.242.14]) by horst.bfd.com (8.8.8/8.8.8) with SMTP id WAA28863; Fri, 10 Apr 1998 22:00:56 GMT (envelope-from ejs@bfd.com) Date: Fri, 10 Apr 1998 15:00:56 -0700 (PDT) From: "Eric J. Schwertfeger" To: Mike Smith cc: Gilad Rom , current@FreeBSD.ORG Subject: Re: ps segfaults since I overclocked. and worries. In-Reply-To: <199804102138.OAA01260@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 On Fri, 10 Apr 1998, Mike Smith wrote: > > > > Well, to the best of my knowledge, the p166 and p200 were almost > > identical except the fact that intel test these prior to shipment, to make > > sure what processor can achieve what clock speed without burning. > > I think overclocking is a 99% fail-proof way to achieve better performance > > from your CPU(To a limited extent, ofcourse) without paying more money > > for something which is about the same. The comparison to an old car being > > raced is not applicable here, as processors at that level are Identical. > > Please correct me if Im wrong, Thanks :) > > You're wrong. > > There are a limited number of cases where the situation you describe is > valid. The typical error is to assume that this is universal, which is > completely fallacious. > > Exceeding the rated specification of electronic components exposes you > to the risk of functional or catastrophic failure. By doing so, you > *must* accept sole responsibility for your situation. Even as a rabbid overclocker, I still have to agree with Mike. The later P166/MMX's are happily overclockable, except that Intel isn't bonding all the pins, and it's still not a sure thing. The non-MMX is not so happily overclockable. Where you get into real trouble when overclocking the external clock rather than the multiplier is on the PCI bus, including the IDE interfaces. In fact, UDMA (actually loading the drivers, or enabling it in the kernel) and an external clock of 83.3Mhz is VERY BAD mojo. I've never seen that combo work, but I haven't tried much. Basically, if it works when not overclocked, but not when overclocked, I never blame the OS. Sure, my wife's P166 will boot DOS at 291Mhz, but just because it won't any real OS faster than 200 doesn't mean that DOS is a good OS and all other OS have bugs. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 10 15:46:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA00660 for freebsd-current-outgoing; Fri, 10 Apr 1998 15:46:29 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bookcase.com (root@notes.bookcase.com [207.22.115.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA00559 for ; Fri, 10 Apr 1998 15:46:11 -0700 (PDT) (envelope-from chadf@bookcase.com) Received: from localhost (chadf@localhost) by bookcase.com (8.8.8/8.8.8) with SMTP id SAA02660 for ; Fri, 10 Apr 1998 18:45:46 -0400 (EDT) (envelope-from chadf@bookcase.com) Date: Fri, 10 Apr 1998 18:45:46 -0400 (EDT) From: "Chad M. Fraleigh" X-Sender: chadf@notes Reply-To: "Chad M. Fraleigh" To: current@FreeBSD.ORG Subject: Misspelling in lib/libutil/login_cap.3 [w/ patch] 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 "authorisation" should be "authorization". -Chad *** lib/libutil/login_cap.3 Wed Nov 5 19:37:54 1997 --- lib/libutil/login_cap.3.new Fri Apr 10 18:40:55 1998 *************** *** 161,167 **** .Ar lc_style field is set by the .Fn login_getstyle ! function to the authorisation style according to the requirements of the program handling a login itself. .Pp As noted above, the --- 161,167 ---- .Ar lc_style field is set by the .Fn login_getstyle ! function to the authorization style according to the requirements of the program handling a login itself. .Pp As noted above, the *************** *** 352,362 **** for more information on boolean flags), and returns 1 if the tag is found. .It Fn login_getstyle ! This function is used by the login authorisation system to determine the style of login available in a particular case. The function accepts three parameters, the login_cap entry itself and ! two optional parameters, and authorisation type 'auth' and 'style', and ! applies these to determine the authorisation style that best suites these rules. .Bl -bullet -indent offset .It --- 352,362 ---- for more information on boolean flags), and returns 1 if the tag is found. .It Fn login_getstyle ! This function is used by the login authorization system to determine the style of login available in a particular case. The function accepts three parameters, the login_cap entry itself and ! two optional parameters, and authorization type 'auth' and 'style', and ! applies these to determine the authorization style that best suites these rules. .Bl -bullet -indent offset .It *************** *** 364,383 **** "auth-" in the capability record. If not present, then look for the default default tag "auth=". .It ! If no valid authorisation list was found from the previous step, then ! default to "passwd" as the authorisation list. .It ! If 'style' is not NULL or empty, look for it in the list of authorisation methods found from the pprevious step. If 'style' is NULL or an empty string, then default to "passwd" ! authorisation. .It ! If 'style' is found in the chosen list of authorisation methods, then return that, otherwise return NULL. .El .Pp This scheme allows the administrator to determine the types of ! authorisation methods accepted by the system, depending on the means by which the access occurs. For example, the administrator may require skey or kerberos as the authentication method used for access to the system via the --- 364,383 ---- "auth-" in the capability record. If not present, then look for the default default tag "auth=". .It ! If no valid authorization list was found from the previous step, then ! default to "passwd" as the authorization list. .It ! If 'style' is not NULL or empty, look for it in the list of authorization methods found from the pprevious step. If 'style' is NULL or an empty string, then default to "passwd" ! authorization. .It ! If 'style' is found in the chosen list of authorization methods, then return that, otherwise return NULL. .El .Pp This scheme allows the administrator to determine the types of ! authorization methods accepted by the system, depending on the means by which the access occurs. For example, the administrator may require skey or kerberos as the authentication method used for access to the system via the To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 10 15:59:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA02889 for freebsd-current-outgoing; Fri, 10 Apr 1998 15:59:07 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cimlogic.com.au ([203.36.2.25]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA02878 for ; Fri, 10 Apr 1998 15:59:03 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.5/8.8.7) id IAA07810; Sat, 11 Apr 1998 08:56:48 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199804102256.IAA07810@cimlogic.com.au> Subject: Re: Misspelling in lib/libutil/login_cap.3 [w/ patch] In-Reply-To: from "Chad M. Fraleigh" at "Apr 10, 98 06:45:46 pm" To: chadf@bookcase.com Date: Sat, 11 Apr 1998 08:56:48 +1000 (EST) Cc: current@FreeBSD.ORG 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 Chad M. Fraleigh wrote: > > "authorisation" should be "authorization". In my _*English*_ dictionary, either is acceptable. -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org 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 Fri Apr 10 16:05:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA04867 for freebsd-current-outgoing; Fri, 10 Apr 1998 16:05:51 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bookcase.com (root@notes.bookcase.com [207.22.115.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA04849 for ; Fri, 10 Apr 1998 16:05:43 -0700 (PDT) (envelope-from chadf@bookcase.com) Received: from localhost (chadf@localhost) by bookcase.com (8.8.8/8.8.8) with SMTP id TAA03039 for ; Fri, 10 Apr 1998 19:05:32 -0400 (EDT) (envelope-from chadf@bookcase.com) Date: Fri, 10 Apr 1998 19:05:32 -0400 (EDT) From: "Chad M. Fraleigh" X-Sender: chadf@notes To: current@FreeBSD.ORG Subject: Re: Misspelling in lib/libutil/login_cap.3 [w/ patch] In-Reply-To: <199804102256.IAA07810@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 Sat, 11 Apr 1998, John Birrell wrote: > Chad M. Fraleigh wrote: > > > > "authorisation" should be "authorization". > > In my _*English*_ dictionary, either is acceptable. Then share/dict/web2 (or web2a) is lacking since authorisation is not in there but authorization is. (That's the first thing I checked before doing the patch). -Chad To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 10 16:12:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA06328 for freebsd-current-outgoing; Fri, 10 Apr 1998 16:12:06 -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 QAA06262 for ; Fri, 10 Apr 1998 16:11:55 -0700 (PDT) (envelope-from grog@lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.8.7/8.8.5) with ESMTP id IAA19673; Sat, 11 Apr 1998 08:41:44 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.8.8/8.8.7) id IAA08552; Sat, 11 Apr 1998 08:41:43 +0930 (CST) (envelope-from grog) Message-ID: <19980411084143.00316@freebie.lemis.com> Date: Sat, 11 Apr 1998 08:41:43 +0930 From: Greg Lehey To: "Chad M. Fraleigh" , current@FreeBSD.ORG Subject: Re: Misspelling in lib/libutil/login_cap.3 [w/ patch] References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: ; from Chad M. Fraleigh on Fri, Apr 10, 1998 at 06:45:46PM -0400 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 10 April 1998 at 18:45:46 -0400, Chad M. Fraleigh wrote: > > "authorisation" should be "authorization". Why? My dictionary allows both spellings. In any case, the appropriate thing to do here is to send in a PR, not diffs to the whole group. Greg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 10 16:13:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA06722 for freebsd-current-outgoing; Fri, 10 Apr 1998 16:13:06 -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 QAA06658 for ; Fri, 10 Apr 1998 16:12:55 -0700 (PDT) (envelope-from grog@lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.8.7/8.8.5) with ESMTP id IAA19681; Sat, 11 Apr 1998 08:42:47 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.8.8/8.8.7) id IAA08568; Sat, 11 Apr 1998 08:42:46 +0930 (CST) (envelope-from grog) Message-ID: <19980411084246.42966@freebie.lemis.com> Date: Sat, 11 Apr 1998 08:42:46 +0930 From: Greg Lehey To: "Chad M. Fraleigh" , current@FreeBSD.ORG Subject: Re: Misspelling in lib/libutil/login_cap.3 [w/ patch] References: <199804102256.IAA07810@cimlogic.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: ; from Chad M. Fraleigh on Fri, Apr 10, 1998 at 07:05:32PM -0400 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 10 April 1998 at 19:05:32 -0400, Chad M. Fraleigh wrote: > > On Sat, 11 Apr 1998, John Birrell wrote: > >> Chad M. Fraleigh wrote: >>> >>> "authorisation" should be "authorization". >> >> In my _*English*_ dictionary, either is acceptable. > > Then share/dict/web2 (or web2a) is lacking since authorisation is > not in there but authorization is. (That's the first thing I checked > before doing the patch). Don't rely on web2 to be complete. I'm sure that there are many errors there. Greg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 10 17:08:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA19342 for freebsd-current-outgoing; Fri, 10 Apr 1998 17:08:11 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.dyn.ml.org (garbanzo@haiti-103.ppp.hooked.net [206.169.228.103]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA19235 for ; Fri, 10 Apr 1998 17:07:47 -0700 (PDT) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost) by zippy.dyn.ml.org (8.8.8/8.8.7) with SMTP id RAA00757; Fri, 10 Apr 1998 17:06:47 -0700 (PDT) X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs Date: Fri, 10 Apr 1998 17:06:46 -0700 (PDT) From: Alex X-Sender: garbanzo@zippy.dyn.ml.org To: John Birrell cc: chadf@bookcase.com, current@FreeBSD.ORG Subject: Re: Misspelling in lib/libutil/login_cap.3 [w/ patch] In-Reply-To: <199804102256.IAA07810@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 Sat, 11 Apr 1998, John Birrell wrote: > Chad M. Fraleigh wrote: > > > > "authorisation" should be "authorization". > > In my _*English*_ dictionary, either is acceptable. I checked my Webster's Seventh New Collegiate Dictionary (c. 1971), authorisation wasn't in there, however authorize and authorization were. If ya'll want to be Britons, fine. Hell, I wouldn't mind seeing FreeBSD distributed solely in Latin ;) - alex "We are upping our standards ... so up yours." - Pat Paulsen for US of A Prez, 1988. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 10 17:28:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA24129 for freebsd-current-outgoing; Fri, 10 Apr 1998 17:28:53 -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 RAA24083 for ; Fri, 10 Apr 1998 17:28:50 -0700 (PDT) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id TAA04418; Fri, 10 Apr 1998 19:26:39 -0500 (EST) (envelope-from toor) From: "John S. Dyson" Message-Id: <199804110026.TAA04418@dyson.iquest.net> Subject: Re: ps segfaults since I overclocked. and worries. In-Reply-To: from Gilad Rom at "Apr 11, 98 00:25:33 am" To: lickyou@ein-hashofet.co.il (Gilad Rom) Date: Fri, 10 Apr 1998 19:26:39 -0500 (EST) Cc: toasty@home.dragondata.com, jkh@time.cdrom.com, steve@visint.co.uk, phk@critter.freebsd.dk, 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 > > > > > This is not the fault of: Ford, the card dealer where you bought the car, or > > the hill itself. > > > > Likewise, Overclocking your processor and having things fail is not the > > fault of: Intel, your board manufacturer, or FreeBSD. > > > > > My hand is broken after I hit it with a sledgehammer :-). There must be a problem with my hand or the sledgehammer :-). John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 10 17:30:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA24971 for freebsd-current-outgoing; Fri, 10 Apr 1998 17:30:41 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.dyn.ml.org (garbanzo@haiti-103.ppp.hooked.net [206.169.228.103]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA24921 for ; Fri, 10 Apr 1998 17:30:33 -0700 (PDT) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost) by zippy.dyn.ml.org (8.8.8/8.8.7) with SMTP id RAA00984 for ; Fri, 10 Apr 1998 17:30:31 -0700 (PDT) X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs Date: Fri, 10 Apr 1998 17:30:30 -0700 (PDT) From: Alex X-Sender: garbanzo@zippy.dyn.ml.org To: current Subject: Any plans to upgrade bind? 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 to a more -current topic. Has anyone planned to upgrade bind to 4.9.7 or even better to the 8.x version? Either way, you'd fix some more security holes (as reported to BugTraq), although 4.9.7 has some reported symlink bugs.. - alex "We are upping our standards ... so up yours." - Pat Paulsen for US of A Prez, 1988. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 10 17:37:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA27274 for freebsd-current-outgoing; Fri, 10 Apr 1998 17:37:09 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from oldnews.quick.net (donegan@oldnews.quick.net [207.212.170.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA27265 for ; Fri, 10 Apr 1998 17:37:02 -0700 (PDT) (envelope-from donegan@oldnews.quick.net) Received: (from donegan@localhost) by oldnews.quick.net (8.8.5/8.6.9) id RAA26546; Fri, 10 Apr 1998 17:36:47 -0700 (PDT) Date: Fri, 10 Apr 1998 17:36:47 -0700 (PDT) From: "Steven P. Donegan" To: Alex cc: current Subject: Re: Any plans to upgrade bind? 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, 10 Apr 1998, Alex wrote: > On to a more -current topic. Has anyone planned to upgrade bind to 4.9.7 > or even better to the 8.x version? Either way, you'd fix some more > security holes (as reported to BugTraq), although 4.9.7 has some reported > symlink bugs.. > > - alex > > "We are upping our standards ... so up yours." > - Pat Paulsen for US of A Prez, 1988. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Yesterday's bind - the one with the bug fixes for the most recent CERT/CIAC panic-o-gram :-) Compiles just fine under current SMP with one very minor tweak to the files. I haven't tried it out yet - too darn busy as usual. So, I'd see this as a simple test it and include it if the group is happy with it thing... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 10 17:43:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA28404 for freebsd-current-outgoing; Fri, 10 Apr 1998 17:43:02 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp02.primenet.com (smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA28391 for ; Fri, 10 Apr 1998 17:42:56 -0700 (PDT) (envelope-from tlambert@usr08.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id RAA10261; Fri, 10 Apr 1998 17:42:50 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp02.primenet.com, id smtpd010209; Fri Apr 10 17:42:41 1998 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id RAA23170; Fri, 10 Apr 1998 17:42:33 -0700 (MST) From: Terry Lambert Message-Id: <199804110042.RAA23170@usr08.primenet.com> Subject: Re: Misspelling in lib/libutil/login_cap.3 [w/ patch] To: grog@lemis.com (Greg Lehey) Date: Sat, 11 Apr 1998 00:42:33 +0000 (GMT) Cc: chadf@bookcase.com, current@FreeBSD.ORG In-Reply-To: <19980411084246.42966@freebie.lemis.com> from "Greg Lehey" at Apr 11, 98 08:42:46 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 > Don't rely on web2 to be complete. I'm sure that there are many > errors there. Patches? ... }B-). 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 Apr 10 17:49:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA29169 for freebsd-current-outgoing; Fri, 10 Apr 1998 17:49:24 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.westbend.net (ns1.westbend.net [207.217.224.194]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA29161 for ; Fri, 10 Apr 1998 17:49:17 -0700 (PDT) (envelope-from hetzels@westbend.net) Received: from admin (admin.westbend.net [207.217.224.195]) by mail.westbend.net (8.8.8/8.8.8) with SMTP id TAA00761 for ; Fri, 10 Apr 1998 19:48:54 -0500 (CDT) (envelope-from hetzels@westbend.net) Message-ID: <017501bd64e3$f11ff880$c3e0d9cf@admin.westbend.net> From: "Scot W. Hetzel" To: Subject: Re: ps segfaults since I overclocked. and worries. Date: Fri, 10 Apr 1998 19:51:19 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----Original Message----- From: John S. Dyson >> >My hand is broken after I hit it with a sledgehammer :-). There must be >a problem with my hand or the sledgehammer :-). > There must be a problem with the sledgehammer, as my hand worked properly before I hit it. :-). Now can we end this thread? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 10 18:47:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA11644 for freebsd-current-outgoing; Fri, 10 Apr 1998 18:47:43 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA11591 for ; Fri, 10 Apr 1998 18:47:39 -0700 (PDT) (envelope-from michaelh@cet.co.jp) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.8/CET-v2.2) with SMTP id BAA03417; Sat, 11 Apr 1998 01:46:28 GMT Date: Sat, 11 Apr 1998 10:46:28 +0900 (JST) From: Michael Hancock To: Alex cc: current Subject: Re: Any plans to upgrade bind? 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, 10 Apr 1998, Alex wrote: > On to a more -current topic. Has anyone planned to upgrade bind to 4.9.7 > or even better to the 8.x version? Either way, you'd fix some more > security holes (as reported to BugTraq), although 4.9.7 has some reported > symlink bugs.. It will be 4.9.7 after it finishes the open test cycle. You can run bind8 out of /usr/local/etc/rc.d, it's in the ports collection and easy enough to setup. Regards, Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 10 19:45:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA21451 for freebsd-current-outgoing; Fri, 10 Apr 1998 19:45:44 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from hwcn.org (ac199@james.hwcn.org [199.212.94.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA21445 for ; Fri, 10 Apr 1998 19:45:38 -0700 (PDT) (envelope-from hoek@hwcn.org) Received: from localhost (ac199@localhost) by hwcn.org (8.8.8/8.8.8) with SMTP id WAA01359; Fri, 10 Apr 1998 22:40:45 -0400 (EDT) Date: Fri, 10 Apr 1998 22:40:44 -0400 (EDT) From: Tim Vanderhoek To: Greg Lehey cc: "Chad M. Fraleigh" , current@FreeBSD.ORG Subject: Re: Misspelling in lib/libutil/login_cap.3 [w/ patch] In-Reply-To: <19980411084143.00316@freebie.lemis.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 Sat, 11 Apr 1998, Greg Lehey wrote: > > "authorisation" should be "authorization". > > Why? My dictionary allows both spellings. So? That doesn't mean we need to use both. > In any case, the appropriate thing to do here is to send in a PR, not > diffs to the whole group. [Yes. After you reply stating some kind of polar opposite opinion, I will refrain from any replies to -current] -- Outnumbered? Maybe. Outspoken? Never! tIM...HOEk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 10 21:13:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA03594 for freebsd-current-outgoing; Fri, 10 Apr 1998 21:13:39 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA03562 for ; Fri, 10 Apr 1998 21:13:37 -0700 (PDT) (envelope-from jfieber@indiana.edu) Received: from localhost (jfieber@localhost) by fallout.campusview.indiana.edu (8.8.8/8.8.7) with SMTP id XAA15173; Fri, 10 Apr 1998 23:12:24 -0500 (EST) Date: Fri, 10 Apr 1998 23:12:23 -0500 (EST) From: John Fieber To: John Birrell cc: chadf@bookcase.com, current@FreeBSD.ORG Subject: Re: Misspelling in lib/libutil/login_cap.3 [w/ patch] In-Reply-To: <199804102256.IAA07810@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 Sat, 11 Apr 1998, John Birrell wrote: > Chad M. Fraleigh wrote: > > > > "authorisation" should be "authorization". > > In my _*English*_ dictionary, either is acceptable. Citation please? Not found in the Oxford English Dictionary (2nd ed), nor any of the American dictionaries I have on hand (American Heritage, Webster). It may be acceptable somewhere, but I dare say that the "z" version is much more widely accepted. -john To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 10 21:14:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA04168 for freebsd-current-outgoing; Fri, 10 Apr 1998 21:14:51 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from andrsn.stanford.edu (andrsn@andrsn.Stanford.EDU [36.33.0.163]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA04163 for ; Fri, 10 Apr 1998 21:14:49 -0700 (PDT) (envelope-from andrsn@andrsn.stanford.edu) Received: from localhost (andrsn@localhost.stanford.edu [127.0.0.1]) by andrsn.stanford.edu (8.8.8/8.6.12) with SMTP id VAA17096 for ; Fri, 10 Apr 1998 21:13:10 -0700 (PDT) Date: Fri, 10 Apr 1998 21:13:09 -0700 (PDT) From: Annelise Anderson Reply-To: Annelise Anderson To: freebsd-current@FreeBSD.ORG Subject: Ports Tree 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 Yesterday (about 36 hours ago) I downloaded the -current sources and did a make world and recompiled the kernel and everything is working just fine. I didn't update the ports collection, though. It seems to me from reading the example files that a supfile for -current ports is the same as it is for -stable. This is what I have been using for -stable (carriage return added): ports-all release=cvs host=cvsup.freebsd.org base=/usr hostbase=/home prefix=/usr delete old use-rel-suffix tag=. This, then, is also the file to use for -current? Thanks-- Annelise To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 10 21:19:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA05355 for freebsd-current-outgoing; Fri, 10 Apr 1998 21:19:08 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freebsd.scds.com (jseger.shore.net [204.167.102.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA05344 for ; Fri, 10 Apr 1998 21:19:04 -0700 (PDT) (envelope-from jseger@freebsd.scds.com) Received: (from jseger@localhost) by freebsd.scds.com (8.8.8/8.8.5) id AAA02150; Sat, 11 Apr 1998 00:23:50 -0400 (EDT) Date: Sat, 11 Apr 1998 00:23:50 -0400 (EDT) Message-Id: <199804110423.AAA02150@freebsd.scds.com> From: "Justin M. Seger" To: andrsn@andrsn.stanford.edu CC: freebsd-current@FreeBSD.ORG In-reply-to: (message from Annelise Anderson on Fri, 10 Apr 1998 21:13:09 -0700 (PDT)) Subject: Re: Ports Tree References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ports-all release=cvs host=cvsup.freebsd.org base=/usr hostbase=/home prefix=/usr delete old use-rel-suffix tag=. This, then, is also the file to use for -current? Yep, this'll work. TTYL, -Justin Seger- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 10 21:19:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA05702 for freebsd-current-outgoing; Fri, 10 Apr 1998 21:19:40 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cimlogic.com.au ([203.36.2.25]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA05635 for ; Fri, 10 Apr 1998 21:19:35 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.5/8.8.7) id OAA08739; Sat, 11 Apr 1998 14:18:23 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199804110418.OAA08739@cimlogic.com.au> Subject: Re: Misspelling in lib/libutil/login_cap.3 [w/ patch] In-Reply-To: from John Fieber at "Apr 10, 98 11:12:23 pm" To: jfieber@indiana.edu (John Fieber) Date: Sat, 11 Apr 1998 14:18:23 +1000 (EST) Cc: jb@cimlogic.com.au, chadf@bookcase.com, current@FreeBSD.ORG 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 John Fieber wrote: > On Sat, 11 Apr 1998, John Birrell wrote: > > > Chad M. Fraleigh wrote: > > > > > > "authorisation" should be "authorization". > > > > In my _*English*_ dictionary, either is acceptable. > > Citation please? The Concise Oxford Dictionary 5th edition. Printed in Great Britain. > Not found in the Oxford English Dictionary (2nd ed), nor any of Check if the 's' and 'z' versions are under the _same_ entry. They are in mine. > the American dictionaries I have on hand (American Heritage, > Webster). > > It may be acceptable somewhere, but I dare say that the "z" > version is much more widely accepted. Sorry, at school I was taught English, not American. -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org 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 Fri Apr 10 21:23:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA06841 for freebsd-current-outgoing; Fri, 10 Apr 1998 21:23:22 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from arh0300.urh.uiuc.edu (arh0300.urh.uiuc.edu [130.126.72.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA06834 for ; Fri, 10 Apr 1998 21:23:17 -0700 (PDT) (envelope-from dannyman@arh0300.urh.uiuc.edu) Received: (from dannyman@localhost) by arh0300.urh.uiuc.edu (8.8.8/8.8.5) id XAA22929; Fri, 10 Apr 1998 23:23:12 -0500 (CDT) Message-ID: <19980410232312.04003@urh.uiuc.edu> Date: Fri, 10 Apr 1998 23:23:12 -0500 From: dannyman To: John Fieber , John Birrell Cc: chadf@bookcase.com, current@FreeBSD.ORG Subject: whose english is it anyway? Mail-Followup-To: John Fieber , John Birrell , chadf@bookcase.com, current@FreeBSD.ORG References: <199804102256.IAA07810@cimlogic.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: ; from John Fieber on Fri, Apr 10, 1998 at 11:12:23PM -0500 X-Loop: djhoward@uiuc.edu X-URL: http://www.uiuc.edu/ph/www/djhoward/ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Apr 10, 1998 at 11:12:23PM -0500, John Fieber wrote: > On Sat, 11 Apr 1998, John Birrell wrote: > > Chad M. Fraleigh wrote: > > > > > > "authorisation" should be "authorization". > > > > In my _*English*_ dictionary, either is acceptable. > > Citation please? 1 definition found >From WordNet (r) 1.6 [wn]: authorisation n : the act of authorizing [syn: {authorization}, {empowerment}] > It may be acceptable somewhere, but I dare say that the "z" > version is much more widely accepted. After all, it's the American way; 2 definitions found >From Webster's Revised Unabridged Dictionary (1913) [web1913]: Authorization \Au`thor*i*za"tion\, n. [Cf. F. autorisation.] The act of giving authority or legal power; establishment by authority; sanction or warrant. The authorization of laws. --Motley. A special authorization from the chief. --Merivale. >From WordNet (r) 1.6 [wn]: authorization n 1: a document giving an official instruction or command [syn: {mandate}] 2: a grant of authority to the executive branch of government to spend money for specified purposes; "authority for the program was renewed several times" [syn: {authority}] 3: a power delegated from one person to another; "deputies are given the power to make arrests" [syn: {authority}] 4: the act of authorizing [syn: {authorisation}, {empowerment}] -- // dannyman yori aiokomete || Our Honored Symbol deserves \\/ http://www.dannyland.org/~dannyman/ || an Honorable Retirement (UIUC) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 10 21:29:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA07901 for freebsd-current-outgoing; Fri, 10 Apr 1998 21:29:06 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA07893 for ; Fri, 10 Apr 1998 21:29:03 -0700 (PDT) (envelope-from jfieber@indiana.edu) Received: from localhost (jfieber@localhost) by fallout.campusview.indiana.edu (8.8.8/8.8.7) with SMTP id XAA15237; Fri, 10 Apr 1998 23:28:30 -0500 (EST) Date: Fri, 10 Apr 1998 23:28:30 -0500 (EST) From: John Fieber Reply-To: John Fieber To: John Birrell cc: chadf@bookcase.com, current@FreeBSD.ORG Subject: Re: Misspelling in lib/libutil/login_cap.3 [w/ patch] In-Reply-To: <199804110418.OAA08739@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 Sat, 11 Apr 1998, John Birrell wrote: > The Concise Oxford Dictionary 5th edition. Printed in Great Britain. > > > Not found in the Oxford English Dictionary (2nd ed), nor any of > > Check if the 's' and 'z' versions are under the _same_ entry. > They are in mine. Sorry, nothing. A keyword search turned up an occurence or two in some random quotations (unrelated to the "authorization" entry), but those contain all sorts of whacky "unapproved" spellings so that means little. -john To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 10 21:31:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA08407 for freebsd-current-outgoing; Fri, 10 Apr 1998 21:31:06 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rf900.physics.usyd.edu.au (rf900.physics.usyd.edu.au [129.78.129.109]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA08398 for ; Fri, 10 Apr 1998 21:31:02 -0700 (PDT) (envelope-from dawes@rf900.physics.usyd.edu.au) Received: (from dawes@localhost) by rf900.physics.usyd.edu.au (8.8.5/8.8.2) id OAA21446; Sat, 11 Apr 1998 14:30:47 +1000 (EST) Message-ID: <19980411143046.35436@rf900.physics.usyd.edu.au> Date: Sat, 11 Apr 1998 14:30:46 +1000 From: David Dawes To: John Fieber Cc: current@FreeBSD.ORG Subject: Re: Misspelling in lib/libutil/login_cap.3 [w/ patch] References: <199804102256.IAA07810@cimlogic.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 In-Reply-To: ; from John Fieber on Fri, Apr 10, 1998 at 11:12:23PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Apr 10, 1998 at 11:12:23PM -0500, John Fieber wrote: >On Sat, 11 Apr 1998, John Birrell wrote: > >> Chad M. Fraleigh wrote: >> > >> > "authorisation" should be "authorization". >> >> In my _*English*_ dictionary, either is acceptable. > >Citation please? > >Not found in the Oxford English Dictionary (2nd ed), nor any of >the American dictionaries I have on hand (American Heritage, >Webster). I have a copy of "The Concise Oxford Dictionary", 6th ed (1976). It shows both forms, with the "z" version preferred. Also, "The Macquarie Dictionary", 1st ed, revised (1985), which is considered by many to be the reference for English as used in Australia shows both with the "s" version preferred. >It may be acceptable somewhere, but I dare say that the "z" >version is much more widely accepted. I tend to agree. I used to think that the "s" version was the real "English" form (consistent with traditional Unix 'spell -b'), but some time ago an Englishman who was somewhat pedantic about such things pointed out that this wasn't the case (referencing the Oxford English Dictionary). I've come to the conclusion that the "s" form is more common in Australian English than elsewhere, and it happens to be the form I use too. BTW, here's an excerpt from the spell(1) man page on Solaris 2.5: -b Check British spelling. Besides preferring "centre," "colour," "programme," "speciality," "travelled," and so forth, this option insists upon -ise in words like "standardise." and in the BUGS section: British spelling was done by an American. :-) David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 10 21:40:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA09263 for freebsd-current-outgoing; Fri, 10 Apr 1998 21:40:54 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA09257 for ; Fri, 10 Apr 1998 21:40:52 -0700 (PDT) (envelope-from jfieber@indiana.edu) Received: from localhost (jfieber@localhost) by fallout.campusview.indiana.edu (8.8.8/8.8.7) with SMTP id XAA15271; Fri, 10 Apr 1998 23:40:35 -0500 (EST) Date: Fri, 10 Apr 1998 23:40:35 -0500 (EST) From: John Fieber To: David Dawes cc: current@FreeBSD.ORG Subject: Re: Misspelling in lib/libutil/login_cap.3 [w/ patch] In-Reply-To: <19980411143046.35436@rf900.physics.usyd.edu.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 Sat, 11 Apr 1998, David Dawes wrote: > I have a copy of "The Concise Oxford Dictionary", 6th ed (1976). It > shows both forms, with the "z" version preferred. OED 2nd edition is 1989, suggesting that the "s" form may be out of fashion, but I would really expect that to be noted if it were the case rather than just omitting it. After all, word history is one of the greatest strengths of the OED. Puzzling.... -john To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 10 21:42:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA09740 for freebsd-current-outgoing; Fri, 10 Apr 1998 21:42: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 VAA09730 for ; Fri, 10 Apr 1998 21:42:34 -0700 (PDT) (envelope-from evanc@synapse.net) Received: (qmail 24422 invoked from network); 11 Apr 1998 04:42:34 -0000 Received: from cpu1970.adsl.bellglobal.com (HELO cello.synapse.net) (206.47.37.201) by conductor.synapse.net with SMTP; 11 Apr 1998 04:42:34 -0000 Message-ID: <00d501bd6504$3e926ce0$c9252fce@cello.synapse.net> From: "Evan Champion" To: "dannyman" , "John Fieber" , "John Birrell" Cc: , Subject: Re: whose english is it anyway? Date: Sat, 11 Apr 1998 00:42:33 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Interesting the sort of things that spark conversation here :-) Authorisation is the British (International) English spelling, authorization is the American English spelling. There are hundreds of words like it, for example centre vs. center, fibre vs. fiber, specialise vs. specialize... I could sit here all day writing out examples. As someone noted, technically either is quite correct. However, due to cultural issues you will likely get odd looks if you use American spellings in Britain and vice versa. Given that FreeBSD is largely an American project, consistent use of American spellings would seem to be the most appropriate solution (as much as I prefer British English :-) Evan -----Original Message----- From: dannyman To: John Fieber ; John Birrell Cc: chadf@bookcase.com ; current@FreeBSD.ORG Date: Saturday, April 11, 1998 12:26 AM Subject: whose english is it anyway? >On Fri, Apr 10, 1998 at 11:12:23PM -0500, John Fieber wrote: >> On Sat, 11 Apr 1998, John Birrell wrote: >> > Chad M. Fraleigh wrote: >> > > >> > > "authorisation" should be "authorization". >> > >> > In my _*English*_ dictionary, either is acceptable. >> >> Citation please? > >1 definition found > >From WordNet (r) 1.6 [wn]: > > authorisation > n : the act of authorizing [syn: {authorization}, {empowerment}] > >> It may be acceptable somewhere, but I dare say that the "z" >> version is much more widely accepted. > >After all, it's the American way; > >2 definitions found > >From Webster's Revised Unabridged Dictionary (1913) [web1913]: > > Authorization \Au`thor*i*za"tion\, n. [Cf. F. autorisation.] > The act of giving authority or legal power; establishment by > authority; sanction or warrant. > > The authorization of laws. --Motley. > > A special authorization from the chief. --Merivale. > >From WordNet (r) 1.6 [wn]: > > authorization > n 1: a document giving an official instruction or command [syn: {mandate}] > 2: a grant of authority to the executive branch of government > to spend money for specified purposes; "authority for the > program was renewed several times" [syn: {authority}] > 3: a power delegated from one person to another; "deputies are > given the power to make arrests" [syn: {authority}] > 4: the act of authorizing [syn: {authorisation}, {empowerment}] > >-- > // dannyman yori aiokomete || Our Honored Symbol deserves >\\/ http://www.dannyland.org/~dannyman/ || an Honorable Retirement (UIUC) > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 10 21:47:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA11686 for freebsd-current-outgoing; Fri, 10 Apr 1998 21:47:46 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from arh0300.urh.uiuc.edu (arh0300.urh.uiuc.edu [130.126.72.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA11678 for ; Fri, 10 Apr 1998 21:47:44 -0700 (PDT) (envelope-from dannyman@arh0300.urh.uiuc.edu) Received: (from dannyman@localhost) by arh0300.urh.uiuc.edu (8.8.8/8.8.5) id XAA11153; Fri, 10 Apr 1998 23:47:38 -0500 (CDT) Message-ID: <19980410234738.57402@urh.uiuc.edu> Date: Fri, 10 Apr 1998 23:47:38 -0500 From: dannyman To: Evan Champion , John Fieber , John Birrell Cc: chadf@bookcase.com, current@FreeBSD.ORG Subject: Re: whose english is it anyway? Mail-Followup-To: Evan Champion , John Fieber , John Birrell , chadf@bookcase.com, current@FreeBSD.ORG References: <00d501bd6504$3e926ce0$c9252fce@cello.synapse.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <00d501bd6504$3e926ce0$c9252fce@cello.synapse.net>; from Evan Champion on Sat, Apr 11, 1998 at 12:42:33AM -0400 X-Loop: djhoward@uiuc.edu X-URL: http://www.uiuc.edu/ph/www/djhoward/ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Apr 11, 1998 at 12:42:33AM -0400, Evan Champion wrote: > As someone noted, technically either is quite correct. However, due to > cultural issues you will likely get odd looks if you use American spellings > in Britain and vice versa. Given that FreeBSD is largely an American > project, consistent use of American spellings would seem to be the most > appropriate solution (as much as I prefer British English :-) I bet SGML could solve our troubles! :) Having concentrated in Linguistics, my inclination is to encourage use of whatever English is widely intelligible. Authorize or authorise to your heart's content, whichever side of the pond you prefer to live. :) -- // dannyman yori aiokomete || Our Honored Symbol deserves \\/ http://www.dannyland.org/~dannyman/ || an Honorable Retirement (UIUC) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 10 21:48:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA12014 for freebsd-current-outgoing; Fri, 10 Apr 1998 21:48:26 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from germanium.xtalwind.net (germanium.xtalwind.net [205.160.242.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA11940 for ; Fri, 10 Apr 1998 21:48:18 -0700 (PDT) (envelope-from jack@germanium.xtalwind.net) Received: from localhost (jack@localhost) by germanium.xtalwind.net (8.9.0.Beta3/8.9.0.Beta3) with SMTP id AAA14625; Sat, 11 Apr 1998 00:47:11 -0400 (EDT) Date: Sat, 11 Apr 1998 00:47:11 -0400 (EDT) From: jack To: John Fieber cc: John Birrell , chadf@bookcase.com, current@FreeBSD.ORG Subject: Re: Misspelling in lib/libutil/login_cap.3 [w/ patch] 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, 10 Apr 1998, John Fieber wrote: > On Sat, 11 Apr 1998, John Birrell wrote: > > > Chad M. Fraleigh wrote: > > > > > > "authorisation" should be "authorization". > > > > In my _*English*_ dictionary, either is acceptable. > > Citation please? > > Not found in the Oxford English Dictionary (2nd ed), nor any of > the American dictionaries I have on hand (American Heritage, > Webster). You're comparing apples to oranges, guys. The languages spoken, and written by the Americans and the British, while sharing a common origin, are not the same. No matter how you colo[u]r them. Were the British as litigious as the Americans they'd probably try to sue us under copyright or trademark laws for calling our language English. :) -------------------------------------------------------------------------- Jack O'Neill Systems Administrator / Systems Analyst jack@germanium.xtalwind.net Crystal Wind Communications, Inc. Finger jack@germanium.xtalwind.net for my PGP key. PGP Key fingerprint = F6 C4 E6 D4 2F 15 A7 67 FD 09 E9 3C 5F CC EB CD enriched, vcard, HTML messages > /dev/null -------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 11 00:57:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA03762 for freebsd-current-outgoing; Sat, 11 Apr 1998 00:57:17 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ix.netcom.com (sil-wa2-23.ix.netcom.com [206.214.137.55]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA03757 for ; Sat, 11 Apr 1998 00:57:12 -0700 (PDT) (envelope-from tomdean@ix.netcom.com) Received: (from tomdean@localhost) by ix.netcom.com (8.8.8/8.8.8) id AAA04637; Sat, 11 Apr 1998 00:56:46 -0700 (PDT) (envelope-from tomdean) Date: Sat, 11 Apr 1998 00:56:46 -0700 (PDT) Message-Id: <199804110756.AAA04637@ix.netcom.com> From: Thomas Dean To: current@FreeBSD.ORG Subject: Emacs E-Mail Slow Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have been using Emacs 19.34.1 for E-Mail and general editing. After processing about a hundred messages and being on line for an hour, or so, things get very slow. Getting mail from /var/mqueue/* takes much longer than at startup. It takes 20 to 30 seconds to sort a hundred headers. Editing in another frame appears normal. If I save RMAIL, delete the buffer, and, read mail, things return to normal. It has been suggested that emacs may have a memory leak. The map starts at about 35 entries and rises to 45 entries. I have this same problem over several versions of -current. All xterms seem normal. The process is not swapping, the disk is not being accessed. Emacs appears to have 6M of swap. At least if I exit and restart emacs, swap usage changes by 6M. But, the disk is not making any noise and the accessed led is not on. I have attached the output from dmesg and top. dmesg: ================================ FreeBSD 3.0-CURRENT #5: Thu Apr 9 08:42:07 PDT 1998 root@celebris:/usr/src/sys/compile/CELEBRIS-SMP Timecounter "i8254" frequency 1193182 Hz cost 2524 ns CPU: Pentium (586-class CPU) Origin = "GenuineIntel" Id = 0x525 Stepping=5 Features=0x3bf real memory = 33554432 (32768K bytes) avail memory = 30367744 (29656K bytes) FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 0, version: 0x00030010, at 0xfee00000 cpu1 (AP): apic id: 1, version: 0x00030010, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x000f0011, at 0xfec00000 Probing for devices on PCI bus 0: chip0: rev 0x11 on pci0.0.0 ncr0: rev 0x02 int a irq 11 on pci0.1.0 ncr0: waiting for scsi devices to settle scbus0 at ncr0 bus 0 sd0 at scbus0 target 0 lun 0 sd0: type 0 fixed SCSI 2 sd0: Direct-Access sd0: 10.0 MB/s (100 ns, offset 8) 1042MB (2134305 512 byte sectors) sd1 at scbus0 target 1 lun 0 sd1: type 0 fixed SCSI 2 sd1: Direct-Access sd1: 10.0 MB/s (100 ns, offset 8) 3090MB (6328861 512 byte sectors) sd2 at scbus0 target 2 lun 0 sd2: type 0 fixed SCSI 2 sd2: Direct-Access sd2: 10.0 MB/s (100 ns, offset 8) 1029MB (2109376 512 byte sectors) cd0 at scbus0 target 5 lun 0 cd0: type 5 removable SCSI 2 cd0: CD-ROM cd0: asynchronous. can't get the size chip1: rev 0x88 on pci0.2.0 vga0: rev 0x01 int a irq 9 on pci0.6.0 de0: rev 0x11 int a irq 10 on pci0.8.0 de0: DEC DE450-CA 21041 [10Mb/s] pass 1.1 de0: address 00:00:f8:02:76:db Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface psm0 at 0x60-0x64 irq 12 on motherboard psm0: model Generic PS/2 mouse, device ID 0 fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in fd0: 1.44MB 3.5in npx0 on motherboard npx0: INT 16 interface Intel Pentium F00F detected, installing workaround APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via pin 2 SMP: AP CPU #1 Launched! ================================ top shows: last pid: 4401; load averages: 0.12, 0.05, 0.01 00:19:12 38 processes: 1 running, 37 sleeping CPU states: 11.0% user, 0.0% nice, 15.1% system, 0.4% interrupt, 73.6% idle Mem: 13M Active, 2128K Inact, 6736K Wired, 1300K Cache, 3506K Buf, 6572K Free Swap: 227M Total, 24M Used, 204M Free, 10% Inuse PID USERNAME PRI NICE SIZE RES STATE C TIME WCPU CPU COMMAND 259 tomdean 2 0 716K 708K select 1 0:16 4.62% 4.62% xterm 4401 tomdean 28 0 816K 752K CPU1 1 0:01 2.26% 1.98% top 181 root 2 0 5568K 5212K select 0 14:41 1.56% 1.56% XF86_SVGA 302 tomdean 2 0 5252K 4868K select 0 11:12 0.57% 0.57% emacs 162 root 2 0 436K 300K select 0 8:18 0.00% 0.00% ppp 266 tomdean 2 0 620K 448K select 0 0:21 0.00% 0.00% twm 279 tomdean 18 0 272K 352K pause 1 0:19 0.00% 0.00% fetchmail /proc/302/map has 44 entries. ======================================================== If I exit emacs and restart it, top shows: last pid: 4533; load averages: 0.12, 0.09, 0.02 00:30:13 37 processes: 1 running, 36 sleeping CPU states: 1.0% user, 0.0% nice, 1.4% system, 0.4% interrupt, 97.3% idle Mem: 11M Active, 3344K Inact, 6752K Wired, 2544K Cache, 3498K Buf, 6020K Free Swap: 227M Total, 18M Used, 209M Free, 8% Inuse PID USERNAME PRI NICE SIZE RES STATE C TIME WCPU CPU COMMAND 4526 tomdean 2 0 3012K 3808K select 0 0:03 2.24% 2.10% emacs 181 root 2 0 5568K 5792K select 0 14:57 1.98% 1.98% XF86_SVGA 4530 tomdean 28 0 816K 772K CPU1 0 0:00 1.29% 0.95% top 266 tomdean 2 0 620K 660K select 0 0:22 0.04% 0.04% twm 259 tomdean 2 0 716K 900K select 0 0:20 0.04% 0.04% xterm /proc/4526/map has 34 entries. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 11 01:26:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA06103 for freebsd-current-outgoing; Sat, 11 Apr 1998 01:26:48 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mailer.tydfam.machida.tokyo.jp (ns.tydfam.machida.tokyo.jp [210.161.209.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA06097 for ; Sat, 11 Apr 1998 01:26:43 -0700 (PDT) (envelope-from ken@tydfam.machida.tokyo.jp) Received: from localhost (ns1.tydfam.machida.tokyo.jp [210.161.209.138]) by mailer.tydfam.machida.tokyo.jp (8.8.8/3.6W) with ESMTP id RAA16898 for ; Sat, 11 Apr 1998 17:00:53 +0900 (JST) To: current@FreeBSD.ORG Subject: Re: Misspelling in lib/libutil/login_cap.3 [w/ patch] In-Reply-To: Your message of "Sat, 11 Apr 1998 08:56:48 +1000 (EST)" <199804102256.IAA07810@cimlogic.com.au> References: <199804102256.IAA07810@cimlogic.com.au> X-Mailer: Mew version 1.93b1 on XEmacs 20.3 (Vatican City) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19980411170052R.ken@ns1.tydfam.machida.tokyo.jp> Date: Sat, 11 Apr 1998 17:00:52 +0900 From: Takeshi Yamada X-Dispatcher: imput version 971024 Lines: 10 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I learned one is Royal english and the other is colonial, and either is correct. From: John Birrell Subject: Re: Misspelling in lib/libutil/login_cap.3 [w/ patch] jb> Chad M. Fraleigh wrote: jb> > jb> > "authorisation" should be "authorization". jb> jb> In my _*English*_ dictionary, either is acceptable. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 11 01:28:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA06439 for freebsd-current-outgoing; Sat, 11 Apr 1998 01:28:52 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mailer.tydfam.machida.tokyo.jp (ns.tydfam.machida.tokyo.jp [210.161.209.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA06433 for ; Sat, 11 Apr 1998 01:28:49 -0700 (PDT) (envelope-from ken@tydfam.machida.tokyo.jp) Received: from localhost (ns1.tydfam.machida.tokyo.jp [210.161.209.138]) by mailer.tydfam.machida.tokyo.jp (8.8.8/3.6W) with ESMTP id RAA16902; Sat, 11 Apr 1998 17:02:22 +0900 (JST) To: chadf@bookcase.com Cc: current@FreeBSD.ORG Subject: Re: Misspelling in lib/libutil/login_cap.3 [w/ patch] Reply-To: ken@tydfam.machida.tokyo.jp In-Reply-To: Your message of "Fri, 10 Apr 1998 19:05:32 -0400 (EDT)" References: X-Mailer: Mew version 1.93b1 on XEmacs 20.3 (Vatican City) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19980411170222L.ken@ns1.tydfam.machida.tokyo.jp> Date: Sat, 11 Apr 1998 17:02:22 +0900 From: Takeshi Yamada X-Dispatcher: imput version 971024 Lines: 19 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Webstar dictionary is American..... From: "Chad M. Fraleigh" Subject: Re: Misspelling in lib/libutil/login_cap.3 [w/ patch] Date: Fri, 10 Apr 1998 19:05:32 -0400 (EDT) Message-ID: chadf> chadf> On Sat, 11 Apr 1998, John Birrell wrote: chadf> chadf> > Chad M. Fraleigh wrote: chadf> > > chadf> > > "authorisation" should be "authorization". chadf> > chadf> > In my _*English*_ dictionary, either is acceptable. chadf> chadf> Then share/dict/web2 (or web2a) is lacking since authorisation is chadf> not in there but authorization is. (That's the first thing I checked chadf> before doing the patch). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 11 05:11:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA25823 for freebsd-current-outgoing; Sat, 11 Apr 1998 05:11:32 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freebsd.scds.com (jseger.shore.net [204.167.102.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA25817 for ; Sat, 11 Apr 1998 05:11:28 -0700 (PDT) (envelope-from jseger@freebsd.scds.com) Received: (from jseger@localhost) by freebsd.scds.com (8.8.8/8.8.5) id IAA15366; Sat, 11 Apr 1998 08:16:09 -0400 (EDT) Date: Sat, 11 Apr 1998 08:16:09 -0400 (EDT) Message-Id: <199804111216.IAA15366@freebsd.scds.com> From: "Justin M. Seger" To: tomdean@ix.netcom.com CC: current@FreeBSD.ORG In-reply-to: <199804110756.AAA04637@ix.netcom.com> (message from Thomas Dean on Sat, 11 Apr 1998 00:56:46 -0700 (PDT)) Subject: Re: Emacs E-Mail Slow References: <199804110756.AAA04637@ix.netcom.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have been using Emacs 19.34.1 for E-Mail and general editing. After processing about a hundred messages and being on line for an hour, or so, things get very slow. Getting mail from /var/mqueue/* takes much longer than at startup. It takes 20 to 30 seconds to sort a hundred headers. Editing in another frame appears normal. I'm not sure about Emacs 19.34, however I've personally been using Emacs 20.2 for a long time now under CURRENT without any problems. You might want to give that a try. We have a port of it, editors/emacs20. TTYL, -Justin Seger- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 11 09:01:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA20466 for freebsd-current-outgoing; Sat, 11 Apr 1998 09:01:28 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ren.dtir.qld.gov.au (firewall-user@ns.dtir.qld.gov.au [203.108.138.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA20461 for ; Sat, 11 Apr 1998 09:01:26 -0700 (PDT) (envelope-from syssgm@dtir.qld.gov.au) Received: by ren.dtir.qld.gov.au; id BAA07463; Sun, 12 Apr 1998 01:59:06 +1000 (EST) Received: from ogre.dtir.qld.gov.au(167.123.8.3) by ren.dtir.qld.gov.au via smap (3.2) id xma007458; Sun, 12 Apr 98 01:58:42 +1000 Received: from troll.dtir.qld.gov.au (troll.dtir.qld.gov.au [167.123.8.1]) by ogre.dtir.qld.gov.au (8.8.7/8.8.7) with ESMTP id BAA05653 for ; Sun, 12 Apr 1998 01:58:42 +1000 (EST) Received: from localhost (syssgm@localhost) by troll.dtir.qld.gov.au (8.8.5/8.8.5) with SMTP id BAA06262; Sun, 12 Apr 1998 01:58:38 +1000 (EST) Message-Id: <199804111558.BAA06262@troll.dtir.qld.gov.au> X-Authentication-Warning: troll.dtir.qld.gov.au: syssgm@localhost didn't use HELO protocol To: freebsd-current@FreeBSD.ORG cc: syssgm@dtir.qld.gov.au Subject: Re: whose english is it anyway? References: <00d501bd6504$3e926ce0$c9252fce@cello.synapse.net> In-Reply-To: <00d501bd6504$3e926ce0$c9252fce@cello.synapse.net> from "Evan Champion" at "11 Apr 1998 14:41:37 +1000" Date: Sun, 12 Apr 1998 01:58:38 +1000 From: Stephen McKay Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Saturday, 11th April 1998, "Evan Champion" wrote: >>> On Sat, 11 Apr 1998, John Birrell wrote: >>> > Chad M. Fraleigh wrote: >>> > > "authorisation" should be "authorization". >>> > >>> > In my _*English*_ dictionary, either is acceptable. >Given that FreeBSD is largely an American >project, consistent use of American spellings would seem to be the most >appropriate solution (as much as I prefer British English :-) I don't like the way this was phrased. Is FreeBSD an American project? I think of it as a global project, and I hope most other people do too. The American flavour is an accident of birth, not a central feature. Rather than promote consistent American spelling I would prefer to retain the original author's dialect on a file by file basis. Yes, this is a rather odd view to hold in today's monoculture. Perhaps it comes from using a minority language (Australian English) and a minority within a minority OS (FreeBSD as a subset of Unix). I like to think of it as a sort of conservation of variety, a parallel to the conservation of genetic diversity that people are just starting to wake up to. So, after all that rambling, let's keep any correct spelling, even if it isn't what you would have used yourself. Stephen. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 11 09:29:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA23896 for freebsd-current-outgoing; Sat, 11 Apr 1998 09:29:52 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from set.spradley.tmi.net (set.spradley.tmi.net [207.170.107.99]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA23885 for ; Sat, 11 Apr 1998 09:29:49 -0700 (PDT) (envelope-from tsprad@set.spradley.tmi.net) Received: from localhost (set.spradley.tmi.net) [127.0.0.1] by set.spradley.tmi.net with esmtp (Exim 1.82 #2) id 0yO39h-0000th-00; Sat, 11 Apr 1998 11:29:25 -0500 X-Mailer: exmh version 2.0zeta 7/24/97 To: Stephen McKay cc: freebsd-current@FreeBSD.ORG Subject: Re: whose english is it anyway? In-reply-to: Your message of "Sun, 12 Apr 1998 01:58:38 +1000." <199804111558.BAA06262@troll.dtir.qld.gov.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 11 Apr 1998 11:29:25 -0500 From: Ted Spradley Message-Id: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [...] > a sort of conservation of variety, a parallel to the conservation of > genetic diversity that people are just starting to wake up to. Very nicely stated. Thank you. > So, after all that rambling, let's keep any correct spelling, even if > it isn't what you would have used yourself. There are plenty of much worse spelling errors to be found. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 11 09:44:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA26249 for freebsd-current-outgoing; Sat, 11 Apr 1998 09:44:10 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from hwcn.org (ac199@james.hwcn.org [199.212.94.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA26241 for ; Sat, 11 Apr 1998 09:44:09 -0700 (PDT) (envelope-from hoek@hwcn.org) Received: from localhost (ac199@localhost) by hwcn.org (8.8.8/8.8.8) with SMTP id MAA02080; Sat, 11 Apr 1998 12:38:56 -0400 (EDT) Date: Sat, 11 Apr 1998 12:38:56 -0400 (EDT) From: Tim Vanderhoek To: John Birrell cc: John Fieber , chadf@bookcase.com, current@FreeBSD.ORG Subject: Re: Misspelling in lib/libutil/login_cap.3 [w/ patch] In-Reply-To: <199804110418.OAA08739@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 Sat, 11 Apr 1998, John Birrell wrote: > > > In my _*English*_ dictionary, either is acceptable. > > > > Citation please? > > The Concise Oxford Dictionary 5th edition. Printed in Great Britain. FWIW, I've never cared much for the use of dictionaries when composing, be they Australian, American, or English. It's my damn language, not theirs. > > It may be acceptable somewhere, but I dare say that the "z" > > version is much more widely accepted. > > Sorry, at school I was taught English, not American. This `s' for `z' thing is something I've thought about ever since I yelled at someone for Zzzing the Zed in their alphabet. In general I much prefer "English"-english to "American"-english, but the `z's are something they got right. Hello! We're wasting a whole letter of the alphabet simply because some people are too caught-up in some sort of anti-American nationalistic pride. Unless you really pronounce "authori[sz]e" with the same loud strong audible `s' sound you use in "Sorry", I believe it should be left as "authorize". Besides all that, it's even more important to be consistent. I don't _don't_ want to read manpages that use "s" on one line, and "z" on the next. Yuck, yuck, yuck. And if you suggest that one manpage can use one alternate spelling, and another manpage another alternate spelling, then I will calmly (or not so) explain that we have enough trouble making people edit manpages without making them first read through the manpage to decide which of several alternate spellings they are supposed to use for various words. -- Outnumbered? Maybe. Outspoken? Never! tIM...HOEk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 11 14:25:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA09978 for freebsd-current-outgoing; Sat, 11 Apr 1998 14:25:30 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA09962; Sat, 11 Apr 1998 14:25:27 -0700 (PDT) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.8.8/8.8.8) with UUCP id XAA11294; Sat, 11 Apr 1998 23:25:24 +0200 (CEST) (envelope-from j@uriah.heep.sax.de) Received: (from j@localhost) by uriah.heep.sax.de (8.8.8/8.8.5) id XAA16570; Sat, 11 Apr 1998 23:12:48 +0200 (MET DST) Message-ID: <19980411231247.52126@uriah.heep.sax.de> Date: Sat, 11 Apr 1998 23:12:47 +0200 From: J Wunsch To: freebsd-scsi@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Cc: Julie Juracich Subject: Re: Problems with Adaptec2920 driver Reply-To: Joerg Wunsch References: <199804050645.WAA08022@grue.xaqti.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: <199804050645.WAA08022@grue.xaqti.com>; from Julie Juracich on Sat, Apr 04, 1998 at 10:45:33PM -0800 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As Julie Juracich wrote: > I have now gone to FreeBSD-CURRENT, and I have tried both that driver > and the patch located here: > ftp://ftp.freebsd.org/pub/FreeBSD/2.2.6-RELEASE/xperimnt/aha2920/tmc18c30-sysdif > f.gz (Btw., your mailer spams long lines. Better replace it.) Sorry, as you can see, i've once hacked this driver kit for 2.2-stable (by the time 2.2.5 has been prepared). While i have been gradually upgrading my -current spam box with this driver enabled, recently it failed compilation with the same problems you are seeing. I haven't found the time yet to even look at what the problems are. (Well, i made a glance on them, but couldn't find the reason within 5 minutes, so i gave up and disabled ahd(4) on this box, in order to get a compilable -current kernel at all.) ahd(4) definately needs someone who'd adopt this baby. Anyway, IMHO it needs some restructuring and ``FreeBSDization'' before getting imported. Also, whoever would like to pick up that job, should be prepared to assist Justin in moving the driver into CAM. I'm definately and ultimately completely out of time for this job. (I've still got one of those cards, and could do testing however.) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 11 15:11:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA18507 for freebsd-current-outgoing; Sat, 11 Apr 1998 15:11:45 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA18500 for ; Sat, 11 Apr 1998 15:11:41 -0700 (PDT) (envelope-from rb@gid.co.uk) Received: from gid.co.uk (uucp@localhost) by isbalham.ist.co.uk (8.8.7/8.8.4) with UUCP id XAA11595; Sat, 11 Apr 1998 23:10:34 +0100 (BST) Received: from [194.32.164.2] by seagoon.gid.co.uk; Sat, 11 Apr 1998 23:05:39 +0100 (BST) X-Sender: rb@194.32.164.1 Message-Id: In-Reply-To: References: <19980411143046.35436@rf900.physics.usyd.edu.au> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sat, 11 Apr 1998 23:00:30 +0100 To: John Fieber , David Dawes From: Bob Bishop Subject: Re: Misspelling in lib/libutil/login_cap.3 [w/ patch] Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 5:40 am +0100 11/4/98, John Fieber wrote: >OED 2nd edition is 1989, suggesting that the "s" form may be out >of fashion, but I would really expect that to be noted if it were >the case rather than just omitting it. After all, word history >is one of the greatest strengths of the OED. > >Puzzling.... Current edition of Chambers (used here as reference by all the crosswords, Scrabble etc) gives both with s preferred; I guess this is the best reference to current usage in the UK. -- Bob Bishop (0118) 977 4017 international code +44 118 rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 11 16:27:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA29218 for freebsd-current-outgoing; Sat, 11 Apr 1998 16:27:20 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [206.246.122.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA29211 for ; Sat, 11 Apr 1998 16:27:16 -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 SAA00485 for ; Sat, 11 Apr 1998 18:26:34 -0400 (EDT) Date: Sat, 11 Apr 1998 18:26:34 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@localhost To: FreeBSD-current@FreeBSD.ORG Subject: disk damage 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 just had my first panic in about 9 months, and I think I took some real disk damage on one of my disks. I was doing a buildworld, and the disk that had obj on it took a big hit. I found the normal fsck failing because it told me that link counts were rising, so I did that manually and told it not to make fixes for link counts that were too low. fsck completed then, and I successfully mounted, and the only damage I can really see is in obj. When I subsequently tried to rm -rf the obj dir, I got errors from rm of: rm: usr/src/usr.bin: Bad file descriptor rm: usr/src/usr.sbin: Bad file descriptor [extra error list, about 8, removed] I tried to do an ls of those directories, and got: ls: usr.bin: Bad file descriptor ls: usr.sbin: Bad file descriptor Should I continue to delete these guys, and if so, how? ----------------------------+----------------------------------------------- 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, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 11 18:39:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA19691 for freebsd-current-outgoing; Sat, 11 Apr 1998 18:39:55 -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 SAA19676 for ; Sat, 11 Apr 1998 18:39:52 -0700 (PDT) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id UAA02518; Sat, 11 Apr 1998 20:39:44 -0500 (EST) (envelope-from toor) Message-Id: <199804120139.UAA02518@dyson.iquest.net> Subject: Re: disk damage In-Reply-To: from Chuck Robey at "Apr 11, 98 06:26:34 pm" To: chuckr@glue.umd.edu (Chuck Robey) Date: Sat, 11 Apr 1998 20:39:44 -0500 (EST) Cc: FreeBSD-current@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@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 Chuck Robey said: > > rm: usr/src/usr.bin: Bad file descriptor > rm: usr/src/usr.sbin: Bad file descriptor > [extra error list, about 8, removed] > > I tried to do an ls of those directories, and got: > > ls: usr.bin: Bad file descriptor > ls: usr.sbin: Bad file descriptor > > Should I continue to delete these guys, and if so, how? > Try doing fsck after the attempted rm commands. Make sure that you reboot with -s, before the additional fsck commands. -- John | Never try to teach a pig to sing, dyson@freebsd.org | it just makes you 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 Sat Apr 11 18:47:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA21619 for freebsd-current-outgoing; Sat, 11 Apr 1998 18:47:31 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [206.246.122.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA21185; Sat, 11 Apr 1998 18:46:16 -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 UAA06116; Sat, 11 Apr 1998 20:45:36 -0400 (EDT) Date: Sat, 11 Apr 1998 20:45:36 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@localhost To: "John S. Dyson" cc: FreeBSD-current@FreeBSD.ORG Subject: Re: disk damage In-Reply-To: <199804120139.UAA02518@dyson.iquest.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 Sat, 11 Apr 1998, John S. Dyson wrote: > Chuck Robey said: > > > > rm: usr/src/usr.bin: Bad file descriptor > > rm: usr/src/usr.sbin: Bad file descriptor > > [extra error list, about 8, removed] > > > > I tried to do an ls of those directories, and got: > > > > ls: usr.bin: Bad file descriptor > > ls: usr.sbin: Bad file descriptor > > > > Should I continue to delete these guys, and if so, how? > > > Try doing fsck after the attempted rm commands. Make sure that > you reboot with -s, before the additional fsck commands. Thanks. I finally got desperate enough to try fsdb (after doing many cycles of rm/fsck's with no effect) and that did it. I had a bunch of directories pointing to inode 0. > > -- > John | Never try to teach a pig to sing, > dyson@freebsd.org | it just makes you look stupid, > jdyson@nc.com | and it irritates the pig. > > ----------------------------+----------------------------------------------- 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, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 11 19:16:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA24781 for freebsd-current-outgoing; Sat, 11 Apr 1998 19:16:11 -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 TAA24679; Sat, 11 Apr 1998 19:15:27 -0700 (PDT) (envelope-from grog@lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.8.7/8.8.5) with ESMTP id LAA21864; Sun, 12 Apr 1998 11:45:22 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.8.8/8.8.7) id LAA24215; Sun, 12 Apr 1998 11:45:20 +0930 (CST) (envelope-from grog) Message-ID: <19980412114520.A24192@freebie.lemis.com> Date: Sun, 12 Apr 1998 11:45:20 +0930 From: Greg Lehey To: Amancio Hasty , Cory Kempf Cc: multimedia@FreeBSD.ORG, freebsd-current@FreeBSD.ORG, FreeBSD Chat Subject: Re: Sound on DK440LX? Reply-To: FreeBSD Chat References: <199804100347.UAA09169@rah.star-gate.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91i In-Reply-To: <199804100347.UAA09169@rah.star-gate.com>; from Amancio Hasty on Thu, Apr 09, 1998 at 08:47:00PM -0700 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 Thu, 9 April 1998 at 20:47:00 -0700, Amancio Hasty wrote: >> As per Greg's request, this is being re-sent to -current. Sorry if you are >> seeing this twice. >> >> FWIW, I am running a slightly old current. > > Greg should have forwarded you to the multimedia mailing list :( Good question. I've currently been evangalizing a little on -questions to get people running -CURRENT to post their views on -CURRENT. What do you people think? Is that still the right thing to do when the question relates to multimedia (as in this case) or Emacs mail (as in another recent case)? I know you (Amancio) are trying to increase the volume and the visibility of the multimedia list, but that's not the case in all lists, and it would be nice to have a uniform "right" way of doing things. Followup to -chat, please. Greg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 11 19:38:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA27990 for freebsd-current-outgoing; Sat, 11 Apr 1998 19:38:40 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com (rah.star-gate.com [209.133.7.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA27982; Sat, 11 Apr 1998 19:38:38 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id TAA12732; Sat, 11 Apr 1998 19:38:35 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199804120238.TAA12732@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: FreeBSD Chat cc: Cory Kempf , multimedia@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: Sound on DK440LX? In-reply-to: Your message of "Sun, 12 Apr 1998 11:45:20 +0930." <19980412114520.A24192@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 11 Apr 1998 19:38:35 -0700 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I don't mean to sound rude . Multimedia related questions to -multimedia. The primary reason for doing so is focus additionally we frequently have to deal with issues that are not related to FreeBSD. As we grow we have to attempt comparmentilize the mailing lists for I am sure that the -current or -hackers readers will not appreciate a flood of questions: like my sound card does not work . Damn, I can't get my Bt848 to recognize my tuner, etc... Last but not least I am not putting this out to a democratic vote and as a contributor I appreciate the groups support in this matter. Tnks, Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 11 22:50:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA21884 for freebsd-current-outgoing; Sat, 11 Apr 1998 22:50:32 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from quokka.prth.tensor.pgs.com (quokka1.prth.tensor.pgs.com [157.147.224.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA21878; Sat, 11 Apr 1998 22:50:28 -0700 (PDT) (envelope-from shocking@ariadne.prth.tensor.pgs.com) Received: from ariadne.tensor.pgs.com (ariadne [157.147.227.36]) by quokka.prth.tensor.pgs.com (8.8.7/8.8.7) with SMTP id NAA15721; Sun, 12 Apr 1998 13:49:43 +0800 (WST) Received: from ariadne by ariadne.tensor.pgs.com (SMI-8.6/SMI-SVR4) id NAA11442; Sun, 12 Apr 1998 13:49:36 +0800 Message-Id: <199804120549.NAA11442@ariadne.tensor.pgs.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Ken Krebs cc: current@FreeBSD.ORG, multimedia@FreeBSD.ORG Subject: Re: Patches to Linux emulator enc. In-reply-to: Your message of "Fri, 10 Apr 1998 11:29:23 MST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 12 Apr 1998 13:49:36 +0800 From: Stephen Hocking-Senior Programmer PGS Tensor Perth Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [problems snipped] You need to do a make in /sys/i386/linux (it's actually make something, but just typing make will tell you what it is) to regen various files and then a make depend et cetera in /usr/src/lkm/linux. Stephen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 11 23:09:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA24397 for freebsd-current-outgoing; Sat, 11 Apr 1998 23:09:02 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from www.giovannelli.it (www.giovannelli.it [194.184.65.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA24390 for ; Sat, 11 Apr 1998 23:08:57 -0700 (PDT) (envelope-from gmarco@giovannelli.it) Received: from giovannelli.it (modem00.masternet.it [194.184.65.254]) by www.giovannelli.it (8.8.8/8.8.5) with ESMTP id IAA00263 for ; Sun, 12 Apr 1998 08:06:08 +0200 (MET DST) Message-ID: <35307774.286EE4AC@giovannelli.it> Date: Sun, 12 Apr 1998 08:12:36 +0000 From: Gianmarco Giovannelli X-Mailer: Mozilla 4.05 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: make world troubles with share/doc/smm/07.lpd Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG After cvsupping this morning (980412) I tried the daily make world but : 1) Soon an error in the make clean complaining about the missing 07.lpd dir in obj tree ... created this dir make world proceeded but it stoped here : 2) ===> share/doc/smm/06.nfs install -c -o bin -g bin -m 444 paper.ascii.gz /usr/share/doc/smm/06.nfs ===> share/doc/smm/07.lpd install -c -o bin -g bin -m 444 bsd.README bsd.dep.mk bsd.doc.mk bsd.info.mk bsd.kern.mk bsd.kmod.mk bsd.lib.mk bsd.libnames.mk bsd.man.mk bsd.obj.mk bsd.own.mk bsd.port.mk bsd.port.subdir.mk bsd.prog.mk bsd.sgml.mk bsd.subdir.mk sys.mk /mk usage: install [-CcDps] [-f flags] [-g group] [-m mode] [-o owner] file1 file2 install [-CcDps] [-f flags] [-g group] [-m mode] [-o owner] file1 ... fileN directory install -d [-g group] [-m mode] [-o owner] directory ... *** Error code 64 Stop. *** Error code 1 but I have this dir : gmarco:/usr/src#ll /usr/share/doc/smm/ total 18 drwxr-xr-x 2 bin bin 512 Apr 12 08:02 01.setup drwxr-xr-x 2 bin bin 512 Apr 12 08:02 02.config drwxr-xr-x 2 bin bin 512 Apr 12 08:02 03.fsck drwxr-xr-x 2 bin bin 512 Apr 12 08:02 04.quotas drwxr-xr-x 2 bin bin 512 Apr 12 08:02 05.fastfs drwxr-xr-x 2 bin bin 512 Apr 12 08:02 06.nfs drwxr-xr-x 2 bin bin 512 Apr 10 22:16 07.lpd drwxr-xr-x 2 bin bin 512 Apr 10 22:15 08.sendmailop drwxr-xr-x 2 bin bin 512 Apr 10 22:15 09.sendmail drwxr-xr-x 2 bin bin 512 Apr 10 22:15 10.named drwxr-xr-x 2 bin bin 512 Apr 10 22:15 11.timedop drwxr-xr-x 2 bin bin 512 Apr 10 22:15 12.timed drwxr-xr-x 2 bin bin 512 Apr 10 22:15 18.net -r--r--r-- 1 bin bin 2367 Apr 12 08:02 Title.ascii.gz -r--r--r-- 1 bin bin 1669 Apr 12 08:02 contents.ascii.gz But I haven't it in the obj tree : gmarco:/usr/obj/usr/src/share/doc/smm#ll total 14 drwxr-xr-x 2 root bin 512 Apr 12 07:49 01.setup drwxr-xr-x 2 root bin 512 Apr 12 07:49 02.config drwxr-xr-x 2 root bin 512 Apr 12 07:49 03.fsck drwxr-xr-x 2 root bin 512 Apr 12 07:49 04.quotas drwxr-xr-x 2 root bin 512 Apr 12 07:49 05.fastfs drwxr-xr-x 2 root bin 512 Apr 12 07:49 06.nfs drwxr-xr-x 2 root bin 512 Apr 12 07:49 08.sendmailop drwxr-xr-x 2 root bin 512 Apr 12 07:49 09.sendmail drwxr-xr-x 2 root bin 512 Apr 12 07:49 10.named drwxr-xr-x 2 root bin 512 Apr 12 07:49 11.timedop drwxr-xr-x 2 root bin 512 Apr 12 07:49 12.timed drwxr-xr-x 2 root bin 512 Apr 12 07:49 18.net drwxr-xr-x 2 root bin 512 Apr 12 07:49 contents drwxr-xr-x 2 root bin 512 Apr 12 07:49 title Uhm, if it is a newbie statment forget it and take this message only as an Happy Easter to everyone... :-) -- Regards... Gianmarco "Unix expert since yesterday" http://www.giovannelli.it To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 11 23:27:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA25916 for freebsd-current-outgoing; Sat, 11 Apr 1998 23:27:06 -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 XAA25892 for ; Sat, 11 Apr 1998 23:27:05 -0700 (PDT) (envelope-from toasty@home.dragondata.com) Received: (from toasty@localhost) by home.dragondata.com (8.8.8/8.8.5) id BAA00788 for current@freebsd.org; Sun, 12 Apr 1998 01:27:01 -0500 (CDT) From: Kevin Day Message-Id: <199804120627.BAA00788@home.dragondata.com> Subject: f00f + SMP = ick To: current@FreeBSD.ORG Date: Sun, 12 Apr 1998 01:27:00 -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 can pretty much confirm that SMP -current kernels are are still vulnerable to the f00f attack... Running the exploit once doesn't do anything... Putting it in a while loop, and then putting the machine under heavy load will kill it though... I've walked into my screensaver running with my chuck daemon just sitting there 3 times now. (rmusering another customer as we speak...) Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message